Meta and Mastodon – What’s really on people’s minds?
ianbetteridge.com
​ There has been a lot of chatter about the decision of some instances on Mastodon to pre-emptively block Meta’s purported new ActivityPub-compatible service: Dare Obasanjo: It’s a weird own …

A very detailed article about the whole Meta (Instagram/Threads) vs. Fediverse discussions. It’s a long read, but well-worth it if you’re interested in the subject.

  • Rentlar@beehaw.orgEnglish
    10·
    2 years ago

    If I run my own instance, I can choose who I share with and who I don’t.

    The simple fact of the matter is that I don’t want my data to be Zucc’d, and clearly I’m not the only one who thinks that way.

    • chamim@kbin.social
      3·
      2 years ago

      I don’t use any Facebook products for a reason, and I would not want to have to move to a different instance if the one I chose would federate with Meta. And the same goes for other data-hoarding companies out there, in case they try to enter this space.

    • HiT3k@beehaw.orgEnglish
      3·
      2 years ago

      Exactly, and that’s why the response has been so negative. Every instance that federates with another stores a complete copy of the posts and comments from every federated user.

      If the majority of instances do not defederate from a Meta instance, that Instance will inevitably become the primary destination for discussion, even between and by non Meta-Instance based users, just because the communities in that Instance will be so large and active. And even if they don’t, Meta Instance will have a stored copy of every community whose Instance is federated.

      Meta will then have carte blanche to collect data on a huge collection of users from outside their own Instance.

      I acknowledge that they could get the same data by scraping the public Instances anyway, but still… Fuck all of that.