[twitter-dev] API method for 'Remove user' functionality for a protected user
For a protected profile, on the followers page of Twitter web interface, there is an option to remove a user from followers list. Is there an API method which does the same function? There are friendships/create and friendships/destroy methods but nothing for approving/rejecting, removing followers. Any idea/ thoughts about API methods for managing followers? BTW, I guess there is one way you could remove a follower using API, by calling blocks/create and then blocks/destroy. Regards, Vinay. -- To unsubscribe, reply using remove me as the subject.
[twitter-dev] profile_image_url in old tweet is different from that in recent tweets
Hi, Have a look at profile_image_url in API response for @jack's first tweet at http://api.twitter.com/1/statuses/show/20.xml and any other recent tweet ( http://api.twitter.com/1/statuses/show/11000892805.xml ). The profile image url is different in these two tweets though they are for the same person, @jack. Does this mean that the profile_image_url is(was?) linked to a tweet (and not to user) ? Is this a known issue? I don't have any problem with tweets giving me old profile image url as long as they are valid and working. The profile image returned by tweet id 20 gives a 403 most of the time. Regards, Vinay. To unsubscribe from this group, send email to twitter-development-talk+unsubscribegooglegroups.com or reply to this email with the words REMOVE ME as the subject.
[twitter-dev] Re: 502 errors on user timelines
I am also facing the same issue, https://twitter.com/vsr/status/10199624984 On Mar 10, 3:09 am, Brendan brender...@gmail.com wrote: I've noticed that when trying to get the entire status timeline for some users (user ID 49777412 was one such user), requesting a page (say the first page) of 200 tweets results in a 502 error. Retrying the request a several seconds (5 seconds, in my case) later succeeds. When requesting the second page of statuses, it again fails, but a few seconds later it succeeds. It seems as though there's some caching issue happening in which the initial request will take too long to return so Twitter returns a 502 error, and by the time the second request happens the data has been retrieved and is ready to serve the request. How should I go about avoiding or reducing the occurrence of these errors? Thanks, Brendan
[twitter-dev] Re: Proper protocol for displaying user's avatar in an app
Doesn't http://twivatar.org solve it? On Nov 23, 9:12 am, Adam Green a...@vibemetrix.com wrote: I'm building a Web app that caches tweets and user info from the streaming API, and then displays all the tweets for a single user. At times up to 30 or 40 tweets from the same user are displayed on a page. I've been caching the profile image url I get back from the streaming API, and then using this URL in an img tag sent to the browser. So I am letting the user's browser pull it from the Twitter server as needed. I don't see anything in the API docs that warns against this, but sometimes I am getting an access denied XML back instead of the proper image. Is this a bug, or should I be downloading each user's avatar and serving it from my server instead? The image is being requested by the user's browser, so whilelisting the server's IP won't help. The access denied response is intermittent. Sometimes it happens after 5 requests for the same image, sometimes 30 appear with no problem. Sometimes a few appear, a few fail, and then the rest work. So it doesn't seem like rate limiting.
