A more important topic is, what federated data will be kept on Meta, and most importantly HOW that data will be processed/used/sold by Meta.
Technology
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.
This has me thinking, is there a space set aside for putting profits over people instances out and center so admins can preemptively defederate and/or block them?
I haven't found one yet but I am rather new to this.
I think it'll be harder than that, even.
Meta doesn't need to spin up an instance to abuse user data on the fediverse, they just need an app that can read it. A hypothetical meta fediverse app could allow users to select their own instance and still read and collect data on the connected instances. As far as I know, there is no way in the protocol to prevent this.
It‘s not just about the data—which is bad enough but as you said they could just write a crawler to get at it. The question is why would they want to federate and why now? Meta being Meta the most likely reasons are terrible for the fediverse and it reminds me very much of Google and xmpp. I saw a really good writeup on this yesterday: https://ploum.net/2023-06-23-how-to-kill-decentralised-networks.html
Meta does some interesting open source work, extra hands on fediverse open source might be reasonable.
We shan't bend the knee!
I’m surprised by all the negativity. Is it not a good thing Meta is going to use open standard instead of a proprietary one?