I visited the page once on my Android using my HN app's built-in webkit browser, where it displayed some interesting stats like the location, the battery level, ISP, etc. I opened the same link in Firefox Android with uBlock Origin installed, and got no hardware stats other than the kernel, no software stats, and no IP. My takeaway from this is to NEVER use an app that uses Webkit. I'm not sure if that was the intend…
My takeaway would've been; use some sort of protection, like NoScript, uBlock, etc. The choice of web-browser engine seems less important when you globally allow javascript or other similar capabilities.
Show HN: What every browser knows about you
61–70 of 209 posts
Re: Show HN: What every browser knows about you
#62OS X 10.11.4: Safari 9.1 : Minimal HW/SW detection, No social media leak, No network scan (after click) Safari 9.1.1 (Tech Preview) : Minimal HW/SW detection, No social media leak, No network scan (after click) Chrome 49.0.2623.110 : Full HW/SW detection, Social media login detected, Network scanning (after click) Firefox 45.0.1 : Full HW/SW detection, Social media login detected, Network scanning (after click)
Wow. Safari is so strict, but I wonder if that's because Safari is (my assumption) a less fat browser after all.
Re: Show HN: What every browser knows about you
#63OS X 10.11.4: Safari 9.1 : Minimal HW/SW detection, No social media leak, No network scan (after click) Safari 9.1.1 (Tech Preview) : Minimal HW/SW detection, No social media leak, No network scan (after click) Chrome 49.0.2623.110 : Full HW/SW detection, Social media login detected, Network scanning (after click) Firefox 45.0.1 : Full HW/SW detection, Social media login detected, Network scanning (after click)
Wow. Safari is so strict, but I wonder if that's because Safari is (my assumption) a less fat browser after all.
Re: Show HN: What every browser knows about you
#64I didn't realize that browser would spill my local IP address, or might be able to scan local devices in the same network. Shouldn't browsers have settings to enable/disable access to device sensors or data?
Re: Show HN: What every browser knows about you
#65OS X 10.11.4: Safari 9.1 : Minimal HW/SW detection, No social media leak, No network scan (after click) Safari 9.1.1 (Tech Preview) : Minimal HW/SW detection, No social media leak, No network scan (after click) Chrome 49.0.2623.110 : Full HW/SW detection, Social media login detected, Network scanning (after click) Firefox 45.0.1 : Full HW/SW detection, Social media login detected, Network scanning (after click)
do you have adblocking or ghostery on one or more of your browsers?
On Safari 9.1.1 TP : no addons
On Safari 9.1 : AB (getadblock.com)
On Firefox : uBO / No "NoScript" (for testing)
On Chrome : uBO
Re: Show HN: What every browser knows about you
#66OS X 10.11.4: Safari 9.1 : Minimal HW/SW detection, No social media leak, No network scan (after click) Safari 9.1.1 (Tech Preview) : Minimal HW/SW detection, No social media leak, No network scan (after click) Chrome 49.0.2623.110 : Full HW/SW detection, Social media login detected, Network scanning (after click) Firefox 45.0.1 : Full HW/SW detection, Social media login detected, Network scanning (after click)
Wow. Safari is so strict, but I wonder if that's because Safari is (my assumption) a less fat browser after all.
Re: Show HN: What every browser knows about you
#67Re: Show HN: What every browser knows about you
#68But a very cool hack.
Re: Show HN: What every browser knows about you
#69> Geo Coordinates: [lat,lng about 90 miles from the correct location] I find that error hilarious, because I setup correct in-addr.arpa and ip6.arpa reverse DNS entries for my (static) IP, which returns a domain name that has an accurate LOC record. My IP is two DNS queries away from my location (~10m precision), yet most of the time everyone uses these geoip databases instead of LOC.
Because you are literally the only one ever who has done this.
Re: Show HN: What every browser knows about you
#70I didn't like that it was able to obtain my battery information. I discovered that this can be prevented in Firefox by setting dom.battery.enabled to "false" under about:config.