It is general advice, but https should have been the default for a good while.
Comment on Chromium Blog: Towards HTTPS by default
Buddahriffic@lemmy.world 1 year agoIs this just general advice? If so, I agree, but if it’s specific to this, what’s the problem you see with it?
the_q@lemmy.world 1 year ago
gravitas_deficiency@sh.itjust.works 1 year ago
If we have to pick just one reason: WEI. As someone who’s been a professional software engineer for a decade and a half, this has the potential to mutate and ruin the internet at large in ways we’re only beginning to fully explore and understand.
Arghblarg@lemmy.ca 1 year ago
Second reason: killing manifest v2 to kneecap ad-blockers.
Third reason: banning ‘trackmenot’ extension from the chrome store since its purpose is to muddy search stats (enhancing privacy, but in a way that messes up Google’s ad metrics and their history of your preferred search terms).
thantik@lemmy.world 1 year ago
Google has shown that they’re going to go the Microsoft strategy with Browser control. So long as they have majority control, that means they can be as anti-user as they would like, but since everything is downstream of chromium, everyone just basically accepts it. Everything from Google AMP (which was their attempt to take over the web in whole), to their new “Web Integrity API” which aims to lock out any competitors.
Buddahriffic@lemmy.world 1 year ago
Agreed, but to clarify, I was asking if there was an issue with this specific change (always using https if it’s available even if the URL uses http), as it does seem to be a positive that makes me wonder why it’s only happening now.