A simple way to block third party trackers/beacons that's on by default, with a simple one-click to disable it on that page load.
Ask HN: What feature would you want the web to “force” next, after HTTPS?
11–20 of 279 posts
Re: Ask HN: What feature would you want the web to “force” next, after HTTPS?
#12Re: Ask HN: What feature would you want the web to “force” next, after HTTPS?
#13I'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.
I second this. DNS is still a privacy killer
Re: Ask HN: What feature would you want the web to “force” next, after HTTPS?
#14Default encrypted email communications
Re: Ask HN: What feature would you want the web to “force” next, after HTTPS?
#15IPv6?
Re: Ask HN: What feature would you want the web to “force” next, after HTTPS?
#16JavaScript Standard Library created that every browser has "installed" and updated automatically.
Yeah. It's a real shame that the language we need batteries-included in the most (because of code size limitations) is one of the most deficient.
Re: Ask HN: What feature would you want the web to “force” next, after HTTPS?
#17- 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 logins and email addresses as UIDs.
- Blocking of any and all forms of popups, including javascript popups, overlays, cookie banners, browser notifications.
The web is rapidly becoming a place I don't want to visit anymore.
Re: Ask HN: What feature would you want the web to “force” next, after HTTPS?
#18It's not security related, but: Accessibility.
Yep, browsers should have screen readers built in. It's ridiculous that you have to shell out $1000+ for a JAWS license (there are alternatives, but they need work).
Re: Ask HN: What feature would you want the web to “force” next, after HTTPS?
#19I'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.
Solid idea, I like it.
Re: Ask HN: What feature would you want the web to “force” next, after HTTPS?
#20A ban of everything JS except for these so-called web apps, which obviously need it.
Make the internet great (performant/efficient/secure) again!