Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Another remotestorage #22

Closed
rosano opened this issue Jan 24, 2024 · 4 comments
Closed

Another remotestorage #22

rosano opened this issue Jan 24, 2024 · 4 comments

Comments

@rosano
Copy link

rosano commented Jan 24, 2024

This looks great, congrats on your release 👍🏽. Good that your server is also designed to be self-hosted. Have you considered making it available for 'one-click' deploys?

I can't help but think of the remoteStorage project that's been around since at least 2010 I guess it's a reflection of how programmers tend to name things… Anyway maybe there's a way to connect the two projects when there are shared goals. The community project seeks to become an internet standard. Will also post this elsewhere as I'm not sure which channel is best.

@christianmat
Copy link
Contributor

One click deploys is coming soon!

On your other note, I think the two projects are substantially different. While this project simply seeks to create a secure backend for localStorage, the project you linked has a ton of features that have nothing to do with the goal of this project (e.g. linking your Dropbox or Google Drive account). They have very little in common except for the name.

@raucao
Copy link

raucao commented Jan 30, 2024

remoteStorage is the name of the protocol. The reference client library called remoteStorage.js (note the .js) also has support for other back-ends, but that has nothing to do with the remoteStorage protocol.

Here is the IETF tracker for the spec: https://datatracker.ietf.org/doc/draft-dejong-remotestorage/

The two projects do have quite a bit in common actually. The idea of the remoteStorage protocol is also to sync your localStorage across devices, but it has auth and folder permissions for apps baked in via OAuth, and it is more focused on letting users choose which server syncs their data (can be custodial or self-hosted).

Considering that the remoteStorage name and spec have been around for over a decade now, and that people are already confused about this one being connected to the original one in some way, I think it would be reasonable to consider a name change to eliminate more misunderstandings in the future, and to make it easier to find this project on search engines in the first place.

@christianmat
Copy link
Contributor

Appreciate the feedback. Closing this for now, but will keep this in the mind as both projects evolve in the future.

@DustinWehr
Copy link

DustinWehr commented Feb 18, 2024

I wasted a lot of time because of this.
I like how easy to use your API is, but for the love of god, change the name.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants