4 ms·

Having an intelligent non https submission warning could be good... You could go so far as to flat out refuse to send a cc number in the clear. The degree of d

Having an intelligent non https submission warning could be good... You could go so far as to flat out refuse to send a cc number in the clear. The degree of dependence on the search engine is troubling, would be interesting to see how much could be handled by a local mini index without involving a 3rd party. Also think browser history could be a lot more useful if it were organized better. For example, maybe grouping pages by the search terms that led to them... Also would be nice to have a quick way to get a detailed history on any given site, along with the pages led in and followed out. The main way I still use bookmarks is for organizing reference material, I think this could be automated partially as well.

nightpool 12y ago
I had similar concerns about the dependence on a search engine, but then I realized this could be the perfect "killer app" for a meta-search engine aggregator, one that thought of SERPs like zero-trust inputs to be mined for data. (and, similarly, not personalizing, aggregation by some "mixer" intermediary, and other privacy optimizations become much more feasible) This seems like it needs to be the end result of search, Google or no Google, but a privacy-conscious organization like putting this tech so front and center could definitely be a foot in the door to making this a reality.
cpeterso 12y ago
Here is a Firefox bug about highlighting or warning about insecure password fields: https://bugzilla.mozilla.org/show_bug.cgi?id=748193 https://bugzilla.mozilla.org/show_bug.cgi?id=748193 And a bug for Chromium (that also mentions credit card number fields): https://code.google.com/p/chromium/issues/detail?id=399416 https://code.google.com/p/chromium/issues/detail?id=399416