What issues have you specifically noticed with this?
The issue I've noticed first and foremost is that there is more than one identically named group. Don't tell me that rpg@kbin.social, rpg@lemmy.ml, and rpg@foo.bar are different communities. They're identically named communities. I'd rather have as false positive of a gun user's instance with threads about rocket-propelled grenades, rather than having to go to each group to browse. Don't tell me to just use the "subscribed" view. That doesn't pick up everything in a topic, nor does it help me to find those - again, identically named - communities on other servers. Whenever a new server comes online with an RPG community, they'll be in their own corner. They can participate as foreigners with another group, but that's not theirs. There's no central place for hosting these communities. If there was a server set up just to host groups, and the rest were for users, that would make sense. I immediately grew tired, trying to find all of the communities related to my interests so I can subscribe to all. I did that back in the day, joining forums and setting up a personal homepage with frames. In theory anyone can join any group, but they have to find it first.
If devs and leaders of the ActivityPub community are going to continue pushing the idea that everyone can talk to everyone else, we absolutely need some form of community merging for identically-named communities. For instance, a kbin.social user should be able to subscribe to cooking and see posts from cooking@*.* , not just cooking@kbin.social. That's a UX issue just as much as a technical one.
I wasn't around this far back. Can you elaborate on this a bit? What's the issue with "having mail on three or four non-multiplexed BBSes" ?
Back in those days, BBS mail was less "email" and more "text stored on server". To get all of your mail from multiples, you had to connect to each of the servers in sequence, download your mail, and then read it offline and reply (any good BBS software would remember where itwas from, and offer to call back and send each message). Multiplexing meant that you could have a BBS in the NYC area, it would be able to contact and download from one in, say, PA or wherever, and they could each download threads and messages, aka federated content. The pain has been massively reduced over time, and I'm glad. My next point bounces off yours:
This I remember well. Sounds like you are trying to create an account on each instance and are constantly logging out of one and into the next to keep up on the latest posts and comments. This .. is not really the way to do it.
You're right, except in cases where I want a different psudonymity; my choice. In this case, I can't check for new posts in, continuing with the same example, rpg@*.* without checking the group from each federated server. Posts are neither mirrored nor transcluded. That's the point I'm getting at. I should be able to just open up m/rpg and have it cover all compatible groups.
I disagree with your latter point. kbin.social has hit a reasonable mass of users to have a strong local community and become a platform unto itself, running on kbin software. I'm not interested in a smaller community. I joined Reddit because it was the largest single-site community on the Web. I want the monolithic community, and I accept the costs that incurs, including ads or ad-first design. Right now, the fediverse is just fragments at the foot of the tower of Babel, each speaking a separate tongue, even if some are intelligible to others.
I don't care about the difference between Mastodo, kbin, & Lemmy. They're web software which are trying to replace a monolith, and have seen imited success. I don't care about political leanings. I'm talking about a UX issue. If you want to defed from a site, and receive no more content, then so be it, that's the right of an Admin.