this post was submitted on 28 Jul 2026
553 points (96.9% liked)
Technology
86735 readers
3278 users here now
This is a most excellent place for technology news and articles.
Our Rules
- Follow the lemmy.world rules.
- Only tech related news or articles.
- Be excellent to each other!
- Mod approved content bots can post up to 10 articles per day.
- Threads asking for personal tech support may be deleted.
- Politics threads may be removed.
- No memes allowed as posts, OK to post as comments.
- Only approved bots from the list below, this includes using AI responses and summaries. To ask if your bot can be added please contact a mod.
- Check for duplicates before posting, duplicates may be removed
- Accounts 7 days and younger will have their posts automatically removed.
Approved Bots
founded 3 years ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments



Are those things like mouse jigglers? It seems those would only work if enough people use them to create a blanket of obscurity.
Isn't there any hardware that just... doesn't log this stuff in a way that's retrievable by backend server scripts?
Analogy
Imagine a restaurant where diners place orders through a discreet slot on the kitchen door.
Now, the diner adds a bizarre request: “Please serve the food, but I never want you to know you ever cooked it.” In practice, the chef can’t fulfill this—once he’s touched the ingredients and used the stove, his hands are inevitably stained, and the kitchen’s heat tells the story. Likewise, when a web user asks a server to fetch data, the server must process the request, so it inevitably knows it handled that request, even if it can’t tie it back to the individual’s identity.
Ad‑blockers, cookies, IP addresses, user‑agents, and browser signatures are like the various “fingerprints” a diner might leave on the restaurant’s doorstep:
Just as no chef can truly be blind to the fact that he cooked a dish, a web service inevitably knows it processed a request, and the “fingerprints” left behind (cookies, IP, user‑agent, etc.) let it—or any intermediary—recognize or track the diner unless the diner takes strong steps (like using a cloak or wiping the floor) to hide those traces.
https://f-droid.org/packages/com.fauxx.full
I think that's an overly reductive analogy. Of course the backend web server knows what it processed on its own hardware, but it doesn't need to know the IP that the request originated from (if using a VPN) and it certainly doesn't need to fingerprint the browser with hidden scripts.
Likewise, the browser probably doesn't even need to make that information available to those scripts. There are extensions to block some of it, but apparently not all. And blocking some things can break some websites.
But there's no reason the chef in the back should be running a forensic analysis on the fingerprints on the ticket, the footprints on the dining room floor, or the crumbs swept up at the end of the day. And if you suspect that they will do this, then it should take be overly complicated to wear gloves, and maybe some boot covers, and possibly a full hazmat suit if you're really worried about dropping crumbs and dander.
Not that all that should be necessary, because it shouldn't be standard practice for web servers to collect all this data to begin with...