this post was submitted on 05 Jul 2023
74 points (90.2% liked)

Technology

60111 readers
3844 users here now

This is a most excellent place for technology news and articles.

Our Rules

  1. Follow the lemmy.world rules.
  2. Only tech related content.
  3. Be excellent to each another!
  4. Mod approved content bots can post up to 10 articles per day.
  5. Threads asking for personal tech support may be deleted.
  6. Politics threads may be removed.
  7. No memes allowed as posts, OK to post as comments.
  8. Only approved bots from the list below, to ask if your bot can be added please contact us.
  9. Check for duplicates before posting, duplicates may be removed

Approved Bots

founded 2 years ago
MODERATORS
L3s
[email protected]
[email protected]
L4s
enu
74
Another case for defederating from threads.net (Meta’s Twitter replacement that supports ActivtyPub) (self.technology)
submitted 2 years ago by LargeHardonCollider to c/technology
22 comments fedilink hide all child comments
 

There’s been a lot of talk about Meta’s new twitter clone called Threads because it will federate with other ActivityPub apps. I’ve seen several posts about them possibly using the app as a way to embrace, extend, and extinguish ActivityPub.

Another more immediate concern I have is that Meta will now be able to harvest data from users of other ActivityPub social networks like Lemmy and Mastodon. If Alice on Threads follows Bob on Mastodon for example, that means Bob’s mastodon instance will send information about all of Bob’s posts and everyone who interacts with them to Meta so that Alice can see it.

This is a concern specifically with Meta and other big tech companies running ActivityPub-enabled servers, because their primary motive is to harvest user data to use for advertising. The scariest part to me is that users on networks like Mastodon specifically migrated to Mastodon to get away from big tech, and Meta is still able to harvest their data with Threads.

you are viewing a single comment's thread
view the rest of the comments
[–] [email protected] 2 points 2 years ago* (last edited 2 years ago)

Or simply query the API from an existing instance, like third party clients do. Though I suppose then it'd have to account for rate limits.