nostr-protocol
Kind mute sets
Fix #1156
JSON Example
{
"kind": 30007,
"content": "<encrypted tags>",
"tags": [
["d", "<kind>"],
["p", "<pubkey 1>"],
["p", "<pubkey 2>"]
]
}
+1.
I feel like it is more generic mute list than the sets. How about using the k tag after all?
Adding both k tag and p tag to kind 10000 makes it complex and will break existing clients.
Expanding k tag to be able to contain pubkey would cause conflicts between NIPs in the future. (It may be okay if the k tag has a different meaning for each NIP, but I don't like it.)
It was not communicated properly. What I want to say is this:
{
"kind": 30007,
"content": "<encrypted tags>",
"tags": [
["d", "<identifier>"],
["k", "<kind>"],
["p", "<pubkey 1>"],
["p", "<pubkey 2>"]
]
}
How about using the k tag like this? Without the k tag, it just looks like a generic mute list, not the sets.
I see.
If <identifier> is free input, multiple events will be created for a kind.
It makes clients complex to use kind mute sets.
If <identifier> is same as <kind>, please see #1156 discussion and edit history.