What about handling secure (https) connections?
We will establish a secure connection from the cloud to the site owner on your behalf for page requests of sites using SSL (e.g. https://siteaddress.com).
Amazon Silk will facilitate a direct connection between your device and that site. Any security provided by these particular sites to their users would still exist.
I’m really not convinced by this statement. Google, Facebook, and Amazon are all in the same game of knowing what their users are doing, seeing, reading, buying and searching for. The fact that Amazon will be making secure https connections on MY BEHALF is enough to keep me off the browser despite the speed gains and mobile optimizations.
Comments
3 responses to “Silky Privacy Concerns”
Message from Amazon Silk browser when connecting to your bank’s web site: “Mr. Bezos has decided you spend too much money to buy any other products from Amazon so we’ve stopped paying some your bills so that you’ll be able to buy more stuff from Amazon. You’re welcome.”
Except I just want to believe that Amazon would never do something like that! Facebook would not only do that but also post your bank balance to your wall along with messages like “Just skipped an alimony payment, bitch!”
And of course there’s the same issue we have with Mint – every bank agreement stipulates that if you provide your account credentials to a 3rd party you’re no longer protected against fraud. If Amazon got hacked and some one emptied your bank account then the bank could legitimately say “stop using the Kindle Fire, oh and you’re SOL.”
Or another interpretation is that when using a secure connection the content will be passed directly through to you without any “optimization” by the Silk cloud.
Which is kind of annoying as I try to use HTTPS for more and more sites (like GMail, G+, etc.) – especially when I’m on a wireless connection. It’s to the point where I instinctively type https://… for every site I visit now.
If you re-read their statement and then go through their T&C’s, you will see that is necessarily the case.