Twitter has followed in the footsteps of Facebook by offering an opt-in "always on" HTTPS setting to users of its micro-blogging service. The Secure Sockets Layer (SSL) encryption protects Twitter users who access the service over unsecured Wi-Fi connections. "This will improve the security of your account and better protect …
Wonderful, but do the API's support it that all the Applications use? The same applies to Facialbook too?
...of course, only a cynic would speculate that Twitter offer https, not provide APIs to other developers that support it, then complain loudly about how third party clients are insecure and ban them "for the good of users".
I'm sure that in no way would they dream of doing this so they could block access to all but their own clients/interfaces, and find fun ways to monetise those (cough, quick bar, cough)...
Well, if you cared about this..
You'd be using HTTPS Everywhere already.
So your inane Twitterings are securely transmitted between your device and their servers.
Then published to world + dog...........
As Jeff 11 and two00lbwaster pointed out there are other reasons. Another one is that some users choose to keep their tweets private except for approved followers.
How about those annoying little things called login credentials?
- One HUNDRED FAMOUS LADIES exposed NUDE online
- Google flushes out users of old browsers by serving up CLUNKY, AGED version of search
- China: You, Microsoft. Office-Windows 'compatibility'. You have 20 days to explain
- GCHQ protesters stick it to British spooks ... by drinking urine
- Twitter: La la la, we have not heard of any NUDE JLaw, Upton SELFIES