{"id":67826,"date":"2013-10-21T01:38:52","date_gmt":"2013-10-20T18:38:52","guid":{"rendered":"http:\/\/moui.net\/blog\/?p=67826"},"modified":"2013-10-21T01:42:14","modified_gmt":"2013-10-20T18:42:14","slug":"how-to-config-the-twitter-digest-for-twitter-api-v1-1","status":"publish","type":"post","link":"https:\/\/moui.net\/blog\/2013\/10\/how-to-config-the-twitter-digest-for-twitter-api-v1-1\/","title":{"rendered":"How to config the Twitter Digest for Twitter API (v1.1)"},"content":{"rendered":"

from : Twitter Digest Lives!<\/a><\/p>\n

Sunday, June 23, 2013<\/abbr><\/div>\n
\n

Despite Twitter\u2019s best efforts, I\u2019ve managed to bring back Twitter Digest from the bring of destruction to work with the new Twitter API (v1.1). Version 2.8<\/a> of the plugin has just been released and should be considered unstable until I\u2019ve had a chance to test it over the a few days. However, considering 2.7 was not working for anyone, we\u2019d be no further behind if a bug in 2.8 prevented tweet digests from being created. Feel free to try it out yourself and let me know if you run into problems.<\/p>\n

Unfortunately, Twitter now requires authentication for all API requests. I won\u2019t get into why this is stupid here, but suffice to say the Four Tokens of the Apocalypse are upon us and we\u2019re all worse off for it. You can check out this post<\/a> to see how you can get your own tokens and, if interested, how I ended up fixing the plugin. Basic instructions are:<\/p>\n

    \n
  1. Login in to http:\/\/dev.twitter.com\/apps<\/a><\/li>\n
  2. Create a new Twitter app and generate tokens.<\/li>\n
  3. Enter the token values in the corresponding fields on the Twitter Digest option page<\/li>\n<\/ol>\n

    Finally, I\u2019m no expert on Twitter authentication or oAuth, but it seems you only need one set of tokens if you are running multiple website with digesting multiple Twitter feeds, as long as the tokens you use on the plugin are associated with a Twitter account that has access to the Twitter account you want to digest. For example, if you create the authentication tokens for @a and @a follows @b, then based on my cursory testing, it appears you don\u2019t need a Twitter App or authentication tokens associated with @b to digest @b. Just put \u2018b\u2019 in \u2018Username\u2019 option field on the Twitter Digest option page and it should work. Like I said though, @a has to be following @b.<\/p>\n

    Let me know if anything fails and thanks for the feedback.<\/p>\n<\/div>\n