It’s easy to discover communities on my instance via the dedicated page in the hamburger menu. But let’s say I want to follow a community on another instance, such as !lemmy@lemmy.ml . I might have found its name mentioned in a post or comment. When I click on the provided link, I’m thrown on that instances web page, from which I of course can’t subscribe.
So what I instead have to do is to copy the description of the link and paste it in my instance’s search bar. Which isn’t easy, since it’s a link, so there isn’t even a straightforward way to select the link text without clicking the link. This seems very unintuitive and makes the process of joining a whole bunch of communities tedious. Is there a better way?
I would love for my one account to be able to access literally every federated service. Imo this is the one thing that would tie absolutely everything together. In my mind this kind of seems like the end goal of federation but I’m not really sure. It would make sense though.
this is currently possible in a way, as the instance you’re on, includes your requested remote community. although it doesn’t seem to work that stable at the moment
I haven’t used it yet, but I wrote a small service to combine webfinger from subdomains into a primary domain, and ended up abandoning it. You’d need to handle more than just the webfinger stuff, and be able to route activity pubs as well, and I’m still learning about the protocol enough to see if this is possible. I think the best case is that locally you might be name@someinstance.example.com, but would federate as name@example.com, and webfinger/mentions would work for that, and something at example.com would route activity pubs appropriately to the “real” hosts with name rewriting.