Show HN: What every browser knows about you
131–140 of 209 posts
Re: Show HN: What every browser knows about you
#132You might want to change that to something on a big company CDN to avoid killing kenrockwell.com's server.
Re: Show HN: What every browser knows about you
#133Earlier quoted context omitted.
Simply visiting a link downloads dozens, sometimes hundreds of files without your explicit permissions. It simply uses a different protocol.
No, it doesn't just use a different protocol. It ignores your network settings (proxy) and exposes your local network information. I can understand not wanting to scare people with "Allow P2P Data Channel", but ignoring proxy settings and revealing all IPs is unacceptable. WebRTC folks toss off these concerns with "there's no way to prevent tracking so heh".
Re: Show HN: What every browser knows about you
#134Not sure why battery is exposed; I guess that's the result of making browsers more like OSes. The only really annoying thing is the idiotic WebRTC settings. Their love for "data channels" with zero prompts, despite having no legitimate uses[1], ignores your proxy settings. This should be fixed. 1: I asked someone involved with WebRTC. They suggested "maybe a page wants to communicate with your fridge directly" as a s…
I am not sure if this battery is not just FUD and some other sections as well. Because I currently have no battery in my laptop (no battery detected) and site is saying "Charging: charging", "Battery level: 100%", "Charging time: 0h"
The page also thinks my system is flat on a table. Close; the screens are, while the tower's on the floor :P
Re: Show HN: What every browser knows about you
#135Surely you can source this information (OS and browser) from the User Agent?
Re: Show HN: What every browser knows about you
#136Not sure why battery is exposed; I guess that's the result of making browsers more like OSes. The only really annoying thing is the idiotic WebRTC settings. Their love for "data channels" with zero prompts, despite having no legitimate uses[1], ignores your proxy settings. This should be fixed. 1: I asked someone involved with WebRTC. They suggested "maybe a page wants to communicate with your fridge directly" as a s…
I am not sure if this battery is not just FUD and some other sections as well. Because I currently have no battery in my laptop (no battery detected) and site is saying "Charging: charging", "Battery level: 100%", "Charging time: 0h"
Re: Show HN: What every browser knows about you
#137Not sure why battery is exposed; I guess that's the result of making browsers more like OSes. The only really annoying thing is the idiotic WebRTC settings. Their love for "data channels" with zero prompts, despite having no legitimate uses[1], ignores your proxy settings. This should be fixed. 1: I asked someone involved with WebRTC. They suggested "maybe a page wants to communicate with your fridge directly" as a s…
I am not sure if this battery is not just FUD and some other sections as well. Because I currently have no battery in my laptop (no battery detected) and site is saying "Charging: charging", "Battery level: 100%", "Charging time: 0h"
Re: Show HN: What every browser knows about you
#138The speedtest http://webkay.robinlinus.com/scripts/speedtest.js downloads a 5mb file from http://www.kenrockwell.com/contax/images/g2/examples/3112003... . You might want to change that to something on a big company CDN to avoid killing kenrockwell.com's server.
Re: Show HN: What every browser knows about you
#139> 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.
Re: Show HN: What every browser knows about you
#140Earlier quoted context omitted.
Multiplayer gaming is a legitimate use of data channels, but I don't see why it couldn't prompt for permission.
WebRTC folks insist prompts will confuse people and be bad. But ignoring explicit networking settings is good, somehow.