this post was submitted on 01 Jun 2023
302 points (99.0% liked)
Lemmy.ca's Main Community
2758 readers
4 users here now
Welcome to lemmy.ca's c/main!
Since everyone on lemmy.ca gets subscribed here, this is the place to chat about the goings on at lemmy.ca, support-type items, suggestions, etc.
Announcements can be found at https://lemmy.ca/c/meta
For support related to this instance, use https://lemmy.ca/c/lemmy_ca_support
founded 4 years ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
That feature is actually partially implemented, but the client you're using (web browser or mobile app) fights you a bit in interesting ways:
On web, when typing in a Lemmy community like [email protected] the client will try to help you complete it, but it completes to a remote instance link: [email protected]
If you change the markdown for that link to point relatively, then it follows standard URL conventions and works in your current instance: [email protected] (You can select
view sourceon this comment to see how I modified this link) However, this same link will probably not work on mobile clients, as the operating system determines how to handle URLs.Thanks. I'm not sure that's exactly what I'm imagining, because this still involves hard-coding an instance to the link. People from many different instances might be viewing the link, so I'd imagine a flow like: when you mouse-hover a link to a community, a little popup appears which provides a custom link based on your home instance. So whether [email protected] is a link to the lemmy.ml or lemmy.ca domain wouldn't matter, ideally you'd always get the option of viewing the community from your home instance at a single click. Hope that makes sense, today is my first day after all.
I totally agree. That's the behaviour I also expected from the default "!"-prefaced community links. Unfortunately it currently doesn't work that way, but if I have time later this week I may take another look into the source code to see if an easy fix can be done.
Found this recent GitHub issue discussing this.