Dear server admins, please defederate threads.net. Dear users, ask your server admin to defederate threads.net.

My Password Is 1234@lemmy.world to Fediverse@lemmy.world – 970 points –
mstdn.social

Meta just announced that they are trying to integrate Threads with ActivityPub (Mastodon, Lemmy, etc.). We need to defederate them if we want to avoid them pushing their crap into fediverse.

If you're a server admin, please defederate Meta's domain "threads.net"

If you don't run your own server, please ask your server admin to defederate "threads.net".

818

You are viewing a single comment

have different problem

platform owned by corporation tends to have more pro corporate users

what happens to existing culture on fediverse

is general trend that online communities get worse when above threshold

Most people on Threads aren’t pro-corporate, they don’t actually give a shit about that. They’re just too confused by the decentralized model to be on Mastodon, couldn’t get an invite to Bluesky, and wanted somewhere to be other than Twitter.

Being connected to it all via Threads could eventually help them get enough understanding to migrate to a different instance.

aren't pro corporate

threads can still have more pro business people than fediverse

does analogy about non-technical topic work better

what happens to existing culture on fediverse

Likely nothing. If Threads users are problematic and Meta refuses to moderate them appropriately, then instances can defederate later.

Doing it preemptively or forming a pact is just absurd, though. It's treating the users of Threads as a threat, instead of Meta (who can and will still be able to harvest anything they want from the Fediverse, because that's how ActivityPub works), and that's not fair to them who didn't ask to be thrown into our community in the first place.

defederate later

problem often cause damage before is addressed

pre block be safer

threads users signed up for threads

problem often causes damage before is addressed

pre block be safer

You build a bridge. After awhile it might start to decay and without proper upkeep it might even collapse! Better to never build a bridge in the first place.

I'd rather not build a bridge to the land of festering pustules to begin with

1 more...

If that's how you want to run your instance, that's your right to do. But for community-based instances, the users should have some say in the matter.

Yes, I can move to another instance if mine decides to defederate, but that's a lot of hassle that I'd have to go through because of a decision somebody else made for me, all because they can't or won't moderate themselves.

If you don't like decisions somebody else makes for you, then run your own instance.

This isn't meant to be snarky, btw, it's a valid solution and one of the freedoms of the fediverse system.

1 more...

Clearly you haven't dealt with a Mastodon instance having a major defederation event.

For most users, regardless of the validity of the defed, the user experience is terrible. Their social graph just suddenly, stops working, the people they follow can no longer see their posts, all because of the actions of a few bad actors or administration failures.

This paired with the fact that maybe only Firefish or Misskey lets you (mostly) seamlessly migrate to a new instance with your data intact, and the lack of a standard way to see what followers you will actually keep when you migrate, means that the defederation experience is sucks, and migrating to a different instance to escape that is a pain in the ass.

Meta has already shown it has piss poor moderation in the best of times, and actively boosts incendiary content in the worst of times, all while collecting, profiling, and exploiting your data. It's literally inevitable that they're going to break the rules of all but the free-est of free speech Instances, so for the privacy, safety, and headaches of everyone in the fediverse, we might as well save ourselves the trouble.**

1 more...
1 more...