45
Meta and Mastodon: What’s really on people’s minds?
(ianbetteridge.com)
A nice place to discuss rumors, happenings, innovations, and challenges in the technology sphere. We also welcome discussions on the intersections of technology and society. If it’s technological news or discussion of technology, it probably belongs here.
Remember the overriding ethos on Beehaw: Be(e) Nice. Each user you encounter here is a person, and should be treated with kindness (even if they’re wrong, or use a Linux distro you don’t like). Personal attacks will not be tolerated.
Subcommunities on Beehaw:
This community's icon was made by Aaron Schneider, under the CC-BY-NC-SA 4.0 license.
If I run my own instance, I can choose who I share with and who I don't.
The simple fact of the matter is that I don't want my data to be Zucc'd, and clearly I'm not the only one who thinks that way.
I don't use any Facebook products for a reason, and I would not want to have to move to a different instance if the one I chose would federate with Meta. And the same goes for other data-hoarding companies out there, in case they try to enter this space.
Exactly, and that's why the response has been so negative. Every instance that federates with another stores a complete copy of the posts and comments from every federated user.
If the majority of instances do not defederate from a Meta instance, that Instance will inevitably become the primary destination for discussion, even between and by non Meta-Instance based users, just because the communities in that Instance will be so large and active. And even if they don't, Meta Instance will have a stored copy of every community whose Instance is federated.
Meta will then have carte blanche to collect data on a huge collection of users from outside their own Instance.
I acknowledge that they could get the same data by scraping the public Instances anyway, but still... Fuck all of that.