Even on centralized platforms you can never be certain about deletion since others can screenshot/archive. So I’m going to assume you are looking for a reasonably effective delete/edit solution that competes with what’s out there.
We might get reasonably effective delete/edit functionality within coordinated clients at some point, but it will never ever be absolute. A proper decentralized solution here also requires time stamps… and everybody hates the guy that made NIP-03 possible right now so I don’t see it being solved soon.
The thing that really matters for deletion anyway is media- which is a reference that you can (and should) maintain control of. Delete the source and voila. But the screenshotting/right-clicking risk remains.
I was in the no-delete absolutist camp until Rizful.com (nprofile…0un9) correctly made a point that kids can be dumb and should be able to delete photos. So I agree with his concerns there (and encourage people to self host media if that’s a concern). I remain skeptical of the feasibility of deleting direct event data contained in JSON that is broadcast and bounced around relays beyond anyone’s control.
Ultimately decentralized designs require tradeoffs, and this is one issue among many that get amplified… and where the only true solution is *personal responsibility*. It is not solvable in an absolute sense, and all solutions require tradeoffs towards centralization (yes, including client coordination).
EricFJ / Eric FJ
npub10x…2g437
2025-05-18 00:31:12
in reply to nevent1q…auw5
Author Public Key
npub10xvczstpwsljy7gqd2cselvrh5e6mlerep09m8gff87avru0ryqsg2g437Published at
2025-05-18 00:31:12Event JSON
{
"id": "e6e49f4063d89f2599f361331ece3d29b4f36e5c2832262118328d89ea8ed0d8",
"pubkey": "7999814161743f2279006ab10cfd83bd33adff23c85e5d9d0949fdd60f8f1901",
"created_at": 1747528272,
"kind": 1,
"tags": [
[
"e",
"929dd96e40edfb68d15f388b949869ab05834b37eed38fdcc3270233e2303a82",
"wss://nproxy.kristapsk.lv",
"root"
],
[
"p",
"97f848adcc4c6276685fe48426de5614887c8a51ada0468cec71fba938272911",
"wss://relay.snort.social/",
"mention"
],
[
"p",
"ee6ea13ab9fe5c4a68eaf9b1a34fe014a66b40117c50ee2a614f4cda959b6e74",
"",
"mention"
]
],
"content": "Even on centralized platforms you can never be certain about deletion since others can screenshot/archive. So I’m going to assume you are looking for a reasonably effective delete/edit solution that competes with what’s out there. \n\nWe might get reasonably effective delete/edit functionality within coordinated clients at some point, but it will never ever be absolute. A proper decentralized solution here also requires time stamps… and everybody hates the guy that made NIP-03 possible right now so I don’t see it being solved soon.\n\nThe thing that really matters for deletion anyway is media- which is a reference that you can (and should) maintain control of. Delete the source and voila. But the screenshotting/right-clicking risk remains. \n\nI was in the no-delete absolutist camp until nostr:nprofile1qqsf07zg4hxyccnkdp07fppxmetpfzru3fg6mgzx3nk8r7af8qnjjygpr9mhxue69uhhyetvv9ujuumwdae8gtnnda3kjctv9uq3vamnwvaz7tmjv4kxz7fwd4hhxarj9ec82c30gr0un9 correctly made a point that kids can be dumb and should be able to delete photos. So I agree with his concerns there (and encourage people to self host media if that’s a concern). I remain skeptical of the feasibility of deleting direct event data contained in JSON that is broadcast and bounced around relays beyond anyone’s control. \n\nUltimately decentralized designs require tradeoffs, and this is one issue among many that get amplified… and where the only true solution is *personal responsibility*. It is not solvable in an absolute sense, and all solutions require tradeoffs towards centralization (yes, including client coordination).",
"sig": "e3374fb0cec2fd81718f07c71e548c1ed5ba491cc01f3a60e57cebbeaba1b5ba4eb403bd8b43331fefe8788aa8d08abafc156c872a0408e3b6780e972ba3e26d"
}