this post was submitted on 19 Jun 2023
237 points (100.0% liked)
Technology
37758 readers
443 users here now
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.
founded 2 years ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
The problem is that the blocking will have to be layers deep. If your instance has defederated from Meta, but is federated with an instance that does federate with Meta, then Meta still has access to all your data through that mutual server. So not only would people have to defederate from Meta, they'd have to defederate with anyone who does federate with Meta. If everyone isn't on board with this, it'll cause a huge fracture to form.
Make no mistake: Meta wants to sell your data. They know all it takes is one server to federate with them and they've unlocked the entire fediverse to be harvested. I would not be shocked to see large amounts of cash flowing in exchange for federation rights.
Meta has access to my data anyway. Everything I post here is public, and there's nothing stopping them from scraping it. That's not the problem. The problem is Meta controlling the Fediverse, not merely observing it.
This is a point I've not seen brought up. Anyone who wants to is already able to (and maybe are) using my data for all sorts of things, including training LLMs.