Amazon Silk browser on Kindle Fire tracks page visits to generate trends, isn’t as spooky as it sounds (update: opt-out exists)

Amazon Silk browser on Kindle Fire tracks page visits to generate trends, isn't as spook

When you pick up that new Kindle Fire HD this fall, one of the first things you'll notice is an updated version of Amazon's Silk web browser with a Trending Now section. It's a clever trick that takes advantage of Silk's server-based caching to find out what sites are popular among owners. That sounds good on the surface, but it doesn't take much effort to realize that there are privacy concerns already in the air -- Amazon is sharing personal web habits with a wider audience, after all. While the section is unlikely to include any identifying information, there's no immediate sign that tablet owners can keep their behavior private, and that could create some indignation among those who'd prefer to surf in isolation. We've asked Amazon if there will be an opt-out escape hatch and will let you know if there's a definitive answer. In the meantime, we wouldn't necessarily worry. Silk shouldn't be caching your e-mail, and it's only likely to ever show pages that have far more traffic than anything you'd be embarrassed to show to others. As far as we can tell, your secret knitting obsession should be safe.

Update: A spokesperson has confirmed that the option to disable Silk's caching is still available, and that switching it off will cut you out of Trending Now; that's a very all-or-nothing approach, but it'll likely suit those put off by the browser's predictive approach in the first place. Secure pages are still out of the picture as well, which should keep those private Twitter messages out of the equation.

Filed under: ,

Amazon Silk browser on Kindle Fire tracks page visits to generate trends, isn't as spooky as it sounds (update: opt-out exists) originally appeared on Engadget on Fri, 07 Sep 2012 14:33:00 EDT. Please see our terms for use of feeds.

Permalink   |  sourceTechCrunch  | Email this | Comments

Google badmouths HTTP behind its back, proposes SPDY as a speedy successor

Google badmouths HTTP behind its back, proposes SPDY as a speedy successor

If there's anything that Google doesn't like, it's things that collect dust. The company is famous for its annual spring cleaning efforts, in which the firm rids itself of redundant and dead-end projects, along with more bullish moves, such as its push to overhaul the internet's DNS system. Now it's looking to replace HTTP with a new protocol known as SPDY, and to that end, it's demonstrating the potential speed gains that one might expect on a mobile network. According to the company's benchmarks, mean page load times on the Galaxy Nexus are 23 percent faster with the new system, and it hypothesizes that further optimizations can be made for 3G and 4G networks. To its credit, Google has already implemented SPDY in Chrome, and the same is true for Firefox and Amazon Silk. Even Microsoft appears to be on-board. As a means to transition, the company proposes an Apache 2.2 module known as mod_spdy, which allows web servers to take advantage of features such as stream multiplexing and header compression. As for HTTP, it's no doubt been a reliable companion, but it seems that it'll need to work a bit harder to earn its keep. Stay weird, Google, the internet wouldn't be the same without you.

Google badmouths HTTP behind its back, proposes SPDY as a speedy successor originally appeared on Engadget on Wed, 02 May 2012 14:19:00 EDT. Please see our terms for use of feeds.

Permalink   |  sourceGoogle Developers Blog  | Email this | Comments