Chewing on the Fire's Detail Page
Sep. 28th, 2011 02:22 pm![[personal profile]](https://www.dreamwidth.org/img/silk/identity/user.png){kind=small}
walkitoutSpecifically, the Fire has some elements designed to speed up browsing (which anyone who has
spent much time doing on a tablet knows is an Issue):
"Amazon EC2 is always connected to the backbone of the Internet where round-trip latency is 5 milliseconds or less to most web sites rather than the 100 milliseconds that’s typical over wireless connections. AWS also has peering relationships with major internet service providers, and many top sites are hosted on EC2. This means that many web requests will never leave the extended infrastructure of AWS, reducing transit times to only a few milliseconds."
That ought to set off some people -- this essentially says, hey, we know that all traffic is not created equal. We're more equal than others, by contract. On the one hand, anyone looking for an advantage is going to be happy (if possibly a little skeptical). On the other hand, anyone who thinks traffic being throttled in favor of other traffic is going to be saying very nasty things.
"Finally, Silk leverages the collaborative filtering techniques and machine learning algorithms Amazon has built over the last 15 years to power features such as “customers who bought this also bought…” As Silk serves up millions of page views every day, it learns more about the individual sites it renders and where users go next. By observing the aggregate traffic patterns on various web sites, it refines its heuristics, allowing for accurate predictions of the next page request. For example, Silk might observe that 85 percent of visitors to a leading news site next click on that site’s top headline. With that knowledge, EC2 and Silk together make intelligent decisions about pre-pushing content to the Kindle Fire. As a result, the next page a Kindle Fire customer is likely to visit will already be available locally in the device cache, enabling instant rendering to the screen."
And _this_ really ought to set off some privacy advocates. It's sort of creeping me out, actually.
ETA:
Sample coverage of privacy concerns will be added in dribs and drabs starting now:
http://www.theregister.co.uk/2011/09/29/amazon_silk_looks_phormulaic/
http://news.cnet.com/8301-30685_3-20113387-264/amazon-silk-one-step-forward-two-steps-back/
spent much time doing on a tablet knows is an Issue):
"Amazon EC2 is always connected to the backbone of the Internet where round-trip latency is 5 milliseconds or less to most web sites rather than the 100 milliseconds that’s typical over wireless connections. AWS also has peering relationships with major internet service providers, and many top sites are hosted on EC2. This means that many web requests will never leave the extended infrastructure of AWS, reducing transit times to only a few milliseconds."
That ought to set off some people -- this essentially says, hey, we know that all traffic is not created equal. We're more equal than others, by contract. On the one hand, anyone looking for an advantage is going to be happy (if possibly a little skeptical). On the other hand, anyone who thinks traffic being throttled in favor of other traffic is going to be saying very nasty things.
"Finally, Silk leverages the collaborative filtering techniques and machine learning algorithms Amazon has built over the last 15 years to power features such as “customers who bought this also bought…” As Silk serves up millions of page views every day, it learns more about the individual sites it renders and where users go next. By observing the aggregate traffic patterns on various web sites, it refines its heuristics, allowing for accurate predictions of the next page request. For example, Silk might observe that 85 percent of visitors to a leading news site next click on that site’s top headline. With that knowledge, EC2 and Silk together make intelligent decisions about pre-pushing content to the Kindle Fire. As a result, the next page a Kindle Fire customer is likely to visit will already be available locally in the device cache, enabling instant rendering to the screen."
And _this_ really ought to set off some privacy advocates. It's sort of creeping me out, actually.
ETA:
Sample coverage of privacy concerns will be added in dribs and drabs starting now:
http://www.theregister.co.uk/2011/09/29/amazon_silk_looks_phormulaic/
http://news.cnet.com/8301-30685_3-20113387-264/amazon-silk-one-step-forward-two-steps-back/
![[identity profile]](https://www.dreamwidth.org/img/silk/identity/openid.png){kind=small}
exploiting past browsing...
Date: 2011-09-28 08:44 pm (UTC)I suppose what really matters with their browser is your connection to their "backbone". Seems like a single point of failure to me ... well they're smart enough to have made it redundant. But did they make it redundant enough?