Join the pact and not just vow but actually do defederate Threads as soon as it comes online: https://fedipact.online/

Meh, federated or defederated, threads poses only the first challenge to the fediverse. There will be other players with their own incentives that will join via ActivityPub, add their own custom features incompatible with the broader world, and entice users with slicker interfaces. Fediverse will need to show it can weather it, especially hard with the network effects of the larger corporations' user bases.

My hope is the pressure will keep open services innovating to better compete and result in a richer experience for everyone.

Absolutely defederate from threads immediately from anything threads related.

Threads will collect any and all data they can about users disregarding which server you are on, and not agreeing to their business practices.

There's a reason they are not in the EU, including NI despite being in UK. And that's probably because their practices are illegal, and don't respect the rights of their users according to EU regulation.

The second Lemmy federates with Threads, I'm out of here.

Ignore it. Defederate. Defederate with any instances that chose to federate with it. Keep the fediverse small and independent. It's nice here, let's keep it nice.

It's a clear EEE attack. Do not federate!

Some food for thought from Mastodon:

https://blog.joinmastodon.org/2023/07/what-to-know-about-threads/

How so many people seem to brush this off is beyond me. As far as I'm concerned the purpose of federated, decentralized services is being in charge of who to trust and huge corporations not controlling or monitoring every part of your online activity.

Obviously as soon as Meta starts dealing with ActivityPub and Fediverse, the overwhelming majority of users will flock to their servers. They will be more userfriendly and responsive. In effect they will also hold the overwhelming majority of content and data. Just a matter of time till most of the other instances will become obsolete, due to bandwith regulations or smth similar,

The fediverse will be rebranded as the "Threadiverse"

Just: We absolutely must wall off Meta.

I think we should defederate any corp version of any federated app. Not due to privacy or anything, but because it silos anyone using those services from everyone else. Bluntly, I don't want people's B.S. propeganda on the fediverse, and the stupid crap conspiracy farm that Facebook and other places have become.

I'm sure it won't stop the stupid from reaching us, but it should limit the amount and impact that those users have. Additionally, it will remove a lot of high quality content from those services making them less viable for corps to run and maintain. They will happily farm the fediverse for content to attract users they can monitize.... I'm not a fan of handing them more content to steal while they share zero of the profits of that content with either the creators or the communities that handle that data.

I'm not doing their job for them in promoting entertaining and informative posts just so they can make money on it. They want it, they can put forth the effort themselves.

Push celebrities, influencers, and businesses to create their own instances, outside of Meta.

If they just use a Threads account, then the Fediverse gets made irrelevant. Along come the Three E's, and Meta walls up the garden and starts putting billboards up everywhere.

Celebrities, influencers, & businesses need to know that they can now have a social media presence that they own, rather than rent, where they can make the rules for the communities they host. It's good for them in that it keeps their Fediverse presence theirs, they get to call the shots and choose how their instance is set up.

Because if enough people have a strong Fediverse presence outside of Threads land, it'll make it much harder for Meta to pull the plug.

In my opinion, the people that use Instagram and will potentially use Threads aren't the ones who will get into the Fediverse.

They will probably not even know that this exists in the app as it just puts you directly in threads.net.

Also, there's the option that this is just a 'trend thing' that will die in a week or two, probably because people won't get used to or due to legal problems (as it's already happening).

Edit: typo.

I'm going to block it as a user until I find a friendly, stable instance of my favoured Fediverse flavours that blocks it for me.

There's no persuasive argument I've heard for treating Meta as anything other than a rampaging horde of Huns on the attack.

I think defederating is the only way forward, Facebook will take over otherwise even if they do it slowly.

I was recently asked by my employer if we should move our social media efforts to fediverse and my recommendation was that this community it's both too small and also would be hostile (rightly) to corporate empty posting.

As soon as threads has a web interface that's usable I will be starting up there...

You put your recycling in the blue can, compost in the green can and your corporate garbage on Meta.

Aren't the privacy concerns about threads so bad they can't release it in Europe?

If you give meta a crack in the door of the fediverse it's going to do all it can to consume it entirely. Allow meta in at the peril of federated social media.

I'm going to recommend that if W3C starts accepting changes to the AP standard from Meta, the community must maintain a fork that rips out any offending parts.

I want nothing to do with meta or facebook.

If this gets serious I'm out of here as fast as I dumped reddit.

~tildes it is.

I feel like the EEE attack is inevitable at this point.

Why else would they even be willing to federate?

They saw the threat that decentralized non-profit social media is and want to kill it before it has a chance.

All Lemmy servers and especially the largest ones need to defederate from it immediately.

Drop that trash

There's really no imminent threat with Meta and ActivityPub, as a standard.

As for Threads and Mastodon, the "threat" is mild. If Meta wants your data, they can get it without spinning up an entire social network. If the concern is that it's going to lower the quality of the content, well, there's probably some truth to that, but that would happen with popularity, regardless of which service became popular, and it's a problem solved by the block function.

I will leave and block any instance that federates with Meta, including this one, and go start my own instance, and only federate with others that also block it if I have to. Don't you dare allow their corporate garbage into our space 😠

Make an account and use chatgpt to shit post on it.

As the fediverse grows, there will inevitably be more centralized instances. Every big tech corp may want to start their own instance, similar to how most tech corps provide their own mail services.

There are millions of email service providers, but Gmail and Outlook are synonymous to email for a large amount of people.

Defederating with Meta and Tumblr is like Protonmail blocking every mail from Gmail. You just cripple yourself and make your instance useless.

Threads doesn't need to do an EEE attack. They've already gained many more users than the entire Fediverse. At this point, I wouldn't be surprised if they decided to not join the Fediverse at all.

I would never use Threads, but I would use a Mastodon instance that federated with Threads. I already see many journalists and content creators I like trying it out, who either stopped using Mastadon long ago or never even tried it in the first place. If Threads started doing things that negatively affected my experience, I would then switch to a Mastodon instance that wasn't federated with Threads.

In my opinion, nothing. If Meta is able to effectively take over Fediverse as people are claiming, then the Fediverse was never destined to survive to begin with. On to the next thing. This is the first real test of the resilience of this type of “decentralized social network”, and if it ends up going to shit, it would have eventually anyway.

we shouldn't do anything.

Isn't the whole promise of the fediverse that whatever the policies of one instance are, that doesn't necessarily affect all the other instances, and each can do their own thing. If an instance doesn't want to accept traffic from threads, good for them. But to try to organize a fediverse-wide response to threads seems a whole lot like the centralization the fediverse is supposed to not be.