Replying to Avatar PABLOF7z

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.
Avatar
rabble 2y ago

I wonder if there is some intersection between the new communities stuff and relay selection. Like a community could have a set of preferred relays just like a user profile does.

We’ve got some relay controls in nos.social around being able to post to specific relays and browse only posts on a specific relay, but it’s just a start. A set of relays is a much safer setup than single ones. I want the topical relay idea to be more of a thing.

Reply to this note

Please Login to reply.

Discussion

Avatar
PABLOF7z 2y ago

me too.

I think most clients are still being designed with a client-server architecture model in mind and the power of relays are not being leveraged.

I also completely agree that sets of relays are a better UX unit than individual relays.

The new UX of Highlighter will put relays at the top of the UX hierarchy:

Avatar
PABLOF7z 2y ago

Avatar
PABLOF7z 2y ago

I will be doing a lot of work from nostr:npub1pages5yhmncmmfxuza9f9fx68fju0nxnewtlffzrapsufax5mv0sznuw9d to create the data for this relay sets so that you could query

`{ "kinds": [11002], "#t": ["philosophy"] }`

and get a list of relays that tend to have more of philosophy tags than other relays, excluding relays which would always be returned because we're still trending towards centralizing around a handful of relays