Is there a way to make a link to a community of a foreign instance that opens on the instance of the user that clicks on it?
For example, I would like to make a link to !some_community@foo.com that, when a user of bar.com clicks on it, opens https://bar.com/c/some_community@foo.com instead of https://foo.com/c/some_community.
If it’s not possible, don’t you think it would be convenient?
You must log in or # to comment.
That’s what this does:
[Some text here](/c/community@instance.here)Tap the ‘more’ skinny hamburger menu just
abovebelow this message to ‘view source’ of the below:blah blah blah links to asklemmy@lemmy.ml
Actually…better, here is one for an instance that is neither yours or the one you posted into:
That’s perfect! Thank you :)
On my instance ( feddit.it ) I see two broken links:
both return
404: couldnt_find_postDoh! I forgot the /c/, correcting.
sorry, still nope … now they are https://feddit.it/comment/asklemmy@lemmy.ml and still 404
Both of those links send me back to this post on lemmy.ml, through kbin, so if that is the end goal, then it worked.
Should these links work? I’m viewing this thread from Lemmy.ca and both give me a 404 error. When testing with jerboa, the app crashes
Yes, you can do this using a relative URL!
Here’s how I wrote it:
[Here's an example.](/c/asklemmy.ml)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@lemmy.ml 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/.Whoa, that’s so cool!
And, man, that’s a bummer.
Trickery using URL features, like this, will work from clients that act like a web browser. Other clients may have problems with it. There should probably be a standard syntax for “a link to community X hosted on instance Y” that all clients can learn to support.
Just FYI, this link…
…causes the Jerboa app to crash. I think it’s a known issue and hopefully one that gets sorted, but just wanted to warn others.
Wow, good thing to point out.
Relative URLs should work straightforwardly for a UI that runs in a browser, but yeah, I can imagine a custom app doesn’t know what domain or even protocol to associate with them.
Edit 6 Cleaning up post.
You can link the community as a whole, but posts you can’t. Solutions to posts are being discussed on Github
https://github.com/LemmyNet/lemmy-ui/issues/1048
This is how to link communities.
[My text here](/c/asklemmy@lemmy.ml)For example if you want cat@lemmy.world you would type this
[Cat pics on Lemmy.world](/c/cat@lemmy.world)Equals
Or aww@lemmy.ml you would type this.
[Aww on Lemmy.ml](/c/aww@lemmy.ml)Equals
You need to have the /c/ or it won’t work. Don’t put the ! or it won’t work.
I’d like to know too. I was hoping it would be something simple like
!community@host.comwhich would resolve for everyone. Didn’t work when I tried it, though I might not have done it correctly.EDIT: I guess I could try again here !asklemmy@lemmy.ml
That link crashes jerboa lol
Fear my wrath!
oh cool this works cross link test
testing a mention to @liaizon@social.wake.st
Once your Lemmy web frontend upgrades to version 0.18, the following should all auto-link with no extra syntax:
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.
Nice, thanks for the info!
I thought it worked if you just linked /c/asklemmy@lemmy.ml
With the only caveat being that users on kbin will need /m/asklemmy.ml
With the only caveat being that users on kbin will need /m/asklemmy@lemmy.mlI 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@lemmy.ml syntax. It’s currently broken. Once fixed, that should work for everyone.
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.
Weirdly enough on kbin.social for me /m/asklemmy.ml link in the post worked for me
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.
Sweet, I didn’t know you could shorthand it with just @asklemmy and it would auto-linkify. Thanks.
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.
