Threads and the Fediverse - A Smarter Battle Plan to Protect the Open Social Web
www.timothychambers.net
With the #meta #Project92 or #Threads Fediverse offering, there has been a, well, robust discussion of how to avoid threats looming. Those advocating mass-preemptive defederation make three cases for it. ➡️ To avoid data mining … However, defederation does virtually zero to avoid any big tech entity scraping all the Fediverse public social graph today - Want proof? See here: is.gd/q8U2pv But what if they merge that Fediverse data with their own internal data from IG isn’t that worse than just scraped data?

It is expected to be 2-3 months before Threads is ready to federate (see link). There will, inevitably, be five different reactions from instances:

  1. Federate regardless (mostly the toxic instances everyone else blocks)

  2. Federate with extreme caution and good preparation (some instances with the resources and remit from their users)

  3. Defederate (wait and see)

  4. Defederate with the intention of staying defederated

  5. Defederate with all Threads-federated instances too

It’s all good. Instances should do what works best for them and people should make their home with the instances that have the moderation policies they want.

In the interests of instances which choose options 2 or 3, perhaps we could start to build a pre-emptive block list for known bad actors on Threads?

I’m not on it but I think a fair few people are? And there are various commentaries which name some of the obvious offenders.

  • vtez44@kbin.social
    0·
    1 year ago

    Only real threats of Threads federation are EEE and server overload. Not the people from there or privacy. If someone wants to see some content you don’t want to see, like some opinion you don’t like, they should be able to see it. I don’t understand why there would be such list, it would be pure censorship and waste of time. I have heard Threads has a pretty good moderation, so that solves this problem anyway.

    I don’t get what would defederating with Facebook-federated instances gives you, though.

    • monerobull@monero.town
      0·
      1 year ago

      I don’t get what would defederating with Facebook-federated instances gives you, though.

      Means the instance isn’t part of the hive mind and we obviously can’t have that!

      • Flax@feddit.uk
        01·
        1 year ago

        I am a fediverse enthusiast and I am excited for Threads federating. I hope it incentivises Tumblr to federate also and then we actually finally have proper choice.

        • Kerrigor@kbin.social
          0·
          1 year ago

          I see you’re not familiar with EEE. This is a classic move by enterprise to kill an open competitor.

          • Flax@feddit.uk
            01·
            1 year ago

            I am. How could they kill the fediverse? If they tried to kill it, it would only return to how things was. Chances are tumblr could join in and then they couldn’t easily extinguish it.

            • Kerrigor@kbin.social
              0·
              1 year ago

              Ever heard of XMPP?

              If a single party participating in an open standard is large enough, they can go off the track, and then kill off interoperability.

              • Flax@feddit.uk
                01·
                1 year ago

                But this isn’t a single party. Mastodon and Lemmy and Kbin are well established

  • Flax@feddit.ukEnglish
    01·
    1 year ago

    5 is an absolutely horrible idea.

    1 and 2 are best