Re: user_timeline limits
Hello Alex, Can the same thing be said for any other (public) user? I mean, should it only be possible the get all of your own tweets or should you be able to get all tweets from any public user? Kind regards, Koen. On Oct 21, 5:50 pm, Alex Payne [EMAIL PROTECTED] wrote: It's a bug that you can't get all of your own tweets, regardless of how far back. You're right that the archive via the Search API is a moving target, but it's our intention to provide user timelines to their owners going as far back as necessary. On Tue, Oct 21, 2008 at 3:00 AM, TCI [EMAIL PROTECTED] wrote: Alex, How about the question for retrieving older tweets? Summize does have some more history than Archive, but I guess we cannot count on these retention times as you are growing quickly! Rafa On Oct 20, 11:50 am, Alex Payne [EMAIL PROTECTED] wrote: Looks like we've got some bugs here, as neither of these behaviors/limitations are intentional. Please file issues athttp://code.google.com/p/twitter-api/issues/entryandwe'll get them taken care of. On Sat, Oct 18, 2008 at 3:46 AM, Phil Gyford [EMAIL PROTECTED] wrote: Hi, I'm trying to archive all my twitters to a local database. I'm using user_timeline but have hit a couple of problems. First, if I set the 'count' parameter to the maximum of 200 and ask for 'page' 2, then it doesn't fetch back tweets 201-400, but instead fetches tweets 21-220. So 'count' does not affect the number of tweets on a 'page'. So if you set the count to 200 and request several incrementally numbered pages, then you're soon only getting 20 new tweets each time, plus 180 you've had before. There doesn't seem much point in being able to set the count higher than 20 unless you're only fetching page 1. Is this normal? Second, I can't fetch tweets further back than page 41 (with 20 tweets per page), which is also as far back as I can go on the website. Is there any way to fetch tweets older than this? If not, will there be? I'd really like to make a local copy of my tweets but can't see how to do so at the moment. Many thanks, Phil -- Alex Payne - API Lead, Twitter, Inc.http://twitter.com/al3x -- Alex Payne - API Lead, Twitter, Inc.http://twitter.com/al3x
Re: Are there threads for replies to the same tweet?
There's not currently an API to see all replies to a given status, but it's something we're considering. In the meantime, you might be able to use the Search API to narrow down the potential set of tweets (you could search for replies to the username of the thread's originator), but you'd still have to do a bit of processing on your side. On Tue, Oct 28, 2008 at 8:12 PM, drupalot [EMAIL PROTECTED] wrote: In other words, if I wanted to view all the replies to a specific tweet, is there a way to do that? Is there a specific comment feed for each tweet? If not, is there a way I could work with the existing APIs to make put that together somehow? It looks like http://atanswerme.com is doing this, but not sure how. Any thoughts? -- Alex Payne - API Lead, Twitter, Inc. http://twitter.com/al3x
Re: Rate Limit For Mass POSTs
For one, you'll need to get your account whitelisted. POST requests aren't rate limited as a rule, but there are some rules around the number updates and direct messages one can send per day that apply whether you're using the API or the web site. Getting whitelisted lifts those limits. Beyond that, feel free to POST either serially or in parallel. Five at a time sounds perfectly reasonable. On Wed, Oct 29, 2008 at 4:28 PM, Tony Stubblebine [EMAIL PROTECTED] wrote: I'm building an app for managing large twitter accounts and have two desires. One, to be able to mass-follow a selection of people who are following me. Two, to send direct messages to all followers or to slices of my followers. These may bring up etiquette/user-expectation/ spam issues, but first I want to get a very specific RATE limiting question answered. The documentation says that POST requests are not limited. My test account has 4900 followers and 4600 unfollowed followers. Can I DM them in parallel? Serially? Five at a time? What's the polite thing to do here? Thanks, Tony http://www.stubbleblog.com http://www.crowdvine.com -- Alex Payne - API Lead, Twitter, Inc. http://twitter.com/al3x
Re: School Project
Sure. Email me off-list with the IPs you'll be requesting from and I can give you a couple different options. On Wed, Oct 29, 2008 at 3:51 PM, James [EMAIL PROTECTED] wrote: I'm currently in a graduate class about natural language processing. My partner and myself came up with a project to do opinion mining on tweets dealing with the election data. We would like to get an archive of the election.twitter.com feed. We have already wrote an application to retrieve the information we would like from search.twitter.com. We are only able to pull about 1 to 2 hours of data per day, hitting the 1500 tweet limit. We would like TONs of data that we believe Twitter already has. Is there a way we would be allow to query this information? -- Alex Payne - API Lead, Twitter, Inc. http://twitter.com/al3x
Re: Does direct_messages (Twitter API) support RFC 1123/RFC 822 date time format
We're pretty sure this isn't a bug on our end. It's come up before, and it's usually some client-side date formatting issue. We've got solid test coverage for it, too. On Wed, Oct 29, 2008 at 8:42 AM, krishnan chakravarthi [EMAIL PROTECTED] wrote: Thanks for the replies. I played around with Ruby 1.8.6 and date sent to Date.parse is now in the correct format: URL string: http://twitter.com/direct_messages.xml?since=Mon27Oct2008 (No Urlencoding is needed as there are no special characters or spaces) Ruby Check: irb(main):037:0 d8 = Date.parse(Mon27Oct2008) = #Date: 4909533/2,0,2299161 irb(main):038:0 d8.ctime() = Mon Oct 27 00:00:00 2008 Note: It is useless providing a time (hr:min:sec) as Date class ignores this and outputs date in the above format. Perhaps Twitter documentation could be updated to mention this or the API can switch to using Ruby DateTime class. I see a http code 302 (page redirect) returned from twitter. The expected results should be all direct messages sent to the authenticating user after Mon Oct 27. It looks like Ruby is generating the correct date but the API does not recognize the format?perhaps an API bug. On 10/28/08, Alex Payne [EMAIL PROTECTED] wrote: Any format that Ruby 1.8.6's Date.parse method can comprehend will be processed. On Tue, Oct 28, 2008 at 11:42 AM, krishnan chakravarthi [EMAIL PROTECTED] wrote: I changed the date format and it made no difference. I am using PHP urlencode method as shown below: direct_messages.xml?since=. urlencode(stripslashes(urldecode(Mon, 27 Oct 13:00:00 EST 2008))); The date/time format is as specified in RFC822. The urlencoded string is output as: Mon%2C+27+Oct+13%3A00%3A00+EST+2008 Note: %3A is encoding format for : (colon) symbol. Twitter returns a 302 return code. Not sure why Date.parse(CGI.unescape()) mangles the date string as urldecode/encode and cgi.escape/unescape work the same way and Date.parse should accept RFC822 compliant dates. What Ruby version is installed in development environment? Is there a specific format in which API expects date/time, to work with Date.parse method. On 10/27/08, Alex Payne [EMAIL PROTECTED] wrote: Your date does not appear to be properly CGI-encoded: Date.parse(CGI.unescape(Sun%2C+26+Oct+22%3:55%3:48+000+2008)) = Mon, 26 Oct 0022 That's what Ruby in our development environment thinks your date is. Those %3s might be the culprit. On Mon, Oct 27, 2008 at 2:01 PM, Kris [EMAIL PROTECTED] wrote: I am aware of the example in the documentation. Thanks for pointing it out and I apologize for not mentioning before that I had tried the format listed in the documentation. For example: $this-twitterHost .= direct_messages.xml?since=Sun%2C+26+Oct +22%3:55%3:48+000+2008; results in error number 502 (server busy) and Twitter is over capacity message. Not sure why the API does not throw a format error? I saw a post (http://groups.google.com/group/twitter-development-talk/ browse_thread/thread/e97f02c8b8012fb5) which mentions that the API conforms to RFC1123 but that does not work either. Any thoughts? Thanks On Oct 27, 4:35 pm, Damon Clinkscales [EMAIL PROTECTED] wrote: On Mon, Oct 27, 2008 at 1:48 PM, Kris [EMAIL PROTECTED] wrote: The API documentation does not clearly list the date format for obtaining direct_messages sent to a user (within the specified date/ time window). I am using RFC 1123/822 format but do not get any messages sent with in the specified date/time window: For Example: direct_messages.xml?since=.urlencode(Sun, 26 Oct 2008 22:00:00 EST) (does not return any messages or errors.) What is the correct date/time format? Has anyone used this successfully? Thanks Personally, I use since_id. But here's the documentation:http://apiwiki.twitter.com/REST+API+Documentation#DirectMessageMethods which contains this example: # since. Optional. Narrows the resulting list of direct messages to just those sent after the specified HTTP-formatted date, up to 24 hours old. The same behavior is available by setting the If-Modified-Since parameter in your HTTP request. Ex:http://twitter.com/direct_messages/sent.xml?since=Tue%2C+27+Mar+2007+... -damon --http://twitter.com/damon- Hide quoted text - - Show quoted text - -- Alex Payne - API Lead, Twitter, Inc. http://twitter.com/al3x -- Alex Payne - API Lead, Twitter, Inc. http://twitter.com/al3x -- Alex Payne - API Lead, Twitter, Inc. http://twitter.com/al3x
Re: Date followed?
Any word on this? I believe this is a repeat of several threads throughout this year and last that all never got answered. Alex - any word on when we can see this? I'd love some sort of communication so I can plan around it. It seems like a very simple update. Thanks, Jesse On Oct 29, 2008, at 2:13 AM, Jesse Stay wrote: What's the best way for me to figure out the date someone else followed me via the API? Is that provided in the followers feed? Jesse
Re: Rate Limit For Mass POSTs
Thanks Alex, What's the limit on DMs per day and is that something that can be whitelisted by IP? I guess whitelisting by IP wouldn't make much sense in a general case. The project I'm working on is going to live on the web and live both inside and outside of CrowdVine. For the inside CrowdVine part, it's for paying conferences doing things like sending updates when a session changes rooms. I can vouch for them. But for general usage, I wouldn't want to open up a loophole. Thx, Tony On Oct 29, 5:17 pm, Alex Payne [EMAIL PROTECTED] wrote: For one, you'll need to get your account whitelisted. POST requests aren't rate limited as a rule, but there are some rules around the number updates and direct messages one can send per day that apply whether you're using the API or the web site. Getting whitelisted lifts those limits. Beyond that, feel free to POST either serially or in parallel. Five at a time sounds perfectly reasonable. On Wed, Oct 29, 2008 at 4:28 PM, Tony Stubblebine [EMAIL PROTECTED] wrote: I'm building an app for managing large twitter accounts and have two desires. One, to be able to mass-follow a selection of people who are following me. Two, to send direct messages to all followers or to slices of my followers. These may bring up etiquette/user-expectation/ spam issues, but first I want to get a very specific RATE limiting question answered. The documentation says that POST requests are not limited. My test account has 4900 followers and 4600 unfollowed followers. Can I DM them in parallel? Serially? Five at a time? What's the polite thing to do here? Thanks, Tony http://www.stubbleblog.com http://www.crowdvine.com -- Alex Payne - API Lead, Twitter, Inc.http://twitter.com/al3x
Re: Does direct_messages (Twitter API) support RFC 1123/RFC 822 date time format
Alex, Would it be possible to share an example date that works in your environment (perhaps a test case)? I have tried a bunch of things at my end without much success. Any help is appreciated. Thanks Kris On Wed, Oct 29, 2008 at 8:32 PM, Alex Payne [EMAIL PROTECTED] wrote: We're pretty sure this isn't a bug on our end. It's come up before, and it's usually some client-side date formatting issue. We've got solid test coverage for it, too. On Wed, Oct 29, 2008 at 8:42 AM, krishnan chakravarthi [EMAIL PROTECTED] wrote: Thanks for the replies. I played around with Ruby 1.8.6 and date sent to Date.parse is now in the correct format: URL string: http://twitter.com/direct_messages.xml?since=Mon27Oct2008 (No Urlencoding is needed as there are no special characters or spaces) Ruby Check: irb(main):037:0 d8 = Date.parse(Mon27Oct2008) = #Date: 4909533/2,0,2299161 irb(main):038:0 d8.ctime() = Mon Oct 27 00:00:00 2008 Note: It is useless providing a time (hr:min:sec) as Date class ignores this and outputs date in the above format. Perhaps Twitter documentation could be updated to mention this or the API can switch to using Ruby DateTime class. I see a http code 302 (page redirect) returned from twitter. The expected results should be all direct messages sent to the authenticating user after Mon Oct 27. It looks like Ruby is generating the correct date but the API does not recognize the format?perhaps an API bug. On 10/28/08, Alex Payne [EMAIL PROTECTED] wrote: Any format that Ruby 1.8.6's Date.parse method can comprehend will be processed. On Tue, Oct 28, 2008 at 11:42 AM, krishnan chakravarthi [EMAIL PROTECTED] wrote: I changed the date format and it made no difference. I am using PHP urlencode method as shown below: direct_messages.xml?since=. urlencode(stripslashes(urldecode(Mon, 27 Oct 13:00:00 EST 2008))); The date/time format is as specified in RFC822. The urlencoded string is output as: Mon%2C+27+Oct+13%3A00%3A00+EST+2008 Note: %3A is encoding format for : (colon) symbol. Twitter returns a 302 return code. Not sure why Date.parse(CGI.unescape()) mangles the date string as urldecode/encode and cgi.escape/unescape work the same way and Date.parse should accept RFC822 compliant dates. What Ruby version is installed in development environment? Is there a specific format in which API expects date/time, to work with Date.parse method. On 10/27/08, Alex Payne [EMAIL PROTECTED] wrote: Your date does not appear to be properly CGI-encoded: Date.parse(CGI.unescape(Sun%2C+26+Oct+22%3:55%3:48+000+2008)) = Mon, 26 Oct 0022 That's what Ruby in our development environment thinks your date is. Those %3s might be the culprit. On Mon, Oct 27, 2008 at 2:01 PM, Kris [EMAIL PROTECTED] wrote: I am aware of the example in the documentation. Thanks for pointing it out and I apologize for not mentioning before that I had tried the format listed in the documentation. For example: $this-twitterHost .= direct_messages.xml?since=Sun%2C+26+Oct +22%3:55%3:48+000+2008; results in error number 502 (server busy) and Twitter is over capacity message. Not sure why the API does not throw a format error? I saw a post (http://groups.google.com/group/twitter-development-talk/ browse_thread/thread/e97f02c8b8012fb5) which mentions that the API conforms to RFC1123 but that does not work either. Any thoughts? Thanks On Oct 27, 4:35 pm, Damon Clinkscales [EMAIL PROTECTED] wrote: On Mon, Oct 27, 2008 at 1:48 PM, Kris [EMAIL PROTECTED] wrote: The API documentation does not clearly list the date format for obtaining direct_messages sent to a user (within the specified date/ time window). I am using RFC 1123/822 format but do not get any messages sent with in the specified date/time window: For Example: direct_messages.xml?since=.urlencode(Sun, 26 Oct 2008 22:00:00 EST) (does not return any messages or errors.) What is the correct date/time format? Has anyone used this successfully? Thanks Personally, I use since_id. But here's the documentation:http://apiwiki.twitter.com/REST+API+Documentation#DirectMessageMethods which contains this example: # since. Optional. Narrows the resulting list of direct messages to just those sent after the specified HTTP-formatted date, up to 24 hours old. The same behavior is available by setting the If-Modified-Since parameter in your HTTP request. Ex:http://twitter.com/direct_messages/sent.xml?since=Tue%2C+27+Mar+2007+... -damon --http://twitter.com/damon- Hide quoted text - - Show quoted text - -- Alex Payne - API Lead, Twitter, Inc. http://twitter.com/al3x -- Alex Payne - API Lead, Twitter, Inc. http://twitter.com/al3x -- Alex Payne - API Lead, Twitter, Inc. http://twitter.com/al3x
