Through Hacker News, I read that Google Chrome will go HTTPS by default with the release of Chrime 154, which is apparently slated for October 2026. I have not regularly used Chrome since 2015 or so, but I recall having heard from a friend that it did not enforce HTTPS by default. I unsurprisingly enable HTTPS by default in Firefox. Google’s post explains the decision well and it sounds to me like a good implementation. But it is worth noting that some sites do have valid reasons for eschewing HTTPS. See for example Frogfind, a search engine (really a DuckDuckGo front-end, but semantics aside) designed to work well on old computers and in old web browsers (see my 2022 Frogfind review). Websites that have no particular reason for not going HTTPS have a year to make the transition before Google Chrome changes its default setting.