Perhaps more importantly why would one retweet a comment? Rather than a post?
The way content propagation works here is that someone using Website A follows a remote content source (either a user, or a group – aka a “community” or a “magazine”), and the remote hosting website (let’s call it Website B) sends all subsequent content from that source to Website A, where the requesting user can then view it. If someone from Website A was already following that content source, then they get to see all of the content that Website A had already received, and benefit from earlier users efforts. But if that person was the first from Website A to subscribe to that content source, then they only get future content.
It’s very similar to a, well, a magazine subscription in that way. NatGeo isn’t sending you their 150 years worth of back catalogue when you subscribe in 2023 (not that you should bother subscribing to NatGeo in 2023).
The ‘boost’ button republishes content, though. Posts, comments, whatever. Hitting ‘boost’ on a comment republishes it, and once republished the group actor (the little bot-like construct that functionally is the group) sees it as new content, and pushes it out to everyone following it. This means it will reach websites that started subscribing to the group after the comment was originally posted.
Boosting is how older content (where older basically means “from anytime before literally right now”) spreads through the fediverse.
So this is one of those things like git, where you can’t explain how it works on the surface to a normal person because it barely even makes sense if you don’t know about the underlying plumbing. :\
Not awesome, but I guess that’s what you get when you graft a reddit-like experience onto a fediverse that was more or less invented for microblogging.
Thank you so much for this explanation, it really helped some of this click for me. I don’t use kbin, so the boosting isn’t so relevant to me, but I’m beginning to understand some of how the federation works together.
I’m not sure how Lemmy syncs and backfill, but under its hood, I imagine it’s doing the same thing, just automatically. Lemmy groups are really spammy with boosts when viewed from Mastodon, for instance.
This makes sense — but if nobody knows it there is lots of room for confusion.
“Boost” seems more like “updoot” than “retweet“. Perhaps more importantly why would one retweet a comment? Rather than a post?
The way content propagation works here is that someone using Website A follows a remote content source (either a user, or a group – aka a “community” or a “magazine”), and the remote hosting website (let’s call it Website B) sends all subsequent content from that source to Website A, where the requesting user can then view it. If someone from Website A was already following that content source, then they get to see all of the content that Website A had already received, and benefit from earlier users efforts. But if that person was the first from Website A to subscribe to that content source, then they only get future content.
It’s very similar to a, well, a magazine subscription in that way. NatGeo isn’t sending you their 150 years worth of back catalogue when you subscribe in 2023 (not that you should bother subscribing to NatGeo in 2023).
The ‘boost’ button republishes content, though. Posts, comments, whatever. Hitting ‘boost’ on a comment republishes it, and once republished the group actor (the little bot-like construct that functionally is the group) sees it as new content, and pushes it out to everyone following it. This means it will reach websites that started subscribing to the group after the comment was originally posted.
Boosting is how older content (where older basically means “from anytime before literally right now”) spreads through the fediverse.
So this is one of those things like git, where you can’t explain how it works on the surface to a normal person because it barely even makes sense if you don’t know about the underlying plumbing. :\
Not awesome, but I guess that’s what you get when you graft a reddit-like experience onto a fediverse that was more or less invented for microblogging.
Thank you so much for this explanation, it really helped some of this click for me. I don’t use kbin, so the boosting isn’t so relevant to me, but I’m beginning to understand some of how the federation works together.
I’m not sure how Lemmy syncs and backfill, but under its hood, I imagine it’s doing the same thing, just automatically. Lemmy groups are really spammy with boosts when viewed from Mastodon, for instance.