- cross-posted to:
- technews@radiation.party
- cross-posted to:
- technews@radiation.party
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”.
Don’t use chromium based browsers.
Is this just general advice? If so, I agree, but if it’s specific to this, what’s the problem you see with it?
It is general advice, but https should have been the default for a good while.
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.
Why just one? :p
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).
I’ll keep using Brave because I like it. Thank you for your concern.
Keep grinding that ax.
I will. It’s sharp now. I will make it sharper.