Agreed! The magic of the protocol

So there’s an explicit NIP about it https://github.com/nostr-protocol/nips/pull/345/files?short_path=319c9bc#diff-319c9bcebb9aa1a6bb2187a77604e2cb409af365a9f504e6d38f01627b6810d4

There’s also attempts to do it without needing a NIP like hornetstorage.com

But it’s been a question ever since people built ways to upload images and embed them in notes (like Nostr.build)

Been thinking about how to do this. Might just build it because then it’s more like a newsletter. But you don’t need email.

Cool! How are you filtering out spam?

🙏

Alright I made two changes as suggested:

1. It only shows you the relays in your latest kind 10002 event not an aggregation of all the recent ones.

2. It’ll save the marker (read/write/advertise etc) and if you republish your relay list it’ll preserve that. (defaults to “write” for adding new relays via the rest of the site though)

What was your comment about the app not finding you NIP05?

Added a bit more validation but I’ll keep looking into making it more resilient

You know that’s a good point. I’ll make it so that it only takes the latest. And yeah I think it strips that extra detail so let me add a way to retain that so nothing gets lost. That’s definitely important.

Thanks I’ll take a look and try to prevent that error. Mind sending me the execs values that got you the error?

Feedback and feature requests welcome!

New features for https://relay.guide

You'll be able to select preferred relays across Relay.Guide and then publish your preferred relays as a NIP 65 Relay List authorized via a nostr even tsigning browser extension.

Next up is supporting both NIP 65 and NIP 02 versions of users' preferred relay lists so that it works on as many clients as possible!

I agree, I don’t want that culture either. Just looking at the nip for the kind 3 event it doesn’t look like it was intended to be where people published their preferred relays.

I’d be happy to standardise on kind 3 if we updated the NIP for that expressed purpose. But in talking to some folks they thought NIP 65 would be the way to solve the preferred relay problem going forward.

I just wanna go with what people prefer I am agnostic. Just pulling for one standard and I haven’t heard consensus yet.

I’d love to understand how you’d prefer users set and publish their preferred relays. The kind 3 contact list seems a little brittle to me

Are you talking about the read and write optional tags on the specified relays?

I’ve been looking at how clients manage user relay preferences and I see a lot of “common public relay” constants being used as a fall back if they can’t find a kind 3 contact list with relays on it.

I think clients unifying on publishing and using kind 10002 relay lists for users would help. But as you already know that requires everyone being more strict and folks tend to not do that.

By tomorrow I’m going to make it so that on https://relay.guide you can create, publish, and manage relay lists for all the clients that respect it. Hopefully more clients move towards using it.

Thanks! Big fan of your work 😊🫂

Agreed thanks for taking a read ❤️

I did some thinking about what it would take to hyper bitcoinize and one of thr first things that came to mind was addressing obsession with the price 😂

https://gregwhite.blog/paths-to-hyper-bitcoinization/

Thanks 😊 let me know if there’s anything you wish you could see

Totally! Then I think there are some scripts out there that you can run but it’s not a crowded service provider space yet 😅