Everything about Lemmy; bugs, gripes, praises, and advocacy.
For discussion about the lemmy.ml instance, go to !meta@lemmy.ml.
Keep in mind, this does not work in Jerboa. It will open a browser tab trying to go to https:///c/some_community@server.tld.
Also, if nobody in your instance has ever subscribed to that community, it results in a 404 error.
EDIT: Nobody should be subscribed to this dead-end sub created and abandoned: Link. Should result in a 404 error for everyone not from sh.itjust.works.
Well shit. So is the only way to get to a community (that nobody from your instance has subscribed to) to go to that instance's community, copy the URL, then go back to your community and paste that URL into the Community Search?
For the time being, yeah. There are multiple github issues open with potential aids to community discoverability and usability, but between lemmy.ml being on fire (recently quenched after moving server... for now), trying to rip WebSockets out of the code before instances hit levels where that'll cripple performance, and dealing with the ~150 other issues per project that have been opened this week, they're... a little preoccupied.
This is a great tip, but it has one caveat. I believe this will return a 404 (not found) if your instance hasn't pulled the community yet. If I create a brand new community on one instance, go to another, and click a link like the one you've proposed, I will see a 404. Then, if I search for that same community on the instance with the 404, it will find it. I believe at that point, the link will work, although it may require me to click on the search result first before the instance is "aware" of the community.
At least, that's the way it worked for me a couple of days ago. 😅
Huh ... funny ... sounds like a bug that could be fixed so that some redirect occurs and you can then subscribe or at least view the community on its original page.