Starting on Tuesday, the million or so third-party applications that use Twitter data must start encrypting all of their communications with the Twitter API, in order to improve security and maintain data integrity. In a short message posted on its service, Twitter announced that, as of Jan. 14, all data requests sent to the Twitter API must be done through the SSL (Secure Socket Layer) protocol, or its successor, the TLS protocol.
Two Takes
View TECHi Stance
Third party Twitter apps must now converse through SSL protocol
Zdnet
View all Zdnet Two Takes by TECHi
Read the original story
Published January 16, 2014
TECHi's Take
Developers whose apps are still using HTTP plaintext connections to connect to Twitter’s API feeds may find their applications broken from today. Twitter has enforced new rules for developers to enhance privacy for end users, which from 14 January will see it block connections to all its API URLs for apps that have not enabled TLS (Transport Layer Security)/ SSL (Secure Sockets Layer) encryption.
NOTE: TECHi Two-Takes are the stories we have chosen from the web along with a little bit of our opinion in a paragraph. Please check the original story in the Source Button below.
Balanced Perspective
TECHi weighs both sides before reaching a conclusion.
TECHi’s editorial take above outlines the reasoning that supports this position.