This points out to me that I don’t think I understand how Lemmy works. Why aren’t comments on this exact post on a different server coming through to this comment section?
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 !technology@beehaw.org.
The weirdness starts, when you realize the canonical source for the post, is lemmy.tf, while @technology@beehaw.org is just a beehaw.org user who boosts it, beehaw.org caches the post, and marks @technology@beehaw.org as a “special user” that makes the post show in a “community” called !technology@behaw.org, even back on lemmy.tf.
Some other instance-agnostic way of referencing “a given post boosted by !technology@beehaw.org”
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 @technology@beehaw.org.
According to Lemmy rules, the post “got submitted to !technology@beehaw.org”, 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.
You are not logged in. However you can subscribe from another Fediverse account, for example Lemmy or Mastodon. To do this, paste the following into the search field of your instance: !technology@beehaw.org
A nice place to discuss rumors, happenings, innovations, and challenges in the technology sphere. We also welcome discussions on the intersections of technology and society. If it’s technological news or discussion of technology, it probably belongs here.
Remember the overriding ethos on Beehaw: Be(e) Nice. Each user you encounter here is a person, and should be treated with kindness (even if they’re wrong, or use a Linux distro you don’t like). Personal attacks will not be tolerated.
There’s some comments here if you’re interested: https://lemmy.tf/post/2853006
Thanks internet friend
I wish there were better ways to past around lemmy post links because lemmy.tf is down for me right now.
Should be back up now. Was funny because it’s a link back to beehaw.
This points out to me that I don’t think I understand how Lemmy works. Why aren’t comments on this exact post on a different server coming through to this comment section?
I think it’s a different post linking a different article about the same story
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 !technology@beehaw.org.
The weirdness starts, when you realize the canonical source for the post, is lemmy.tf, while @technology@beehaw.org is just a beehaw.org user who boosts it, beehaw.org caches the post, and marks @technology@beehaw.org as a “special user” that makes the post show in a “community” called !technology@behaw.org, 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 @technology@beehaw.org.
According to Lemmy rules, the post “got submitted to !technology@beehaw.org”, 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.
Lemmy.TF was down because it was being updated to 0.19, so the URL couldn’t find what the link ID was pointing to