re: https I meant that men-in-the-middle advertising such as by WLAN providers and ISPs is prevented, and rightly so. OTOH, this leads us into monopolism or duopolism which at this point might be even worse. The argument in this context is that whatever action Google does isn't bad per se and absolutely defensible from a security and even privacy PoV, but at the same time is something that helps Google first and foremost. In the same way, Google can present ad-blocking support in Chrome as a pro-consumer measure, when in reality its purpose is to go after the remaining alternative ad network revenue to achieve increasingly difficult growth.
FSF's LibreJS initiative is laudible, and something I'm willing to support with what I'm offering on the web. I found that sites that have content worth reading typically aren't script-heavy and entirely usable without script, or by using either F/OSS JavaScript (including jquery) and "trivial scripts" according to FSFs definition. The notorious exceptions are Google Analytics, ReCaptcha, and maybe Disqus, for which solutions must be found. Google Analytics, and the necessity to make use of it might be a case where Google as a major sponsor of web standards are acting in conflict with a solution based on web standards.
Wrt. ABP my initial gut reaction to paid ABP acceptable ads was extremely negative, but maybe I might reconsider.