When I type @[email protected], there is no hyperlink created. Does that mean I did not properly mention them? I also tried u/[email protected].
The docs do not cover this.
Using Liftoff, I get hyperlinks for both of those, though they don’t lead anywhere.
[email protected]
Works for meI’m skeptical. That mention of me in your msg is an URL with the mailto: scheme, which has the effect of launching an email client that tries to treat a Lemmy address as an email address.
that shouldnt happen lmao
Works (mostly) on lemmy desktop, neither Jerboa nor Voyager support automatic user linking.
@[email protected]…yep, works on desktop.
It used to work but I’ve found it patchy , however, starting to @ your user name in the web interface worked: @[email protected] so…
I’m using the stock web client of slrpnk.net (whatever version that is), and when I type @[email protected] … oh, wow, that worked. Strange. In the cases that failed me, I copy-pasted the user’s address. So apparently it must be typed out manually to trigger auto-complete. I see that the client just makes it a markdown hyperlink to your profile. That’s useful, but what’s more important is that the user get a notification. When i copy-paste the address (e.g. @[email protected]) there’s nothing to signal to me that the user was recognized and that they will actually be populated in the “mentions” field of the JSON record.
Yea, I’ve had it not work before but it seems to kicked in now. Just checking and it may just be that some users don’t trigger it. I believe you can construct a working mention link manually using the link button too but autocomplete is simpler when it works.
When you say “some users don’t trigger it”, that’s probably a feature. It’s important to know if a user is federated with the server the msg is posted to in order for them to get the notification.
Indeed we can always write a markup hyperlink and put the users address in it, but that’s not the point. That would not ensure that they get the notification. It’s the automatic generation of that link that tells us whether the user was recognized.
I believe we 1st have a documentation bug since the docs do not cover this. And functionality-wise, we should be able to see a list of who is mentioned for the purpose of notifications.
When you say “some users don’t trigger it”, that’s probably a feature. It’s important to know if a user is federated with the server the msg is posted to in order for them to get the notification.
The one I had trouble with was the admin of the instance.
I’m calling this a #LemmyBug. When an address is copy-pasted into a msg, you have no indication of whether the other account was properly recognized and that they will get a notification. When I view source, it just shows the body of the msg not the JSON record.
That definitely sounds like a bug I would check if it exists on their GitHub and report it if it doesn’t.
I don’t do MS #Github (#deleteGithub). Or MS (anything) for that matter. I am 100% #GAFAM and #Cloudflare-free. I will generally report issues to #Debian’s bug tracker but that’s only an option for pkgs that are in Debian’s official repos. #Lemmy is not – which in itself is a concern.
Debian requires packages to reach a certain quality standard. When a pkg becomes official Debian it suggests the package has enough popularity & quality to be taken seriously. Debian is quite popular¹ so Lemmy should try to put itself on the map. Until then I’ll have to file my bugs under the LemmyBug hashtag.
1: https://has-no.solutions/objects/5891cf49-163d-491e-900a-6b5af92fa9a0
deleted by creator
deleted by creator
