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.
“Protecting your data” is probably a nonsense thing to say. You can’t at the same time make a post public and “protect” it from someone copying, reading, or learning from it.
It is theoretically possible to publish in public while protecting information but it requires the added step of maintaining authorization for those you wish to see that data.
You could create a protocol where poster info is encrypted and only the appropriate parties are given the keys to access that information. To the general public it’s posted by an anonymous user.
The question to ask is who really cares that much about your posts? Use a VPN and make an alt account and Bob’s your Uncle.
There’s also the question of the value of that metadata. If something like an email address or phone number was tied to your account in a publicly available fashion that would be one thing as those are relatively unique and can be used to tie back to an individual person. But if all you’re getting is a username with nothing else attached that’s a lot more nebulous. If you care to obfuscate your activity you could easily just create an account with a name you’ve never used before. That’s probably far more effective at preventing your “data” from being harvested by meta than some kind of encryption scheme would be unless you’re willing to go all in on E2E encryption which creates a ton of other problems that would need to be solved.
Exactly. But you can now get burner numbers much easier so obfuscating the meta data outside the service is getting easier. Not perfect but easier.
If you are doing things where you need full on clean room level obfuscation you can never use any type of service outside of your full control. At that point you’re talking one time pads and posting messages in the wanted ads of news papers.