The exchange is about Meta’s upcoming ActivityPub-enabled network Threads. Meta is calling for a meeting, his response is priceless!

    • Bloonface@kbin.social
      link
      fedilink
      arrow-up
      1
      ·
      edit-2
      1 year ago

      For some reason, your link doesn’t work.

      The second part of your comment doesn’t answer my question, nor would “they want our data!!!” explain why Meta would want or need to create an instance in order to get it, or how the “data” (what data? Your posts? The ones that ActivityPub syndicates to hundreds of other servers automatically? Do you know exactly which servers your posts are on at the moment?) of other users on other fedi instances could somehow be “monetised” by them.

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

          OK, I’ve read that link and it still doesn’t really explain how exactly Meta intends to monetise other peoples’ posts - “collect data from and monetise”, how exactly are they going to monetise other peoples’ posts on other instances, when they have no ability to e.g. serve ads to those people?

            • QHC@kbin.social
              link
              fedilink
              arrow-up
              2
              ·
              edit-2
              1 year ago

              I don’t think anyone is questioning your cynicism of Meta’s intentions or motivations, but the nature of the Fediverse is specifically designed to make it very difficult (if not impossible) for any one party to control the entire thing. It’s a question of how not if.

              The worst thing I could see is something like the development of React where FB has an overwhelming advantage in sheer resources and ends up having a major influence on the direction of software trends. But that would still just be a popularity thing and would not actively stop anyone from doing their own thing. Maybe there is something in the license for ActivityPub that would let them pull a Google-vs-Oracle reverse engineering, but again that won’t stop other instances or developers from ignoring them if they wanted.