Naturally, the more I think about it, the more I come with refined requirements
I’d like the service to work anonymously. A user will generate or choose a uniq name (preferably complicated), and only those who know the name will access the data.
Something similar to etherpad, but to sync key-value pairs.
The second requirement here would require some form of authentication (not that you have to implement this) as there would need to be some form of identification when accessing the data. This conflicts with the first requirement of the data access being, essentially, only a password.
As far as the anonymity of an account, that’s hard to say as it can vary by service used or implementation. E.g. if you setup authentication through a magic link setup (sends a unique code to an email) then the anonymity is determined by the email address used.
I’m considering a message bus like NATS. I already used it to implement a chat in Elm. Just a port to create to bind the websocket and send/receive messages. Was nice.
But still, I have to find a way to segregate users data. I don’t thing it is possible to create a topic in Nats on the fly …
This is very doable with Lamdera and you could have this setup in a few minutes. However you’d want to be careful about what you put into this system. It’s not secure at all. As you said before
and this isn’t practical for the system you’re describing.
If you want information to be publicly available, then this is a perfectly fine setup to have. If you want people to put private information in this system then I’d recommend something with user authentication.