Open chmac opened 1 month ago
Research on nos.lol
says they process deletions by deleting the event, but only tell clients about the deletion if the client is listening with a query that would include the kind 5
deletion event. So a subscription for the pubkey of the author would work, but a subscription for author + kind 30397
will not. The deletions will never be seen by the client.
This needs some design. We need to actively subscribe to kind 5
events, which means we need to think about how to do that. I'll put this on pause for now as it's not critical for the next few weeks.
NIP9 defines deletion events.
kind 5
<kind>:<pubkey>:<d-identifier>
Events should also have a
k
tag for each kind being deleted. I guess for filtering purposes.