Avatar
Mazin
3d842afecd5e293f28b6627933704a3fb8ce153aa91d790ab11f6a752d44a42d
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

Happy New Year, nostr!

Happy Friday 🍷

I promised nostr:npub180cvv07tjdrrgpa0j7j7tmnyl2yr6yr7l8j4s3evf6u64th6gkwsyjh6w6 a long time ago that we’d put our trending feed in to a relay but we got sidetracked and he beat us to it. Thank you sir - this is cool.

If anyone else wants to use our trending API, it’s free and customizable! Learn more here: https://docs.nostr.wine/api/trending

nostr:note1t6tcus4z3ly720vtph0ufjzgs3t8lehw370uwqjsrm85mnsprfysx90zuq

Hey! Sorry for any confusion. The main nostr.wine relay is just a one time payment, not a subscription so you are all set.

The relays are separate as they serve distinct purposes. Though we could merge them in some ways, we prefer to let users decide which of them they want to use even if that adds a bit of confusion. I know it’s still all a bit unrefined so apologies for that. We are still focused on functionality over polish at this point. Let me know if you have other questions!

nostr:npub1fyvwkve2gxm3h2d8fvwuvsnkell4jtj4zpae8w4w8zhn2g89t96s0tsfuk still responding to me :) but yes it’s still NIP4. We will add 44 as well though, it just doesn’t work as well with standard paid relays so delivery is less reliable.

Bit more cloud surfing today. A few bumps and occasional sprinkle to go with it but overall a very pleasant flight.

https://video.nostr.build/503a55e7aabea3b7f28f2d27a8ce436d9b21466b49da179d0450c3f017fe22f2.mp4

Ok - NOW its fixed :) try one more time

Good point! We should add some documentation. Translate.nostr.wine uses the LibreTranslate API syntax. POST request to /translate with api_key, q, source, target. We also have an endpoint for creating a key/invoice.

See this discussion for details: https://github.com/lumehq/lume/issues/133

Do it! Go for an introductory flight anywhere and you’ll be hooked.

😂 yup. I almost always file and fly IFR to avoid solving this riddle.

I think it did work some originally, when users were physically adding the relay to their list or seeing it in their own list. I can’t imagine it will convert well if it is randomly appearing due to outbox with no previous knowledge of the nostr.wine relay.

Maybe the notify for new users should just drop the invoice completely and just have a link to the website and a brief description instead. DMs feel spammier for new usersbecause the user might not realize they ever connected to the relay and might just think we are soliciting.

Will think about this though. I think we should change the message and probably drop the invoice.

I believe it already works as you described. We first check if the user is authenticated with NIP-42. If so, we check if the event author == the authorized pubkey. If those match and we haven’t previously notified them on this connection, we then send the NOTIFY. It should not get triggered if the authenticated user rebroadcasts an event from a different author.

I’m adding the npub to the message now. Let me know if you notice something not working as described. It’s always possible I introduced some new issues supporting multiuser auth.

Yes, but I haven’t yet seen a way to have your relay lists continue to work with Damus or other single relay list clients. I’m still stuck in the same boat.

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 nostr:npub1qlkwmzmrhzpuak7c2g9akvcrh7wzkd7zc7fpefw9najwpau662nqealf5y nostr:npub1qlkwmzmrhzpuak7c2g9akvcrh7wzkd7zc7fpefw9najwpau662nqealf5y made to illustrate how it all works:

Haha no there is someone spamming nostr relays at the moment just replying to every note from new npubs quoting the original post.