Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Bypassing Safari 17's advanced audio fingerprinting protection

fingerprint.com

Post reply on HN
Print view View original

261–266 of 266 posts

Re: Bypassing Safari 17's advanced audio fingerprinting protection

#261

Post by Zuiii »

Spivak wrote: post #255
zuhsetaqi wrote: post #236

Earlier quoted context omitted.

How is that difficult? Anything that is stored to recognise a user on two different devices/sites is fingerprinting.

Oh no my session cookie! Remember Me On This Device: Not today Satan! Use code LINUS for immediate jail-time. Find My iPhone — You mean find my digital privacy regulator. I think the only way you're gonna swing it legally is by intention.

What's key here is consent. (the real kind, not the EULA kind)

If you knowingly opt into being identified (like ticking an unticked "remember me" box that clearly explains the precise purpose of the identification) then it is okay.

If some asshat decides to do it without your informed, clear, and uncompelled consent, throw the fucker in the slammer.

It's not that complicated.

Re: Bypassing Safari 17's advanced audio fingerprinting protection

#262

Post by NikkiA »

nox101 wrote: post #251
zuhsetaqi wrote: post #237

Earlier quoted context omitted.

A "sandbox" that can freely send anything it wants to any computer connected to the internet

confused why you'd think a native app has any less restrictions on sending anything it wants to any computer connected to the internet.

Well, my application level firewall prompts me if audacity attempts to connect to the internet, and I refuse it. Refusing firewall access to a web browser renders it useless for every website, not just a 'audacity as a service' site.

Re: Bypassing Safari 17's advanced audio fingerprinting protection

#263

Post by JohnFen »

cedws wrote: post #225
chii wrote: post #110

Earlier quoted context omitted.

browsers should come with a default software renderer, and behave like the mic and camera where the site will require user permission to release the hardware GPU render path.

What's the point? The capabilities of browsers are so vast they'll just find other ways to fingerprint. Privacy in browsers is a lost cause. It's a 30+ year old technology that has become ridiculously bloated in scope, with privacy and security only considered as an afterthought.

Entirely this. It's a huge part of why the portion of the web I'm willing to go to gets smaller and smaller over time.

Re: Bypassing Safari 17's advanced audio fingerprinting protection

#265

Post by dartos »

BenjiWiebe wrote: post #259
dartos wrote: post #248

Earlier quoted context omitted.

Responsive sites could’ve been done with css a decade ago too. IIRC Even IE6 has some support for flexbox and media queries. but people would rather pick up react and have a pile of js do it for them.

IE6 was EOL before flexbox was a thing, according to Wikipedia.

I may be thinking IE11 then.

Re: Bypassing Safari 17's advanced audio fingerprinting protection

#266

Post by wdr1 »

zuhsetaqi wrote: post #236
wdr1 wrote: post #123

Earlier quoted context omitted.

Defining fingerprinting in a legal terms is fairly difficult. Most regulators would also likely consider fingerprinting for certain use cases as acceptable. E.g., detecting abuse, fraud, CP, etc.

How is that difficult? Anything that is stored to recognise a user on two different devices/sites is fingerprinting.

So if you make that illegal, you just made basic website logins illegal.

Again, it's really hard to define what we all "mean" in legal terms.

Post reply on HN