You cannot just consume and hope nobody cares that you don't give back.

So many knee-jerk comments here. Get a grip folks.

This is about how we treat data of a citizen from one large jurisdiction when it moves to or is stored in another large jurisdiction, and removing legal uncertainty for the companies doing so. For example, this very site's account info of EU residents being stored in the US (handle, email and encrypted password). Nothing overly private, but still falls under privacy laws of hundreds of countries, each of which could voice a problem and issue a warrant or subpoena. Without overarching legal frameworks governing and taming this legal diversity and uncertainty, it is basically impossible to run a large website. Plain and simple. If you're an engineer, you absolutely want to be insulated and protected from all this possible BS, regardless of how much of a non-issue your own data collection might be to your engineering mind.

Even is ISPs are relatively transparent about what they sell you, it is always about maximum download and upload speed, and never about latency and quality of service. In fact, sales and first-tier support folks don't even know these terms, much less what their company's typical values are. In practice, a stable, low latency broadband connection with 15 Mbit/s cap gives you a better overall experience than a jerky, high latency connection which on paper tops out at 50 Mbit/s.

I am very glad the FCC is including these numbers by default to judge a provider's disclosure practices.
As an aside, test your connection at https://www.voipreview.org/spe... and see your latency, jitter and packet loss alongside the other metrics.

It's an iPhone 5C without secure area on the silicon itself. Much weaker than iPhone 6 and 6S, relying on software to do the job of the silicon.
I'd expect newer iPhones to be secure for now.

You do realize that a site only embeds the ad network code, not the final downloaded content? I.e. yes, a site takes some sort of responsibility when deciding to run ads from an ad network. Beyond that, however, every user gets potentially different ads. There are real time bidding platforms and user profiling code in the middle, completely outside the direct control of the website.

If it were that easy this wouldn't be a problem. You've got a least three players here: The website running ads and trying to fight off the bad stuff, the ad networks which only sometimes care enough, and the advertiser trying to game the system into running bad ads. It's a continuous arms race, and as a website owner you end up in reactive mode, rather than proactive.

Won't work anymore. Big advertisers want proof that their ad was seen, via Double Verify or similar, and only pay for ads that were in front of users for a certain amount of time. Javascript and CSS make this easy to measure, and hard to work around.

I was very active on /. in the late 90s and early 2000s. Then life, work, and other interests took over. Can't day it was a conscious decision to stay away.

Well, some of us on the new team have been around for a while. I remember a magenta and white version of /. run out of Rob Malda's dorm room.
It's like meeting up with a long lost friend - happy to be involved behind the scenes now.

HTTPS also blinds "proxies" and antivirus software which may have their own opinions of what should and should not travel over plain old port 80. ISPs have done stunts like ad injection, antivirus software routinely blocks websockets, and on and on. HTTPS is a godsend around this bullshit.