Brainstorming some spam-filter ideas for the aggregator relay behind filter.nostr.wine…
First, we want to be transparent about how what we are detecting as spam and what we are going to do with it.
We are thinking we will take any event write that we determine is spam and write it to a separate relay (say spam.nostr.wine). Then, we’ll expose that relay to our users so they can choose to “opt out” of our spam filter.
In addition, this will offer a large catalogue of spam to train models on for other relay operators seeking to battle the present and future spam of nostr.
What do you all think of that?
Mazin
npub18k…mx5sz
2023-02-10 00:59:53
Author Public Key
npub18kzz4lkdtc5n729kvfunxuz287uvu9f64ywhjz43ra482t2y5sks0mx5szPublished at
2023-02-10 00:59:53Event JSON
{
"id": "6f2ec4be527e9c543a643cd27a7c584bdc53e8773797125138d848d84b344f45",
"pubkey": "3d842afecd5e293f28b6627933704a3fb8ce153aa91d790ab11f6a752d44a42d",
"created_at": 1675990793,
"kind": 1,
"tags": [],
"content": "Brainstorming some spam-filter ideas for the aggregator relay behind filter.nostr.wine…\n\nFirst, we want to be transparent about how what we are detecting as spam and what we are going to do with it.\n\nWe are thinking we will take any event write that we determine is spam and write it to a separate relay (say spam.nostr.wine). Then, we’ll expose that relay to our users so they can choose to “opt out” of our spam filter. \n\nIn addition, this will offer a large catalogue of spam to train models on for other relay operators seeking to battle the present and future spam of nostr. \n\nWhat do you all think of that?",
"sig": "cd35ce5beb155f39f1b4eb0623ba359cd03c11e7654b91295b8beebebdf51607e4e9aa522aa61bce7a4bedb8e155e72f1031c651da8b6ee3b3625b3c00ec7353"
}