Earlier quoted context omitted.
it's kinda been tried by proxy through authentication standards like OpenID. i wonder if the solution isn't to back off a little though. that is, standardize some process instead of (de?)centralizing authentication. something that gives developers more control, and users more familiarity, than OpenID.
open ID moves the user away from your service, which i think is not what some sites want because they want more user info and control. that's why openid failed.
Ask HN: What feature would you want the web to “force” next, after HTTPS?
181–190 of 279 posts
Re: Ask HN: What feature would you want the web to “force” next, after HTTPS?
#182Add SRV lookups to the HTTP standard. There's a tremendous amount of complexity and cost attached to the fact that browsers look up the IP address of the hostname and then connect to port 80. First, it's true that you can specify another port in the URL, but nobody does that because it's ugly and hard to remember. If you want to be able to send people to your website, you need to be able to tell people what the url i…
Re: Ask HN: What feature would you want the web to “force” next, after HTTPS?
#183Re: Ask HN: What feature would you want the web to “force” next, after HTTPS?
#184MIME is a format that can contain html/css/script/images/etc in single file (or stream).
Thus the whole web application can be served as a single stream by the server.
Yet emails (that are MIME files) can be opened by browsers as natively supported documents.
[1] MIME : https://tools.ietf.org/html/rfc2045
Re: Ask HN: What feature would you want the web to “force” next, after HTTPS?
#185A ban of everything JS except for these so-called web apps, which obviously need it. Make the internet great (performant/efficient/secure) again!
Forgive me, but I just don't understand this sentiment at all. I understand your general frustration with over-engineered websites - but is it not your choice to visit that website? Do you not also have the ability to block javascript just like the scourge of flash websites before it? We aren't talking about vulnerabilities here though, youre just saying that there are websites out there that could do with less (or n…
Re: Ask HN: What feature would you want the web to “force” next, after HTTPS?
#186Ajax without JavaScript. Ability to send a response from server updating only part of DOM. Basically, react with virtual DOM on the server pushing diffs to user with http2 awesomness. There will be no need for JS on most sites, can be adapted to current frameworks, and with preload/prefetch it might be very fast. * U can prefetch progress bar / loading state for example, and redirect to partial url of a real content
intercooler also supports something similar to the server pushed DOM diff flow you envision:
Server Sent Events BETA (http://intercoolerjs.org/docs.html#sse)
"Server Sent Events are an HTML5 technology allowing for a server to push content to an HTML client. They are simpler than WebSockets but are unidirectional, allowing a server to send push content to a browser only." http://intercoolerjs.org/docs.html#sse
Re: Ask HN: What feature would you want the web to “force” next, after HTTPS?
#187Pay turn off ads. A certain percentage of visitors are asked to rate the content (to avoid paying) the rest of the visitors are automatically billed and pay the average rating. Each user can specify a maximum payment and can opt to view with ads if payment requested is too much.
Re: Ask HN: What feature would you want the web to “force” next, after HTTPS?
#188- 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…
The login problem was attempted to be solved by Mozilla's "persona", now deprecated. I like the general idea that I strongly authenticate to my browser, which can then "vouch" for me to various sites using cryptographic tokens that are otherwise useless (so no cracking/stealing passwords, etc). The devil of course would be in the details.
Re: Ask HN: What feature would you want the web to “force” next, after HTTPS?
#189Hard deprecation of the long tail of Javascript browser capabilities and incompatibilities. So much code and so many libraries are littered with "if (old version browser) do x, else if IE, do y, else, ..."
So IE should say "sorry I suck, switch to another browser?" Doesn't make any sense... I mean sites will already tell users they don't support older browsers.
Re: Ask HN: What feature would you want the web to “force” next, after HTTPS?
#190Earlier quoted context omitted.
Maybe im missing something You definitely are. Disable js and try browsing. Note the quadrupled battery life in your laptop.
I don't doubt improved battery life (although quadrupled seems like a stretch) - but I bet if you turned off images and video you'd have a similar improvement - but nobody is saying that pictures are ruining the web. Again, arent you capable of choosing the websites you use? Are there websites you are required to spend extended amounts of time with that you want the browsers to step in and force them to use less java…