Who’s working on the third one? https://image.nostr.build/ac9fcfa76f2f6e5414fad0a2c64488145024e7e1e5e7eb85a63426f1a84c9ca5.jpg
Easy to use relay management and exploration is an area that can see vast improvements.
Check out relay.tools @cloud fodder
Neat tool, but it doesn't simplify anything about relays for the non-technical user.
When’s the last time you checked? It’s 1 click to deploy, pretty simple! Also each relay has a relay explorer
Aha! I see the confusion. I don't mean creating relays, I meant user management of relays client-side. Deployment of new relays has definitely made progress, though, and that tool looks great.
Oh yeah… I thought you meant relay admin as well. But as long as we’re talking about clients, I would love to have a client that could read/write from public and private relays within that same interface. I was going to say it doesn’t even need to store private relays in the kind 3 relay-url field(s) - then just discovered nip-65 is attempting to supplant this with replaceable events https://github.com/nostr-protocol/nips/blob/master/65.md
Relay management needs more love. Relays, while the dumb data stores of Nostr, are the lifeblood that allows our content to be decentralized and censorship resistant. Imagine a time when someone, a group of people, or even an entire country is banned from accessing certain relays. These users need better tools for discovery and migration. nostr:nevent1qqs0l6g0syl0m3lpy2jgw9le30m6xyk8r69nf32x3qclggv0c3323hspzemhxue69uhkummnw3ex2mrfw3jhxtn0wfnj7q3q8jgxqshg38cgzcv43zvqhnc7hjn223psy2kkmkpqt2azd9thyy4sxpqqqqqqz2t0rz7