Maybe what we need is a decoupling of user-hosting instances and post-hosting instances. Probably the biggest issue I have with twitter is that I have multiple

Maybe what we need is a decoupling of user-hosting instances and post-hosting instances. Probably the biggest issue I have with twitter is that I have multiple interests/communities I'm involved with. If I post a lot about topic A, get some followers who know me through A, that's great! But then I want to talk about B with the community who knows me through topic B and I feel the need to self-censor as to not spam the topic A followers. I've always felt I would like to be able to tweet only to the TopicA people or only to the TopicB people. But I don't really care that my user data is stored on the same instance as the people in TopicA or TopicB. So maybe a better model for federation would be that you can host your user on an instance, and then also when you post, you are deciding which instance to post on. At the same time, being on a generalist server (mastodon.social) I really couldn't possibly care less about looking at the trending posts on my server as that is just a general slice of mastodon users and I am not in any specific community with them. I want to subscribe to specific niche/thematic mastodon instances for my feed.