richard's avatar
richard 1 week ago
non-centralizing defaults come with outbox to begin with. however the user discovered nostr already gives a point of entry into the ecosystem, that could be following someone or connecting to a relay. and for obvious reasons, your third option is objectively the best, users need to have a basic idea of what goes on behind the UI so that they can make conscious choices. i agree with you that it gets really confusing, and thus the reason why this space needs more UX designers which are good at dealing with decentralized tools.

Replies (2)

JOE2o's avatar
JOE2o 1 week ago
I think outbox defaults can only be properly non-centralising if they are not penalising. person A can't be given a pickier set of relays than person B, such that person A just can't do or experience certain things they want to, whereas person B is fine for those same tasks or experiences. just based on luck of the draw. unless you have some uniformity in the base set then even for outbox you need to force a choice.
richard's avatar
richard 1 week ago
they wouldn't even be given any choice at first, outbox should handle it all for them. the client would look for the relay list of the npub they're trying to follow, in a predefined set (including nip65 specialized relays), which should be as large as possible. once the relay list is retrieved, thats a bunch of relays to explore, and in those relays, they might find hundreds of relay hints in events. thats how the magic happens, unless they're exploring nip70 dedicated relays. now if their point of entry is a relay, it's either: - amazing, a regular relay that relays events as it should - terrible, that relay is nip70 only, all the events are exclusive to it, no other relay hint can be found