Context post at Mastodon.

Meta’s activitypub Twitter/Mastodon clone will be going live under the name threads.net on July 6th (less than 24 hours from the time of this post).

Are there any plans for lemmy.one to join the FediPact in blocking all of Meta’s bullshit? Considering this instance is built on the concept of privacy guides, with everything Zuck touches becoming completely antithetical to the word “privacy”, I would feel it fitting for us to join the block. Meta can, and probably will, farm every federated instance out there for both user data and to populate their own monetized platform with content. They need to be contained.

This post also applies to anyone federated to this instance who sees this post. Contact your admins. Get Meta on the blocklist.

  • bhj 🦥@lemmy.one
    link
    fedilink
    English
    arrow-up
    6
    ·
    edit-2
    1 year ago

    A little late to the party. I was on board with defederating until I read this comment on another instance’s meta community and it completely changed my mind.

    https://programming.dev/comment/690107

    tl;dr: Defederating doesn’t benefit us at all and just makes more users move to Threads, or at least an instance that hasn’t defederated.

    • Boz (he/him)@lemmy.one
      link
      fedilink
      English
      arrow-up
      3
      ·
      1 year ago

      I think this makes a good point about defederation being an unnecessarily dramatic step, but the poster also describes various steps instances might take to protect content and users without actually dropping the portcullis. It’s difficult to welcome Meta users (desirable) without welcoming Meta’s corporate interests (undesirable).