Re: [twitter-dev] Search API for getting tweet counts by date?
Hi, The Search API only keeps it's index for about a week so searches older than that are not possible. To perform analysis of Tweets like you ask you will can monitor them as they happen through the Streaming API. Alternatively some third party services maybe able to offer this information. Best, @themattharris https://twitter.com/intent/follow?screen_name=themattharris Developer Advocate, Twitter On Thu, Jun 23, 2011 at 7:45 PM, jburke jmbu...@gmail.com wrote: If I want to get tweet counts (for a particular query) by date over a particular date range, does the search API support? Is the date range limited to the tight range that is in place for search that returns tweets? -- Twitter developer documentation and resources: https://dev.twitter.com/doc API updates via Twitter: https://twitter.com/twitterapi Issues/Enhancements Tracker: https://code.google.com/p/twitter-api/issues/list Change your membership to this group: https://groups.google.com/forum/#!forum/twitter-development-talk -- Twitter developer documentation and resources: https://dev.twitter.com/doc API updates via Twitter: https://twitter.com/twitterapi Issues/Enhancements Tracker: https://code.google.com/p/twitter-api/issues/list Change your membership to this group: https://groups.google.com/forum/#!forum/twitter-development-talk
Re: [twitter-dev] Search Api limit
Hi Alessandro,
We've produced a small guide on using search that explains the search rate
limits a little more.
You can find the page here:
https://dev.twitter.com/pages/using_search
In it we say:
The Rate Limits for the Search API are not the same as for the REST API.
When using the Search API you are not restricted by a certain number of API
requests per hour, but instead by the complexity and frequency.
As requests to the Search API are anonymous, the rate limit is measured
against the requesting client IP.
To prevent abuse the rate limit for Search is not published. If you are rate
limited, the Search API will respond with an HTTP 420 Error. {error:You
have been rate limited. Enhance your calm.}.
I hope that explains what is going on,
@themattharris https://twitter.com/intent/follow?screen_name=themattharris
Developer Advocate, Twitter
On Fri, Jun 24, 2011 at 2:08 AM, Alessandro alessandro.marrone...@gmail.com
wrote:
Hi
I'm using the search api (for example:
http://search.twitter.com/search.rss?q=%23juventusrpp=100page=4)
I read here: http://search.twitter.com/api/ this:
We do not rate limit the search API under ordinary circumstances,
however we have put measures in place to limit the abuse of our API.
If you find yourself encountering these limits, please contact us and
describe your app's requirements.
The limit seems random: sometimes I do 150 requests sometimes 300,
generally, after 5 minutes I can do other requests.
I was wondering if is it possible do more requests
--
Twitter developer documentation and resources: https://dev.twitter.com/doc
API updates via Twitter: https://twitter.com/twitterapi
Issues/Enhancements Tracker:
https://code.google.com/p/twitter-api/issues/list
Change your membership to this group:
https://groups.google.com/forum/#!forum/twitter-development-talk
--
Twitter developer documentation and resources: https://dev.twitter.com/doc
API updates via Twitter: https://twitter.com/twitterapi
Issues/Enhancements Tracker: https://code.google.com/p/twitter-api/issues/list
Change your membership to this group:
https://groups.google.com/forum/#!forum/twitter-development-talk
Re: [twitter-dev] Search API Rate Limiting
Hi, sounds like you really want to look into the streaming API instead. http://dev.twitter.com/pages/streaming_api_methods#statuses-filter cheers -m On Thu, Jun 2, 2011 at 1:00 PM, HRyba bhrdes...@gmail.com wrote: I'm developing an application that uses the Twitter Search API. The app searches Twitter for many (at least a couple thousand) specific keywords in real time. A server would be set up to get the results for the many keywords in tweets and store them in a database that the application would access to return the results, as opposed to every user searching for the keywords on their end every time. The problem is after a while I notice that Twitter stops responding with new results. Is Twitter caching the results after a set amount of requests I can make in a given time period? The FAQ section on the developer's wiki does not provide much info on the rate limiting of the Search API other than that it is generous. Do you guys have the inside scoop on the actual numbers? I see where to submit an application and the application is basically working, but my client hasn't finalized the details for the app like the name and url yet. Am I out of luck until I am ready to officially submit the application for whitelisting. If not, how can I get my application's server added to a whitelist to ensure that the tweets return from twitter are real-time? -- Twitter developer documentation and resources: https://dev.twitter.com/doc API updates via Twitter: https://twitter.com/twitterapi Issues/Enhancements Tracker: https://code.google.com/p/twitter-api/issues/list Change your membership to this group: https://groups.google.com/forum/#!forum/twitter-development-talk -- Twitter developer documentation and resources: https://dev.twitter.com/doc API updates via Twitter: https://twitter.com/twitterapi Issues/Enhancements Tracker: https://code.google.com/p/twitter-api/issues/list Change your membership to this group: https://groups.google.com/forum/#!forum/twitter-development-talk
Re: [twitter-dev] search api limit
Hi, Max, First of all, this is just from personal experience with my own application, so, take it with all the necessary grains of salt about rate limits changing based on traffic and time of day, your searches being different from mine, etc, etc. My experience has been that I tend not to run into trouble if I can stay under 20 search API requests per minute, and that if I do go over, I'm typically only rate-limited for a few minutes. So, if you can either reduce the frequency of your search calls to every 15 seconds instead of every 10, or can tolerate a few of them failing once in a while, you should be fine. You mention four different CPU's -- are they searching for different things? If so, you might consider just having one CPU do a single search request every 10 seconds, stringing the four original searches together with OR's -- I've had great success using this method to batch what would've been up to 50 different searches into a single API call. You mention an art installation -- if your problem is that you've got the software to put interesting twitter-driven graphics on one monitor with one CPU, but your installation needs four monitors, so, it's easiest to just run the same software on four different CPU's, I'd say this is exactly the kind of scenario where Twitter would encourage you to make more efficient use of the API calls. Were I in your shoes, I'd think about setting up one master server, which would run a script to search Twitter every 10 seconds and dump the resulting JSON into a flat file. The master would also be running Apache to serve that flat file up over HTTP, and any number of slave machines showing interesting graphics could hit your master server instead of Twitter. Other than changing what URL they hit for data, you wouldn't have to change the show-interesting-graphics code at all, since the master would be serving up the exact same data the slaves would've gotten from Twitter directly. Best of luck, -Alex On Thu, May 19, 2011 at 6:26 AM, Max maxdo...@googlemail.com wrote: Hello, for an art installation i will be having 4 cpus running the search twitter query (search.twitter.com) . because the rate limit is not made public, if you could authorize my proposed request frequency. if i have each computer (on the same IP adress) calling the search api every 10 seconds, that comes to 1440 calls per hour (from the same Ip adress) whilst also simultaneously running the sample stream (on each cpu) . would this be allowed? it would be between June 16th and June 24th, continuously during day time hours. thanks alot. max maxdo...@gmail.com -- Twitter developer documentation and resources: https://dev.twitter.com/doc API updates via Twitter: https://twitter.com/twitterapi Issues/Enhancements Tracker: https://code.google.com/p/twitter-api/issues/list Change your membership to this group: https://groups.google.com/forum/#!forum/twitter-development-talk -- Alex Feinberg CTO, Trak.ly http://trak.ly/ -- Twitter developer documentation and resources: https://dev.twitter.com/doc API updates via Twitter: https://twitter.com/twitterapi Issues/Enhancements Tracker: https://code.google.com/p/twitter-api/issues/list Change your membership to this group: https://groups.google.com/forum/#!forum/twitter-development-talk
Re: [twitter-dev] search api limit
Hey Max, That looks pretty extreme! What's your use case? Why would you need to make that much queries? Are you going to use the Search API or the website? If you're using the API, Did you consider using the Streaming API statuses/filter method with the track parameter? http://dev.twitter.com/pages/streaming_api_methods#statuses-filter All the best, Arnaud / @rno http://twitter.com/rno On Thu, May 19, 2011 at 6:26 AM, Max maxdo...@googlemail.com wrote: Hello, for an art installation i will be having 4 cpus running the search twitter query (search.twitter.com) . because the rate limit is not made public, if you could authorize my proposed request frequency. if i have each computer (on the same IP adress) calling the search api every 10 seconds, that comes to 1440 calls per hour (from the same Ip adress) whilst also simultaneously running the sample stream (on each cpu) . would this be allowed? it would be between June 16th and June 24th, continuously during day time hours. thanks alot. max maxdo...@gmail.com -- Twitter developer documentation and resources: https://dev.twitter.com/doc API updates via Twitter: https://twitter.com/twitterapi Issues/Enhancements Tracker: https://code.google.com/p/twitter-api/issues/list Change your membership to this group: https://groups.google.com/forum/#!forum/twitter-development-talk -- Twitter developer documentation and resources: https://dev.twitter.com/doc API updates via Twitter: https://twitter.com/twitterapi Issues/Enhancements Tracker: https://code.google.com/p/twitter-api/issues/list Change your membership to this group: https://groups.google.com/forum/#!forum/twitter-development-talk
Re: [twitter-dev] Search API not delivering popular tweets
I'm not aware of any issues and see popular tweets returned both when requested in mixed and popular-only modes: GET http://search.twitter.com/search.json?q=googleresult_type=mixed GET http://search.twitter.com/search.json?q=googleresult_type=popular Are you including the result_type parameter? @episod http://twitter.com/episod - Taylor Singletary On Sun, Mar 27, 2011 at 11:54 PM, Ana anap...@gmail.com wrote: Dear all Is it correct that the Twitter Search API is not delivering popular tweets at the moment (and within the last days)? Thank you very much, Ana -- 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 -- 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
Re: [twitter-dev] Search API: Secure profile image URLs
Hey Jacob, Valid SSL certificates are installed on si[0-5].twimg.com subdomains. On your SSL served pages, you could simply replace http://a; with https://si;. Example for the @twitter account: - HTTP: http://a3.twimg.com/profile_images/1124040897/at-twitter_normal.png - HTTPS: https://si3.twimg.com/profile_images/1124040897/at-twitter_normal.png Arnaud / @rno On Tue, Mar 22, 2011 at 4:37 PM, Jacob jacob.h.p...@gmail.com wrote: Our application can sometimes be rendered within an HTTPS URL. To avoid mixed security content warnings in browsers, we were able to selectively convert our search API calls so they use HTTPS. However, the profile image URLs returned by the search API are HTTP URLs, and changing the protocol to HTTPS doesn't work (it seems like the image servers don't support HTTPS). This causes a mixed content warning when we render those URLs as HTML images. I would be OK with us having mixed content, but IE8 is particularly bad at how it confronts users with this condition. Is there way for me to create an HTTPS user profile image URL that works? -- 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 -- 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
Re: [twitter-dev] Search API: Secure profile image URLs
That worked perfectly. Thanks a whole lot! On Wed, Mar 23, 2011 at 08:38, Arnaud Meunier arn...@twitter.com wrote: Hey Jacob, Valid SSL certificates are installed on si[0-5].twimg.com subdomains. On your SSL served pages, you could simply replace http://a; with https://si. Example for the @twitter account: - HTTP: http://a3.twimg.com/profile_images/1124040897/at-twitter_normal.png - HTTPS: https://si3.twimg.com/profile_images/1124040897/at-twitter_normal.png Arnaud / @rno On Tue, Mar 22, 2011 at 4:37 PM, Jacob jacob.h.p...@gmail.com wrote: Our application can sometimes be rendered within an HTTPS URL. To avoid mixed security content warnings in browsers, we were able to selectively convert our search API calls so they use HTTPS. However, the profile image URLs returned by the search API are HTTP URLs, and changing the protocol to HTTPS doesn't work (it seems like the image servers don't support HTTPS). This causes a mixed content warning when we render those URLs as HTML images. I would be OK with us having mixed content, but IE8 is particularly bad at how it confronts users with this condition. Is there way for me to create an HTTPS user profile image URL that works? -- 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 -- 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
Re: [twitter-dev] Search API: retrieve the number of times a particular URL was tweeted?
Hi Doug, We don't have a search result counting API available at this time. One approach would be to prepare ahead of time and use the Streaming API's track filter on the URL you're interested in, keeping the stream open and counting tweets featuring your URL as it spreads on Twitter. http://dev.twitter.com/pages/streaming_api_methods#track Taylor @episod http://twitter.com/episod - Taylor Singletary - Twitter Developer Advocate On Tue, Mar 22, 2011 at 7:13 AM, doug douglas.r...@gmail.com wrote: The Facebook API has a FQL query that allows one to retrieve the number of Likes or Shares a particular URL got. I can certainly find a way to use the Twitter Search API to retrieve the raw statuses that mention a particular URL... but it seems like overkill when all I would like is the count... the number of statuses that mention that URL. Is there a way to simply retrieve _just_ the count of URL mentions? Thanks, Doug -- 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 -- 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
Re: [twitter-dev] Search API: retrieve the number of times a particular URL was tweeted?
Hi Doug, Tweetmeme have an API that can give you this info. http://help.tweetmeme.com/2009/04/07/api-documentation/ -Stuart -- Stuart Dallas 3ft9 Ltd http://3ft9.com/ On Tuesday, 22 March 2011 at 14:13, doug wrote: The Facebook API has a FQL query that allows one to retrieve the number of Likes or Shares a particular URL got. I can certainly find a way to use the Twitter Search API to retrieve the raw statuses that mention a particular URL... but it seems like overkill when all I would like is the count... the number of statuses that mention that URL. Is there a way to simply retrieve _just_ the count of URL mentions? Thanks, Doug -- 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 -- 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
Re: [twitter-dev] Search API: Can the geocode param only give me lat/long results?
Streaming API will give what you need through locations method. http://dev.twitter.com/pages/streaming_api_methods#locations On Mon, Mar 21, 2011 at 12:22 PM, Stu stuart.batter...@gmail.com wrote: Hi, I have a pre-question before my question. With the search API's geocode based search, if it falls back on the user's profile information does it use GPS positions in their profile or some location such as 'London'. The problem is that I need much greater precision than that. Thus, if I perform this search: http://search.twitter.com/search.json?geocode=51.53,-0.14,1mi Am I able to get results back that only contain lat/long values of the tweet? The json returned here has basically no values for 'geo'. Thanks S. -- 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 -- 氣 -- 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
Re: [twitter-dev] Search API uses different pool of user ids?
* ce conor.e...@gmail.com [110228 12:01]: A totally different user! There appears to be no way to get the proper numerical id from the search API. Am I doing something wrong or is this a known issue and I should just rewrite to use their screen name to look up users instead? See the Warning here: http://dev.twitter.com/doc/get/search -Marc -- 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
Re: [twitter-dev] Search API http response code 500
Hey Zaver, Repeating the query should work. If the error is persistent let us know what the term is so we can take a look. Best, @themattharris On Feb 25, 2011, at 10:09, zaver zave...@hotmail.com wrote: Hello, I ve been getting a 500 response code lately on searching some keywords. How do i handle that code? Any help is greatly appreciated. Zaver -- 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 -- 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
Re: [twitter-dev] Search API from_user_id doesn't match up with the proper Twitter user_id
I'm sure Taylor or Matt will reply politely to this rant. I don't work for Twitter, so I'd like to take on your attitude of entitlement directly towards this free service. Your basic approach can be summed up as How dare Twitter have problems in a totally free API that I can use to build a business on! First of all, this service is free, second there is an easy workaround for this. - You collect the tweets from the search API and store the user name, which is delivered correctly, along with the tweet info. You also get the avatar image. So you have enough now to display the tweet. - You then run a background process which waits until you have 100 user names, and requests their correct user info from the REST API. This can be stored in a separate user table. - This same process goes back to the tweets and updates each one with the correct user id. - You now have a valid relational database with a table for tweets, and a table for users. While this isn't perfect, it isn't hard to do either. At 100 users per request, and as long as you only request data for users you haven't seen before, there is no problem back filling this user data within the rate limits. Now, back to your attitude. The Twitter API is free. I agree that they should fix search, but it is acquired code, and my bet is that they want to rewrite it rather than patch it. The real point is that it is free. It is not a right granted to you to always have perfect code delivered to you. Twitter benefits from you writing code against there API, and you benefit from getting the data for free. Be grateful. Chill. On Wed, Dec 22, 2010 at 9:42 AM, Corey Ballou ball...@gmail.com wrote: I just wanted to bring group-wide awareness to the fact that search results from Twitter do not return an actual user_id. This has been a known defect (and yes, I do believe it's a *very large* defect) going on over 2 years now. This is a call to arms to get this shit fixed. I can't believe it's marked as an enhancement. There's nobody else to blame for providing a return param of from_user that doesn't actually map to an actual user. For those of us storing relational data, you're costing precious API calls for those users who are still utilizing the search API. The streaming API is not sufficient for all use cases, so that's not a valid answer. Below is the direct link to the issue tracker. https://code.google.com/p/twitter-api/issues/detail?id=214 -- 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 -- Adam Green Twitter API Consultant and Trainer http://140dev.com @140dev -- 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
Re: [twitter-dev] Search API from_user_id doesn't match up with the proper Twitter user_id
I think twitter's response to this call to arms should be the HTTP Status Code: 420 - Chill ;-} -- 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
Re: [twitter-dev] Search API cURL strangeness
And your UserAgent is? Tom On 12/14/10 5:02 PM, Brian Medendorp wrote: I'm building an application that uses the search API to check for data related to particular domains, and suddenly (within the last week or so), I have started to experience a strange problem. Some of my requests are coming back with a cURL error Empty reply from server, but only when I am searching for a specific set of domains (all of the other domains work fine). I wrote a small test script to try and track down the problem, and it seems that the UserAgent I am setting with cURL seems to be causing the problem (or part of the problem). If I change the UserAgent to anything else, I get a normal response. I remember reading in the documentation that Twitter expects a unique UserAgent for the application, so that's what I did, but that seems to be causing problems. This seems like it's likely some sort of blacklist problem, but I can't figure out why it would work in this manner (only blocking a small subset of my queries, and not IP-based). Here are some sample queries I am trying to cURL: http://search.twitter.com/search.json?q=batteryoperatedcandles.netrpp=100since_id=9431322892177408since=until= http://search.twitter.com/search.json?q=carnationbreakfastessentials.comrpp=100since_id=since=2010-12-14until= http://search.twitter.com/search.json?q=apple.comrpp=100since_id=since=2010-12-14until= The first two don't work unless I change my UserAgent to something else, but the last one works no matter what. -- 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
Re: [twitter-dev] Search API - Show From user but not @replies
Hi Dan, Search is fairly basic in it's use of operators so the query you are trying to do isn't possible. If all you really want is a users timeline have you tried: http://api.twitter.com/1/statuses/user_timeline.json?screen_name=username_you_want This will give you all tweets sent by a particular user. There is also a new flag for timelines which you can add that will exclude replies: http://api.twitter.com/1/statuses/user_timeline.json?screen_name=username_you_wantexlude_replies=true Hope that helps, @themattharris On Thu, Sep 23, 2010 at 10:02 AM, Dan d...@d4nz.net wrote: Is it possible using a search query to show tweets from a user but not include their @ replies? I can see that it's possible to negate a query (such as @user) but not possible to use a wildcard (to negate all @users) so how could you do this? -- 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 -- Matt Harris Developer Advocate, Twitter http://twitter.com/themattharris -- 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
Re: [twitter-dev] Search API
Hi Travis, The Search API's corpus of tweets is a rolling window that generally only goes back about 5 days, sometimes less depending on tweet velocity. We hope to some day offer a much larger pool of tweets for searching. Taylor On Thu, Sep 16, 2010 at 10:50 PM, Travis Beauvais tbeauv...@gmail.comwrote: I have been experimenting with the search API and every search I try only goes back to Spet 12 (calls being made on Sept 16). No matter how many results there are it always stops on Sept 12. Is there a limit I don't know about? -- 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 -- 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] search api - since date format
Hi Arian, A date string really is the only valid format for this function. If you want to cut the search off by certain times of day, you're best off post-processing your results for that kind of resolution. Thanks, Taylor On Thu, Sep 9, 2010 at 8:15 AM, arian arianpasqu...@gmail.com wrote: hi guys, I have a question about search api about 'until' parameter to be more exactly according to documentation until is Optional. Returns tweets generated before the given date. Date should be formatted as -MM- DD. example: http://search.twitter.com/search.json?until=2010-03-28; I need to know if its possible to set datetime, for example http://search.twitter.com/search.json?until=2010-09-08-19:00; or something like this. according to doc date should be formatted as -MM-DD, but I need inform time, if its possible what would be the string format in this case? is it possible? or how could I get a similar result? Arian -- 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 -- 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] Search API not returning tweet
When I run your queries above I see, in both cases, the Tweet from monkeyhelpr. When you ran the queries it may have been the Tweet was new and the caching on search.twitter.com hadn't fully updated. If you need real-time results you may want to consider using the Streaming API. The query you are running in Search can be applied to the Streaming API and will mean you see all the public Tweets from those users as soon as they happen. You can learn more about the Streaming API on our developer resources site: http://dev.twitter.com/pages/streaming_api Best, Matt On Thu, Aug 26, 2010 at 1:18 AM, Rob Lee r...@rjlee.net wrote: I'm trying to understand why this query doesn't return a tweet : http://search.twitter.com/search.json?q=%23tea%20from:jamesb%20from:frankieroberto%20from:andrewpendrick%20from:monkeyhelpr%20from:topfife But this one does : http://search.twitter.com/search.json?q=%23tea%20from:jamesb%20from:frankieroberto%20from:andrewpendrick%20from:monkeyhelpr%20from:urbanwide The only difference seems to be changing the from:topfife account to from:urbanwide, the returned tweet is from the monkeyhelpr account, so changing the final from:account shouldn't make a difference as far as I'm aware. -- 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 -- Matt Harris Developer Advocate, Twitter http://twitter.com/themattharris -- 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] Search API problems...
There are no known issues with search and running your query works for me. Hey Ben, The Search API does not use authentication and is rate limited differently to the 150 IP requests allowed on the REST API. If you are rate limited on the Search API we would return an error telling you rather than not reply. If the atom link is still not responding can you try http://search.twitter.com/search.json?q=test and let us know the result? Thanks, Matt On Tue, Aug 24, 2010 at 4:28 PM, Ben goo...@iamben.co.uk wrote: Hey guys - I'm curious as to know whether there's any problems with the search API? I'm curling from a PHP script, and it keeps timing out with 'couldn't connect to host' errors when my URL is a search (eg: http://search.twitter.com/search.atom?q=test). Interestingly, if I curl either of the following: http://api.twitter.com/1/help/test.xml http://api.twitter.com/1/account/rate_limit_status.xml ...and it doesn't time out, I get a true, and my rate limit is 150/150. I'm not using any authentication, this is a straight request from a script. Could I be on an IP blacklist for search (can I check this?)? I've been pretty careful with my caching, I make nowhere near 150 requests an hour, although my site is on a shared server, so it's entirely plausible someone else has been hammering it. Although if that was the case, would something not show up on the odd times I actually get the rate limit to show something? If anyone can help, or point me in the direction of something I've missed, I'd be eternally grateful... ben -- 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 -- Matt Harris Developer Advocate, Twitter http://twitter.com/themattharris -- 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] Search API issue involving server cookies
Hi Mike,
Thanks for reporting this bug, I'm able to reproduce and I'll report it to
the team.
Thanks!
Taylor
On Wed, Aug 4, 2010 at 5:35 PM, Mike Ward m...@blueonionsoftware.comwrote:
There appears to be an issue with Twitter's API and cookies. The
following yields no results found:
GET http://search.twitter.com/search.json?q=%23tweetz HTTP/1.1
Accept: */*
Accept-Language: en-us
Content-Type: application/x-www-form-urlencoded
UA-CPU: AMD64
Accept-Encoding: gzip, deflate
User-Agent: Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 6.1; Win64;
x64; Trident/4.0; .NET CLR 2.0.50727; SLCC2; .NET CLR 3.5.30729; .NET
CLR 3.0.30729; Media Center PC 6.0; Tablet PC 2.0; .NET4.0C; .NET4.0E)
Host: search.twitter.com
Connection: Keep-Alive
Cookie: k=68.40.12.103.1280961938551221; guest_id=128035711958013764;
lang=en;
_twitter_sess=BAh7CDoPY3JlYXRlZF9hdGwrCJWulT8qASIKZmxhc2hJQzonQWN0aW9uQ29u
%250AdHJvbGxlcjo6Rmxhc2g6OkZsYXNoSGFzaHsABjoKQHVzZWR7ADoHaWQiJWQ3%250AMWIxNzJlZmUzNThmM2Y1NGRkYzYwZTRjZmM1YmNh--0871d612503b63999c65c8c6abefb83f6bed9643
The response is:
HTTP/1.0 200 OK
Date: Thu, 05 Aug 2010 00:32:14 GMT
Server: hi
Status: 200 OK
X-Served-From: sjc1r085
X-Runtime: 0.02556
Content-Type: application/json; charset=utf-8
X-Timeline-Cache-Hit: Hit
X-Served-By: sjc1v012.prod.twitter.com
Cache-Control: max-age=15, must-revalidate, max-age=300
Expires: Thu, 05 Aug 2010 00:37:14 GMT
Content-Length: 251
Vary: Accept-Encoding
X-Varnish: 2325786061
Age: 0
Via: 1.1 varnish
X-Cache-Svr: sjc1v012.prod.twitter.com
X-Cache: MISS
Connection: close
{results:[],max_id:20340216330,since_id:
20294384707,refresh_url:?since_id=20340216330q=
%23tweetz,results_per_page:15,page:1,completed_in:
0.017987,warning:adjusted since_id to 20294384707 due to temporary
error,query:%23tweetz}
Issue the same request without the cookies and search returns expected
results.
I can't remove the cookies since they're server issued (I'm running in
a browser). Is there a workaround?
Re: [twitter-dev] Search API rate limit
Hi Shan, The Search API is anonymous so authenticating makes no difference to the rate limit there. If you are requesting a lot of information from the search API you may want to look at the streaming API instead: http://dev.twitter.com/pages/streaming_api The majority of search cases can be handled by the default filter limits available through the streaming API. Best, Matt On Tue, Jul 6, 2010 at 7:31 AM, Ramanean shang...@gmail.com wrote: I am developing a normal twitter search application Inorder to beat the search rate limit if I ask a user to authenticate whether that would be helpful? Whether the calls made by the user for search api will be counted in the user's account ? or whether that would be still counted as a call from the IP address of the website? I am little bit confused here... Thanks Shan -- Matt Harris Developer Advocate, Twitter http://twitter.com/themattharris
Re: [twitter-dev] Search API returns only 15 results, even if rpp=100?
Try a less complex query, and you should get more results. On Mon, Jun 21, 2010 at 8:39 PM, Josh Santangelo j...@endquote.com wrote: For example, this query: https://search.twitter.com/search.atom?q=microsoft+OR+#ms+OR+lnk.ms+OR+msft+OR+#surfacepage=1rpp=100result_type=recent Is there any way to get a larger number of results per page? thanks, -josh
Re: [twitter-dev] Search API returns only 15 results, even if rpp=100?
There are plenty of results for this, but your url is encoded incorrectly http://search.twitter.com/search.atom?q=microsoft+OR+%23ms+OR+lnk.ms+OR+msft+OR+%23surfacerpp=100 # is %23 in url-encoded form As the query exists it is microsoft OR with a page reference. Jonathan On Tue, Jun 22, 2010 at 6:34 AM, John Kalucki j...@twitter.com wrote: Try a less complex query, and you should get more results. On Mon, Jun 21, 2010 at 8:39 PM, Josh Santangelo j...@endquote.com wrote: For example, this query: https://search.twitter.com/search.atom?q=microsoft+OR+#ms+OR+lnk.ms+OR+msft+OR+#surfacepage=1rpp=100result_type=recent Is there any way to get a larger number of results per page? thanks, -josh
Re: [twitter-dev] search api :slowdown or throttling?
Hi Jeff, We've been having some general performance issues recently ( http://status.twitter.com/ ). If you're a heavy user of the search API, you may be better served by our Streaming API ( http://apiwiki.twitter.com/Streaming-API-Documentation ). Taylor Singletary Developer Advocate, Twitter http://twitter.com/episod On Thu, May 20, 2010 at 6:44 AM, Jeffrey Greenberg jeffreygreenb...@gmail.com wrote: Our app uses the search api extensively and we've noticed that the response time has fallen dramatically for aggregates of search requests in the past days . Is that really the case? Our production app is using basic auth at the moment, and we're wondering if that's a factor in this? jeffrey greenberg
Re: [twitter-dev] Search API or Streaming API?
If you are going to build a search engine, you'll need all of the Tweets to search over them. For this, you'll want to take the Firehose of all public statuses. http://apiwiki.twitter.com/Streaming-API-Documentation You'll need a commercial data license to do this. Email api to get started. GAE currently does not allow standing connections to the Streaming API. Also, you'll need considerably more resources than GAE to build a search engine. You'll need dozens of cores and hundreds of spindles just to get started. -John Kalucki http://twitter.com/jkalucki Infrastructure, Twitter Inc. On Sun, May 2, 2010 at 5:28 AM, nischalshetty nischalshett...@gmail.com wrote: I plan to build a search engine which would utilize the search APIs. Should I be using the Twitter Search API or the Streaming API to do the same? What is the difference between the two and would the Streaming API work on the Google App Engine?
Re: [twitter-dev] Search API - from:xxx not returning @ replies
The API worked for me. http://hurl.it/hurls/b038fc2feab35f899dad30dc3d30de8b310b8520/016284e356b27667be31737e2aeb7d6593ea87dc On Thu, Apr 29, 2010 at 11:39, mikawhite mikawh...@me.com wrote: Thursday 2010.04.29 - 11:33am PDT Search API : No posted @ replies are found I tried from:comcastbonnie from:al3x from:raffi Search web is OK. -- Abraham Williams | Developer for hire | http://abrah.am @abraham | http://projects.abrah.am | http://blog.abrah.am This email is: [ ] shareable [x] ask first [ ] private.
Re: [twitter-dev] Search API - 420 increase at 17:01 PDT
420 is a rate limit. Are you in shared hosting or have you changed the access pattern? On Wed, Apr 14, 2010 at 7:24 PM, mikawhite mikawh...@me.com wrote: The Search API is returning 420 code this afternoon. Did something change at twitter? To my knowledge, nothing has changed at my location. -- To unsubscribe, reply using remove me as the subject.
Re: [twitter-dev] Search API...searching for videos
Repeated automated queries like this should be done on the Streaming API. You can track on words like youtube to grab various domains, track on keywords that indicate a video URL extension, or, you could apply for the Links stream and process all links however you'd like. You should not start off by hitting the Search API. In most cases, your results will be filtered for relevance. In the one case where relevance is turned off -- soon it will be turned on. -John Kalucki http://twitter.com/jkalucki Infrastructure, Twitter Inc. On Fri, Mar 12, 2010 at 5:57 PM, eco_bach bac...@gmail.com wrote: Hi Currently in beta and viewable at http://www.tweetmasher.com, I am building a Twitter search application and slowly adding new features. One thing I would like to add is the ability to search for video links. Can anyone offer suggestions on what I would use in my search query? I assume the links would be mostly youtube videos.
Re: [twitter-dev] search api problem
Have a look at the Streaming API. [1] You can open a connection and count through every thousand results. Abraham [1] http://apiwiki.twitter.com/Streaming-API-Documentation On Mon, Mar 1, 2010 at 04:17, enes akar enesa...@gmail.com wrote: Hello; I want to find when the publish time of 1000th tweet that contains word 'love'. So I make the following query. http://search.twitter.com/search.atom?rpp=1page=1000q=love But the results are instable. Sometimes, the result is the tweet that is just 10 minutes ago from now. (this result is logical) Sometimes, the result is the tweet that is 7-8 hours ago from now. (this is not logical) I tried to use max_id to fix the results. But again for different max_id, the interval between published_time are very instable. Are not the search results ordered by published time? Extra note, I see this problem only the words with heavy usage like 'love', 'yes'. Search queries for specisific searches are stable and logical. -- Enes Akar http://www.linkedin.com/pub/enes-akar/7/835/3aa -- Abraham Williams | Community Advocate | http://abrah.am TwitterOAuth | http://github.com/abraham/twitteroauth This email is: [ ] shareable [x] ask first [ ] private.
Re: [twitter-dev] Search API rate limit IP address question
On 2 March 2010 14:05, eys eddiey...@yahoo.com wrote: Hello there! I have two questions: First, I received an approval for whitelisting for my server's IP address (as in, the IP number that I see when I log onto my webhosting account). I'm currently building my application in Flash using AS3 and after I've tested my project a few times, I'll get this error: Error #2032: Stream Error...[my search request] I assume this is rate limiting in action? If this were true then sometimes your request works and other times it doesn't. Is that the case? I read on this discussion board that whitelisting doesn't affect Search API. Does this mean I will always be limited to some arbitrary (unpublished) search limit? Then, I noticed the IP address used for the GET request is the IP address of the computer I'm using, NOT the IP address of my web server. How is this happening even though I'm using a proxy installed on my web server? Shouldn't the call be made from the server, not the computer? There are multiple requests happening here. I assume the following, which may or may not be correct: - From your browser you call your app - Your app runs some call through the twitter API - Twitter servers process the call and send it back to your app - Your app returns processed code back to your browser From the above processes your IP address is passed through by the Twitter API to the twitter service. I'd suggest try running your request from a completely different network and see what happens. Thank you. I'm pretty new at developing applications, so any help or advice is greatly appreciated! -- Charles A. Lopez charlesalo...@gmail.com What's your vision for your organization? What's your biggest challenge? Let's talk. (IBM Partner)
Re: [twitter-dev] Search API..receiving the refresh_url
If you are performing repeated automated searches and/or looking for low-latency results, you should be using the Streaming API. http://groups.google.com/group/twitter-api-announce/browse_thread/thread/c8c713bb63fac24c -John Kalucki http://twitter.com/jkalucki Infrastructure, Twitter Inc. On Tue, Feb 23, 2010 at 8:55 AM, eco_bach bac...@gmail.com wrote: Hi If you do a search from the official twitter search page, every 10-20 seconds or so, you receive a json response with a refresh_url. I'm building my own Twitter search appliance and want to incorporate this feature. How can I receive this refresh url after every search and is there a way to change the interval that it updates?
Re: [twitter-dev] search api and until parameter
Search results are kept for a fairly short period of time... definitely not a full month. This URL http://search.twitter.com/search.json?q=googleuntil=2010-02-20 Does return results. ---Mark http://twitter.com/mccv On Tue, Feb 23, 2010 at 1:04 AM, enes akar enesa...@gmail.com wrote: Hi; Is there a date limit for until parameter in search API? Is so what is it? For example following gives nothing. http://search.twitter.com/search.atom?q=googleuntil=2010-01-21 -- Enes Akar http://www.linkedin.com/pub/enes-akar/7/835/3aa
Re: [twitter-dev] Search API and total number of matches
Nope. You can iterate and count them yourselves but you will be limited to the results Search returns. Abraham On Wed, Feb 17, 2010 at 19:12, eco_bach bac...@gmail.com wrote: Hi You determine the number of tweets per age using the 'rpp' query parameter, with a maximum of I believe, 100 tweets per page, but is there also a way to determine the total number of 'matches' for a given search query? -- Abraham Williams | Community Advocate | http://abrah.am Project | Out Loud | http://outloud.labs.poseurtech.com This email is: [ ] shareable [x] ask first [ ] private. Sent from Seattle, WA, United States
Re: [twitter-dev] Search API Irregularity
http://help.twitter.com/forums/31935/entries/66018 not all tweets are guaranteed to be in search. on top of this, i highly don't recommend using the search API for this, and instead, use the streaming API. On Sat, Feb 13, 2010 at 11:24 AM, TimeSnag wmulli...@me.com wrote: I am a college student working on a project that requires me to capture all (or as many as possible) retweets and store them in a database. I currently have a script setup to search for RT and return 100 results per page. What I have discovered is that sometimes, the results are a random sample of the results. Other times, it will actually return all the tweets. I know this because when the results are correct, it will return about 30-40 tweets that match my search result in each second. So the time difference between the top tweet and bottom tweet is about 3 seconds. This seems to be correct. Other times.. it will return about 1-2 tweet each second and show me about 1 minute worth of tweets. Can someone tell me why the API will sometimes randomly display all the tweets and sometimes display only a select few? -- Raffi Krikorian Twitter Platform Team http://twitter.com/raffi
Re: [twitter-dev] Search API domain
Yes I have been using the search.twitter.com domain for all the search methods in my library. It was just brought up in a ticket that some of the search methods do work on api.twitter.com. This does appear to be true after some testing, so I thought maybe Twitter was finally merging the two API's together. Thank you for clearing this up. I will continue using the two separate domains search.* and api.* in my library. Josh On Sun, Jan 31, 2010 at 10:41 AM, Raffi Krikorian ra...@twitter.com wrote: please check out http://apiwiki.twitter.com/Twitter-API-Documentation - it lists the full domain and URL you should be using for all calls. in general, all the timeline, status, user related methods are on api.twitter.com, and search related methods are on search.twitter.com. the exception comes with trends: the trends api which has local trends and global trends is on api.twitter.com; the original trends information (global trends, daily global trends, weekly global trends) are on search twitter.com. On Sat, Jan 30, 2010 at 2:05 PM, Josh Roesslein jroessl...@gmail.com wrote: Hello, I have discovered that the search methods search and trends seem to work okay with the domain api.twitter.com. But the methods trends/current, trends/daily, and trends/weekly return 401's. They only appear to work correctly on the search.twitter.com. I have opened an issue here [1]. Will all search methods eventually work on the api.twitter.com domain? Thanks. Josh [1] http://code.google.com/p/twitter-api/issues/detail?id=1413 -- Raffi Krikorian Twitter Platform Team http://twitter.com/raffi
Re: [twitter-dev] Search API domain
merging the two is still high on the list -- we're unfortunately not there yet... On Sun, Jan 31, 2010 at 8:57 AM, Josh Roesslein jroessl...@gmail.comwrote: Yes I have been using the search.twitter.com domain for all the search methods in my library. It was just brought up in a ticket that some of the search methods do work on api.twitter.com. This does appear to be true after some testing, so I thought maybe Twitter was finally merging the two API's together. Thank you for clearing this up. I will continue using the two separate domains search.* and api.* in my library. Josh On Sun, Jan 31, 2010 at 10:41 AM, Raffi Krikorian ra...@twitter.com wrote: please check out http://apiwiki.twitter.com/Twitter-API-Documentation - it lists the full domain and URL you should be using for all calls. in general, all the timeline, status, user related methods are on api.twitter.com, and search related methods are on search.twitter.com. the exception comes with trends: the trends api which has local trends and global trends is on api.twitter.com; the original trends information (global trends, daily global trends, weekly global trends) are on search twitter.com. On Sat, Jan 30, 2010 at 2:05 PM, Josh Roesslein jroessl...@gmail.com wrote: Hello, I have discovered that the search methods search and trends seem to work okay with the domain api.twitter.com. But the methods trends/current, trends/daily, and trends/weekly return 401's. They only appear to work correctly on the search.twitter.com. I have opened an issue here [1]. Will all search methods eventually work on the api.twitter.com domain? Thanks. Josh [1] http://code.google.com/p/twitter-api/issues/detail?id=1413 -- Raffi Krikorian Twitter Platform Team http://twitter.com/raffi -- Raffi Krikorian Twitter Platform Team http://twitter.com/raffi
Re: [twitter-dev] search api results down by a factor of ten since Jan 15, 2010
Perhaps someone from Search can comment? In the mean time, please see: http://groups.google.com/group/twitter-api-announce/browse_thread/thread/c8c713bb63fac24c On Mon, Jan 18, 2010 at 2:37 AM, mikiobraun mikiobr...@googlemail.comwrote: Hello, you may have heard of twimpact.com. We are using the search api to get a filtered list of retweets only. We have just noticed that since January 15, 2010, about midnight UTC, the volume of results returned by the search API (JSON format) has gone down by about a factor of ten. I would like to ask whether this decrease is somehow connected to the suggested migration to the streaming API, or whether it's just us. Our system's user agent begins with twimpact/1.0, just in case. Best, Mikio Braun
Re: [twitter-dev] Search API suddenly stopped returning results for the same query
I'm seeing the 4 most recent statuses which is consistant with without since_id after 7452902654. Abraham On Fri, Jan 8, 2010 at 12:34, Aaron Rankin aran...@gmail.com wrote: Is anyone else seeing the Search API not returning results that it had been returning recently? For example, this query returned results consistently this morning and then recently stopped: http://search.twitter.com/search.json...@aaronrankinpage=1rpp=100since_id=7452902654 It works without the since_id. And, I'm not having a rate limiting issue. -- Abraham Williams | #doit | http://hashtagdoit.com Project | Intersect | http://intersect.labs.poseurtech.com Hacker | http://abrah.am | http://twitter.com/abraham This email is: [ ] shareable [x] ask first [ ] private. Sent from Madison, WI, United States
Re: [twitter-dev] Search API suddenly stopped returning results for the same query
Hello, Is there a way to search for a specific user using their email address on twitter.com? Either through the interface, or using the API. I don't want to give twitter the login to my account (gmail,hotmail,yahoo). I don't like the idea of 3rd party parsing through my contact list to find my friends on the network. Thanks mon.
Re: [twitter-dev] Search API: rate limit response code not changing 12/16
Don't forget to update the changelong :-P Abraham On Tue, Dec 15, 2009 at 18:43, Wilhelm Bierbaum wilh...@twitter.com wrote: On December 3rd, I announced on twitter-api-announce that the Search API rate limit response code would change to HTTP 400 as of December 16th, 2009. (http://bit.ly/6yIjEn) Based on feedback we've been getting, we won't be changing the response code for rate limiting to 400. For technical reasons, this code will have to change soon. We're considering feedback we've received to figure what makes the most sense. We will be announcing the change to another 400-series error code when it is apparent what is best. Thanks, Wilhelm Bierbaum Twitter Platform Team -- Abraham Williams | Awesome Lists | http://bit.ly/sprout608 Project | Intersect | http://intersect.labs.poseurtech.com Hacker | http://abrah.am | http://twitter.com/abraham This email is: [ ] shareable [x] ask first [ ] private. Sent from Madison, WI, United States
Re: [twitter-dev] Search API questions
I have been using the Twitter Search API to query the public line for Twitter status updates originating out of a particular location. Currently, I run one search every 15 minutes using an automated script. However I have found that the search results returned contain a number of old search results . An average of 30 new tweets come up for my location every 5 minutes or so. Therefore this shouldn't be the case. Also Results for the same search criteria using search.twitter.com show different results, with no repeats of old search results. Any idea why this is so ? i don't have a direct answer for this, however, if you are polling search every 15 minutes -- then this seems like a clear reason for you to switch over to the streaming API instead. http://apiwiki.twitter.com/Streaming-API-Documentation A second question is regarding published date. Is the published date returned by the search API in GMT ? If so, is there any way to have the search API return the published date as per local time ? the created_at strings in the search API look like created_at:Fri, 27 Nov 2009 00:06:44 + the + is the timezone. no, there is no way to ask search to return those values in local time -- just do the conversion yourself when you receive the status objects. -- Raffi Krikorian Twitter Platform Team ra...@twitter.com | @raffi
