There is a specific kind of event you can send to request that a server delete a text event, but you have to make sure every server that has your text gets the delete event or it won’t be deleted. It’s also up to the server to actually delete the event from its databases. Hopefully my previous post does help explain why deletion is a pain on nostr. Nostr is optimized for broadcasting and not consensus on a certain state… once something goes out it can be hard to totally revoke
See NIP-09 for more info on deletion: https://github.com/nostr-protocol/nips/blob/master/09.md
armstrys /
npub1eq…4er58
2023-02-13 05:11:00
in reply to nevent1q…6hjh
Author Public Key
npub1eq94yj8maree90pm53gfr76wdc44su3cwcqmly848xfrv6es6usqg4er58Published at
2023-02-13 05:11:00Event JSON
{
"id": "81fa94aa003fc5d4e26383f68e9b8ea5870ed4231c75e625140371e24cd048ad",
"pubkey": "c80b5248fbe8f392bc3ba45091fb4e6e2b5872387601bf90f53992366b30d720",
"created_at": 1676265060,
"kind": 1,
"tags": [
[
"e",
"4d272d26604053de4a23594153578e0fefd54a912dd0844a2bb0cb1a40316d10"
],
[
"e",
"856b729b4ea0ef229f5148190342a249be48ac031599b9a585651570dbb25034"
],
[
"p",
"4ccb4096d76c3a22767d68bd680ddccfde4943f7c6136f5e8f6deb5f2bb871da"
]
],
"content": "There is a specific kind of event you can send to request that a server delete a text event, but you have to make sure every server that has your text gets the delete event or it won’t be deleted. It’s also up to the server to actually delete the event from its databases. Hopefully my previous post does help explain why deletion is a pain on nostr. Nostr is optimized for broadcasting and not consensus on a certain state… once something goes out it can be hard to totally revoke\n\nSee NIP-09 for more info on deletion: https://github.com/nostr-protocol/nips/blob/master/09.md",
"sig": "8e522e5f9b5db1236a2d1184dd3142542eeed0ea6b21d8693aafbeaf28cfee436bc775e493093e3aae93efafba4b2f4c06a4fcb7eae0247527f748225758c3b1"
}