Last year Twitter implemented a security feature that allowed its users to browse the site via a secured HTTP connection (HTTPS). This feature was not enabled by default and users had to go to their Settings and enable the feature. However, Twitter now wants to secure user profiles and has made the feature enabled by default.

Security researchers show off HTTPS URL spoofing on Chrome 14/15.

Google Chrome now blocks insecure scripts from running. Google Chrome is blocking non-https JavaScript from running on a HTTPS connection.

Few days back I wrote an article about FaceNiff, an Android app that lets users access web sessions profiles over Wi-Fi networks and hijack your connected Facebook or Twitter account. If your connection is unsecured, then anyone using FacNiff can easily deflect your data or steal your information.

Twitter has now rolled out HTTPS support to everyone. Enable HTTPS browsing in Twitter.

Facebook now has full HTTPS support. Learn how to securely browse Facebook using HTTPS. In addition Facebook also has Social Authentication which will replace traditional captchas.

Twitter now allows users to always use HTTPS while browsing twitter. Enable HTTPS Only Support in Twitter.