Twitter Joins the HTTPS By Default Party 95
wiredmikey writes "Following a trend in allowing users to automatically utilize the secure HTTPS protocol when accessing Web based services, Twitter announced this week that it has added the option for users to force HTTPS connections by default when accessing Twitter.com.
The reasons to utilize HTTPS when accessing any personal accounts aren't new, but an easy to use extension for FireFox called 'FireSheep,' released in October 2010, spiked concern, as it enables HTTP session hijacking for the masses."
What's the penalty for HTTPS? (Score:4, Interesting)
Back some years ago, there was talk about dedicated SSL hardware. What's the performance penalty for HTTPS anymore?
Say you're a small startup running your "the next Twitter" app on a Xen or OpenVZ VPS instance.
What's the hit for HTTPS?
Any thoughts on HTTPS only for the login page, or for all pages?
Good start, but install HTTPS everywhere (Score:5, Interesting)
I don't like keeping track of what sites I can and can't use HTTPS on, so I installed HTTPS Everywhere [eff.org] on my browsers and get HTTPS access to a bunch of sites by default.
BTW, when do we get HTTPS access to /.?