The tragedy here is that you had to make a screenshot to then upload to Mastodon, only later to come here and have to point out where the original post is. It would be great if you could have made the post on Mastodon simply by linking to the original post and then the format would have looked just as good as the screenshot, and then both sides of the Fediverse could converse. Or, the opposite could happen.
I’ve talked about this kind of thing before https://lemm.ee/post/4955936 and some are confident this is how things will eventually end up, so I hope they’re right.
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.
Here’s a link to @maxprime@lemmy.ml’s comment: https://lemmy.ml/comment/6075385
The tragedy here is that you had to make a screenshot to then upload to Mastodon, only later to come here and have to point out where the original post is. It would be great if you could have made the post on Mastodon simply by linking to the original post and then the format would have looked just as good as the screenshot, and then both sides of the Fediverse could converse. Or, the opposite could happen.
I’ve talked about this kind of thing before https://lemm.ee/post/4955936 and some are confident this is how things will eventually end up, so I hope they’re right.
Friendica does this already! This is how I see your comment:
Well that didn’t quite work, did it? Here’s the screenshot:
Ah, I see. Lemmy handles comment images differently from the rest of the Fediverse, even including kbin. Annoying.
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@hostinstanceThe 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.
While 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
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.