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.
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.
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.
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.
Wait so when I boost a comment it appears on my feed or something? I am a bit confused
I am also confused, but I’ll take a stab at it. Boost is basically retweet in Twitter. Stronger than upvotes since it hits a wider audience.
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.
How are they able to post from their mastadon account? Do you link your mastadon account to kbin somehow?
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.