[twitter-dev] Blocked users appear in the API, not in the website
Guys, I opened this bug about a year ago but it got lost in the bug tracking and I'm not in the mood to search that mess again. http://imgur.com/JTxm1.png As you can see, there is one tweet that appears in the application, but it doesn't appear in the website. The reason is that the author of the tweet (the original tweet, not the retweet) is blocked, which the website does it right and don't display it, but the message still appears in the API. And no, I'm not the author or am in anyway related to Nambu, but I had the same problem with my (now defunct) application. -- Julio Biason julio.bia...@gmail.com Twitter: http://twitter.com/juliobiason -- Twitter developer documentation and resources: http://dev.twitter.com/doc API updates via Twitter: http://twitter.com/twitterapi Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list Change your membership to this group: http://groups.google.com/group/twitter-development-talk?hl=en
Re: [twitter-dev] Blocked users appear in the API, not in the website
The API doesn't check for blocked users. You need to implement that manually. Tom On 9/8/10 6:45 PM, Julio Biason wrote: Guys, I opened this bug about a year ago but it got lost in the bug tracking and I'm not in the mood to search that mess again. http://imgur.com/JTxm1.png As you can see, there is one tweet that appears in the application, but it doesn't appear in the website. The reason is that the author of the tweet (the original tweet, not the retweet) is blocked, which the website does it right and don't display it, but the message still appears in the API. And no, I'm not the author or am in anyway related to Nambu, but I had the same problem with my (now defunct) application. -- Twitter developer documentation and resources: http://dev.twitter.com/doc API updates via Twitter: http://twitter.com/twitterapi Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list Change your membership to this group: http://groups.google.com/group/twitter-development-talk?hl=en
Re: [twitter-dev] Blocked users appear in the API, not in the website
On Wed, Sep 8, 2010 at 1:54 PM, Tom van der Woerdt i...@tvdw.eu wrote: The API doesn't check for blocked users. You need to implement that manually. So for every request for the user_timeline I need to request the list of blocked users, to have a proper list in case the user blocks someone in the website? That sounds incredible stupid. -- Julio Biason julio.bia...@gmail.com Twitter: http://twitter.com/juliobiason -- Twitter developer documentation and resources: http://dev.twitter.com/doc API updates via Twitter: http://twitter.com/twitterapi Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list Change your membership to this group: http://groups.google.com/group/twitter-development-talk?hl=en
Re: [twitter-dev] Blocked users appear in the API, not in the website
On 9/8/10 7:15 PM, Julio Biason wrote: On Wed, Sep 8, 2010 at 1:54 PM, Tom van der Woerdt i...@tvdw.eu wrote: The API doesn't check for blocked users. You need to implement that manually. So for every request for the user_timeline I need to request the list of blocked users, to have a proper list in case the user blocks someone in the website? That sounds incredible stupid. I'm not 100% about my last post. Anyway, the documentation says this about blocks : The block list should be cached locally - the change velocity is usually quite low. If possible, save the cache to disk to avoid polling for the block list upon startup. Timestamp the block list write time and only update perhaps as infrequently as every 6 to 24 hours. Tom -- Twitter developer documentation and resources: http://dev.twitter.com/doc API updates via Twitter: http://twitter.com/twitterapi Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list Change your membership to this group: http://groups.google.com/group/twitter-development-talk?hl=en
