Securing Twitter With HTTPS: But Is It Ready For Prime Time Yet?
Twitter has announced an important security option that you should be aware of:
Today, we’re taking an important step to make it easier to manage the security of your Twitter experience – we are adding a user setting that lets you always use HTTPS when accessing Twitter.com. Using HTTPS for your favorite Internet services is particularly important when using them over unsecured WiFi connections. Source
To turn HTTPS on all you need do is go to your settings and check the box next to “Always use HTTPS” near the bottom of the page. That means your Tweeting will now be SSL-encrypted which will put up a wall to external attacks.
This will better protect your information, especially if you are using Twitter over an unsecured Internet connection such as public WiFi where anyone can eavesdrop on you. Twitter plans to make HTTPS the default setting in the future.
They caution however if you are using Twitter from a mobile browser, you will need to go to https://mobile.twitter.com in order to use HTTPS.
My Experience With Twitter HTTPS:
One thing that I noticed right away is I always have to login after closing my browser .. and that’s a good thing. But there was also a drawback. So far my favorite newsfeed reader Feedly can’t tweet with HTTPS turned on.
After switching HTTPS off Twitter was still trying to force me to use HTTPS. I had logged out, cleared the cache and cookies, but Twitter still insisted on HTTPS. Trying to log out also crashed Twitter and only after several failed attempts did it finally let me back in without HTTPS.
Hmm, Twitter HTTPS is obviously still buggy and lacking 3rd party support. No wonder they haven’t made it mandatory (yet). Thanks for using me as a beta tester Twitter … NOT.
The moral of this story is securing Twitter with HTTPS makes sense and is long overdue. But for obvious reasons I think I’ll avoid it for now.
How about you? Try it for yourself and let me know how it works for you. Or you can just wait in line like me.
UPDATE 04-14-11: @Feedly seems to be working with HTTPS now so I have no more caveats recommending it.
This Tweetcast is brought to you by BLOGBloke: Veteran Blog Pioneer, Tech Author/Editor, and Social Media Tips (with just a little attitude). Read even more BLOGBloke @ Twitter.