Skip Navigation

We have 2-3 months to compile a Threads block list

www.timothychambers.net /2023/06/23/project-and-the.html

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.

134
TechNews @radiation.party irradiated @radiation.party
BOT
[HN] A Smarter Battle Plan to Protect the Open Social Web

You're viewing a single thread.

134 comments
  • So why is it important to not federate (or block) with Thread? Asking seriously. I read the article and while those are valid and real concerns. What is the net gain of that action? How does it help the fediverse? I cant see any way that it helps and lots of ways it hurts. At this point it seems like a lot of what ifs.

    Edit:

    If you need the reasons why to block Threads (meta) I think the answers below explain it better than most!

    • From what I understand, they're likely trying to kill the fediverse by making it irrelevant (embrace, extend, extinguish) seeing how it's finally starting to grow, since they can't just buy it up this time like they've always done to competitors.

      Even aside from that though, their algorithms designed to retain user attention by any means necessary are definitely going to seep into and poison the fediverse, at least indirectly, if they're federated.

      Not to mention they could easily run ads as normal posts and boost them artificially; they are an ad company after all. Wouldn't put it past them.

      Not federating with them means we don't have to deal with all that, and the fediverse can just continue to grow naturally as it's been doing.

      Federating on the other hand means a very real risk of permanently halting the fediverse's growth in favour of corporations', like Google did to XMPP

      • That's a good point. Would it not make more sense to block/de-federate when they start being bad actors rather than preemptively block? I'm not saying that preparing is bad, I think it's very much need and valid to assume they will be bad actors. I would like to be wrong and believe that being good hosts is better for their bottom lines. I do not expect them to do anything good because it's the "right" thing.

    • Once federated, an instance get a ton of data about users and their actions. I am not willing to provide that to facebook.

      • Defederating is a one-way transaction. Any instance that defederates from Threads will only stop themselves from receiving data from it, but Threads will still be able to pull data directly from any and all instances.

        • With enough instances not federating threads thr data they can get will become spotty.

          I understand it might not be everyone's cup of tea, but there's nothing on threads I want to receive.

          • I don’t think that’s true. Unless it’s a server side server denial rather than defederation, all posts on Lemmy are public. This means Threads will directly receive updates even from defederated instances.

            • Posts are public, yes, but you won't be able to see a post from an instance you're not federated with on your own instance. Yes, you can just load the instance url directly, but that's just web scraping. All voting interactions, views, etc are not available in those cases.

              I understand that if we have a setup like this:

                  Threads
                /         X
              A ----------- B
              

              then interactions from instance B on a post on instance A will, in fact, be available to Threads. But nothing happening on B will.

              Interactions on posts/communities on instance B coming from instance A will not be seen by Threads.

              Overall, I think Threads will not actually ever enable federation to begin with, and even if it does - Lemmy is a bit of a different beast compared to Mastodon.

        • CMV: The people who want to receive data from Threads should just...make a freaking Threads account. The whole argument to connect with them at all is weird. It's like recording a Disney movie to your DVR box and setting up streaming from your smart TV to your tablet so you can now enjoy the movie you recorded in bed....when you could've just downloaded the freaking Disney+ app.

          It's also (somehow) like when you're already in shorts and a t-shirt but still a little warm and someone else wants to turn the A/C off cause they're cold. They can put on more clothes and be totally comfy, I cannot (politely) take any more clothes off.

          • Accessing threads from mastodon is significantly more private than downloading the official app.

      • That’s something I had not considered, good to know. I think I need to setup an instance in my lab and do a deep dive into it. Thanks!

    • @ninekeysdown @jocanib i would say its because its meta trying to get a foothold on the fediverse and possibly take people away from here. people might just use threads instead of mastodon or lemmy since they can get the content on threads. my take

134 comments