Some other instance-agnostic way of referencing “a given post boosted by [email protected]”
According to Mastodon rules, the canonical source (on lemmy.tf) should be the reasonable place to link, then when pasted into your instance you could see that it got boosted by @[email protected].
According to Lemmy rules, the post “got submitted to [email protected]”, so it could make sense to link to the cached copy on beehaw.org… but that’s just a boosted cached copy, multiple instance users/communities could boost the same canonical post from lemmy.tf.
Although, each boost links back to the original post, so it could make sense to just link to the canonical post, and have each instance check whether any of its communities has boosted it and redirect you there… the only problem is that the canonical post is referred to by its web url, so if you paste it directly in a browser, it will take you to the instance where it was written.
Links on Lemmy are messed up, and both apps and the UI are offering links in a “technically correct”, but “practically weird” way.
In this case: a user on lemmy.tf, created a post, and submitted it to [email protected].
The weirdness starts, when you realize the canonical source for the post, is lemmy.tf, while @[email protected] is just a beehaw.org user who boosts it, beehaw.org caches the post, and marks @[email protected] as a “special user” that makes the post show in a “community” called [email protected], even back on lemmy.tf.
Now, where should an application/UI link to?
According to Mastodon rules, the canonical source (on lemmy.tf) should be the reasonable place to link, then when pasted into your instance you could see that it got boosted by @[email protected].
According to Lemmy rules, the post “got submitted to [email protected]”, so it could make sense to link to the cached copy on beehaw.org… but that’s just a boosted cached copy, multiple instance users/communities could boost the same canonical post from lemmy.tf.
Although, each boost links back to the original post, so it could make sense to just link to the canonical post, and have each instance check whether any of its communities has boosted it and redirect you there… the only problem is that the canonical post is referred to by its web url, so if you paste it directly in a browser, it will take you to the instance where it was written.