Twitter implemented OAuth authentication for read requests, which allows user- rather than IP-based rate restrictions as well as a higher rate limit. This would be a great feature for Twitter Pull:
http://dev.twitter.com/pages/auth

CommentFileSizeAuthor
#2 twitter_pull_oauth.tgz11.92 KBdgsiegel

Comments

irakli’s picture

irakli commented
Priority: Normal » Minor
Status: Active » Postponed

Twitter Pull has been designed so that it does not need to authenticate at all. This was a conscious decision to make the module as simple to use as possible.

While user-specific vs IP-based rate restriction may sound tempting, at this point it's a very low priority change. Module does extensive caching and Twitter rate limits are very liberal, so rate limit is hardly ever a problem when using this module.

dgsiegel’s picture

dgsiegel commented
StatusFileSize
new twitter_pull_oauth.tgz11.92 KB

as i needed the twitter home_timeline feed for my site, oauth was a must. i basically took the php oauth library from abraham williams (https://github.com/abraham/twitteroauth), the admin menu and oauth authentication process from the twitter module and modified the twitter_pull module to support only oauth.

i changed the module to suit my needs. for example i wanted to specify just a single key, which is "statuses/home_timeline" and no username, lists or search like twitter_pull currently does. additionally i removed the custom caching table too, and moved the caching mechanism to the "cache" table.

as you can see, you can't just apply my changes to the current state, but, if you like to have oauth support in twitter_pull i would gladly help you merge my stuff.