Why YSK: right now, Lemmy’s autocomplete for the !community syntax isn’t working correctly.
It will appear to work, like so:
But the link produced will redirect you away from your home instance and leave you unable to vote/subscribe…
To fix this issue, you’ll need to manually edit the autocompleted link like so:
BAD LINK: [!youshouldknow@lemmy.world](https://lemmy.world/c/youshouldknow)
⬇️⬇️⬇️ Remove the domain (i.e.: https://lemmy.world) & append the @ identifier (i.e.: @lemmy.world)
GOOD LINK: [!youshouldknow@lemmy.world](/c/youshouldknow@lemmy.world)
Removing the domain like this transforms it into a local link which prevents the instance redirection. Doing this will make it easier for newcomers to join your community and participate in discussions!
Those interested can monitor Github issues #369 & #1048 for when this UI bug is fixed!
YSK that a URL without a protocol or domain is a relative URL.
It’s “relative” to the page that it’s displayed on.
Your browser fills in the protocol and domain from the URL of the page you’re on when you click on it. That’s how it stays local to the instance that you’re viewing it on.
Thanks for providing the Github links!
Of course! Perhaps one of the greatest public goods to come out of FOSS is the public bug tracker. Not a “known issue” list, not a “ticket system”, but rather a place where you can see work happening on your issue in realtime.
If you are using the mlem app to browse, the good link will crash your app so don’t click it for now. They are aware and it is raised as an issue in their github.
Same for Jeroba.
Hmm this still doesn’t quite work for those of us visiting from kbin because from kbin we access this community as: https://kbin.social/m/youshouldknow@lemmy.world/ so even the /c/ doesn’t match up.
We probably will need some special markup that each instance converts to their own local community / magazine format.
Confusing bug. I thought I was doing something wrong.
Wow, this is really useful, thank you!
Hi - just FYI, the Good link makes the app Jerboa crash (for me at least). Probably something needing changed in the app, but wanted to share anyway.
This issue should be fixed now in the edited version of my post. I made a rather silly mistake in the original version that @justin@sh.itjust.works helped me solve.Still crashing, sadly. I’m sure it’s Jerboa though. It’ll get sorted at some point, thanks anyway :-)
Bummer… looks like this is indeed a Jerboa issue (Github #556). Hopefully that gets resolved soon so we can have links that reliably work on every frontend.
Yeah that’d be great.
Thanks for checking GitHub, I can’t really find my way around on there. Good that it’s a known issue at least.
Cool
Is there any way to link to posts like this?
Found that crossposting does not provide a instance neutral link.Unfortunately, no. For posts/comments, there’s currently no way to create cross-instance permalinks. You can follow progress on fixing that issue via Github #2987.
There is an issue with this. If nobody on the instance of the user that clicks the link is subscribed to that community, this will result in a 404 error. If at least one person on the instance is subscribed, it’ll work. In a browser. Not in Jerboa.
As a temporary bandaid, it looks like every instance needs a sacrificial user/volunteer to subscribe to every community they can find.
Yes, unfortunately. This is one of those situations where it’s technically less user friendly to browse on a smaller instance (since large instances are more likely to already be subscribed to a given random community). Of course, this issue affects anyone who tries to visit a given community via their home instance, not just people using this particular link style.
Right now this problem is being tracked on the backend Github as #2951. Hopefully they manage to sand off this particular rough edge ASAP.
