pull down to refresh
113 sats \ 18 replies \ @analogue 1 Jul 2022 freebie \ parent \ on: Damus is a Nostr client with Lightning ⚡️ integration nostr
The only way to be able to delete something that you made public in the past, is to exclusively host it yourself, at all times.
Such a feature is not compatible with any kind of decentralization.
This is a false dichotomy.
We both know that there are multiple different solutions, if people actually care about UX.
Soft-deletes is one option. Private groups is another option.
overall, I just don’t like the architecture. I’m more interested in decentralized networks that have forward secrecy and don’t assume that you want your data blasted to every corner of the earth. Again, that idea is useful for some things, but not for a normal social user imo.
reply
Could we encrypt the data in a way that to unencrypt it one would need current permission from the originator? This way it lives in the network, but only included parties can actually view the info.
reply
Yeah that is the “private group” idea.
Your data is encrypted and all the nodes are doing is passing around decryption keys to the people that you want to see it. So the nodes just pass keys and pointers to data rather than data itself.
But NOSTR architecture simply doesn’t allow this kind if thing. It’s not what it is built for.
reply
I thought the inverse. Nodes could distribute the data, so it can have redundancy, but you directly give decryption keys to those who you actually want to give access to viewing the data.
reply
But again, once a client has the encrypted data and the decryption key, you cannot make them forget those 2, and thus you cannot delete your data.
This idea that "right to be forgotten" can be implemented in a decentralized solution is false.