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
Hi! They are completely unique and serve different purposes.
nostr.wine is a “typical” paid relay. You have to pay a one time 18,888 sats admission fee to be able to write to the relay but anyone can read from it.
filter.nostr.wine is a paid subscription service (5000-10000 sats per month depending on duration of purchase). Filter is a public/free relay aggregator with several additional features. Here are some of the highlights:
- Aggregates notes from the largest 20+ free relays
- Broadcasts your notes out to 10+ free relays
- Also broadcasts to your first 4 "write" relays and the first 4 "read" relays from the first 5 tagged users (NIP-65 list)
- Offers a (configurable) follows+follows filter for “global” view so you can explore notes outside of your immediate follows but still within your network
- Full text search across all aggregated events
You can learn more about the full functionality of Filter here:
View quoted note →
Filter Relay Readme | nostr.wine
Last Updated: June 24, 2025
Don’t give spammers attention or praise. They aren’t trying to make nostr better. It’s always the same narrative with these children. They only seek your attention.
Relay operators who don’t want to lose Sleepy use @RelayGuardian View quoted note →
Doing some initial testing of our new event ingress pipeline tonight! It’s insanely cool and already yielding great insights.
Much easier to separate legitimate users from spam when you’re looking at 10 of their events instead of 1. View quoted note →
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:
View quoted note →
Filter Relay Readme | nostr.wine
Last Updated: June 24, 2025
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!
If you’re looking for temporarily relief from ReplyGuy now is a great time to try
- 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 →
Filter Relay Readme | nostr.wine
Last Updated: June 24, 2025
