Current nostr client ecosystem is not encouraging diverse relay selection which could lead to some relays becoming so large that the service becomes centralized.

Reply to this note

Please Login to reply.

Discussion

Of course that will happen. Same thing happened to the Fediverse. Just wait for the relay blocking

Exactly I don't know what we have waiting for.

Is it intentional, I mean I don't trust anyone at this point

#[0]

Is it intentional? I donโ€™t know of a single client that disallows configuration of a userโ€™s preferred relays. There is no centralized catalog of available relays (paid or unpaid) but there is also nothing stopping anybody from creating that. Itโ€™s been all of 10 weeks since the first clients gained widespread use.

Using alpha/beta versions isnโ€™t for everybody.

#positivity

I understand your point of view but:

They don't necessarily have to disallow it; we've learned that if they put a feature behind 3-4 buttons, daily users are unlikely to use it, much less write out an entire cryptic URL.

I mean you can call me a relay fanatic๐Ÿ˜…, IMO relays are a crucial component of nostr and we should strive to build everything around them. Diverse relay distribution should be by design.

It's hard to say whether the potential centralization of the platform is intentional, but there may be incentives to move in that direction.

Personally, I don't trust anyone and believe that decentralization is key to preserving user privacy and sovereignty, easy diverse selection of relays are essential for that . ๐Ÿฅ‚

#Respectfully ๐Ÿ˜Š

Pretty cynical. ยฏ\_(ใƒ„)_/ยฏ

Advocate for relay diversification and build that recommendation service. Somebody should build a relay discovery and info website that has the attributes of each. #positivity

I'm working on that, planning to make user specific relay Recommendation system, that will also encourage relay diversification by design and integrate that with my current auto-backups service. Let's see ๐Ÿ˜…๐Ÿ•Š๏ธ

Look forward to seeing that. ๐Ÿค™๐Ÿผ