Earlier quoted context omitted.
Even if you use a desktop client, email is part of the world wide web.
How do you figure that? If you're using a desktop client, it seems pretty exactly not part of the web.
Ask HN: What feature would you want the web to “force” next, after HTTPS?
201–210 of 279 posts
Re: Ask HN: What feature would you want the web to “force” next, after HTTPS?
#202Re: Ask HN: What feature would you want the web to “force” next, after HTTPS?
#203Re: Ask HN: What feature would you want the web to “force” next, after HTTPS?
#204I'm ignorant of a lot but, segregation of cookies by browser tab. If I log into Xsocialmedia in Tab 1, and go to news site in Tab 2 using Xsocialmedia plugin, it doesn't know that tab A logged in, or that it came from same browser. Basically, I want my tabs to be isolated and treated as completely separate, isolated browsing histories, caches, and cookies. ...This is my gmail tab. All that tab ever sees is gmail. Thi…
It would be a bit frustrating because once you close the tabs everything is lost. However I am not sure how different browsers "incognito mode" handle multiple tabs.
I do like your idea though.
Re: Ask HN: What feature would you want the web to “force” next, after HTTPS?
#205Now that adoption of HTTPS has solved all SQL injection holes, we can take steps to further modernize the Web so people can feel secure. Require Facebook login for everything. Just don't serve the content without a Facebook login. Can use DPI at the network layer to help enforce. Add phone-home features to CPUs to make them turn off 6 months after product introduction. Everyone ought to be buying a new computer every…
Re: Ask HN: What feature would you want the web to “force” next, after HTTPS?
#206Earlier quoted context omitted.
- no max length on password at all, or allow a 3 digit number of chars. Never silently truncate passwords either. - never disable paste on a password field.
You'll have half your users with passwords like '123'. You could say it's the user's fault and their account is compromised, but when it's half the users on your site, really your site is compromised. Better to have a minimum password entropy.
Re: Ask HN: What feature would you want the web to “force” next, after HTTPS?
#207I'm ignorant of a lot but, segregation of cookies by browser tab. If I log into Xsocialmedia in Tab 1, and go to news site in Tab 2 using Xsocialmedia plugin, it doesn't know that tab A logged in, or that it came from same browser. Basically, I want my tabs to be isolated and treated as completely separate, isolated browsing histories, caches, and cookies. ...This is my gmail tab. All that tab ever sees is gmail. Thi…
You can kind of do this with incognito mode. It would be a bit frustrating because once you close the tabs everything is lost. However I am not sure how different browsers "incognito mode" handle multiple tabs. I do like your idea though.
You can create a container for each compartmentalized context (work, social media, whatever) and then create tabs assigned to diffent containers. They're visually distinguished as to which tab is "in" which container, but otherwise you can manipulate and mingle them freely with the rest of your tabs. Each container's persistent state is isolated from both the other containers and your default browsing context.
Re: Ask HN: What feature would you want the web to “force” next, after HTTPS?
#208Adding support of Internet Message Body Format (a.k.a. MIME) to browsers [1]. MIME 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
You might be interested in Web Packaging: https://github.com/WICG/webpackage
Re: Ask HN: What feature would you want the web to “force” next, after HTTPS?
#209Re: Ask HN: What feature would you want the web to “force” next, after HTTPS?
#210Dear overlord, stop this shit. Don't force any web user over your agenda BS. Amazon.com worked fine from 1995 to 2016 with HTTP (only the login page was HTTPS). If you have a crappy ISP like Verizon or whatever, it's your own personal problem - 99% of the web user don't care about your problem. Maybe use a VPN to somewhere to an ISP you can trust. I stopped using Firefox because they turned mad. Chromium with some cu…