News for hackers. Stuff that matters.
Re:The privacy nightmare of browser fingerprinting by drnick1 on Saturday November 22, 2025 @01:14PM (#46016868)
Firefox w/ the Arkenfox user.js is probably as good as it gets in terms of privacy. By default, this config burns cookies on exit, standardizes the time zone to UTC, spoofs the canvas fingerprint, and does other helpful things. Basically, it makes Firefox expose the same information as the Tor browser.

In addition, I block most known advertizing/tracking domains at the DNS level (I run my own server, and use Hagezi's blacklists).

Finally, another suggestion would be to block all third party content by default using uBlock Origin and/or uMatrix. This will break a lot of websites, but automatically rules out most forms of tracking through things such as fonts hosted by Google, Adobe and others. I manually whitelist required third party domains (CDNs) for websites I frequently visit.

Re:The privacy nightmare of browser fingerprinting by hilbert42 on Saturday November 22, 2025 @04:17PM (#46018358)
"This will break a lot of websites, but automatically rules out most forms of tracking…"

Whether one breaks a lot of websites or not depends on the type of user one is. People who regularly use the Google ecosystem, Amazon and Social Media etc. cannot afford to break sites for obvious reasons, they too are those that websites are most interested in tracking and fingerprinting.

Those who use the web in the way advertisers and Big Tech intend users to use it are the most vulnerable, they're the ones who most need protection.

I break websites regularly but it doesn't worry me, I browse with the premise that there are more websites on the internet than I'll ever be able to visit and if I break sites or are blocked by paywalls then there are usually alternatives and workarounds.

But then I'm not a typical user, I block ads, I usually browse with JS off, kill cookies, use block lists, use multiple browsers (there are six on this deGoogled, rooted phone), browse from multiple machines—Windows, Linux and use multiple ISPs. Also, I've no Social media or Google accounts and rarely ever purchase stuff online. Internet access is via dynamic IP addresses and routers are rebooted often. There's more but you get the picture.

I assume browsing sans JS makes me a first-class target for fingerprinting and that websites know about me but it doesn't matter. Whatever I'm doing seems to work, over the years I've had very little trouble doing everything on the web that I want to do. Clearly I'm of little interest to advertisers and I never see ads let alone targeted ones. I used to use uBlock Origin but I don't bother now as browsing sans JS is just so effective at blocking ads.

I'm lucky in the fact that I use no service that would benefit from fingerprinting me. Whilst my web browsing is atypical of most users I reckon many could benefit by being more proactive—using multiple machines, browsers, ISPs etc.—to disrupt the outflow of personal data. For example, this is being written on a rooted Android using Privacy Browser from F-Droid sans JS and with block lists. If I really need to go to a site where JS is required, I can simply hit a toggle and turn on JS or alternatively use another browser.

Re:The privacy nightmare of browser fingerprinting by codedokode on Saturday November 22, 2025 @01:23PM (#46016971)
Does it hide GPU name that is exposed via WebGL/WebGPU? Does it hide internal IP address, available via WebRTC?

> block all third party content

It's not going to work, because the fingerprinting script can be (and is often served) from first-party domain.

Also imagine if browser didn't provide drawing API for canvas (if you would have to ship your own wasm rendering library). Canvas would become useless for fingerprinting and its usage would drop manyfold. And the browser would have less code and smaller attack surface.

Re:The privacy nightmare of browser fingerprinting by drnick1 on Saturday November 22, 2025 @01:31PM (#46017036)
> Does it hide GPU name that is exposed via WebGL/WebGPU? Does it hide internal IP address, available via WebRTC?

My GPU is reported as simply "Mozilla" by https://abrahamjuliot.github.io/creepjs/.

The number of cores is also set to 4 for everyone using this config and/or Tor.

> It's not going to work, because the fingerprinting script can be (and is often served) from first-party domain.

This may be true, but allowed third party content makes it trivially easy for Google and others to follow people around the Internet through fonts delivery systems among others.

Re:The privacy nightmare of browser fingerprinting by tempest_ on Saturday November 22, 2025 @03:52PM (#46018149)
I had forgotten I was running Ublock origin / Privacy Badger / Ghostry so I was a bit confused with the results from that site.

I think it is Ghostry that is faking the responses but I still have a pretty unique fingerprint according to https://abrahamjuliot.github.io/creepjs/

Re:The privacy nightmare of browser fingerprinting by ifh-hn on Saturday November 22, 2025 @06:51PM (#46019419)
Isn't ghostry compromised? Having been bought out by an ad company?
Re:The privacy nightmare of browser fingerprinting by nativeit on Saturday November 22, 2025 @08:27PM (#46019905)
As near as I can tell, it’s always been owned by Cliqz, who produced some privacy-focused browsers (named Dawn or Lumen) and a search engine (Tailcat) that was ultimately purchased by Brave. The whole thing is majority owned by a German media group, Hubert Burda Media, and while its missions towards increased privacy seem to be sincere, I don’t know if I’d trust them implicitly.

All that said, the main project looks to be open sourced under a GPL3 license, so distrust and verify: https://github.com/ghostery

Re:The privacy nightmare of browser fingerprinting by tempest_ on Saturday November 22, 2025 @10:36PM (#46020552)
Honestly I did not know.

I have had it installed so long I don't even remember when I did it.

Ill look more into it and perhaps re-evaluate

Re:The privacy nightmare of browser fingerprinting by dminuoso on Saturday November 22, 2025 @01:39PM (#46017103)
If I infiltrate someone else’s computer, secretly run code in order to to exfiltrate data I risk prison time because objectively it seems to satisfy criminal laws over where I live.

How do prosecutors in any modern country/state not charge this behavior when done by a website owner?

Re:The privacy nightmare of browser fingerprinting by gruez on Saturday November 22, 2025 @01:53PM (#46017222)
The difference is that there's implied consent to run arbitrary (albeit sandboxed) code when you visit a website. Moreover it's not the website causing the code to be executed, it's your browser. Otherwise if the bar is "code is being run but the user doesn't know about it", it would lead to either any type of web pages with javascript being illegal (or maybe without javascript, given that CSS turing complete), or a cookie banner type situation where site asks for consent and everyone just blindly accepts.
Re:The privacy nightmare of browser fingerprinting by mh- on Saturday November 22, 2025 @02:50PM (#46017666)
> if the bar is "code is being run but the user doesn't know about it",

.. would lead to all modern electronics being illegal, not just web pages with javascript.

Re:The privacy nightmare of browser fingerprinting by nativeit on Saturday November 22, 2025 @08:30PM (#46019921)
I guess it’s fortunate that this quote only includes a portion of the assertion they’re making. What happens when you include the rest?
Re:The privacy nightmare of browser fingerprinting by bandrami on Saturday November 22, 2025 @05:00PM (#46018629)
> any type of web pages with javascript being illegal

Inshallah

Re:The privacy nightmare of browser fingerprinting by geocar on Sunday November 23, 2025 @01:48AM (#46021353)
I suppose it depends on what you mean by "modern"

In Europe we have the GDPR which does exactly this

Re:The privacy nightmare of browser fingerprinting by dminuoso on Sunday November 23, 2025 @06:59AM (#46022868)
The GPDR is not criminal law. But ignoring that, regulators barely pursue GPDR violations.

Consider the swaths of dark patterns surrounding cookie terror banners. The GPDR language is extremely clear that none of them are legal, but virtually nobody is ever punished.

Re:The privacy nightmare of browser fingerprinting by geocar on Sunday November 23, 2025 @10:26AM (#46024259)
> The GPDR is not criminal law

While the GDPR does not directly prescribe prison sentences, it absolutely enables countries to establish criminal offences for severe data protection violations, and they will clearly extradite!

https://ico.org.uk/about-the-ico/media-centre/news-and-blogs...

https://ico.org.uk/about-the-ico/media-centre/news-and-blogs...

> But ignoring that,

No don't ignore that. When you're so completely wrong about the first thing you say, everything that follows is going to be even more wrong.

> Consider ... cookie ... banners. The GPDR language is extremely clear that none of them are legal

You are confusing the ePrivacy directive (2002/58/EC) with the GDPR (2016/679).

Re:The privacy nightmare of browser fingerprinting by kachapopopow on Saturday November 22, 2025 @01:44PM (#46017151)
All javascript based anti-fingerprinting is detectable and is also a major source of uniqueness!
Re:The privacy nightmare of browser fingerprinting by vorticalbox on Saturday November 22, 2025 @03:23PM (#46017926)
Sure but if you are always unique for every website then you can’t be tracked overtime.
Re:The privacy nightmare of browser fingerprinting by HumanOstrich on Saturday November 22, 2025 @05:07PM (#46018703)
They meant a signal of uniqueness for your setup that could still assist with tracking, not being unique for every site.
Re:The privacy nightmare of browser fingerprinting by alcide on Saturday November 22, 2025 @01:21PM (#46016958)
Orion Browser (Kagi Product) prevents fingerprinters from running by default.

https://help.kagi.com/orion/privacy-and-security/preventing-...

Re:The privacy nightmare of browser fingerprinting by ashman5 on Saturday November 22, 2025 @03:31PM (#46017991)
Orion browser is also capable of running uBlock Origin (not Lite) on iOS.
Re:The privacy nightmare of browser fingerprinting by codedokode on Saturday November 22, 2025 @01:37PM (#46017088)
How do they reliably detect fingerprinting? Did they solve the Halting Problem? Sounds fishy.
Re:The privacy nightmare of browser fingerprinting by gruez on Saturday November 22, 2025 @01:44PM (#46017144)
>The only efficient protection against fingerprinting is what Orion is doing — preventing any fingerprinter from running in the first place. Orion is the only browser on the market that comes with full first-party and third-party ad and tracking script blocking, built-in by default, making sure invasive fingerprinters never run on the page.

sounds like they block "known" fingerprinting scripts and call it a day.

Re:The privacy nightmare of browser fingerprinting by jorvi on Saturday November 22, 2025 @04:15PM (#46018338)
> Orion is the only browser on the market that comes with full first-party and third-party ad and tracking script blocking

I love Kagi, but that is a laughable statement. Brave has been offering ad and fingerprint blocking for years now. The reason why they don't have full first party blocking ("aggressive" mode blocking) on by default is because it tends to break things.

Re:The privacy nightmare of browser fingerprinting by 0xy on Saturday November 22, 2025 @02:53PM (#46017702)
This makes you inherently trackable, ironically. No trace is a massive trackable attribute, since almost nobody is untraceable.
Re:The privacy nightmare of browser fingerprinting by RamRodification on Saturday November 22, 2025 @04:14PM (#46018328)
Hey look it's that invisible guy again!
Re:The privacy nightmare of browser fingerprinting by nativeit on Saturday November 22, 2025 @08:33PM (#46019932)
This is also covered in the article. I appreciated the analogy they used: You can put on a ski mask when you go to the mall, and it will conceal your identity, but you will also be instantly suspicious to everyone around you, and will likely be asked to leave most of the stores you try to visit.
Re:The privacy nightmare of browser fingerprinting by codedokode on Sunday November 23, 2025 @06:04AM (#46022517)
This is only because there are only 0.001% of people using anonymizers. If you are a minority with specific requirements, you are shown the door almost in any case, not only on the Internet.
Re:The privacy nightmare of browser fingerprinting by mmooss on Saturday November 22, 2025 @09:41PM (#46020265)
To ask the obvious question: Doesn't blocking fingerprinters itself fingerprint the browser.

(Also, what is a 'fingerprinter'? Isn't it something that runs server-side, out of reach of the browser, based on data collected?)

Re:The privacy nightmare of browser fingerprinting by h33t-l4x0r on Sunday November 23, 2025 @02:24AM (#46021503)
No it's usually a javascript script that does weird things like drawing strings on an invisible canvas and sends it back to the server. I'm wondering if a browser extension that intercepts those payloads and randomizes them with other people's payloads is what's called for here.
Re:The privacy nightmare of browser fingerprinting by 0xy on Saturday November 22, 2025 @02:52PM (#46017691)
As someone who utilizes these tools for anti-fraud purposes, Firefox is just as trackable if not more trackable than Chrome (especially because you stand out by using a niche browser in the first place).

Firefox exposes a massive amount of identifiable information via canvas, audio device and feature detection methods. There's also active methods to detect private windows, use of the developer console and more.

Re:The privacy nightmare of browser fingerprinting by vpShane on Saturday November 22, 2025 @03:08PM (#46017816)
Of course. There's data where there isn't data.

-make client load something

-client doesn't load it

-add.fingerprint.point(client,'doesnltloadthings',1)

-detect if client does something only a certain browser does

-client does it

-add.fingerprint.point(client,'doesthisbrowsderthing',1)

-window was resized/moved, send a websocket snitch to the backend

- keep a consistent web socket open, or fetch a backend-api call for updates on X events - more calls are made, means user is probably scrolling, inject more things/different things.

I see some js obfuscators out there where I look at the js file and it's all mumbo jumbo.

It is indeed a privacy nightmare, where whatever we do feeds the algorithms to aide in making other people do things.

But it's also used in network security, organizations etc. Staff/employees will use the system a certain way, if something enters it without the behaviors, it's detectable. I assume that's what you mean in anti-fraud.

Sad part is we don't know what the data is ever used for, and it's often bought and sold and the cycle repeats.

Re:The privacy nightmare of browser fingerprinting by zelphirkalt on Sunday November 23, 2025 @05:47AM (#46022403)
In the end all this shit we have to deal with is probably 99% used for deciding which ads to show you, which we are gonna block anyway, and it's all a complete and utter waste of computing power and electricity. This is how big tech "makes the world a better place" apparently.
Re:The privacy nightmare of browser fingerprinting by pteraspidomorph on Sunday November 23, 2025 @02:31AM (#46021537)
If you enable privacy.resistFingerprinting in about:config I believe instead of trying to prevent fingerprinting entirely, it's supposed to make things annoying for the fingerprinters by regularly changing the various spoofed factors.
[dead]
Re:The privacy nightmare of browser fingerprinting by ykonstant on Sunday November 23, 2025 @02:16AM (#46021466)
Unfortunately, recently more and more sites fail to work with Tor Browser. Notably, I am informed by people who are not me, Anna's archive and libgen.
Re:The privacy nightmare of browser fingerprinting by integralid on Sunday November 23, 2025 @03:48AM (#46021852)
The sites block Tor, not fail to work with Tor browser itself. I know this is a meaningless distinction for end user.

In theory you could use Tor browser with Tor stripped (I heard this is what mullvad browser is?) or go tor-then-proxy (this is what I often do, because I sometimes use whonix at work). I don't know about libgen or Anna's archive, I don't use them.

Re:The privacy nightmare of browser fingerprinting by Lio on Monday November 24, 2025 @01:56AM (#46031123)
Why shouldn’t you care and how is the issue with fingerprinting overblown?
Re:The privacy nightmare of browser fingerprinting by capitainenemo on Saturday November 22, 2025 @04:26PM (#46018424)
unfamiliar with the Arkenfox user.js but are any of these things that are beyond what firefox enables out of the box if you turn on privacy.resistFingerprinting ? Because what you describe seems to be all stuff it does just by flipping flag.
Re:The privacy nightmare of browser fingerprinting by drnick1 on Saturday November 22, 2025 @11:39PM (#46020797)
Arkenfox does far more than that, just look at the user.js. Among others, it spoofs the time zone, number of cores, window size and many other attributes that assist fingerprinting. It basically mimics the settings of the Tor browser.
Re:The privacy nightmare of browser fingerprinting by capitainenemo on Sunday November 23, 2025 @03:53PM (#46027226)
privacy.resistFingerprinting = true is basically activating most of the Tor browser features in baseline Firefox. That's why it is turned off by default. It does all the things you listed above only at a lower level than a user script. It's been in Firefox for over a decade.

https://www.ghacks.net/2018/03/01/a-history-of-fingerprintin...

The flag was in fact designed to control the activation of the Tor browser uplift features, and reduce maintenance issues. That way the Tor browser could pretty much just be Firefox with certain flags turned on.

Re:The privacy nightmare of browser fingerprinting by samtheprogram on Saturday November 22, 2025 @05:12PM (#46018750)
There's no point unless a critical mass of people use these tools. You will be the only one on your IP address using this configuration of masked fingerprinting, which is itself a fingerprint.

That's also why it's indeed useful when using Tor, because you're not identified by your base IP.

Unless we make this part of the culture, you have basically 0 recourse to browser fingerprinting except using Tor. Which can itself still be a useful fingerprint depending on the context.

EDIT: I'll add that using these tools outside of normal browsing use can be useful for obfuscating who's doing specific browsing, but it should be emphasized that using fingerprinting masking in isolation all the time is nearly as useful as not using them at all.

Re:The privacy nightmare of browser fingerprinting by cortesoft on Saturday November 22, 2025 @06:21PM (#46019243)
Basically the XKCD license plate comic: https://xkcd.com/1105/
Re:The privacy nightmare of browser fingerprinting by nativeit on Saturday November 22, 2025 @08:13PM (#46019835)
Has anyone wrote software that automatically surfaces the relevant XKCD comic for every article this happens under?

I’d like a feature in my HN reader that sticks a red button at the bottom anytime XKCD has already made the points I’m reading.

Re:The privacy nightmare of browser fingerprinting by faidit on Saturday November 22, 2025 @10:27PM (#46020504)
We should go further and make an AI agent that creates counterfeit XKCD comics of dubious quality for literally every scenario.
Re:The privacy nightmare of browser fingerprinting by SV_BubbleTime on Saturday November 22, 2025 @11:19PM (#46020715)
Randal had a long career of good takes, until around 2016 when they stopped being objectively good.

I’m not kidding at all, that my guess is he was doing drugs and stopped.

Re:The privacy nightmare of browser fingerprinting by koolba on Saturday November 22, 2025 @11:49PM (#46020847)
> Randal had a long career of good takes, until around 2016 when they stopped being objectively good.

Specifically it was at this point in 2016: https://xkcd.com/1756/

> I’m not kidding at all, that my guess is he was doing drugs and stopped.

I don’t know if he stopped or started, but something changed.

Re:The privacy nightmare of browser fingerprinting by franga2000 on Sunday November 23, 2025 @01:26AM (#46021273)
A person used their relatively large platform to tell people that they don't support a crazy lunatic millionaire running the world's most powerful country? How scandalous!

In the USA, 2016 and onwards wasn't "just an election". It was something between a mildly harmful establishment candidate or a useless new face on one side, and "holy fucking shit are we actually letting this deranged wannabe monarch run for office?!?" on the other.

Give the man a break, it was (the start of) a crazy time, I'm actually surprised more creators didn't do something like this. If anything, it was barely even a political statement, more of a "hey fellow dems, go vote!" type thing.

Re:The privacy nightmare of browser fingerprinting by sdoering on Sunday November 23, 2025 @05:38AM (#46022345)
Couldn’t have said it better. But hey, they made their bed…
Re:The privacy nightmare of browser fingerprinting by cortesoft on Sunday November 23, 2025 @05:48PM (#46028145)
Coming our against a candidate that literally said the words "grab them by the pussy" is a bad thing?
Re:The privacy nightmare of browser fingerprinting by SV_BubbleTime on Monday November 24, 2025 @09:46AM (#46034709)
No, but not understanding your audience, not being able to not divide your fanbase for absolutely no reason, and doing all that for Hillary Clinton who history will not at all be kind to…

His traffic and hot takes dropped and his influence declined to almost nothing… maybe those things aren’t unrelated?

Re:The privacy nightmare of browser fingerprinting by naniwaduni on Sunday November 23, 2025 @01:31AM (#46021293)
1357 (2014-04-18) is pretty bad.

(Bonus points for the alt-text argument being isomorphic to nothing-to-hide.)

Re:The privacy nightmare of browser fingerprinting by SV_BubbleTime on Sunday November 23, 2025 @09:26PM (#46029707)
He was effectively years early to the “if you don’t like how twitter is run, build your own <smug face>” interesting how that argument isn’t used anymore.
Re:The privacy nightmare of browser fingerprinting by wizzwizz4 on Sunday November 23, 2025 @04:21AM (#46021994)
As far as "obligatory xkcd" is concerned: 3154, 3155, 3159, 3160, 3162, 3165 and 3167 are all relevant. (I've found myself citing 3155 a lot, in attempts to deradicalise cranks: it sometimes works, if I can convince them to quit ChatGPT cold-turkey.)

It's fine to like the comics before around 2016, and dislike the ones afterwards, but there's nothing objective about that. Various people have put forward various thresholds for when xkcd "stopped being good", but ultimately it boils down to a combination of what TV Tropes would call "Tone Shift" and "They Changed It, Now It Sucks!".

Re:The privacy nightmare of browser fingerprinting by sdoering on Sunday November 23, 2025 @05:40AM (#46022354)
Wow. Not liking their political views equals doing drugs.

Must be an interesting place, that originates these "arguments".

Re:The privacy nightmare of browser fingerprinting by einsteinx2 on Sunday November 23, 2025 @03:03PM (#46026819)
I think you misread. They said the opposite: that he was taking drugs and his takes were good, then he stopped taking drugs and now they’re bad.

I’m not saying I agree or that I even think his takes have gotten worse, just clarifying what the other poster said.

Re:The privacy nightmare of browser fingerprinting by zelphirkalt on Sunday November 23, 2025 @05:00AM (#46022180)
You can and should be using a good VPN to make the masked fingerprint and IP address non-unique.
Re:The privacy nightmare of browser fingerprinting by thrw888 on Sunday November 23, 2025 @11:20AM (#46024655)
I have packed ff with arkenfox js into container and maybe a handful other people use it https://github.com/grzegorzk/ff_in_podman. Still, most likely the IP address alone is probably the strongest part of fingerprint vector Maybe instead it would be better to have very different vector each time?
Re:The privacy nightmare of browser fingerprinting by DavideNL on Sunday November 23, 2025 @12:18PM (#46025232)
> "There's no point unless a critical mass of people use these tools"

That's what Mullvad Browser attempts to solve i guess:

https://mullvad.net/en/browser

Re:The privacy nightmare of browser fingerprinting by DeathArrow on Saturday November 22, 2025 @05:21PM (#46018822)
There is also server side fingerprinting like JA4+ and others. Also, if you somehow evade fingeprinting, you have to prepare yourself to solve some very slow Google and Cloudflare captchas.
Re:The privacy nightmare of browser fingerprinting by bradleyankrom on Saturday November 22, 2025 @09:05PM (#46020085)
Privacy tax, sigh
Re:The privacy nightmare of browser fingerprinting by mmooss on Saturday November 22, 2025 @09:38PM (#46020254)
> Basically, it makes Firefox expose the same information as the Tor browser.

Is it based on the Tor browser?

Some solutions, like Tor browser or GrapheneOS, are engineered for the purpose.

Some free online tools are an aggregation of ideas from social media and someone's personal understanding. These solutions can have limited benefits or be worse than the problem. Many settings don't work as expected, there are unintended consequences (such as making the browser more unique and easier to fingerprint), unusual combinations of settings can have unintended consequences or break things (Mozilla can't test every combination of about:config settings).

Re:The privacy nightmare of browser fingerprinting by potato-peeler on Sunday November 23, 2025 @04:53AM (#46022134)
Firefox already provides this feature in about:config using resist fingerprint - https://support.mozilla.org/en-US/kb/resist-fingerprinting
Re:The privacy nightmare of browser fingerprinting by soulofmischief on Monday November 24, 2025 @11:40AM (#46035981)
You could just use `privacy.resistFingerprinting` in Firefox, tweak a few other settings, install uBlock Origin/uMatrix and you get the same thing, unless I'm missing something?