These should then all link to the instance you're currently on.
Note: because this is implemented in the frontend and does not change the underlying data, other Fediverse clients will not show these the same unless they also implement this themselves.
I would normally test the crap out of these before posting since I really don't know what I'm doing, but I'm on my phone and mostly busy at the moment. Sorry if it doesn't work.
Kbin needs /m/asklemmy@lemmy.ml (domain is important) or a bit simpler is with an @ symbol in front: @asklemmy (note: the domain is here but kbin currently renders it without the domain -- that needs to be changed as it has potential to confuse and mislead)
Downside to the /m/asklemmy@lemmy.ml format is that it doesn't currently auto linkify. Gotta do [/m/asklemmy@lemmy.ml](/m/asklemmy@lemmy.ml) (/m/asklemmy@lemmy.ml)
Hopefully kbin soon fixes the !asklemmy syntax. It's currently broken. Once fixed, that should work for everyone.
I'm the problem. As feared I fudged it up as I was rushing to type it up on my phone. As @CoderKat mentioned, the problem with typing it out as /m instead of using @, is that you have to manually enter the visible text in [ ] and the hyperlink in ( ). I got the hyperlink correct and beefed it on the visible text.
An outstanding problem, though, is linking to specific posts and comments. And, after that, I would argue both kbin and Lemmy should support more nuanced parsing of cross-instance hyperlinks, to reduce friction and UX pain without requiring users to memorise new syntax just to make links work.
Because this URL doesn't have a protocol or a domain, your browser fills those in from the URL of the page you're on when you see it. Since that's on your local Lemmy instance, you'll see a link to !asklemmy on that instance.
Also: When you're looking at a Lemmy comment, if you don't know how the author wrote the markup for it, you can use the "view source" button underneath the "..." menu.
Note: These links will NOT work between Lemmy and Kbin, because Kbin uses /m/ instead of /c/.
Yes it would be very convenient, right now if I’m recommending a community I simply write out the URL manually to make sure it routes via the respective user’s instance first.
I'd like to know too. I was hoping it would be something simple like !community@host.com which would resolve for everyone. Didn't work when I tried it, though I might not have done it correctly.
Add comment