Took me a couple weeks to get everything migrated but finally I’m free of bare metal k8s hell. Oddly I was even able to reduce costs by having less nodes running 24/7. Now back to something a bit more entertaining… View quoted note →

Randomly assigning relays to new users without any reliability or performance metrics will not end well. Primal has the benefit of their caching service to mask the problem but those users will suffer on other apps that don’t support it.

This has been stable for a few days now! Filter now broadcasts to your own write relays (in addition to our public relay list) and helps you reach any tagged user even if they only read from their own personal relay. View quoted note →

Ok I’ve got some real work to do today. Enjoy your Wednesday!

This framing of outbox vs proxy relays on separate sides is disingenuous at best. My main criticism of outbox model has always been that it will REQUIRE intermediaries to be usable on most clients if nostr users spread out across more relays. If all I wanted was for the “smart proxy relays to win” I wouldn’t bother having these conversations. The fact that any criticism of outbox model is received as “you must have another agenda” or “you must be too lazy to update your client” doesn’t help convince anyone that it’s a good idea. View quoted note →

If you haven’t tried 🍷 filter.nostr.wine yet - give it a try! Works with any nostr client. Learn more here:

Filter Relay Readme | nostr.wine

Last Updated: June 24, 2025

View quoted note →

Here’s how our new NIP-65 broadcast service for 🍷 filter.nostr.wine works: 1. A background service constantly monitors kind 10002 events across (most) known relays and updates the results in redis. 2. When one of our paid users sends an event to filter, their first 4 “write” relays are pulled from redis and sent to our broadcaster. 3. If users are tagged in the event, the first 4 “read” relays from the first 5 tagged pubkeys are pulled from redis and sent to our broadcaster. 4. The broadcaster service batches requests and then connects to the necessary relays and sends the events. 5. In addition, events are also broadcasted to our list of public relays visible on

Filter Relay Readme | nostr.wine

Last Updated: June 24, 2025

This is now live with the following limitations: - We will only broadcast to the first 4 write relays in your kind 10002 event. - We will only broadcast to the first 4 read relays of the first 5 tagged users in an event. View quoted note →

🍷 nostr.wine and filter.nostr.wine now support up to 4000 event tags and larger websocket message size limits to help with your follow list struggles! Our NIP-11 json has been updated to reflect this change.

A few limitations to keep our connection count reasonable: - We will only broadcast to the first 4 write relays in your kind 10002 event. - We will only broadcast to the first 4 read relays of the first 5 tagged users in an event. View quoted note →

Just tested this and it works! Should be able to get it deployed very soon. View quoted note →

Close to finishing up NIP-65 support for the broadcasting side of filter.nostr.wine 🚀 In addition to our usual list of public relays, we will soon also broadcast your notes to your “write” relays and any tagged user’s “read” relays.

I’ve got a new 🍷 nostr.wine landing page to finish and release today. It’s only the first phase of our new site migration since we plan on integrating all of our relays and services in one place.