this post was submitted on 10 Jul 2023
259 points (92.7% liked)

Fediverse

28518 readers
557 users here now

A community to talk about the Fediverse and all it's related services using ActivityPub (Mastodon, Lemmy, KBin, etc).

If you wanted to get help with moderating your own community then head over to [email protected]!

Rules

Learn more at these websites: Join The Fediverse Wiki, Fediverse.info, Wikipedia Page, The Federation Info (Stats), FediDB (Stats), Sub Rehab (Reddit Migration), Search Lemmy

founded 2 years ago
MODERATORS
259
submitted 1 year ago* (last edited 1 year ago) by jocanib to c/fediverse
 

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.

you are viewing a single comment's thread
view the rest of the comments
[–] ninekeysdown 18 points 1 year ago* (last edited 1 year ago) (25 children)

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!

[–] [email protected] 17 points 1 year ago (8 children)

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

[–] CthuluVoIP 18 points 1 year ago (5 children)

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.

[–] MeetInPotatoes 3 points 1 year ago (1 children)

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.

[–] [email protected] 3 points 1 year ago

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

load more comments (3 replies)
load more comments (5 replies)
load more comments (21 replies)