Lemmy

12506 readers

11 users here now

Everything about Lemmy; bugs, gripes, praises, and advocacy.

For discussion about the lemmy.ml instance, go to !meta@lemmy.ml.

founded 4 years ago

MODERATORS

nutomic@lemmy.ml

148

Following remote communities is hard. (beehaw.org)

submitted 1 year ago by Raincloud@beehaw.org to c/lemmy@lemmy.ml

75 comments fedilink hide all child comments

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?

you are viewing a single comment's thread
view the rest of the comments

[–] kosmo@satl.ink 2 points 1 year ago

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.