3 ms·
Reminds me of https://remotestorage.io/ https://remotestorage.io/ which I have used in a (mostly personal) website. I like that I can provide a service as a sta
by kevincox 6y ago
Reminds me of https://remotestorage.io/ https://remotestorage.io/ which I have used in a (mostly personal) website. I like that I can provide a service as a static website, and users pay for, manage and have control over their own storage. One of the things that could help it bootstrap is that they also support client-side Google Drive and Dropbox shims, so users who want to use something else can, but most users will just use one or the other.
There are downsides though.
- The API may be less than ideal for some use cases. This can make a well-performing app hard. For example there is no relational-sql API.
- You can't migrate user's data. So if you make changes to the format you need to retain backwards compatibility "forever".
- If you want to provide "discovery" or cross-user features you will need to have your own storage anyways.
- anderspitman 6y agoI actually started working on just such a shim yesterday. The idea is to represent all major cloud storage through a single simple frontend API. You have to implement each provider's OAuth flow, but once you have the files it's pretty much the same. Dropbox, Google, and my own protocol[0] will come first, but Solid is planned eventually. What I've learned so far: * Google is extremely draconian unless you use their JavaScript picker. To really integrate nicely you would have to spend at least $15000-$75000 getting your app audited by a 3rd party. * Dropbox picker integration is very easy and slick. [0]: https://github.com/gemdrive https://github.com/gemdrive