3 ms·

This is interesting and (like everyone else) I have a few questions: - Will this be based on open, industry standard protocols? - It looks like there are mult

This is interesting and (like everyone else) I have a few questions: - Will this be based on open, industry standard protocols? - It looks like there are multiple applications combined into one giant system in the web- and Android apps right now. Will those be interchangeable (with say, third party implementations)? Are the apps somehow connected (do the music player and the gallery for example get their content from the drive)? (Basically, does it follow something like the Unix principles [1]?) - Can I self-host this without AWS? If no were there any privacy/ethical considerations taken around the decision to go full-AWS? I know these are critical questions but as a potential customer I'd like to know this kinda stuff. I understand if you don't have answers to everything atm though and I like the spirit of this project! :) [1] https://en.wikipedia.org/wiki/Unix_philosophy https://en.wikipedia.org/wiki/Unix_philosophy

LamaOfRuin 7y ago
It looks like the download manager, music player, and gallery are all built to work with the drive. The other ones that could don't say and don't really require much storage so it's not clear if the raw data is stored on the drive in case you want it.
z0mbie42 7y ago
(1) Currently not really, we have a (self made) HTTP API, and S3 API support for blob storage. We don not support (and do not have yet examined things like WebDAV...) (2) You can see current Bloom as an Unikernel, So yes the music player and the gallery lets you play files directly from your Drive :) One things like oauth will be implemented I see no constraint to use third party implementations (planned for Q4 2019). (3) Totally, Better self hosting documentation is planned for next version: https://gitlab.com/groups/bloom42/-/epics/5 https://gitlab.com/groups/bloom42/-/epics/5
- t0astbread 7y ago
  Thank you, this sounds pretty promising (and ambitious) so far. Will watch this project for the future!

LamaOfRuin 7y ago

It looks like the download manager, music player, and gallery are all built to work with the drive. The other ones that could don't say and don't really require much storage so it's not clear if the raw data is stored on the drive in case you want it.

z0mbie42 7y ago

(1) Currently not really, we have a (self made) HTTP API, and S3 API support for blob storage. We don not support (and do not have yet examined things like WebDAV...) (2) You can see current Bloom as an Unikernel, So yes the music player and the gallery lets you play files directly from your Drive :) One things like oauth will be implemented I see no constraint to use third party implementations (planned for Q4 2019). (3) Totally, Better self hosting documentation is planned for next version: https://gitlab.com/groups/bloom42/-/epics/5 https://gitlab.com/groups/bloom42/-/epics/5

t0astbread 7y ago
Thank you, this sounds pretty promising (and ambitious) so far. Will watch this project for the future!