3 ms·
I couldn't work out why people didn't just use the browser cookie controls. It seems shortsighted to force the server to bundle a message down the wire to me -
by 72deluxe 11y ago
I couldn't work out why people didn't just use the browser cookie controls. It seems shortsighted to force the server to bundle a message down the wire to me - the browser should tell me that. What if I am a dumb client like telnet that's just done a GET?
Do we also need servers to inform us in large letters that they're making a note of our IP address and adding it to their logs? That they're using our referral info and browser details (I'm using Chromium on a Mac!)? That they'll use those details for analysis? Weirdly people have switched to Google analytics instead of just looking at the server logs (like awstats from yesteryear). Do we need messages telling us that the ISP is throttling us or logging too? That I'm using PPP or something?
It's all daft. Hopefully this madness doesn't make it into mobile telephone calls - "your location can be triangulated from our phone towers"; "you're using GSM which has weak encryption and can be eavesdropped" etc. etc.
We should have the option of authorising all the GET requests it makes too I feel! That'd keep websites from loading too much (and suffering website bloat, as the average website data size has been climbing massively due to all that JavaScript)