Hacker News new | ask | show | jobs
by toomuchtodo 2172 days ago
Submit an https Wayback archive link instead. The initial retrieval from origin to Wayback will be unencrypted, but everyone’s connection to Wayback will be TLS.

HN could even do this programmatically when you submit the http link, kicking off the Wayback archive op and substituting the resulting link. This future proofs the thread in case the content disappears later.
1 comments
tjoff 2172 days ago
And that is absolutely horrendous user experience.

Http isn't that bad and if you happen to have an ISP that injects ads you have way bigger problems and probably live in a country so infested with ads you won't even notice the difference anyway.

Most certainly not worth banning http submissions for that.

link
user5994461 2172 days ago
The main US ISPs have all been caught injecting ads, tracking cookies and other things.
link
aflag 2172 days ago
I think it was veiled criticism to the United States' ad culture.

Someone using those ISPs should probably look into a vpn. I know it feels weird to trust a third party more than your ISP, but if they're injecting ads into your HTTP responses, maybe you should.

Anyway, giving the user the option of using https and even defaulting to it is a good thing. But I don't think non-encrypted protocols are that disastrous if no secrets are being transmitted.

link