Mazin on Nostr: Brainstorming some spam-filter ideas for the aggregator relay behind ...
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?
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?