Filter.nostr.wine was just down for ~100 minutes. The issue has been resolved and everything is back up. Apologies for the inconvenience.

Happy Monday! We have just completed normal maintenance on all nostr.wine regional relays and filter.nostr.wine 🍷

I’m sad

GitHub

NIP 67: Nostr Wallet Auth by benthecarman · Pull Request #851 · nostr-protocol/nips

There are a lot of technical and UX problems with NWC connection strings, this defines a better way to establish a wallet connection. Naming and wo...

never got merged. We built a nostr.wine NWC service that relied on this improved onboarding flow in December of 2023. At the time Mutiny was leading the effort. I don’t understand why it wasn’t merged then when we had 4 working implementations. It is the only reasonable NWC on-boarding flow I’ve seen for services (like nostr.wine).

Happy New Years #nostr Really proud of the reliability across all of our nostr.wine products this year. Let’s run it back next year 🥂

One of our hosting providers is having a massive west coast outage. We are trying to get more information from them at this time. They are total clowns.

Rolling restarts across a few services in progress for updates!

Introducing Purgatory - our new spam evaluation engine for filter.nostr.wine. The newest addition to our nostr event data pipeline. Here is a flowchart that @Katie @Katie made to illustrate how it all works:

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 →