As I work on updating my CMS component, I am incorporating integration with the Twitter API to fetch and showcase a list of tweets related to a user or search query. I have chosen to utilize the Twitter Restful API v1.1 as the 1.0 version is set to be discontinued in two months. The user_timeline and search requests are particularly intriguing to me.
Given that caching plays a significant role in my technology, I aim to minimize server-side processing by providing static HTML and a segment of JavaScript whenever possible. Although I successfully implemented this method for the older API version, the updated approach necessitates authentication data through OAuth. One crucial property (oauth_signature
) involves hashing other properties (including oauth_timestamp
and oauth_nonce
, both of which presumably should be unique for each Twitter request) along with secret keys, thereby posing a security risk if generated on the client side.
My main concern is whether there exists a secure means of obtaining a tweet list on the client side using the new API?