In general tools to understand relays are severely lacking, but I think that’s a byproduct from the fact that all relays are used indistinctively by clients, so all people that might query stuff about a relay solely use speed/uptime metrics, which I think is boring and barely useful.
A tool like the one you mention is downstream from clients changing their behavior.
But hey, you want to skate where the puck is going, not where it is.
The question every mildly curious person asks is “what relays should I use?”
Is a good question (currently) without an answer. It’s highly subjective. And, again, speed/latency/uptime is maybe 2% of the answer.
Agreed, I’ve definitely had that same question.
I definitely wanna hack on this.
I know you can query relay metadata. And people can publish relay lists. I’m wondering if relays can currently state in their metadata some concept of “communities” that the relay is “intended for”
Something optional that just indicates what the relay’s host wants to attract. They wouldn’t boot people based on this, they’d just be raising their hand so that people can find the relay based on interests/identity/locale/etc.
If that already exists then I’ll just build a relay discovery tool that aggregates this info in a way that’s searchable by Nostr users.
If not I may try to add a NIP for it / set a pattern and see if people are interested even before a NIP.
What do you think?
Thread collapsed