It’s in my plan to launch relay just to store this for users. Do you think that would be a good idea that would partially solve this?
Discussion
I don't think clients should run relays. Not doing so forces clients and relays to come up with an incentive model for the service they're offering. If a client runs a relay for their special purpose, the relay is artificially supported by the client service. If the incentive model for other relays to exist doesn't exist, the client becomes a centralized service with a front end and a database for the majority of users.
Of course, you could run your own to experiment with how such a relay should operate, but an accepted model for relays to accommodate encrypted data needs to emerge.
I have a thought about you saying “storing sensitive data”. I was thinking we can make a specialised relay, open source relay, for storing all sensitive data. So anyone can spin up their own if they like. Otherwise, we can host one or two too.
Yeah, client operators running a particular type of relay for a particular use case is totally fine. I think something like pay per event might work. Keeping a balance might be tricky though if the user wants to stay anonymous (as is common with encrypted data). Maybe a relay could issue a payment key out of band and have the client AUTH with that?
Food for thought.
If you have similar use case, and we can get more hands on deck to design something.
Yes, let's put a pin in it. I want to address this at some point, but don't currently have the time and public relays seem to be ok with encrypted data for the most part. Once they start rejecting encrypted events and it breaks Coracle this will be top of the list.