Mazin's avatar
Mazin
_@mazinkhoury.com
npub18kzz...x5sz
Used to play poker now I build things and fly planes. 🍷 relay: wss://nostr.wine 🎥 relay: wss://creatr.nostr.wine Filter and API: https://docs.nostr.wine Translations: https://translate.nostr.wine
Mazin's avatar
Mazin 1 year ago
The problem: when a brand new pubkey starts sending events, it can be difficult to tell immediately whether they are a legitimate user or spam. Our solution: accept all new user notes temporarily in a separate database. As they send events, we continually evaluate their behavior based on several rules (and eventually by a trained model) and approve/block the pubkey. If approved, all of their old events get added to our aggregator relay and the user is immediately discoverable. Their future notes will also go directly to the relay. If blocked, the events are sent to a purged database (for transparency and evaluation) and never reach our relay. Still an early WIP but coming along! It doesn’t solve all the issues but it is a massive improvement on our current rules. View quoted note →
Mazin's avatar
Mazin 1 year ago
I wanted to clarify how filter works because there has been some misinformation. By default we use your WoT (follows+follows) to filter the global feed our subscribers see when they connect to filter.nostr.wine. We do NOT filter replies to notes by WoT so that users outside of your network can be discovered. This can allow in unwanted spam too. This new solution will not change that design but instead improve upon it. Learn more here: View quoted note →
Mazin's avatar
Mazin 1 year ago
Started working on our new spam protection for 🍷 filter.nostr.wine this week. Our repeat message filters and rate limiting helps but still leaks a lot. We expect the new solution to be much more effective AND create less false positives. More details soon!