- cross-posted to:
- browsers
- hackernews@derp.foo
- cross-posted to:
- browsers
- hackernews@derp.foo
cross-posted from: https://lemmy.world/post/3301227
Chrome will be experimenting with defaulting to https:// if the site supports it, even when an http:// link is used and will warn about downloads from insecure sources for “high-risk files” (example given is an exe). They’re also planning on enabling it by default for Incognito Mode and “sites that Chrome knows you typically access over HTTPS”.
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.
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).