petition: Defederate any instances that federates with threads proactivly , add threads.net on blocklists everywhere.

I'm for blocking Threads. I'm not for blocking instances that support Threads. That's ridiculous, you'd just split the community and make the Fediverse irrelevant.

Funny thing - the last time I saw a promising forum destroyed, the beginning of the end was when people got all in a panic about some purported external threat and started demanding a "united front" to combat it. Then they started calling for retribution against anyone who didn't join them. Then they just kept fanning the flames of hostility against anyone on the forum that they decided wasn't sufficiently devoted to their cause, and the forum ended up tearing itself apart from within.

And this is how you gut the Fediverse.... Don't even give people the option to run their own single-user instance to avoid the drama. Defederate them, too. Splinter everything into oblivion.

EDIT: Seriously. As someone who isn't a hardcore militant FOSS federation activist, this is the kind of stuff that makes me want to throw up my hands and say, "Screw it. I guess I'll go sign up at Threads."

I support blocking Facebook but not other instances.

I'm all for blocking threads on instances, BUT

defederating with OTHER instances just because they haven't blocked threads is gonna create a massive split in this community, possibly could kill it. big no 👎

I must genuinely ask? What does this accomplish, a lot of instances being split apart because one federates with meta and the other doesnt, its not like the meta posts are gonna make it to your instance if you defederate meta, so you are really just splitting the community over nothing. Privacy wise, activity pub is public, by design, so they can just already pull all the information it exposes, and likely do. And finally? How does this stop EEE?

If the Fediverse can't survive Threads is can't survive period, and we should all just move on now.

This has to be a joke, you can’t be this serious over nothing.

Defederating from Threads makes sense. Defederating transitively from anything federated with Threads ends in one of two ways: your instance shrivels up and dies, or you successfully kill Threads. Not particularly good odds. You can't compete with Meta, you can only try to maintain your independence and value as an independent platform.

I hate defederation for things like this. This should be a user's choice, not imposed by the instance itself. I hate how the fediverse forces the moderation choices on you.

I dont care that instagram uses activityPub. As long as I can use activityPub myself, thats enough for me. Most people will always stick with big social media, and I would rather be able to interact with them vs. not

I'm all for blocking Threads as an instance or user, but blocking instances that choose to federate with threads is going to leave a lot users who when Threads breaks its compatibility with Activity Pub with no social graph to keep them tethered to ActivityPub.

Threads can't get the data we're worried about it collecting from federation, they can only get it from you installing/using their site or their app. So don't do that.

I think the difference between this EEE and say XMPPs EEE is Meta/facebook is widely seen as a cancerous entity that people who are already here aren't going to want to use, and when they break compatibility few people are going to want to switch to their service as long as there's still enough people here to talk to.

Not to downplay the threat of EEE, we need to remain vigilant. Our best defenses are preemptive defederation or shitposting how we never see ads.

At this rate we'll extinguish ourselves before Meta even gets to the third E.

Does it use activitypub?

This is cutting off your nose to spite your face.

Most of the activity on any given instance or community comes from outside of the instance. If you start cutting off instances because they are sharing their own stuff with Meta, then you will also be negatively impacting your own communities since the amount of active users will go down.

Most users won't react to something like this by joining your instance or an instance that you approve of (or, at least, currently approve of). They'll either find another community on an instance they're federated with or they'll switch to another social media platform. The latter becomes more likely depending on how many instances end up on either "side" of the issue. Although most user accounts are relatively new, it's still a pain to switch over to something else once you've gotten used to something.

The scale of defederation you propose, especially this early in the fediverse, would be enough to turn off a lot of folks from federation. If admins are just going to defederate from each other at the first sign of disagreement, that weakens my faith in the fediverse.

I absolutely believe that instances should not federate with meta's stuff. The largest servers had enough issues when we were getting new users in the thousands. Meta will likely bring in users in the millions. However, it makes no difference to me if another instance federates with Meta.

What if you are on Meta's payroll and want to start this so the Fediverse destroys itself from within? Gotya, sucky Zucc! Nice try. /s

For real, can't this Meta train derail next to the Titanic already? Joining an open communication standard platform and then complain the open standard communicates with outside. I really think you have been in the wrong place from the very beginning.

Wtf, it doesn't make any absolute sense to defederate from instances that accepted to federate with threads!

Jesus christ this is turning into virtue signalling brain rot

Absolutely not! Do that and you'll skip right to the "Extinguish" part in EEE.

The biggest advantage of the Fediverse is the decentralized moderation. People will disagree on what to do with threads ATM. This comment section is proof on the lack of consensus of this.

Besides, this isn't a black and white issue. Some mods may blacklist some accounts on threads and allow others. Or choose to do a whitelist system and only allow certain accounts. There's many compromises that can be made in this area. But forcing one solution for this is harmful and runs counter to the spirit of the fediverse.

I’m all for individual users blocking Threads if they’d like to, but I think it’s a terrible idea for instance admins to make that decision for all of their users.

Personally, I don’t see why this is so controversial. I view it as a way to follow the celebs and organizations that would rather use threads, but from the comfort of Mastodon that is outside of Meta’s ecosystem.

ActivityPub and the Fediverse is designed to for natural selection to take place. So let it. The users that want to be part of the Fediverse are already here and won’t don’t leave based on what Meta does with Threads. Threads utilizing ActivityPub in the future justifies the means of the Fediverse more than anything else IMO. I despise Meta as much as the next person, but this is not the end of the Fediverse as we know it.

I expected the anti-Meta division to eventually demand recursive bans. The end result will be a hermit kingdom, and that's fine and dandy, but expect the Fedipact users to keep talking solely among themselves. (And the users that disagree to move elsewhere, making the hermit kingdom to become even more of an echo chamber)

I just blocked them on Mastodon. Thanks!

threads will never federate.

I agree, any fediverse servers that remain federated with Meta servers, they are helping Meta to collect your data.

Remember, the Threads app itself is a privacy nightmare.