Your landing page at https://remote.storage/ is so good, I love the minimalism. Six lines of code tell me exactly what it does.
Show HN: RemoteStorage – sync localStorage across devices and browsers
11–20 of 69 posts
Re: Show HN: RemoteStorage – sync localStorage across devices and browsers
#12Re: Show HN: RemoteStorage – sync localStorage across devices and browsers
#13Re: Show HN: RemoteStorage – sync localStorage across devices and browsers
#14[1]: https://pouchdb.com/
Re: Show HN: RemoteStorage – sync localStorage across devices and browsers
#15The developer's backend could issue a JWT, which is validated by the remoteStorage backend. Then, use the `sub` field as the user ID. JWTs are pretty ubiquitous in frontend applications, so many people would be able to reuse their existing auth setup.
Re: Show HN: RemoteStorage – sync localStorage across devices and browsers
#16On the authentication front - JWTs would be a great fit here! The developer's backend could issue a JWT, which is validated by the remoteStorage backend. Then, use the `sub` field as the user ID. JWTs are pretty ubiquitous in frontend applications, so many people would be able to reuse their existing auth setup.
Re: Show HN: RemoteStorage – sync localStorage across devices and browsers
#17An OpenAPI spec should be enough, right?
Re: Show HN: RemoteStorage – sync localStorage across devices and browsers
#18How does this compare to PouchDB[1]? [1]: https://pouchdb.com/
I think the main difference here is the use case. remoteStorage is not intended to be used as a database (just like localStorage is not intended to either), but rather to store non PII data such as preferences, impression events, etc. without having to roll and stand up your own DB and API.
Re: Show HN: RemoteStorage – sync localStorage across devices and browsers
#19Re: Show HN: RemoteStorage – sync localStorage across devices and browsers
#20What is special with the server? I was surprised you offered a community-hosted server. An OpenAPI spec should be enough, right?
The server is nothing special by design, just essentially Docker/Node/Redis with persistence enabled.
The free hosted community server is supposed to be used for testing / proof of concept.