Meta/Instagram launched a new product called Threads today (working title project92). It adds a new interface for creating text posts and replying to them, using your Instagram account. Of note, Meta has stated that Threads plans to support ActivityPub in the future, and allow federation with ActivityPub services. If you actually look at your Threads profile page in the app your username has a threads.net tag next to it - presumably to support future federation.

Per the link, a number of fediverse communities are pledging to block any Meta-directed instances that should exist in the future. Thus instance content would not be federated to Meta instances, and Meta users would not be able to interact with instance content.

I’m curious what the opinions on this here are. I personally feel like Meta has shown time and time again that they are not very good citizens of the Internet; beyond concerns of an Eternal September triggered by federated Instagram, I worry that bringing their massive userbase to the fediverse would allow them to influence it to negative effect.
I also understand how that could be seen to go against the point of federated social media in the first place, and I’m eager to hear more opinions. What do you think?

  • SickIcarus
    link
    fedilink
    English
    arrow-up
    11
    arrow-down
    1
    ·
    1 year ago

    Honestly, this would be a non-issue if we could block instances at the user level. Since they’re not federated yet, and User-level instance blocking should be coming, I say we wait and see.

    • DiaryOfJayne@vlemmy.net
      link
      fedilink
      English
      arrow-up
      9
      arrow-down
      1
      ·
      edit-2
      1 year ago

      I wish there was a way to grey-list an instance, to where a user has to seek out and subscribe to content that admins don‘t want spamming users by default, so it doesn‘t get added to the „ALL“ feed for everyone else.

      Just give users more control.