Evergreen web browsers. Safari and IE11 continue to ruin my life.
Ask HN: What feature would you want the web to “force” next, after HTTPS?
21–30 of 279 posts
Re: Ask HN: What feature would you want the web to “force” next, after HTTPS?
#22I'd vote for DNS-over-HTTPS or similar tech. Encrypting domain name resolution should help mitigate a gateway or proxy (Comcast) from knowing or blocking sites you visit.
DNS is a non-trivial amount of traffic to go moving from a lightweight UDP protocol to something like HTTPS. Furthermore, that would dramatically increase page load times (for reasonably sized pages) since HTTPs requires more turns.
Re: Ask HN: What feature would you want the web to “force” next, after HTTPS?
#23I would love package systems and server admins to recognize the inherit danger in allowing the servers to call out to the wild. All internet facing servers should be allowed to only call out to white listed addresses.
Re: Ask HN: What feature would you want the web to “force” next, after HTTPS?
#24A ban of everything JS except for these so-called web apps, which obviously need it. Make the internet great (performant/efficient/secure) again!
Really what browsers need are profiles. Maybe a research profile that just supports submitting search forms and renders everything in the same colors and the same fonts and the same margins, and an app profile which lets pages do all the ridiculous JS crap.
Re: Ask HN: What feature would you want the web to “force” next, after HTTPS?
#25Ending the NSA dragnet
Re: Ask HN: What feature would you want the web to “force” next, after HTTPS?
#26Default encrypted email communications
That's not part of the web.
Re: Ask HN: What feature would you want the web to “force” next, after HTTPS?
#27I'd vote for DNS-over-HTTPS or similar tech. Encrypting domain name resolution should help mitigate a gateway or proxy (Comcast) from knowing or blocking sites you visit.
But then how would the Food Standards Agency get access to my browsing history?
https://www.reddit.com/r/unitedkingdom/comments/5ei5dz/list_...
Re: Ask HN: What feature would you want the web to “force” next, after HTTPS?
#28ML driven content blocking for ads and other garbage such as social widgets and beacons. Red screen warning as deceptive on any site that tries to hack its way around the filter.
Wouldn't you by definition not be able to detect working around the filter? Because if you could detect it, why would it not just be another filter condition?
Re: Ask HN: What feature would you want the web to “force” next, after HTTPS?
#29Evergreen web browsers. Safari and IE11 continue to ruin my life.
Unfortunately this one is impossible even if every developer and browser vendor were all unanimously in favor. Edge-née-IE is evergreen now, but users have to upgrade Windows first, and that's not something that can be forced.
Re: Ask HN: What feature would you want the web to “force” next, after HTTPS?
#30- A protocol for sites to get my public PGP key for server side use - The discontinuation of using SSL certificates for verification of website identities and a move to true fingerprinting ala SSH. - Deprecation of email or rather its insecurity. - Logins on websites with a public / private keypair ala SSH. - A resurgence in sites that let me pick my own anonymous username instead of Facebook, Google or Twitter login…
> Deprecation of email or rather its insecurity.
We would need something to replace it with, there is really nothing right now.