this post was submitted on 23 Dec 2025
166 points (96.6% liked)

Technology

77899 readers
2395 users here now

This is a most excellent place for technology news and articles.

Our Rules

  1. Follow the lemmy.world rules.
  2. Only tech related news or articles.
  3. Be excellent to each other!
  4. Mod approved content bots can post up to 10 articles per day.
  5. Threads asking for personal tech support may be deleted.
  6. Politics threads may be removed.
  7. No memes allowed as posts, OK to post as comments.
  8. 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.
  9. Check for duplicates before posting, duplicates may be removed
  10. Accounts 7 days and younger will have their posts automatically removed.

Approved Bots

founded 2 years ago
MODERATORS
L3s@lemmy.world
enu@lemmy.world
technopagan@lemmy.world
L4s@lemmy.world
L3s@hackingne.ws
L4s@hackingne.ws
166
How VPNs really work: Protocols, safety and myth - Sentient Rant (sentientrant.com)
submitted 1 day ago by sentientRant@lemmy.world to c/technology@lemmy.world
30 comments fedilink hide all child comments
 

VPNs are often sold as a “privacy silver bullet,” but that framing causes more confusion.

A VPN does not make you anonymous.

It does not stop cookies, logins, browser fingerprinting, or payment-based identification.

What a VPN actually does is much narrower and more technical:

  1. It encrypts your internet traffic in transit
  2. It prevents your ISP or local network from seeing which destinations you connect to
  3. It makes websites see the VPN server’s IP instead of your real one
  4. That’s privacy at the network level, not identity hiding.

I wrote a detailed blogpost. Check it out.

you are viewing a single comment's thread
view the rest of the comments
[–] nyan@lemmy.cafe 1 points 1 hour ago

Attempting to defeat browser fingerprinting (you can never be 100% sure you've defeated everything) without TOR is kind of an advanced subject, yeah, and one of which I have only shallow knowledge. A lot of it is Javascript-dependent, so allowing Javascript only on a whitelist basis should help (but is too tedious for a lot of people). Deliberately pissing in the pool by varying prominent identifiers like the User-Agent string should help. Canvas poisoning. Specialist browser extensions, some of which may be more effective than others. Running the blandest default-settings browser possible in the blandest possible default-settings environment (a container or live media inside a VM) could conceivably cause you to vanish into the noise, but may be highly inconvenient.

It's worth considering who is likely to be interested in going to the trouble of browser fingerprinting in the first place. Small players have little use for the information and aren't likely to accumulate enough to sell it for much money. So the problems are going to come from ad networks, large digital networks like Google and Meta/Facebook, possibly CDNs and service providers like Shopify if they think it's worth their while, maybe some governments, and completely dishonest scam sites that think any money is good. Some of these can be avoided altogether if you work at it.