The idea of community hub relays initally seemed reasonable to me. But the more I think it through, the more I like the other two options. Managing relays for that purpose seems like a pain/nightmare and makes it really hard to follow things. I think if you want to keep topics very separate, use a different identity, and if you only want them separate in an advisory way, use topic tags. That's where I'm at right now anyways.

Reply to this note

Please Login to reply.

Discussion

Mix of personal, public, and paid relays where the clients have smart ways of finding the notes you need by connecting/disconnecting.

I agree and I like this best because it keeps all the smarts in the clients and keeps the relays more agnostic.

So I think being able to browse "relay global" is a nice feature, and being able to direct posts to specific relays is a nice hack, but even while offering those features I don't think they are how to handle different topics. I'll then design the UX to handle topics the other two ways, and leave those other things as manual override features.

Our current approach is your #3 option. Will there be some published taxonomy of topics? Do you plan to just use #tags?

I don't know, but I wouldn't want people limited by the friction of adding a dynamic new topic to an official taxonomy. I suppose #tags makes sense. There may be NIPs with ideas on this. I'd prefer to follow someone else's lead. I like the general concept but I'm not really interested in the details of how, I just want to do it.

My plan is to use tags for now. I saw something about following tags but not sure if that is implemented.

An author's (self-defined) tags could be part of their profile.

It’s an interesting puzzle to solve and one I’ve been thinking through as well. How a user can engage in different contexts and possibly different “personas” with the least amount of friction?