mattgaidica

3 ms·

1. 1.▲
   by mattgaidica 16y ago

   Yea, I am sure there is some top secret Google magic if they are forced through SSL!
2. 2.▲
   by mattgaidica 16y ago

   Yea, luckily nearly every major API and service (Amazon, Facebook, Google..) has an encrypted version to pull from. So as long as the entire team understands that, then I only have the usability issue as an argument. If we could get GoDaddy
3. 3.▲
   by mattgaidica 16y ago

   Encrypting site content increases server load, so response time may lack a little.. and we all know Google does take that into account. Also, it might be important that robot files and sitemaps are under the https protocol. I am guessing Go
4. 4.▲
   by mattgaidica 16y ago

   I am 100% with that mentality, I guess I just see the overhead and understanding of HTTPS causing more problems in practice than solutions for developers who are not security-centric. Think we'll ever see google.com go to SSL?
5. 5.▲
   by mattgaidica 16y ago

   No. I think the HTTPS in the browser prompts a user to think there is confidential information being passed when your just browsing, so now your break user experience. The app portion could be, and should be for any semi-secret information,