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

  • Kichae@kbin.social
    link
    fedilink
    arrow-up
    5
    ·
    1 year ago

    Boosting is super important in all contexts in the Fediverse.

    When am instance subscribes to a content source - be that a user actor or a group actor - on behalf of a user, it only requests future content. Back catalogues are not fetched by default. Boosting re-publishes the content, so that it is received by new followers.

    With a group actor, the boost triggers the actor to reboot the content itself, sending it out to new subscribers to the group, and filling in that back catalogue.

    • blazera@kbin.social
      link
      fedilink
      arrow-up
      1
      ·
      1 year ago

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

      • Kichae@kbin.social
        link
        fedilink
        arrow-up
        1
        ·
        1 year ago

        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.

        • blazera@kbin.social
          link
          fedilink
          arrow-up
          1
          ·
          1 year ago

          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.

          • Kichae@kbin.social
            link
            fedilink
            arrow-up
            1
            ·
            1 year ago

            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.

            • blazera@kbin.social
              link
              fedilink
              arrow-up
              1
              ·
              1 year ago

              “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.

              • Kichae@kbin.social
                link
                fedilink
                arrow-up
                1
                ·
                1 year ago

                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.

          • Kichae@kbin.social
            link
            fedilink
            arrow-up
            1
            ·
            1 year ago

            This is why the functionality was hidden behind the upvote button initially, but people wanted the arrows to match the arrows on Lemmy.