The US Customs and Border Protection (CBP) has just developed a tool, called Babel X, which links social media posts to citizens' Social Security number and location data.
It's not just abuse by surveillance capitalists we must concern ourselves with. It's also governments.
This is all the more reason that people must not only examine how they use social media, but consider owning their social media presence as well.
Never has the idea of a #Fediverse been so important.
https://www.vice.com/en/article/m7bge3/dhs-uses-ai-tool-babel-x-babel-street-social-media-citizens-refugees
@socialmedianews@venera.social
But how does Fediverse prevent that?
Seems like their system would be just about as effective here as it vacuums up the content ActivityPub is broadcasting.
@socialmedianews
@volkris @nyquildotorg
The fediverse is very different from corporate/government social media. Fediverse SW makes almost no attempt to identify people and their accounts. If you want to associate one of your accounts to your real name and verify against your domain, you are welcome, but the amount of data you expose is mostly up to you.
Contrast this with centralized social media with identity management and verification systems that use browser and device fingerprinting and cookies.
But the distributed design of Fediverse requires it to broadcast content in ways that make it easier for third parties to vacuum content.
Not only is it still possible for instances to set up fingerprinting and cookies, but there's the new vector of all of the connectivity stuff normally inside a centralized system being broadcast to the world as it has to traverse between instances.
@volkris @nyquildotorg
I am unaware of any fedi projects that have implemented advanced identification management. It is possible to develop this, but I suspect few people would join such instances using it.
ActivityPub was designed with the instance focus, so that ship has sailed. A user focus is just not in the cards for this system, having already been passed on.
Sure, if you only interact with yourself on your own instance.
But the moment you federate, you're trusting the instance owners of those you federate with.
@nyquildotorg
@nyquildotorg
That article was about web3 and its blockchain based connections to instances. The fediverse is currently not linked by any blockchain that enables centralization. Moxie did not think people wanted to run their own servers, but it has become easier by the day since this was written.
@volkris
@Bernard @volkris The blockchain stuff is irrelevant this discussion.
The important part of that piece is the history of how email went from federated to just a handful of giant players, driven not by the actions of those companies, but because users simply didn't want to bother with hosting stuff, prefer to pay for it to "just work."
@nyquildotorg
The fediverse encourages and protects anonymity more than any social media platform. An instance or server operator can see a little more information about accounts such as IP addresses used to connect, but without more advanced ID management, identification is difficult.
If your endpoint device is infected with malware that scans and tracks your activity, you are screwed regardless which is what this article was mainly discussing.
@volkris
Of course. It is the same as when you send an email to someone on another mail server you do not control.
@nyquildotorg