Free relays that allow and store unlimited spam will simply stop working long term. It is not an option to just ignore it and let the clients filter. View quoted note →

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 →

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:

Filter Relay Readme | nostr.wine

Last Updated: June 24, 2025

View quoted note →

Hahahahah this is awesome View quoted note →

If you’re looking for temporarily relief from ReplyGuy now is a great time to try

Filter Relay Readme | nostr.wine

Last Updated: June 24, 2025

- keep your network view/reach without all the noise. A few are still leaking through but our rate limits/repetitive message filters are keeping the majority out of sight. View quoted note →