this post was submitted on 05 Jul 2023
20 points (100.0% liked)

main

76 readers
9 users here now

Default community for midwest.social. Post questions about the instance or questions you want to ask other users here.

founded 3 years ago
MODERATORS
seahorse@midwest.social
20
Meta's Threads.net (midwest.social)
submitted 1 year ago by Banzai51@midwest.social to c/main@midwest.social
39 comments fedilink hide all child comments
 

Are we going to block Meta's Threads.net? I get it if people want to keep things open. However, Meta is a proven bad actor. They claim they didn't put in ActivityPub because it was too complicated to get it done at launch, and they can't get EU approval of their service because of the rampant and invasive data they gather. IMHO, they are going to attempt to muscle the fediverse out of the equation.

you are viewing a single comment's thread
view the rest of the comments
[–] oatscoop@midwest.social 2 points 1 year ago* (last edited 1 year ago)

The privacy concerns immediately fall apart when you realize Meta doesn’t have to have their brand-name service to get access to everything going across ActivityPub.

There's far less incentive to scrape that content when you remove the ability to interact with and find it through Threads. It's unlikely facebook itself will be combing though lemmy instances looking for quality content to ~~rip off~~ "share" -- it will be the users.

Defederation creates a far higher barrier for Thread users to find and engage with posts on the wider ~~lemmy~~ ActivityPub network, which means far less of the fediverse's content being used for Meta's benefit.