Łukasz Olejnik, a privacy researcher, writes about browser privacy, web standards, GDPR, tracking, and security of web APIs.
HN commenters link it for privacy analyses of Web Bluetooth, Chrome login changes under GDPR, and a tracking prevention vulnerability.
This is starting to remind me of when Intelligent Tracker Prevention(tm) was released and instead was a super cookie leaking history. http://blog.lukaszolejnik.com/curious-case-of-privacy-vulnerability-in-intelligent-tracking-prevention/
I'd be much more comfortable with Apple being Privacy, Inc. if they kept their commitment to it, too often it looks like engineers got overrode by marketing. It's v unlikely a privacy engineer signed off on something, with so many side channels, with real world consequences, compromising a billion + iOS devices
Brave indeed does block WebBluetooth by default, but it can be turned on by the user using flags.
It's by no means a new feature, but the privacy concerns outlined in this post are still valid 10 years later: https://blog.lukaszolejnik.com/w3c-web-bluetooth-api-privacy/
http://info.iapp.org/dz0uBmdUa20MA00Z5o100E0 redirects to:
https://blog.lukaszolejnik.com/am-i-logged-in-or-not-gdpr-case-study-on-the-example-of-chrome-browser-change/
Please update the submission URL.
Real URL in case you don't allow JavaScript for the redirect: https://blog.lukaszolejnik.com/am-i-logged-in-or-not-gdpr-case-study-on-the-example-of-chrome-browser-change
Your url does not work for me (404), this one does: https://blog.lukaszolejnik.com/am-i-logged-in-or-not-gdpr-case-study-on-the-example-of-chrome-browser-change/
Url changed from https://blog.lukaszolejnik.com/solving-phishing-is-not-simple-can-anti-phishing-training-make-it-even-worse/, which points to this.