If you type it like this you’ll get an instance agnostic link (at least on instances v0.18 and above, not necessarily in apps): /u/ChamrsDeluxe@lemmy.world.
You can also select from a dropdown box on the website to send a mention, however this link goes to their instance rather than your own: @ChamrsDeluxe@lemmy.world. The code for this is [@ChamrsDeluxe@lemmy.world](https://lemmy.world/u/ChamrsDeluxe), you can type this manually and replace any link text in between the square brackets, so generally [link text](https://userinstance/u/user).
The old pre-0.17 instance agnostic links were [link text](/c/community@instance) or [link text](/u/user@instance), but the new versions will automatically generate without link code:
/c/community@instance
!community@instance
/u/user@instance (does not send a mention)
Also, kbin doesn’t federate properly. You might not even see this comment over there…
The first one will generate a link automatically with no code (on lemmy v0.18 and above, not necessarily in apps - it doesn’t seem to work in Jerboa currently). This link is instance agnostic, meaning the viewer sees a link in their own instance, rather than the example.com instance. This means you can send them a DM, or open their comments and reply to them.
The second one isn’t enough on its own, it needs to be in the form [link text](https://example.com/u/user). However, if you start typing @user@example.com on the website, a pop up box will allow you to select the user and generate the link code for you - it will give you [@user@example.com](https://example.com/u/user). This version is not agnostic, it takes you to the user’s instance, however it does send a mention to the user’s inbox.
Hopefully in a future update they will combine these two, so that an agnostic link will also send a mention, and so the mention link will auto-generate and be agnostic. Right now, one is for linking to a profile you want to interact with, the other is for calling that person into the thread with a mention.
Edit: Just for a little more fun variation, it looks like Jerboa handles the @user@instance link as if it were instance agnostic. On the website it opens the user’s instance.
That’s all well and good, but I was telling them to include the instance for their mastodon handle, which they’ve gone back and edited to include it now.
Yes, but this doesn’t have anything to do with mastodon which was my point. You need to include the instance in your mastodon handle. Which I see you’ve gone back and edited now, but that was my whole point. I didn’t need a lesson on something I literally just demonstrated I know about.
If you type it like this you’ll get an instance agnostic link (at least on instances v0.18 and above, not necessarily in apps): /u/ChamrsDeluxe@lemmy.world.
You can also select from a dropdown box on the website to send a mention, however this link goes to their instance rather than your own: @ChamrsDeluxe@lemmy.world. The code for this is
[@ChamrsDeluxe@lemmy.world](https://lemmy.world/u/ChamrsDeluxe), you can type this manually and replace any link text in between the square brackets, so generally[link text](https://userinstance/u/user).The old pre-0.17 instance agnostic links were
[link text](/c/community@instance)or[link text](/u/user@instance), but the new versions will automatically generate without link code:/c/community@instance!community@instance/u/user@instance(does not send a mention)Also, kbin doesn’t federate properly. You might not even see this comment over there…
If I’m reading this right there are two ways to indicate a user including its instance:
/u/username@example.com@username@example.comWhich one is the recommended one?
The first one will generate a link automatically with no code (on lemmy v0.18 and above, not necessarily in apps - it doesn’t seem to work in Jerboa currently). This link is instance agnostic, meaning the viewer sees a link in their own instance, rather than the
example.cominstance. This means you can send them a DM, or open their comments and reply to them.The second one isn’t enough on its own, it needs to be in the form
[link text](https://example.com/u/user). However, if you start typing@user@example.comon the website, a pop up box will allow you to select the user and generate the link code for you - it will give you[@user@example.com](https://example.com/u/user). This version is not agnostic, it takes you to the user’s instance, however it does send a mention to the user’s inbox.Hopefully in a future update they will combine these two, so that an agnostic link will also send a mention, and so the mention link will auto-generate and be agnostic. Right now, one is for linking to a profile you want to interact with, the other is for calling that person into the thread with a mention.
Edit: Just for a little more fun variation, it looks like Jerboa handles the
@user@instancelink as if it were instance agnostic. On the website it opens the user’s instance.That’s all well and good, but I was telling them to include the instance for their mastodon handle, which they’ve gone back and edited to include it now.
Yes, but this doesn’t have anything to do with mastodon which was my point. You need to include the instance in your mastodon handle. Which I see you’ve gone back and edited now, but that was my whole point. I didn’t need a lesson on something I literally just demonstrated I know about.