• farcaster@lemmy.world
    link
    fedilink
    English
    arrow-up
    16
    arrow-down
    9
    ·
    1 year ago

    Ok, so what is actually the main argument people have to preventatively defederate with Threads? I perhaps haven’t thought about it much, but I don’t personally see the problem if my instances would federate with them. I’m mentally comparing this to email. If I ran my own email service, or used someone else’s, why would I want to block Gmail, or icloud, or Hotmail/Outlook?

    Of course if they don’t have effective admin/moderation policies and actions then, yeah they should be blocked or limited. The same holds true with email federation.

      • farcaster@lemmy.world
        link
        fedilink
        English
        arrow-up
        12
        ·
        1 year ago

        Thanks, that’s actually precisely what I was interested in reading. That admin team totally rocks for motivating their decision with such a comprehensive argument.

    • spiderman@ani.social
      link
      fedilink
      English
      arrow-up
      5
      ·
      1 year ago

      The content on threads are utter garbage. I have tried to get on with it but it doesn’t seem to work out for me.

    • pomodoro_longbreak@sh.itjust.works
      link
      fedilink
      English
      arrow-up
      1
      ·
      1 year ago

      I think the issue is that on most people’s feeds, the vast, vast majority of the content that they see would be from the @threads “instance.” Think of how salty people get about the size of mastodon.social or lemmy.world are compared to other instances, and multiply that along with the threat of a poison pill in the form of corporate embrasure.

      Culturally, the fedi is pretty anti-corporate, so a lot of members are suspicious of centralization / partnership with corporate entities. Though this lens, I think the objections make total sense.