514
PSA: while upvoting exists, to get the "move closer to the top" effect that reddit's upvote had, you need to click boost (kbin.social)
submitted 3 years ago by to c/RedditMigration@kbin.social
85 comments fedilink hide all child comments
 

a small difference, but important to how people use the site

you are viewing a single comment's thread
view the rest of the comments
[–] 2 points 3 years ago (9 children)

if old content isnt fetched for a newly subscribed instance to see, how are users going to boost that content in the first place?

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 9 child comments
    •
  • [–] 1 point 3 years ago (8 children)

    Users who can see the content need to boost it?

    Users who use the website that the community is hosted on have access to the full library of it. They need to boost stuff. And people who subscribe from remote sites need to boost older content that they've seen.

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 8 child comments
    •
  • [–] 3 points 3 years ago (5 children)

    but relevant users cant see it, its never fetched for them to see it. Sure users on the home instance can see it, but they're on the home instance, it's already fetched for them. Ive run into this problem on here, where there is a lot of content on other instances that isnt visible from kbin. I have the option of visiting the home instance to see it, but it takes me completely off of kbin, I cant boost it from that page.

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 5 child comments
    •
  • [–] 1 point 3 years ago (4 children)

    Someone just needs to follow. The community owner either needs to seed the community to big instances using accounts on them, or people who find the community via other instances need to subscribe and know that fresh content will come. Then they can boost older content from the hosting site.

    Things take some conscious effort here. That isn't necessarily a bad thing.

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 4 child comments
    •
  • [–] 2 points 3 years ago (3 children)

    "Then they can boost older content from the hosting site." No that's the problem. Like you yourself said back catalogues arent fetched. They can't see the older content to be able to boost it, they'll only see new content.

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 3 child comments
    •
  • [–] 1 point 3 years ago (2 children)

    If my instance follows a community at time t = T, and your instance starts following it at time t = T+10, I can boost content posted between T and T+9 so that you can see it.

    Meanwhile, if people on the hosting instance boost things posted from times earlier than T, we both get to see them. Then, once they're visible to us, we can continue to boost them for new instances to see.

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 2 child comments
    •
  • [–] 1 point 3 years ago (1 child)

    If boosting is meant to be a solution to the back catalogue problem, then it's a horrible way to do it. You'd have to go through and boost every single post from before the hosting instance was followed, and then it'd only show up the user page of the guy who went to all of that effort? (or, realistically, bot).

    If what I'm saying is accurate (and I'm still not sure because this is admittedly a bit too complicated for me) then it doesn't sound very useful since individual profiles aren't nearly as important in a forum context when compared to something like twitter, and especially when you can just upvote something and have that show on your profile. Unless I'm mistaken and anything you've upvoted doesn't propagate to another automatically instance while boosts do... but I don't think that's a big enough distinction to have two different buttons? You could just have an upvote also do that.

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 1 child comment
    •