You may have your own reasons for not preferring https, but having it default is important for security for others, even when the page doesn't contain sensitive material (a point which is debatable as well). https://doesmysiteneedhttps.com is a good short summary of reasons.
I think I understand the arguments for and I disagree.
There may be benefits to some users and those users can mitigate them easily (eg, vpn) without having to impact all users.
I don’t like it being proposed as a solved, no brainer when there should be considerations.
The site you linked to has straw man arguments for many of the items like whether someone can impersonate a site. While possible, it’s unlikely and not reasonable for many sites to worry about.
Take my example of the Feynman article. Perhaps someone MITM the site and changes content. That could happen, but is it likely? Do I care?
The privacy impact is moot because there are large orgs (Google, facebook, etc) monitoring all traffic so I’m not sure why I care that ISPs and wifi hotspots can monitor traffic as well.
I wish sites would present serious arguments rather than assuming simple, weak versions.
> I don’t like it being proposed as a solved, no brainer when there should be considerations.
> I wish sites would present serious arguments rather than assuming simple, weak versions.
It seems to me that considerations on this matter has been seriously and carefully taken in recent years and you seem to be the one going against today's consensus. The charge of providing evidences that HTTPS is not always the right thing on the Web is therefore probably on you¹.
I care about both ecology (if this is your point?) / efficiency and privacy and still prefer that encryption by default. It seems to me that HTTPS is not a significant overhead.
But providing privacy to people who really need it (and not for the wrong reasons) without them looking suspicious is badly needed for a well-functioning society, and this includes good decisions related to ecology.
I would suggest you to build an HTTP-everywhere extension, but many websites will refuse to serve your requests on HTTP so…
1: I actually can see an issue for HTTPS everywhere, and this is that it makes websites unreachable to old devices. But there, outdated browsers are probably an obstacle too, and I guess it would be possible to set up some kind of HTTP proxy for them (?)
