That's the federated aspect of those platforms at work. Assuming both instances of a given platform on the Fediverse (here, Fosstodon and kbin.social) are federated together, which they are by default, content from both will be accessible from users of the instances.
This might just be me, but arbitrary CAPSLOCK on words and Title Case on threads that aren't a link to a news article are clickbait patterns that I'd prefer to not see on kbin.
As for the object of the thread itself... I am thoroughly unsurprised. I have never seen IranianGenius involved in any positive manner with /r/tumblr whereas TayTay was singlehandedly responsible for making /r/tumblr into slightly less of a garbage heap. Removing the one mod that was actually improving things is perfectly in line with Reddit's recent behavior.
As far as kbin is concerned, it will appear under the "boosted" category. Some platforms handle this differently. To take a random user as an example, this fosstodon user has a bunch of posts which will show up separately from their boosts when viewed from kbin. But looking at their profile from Fosstodon itself, you will see posts and boosts mixed together as is the norm on Mastodon.
On that note, upvotes and downvotes upvote matter even less here ("here" meaning kbin) as the factor dictating comment order in the "hot" ranking is boosting (think retweet equivalent), not the vote count.
Not sure how that goes on Lemmy though.
He's just trolling us and speedrunning the PR meltdown category at this point, isn't he?
I can understand the value of making your community a more tight-knit one with a proactive stance on moderation, that's how Tildes operate and they're doing fine. The thing is I'm not sure I understand why, given this goal, Beehaw is part of the Fediverse in the first place, where there isn't much preventing someone from an outside group coming in. This sounds like a case where a centralized instance makes more sense. Maybe they're trying to see if such a community can exist on the Fediverse, in which case fair enough, but this seems like an uphill road.
Given that kbin (or at least kbin.social) generally doesn't have restrictions on making accounts either I would assume we're next, eventually.
@onceuponaban
@kbin.social