I'm not very technical so pardon my language. Why does the client need the data and the key? Is client the same as end-user?

I understand that once a person decrypts a file, they could then copy and share that file, but I'm talking about a circumstance in which ONLY the intended person has the keys to decrypt the file. In that case, it wouldn't matter if the network still has a copy of the file, or if the originator decides to delete it from the network and some nodes refuse to comply because they'd just have an encrypted file in their node.

Yes, the client code can be told to delete the data. The fact that someone *could* alter their client to ignore these rules doesn’t mean that you should *ensure* that *everyone* ignores them lol. 


Right to be forgotten could be implemented in multiple ways, but you simply don’t care and you’re not interested. Which is why these types of products fail. Because the people that make them don’t care about UX. 

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.

analogue

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.

premitive1

nostr

Damus is a Nostr client with Lightning ⚡️  integration 

moel

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. 