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

Fediverse

28295 readers
732 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 !moderators@lemmy.world!

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 1 year ago
MODERATORS
ruud@lemmy.world
Xylinna@lemmy.world
MrCenny@lemmy.world
TragicNotCute@lemmy.world
automodbeta@lemmy.world
woelkchen@lemmy.world
259
We have 2-3 months to compile a Threads block list (www.timothychambers.net)
submitted 1 year ago* (last edited 1 year ago) by jocanib@lemmy.world to c/fediverse@lemmy.world
135 comments fedilink hide all child comments
 

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
[โ€“] dystop@lemmy.world 15 points 1 year ago* (last edited 1 year ago) (1 children)

Everyone is talking about defederating preemptively because of XMPP and EEE. But the very fact that we know about EEE means that it's much less likely to succeed.

Zuck is seeing the metaverse crash and burn and he knows he needs to create the next hot new thing before even the boomers left on facebook get bored with it. Twitter crashing and burning is a perfect business opportunity, but he can't just copy Twitter - it has to be "Twitter, but better". So, doing what any exec does, he looks for buzzwords and trends to make his new product more exciting. Hence the fediverse.

From Meta's standpoint, they don't need the Fediverse. Meta operates at a vastly different scale. Mastodon took 7 years to reach ~10M users - Threads did that in a day or two. My guess is that Zuck is riding on the Fediverse buzzword. I'm sure whatever integration he builds in future will be limited.

TL;DR below:

[โ€“] inexplicablehaddock@lemmy.loungerat.io 4 points 1 year ago

I agree. All the Fediverse is to the Silicon Valley firms is the current buzzword. Like you said; if- and to me, it's a question of if and not when- Fediverse integration gets built into Threads, it's gonna be limited. My bet is that somehow they're gonna make it so that Threads instances can only federate with other Threads instances.

And that's if it exists at all. I feel there's a considerable chance that Meta just throws away the Fediverse integration idea. Either it's too much effort for too little profit, or some new buzzword comes along for them to chase.