Again, all your trust is client side. Any client can act legit to the network and still save everything it sees, there is no way for the network to know about it, and your right to be forgotten cannot be trusted.

BTW: I appreciate your last post, I just cannot see how what you ask is possible, and IMO it's not fair to ask for such an impossible feature to the Nostr or any other network.

You keep saying things without backing them up. Just stop or throw concrete examples. I'll stop replying until you do.

That's true. If you believe otherwise, ask yourself why this has not been done before.

To avoid the overhead of having to manage 2 wallets, and some peers accept only L1, and some only L2.

Some context would help ;)

You keep repeating you can do this, but never explain how.

Keys to what data? The encrypted data needs to exist somewhere. Once any entity had access to both the encrypted data, or the decryption key anywhere anytime, even if those are not the same entity, you cannot guarantee that data cannot ever be decrypted.

The right to be forgotten is pointless if you can't ensure that the data is sure to be deleted. It's not a UX problem.

Yes: Stacker News > Reddit > Twitter in term of signal to noise, or even trigger ability.

There is no difference between the original and a copy in a digital world.

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.

Such a good piece summing up the situation.

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.

But then, won't it add to the inflation?