I am not sure what is correct to put in [kbin-core/issues](https://codeberg.org/Kbin/kbin-core/issues) without cluttering it up with somewhat speculative requests. I have no idea how to implement this or whether it is possible. So I will post here?...
We already have the IDs you mention in the URLs though, right? In the post I used as the example, the author’s home instance URL for the item is https://lebowski.social/post/12337
Yes, the needed information is already present in those URLs, but as URLs, they instruct the browser to leave the current site and visit the origin instance, which is not what we want. To get the desired behavior, we would want:
Those two fields combined in a distinct format (not easily confused with a URL).
An obvious way for readers to get the global ID for any message they see (perhaps with the community/magazine name embedded, to make finding the source forum easy for humans who see it)
Apps (including the web interface) displaying each global ID as a link to the nearest copy of its message (local copy when available, origin instance copy as a fallback)
An easy way to manually navigate to any message by entering its global ID
a way that can be easily learned to transform the URL by copy/paste by hand
Yes, the needed information is already present in those URLs, but as URLs, they instruct the browser to leave the current site and visit the origin instance, which is not what we want. To get the desired behavior, we would want:
Yep. That’s the kind of ID we want. :)