I wish Lemmy would make instance agnostic post and comment links. With the current system it’s impossible, as every instance assigns its own number. Instead, links could be in the form https://your instance/comment/number@hostinstance
Done. I hadn’t seen that issue before, not that I really dig into github all that much.
However the issue is somewhat outdated. We do have instance agnostic links for communities and users now, and we have since I joined, which was less than 2 weeks after this issue was posted. We may need a new updated issue that focuses on posts and comments specifically.
It could just be a GUID. The community’s host instance assigns a GUID (which by definition is unique in all GUIDs) and then when sending the post or comment out to federate to other servers it includes the GUID for the other instances to use.
I don’t think there’s a need for a GUID, in fact it would be quite difficult - every instance would have to check with every other instance to ensure that the ID’s are unique. Meanwhile, if we just have the federated host picking a number, then every other host uses that number followed by @hostinstance, we don’t need cross-checking but still have unique ID’s for everything.
For example, https://lemm.ee/comment/123456 would be a different comment to https://lemmy.nz/comment/123456 (as it is currently also), but the first comment could be found on the 2nd instance as https://lemmy.nz/comment/123456@lemm.ee.
I wish Lemmy would make instance agnostic post and comment links. With the current system it’s impossible, as every instance assigns its own number. Instead, links could be in the form
https://your instance/comment/number@hostinstanceWhile I completely agree, a partial solution is to use clients that open fediverse links locally. I use Eternity which does it nicely.
That works for a Lemmy user, but it doesn’t help for sharing on other platforms or for users discovering content elsewhere
The GitHub issue is here, you could put a thumbs up reaction on it, and also subscribe to the issue to get updates about it
https://github.com/LemmyNet/lemmy/issues/2987
Done. I hadn’t seen that issue before, not that I really dig into github all that much.
However the issue is somewhat outdated. We do have instance agnostic links for communities and users now, and we have since I joined, which was less than 2 weeks after this issue was posted. We may need a new updated issue that focuses on posts and comments specifically.
It could just be a GUID. The community’s host instance assigns a GUID (which by definition is unique in all GUIDs) and then when sending the post or comment out to federate to other servers it includes the GUID for the other instances to use.
I’m a massive fan of GUIDs, too, but you’d have no protection from rogue instances reusing GUIDs of existing posts…
I don’t think there’s a need for a GUID, in fact it would be quite difficult - every instance would have to check with every other instance to ensure that the ID’s are unique. Meanwhile, if we just have the federated host picking a number, then every other host uses that number followed by
@hostinstance, we don’t need cross-checking but still have unique ID’s for everything.For example,
https://lemm.ee/comment/123456would be a different comment tohttps://lemmy.nz/comment/123456(as it is currently also), but the first comment could be found on the 2nd instance ashttps://lemmy.nz/comment/123456@lemm.ee.