It’s excruciatingly obnoxious to have to rely on third party sources for what should be a first-party feature.
Like, I select all and then search a query. “Oh no, nobody on your server used a third party service to find it, so you won’t see it here.”
Like, how short-sighted is that, really? If I search for a string in the ‘all’ servers, I should have a list of ‘all’ the servers containing that string.
It’s a really simple concept. Not sure why this post even has to be made, but I’m wondering if there’s something I can do to make these ‘features’ more intuitive.
How does posting and reading posts work - and how do you know that nobody tracks their users? I was under the assumption that admins of a node have totals access to data going in/out/through their instance.
Just have a look at the data accessed by the apps, both stores display them. It’s something else than the Reddit app.
There might be some data agregation on the server side indeed, but compared to the ads promotion machine than Reddit has become (and even announced openly, with subreddits now being platform to promote products), it’s a completely different story.
What app? As far as I’m concerned there’s no reason to believe that fediverse users aren’t tracked. Probably not all, but where there’s users interacting with each other discussing different subjects there’s money to be made, and data to sell to AI companies for training.
https://lemmy.world/post/2807814?scrollToComments=true
Sort by Top
The app works between an instance/server and the user. This does not affect what the admins/owners of an instance/server can track.
It’s already better than what Reddit does with its app then.
If you want to improve your privacy, browse Lemmy using a VPN and a fingerprint protected browser such as Mullvad browser, and you’re pretty much set against potential data collection from our instance admin. You can even share your account with a few other people to make your ghost profile harder to populate.
I’m not sure you understand how the fediverse works on protocol level or how posts are stored. None of what you suggest will protect you. There is no way you can protect yourself from tracking by those with access to raw data.
I’m indeed not sure we are talking about the same thing.
You are talking about tracking the data and selling it to AI for training.
I don’t even know why AI companies would bother with buying that data when they can just parse that information directly from the website and then train their model on it.
I was talking about selling user profiles to advertising companies willing to reach specific potential customer audiences. In that scenario, the measures I explained prevent your profiling.
I’m talking about tracking and profiling in general. This is possible by crawling to a certain extent, but it’s 100% possible when you have the data of who’s voting up/down on what, and what posts they are shown and how they interact with them.
This is possible from app or website, and that part can be mitigated somewhat by the stuff you proposed. But if you control to the code and database you have 100% access to this information. How you interact with posts are very interesting for AI training and analysis, similar to what Cambridge Analytica had a great run at using Facebook data.