I'm not convinced it's BULLSHIT yet
not 'BULLSHIT' yet, i.e. the idea that the FTC already has protections in place for BASIC privacy. Like banks, credit cards, and merchants, for example. They're the ones that are supposed to be making THOSE kinds of rules.
The FCC rules were more restrictive, for sure, but didn't apply to Facebook, Google, etc.. It was also a serious OVERSTEPPING OF AUTHORITY, which is why I am glad it's GONE. It's _NOT_ the business of the FCC to suddenly re-classify the internet as "something else" and REGULATE CONTENT and its usage.
But the next phase might just be to MAKE IT RIGHT, by having the FTC put the ISPs under the SAME privacy and data protection rules that financial institutions already are, regarding "the things we access". Same with Face-b[itch,ook] and Google, for servers located in the USA at any rate. A simple privacy policy [that's enforced] and an opt-out will do (just like my bank has to honor). FTC, yeah.
And as long as there are no 'man in the middle' attacks going on, I think https might be sufficient to protect you the rest of the way. Just make sure you don't use a "poisoned" DNS (from your ISP) that begs you to install new certs... it adds credibility to using google's free DNS service, or your own bind implementation.