573

What should we do about Threads? (programming.dev)

submitted 1 year ago* (last edited 1 year ago) by NineteenDoornails@programming.dev to c/fediverse@lemmy.world

279 comments fedilink hide all child comments

A lot of people dislike it for the privacy nightmare that it is and feel the threat of an EEE attack. This will also probably not be the last time that a big corporation will insert itself in the Fediverse.

However, people also say that it will help get ActivityPub and the Fediverse go more mainstream and say that corporations don't have that much influence on the Fediverse since people are in control of their own servers.

What a lot of posts have in common is that they want some kind of action to be taken, whether it'd be mass defederating from Threads, or accept them in some way that does not harm the Fediverse as much.

What actions can we take to deal with Threads?

you are viewing a single comment's thread
view the rest of the comments

[-] Zoldyck@lemmy.world 6 points 1 year ago

I think defederation isn't the solution. Am I dumb in thinking this could actual have a mutual benefit?

Just an example: I will never use Threads, but if I can communicate with them from my Mastodon account, I would like to have that option.

[-] PortugalSpaceMoon@infosec.pub 19 points 1 year ago

Many who don't see the danger were not here in the 2000's. There are so many great technical achievements that were killed by microsoft, google or facebook EEE'ing the shit out of it. Remember jabber/xmpp? Yeah, both FB and Google implemented the protocol in their chat apps. Everyone was thrilled; I could use my jabber client to connext to fb and talk to my friends. Then they remembered there's not any money in that and killed the projects.

Even if it's good for the fediverse now, as soon as they realize they can make more money by not having to sync with other companies and organizations, they'll be out of here, leaving nothing behind like a swarm of locusts. The only defense is defederation.