4 ms·
Actually, there is a very good excuse: I want to access the content I need with the browser and configuration I currently have, and without the ability to alter
by forgotmypw17 4y ago
Actually, there is a very good excuse: I want to access the content I need with the browser and configuration I currently have, and without the ability to alter it.
While the threat of MITM is technically true, thanks to being on a relatively safe networks segment, I have yet to encounter it happening in the real world, except in cases of captive portals, when I actually want it to happen.
I think it is largely an over-stated threat for most read-only applications.
The impact on accessibility, on the other hand, is real and huge.
- neurostimulant 4y agoYou must be lucky. My cellphone carrier used to injects scripts and ads on plain http requests. Imagine seeing ads on wikipedia. Now that https is everywhere, this behavior is largely stop.
- forgotmypw17 4y agoI know that ads sometimes get injected for some people, but it has not been an issue for me. I see loud and intrusive ads on Wikipedia already, and it's why I've started using wikiless instead.
- neurostimulant 4y agoAre you sure about seeing ads Wikipedia? AFAIK Wikipedia itself doesn't run any ads [1] (except occasional call for donation), so the ads must've come from other source (e.g malicious extensions, malwares that install mitm proxy to inject ads, etc). [1] https://en.wikipedia.org/wiki/Wikipedia:Funding_Wikipedia_through_advertisements https://en.wikipedia.org/wiki/Wikipedia:Funding_Wikipedia_th...
- myfonj 4y agoThere was similar discussion about "provide un-encrypted access to your pages for accessibility" few months ago here at HN under "Consider disabling HTTPS auto redirects" post [1]. [1] https://news.ycombinator.com/item?id=31895148 https://news.ycombinator.com/item?id=31895148