🍷 filter.nostr.wine now requires NIP-42 AUTH 🎉 It’s time to drop the /npub path from your relay list and connect directly to wss://filter.nostr.wine instead! Broadcast=true is now the default and no longer needed. You may still set ?broadcast=false if you do not wish to use our public relay/NIP-65 broadcaster.

Add Nostromo to the list of NIP-42 supporting clients for all platforms! View quoted note →

Does your kind 1 client support NIP-42? If so - tell me about it and help me add to this list. Android: Amethyst iOS: Damus, Nostur Web: Coracle, Iris, Snort

I think we’ve waited long enough on this one. I’ll be rolling this out shortly. Please note this means 🍷 filter.nostr.wine will no longer work on Primal or any other client that does not support NIP-42. View quoted note →

Back up 🚀 View quoted note →

Quick filter.nostr.wine restart in progress…

Lots of good nuance in here. It’s more complicated than it sounds. View quoted note →

🍷 nostr.wine and filter.nostr.wine both support NIP-50 We also provide a free Kibana frontend to explore our data:

Elastic

And a free REST API:

Search | nostr.wine

Documentation for nostr event search

View quoted note →

ICYMI - the 🍷 filter.nostr.wine broadcaster now supports NIP-65 🎉 View quoted note →

Am I the only one that doesn’t think nostr will ever replace YouTube? Are we supposed to pretend that the expense/technical challenge of hosting, processing, and streaming videos is going to be handled reliably by my uncle Jim and yours? We aren’t even anywhere close to replacing existing text-only use cases at scale and I can’t help but think we’d be further along if we didn’t spend so much time with our heads in the clouds. Good morning!

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 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 →

🍷 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.