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".

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

[–] Creatortray 43 points 9 months ago (59 children)

Okay. I’ve seen stuff like this on both mastodon, and here, but i haven’t heard about them doing anything that would actually harm the fediverse. I guess i don’t know what the problem is. I know they’ve got a negative reputation, and for good reason, but isn’t that the awesome part of threads being federated? We can follow and connect to people there without being part of their system, and therefor not susceptible to their bs? If I’m missing something please fill me in.

[–] [email protected] 11 points 9 months ago (1 children)

@Creatortray
You've just written it : their negative reputation for easaly understandable reasons. We can already foresee Threads will very soon be used to spread the most toxic campaigns on the net and that will undoubtably harm the Fediverse. One of the most valuable trait of the Fediverse is its decentralization and consequently, the potential accountability of any server administrator. Why should we take those risks when it's so easy to avoid it? #BlockThreadsOut
@mypasswordis1234

[–] [email protected] 0 points 9 months ago (1 children)

@Nelfan @Creatortray @mypasswordis1234 if my server federates with #Threads and it creates a problem, I’ll stop supporting it and move to one that doesn’t.

[–] [email protected] 1 points 9 months ago

@boiglenoight @Nelfan @Creatortray @mypasswordis1234
Great toot, Nelfaneor, but to use the word 'risk' with respect to the probability of #falseBook creating harm in the #fediverse network, is a mistake — it is a "certainty".

Boiglenoight if you value the free and open web we have news for you, your instance is having its HTTPS intercepted by Cloud(G)lare (change 'G' to 'F'). Move to a different one, if you want us to continue dialog with you.

load more comments (57 replies)