rodbishop on Nostr: I've spent the day thinking about this and now I think relays != communities but that ...
I've spent the day thinking about this and now I think relays != communities but that UX probably still solves this. I may only be slowly catching up here to things you've already thought through.
Where relays are physical servers, and
Where communities are groups of users
I can imagine situations of multiple communities within one relay (e.g. the user is a family member involved in many other small family groupings but does not need dedicated relay for each)
I can imagine situations of multiple relays for one community (e.g. the user is a large multinational company who wants high availability and hosts a relay in each of US-East and Asia geography)
Examples seem to break the 1:1 association and require NIP-28 (or 29?) as well. So then the question is of hierarchy and primacy in the UX.
What were you thinking?
Where relays are physical servers, and
Where communities are groups of users
I can imagine situations of multiple communities within one relay (e.g. the user is a family member involved in many other small family groupings but does not need dedicated relay for each)
I can imagine situations of multiple relays for one community (e.g. the user is a large multinational company who wants high availability and hosts a relay in each of US-East and Asia geography)
Examples seem to break the 1:1 association and require NIP-28 (or 29?) as well. So then the question is of hierarchy and primacy in the UX.
What were you thinking?