This is actually a really great idea. A NIP that has a kind which is a list of pubkeys, that any user can publish, and anyone can pull any of this kind of note from anyone and incorporate it into their spam filter. So you could say that you trust my spam filter list, or someone else's, or 5 people's, and then your client will just use it (giving you the option to not block certain keys of course) and your client might even optionally update yours so that others can use yours.
I can think of a problem with it, which is auto updating these lists will make them trend towards uniformity across the network, there's a lot of redundancy as well.
Another idea is to let relays put it in their relay information note, it updates it every time the relay blacklists a spam pub key, but the issue with that is that relays will then over time trend towards censoring people. A relay adds me to it's list because it doesn't like some opinion of mine, too many people use it and now I become undiscoverable on the network. This is dangerous, you see a similar thing happening across the fediverse.
The user blocklist idea will also enable trusted users to censor a little, but usually this will be ideologues who's followers choose to use their list because they're also ideologues, it's much more resistant to network wide censorship and network fragmentation. The danger here is that relays begin doing the blocking on behalf of users, which would probably happen to some degree anyway.
mister_monster
npub1m5…jgjl3
2024-09-09 23:40:38
in reply to nevent1q…n05n
Author Public Key
npub1m5s9w4t03znyetxswhgq0ud7fq8ef8y3l4kscn2e8wkvmv42hh3qujgjl3Published at
2024-09-09 23:40:38Event JSON
{
"id": "a660aed671c0b494d1c7dba901b85ebf99bdaf4ec54f381dc091eba3fb7e6c59",
"pubkey": "dd2057556f88a64cacd075d007f1be480f949c91fd6d0c4d593baccdb2aabde2",
"created_at": 1725925238,
"kind": 1,
"tags": [
[
"e",
"b8a098bb739382837226ea4ef88e4d2d9cf8a491e2071e2bebceb0d63fb14558",
"",
"root"
],
[
"p",
"5d1d83de3ee5edde157071d5091a6d03ead8cce1d46bc585a9642abdd0db5aa0"
],
[
"monero",
"85d6A16RJfyAdmwCx765vnXNcFGYudSXvb1uYWtLfvrDfc3vkvm6LPRW65T1TY51UucWgfuu9pWpUj6SPkUWX7LrMD7B36B",
"1.0"
]
],
"content": "This is actually a really great idea. A NIP that has a kind which is a list of pubkeys, that any user can publish, and anyone can pull any of this kind of note from anyone and incorporate it into their spam filter. So you could say that you trust my spam filter list, or someone else's, or 5 people's, and then your client will just use it (giving you the option to not block certain keys of course) and your client might even optionally update yours so that others can use yours.\n\nI can think of a problem with it, which is auto updating these lists will make them trend towards uniformity across the network, there's a lot of redundancy as well.\n\nAnother idea is to let relays put it in their relay information note, it updates it every time the relay blacklists a spam pub key, but the issue with that is that relays will then over time trend towards censoring people. A relay adds me to it's list because it doesn't like some opinion of mine, too many people use it and now I become undiscoverable on the network. This is dangerous, you see a similar thing happening across the fediverse.\n\nThe user blocklist idea will also enable trusted users to censor a little, but usually this will be ideologues who's followers choose to use their list because they're also ideologues, it's much more resistant to network wide censorship and network fragmentation. The danger here is that relays begin doing the blocking on behalf of users, which would probably happen to some degree anyway.",
"sig": "aaf5a2b3ebf55205e0a2401d092ac85ac76014ac9e8c61b09cefebc43e7153e3495b4686e122ae7f85486b0d9cba864a20c7f745933e7f88230af89f47062012"
}