nip09: filtered deletation. #1509
Open
+26
−0
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| "kind": 5, | ||
| "pubkey": <32-bytes hex-encoded public key of the event creator>, | ||
| "tags": [ | ||
| ["f", "{\"kinds\":[1,7]}"] |
There was a problem hiding this comment.
Is the author pubkey implicit here?
There was a problem hiding this comment.
the author field of course can only be set to event public key. maybe in groups and moderated communities, more public keys would be helpful...
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
using the current model, it's hard to remove events with complex conditions. client needs to turn user action into a huge event and send it to relay and then relay needs to do an iteration and remove them.
using
ftag, we can make it much easier. filter already exists on relay and clients and they can parse, construct, and interpret them. for relys it's easy to turn this filter to a remove/delete query on different query languages compared with the current model.then clients can support delete account, removing all chat messages, or even getting the filter as input from the user.
of course, the
"authors"filed MUST be considered only if the matching events are kind of in the control of the"pubkey"field owner in the case of moderated communities and similar stuff.