Fediverse

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.

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.

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

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.

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.

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.

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.

Some food for thought from Mastodon:

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

I don't think we should defederate threads. It would only give Meta a walled garden which we will be outside of. Let them embrace us here and encourage everybody to scatter across instances so they can't defederate reasonably

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.

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

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

The EEE argument is a red herring at the moment. Sure, in the future, Meta and others could get clever in ways we can't imagine right now, but currently it's a "sky is falling" kind of threat. As it currently stands, the path from Threads launching to "Meta killing the fediverse" has all the logical progression as the Underpants Gnomes.

Threats is a better name for that data collecting pos.

"Should 'we' do?"

Nothing. If people and/or communities coming in through Threads are engaging in good faith, cool, more nice folks to have a community with. People/communities engaging in bad faith get blocked/defederated as is already common practice (and seems to be working outstandingly already, looking at average quality of posts and discourse "here" as compared to the "big platforms").

When Meta/Threads is hosting communities I like to see/be a part of, I'll figure out how to subscribe/integrate those. Besides that, they're free and welcome to run echo chambers in their own instances and communities, I don't see how any of that would ever show up on my feed.

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.

threads will never federate.