[twitter-dev] Re: Search with multiple terms
Hi, I need a query this way, #term1 OR (term2 from: term3) Means: #term1 from any user or containing string term2 from user term3 Please reply me quick on this Thanks, S. Karthick Rajan On May 11, 11:13 pm, Matt Harris thematthar...@twitter.com wrote: Hi Adrian, Check out our guide on how to use the Search API: http://dev.twitter.com/pages/using_search It includes information about how to do this and other types of queries. Best, @themattharris Developer Advocate, Twitterhttp://twitter.com/themattharris On Wed, May 11, 2011 at 8:50 AM, Adrian arco.wagemak...@gmail.com wrote: Is it possible to do a search for multiple words that belong together combined with the OR operator? For example if I want to capture all tweets for The Bachelor including people who use hashtags, I would like the query to look something like: the bachelor or thebachelor on Twitter search this is translated as: ors=the+bachelor+thebachelor which is clearly wrong. I have tried it many ways now but seem to fail constantly. Any suggestions? -- 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
[twitter-dev] Re: Search API
The best way to do this is to use the streaming API and catch all the tweets containing stanley cup when they happen. The search API is very limited and you will never get more then a couple of thousand results in the past. Oftentimes much less. Best regards, Stefan -- 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-dev] Re: Search all tweets by application
Hi Taylor, thanks for the answer. I'm literally trying to do that, display all the tweets from our app. We are adding some automated text to the tweet, but since we give users the option to modify that text, we could be losing some tweets. Do you have an example of searching that tweet source? Thanks, Juan On Jun 13, 10:41 pm, Taylor Singletary taylorsinglet...@twitter.com wrote: Hi Juan, There's no way to effectively retrieve all tweets sent by a given application using primary methods of any of our APIs. The Search API has some advanced operators that allow you to specify a specific tweet source (effectively the string of text that represents the application that posted the Tweet), but that operator must be used in conjunction with another portion of your query. One could also use the Streaming API to estimate a specific client's tweeting velocity by measuring from the sample hose (which represents 1% of the total tweets being posted) and extrapolate from there, but in the case of measuring a Twitter client's popularity this would not be super-effective since tweeting is just one activity that a client can perform. Is there something with that information you're specifically wanting to accomplish? @episod http://twitter.com/intent/user?screen_name=episod - Taylor Singletary On Mon, Jun 13, 2011 at 2:12 PM, Juan Delgado zzzar...@gmail.com wrote: Hi there, I cannot find a way of retrieving all the tweets coming from a given application. For example, can I retrieve all the tweets posted using TweeDeck? Nothings comes up on the documentation or in google, any idea? Cheers! Juan -- 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
[twitter-dev] Re: Search all tweets by application
If it's your app, why not have your app notify you of every tweet sent? On Jun 14, 10:03 am, Juan Delgado zzzar...@gmail.com wrote: Hi Taylor, thanks for the answer. I'm literally trying to do that, display all the tweets from our app. We are adding some automated text to the tweet, but since we give users the option to modify that text, we could be losing some tweets. Do you have an example of searching that tweet source? Thanks, Juan On Jun 13, 10:41 pm, Taylor Singletary taylorsinglet...@twitter.com wrote: Hi Juan, There's no way to effectively retrieve all tweets sent by a given application using primary methods of any of our APIs. The Search API has some advanced operators that allow you to specify a specific tweet source (effectively the string of text that represents the application that posted the Tweet), but that operator must be used in conjunction with another portion of your query. One could also use the Streaming API to estimate a specific client's tweeting velocity by measuring from the sample hose (which represents 1% of the total tweets being posted) and extrapolate from there, but in the case of measuring a Twitter client's popularity this would not be super-effective since tweeting is just one activity that a client can perform. Is there something with that information you're specifically wanting to accomplish? @episod http://twitter.com/intent/user?screen_name=episod - Taylor Singletary On Mon, Jun 13, 2011 at 2:12 PM, Juan Delgado zzzar...@gmail.com wrote: Hi there, I cannot find a way of retrieving all the tweets coming from a given application. For example, can I retrieve all the tweets posted using TweeDeck? Nothings comes up on the documentation or in google, any idea? Cheers! Juan -- 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] Re: Search all tweets by application
As Orian said, if you want to know every single tweet posted by your application you need to cache them at source. There are no API endpoints which can provide this information for you. On 14 Jun 2011, at 19:43, Orian Marx wrote: If it's your app, why not have your app notify you of every tweet sent? On Jun 14, 10:03 am, Juan Delgado zzzar...@gmail.com wrote: Hi Taylor, thanks for the answer. I'm literally trying to do that, display all the tweets from our app. We are adding some automated text to the tweet, but since we give users the option to modify that text, we could be losing some tweets. Do you have an example of searching that tweet source? Thanks, Juan On Jun 13, 10:41 pm, Taylor Singletary taylorsinglet...@twitter.com wrote: Hi Juan, There's no way to effectively retrieve all tweets sent by a given application using primary methods of any of our APIs. The Search API has some advanced operators that allow you to specify a specific tweet source (effectively the string of text that represents the application that posted the Tweet), but that operator must be used in conjunction with another portion of your query. One could also use the Streaming API to estimate a specific client's tweeting velocity by measuring from the sample hose (which represents 1% of the total tweets being posted) and extrapolate from there, but in the case of measuring a Twitter client's popularity this would not be super-effective since tweeting is just one activity that a client can perform. Is there something with that information you're specifically wanting to accomplish? @episod http://twitter.com/intent/user?screen_name=episod - Taylor Singletary On Mon, Jun 13, 2011 at 2:12 PM, Juan Delgado zzzar...@gmail.com wrote: Hi there, I cannot find a way of retrieving all the tweets coming from a given application. For example, can I retrieve all the tweets posted using TweeDeck? Nothings comes up on the documentation or in google, any idea? Cheers! Juan -- 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 -- Scott Wilcox @dordotky | sc...@dor.ky | http://dor.ky +44 (0) 7538 842418 | +1 (646) 827-0580 -- 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-dev] Re: Search with multiple terms
I did not see the solution for multiple words. It is clear that for single words it is: this OR that becomes ors=this+that I did not see the solution for this sentence OR these words On May 11, 8:13 pm, Matt Harris thematthar...@twitter.com wrote: Hi Adrian, Check out our guide on how to use the Search API: http://dev.twitter.com/pages/using_search It includes information about how to do this and other types of queries. Best, @themattharris Developer Advocate, Twitterhttp://twitter.com/themattharris On Wed, May 11, 2011 at 8:50 AM, Adrian arco.wagemak...@gmail.com wrote: Is it possible to do a search for multiple words that belong together combined with the OR operator? For example if I want to capture all tweets for The Bachelor including people who use hashtags, I would like the query to look something like: the bachelor or thebachelor on Twitter search this is translated as: ors=the+bachelor+thebachelor which is clearly wrong. I have tried it many ways now but seem to fail constantly. Any suggestions? -- 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- Hide quoted text - - Show quoted text - -- 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-dev] Re: Search API return 402 You have been rate limited. Enhance your calm each time
1 - Hosted on GAE is probably your problem you are sharing a limited pool of IP adresses shared by many other GAE based appls using Twitter API. see here : http://groups.google.com/group/google-appengine/browse_thread/thread/20931a508f4dd6e9 happy coding:-) Nick http://gaengine.blogspot.com/ On Apr 18, 11:49 pm, kghate kgh...@gmail.com wrote: I am writing a new application and all was going smoothly until I deployed the application and am getting a 402 on all requests! The application searches based on both geo-location and query terms. Am literally making only test api calls from the application (less than 10 every hour) and each one of it returns a 402. What could be happening? Here are some details 1. Test Application hosted on the Google App Engine 2. Using JTwitter 3. Using OAuth The first time, I thought Twitter might be having issues; but it cant be true all the time. Please help! -- 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-dev] Re: Search API: retrieve the number of times a particular URL was tweeted?
Got it. Thanks, Taylor. On Mar 22, 11:16 am, Taylor Singletary taylorsinglet...@twitter.com wrote: 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] Re: Search API rate limit change?
I just wanted to add to this. The 420s have let up for the most part and I'm no longer seeing rate limiting behavior significantly different from the norm. I've noticed that many result pages are coming back with empty results but if I re-request the same page (after a couple second delay), I can often get results for that page. These are for queries with very low tweet velocity, so it's not like these are new results coming in. Is this related to http://status.twitter.com/post/3785043723/slow-searches ? Thanks. Hayes On Mon, Mar 21, 2011 at 6:13 PM, Matt Harris thematthar...@twitter.comwrote: In many cases we are forced to change the rate limits in response to a significant increase in requests, which means it isn't always possible to give advanced notice of rate limit changes. For some of you it sounds like your code that handles rate limiting didn't react appropriately. When receiving a 420 response we recommend you stop making requests and then after the retry-after, slowly build up the number of requests you make. Put another way it isn't a good idea to make requests to the API at the velocity that caused the 420 response before. As always, the rate limits are there to ensure the system is responsive and available to as many users as possible. This means it is necessary to reduce the number of queries you can make without notice. The best place to stay informed about issues like this are posted through @twitterapi and published on the Twitter status blog: http://status.twitter.com/post/3785043723/slow-searches Best, @themattharris Developer Advocate, Twitter http://twitter.com/themattharris On Mon, Mar 21, 2011 at 7:41 AM, Colin Surprenant colin.surpren...@gmail.com wrote: By adjusting the rate limits to reduce the stress on your search api without notice you have significantly increased the stress level on our end :P Seriously, advanced notice of the situation would have been welcome. In particular what created lots of confusion on our end is that even after pausing for the specified retry_after delay we would immediately get repeated 420s at which point we started to assume our IPs were banned (which also contributed to increase the stress level). Colin On Mar 21, 9:12 am, Jeffrey Greenberg jeffreygreenb...@gmail.com wrote: Taylor, Yeah this was definitely NOT good.In the past, when there is a service disruption, your api group would post something on your status page and tweet about it... Instead, I'm finding out about this from my customers... Did y'all tweet about this or present this somewhere where I could find it? Jeffrey Tweettronics.com On Sun, Mar 20, 2011 at 3:14 PM, Waldron Faulkner waldronfaulk...@gmail.com wrote: Without prior notice, I can understand (circumstances), but without any kind of subsequent announcement?? Means we have to discover issues ourselves, verify that they're Twitter related (and not internal), then search around for existing discussion on the topic. Saves us a lot of time and headaches if Twitter would just announce stuff like this. On Mar 18, 2:51 pm, Taylor Singletary taylorsinglet...@twitter.com wrote: We're working to reinstate the usual limits on the Search API; due to the impact of the Japanese earthquake and resultant query increase against the Search API, some rates were adjusted to cope better serve queries. Will give everyone an update with the various limits are adjusted. @episod http://twitter.com/episod - Taylor Singletary - Twitter Developer Advocate On Fri, Mar 18, 2011 at 11:39 AM, Hayes Davis ha...@appozite.com wrote: Hi, We're seeing this as well starting at approximately the same time as described. We've backed off on searching but are seeing no reduction in the sporadic limiting. It also appears that the amount of results returned on successful queries is severely limited. Some queries that often have 1500 tweets from the last 5 days are returning far fewer results from only the last day. Could we get an update on this? Hayes On Fri, Mar 18, 2011 at 10:13 AM, Eric e...@telvetto.com wrote: We're also seeing 400s on different boxes across different IP addresses with different queries (so it does not appear to be server or query specific). These began on all boxes at 2 a.m. UTC. We've backed off on both number and rate of queries with no effect. We've also noticed an increase in sporadic fail whales via browser based search (atom and html) from personal accounts, although we haven't attempted to quantify it. On Mar 18, 7:40 am, zaver zave...@hotmail.com wrote: Hello, After the latest performance issues with the search api i have been seeing a lot of 420 response codes.From yesterday until now i only get 420 responses on the every search i make. In particular, i search for about
Re: [twitter-dev] Re: Search API rate limit change?
Taylor, Yeah this was definitely NOT good.In the past, when there is a service disruption, your api group would post something on your status page and tweet about it... Instead, I'm finding out about this from my customers... Did y'all tweet about this or present this somewhere where I could find it? Jeffrey Tweettronics.com On Sun, Mar 20, 2011 at 3:14 PM, Waldron Faulkner waldronfaulk...@gmail.com wrote: Without prior notice, I can understand (circumstances), but without any kind of subsequent announcement?? Means we have to discover issues ourselves, verify that they're Twitter related (and not internal), then search around for existing discussion on the topic. Saves us a lot of time and headaches if Twitter would just announce stuff like this. On Mar 18, 2:51 pm, Taylor Singletary taylorsinglet...@twitter.com wrote: We're working to reinstate the usual limits on the Search API; due to the impact of the Japanese earthquake and resultant query increase against the Search API, some rates were adjusted to cope better serve queries. Will give everyone an update with the various limits are adjusted. @episod http://twitter.com/episod - Taylor Singletary - Twitter Developer Advocate On Fri, Mar 18, 2011 at 11:39 AM, Hayes Davis ha...@appozite.com wrote: Hi, We're seeing this as well starting at approximately the same time as described. We've backed off on searching but are seeing no reduction in the sporadic limiting. It also appears that the amount of results returned on successful queries is severely limited. Some queries that often have 1500 tweets from the last 5 days are returning far fewer results from only the last day. Could we get an update on this? Hayes On Fri, Mar 18, 2011 at 10:13 AM, Eric e...@telvetto.com wrote: We're also seeing 400s on different boxes across different IP addresses with different queries (so it does not appear to be server or query specific). These began on all boxes at 2 a.m. UTC. We've backed off on both number and rate of queries with no effect. We've also noticed an increase in sporadic fail whales via browser based search (atom and html) from personal accounts, although we haven't attempted to quantify it. On Mar 18, 7:40 am, zaver zave...@hotmail.com wrote: Hello, After the latest performance issues with the search api i have been seeing a lot of 420 response codes.From yesterday until now i only get 420 responses on the every search i make. In particular, i search for about 100 keywords simultaneously every 6 mins. Why is this happening? Was there any change on the Search API limit? Any help is greatly appreciated. Thanks, 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 -- 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
[twitter-dev] Re: Search API rate limit change?
By adjusting the rate limits to reduce the stress on your search api without notice you have significantly increased the stress level on our end :P Seriously, advanced notice of the situation would have been welcome. In particular what created lots of confusion on our end is that even after pausing for the specified retry_after delay we would immediately get repeated 420s at which point we started to assume our IPs were banned (which also contributed to increase the stress level). Colin On Mar 21, 9:12 am, Jeffrey Greenberg jeffreygreenb...@gmail.com wrote: Taylor, Yeah this was definitely NOT good. In the past, when there is a service disruption, your api group would post something on your status page and tweet about it... Instead, I'm finding out about this from my customers... Did y'all tweet about this or present this somewhere where I could find it? Jeffrey Tweettronics.com On Sun, Mar 20, 2011 at 3:14 PM, Waldron Faulkner waldronfaulk...@gmail.com wrote: Without prior notice, I can understand (circumstances), but without any kind of subsequent announcement?? Means we have to discover issues ourselves, verify that they're Twitter related (and not internal), then search around for existing discussion on the topic. Saves us a lot of time and headaches if Twitter would just announce stuff like this. On Mar 18, 2:51 pm, Taylor Singletary taylorsinglet...@twitter.com wrote: We're working to reinstate the usual limits on the Search API; due to the impact of the Japanese earthquake and resultant query increase against the Search API, some rates were adjusted to cope better serve queries. Will give everyone an update with the various limits are adjusted. @episod http://twitter.com/episod - Taylor Singletary - Twitter Developer Advocate On Fri, Mar 18, 2011 at 11:39 AM, Hayes Davis ha...@appozite.com wrote: Hi, We're seeing this as well starting at approximately the same time as described. We've backed off on searching but are seeing no reduction in the sporadic limiting. It also appears that the amount of results returned on successful queries is severely limited. Some queries that often have 1500 tweets from the last 5 days are returning far fewer results from only the last day. Could we get an update on this? Hayes On Fri, Mar 18, 2011 at 10:13 AM, Eric e...@telvetto.com wrote: We're also seeing 400s on different boxes across different IP addresses with different queries (so it does not appear to be server or query specific). These began on all boxes at 2 a.m. UTC. We've backed off on both number and rate of queries with no effect. We've also noticed an increase in sporadic fail whales via browser based search (atom and html) from personal accounts, although we haven't attempted to quantify it. On Mar 18, 7:40 am, zaver zave...@hotmail.com wrote: Hello, After the latest performance issues with the search api i have been seeing a lot of 420 response codes.From yesterday until now i only get 420 responses on the every search i make. In particular, i search for about 100 keywords simultaneously every 6 mins. Why is this happening? Was there any change on the Search API limit? Any help is greatly appreciated. Thanks, 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 -- 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
[twitter-dev] Re: Search API: Can the geocode param only give me lat/long results?
Hi Augusto, Thanks for your reply. The problem with the Streaming API is that I'd have to have set some database app listening to the stream for the past few years to be able to get all the data (especially for remote locations). I also don't know where my users are going to be, so I don't have the ability to set any bounding boxes... I need something that I can search back in time, rather than set listening.. without knowing in advance where the users will be. Hence the need for the search API... S. On Mar 21, 4:05 pm, Augusto Santos augu...@gemeos.org wrote: 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] Re: Search API: Can the geocode param only give me lat/long results?
Hi Stu, If you need to use the search API for this, you'll need to tolerate the greedy-matching on the profile location field, by discarding the results uninteresting for your purposes (those tweets with no explicit geotagging). Taylor On Mon, Mar 21, 2011 at 9:15 AM, Stu stuart.batter...@gmail.com wrote: Hi Augusto, Thanks for your reply. The problem with the Streaming API is that I'd have to have set some database app listening to the stream for the past few years to be able to get all the data (especially for remote locations). I also don't know where my users are going to be, so I don't have the ability to set any bounding boxes... I need something that I can search back in time, rather than set listening.. without knowing in advance where the users will be. Hence the need for the search API... S. On Mar 21, 4:05 pm, Augusto Santos augu...@gemeos.org wrote: 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 -- 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] Re: Search API rate limit change?
In many cases we are forced to change the rate limits in response to a significant increase in requests, which means it isn't always possible to give advanced notice of rate limit changes. For some of you it sounds like your code that handles rate limiting didn't react appropriately. When receiving a 420 response we recommend you stop making requests and then after the retry-after, slowly build up the number of requests you make. Put another way it isn't a good idea to make requests to the API at the velocity that caused the 420 response before. As always, the rate limits are there to ensure the system is responsive and available to as many users as possible. This means it is necessary to reduce the number of queries you can make without notice. The best place to stay informed about issues like this are posted through @twitterapi and published on the Twitter status blog: http://status.twitter.com/post/3785043723/slow-searches Best, @themattharris Developer Advocate, Twitter http://twitter.com/themattharris On Mon, Mar 21, 2011 at 7:41 AM, Colin Surprenant colin.surpren...@gmail.com wrote: By adjusting the rate limits to reduce the stress on your search api without notice you have significantly increased the stress level on our end :P Seriously, advanced notice of the situation would have been welcome. In particular what created lots of confusion on our end is that even after pausing for the specified retry_after delay we would immediately get repeated 420s at which point we started to assume our IPs were banned (which also contributed to increase the stress level). Colin On Mar 21, 9:12 am, Jeffrey Greenberg jeffreygreenb...@gmail.com wrote: Taylor, Yeah this was definitely NOT good.In the past, when there is a service disruption, your api group would post something on your status page and tweet about it... Instead, I'm finding out about this from my customers... Did y'all tweet about this or present this somewhere where I could find it? Jeffrey Tweettronics.com On Sun, Mar 20, 2011 at 3:14 PM, Waldron Faulkner waldronfaulk...@gmail.com wrote: Without prior notice, I can understand (circumstances), but without any kind of subsequent announcement?? Means we have to discover issues ourselves, verify that they're Twitter related (and not internal), then search around for existing discussion on the topic. Saves us a lot of time and headaches if Twitter would just announce stuff like this. On Mar 18, 2:51 pm, Taylor Singletary taylorsinglet...@twitter.com wrote: We're working to reinstate the usual limits on the Search API; due to the impact of the Japanese earthquake and resultant query increase against the Search API, some rates were adjusted to cope better serve queries. Will give everyone an update with the various limits are adjusted. @episod http://twitter.com/episod - Taylor Singletary - Twitter Developer Advocate On Fri, Mar 18, 2011 at 11:39 AM, Hayes Davis ha...@appozite.com wrote: Hi, We're seeing this as well starting at approximately the same time as described. We've backed off on searching but are seeing no reduction in the sporadic limiting. It also appears that the amount of results returned on successful queries is severely limited. Some queries that often have 1500 tweets from the last 5 days are returning far fewer results from only the last day. Could we get an update on this? Hayes On Fri, Mar 18, 2011 at 10:13 AM, Eric e...@telvetto.com wrote: We're also seeing 400s on different boxes across different IP addresses with different queries (so it does not appear to be server or query specific). These began on all boxes at 2 a.m. UTC. We've backed off on both number and rate of queries with no effect. We've also noticed an increase in sporadic fail whales via browser based search (atom and html) from personal accounts, although we haven't attempted to quantify it. On Mar 18, 7:40 am, zaver zave...@hotmail.com wrote: Hello, After the latest performance issues with the search api i have been seeing a lot of 420 response codes.From yesterday until now i only get 420 responses on the every search i make. In particular, i search for about 100 keywords simultaneously every 6 mins. Why is this happening? Was there any change on the Search API limit? Any help is greatly appreciated. Thanks, 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-dev] Re: Search API rate limit change?
Without prior notice, I can understand (circumstances), but without any kind of subsequent announcement?? Means we have to discover issues ourselves, verify that they're Twitter related (and not internal), then search around for existing discussion on the topic. Saves us a lot of time and headaches if Twitter would just announce stuff like this. On Mar 18, 2:51 pm, Taylor Singletary taylorsinglet...@twitter.com wrote: We're working to reinstate the usual limits on the Search API; due to the impact of the Japanese earthquake and resultant query increase against the Search API, some rates were adjusted to cope better serve queries. Will give everyone an update with the various limits are adjusted. @episod http://twitter.com/episod - Taylor Singletary - Twitter Developer Advocate On Fri, Mar 18, 2011 at 11:39 AM, Hayes Davis ha...@appozite.com wrote: Hi, We're seeing this as well starting at approximately the same time as described. We've backed off on searching but are seeing no reduction in the sporadic limiting. It also appears that the amount of results returned on successful queries is severely limited. Some queries that often have 1500 tweets from the last 5 days are returning far fewer results from only the last day. Could we get an update on this? Hayes On Fri, Mar 18, 2011 at 10:13 AM, Eric e...@telvetto.com wrote: We're also seeing 400s on different boxes across different IP addresses with different queries (so it does not appear to be server or query specific). These began on all boxes at 2 a.m. UTC. We've backed off on both number and rate of queries with no effect. We've also noticed an increase in sporadic fail whales via browser based search (atom and html) from personal accounts, although we haven't attempted to quantify it. On Mar 18, 7:40 am, zaver zave...@hotmail.com wrote: Hello, After the latest performance issues with the search api i have been seeing a lot of 420 response codes.From yesterday until now i only get 420 responses on the every search i make. In particular, i search for about 100 keywords simultaneously every 6 mins. Why is this happening? Was there any change on the Search API limit? Any help is greatly appreciated. Thanks, 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 -- 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-dev] Re: Search API rate limit change?
We're also seeing 400s on different boxes across different IP addresses with different queries (so it does not appear to be server or query specific). These began on all boxes at 2 a.m. UTC. We've backed off on both number and rate of queries with no effect. We've also noticed an increase in sporadic fail whales via browser based search (atom and html) from personal accounts, although we haven't attempted to quantify it. On Mar 18, 7:40 am, zaver zave...@hotmail.com wrote: Hello, After the latest performance issues with the search api i have been seeing a lot of 420 response codes.From yesterday until now i only get 420 responses on the every search i make. In particular, i search for about 100 keywords simultaneously every 6 mins. Why is this happening? Was there any change on the Search API limit? Any help is greatly appreciated. Thanks, 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
Re: [twitter-dev] Re: Search API rate limit change?
We're working to reinstate the usual limits on the Search API; due to the impact of the Japanese earthquake and resultant query increase against the Search API, some rates were adjusted to cope better serve queries. Will give everyone an update with the various limits are adjusted. @episod http://twitter.com/episod - Taylor Singletary - Twitter Developer Advocate On Fri, Mar 18, 2011 at 11:39 AM, Hayes Davis ha...@appozite.com wrote: Hi, We're seeing this as well starting at approximately the same time as described. We've backed off on searching but are seeing no reduction in the sporadic limiting. It also appears that the amount of results returned on successful queries is severely limited. Some queries that often have 1500 tweets from the last 5 days are returning far fewer results from only the last day. Could we get an update on this? Hayes On Fri, Mar 18, 2011 at 10:13 AM, Eric e...@telvetto.com wrote: We're also seeing 400s on different boxes across different IP addresses with different queries (so it does not appear to be server or query specific). These began on all boxes at 2 a.m. UTC. We've backed off on both number and rate of queries with no effect. We've also noticed an increase in sporadic fail whales via browser based search (atom and html) from personal accounts, although we haven't attempted to quantify it. On Mar 18, 7:40 am, zaver zave...@hotmail.com wrote: Hello, After the latest performance issues with the search api i have been seeing a lot of 420 response codes.From yesterday until now i only get 420 responses on the every search i make. In particular, i search for about 100 keywords simultaneously every 6 mins. Why is this happening? Was there any change on the Search API limit? Any help is greatly appreciated. Thanks, 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 -- 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-dev] Re: Search API: Searching world twits (location enabled)
You could use the streaming api and throw away tweets that have no location data/show them as having a default location. Whether or not this is a viable option for you depends on how often the keyword is tweeted and whether you need to index absolutely all tweets for the keyword... On Mar 4, 11:02 am, mahorad maho...@gmail.com wrote: Does any body know how is it possible to: search a keyword among all twits in the whole world, while each returned twit contains the location it was generated? I know that twits can be searched within an area passing lat,lon and radius but I want to search the keyword within the twits in the whole world. Any help will be truly appreciated. -- 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-dev] Re: Search across multiple accounts
Fantastic, thanks Taylor... I had tried that but with = instead of :. Works a treat now :) Also, thanks for quick response... On Feb 23, 5:50 pm, Taylor Singletary taylorsinglet...@twitter.com wrote: Hi Justin, See this thread for an explanation of how to do multi-user search and/or streaming search:http://groups.google.com/group/twitter-development-talk/browse_thread... @episod http://twitter.com/episod - Taylor Singletary - Twitter Developer Advocate On Wed, Feb 23, 2011 at 9:35 AM, Justin justin.realw...@gmail.com wrote: Is it possible to perform a search across multiple accounts? I've had a look though the search api and can't see anything but I could very well have missed something. What I'm thinking is something along the lines of: ?q=searchQuery+from%3Auser1,user2,user3 Also (again I can't see anything in the REST documentation straight away), is there a way to aggrigate streams of a defined list of users? Say; last X tweets from user1, user2 and user3? If not part of the twitter api, any suggestions? Many thanks Justin -- 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
[twitter-dev] Re: Search across multiple accounts
I thought about that but figgured there must be a way to do it more efficiently - Taylor provided a link (above) to to solution... Thanks for the suggestion though :-) On Feb 23, 5:52 pm, yaemog Dodigo yae...@gmail.com wrote: Hi Justin, you could follow (with the streaming api) users 1,2,and 3. But then you'd have to perform the search yourself. Alternatively, you can track (with the streaming api) your searchQuery and only keep tweets from users 1,2, and 3. Maybe I'm missing something here (e.g., userstreams?) -m On Wed, Feb 23, 2011 at 9:35 AM, Justin justin.realw...@gmail.com wrote: Is it possible to perform a search across multiple accounts? I've had a look though the search api and can't see anything but I could very well have missed something. What I'm thinking is something along the lines of: ?q=searchQuery+from%3Auser1,user2,user3 Also (again I can't see anything in the REST documentation straight away), is there a way to aggrigate streams of a defined list of users? Say; last X tweets from user1, user2 and user3? If not part of the twitter api, any suggestions? Many thanks Justin -- 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] Re: Search across multiple accounts
Hi, The thread regard my question, and the suggested solution works fine. I'm using now in my application and has no problems. Enrico On 23 February 2011 19:39, Justin justin.realw...@gmail.com wrote: I thought about that but figgured there must be a way to do it more efficiently - Taylor provided a link (above) to to solution... Thanks for the suggestion though :-) On Feb 23, 5:52 pm, yaemog Dodigo yae...@gmail.com wrote: Hi Justin, you could follow (with the streaming api) users 1,2,and 3. But then you'd have to perform the search yourself. Alternatively, you can track (with the streaming api) your searchQuery and only keep tweets from users 1,2, and 3. Maybe I'm missing something here (e.g., userstreams?) -m On Wed, Feb 23, 2011 at 9:35 AM, Justin justin.realw...@gmail.com wrote: Is it possible to perform a search across multiple accounts? I've had a look though the search api and can't see anything but I could very well have missed something. What I'm thinking is something along the lines of: ?q=searchQuery+from%3Auser1,user2,user3 Also (again I can't see anything in the REST documentation straight away), is there a way to aggrigate streams of a defined list of users? Say; last X tweets from user1, user2 and user3? If not part of the twitter api, any suggestions? Many thanks Justin -- 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 -- 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-dev] Re: Search API the public alternative to URL count API?
Hi Carlos, I am not sure I understand the relevance of your question. I am planning on using OAuth for authentication. The URL count API (url.api.twit..) does not need authentication. Assuming that with callback you refer to the Javascript callbacks; The processing in question will happen in a backend component and thus wont be able to receive the callbacks? Martin On Feb 14, 7:14 pm, Carlos Hugo Gonzalez Castell carlos.hugo.gonzalez.cast...@gmail.com wrote: are usign oauth api? in this api your manage the callbacks twitter On 13 feb, 07:51, Martin Cronjé martincronj...@gmail.com wrote: Hi there, I am busy writing an aggregator and I am looking at using the Twitter API to get URL counts. I seems that public developers are not allowed to use the URL counting API based on the Tweet Button FAQ. Which leaves me with not other option but to use the search API for URL counting. Using the search API makes not sense if there a Count API. This leaves me with the following questions 1. Will my application / I.P. get banned if I use the Count API? 2. Is there a way to request multiple URLs at once to limit round- trips? 3. The URL count API returns not threshold information. So if I am allowed to use it, should I manage the thresholds myself FAQ -http://dev.twitter.com/pages/tweet_button_faq#count-api URL Count API -http://urls.api.twitter.com/1/urls/count.json?url=URL Search API -http://search.twitter.com/search.format My application aggregates URLs on a central server using a shared account so the request numbers may be quite high Martin- Hide quoted text - - Show quoted text - -- 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-dev] Re: Search API the public alternative to URL count API?
are usign oauth api? in this api your manage the callbacks twitter On 13 feb, 07:51, Martin Cronjé martincronj...@gmail.com wrote: Hi there, I am busy writing an aggregator and I am looking at using the Twitter API to get URL counts. I seems that public developers are not allowed to use the URL counting API based on the Tweet Button FAQ. Which leaves me with not other option but to use the search API for URL counting. Using the search API makes not sense if there a Count API. This leaves me with the following questions 1. Will my application / I.P. get banned if I use the Count API? 2. Is there a way to request multiple URLs at once to limit round- trips? 3. The URL count API returns not threshold information. So if I am allowed to use it, should I manage the thresholds myself FAQ -http://dev.twitter.com/pages/tweet_button_faq#count-api URL Count API -http://urls.api.twitter.com/1/urls/count.json?url=URL Search API -http://search.twitter.com/search.format My application aggregates URLs on a central server using a shared account so the request numbers may be quite high Martin -- 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-dev] Re: Search API intermittently returning invalid results
We're seeing the exact same problem in our application. We happen to be using the Twitter ruby gem, but we are experiencing the same behavior. -Ryan On Feb 9, 3:22 pm, chouck cho...@gnipcentral.com wrote: I've been using curl to access search.twitter.com and recently I've noticed that occasionally it is returning invalid tweets. I'm searching for a query-term that shows up very infrequently in the tweet stream, and am using the curl command: curl http://search.twitter.com/search.atom?q=query- termrpp=99result_type=recentsince_id=35409539146719234 What I've found is that about 99% of the time I get back an empty response, just the feed tag wrapped around the meta data for the query but no results. But if I just run the exact same curl command over and over again, occasionally I'll get a response with a full payload of 99 tweets, none of which have anything to do with my search terms. Subsequent executions of the same curl command return the response w/o any tweets in it. Its a little hard to explain, but I have a log file that shows: curl - no tweets curl - no tweets curl - no tweets curl - 99 unrelated tweets curl - no tweets All running the same command via cut-and-paste and all within the space of a few seconds. More often than not, it seems like the invalid tweets are all somehow related, as if I had gotten the response for some other active query. Anyone else seeing anything this problem? The log file is 16K compressed, let me know if you'd like me to send it in. Thanks, -Chris -- 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-dev] Re: Search API rate limit on some keywords
have observed that sometimes some of the keywords get a 420 code? Any ideas why is this happening? You get a 420 NOT USED when a search term hasn't been used recently where the recently is whatever small timeframe (sometimes 7 days, often less) is currently available in the search index. I get it all the time for things like #stlcards :) -- 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-dev] Re: Search API rate limit on some keywords
Thanks for the reply. So as i understand it i am not being rate limited, it just doesn't find any results to return for the specific keywords. In that case should i wait for the amount of time specified on the Retry-after field to make a new search? If i don't wait will that lead to my ip getting blacklisted or it will just not return accurate search results? Thanks in advance. On Feb 2, 3:04 am, @IDisposable idisposa...@gmail.com wrote: have observed that sometimes some of the keywords get a 420 code? Any ideas why is this happening? You get a 420 NOT USED when a search term hasn't been used recently where the recently is whatever small timeframe (sometimes 7 days, often less) is currently available in the search index. I get it all the time for things like #stlcards :) -- 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-dev] Re: Search for terms ignoring punctuation have stopped working properly
Hi Taylor, When using Twitter search, the following query returns statuses with the words ATT and Verizon, including statuses with ATT. http://search.twitter.com/search?q=ands=att+verizon This is the expected behavior as understood from the documentation - exact-matched ignoring punctuation. Doesn't that mean punctuations are removed from the terms and then exact-matched, meaning ATT would become ATT and then matched, or are you replacing punctuation with a whitespace, so it becomes AT T? Anyway, this is not the case with the Streaming API - tracking att does not return statuses with ATT (wheres twitter search does). Using track for at,t will return all statuses with at or t in them, not as intended. Thanks, Niv On Jan 20, 7:49 pm, Taylor Singletary taylorsinglet...@twitter.com wrote: Hi Niv, I don't believe this behavior has changed recently. With the Search and Streaming APIs, the following should be true: - ATT should match ATT - track=at%26t - AT and T should match ATT - track=at,t - ATT should/will not match ATT - track=att Were you seeing different behavior than this recently? Taylor On Wed, Jan 19, 2011 at 5:01 PM, Niv n...@tra.cx wrote: Hello. Until recently, searching using the Search API and the Streaming track filter matched terms ignoring punctuation. Searching for att used to match statuses containing ATT, at t, at.t, etc. Currently, searching for ATT Server or att server return different results - specifically, searching for att server does not return results containing the terms ATT server. From the Streaming API documentation: Terms are exact-matched, and also exact-matched ignoring punctuation. ... Keywords containing punctuation will only exact match tokens and, other than keywords prefixed by # and @, will tend to never match. Thanks, −−− Niv Singer, CTO ≈ Tracx »http://tra.cx Twitter » @nivs ‾‾‾ -- 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
[twitter-dev] Re: Search Twitter Feed from a group of Twitters
Thanks Taylor! This was helpful. On Jan 12, 12:01 pm, Taylor Singletary taylorsinglet...@twitter.com wrote: There are no search within a set capabilities really in the Twitter API or Search API. There are a few approaches you can take, but all of them defer the search part of operation to you and you'll have to accept that you'll not have the full possible dataset to search against. One popular way to search within a given set of users is to assemble a Twitter List containing the users of interest, paginate through the List timeline as your needs (and the data supply) allows, and then perform the search against the tweets/metadata retrieved, acknowledging that a list doesn't comprise all of the tweets (or any of the retweets) authored by the users on the list (@replies / tweets beginning with a @mention to users not belonging to the list are excluded). Other methods are retrieval of various (user) timelines, merging them together, then searching against. The most efficient way to collect tweets for a given set of public users when historical tweets are not important is to use the follow feature of the Streaming API. Taylor On Wed, Jan 12, 2011 at 10:22 AM, Abhi abhishek2j...@gmail.com wrote: Thanks. I looked at it but It just allows me to search for twitter feed from one user. I want to be able to search for twitter feed from multiple users at once. On Jan 12, 12:30 am, Mauro Asprea mauroasp...@gmail.com wrote: Hi you can take a look at http://dev.twitter.com/doc;) On Wed, Jan 12, 2011 at 7:13 AM, Abhi abhishek2j...@gmail.com wrote: Hi, I am New to the Twitter search API and was wondering if someone can please help me on where to find some guidance on how to use Twitter Search API to find tweets from a group of twitters. Thanks for all the help in advance -- 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 -- Mauro Sebastián Asprea E-Mail: mauroasp...@gmail.com Mobile: +34 654297582 Skype: mauro.asprea Algunos hombres ven las cosas como son y se preguntan porque. Otros sueñan cosas que nunca fueron y se preguntan por qué no?. George Bernard Shaw -- 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
[twitter-dev] Re: Search Twitter Feed from a group of Twitters
Thanks. I looked at it but It just allows me to search for twitter feed from one user. I want to be able to search for twitter feed from multiple users at once. On Jan 12, 12:30 am, Mauro Asprea mauroasp...@gmail.com wrote: Hi you can take a look at http://dev.twitter.com/doc;) On Wed, Jan 12, 2011 at 7:13 AM, Abhi abhishek2j...@gmail.com wrote: Hi, I am New to the Twitter search API and was wondering if someone can please help me on where to find some guidance on how to use Twitter Search API to find tweets from a group of twitters. Thanks for all the help in advance -- 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 -- Mauro Sebastián Asprea E-Mail: mauroasp...@gmail.com Mobile: +34 654297582 Skype: mauro.asprea Algunos hombres ven las cosas como son y se preguntan porque. Otros sueñan cosas que nunca fueron y se preguntan por qué no?. George Bernard Shaw -- 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] Re: Search Twitter Feed from a group of Twitters
There are no search within a set capabilities really in the Twitter API or Search API. There are a few approaches you can take, but all of them defer the search part of operation to you and you'll have to accept that you'll not have the full possible dataset to search against. One popular way to search within a given set of users is to assemble a Twitter List containing the users of interest, paginate through the List timeline as your needs (and the data supply) allows, and then perform the search against the tweets/metadata retrieved, acknowledging that a list doesn't comprise all of the tweets (or any of the retweets) authored by the users on the list (@replies / tweets beginning with a @mention to users not belonging to the list are excluded). Other methods are retrieval of various (user) timelines, merging them together, then searching against. The most efficient way to collect tweets for a given set of public users when historical tweets are not important is to use the follow feature of the Streaming API. Taylor On Wed, Jan 12, 2011 at 10:22 AM, Abhi abhishek2j...@gmail.com wrote: Thanks. I looked at it but It just allows me to search for twitter feed from one user. I want to be able to search for twitter feed from multiple users at once. On Jan 12, 12:30 am, Mauro Asprea mauroasp...@gmail.com wrote: Hi you can take a look at http://dev.twitter.com/doc;) On Wed, Jan 12, 2011 at 7:13 AM, Abhi abhishek2j...@gmail.com wrote: Hi, I am New to the Twitter search API and was wondering if someone can please help me on where to find some guidance on how to use Twitter Search API to find tweets from a group of twitters. Thanks for all the help in advance -- 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 -- Mauro Sebastián Asprea E-Mail: mauroasp...@gmail.com Mobile: +34 654297582 Skype: mauro.asprea Algunos hombres ven las cosas como son y se preguntan porque. Otros sueñan cosas que nunca fueron y se preguntan por qué no?. George Bernard Shaw -- 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
[twitter-dev] Re: Search API and location
Hi Tom, DataSift is still in closed Alpha but we have enabled a large number of users within the Alpha to date and will add additional users for the Beta so if you'd like early access it's well worth signing up on http://datasift.net and you may find you get in before we launch the consumer release version. Many thanks Sarah Community Manager DataSift.net On Dec 29 2010, 11:50 am, Tom van der Woerdt i...@tvdw.eu wrote: On 12/29/10 10:40 AM, L. Mohan Arun wrote: I just tried to construct a query that searches for users by location, as it is registered in the location field of their profiles. I had no luck and it seems this is not possible. You can also do this using Datasift's FSDL. ✿✿✿ Mohan ✿✿✿ DataSift is still in closed alpha testing phase... 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
Re: [twitter-dev] Re: Search API and location
Hi Sarah, I'm already a member. Thanks for the offer though :-) Tom On 1/4/11 3:45 PM, Sarah - DataSift wrote: Hi Tom, DataSift is still in closed Alpha but we have enabled a large number of users within the Alpha to date and will add additional users for the Beta so if you'd like early access it's well worth signing up on http://datasift.net and you may find you get in before we launch the consumer release version. Many thanks Sarah Community Manager DataSift.net On Dec 29 2010, 11:50 am, Tom van der Woerdti...@tvdw.eu wrote: On 12/29/10 10:40 AM, L. Mohan Arun wrote: I just tried to construct a query that searches for users by location, as it is registered in the location field of their profiles. I had no luck and it seems this is not possible. You can also do this using Datasift's FSDL. ✿✿✿ Mohan ✿✿✿ DataSift is still in closed alpha testing phase... 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
[twitter-dev] Re: Search API and location
I just tried to construct a query that searches for users by location, as it is registered in the location field of their profiles. I had no luck and it seems this is not possible. You can also do this using Datasift's FSDL. ✿✿✿ Mohan ✿✿✿ -- 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] Re: Search API and location
On 12/29/10 10:40 AM, L. Mohan Arun wrote: I just tried to construct a query that searches for users by location, as it is registered in the location field of their profiles. I had no luck and it seems this is not possible. You can also do this using Datasift's FSDL. ✿✿✿ Mohan ✿✿✿ DataSift is still in closed alpha testing phase... 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
[twitter-dev] Re: Search API and location
I just tried to construct a query that searches for users by location, as it is registered in the location field of their profiles. I had no luck and it seems this is not possible. Google find twitter users by location See localtweeps.com ### Mohan ### -- 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-dev] Re: Search API from_user_id doesn't match up with the proper Twitter user_id
Also, while it would be possible to use screen names for relations (i.e. from_user), this would have a very negative side effect. Mainly, if a user were to change their Twitter account name, previous relations would be lost. On Dec 22, 9:44 am, Corey Ballou ball...@gmail.com wrote: For clarification, I had intended to say from_user_id, as the username is returned properly. On Dec 22, 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
[twitter-dev] Re: Search API from_user_id doesn't match up with the proper Twitter user_id
I'm sure I came off a little strong in the initial post; unfortunately for me google groups doesn't supply an edit button. I think there is still a grain of merit to the request to fix the issue, regardless of the API being free. I'm interest in knowing the trade-offs of Twitter essentially requiring third party apps to make subsequent calls to users/lookup for each unique user in a batch of results. The current problem I see, from Twitter's end, is that the subsequent call returns far more data than necessary. It's doubling the RTTs on both ends and creating an excessive amount of bandwidth for a trivial amount of data. I've got to imagine there's a number of cache misses going on due to the frequency of user updates and pulling the latest tweet, so it would seem rather costly. On Dec 22, 4:33 pm, Robbie Coleman rob...@robnrob.com wrote: 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] Re: Search API from_user_id doesn't match up with the proper Twitter user_id
Yeah, well the call to arms may have been over the top. :) I agree that Twitter should fix the search API. Every time I ask, the answer is that it will be done eventually, and that it will have entities and everything else the streaming API has. I think this means that it will be the streaming API code with the ability to look backwards added. Think about it, isn't that what any architect would do? You combine your code bases. The real problem with search is its inability to go back beyond 5-7 days. Since Twitter plans to make its money from search ads and compete for Google ad revenue, more search results means more searching and more ad revenue. I bet they plan on an IPO within a year, and the story that Twitter search is just a tiny fraction of Google search but growing like crazy is exactly the type of promise that makes investors crazy for an IPO. It is also pretty sad that Google just added the ability to search millions of books going back 500 years, and Twitter only goes back 5 days! So search is clearly very important. I just don't think they want to fix this code. It is Summize code, and they show no interest in diving into it. Until they rewrite it, we have to wait. On Wed, Dec 22, 2010 at 8:55 PM, Corey Ballou ball...@gmail.com wrote: I'm sure I came off a little strong in the initial post; unfortunately for me google groups doesn't supply an edit button. I think there is still a grain of merit to the request to fix the issue, regardless of the API being free. I'm interest in knowing the trade-offs of Twitter essentially requiring third party apps to make subsequent calls to users/lookup for each unique user in a batch of results. The current problem I see, from Twitter's end, is that the subsequent call returns far more data than necessary. It's doubling the RTTs on both ends and creating an excessive amount of bandwidth for a trivial amount of data. I've got to imagine there's a number of cache misses going on due to the frequency of user updates and pulling the latest tweet, so it would seem rather costly. On Dec 22, 4:33 pm, Robbie Coleman rob...@robnrob.com wrote: 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 -- 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
[twitter-dev] Re: Search API cURL strangeness
So it must be based on the IP Address and the UserAgent...
I have changed the UserAgent, so it works now, but I don't
particularly like this solution. It would be nice to know what
happened, and what caused it, so I can try to prevent it from
happening in the future.
On Dec 14, 11:24 am, Tom van der Woerdt i...@tvdw.eu wrote:
Tested it myself with :
tom-mbp:~ tom$ curl --user-agent PivotalVeracity/0.4
http://search.twitter.com/search.json?q=batteryoperatedcandles.netrp...;
Result :
{results:[],max_id:14696108638863361,since_id:9431322892177408,refresh_url:?since_id=14696108638863361q=batteryoperatedcandles.net,results_per_page:100,page:1,completed_in:0.006856,since_id_str:9431322892177408,max_id_str:14696108638863361,query:batteryoperatedcandles.net}
Seems to work fine... Getting exactly the same results when using the
default User Agent.
Tom
On 12/14/10 5:15 PM, Brian Medendorp wrote:
UserAgent is 'PivotalVeracity/0.4'
Here's the test script that helped me track down the problem:
[code]
?php
$timeout = 30;
$useragent = 'PivotalVeracity/0.4';
#$useragent = 'Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US; rv:
1.9.2.13) Gecko/20101203 Firefox/3.6.13';
$url = 'http://search.twitter.com/search.json?
q=batteryoperatedcandles.netrpp=100since_id=9431322892177408since=until=';
#$url = 'http://search.twitter.com/search.json?
q=carnationbreakfastessentials.comrpp=100since_id=since=2010-12-14until=';
#$url = 'http://search.twitter.com/search.json?
q=apple.comrpp=100since_id=since=2010-12-14until=';
$ch = curl_init($url);
curl_setopt($ch, CURLOPT_RETURNTRANSFER, true);
curl_setopt($ch, CURLOPT_USERAGENT, $useragent);
curl_setopt($ch, CURLOPT_TIMEOUT, $timeout);
$content = curl_exec($ch);
if(curl_errno($ch))
{
print curl error: .curl_error($ch).\n;
print_r(curl_getinfo($ch));
}
print_r($content);
[/code]
On Dec 14, 11:03 am, Tom van der Woerdti...@tvdw.eu wrote:
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.netrp...
http://search.twitter.com/search.json?q=carnationbreakfastessentials
http://search.twitter.com/search.json?q=apple.comrpp=100since_id=s...
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
[twitter-dev] Re: Search API cURL strangeness
UserAgent is 'PivotalVeracity/0.4'
Here's the test script that helped me track down the problem:
[code]
?php
$timeout = 30;
$useragent = 'PivotalVeracity/0.4';
#$useragent = 'Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US; rv:
1.9.2.13) Gecko/20101203 Firefox/3.6.13';
$url = 'http://search.twitter.com/search.json?
q=batteryoperatedcandles.netrpp=100since_id=9431322892177408since=until=';
#$url = 'http://search.twitter.com/search.json?
q=carnationbreakfastessentials.comrpp=100since_id=since=2010-12-14until=';
#$url = 'http://search.twitter.com/search.json?
q=apple.comrpp=100since_id=since=2010-12-14until=';
$ch = curl_init($url);
curl_setopt($ch, CURLOPT_RETURNTRANSFER, true);
curl_setopt($ch, CURLOPT_USERAGENT, $useragent);
curl_setopt($ch, CURLOPT_TIMEOUT, $timeout);
$content = curl_exec($ch);
if(curl_errno($ch))
{
print curl error: .curl_error($ch).\n;
print_r(curl_getinfo($ch));
}
print_r($content);
[/code]
On Dec 14, 11:03 am, Tom van der Woerdt i...@tvdw.eu wrote:
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.netrp...
http://search.twitter.com/search.json?q=carnationbreakfastessentials
http://search.twitter.com/search.json?q=apple.comrpp=100since_id=s...
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] Re: Search API cURL strangeness
Tested it myself with :
tom-mbp:~ tom$ curl --user-agent PivotalVeracity/0.4
http://search.twitter.com/search.json?q=batteryoperatedcandles.netrpp=100since_id=9431322892177408;
Result :
{results:[],max_id:14696108638863361,since_id:9431322892177408,refresh_url:?since_id=14696108638863361q=batteryoperatedcandles.net,results_per_page:100,page:1,completed_in:0.006856,since_id_str:9431322892177408,max_id_str:14696108638863361,query:batteryoperatedcandles.net}
Seems to work fine... Getting exactly the same results when using the
default User Agent.
Tom
On 12/14/10 5:15 PM, Brian Medendorp wrote:
UserAgent is 'PivotalVeracity/0.4'
Here's the test script that helped me track down the problem:
[code]
?php
$timeout = 30;
$useragent = 'PivotalVeracity/0.4';
#$useragent = 'Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US; rv:
1.9.2.13) Gecko/20101203 Firefox/3.6.13';
$url = 'http://search.twitter.com/search.json?
q=batteryoperatedcandles.netrpp=100since_id=9431322892177408since=until=';
#$url = 'http://search.twitter.com/search.json?
q=carnationbreakfastessentials.comrpp=100since_id=since=2010-12-14until=';
#$url = 'http://search.twitter.com/search.json?
q=apple.comrpp=100since_id=since=2010-12-14until=';
$ch = curl_init($url);
curl_setopt($ch, CURLOPT_RETURNTRANSFER, true);
curl_setopt($ch, CURLOPT_USERAGENT, $useragent);
curl_setopt($ch, CURLOPT_TIMEOUT, $timeout);
$content = curl_exec($ch);
if(curl_errno($ch))
{
print curl error: .curl_error($ch).\n;
print_r(curl_getinfo($ch));
}
print_r($content);
[/code]
On Dec 14, 11:03 am, Tom van der Woerdti...@tvdw.eu wrote:
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.netrp...
http://search.twitter.com/search.json?q=carnationbreakfastessentials
http://search.twitter.com/search.json?q=apple.comrpp=100since_id=s...
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
[twitter-dev] Re: Search API Optional lang Has Problem.
Same here. On Nov 29, 1:50 am, Jeong Hoon Kim redi...@gmail.com wrote: About 5 days ago, Suddenly Search API Optional lang had no results..My optional lang is ko. Did anybody apply Search API lang option? Did the results come out correctly? -- 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-dev] Re: Search API Optional lang Has Problem.
And same with some search operators (like source:xxx) Sorry for posting twice :) On Nov 29, 1:50 am, Jeong Hoon Kim redi...@gmail.com wrote: About 5 days ago, Suddenly Search API Optional lang had no results..My optional lang is ko. Did anybody apply Search API lang option? Did the results come out correctly? -- 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-dev] Re: Search API Optional lang Has Problem.
Same problem here. When lang=all is used I am getting results. When a language is specified I get zero results most of the time, while in some cases I do get a result. Seems very strange. On Nov 29, 9:25 am, fbparis fbou...@gmail.com wrote: And same with some search operators (like source:xxx) Sorry for posting twice :) On Nov 29, 1:50 am, Jeong Hoon Kim redi...@gmail.com wrote: About 5 days ago, Suddenly Search API Optional lang had no results..My optional lang is ko. Did anybody apply Search API lang option? Did the results come out correctly?- Hide quoted text - - Show quoted text - -- 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] Re: Search API Optional lang Has Problem.
I'm seeing this as well. Including filter:links or setting that language causes the search to fail. I get an error message saying since_id has been adjusted due to a temporary error. I'm *not* including a since_id in the search parameters. Hayes On Mon, Nov 29, 2010 at 10:08 AM, Randomness randomness.bl...@gmail.comwrote: Same problem here. When lang=all is used I am getting results. When a language is specified I get zero results most of the time, while in some cases I do get a result. Seems very strange. On Nov 29, 9:25 am, fbparis fbou...@gmail.com wrote: And same with some search operators (like source:xxx) Sorry for posting twice :) On Nov 29, 1:50 am, Jeong Hoon Kim redi...@gmail.com wrote: About 5 days ago, Suddenly Search API Optional lang had no results..My optional lang is ko. Did anybody apply Search API lang option? Did the results come out correctly?- Hide quoted text - - Show quoted text - -- 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
[twitter-dev] Re: Search API Optional lang Has Problem.
This has happened before. Appending a since clause works around it, but limits your search results to only five days. Also last time this happened they fixed it within a few weeks. I just wish we could get an official comment on this. On Nov 28, 5:50 pm, Jeong Hoon Kim redi...@gmail.com wrote: About 5 days ago, Suddenly Search API Optionallanghad no results..My optionallangis ko. Did anybody apply Search APIlangoption? Did the results come out correctly? -- 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-dev] Re: Search API Optional lang Has Problem.
There is an issue with Twitter's language detection. When specifying a language (lang=nl) , there is no result, when using lang=all, I do get results, in my language. Using lang=all gives us so many results, that we're hitting the rate limits with lots of stuff we're throwing away straight away after we've passed it past our own language detection Are there any plans to fix this? On Nov 29, 1:50 am, Jeong Hoon Kim redi...@gmail.com wrote: About 5 days ago, Suddenly Search API Optional lang had no results..My optional lang is ko. Did anybody apply Search API lang option? Did the results come out correctly? -- 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] Re: Search with geocode does not respect search radius?
This is by design for the Search API. When a Tweet doesn't include any Geo information the Search API will instead use the location in the users profile. The Streaming API looks only for Geo information on a Tweet and ignores the user location. If the users location is not important to you this may be a better solution. Best, @themattharris Developer Advocate, Twitter http://twitter.com/themattharris On Sun, Oct 17, 2010 at 2:41 PM, Daniel daniel.a...@gmail.com wrote: the issue is still happening... You could check it at http://metaki.com Some times the search api query with geo params returns tweets with the lat lon of the BIO and not the lat lon of the tweet!!! You may check this problem for example in Santiago de Chile, or in Buenos Aires. On 16 oct, 05:51, Johannes la Poutre jsixp...@gmail.com wrote: Update: the ticket is closed and @TweepsAround seems to be working fine again. Details:http://code.google.com/p/twitter-api/issues/detail?id=1930 Quote: Comment 3 by project member tokofu, Today (13 hours ago) We've deployed some changes which should have fixed this issue so i'm closing the ticket. Many thanks! On Oct 11, 9:38 pm, themattharris thematthar...@twitter.com wrote: Thanks for filing the ticket on this, we'll post there when a fix is deployed. Progress wise I checked in with the team today and they continue to work on a fix. To keep things connected there is another thread that was discussing the issue with geocoded search here: http://groups.google.com/group/twitter-development-talk/browse_thread... More information will be filed on the ticket here: http://code.google.com/p/twitter-api/issues/detail?id=1930 Thanks for bearing with us whilst we work out what went wrong with the location index and how to resolve it. Best, @themattharris On Oct 10, 9:29 pm, Nick nick.fritzkow...@gmail.com wrote: We are having issues with this as well and it has completely broken our system. We have sent many support tickets but have received no response to them. It looks to be breaking plain searches to not just those requested via the API. Some examples of broken searches are: http://search.twitter.com/search?q=bigpond+near%3Aaustralia http://search.twitter.com/search.json?q=bigpondgeocode=-27.766513,13... These were working before this issue. Best Regards Nick Fritzkowski On Oct 6, 2:42 am, Matt Harris thematthar...@twitter.com wrote: This is a know issue which the team is working on at the moment. I'll post an update when a fix is deployed. --- @themattharris Developer Advocate, Twitterhttp://twitter.com/themattharris On Mon, Oct 4, 2010 at 8:36 PM, _ado adri...@tijsseling.com wrote: For what it's worth, I'm seeing the same issue. Radius parameter is completely ignored. Data returned for, for example, a 1 mile radius will return results spanning 60 miles. -- 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 -- 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-dev] Re: Search with geocode does not respect search radius?
the issue is still happening... You could check it at http://metaki.com Some times the search api query with geo params returns tweets with the lat lon of the BIO and not the lat lon of the tweet!!! You may check this problem for example in Santiago de Chile, or in Buenos Aires. On 16 oct, 05:51, Johannes la Poutre jsixp...@gmail.com wrote: Update: the ticket is closed and @TweepsAround seems to be working fine again. Details:http://code.google.com/p/twitter-api/issues/detail?id=1930 Quote: Comment 3 by project member tokofu, Today (13 hours ago) We've deployed some changes which should have fixed this issue so i'm closing the ticket. Many thanks! On Oct 11, 9:38 pm, themattharris thematthar...@twitter.com wrote: Thanks for filing the ticket on this, we'll post there when a fix is deployed. Progress wise I checked in with the team today and they continue to work on a fix. To keep things connected there is another thread that was discussing the issue with geocoded search here: http://groups.google.com/group/twitter-development-talk/browse_thread... More information will be filed on the ticket here: http://code.google.com/p/twitter-api/issues/detail?id=1930 Thanks for bearing with us whilst we work out what went wrong with the location index and how to resolve it. Best, @themattharris On Oct 10, 9:29 pm, Nick nick.fritzkow...@gmail.com wrote: We are having issues with this as well and it has completely broken our system. We have sent many support tickets but have received no response to them. It looks to be breaking plain searches to not just those requested via the API. Some examples of broken searches are: http://search.twitter.com/search?q=bigpond+near%3Aaustralia http://search.twitter.com/search.json?q=bigpondgeocode=-27.766513,13... These were working before this issue. Best Regards Nick Fritzkowski On Oct 6, 2:42 am, Matt Harris thematthar...@twitter.com wrote: This is a know issue which the team is working on at the moment. I'll post an update when a fix is deployed. --- @themattharris Developer Advocate, Twitterhttp://twitter.com/themattharris On Mon, Oct 4, 2010 at 8:36 PM, _ado adri...@tijsseling.com wrote: For what it's worth, I'm seeing the same issue. Radius parameter is completely ignored. Data returned for, for example, a 1 mile radius will return results spanning 60 miles. -- 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
[twitter-dev] Re: Search with geocode does not respect search radius?
Update: the ticket is closed and @TweepsAround seems to be working fine again. Details: http://code.google.com/p/twitter-api/issues/detail?id=1930 Quote: Comment 3 by project member tokofu, Today (13 hours ago) We've deployed some changes which should have fixed this issue so i'm closing the ticket. Many thanks! On Oct 11, 9:38 pm, themattharris thematthar...@twitter.com wrote: Thanks for filing the ticket on this, we'll post there when a fix is deployed. Progress wise I checked in with the team today and they continue to work on a fix. To keep things connected there is another thread that was discussing the issue with geocoded search here: http://groups.google.com/group/twitter-development-talk/browse_thread... More information will be filed on the ticket here: http://code.google.com/p/twitter-api/issues/detail?id=1930 Thanks for bearing with us whilst we work out what went wrong with the location index and how to resolve it. Best, @themattharris On Oct 10, 9:29 pm, Nick nick.fritzkow...@gmail.com wrote: We are having issues with this as well and it has completely broken our system. We have sent many support tickets but have received no response to them. It looks to be breaking plain searches to not just those requested via the API. Some examples of broken searches are: http://search.twitter.com/search?q=bigpond+near%3Aaustralia http://search.twitter.com/search.json?q=bigpondgeocode=-27.766513,13... These were working before this issue. Best Regards Nick Fritzkowski On Oct 6, 2:42 am, Matt Harris thematthar...@twitter.com wrote: This is a know issue which the team is working on at the moment. I'll post an update when a fix is deployed. --- @themattharris Developer Advocate, Twitterhttp://twitter.com/themattharris On Mon, Oct 4, 2010 at 8:36 PM, _ado adri...@tijsseling.com wrote: For what it's worth, I'm seeing the same issue. Radius parameter is completely ignored. Data returned for, for example, a 1 mile radius will return results spanning 60 miles. -- 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
[twitter-dev] Re: Search with geocode does not respect search radius?
Thanks for filing the ticket on this, we'll post there when a fix is deployed. Progress wise I checked in with the team today and they continue to work on a fix. To keep things connected there is another thread that was discussing the issue with geocoded search here: http://groups.google.com/group/twitter-development-talk/browse_thread/thread/c8826d16b613cf23/79e3d726021652e9#79e3d726021652e9 More information will be filed on the ticket here: http://code.google.com/p/twitter-api/issues/detail?id=1930 Thanks for bearing with us whilst we work out what went wrong with the location index and how to resolve it. Best, @themattharris On Oct 10, 9:29 pm, Nick nick.fritzkow...@gmail.com wrote: We are having issues with this as well and it has completely broken our system. We have sent many support tickets but have received no response to them. It looks to be breaking plain searches to not just those requested via the API. Some examples of broken searches are: http://search.twitter.com/search?q=bigpond+near%3Aaustralia http://search.twitter.com/search.json?q=bigpondgeocode=-27.766513,13... These were working before this issue. Best Regards Nick Fritzkowski On Oct 6, 2:42 am, Matt Harris thematthar...@twitter.com wrote: This is a know issue which the team is working on at the moment. I'll post an update when a fix is deployed. --- @themattharris Developer Advocate, Twitterhttp://twitter.com/themattharris On Mon, Oct 4, 2010 at 8:36 PM, _ado adri...@tijsseling.com wrote: For what it's worth, I'm seeing the same issue. Radius parameter is completely ignored. Data returned for, for example, a 1 mile radius will return results spanning 60 miles. -- 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
[twitter-dev] Re: Search with geocode does not respect search radius?
Hi Matt, Just thought I add more heat. My app is dead because of this bug. Looking forward to a fix. On Oct 5, 7:42 pm, Matt Harris thematthar...@twitter.com wrote: This is a know issue which the team is working on at the moment. I'll post an update when a fix is deployed. --- @themattharris Developer Advocate, Twitterhttp://twitter.com/themattharris On Mon, Oct 4, 2010 at 8:36 PM, _ado adri...@tijsseling.com wrote: For what it's worth, I'm seeing the same issue. Radius parameter is completely ignored. Data returned for, for example, a 1 mile radius will return results spanning 60 miles. -- 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
[twitter-dev] Re: Search with geocode does not respect search radius?
We are having issues with this as well and it has completely broken our system. We have sent many support tickets but have received no response to them. It looks to be breaking plain searches to not just those requested via the API. Some examples of broken searches are: http://search.twitter.com/search?q=bigpond+near%3Aaustralia http://search.twitter.com/search.json?q=bigpondgeocode=-27.766513,134.121094,2500km These were working before this issue. Best Regards Nick Fritzkowski On Oct 6, 2:42 am, Matt Harris thematthar...@twitter.com wrote: This is a know issue which the team is working on at the moment. I'll post an update when a fix is deployed. --- @themattharris Developer Advocate, Twitterhttp://twitter.com/themattharris On Mon, Oct 4, 2010 at 8:36 PM, _ado adri...@tijsseling.com wrote: For what it's worth, I'm seeing the same issue. Radius parameter is completely ignored. Data returned for, for example, a 1 mile radius will return results spanning 60 miles. -- 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
[twitter-dev] Re: Search with geocode does not respect search radius?
For what it's worth, I'm seeing the same issue. Radius parameter is completely ignored. Data returned for, for example, a 1 mile radius will return results spanning 60 miles. -- 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] Re: Search with geocode does not respect search radius?
This is a know issue which the team is working on at the moment. I'll post an update when a fix is deployed. --- @themattharris Developer Advocate, Twitter http://twitter.com/themattharris On Mon, Oct 4, 2010 at 8:36 PM, _ado adri...@tijsseling.com wrote: For what it's worth, I'm seeing the same issue. Radius parameter is completely ignored. Data returned for, for example, a 1 mile radius will return results spanning 60 miles. -- 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
[twitter-dev] Re: search results - how far does it go back
The time window depends on how busy Twitter is as a whole - the search is not a fixed timeframe. On Oct 5, 7:16 am, Quy quyten...@gmail.com wrote: When try to search on results from a user like from:mashable, I only see results going as far back as 24 hours? I thought the archive went back further for a search. -- 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] Re: search results - how far does it go back
Hey Quy, Search is focused on real-time relevant Tweets, so the index is fairly short. At the moment the index is ~5 days of relevant Tweets. I hope that answers your question, @themattharris Developer Advocate, Twitter http://twitter.com/themattharris On Mon, Oct 4, 2010 at 1:32 PM, Tim Bull tim.b...@binaryplex.com wrote: The time window depends on how busy Twitter is as a whole - the search is not a fixed timeframe. On Oct 5, 7:16 am, Quy quyten...@gmail.com wrote: When try to search on results from a user like from:mashable, I only see results going as far back as 24 hours? I thought the archive went back further for a search. -- 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
[twitter-dev] Re: Search Twitter replies
When #newtwitter was launched, this was added. The API method isn't documented yet so they're saying it could change, but the the method is: GET /1/related_results/show/:id - also worth noting the authenticated user must have access to #newtwitter. Checkin here for more details: http://groups.google.com/group/twitter-development-talk/browse_thread/thread/cdc34ae78a2350b8 On Sep 29, 7:21 am, jparicka jpari...@gmail.com wrote: Hi there, Quick question - is it possible to search for replies for a tweet id? Why not? Thanks, Jan -- Thomas Mango tsma...@gmail.com -- 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] Re: Search with geocode does not respect search radius?
This is being investigated at the moment so were still waiting for a fix. When one is deployed we'll let you know. Best, @themattharris Developer Advocate, Twitter http://twitter.com/themattharris On Fri, Oct 1, 2010 at 1:58 AM, Johannes la Poutre jsixp...@gmail.com wrote: Hi Taylor, Any updates on this? Currently the geocode search is still broken... On Sep 24, 4:33 pm, Taylor Singletary taylorsinglet...@twitter.com wrote: We have a bug right now effecting exactly these kinds of searches. I'm not sure how quickly it will be fixed, but I'm hoping it will be early next week. I don't think there are any functional workarounds besides merging multiple searches. Sorry about the mess! Taylor On Fri, Sep 24, 2010 at 6:57 AM, Johannes la Poutre jsixp...@gmail.comwrote: Hello, Since a few days it seems that search restricted by geolocation and search radius is not working correctly anymore. If I submit this request: http://search.twitter.com/search.json?geocode=52.360773%2C4.871720%2C... I expect all resuls to originate from a geocode within 1km radius around the central coordinate. As of a few days ago I get many results from much farther away, up to several tens of kilometers. Is this a known issue? Any time to a fix? Or has there been an API change? Note: I revisited the API documentation ad could not find any recent changes. Best, Joe. -- 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 -- 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-dev] Re: Search with geocode does not respect search radius?
Ouch, that is pretty nasty... I'll see what can be done as merging multiple searches will degrade response times rather badly. Thanks for the reply! On Sep 24, 4:33 pm, Taylor Singletary taylorsinglet...@twitter.com wrote: We have a bug right now effecting exactly these kinds of searches. I'm not sure how quickly it will be fixed, but I'm hoping it will be early next week. I don't think there are any functional workarounds besides merging multiple searches. Sorry about the mess! Taylor On Fri, Sep 24, 2010 at 6:57 AM, Johannes la Poutre jsixp...@gmail.comwrote: Hello, Since a few days it seems that search restricted by geolocation and search radius is not working correctly anymore. If I submit this request: http://search.twitter.com/search.json?geocode=52.360773%2C4.871720%2C... I expect all resuls to originate from a geocode within 1km radius around the central coordinate. As of a few days ago I get many results from much farther away, up to several tens of kilometers. Is this a known issue? Any time to a fix? Or has there been an API change? Note: I revisited the API documentation ad could not find any recent changes. Best, Joe. -- 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
[twitter-dev] Re: Search API is acting weird.
The adjusted since_id to xxx due to temporary error really means this: the since_id was not specified so I went back as far as I could. The earliest tweet is the database was 25075604044 so i used that. For users who tweet more often this error can still occur but is less likely. This is because the search results per page fit into the available index and so no adjustment of since_id is required. For less active accounts the error above occurs because search tries to get n results per page. If there aren't n tweets in the available index the since_id goes beyond what we have stored - so the message above is displayed. As for the other users not showing up when you search for them using from:. There are many reasons for users not to show up in Search. The most common one (and applicable to your account gena01) is there haven't been any tweets in the last 5 days. Other reasons are explained on our help site: http://support.twitter.com/groups/32-something-s-not-working/topics/118-search/articles/66018-my-tweets-or-hashtags-are-missing-from-search-known-issue Hope that's helpful, @themattharris On Sep 21, 8:22 am, Gena01 gen...@gmail.com wrote: So I've been messing with the search API and I am seeing some strange stuff going on. When I request: http://search.twitter.com/search.json?q=to:evI get normal results. If i requesthttp://search.twitter.com/search.json?q=to:aorhttp://search.twitter.com/search.json?q=to:gena01then I get a warning: adjusted since_id to 25075604044 due to temporary error. If I do from: instead of to: I also get these sort of discrepancies. For people like @ev I get feeds/tweets/etc for people not as popular I get nothing back. Is there something I am doing wrong or is search api broken? Gena01 -- 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-dev] Re: search api - since date format
here is my problem I need to catch some tweets since yesterday 20pm until this morning 8am. the problem is that there is more than 1500 tweets that I need, and according to search api docs, I can get a max of roughly 1500 tweets per search query. [...] rpp The number of tweets to return per page, up to a max of 100. http://search.twitter.com/search.json?rpp=100 page The page number (starting at 1) to return, up to a max of roughly 1500 results (based on rpp * page). http://search.twitter.com/search.json?page=10 [...] from http://dev.twitter.com/doc/get/search i'm struggling to build a query where I can get my tweets since yesterday night. any idea? Arian On 9 set, 12:23, Taylor Singletary taylorsinglet...@twitter.com wrote: 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] Re: search api - since date format
This sort of scenario is better served with advance preparation, rather than relying on the Search API to excavate the tweets after the fact, it would be more advantageous to utilize the Streaming API, tracking and storing all relevant tweets during your period of interest. Is this a one-off task you're trying to accomplish or something more general you're looking to accomplish? Taylor On Thu, Sep 9, 2010 at 9:32 AM, arian arianpasqu...@gmail.com wrote: here is my problem I need to catch some tweets since yesterday 20pm until this morning 8am. the problem is that there is more than 1500 tweets that I need, and according to search api docs, I can get a max of roughly 1500 tweets per search query. [...] rpp The number of tweets to return per page, up to a max of 100. http://search.twitter.com/search.json?rpp=100 page The page number (starting at 1) to return, up to a max of roughly 1500 results (based on rpp * page). http://search.twitter.com/search.json?page=10 [...] from http://dev.twitter.com/doc/get/search i'm struggling to build a query where I can get my tweets since yesterday night. any idea? Arian On 9 set, 12:23, Taylor Singletary taylorsinglet...@twitter.com wrote: 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 -- 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-dev] Re: search users on twitter api, is it possible?
thnx, that worked! I was just not looking good enough :) On 8 sep, 18:33, Taylor Singletary taylorsinglet...@twitter.com wrote: Hi Bram, I think this documentation is what you're looking forhttp://dev.twitter.com/doc/get/users/search Example usage: GEThttp://api.twitter.com/1/users/search.xml?q=HULK Taylor On Wed, Sep 8, 2010 at 9:21 AM, Bram Hammer bhamme...@gmail.com wrote: Hello all, I'm now making some app with search on tweets, but now i want to make the option to search on usernames also. Is this possible in any other way? If so, kick me in the right direction please! Thanks in advance -- 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
[twitter-dev] Re: Search API problems...
Matt, thanks for the quick response. After an evening of trying to figure out what's going on, it appears to be working again. I guess the problem must have been on my side. Thank you so much for replying so quickly though, and for the explanation on rates and error messages! Many thanks, ben On Aug 25, 1:02 am, Matt Harris thematthar...@twitter.com wrote: 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 tryhttp://search.twitter.com/search.json?q=testand 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, Twitterhttp://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
[twitter-dev] Re: search for hashtags
Thank you guys for your insight. I was in a rush so I picked simple search but I'll revert it to stream. Not quite clear what do you mean by saying to revert stream every hour but I guess it's in the docs. On Aug 13, 1:58 am, Mark McBride mmcbr...@twitter.com wrote: In both cases it's still probably best to use streaming. You don't want to connect to often, but once an hour should be totally fine. ---Mark http://twitter.com/mccv On Tue, Aug 10, 2010 at 6:34 AM, Tom van der Woerdt i...@tvdw.eu wrote: On 8/10/10 12:58 PM, bitstream wrote: Hi all, I've been reading api docs lately but still can't figure it out what will be the best approach when searching for hashtags. streaming I know that streaming api support statuses/filter where I can declare 'track'. It's possible to use statuses/filter and add a track on '%23hashtag' ? search Or use a simple approach by calling search api and parse response from something like this:http://search.twitter.com/search.json?q=%23hashtag My opinion: It depends. If you want to track a lot of keywords, you should use streaming. If you track only one keyword, then both are an option, depending on the amount of tweets for the hashtag. If you have a lot of keywords but they vary (for example, when users can add/remove hashtags) then you should consider a combination of both, where you reset the stream every hour and update it with new hashtags, and use the REST API for the hashtags that get added in the hour. After all, you don't want to reconnect too often. Tom
[twitter-dev] Re: Search API bug when using lang parameter
Not sure if this matters, but I've tried using no authentication and oauth authentication for this search API call, and am receiving the same results for both. For a while now, I've been tweeting this bug at @twitterapi and @twitter searching for people who've come across it, and I'm coming up empty. It's a huge problem for me and my app development. Am I just overlooking something?
[twitter-dev] Re: search randomly limits result set
this may be what you're looking for in the stream API http://dev.twitter.com/pages/streaming_api_methods I am having the same problems with the search API. To be blunt: it's unreliable, especially for business use. On Aug 10, 9:25 am, michael xenakis michael.g.xena...@gmail.com wrote: Thanks, Taylor. And to clarify my understanding: The Search API is the only entry point for compound searches, yes? I.e., if I want to get Tweets from multiple users in a single call? Also, the REST API does not support searching for hash tags in any form, yes? So the Search API is the only means for that? Thanks again, mX. p.s. The Search Quality Help Page link at the bottom of the page you linked below is dead. I.e.,:http://support.twitter.com/groups/32-something-s-not-working/topics/1... On Aug 10, 2010, at 8:31 AM, Taylor Singletary wrote: The search API's available corpus of tweets for search varies -- it's not always exactly a week, as tweet velocity has an effect on how many tweets can be made readily available for searching. Search also contains only a portion of the total amount of tweets in the system at any one time:http://support.twitter.com/groups/32-something-s-not-working/topics/1... Thanks, Taylor On Tue, Aug 10, 2010 at 8:00 AM, mX. michael.g.xena...@gmail.com wrote: Hullo all - While I opted to keep the subject line short(er), I allow that this may all be a case of user error and that there may be nothing either random w/ the API. That said... ... I've been working w/ the REST API and am trying to incorporate some of the Search API functionality, but am having a very difficult time w/ it. An immediate example is the fact that the API seems to return very few items from its search. E.g., the following search strings (740AM PST, Tue Aug 10): feed://search.twitter.com/search.atom?q=%23thenyknicks+OR+%23allan_houston - returns 4 tweets dating back to Thu Aug 5, 110P (per Twitter feeds) feed://search.twitter.com/search.atom?q=%23thenyknicks+OR+%23allan_houston+OR+from%3Athenyknicks+OR+from%3Aallan_houston - returns 13 tweets dating back to Thu Aug 5, 601A (per Twitter feeds) feed://search.twitter.com/search.atom?q=%23thenyknicks+OR+%23allan_houston+OR+from%3Athenyknicks+OR+from%3Aallan_houston+OR+%232MNBA - returns 15 tweets dating back to Sun Aug 8, 127P (per Twitter feeds) All the information I've read re: rate limits should put 15 tweets well below that. Further, although the API docs suggest the data for the Search API is indexed only for the last seven days, I would still expect to see tweets for all of the last seven days, rather than only five (e.g., the first search should have returned more Tweets dating back to Aug 3. All in all the API does not appear to be working as advertised, however, I may be missing the fine print. Is there a limit on the # of days back which the search parameters will reach? And what is it? Is there a limit on the # of tweets that will be returned? And what is it? Thank you in advance! mX.
[twitter-dev] Re: Search API reporting temporary error
I'm going directly to the URL in question; it only seems to happen to me when I have lang=en anywhere in the url. On Jun 15, 1:35 pm, Mack D. Male master...@gmail.com wrote: There seems to be something wrong with thesearchAPI. It is only returning a tiny subset of what I would expect (after looking at the same query onsearch.twitter.com for instance) and is reporting the following: adjustedsince_idto 16201119561 due to temporary error Any word on what this temporary error is, or when it'll be fixed? I'm using the latest build of TweetSharp, if that makes any difference.
[twitter-dev] Re: Search within followers / following
does anyone know of a way to search just among the people you are following?
[twitter-dev] Re: Search Users Per Location
I built TweepSearch.com to do this. Example: http://tweepsearch.com/search?query=name:joe+location:montrealcommit=Do+Your+Thing! Your milage may vary - the site is definitely slow at the moment and somewhat out-of-date. Damon On Jul 13, 2:28 pm, PhilGo20 gauvin.phili...@gmail.com wrote: anyone ? On 29 juin, 16:20, PhilGo20 gauvin.phili...@gmail.com wrote: Is there a way to run a query returning Users around a particular location based on the location specified in their profile (returns all user with name=joe in montreal ? Or is the only way is to use the user/search method and filter out the results set ?
[twitter-dev] Re: Search Users Per Location
anyone ? On 29 juin, 16:20, PhilGo20 gauvin.phili...@gmail.com wrote: Is there a way to run a query returning Users around a particular location based on the location specified in their profile (returns all user with name=joe in montreal ? Or is the only way is to use the user/search method and filter out the results set ?
Re: [twitter-dev] Re: Search Users Per Location
Not currently. You can search by location and find users tweeting from there or nearby, but can't search by users at a specific location by profile. Jonathan On Tue, Jul 13, 2010 at 2:28 PM, PhilGo20 gauvin.phili...@gmail.com wrote: anyone ? On 29 juin, 16:20, PhilGo20 gauvin.phili...@gmail.com wrote: Is there a way to run a query returning Users around a particular location based on the location specified in their profile (returns all user with name=joe in montreal ? Or is the only way is to use the user/search method and filter out the results set ?
[twitter-dev] Re: Search API -Timezones problem
Can anyone answer my questions??
[twitter-dev] Re: Search API rate limit
Matt, What is exact limit..Whether I can write to twitter for whitelisting of the IP? Whether whitelisting of the IP would do any good? Shan On Jul 7, 12:16 am, Matt Harris thematthar...@twitter.com wrote: 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, Twitterhttp://twitter.com/themattharris
Re: [twitter-dev] Re: Search API rate limit
Shan, as far as I know twitter has been reluctant to state definite numbers, so you'll have to experiment and implement a backoff mechanism in your app. Here is the relevant part of the docs: Search API Rate Limiting The Search API is rate limited by IP address. The number of search requests that originate from a given IP address are counted against the search rate limiter. The specific number of requests a client is able to make to the Search API for a given hour is not released. Note that the Search API is not limited by the same 150 requests per hour limit as the REST API. The number is quite a bit higher and we feel it is both liberal and sufficient for most applications. We do not give the exact number because we want to discourage unnecessary search usage. Search API usage requires that applications include a unique and identifying User Agent string. A HTTP Referrer is expected but is not required. Consumers using the Search API but failing to include a User Agent string will receive a lower rate limit. An application that exceeds the rate limitations of the Search API will receive HTTP 420 response codes to requests. It is a best practice to watch for this error condition and honor the Retry-After header that instructs the application when it is safe to continue. The Retry-After header's value is the number of seconds your application should wait before submitting another query (for example: Retry-After: 67). Cheers, Pascal On Jul 7, 2010, at 1:55 , Ramanean wrote: Matt, What is exact limit..Whether I can write to twitter for whitelisting of the IP? Whether whitelisting of the IP would do any good? Shan
[twitter-dev] Re: Search?
It looks like it is working again now. My test was as follows: 1) Go to http://search.twitter.com, click on the top trending topic. 2) Look at the 15 results returned. Usually they all say half a minute ago or less than a minute ago In my test, it said 3 minutes ago, 5 minutes ago, 9 minutes ago, etc. Thanks. On Jun 28, 9:54 am, Jonathan Reichhold jonathan.reichh...@gmail.com wrote: Can you provide more details? We aren't seeing this behaviour. Search has never returned all of the data and in periods of high volume will not index every single tweet. If you want every tweet on a topic we highly suggest the streaming interface. Jonathan @jreichhold On Mon, Jun 28, 2010 at 8:09 AM, Mack D. Male master...@gmail.com wrote: What's the deal with search? It's not returning all the data. Just look at any of the trending topics for instance. The Status site hasn't been updated.
[twitter-dev] Re: Search API returns only 15 results, even if rpp=100?
Thanks for that -- I just figured that out and was coming back to report my findings, but I guess you beat me to it. :) On Jun 22, 8:01 am, Jonathan Reichhold jonathan.reichh...@gmail.com wrote: 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+... # 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+O... Is there any way to get a larger number of results per page? thanks, -josh- Hide quoted text - - Show quoted text -
[twitter-dev] Re: Search API: searching for Don and finding don't instead
Hello Twitter, Anyone home? j On Jun 2, 11:28 pm, Jeffrey Greenberg jeffreygreenb...@gmail.com wrote: We have a user that is causing us to create a search of the form: Don SomeLastName which is returning tweets containing don't and SomeLastName. Thats a no good! Is there a decent workaround for this by modifying the search? e.g. Don SomeLastName -don't but how do you escape the single quote? Like this? Don SomeLastName -don't
[twitter-dev] Re: Search API: searching for Don and finding don't instead
Hi Jeffrey, Thanks for bumping this to our attention. Some of the threads fall off our radar so a prompt is always welcome. Search treats separate words as an AND search meaning a search for: Don SomeLastName will translate to: Don AND SomeLastName. For a complete phrase search you would instead want to search for: Don SomeLastName. The problem you are experiencing with Don matching Don't is, as you suggested, managed by appending -don't to the query. You don't need to escape the apostrophe and the quotes are not necessary, making your search query: Don SomeLastName -don't You can read more about the supported advanced search operators on the search site [1]. Hope that helps, Matt Harris Developer Advocate, Twitter http://twitter.com/themattharris 1. http://search.twitter.com/operators On Jun 7, 9:09 am, Jeffrey Greenberg jeffreygreenb...@gmail.com wrote: Hello Twitter, Anyone home? j On Jun 2, 11:28 pm, Jeffrey Greenberg jeffreygreenb...@gmail.com wrote: We have a user that is causing us to create a search of the form: Don SomeLastName which is returning tweets containing don't and SomeLastName. Thats a no good! Is there a decent workaround for this by modifying the search? e.g. Don SomeLastName -don't but how do you escape the single quote? Like this? Don SomeLastName -don't
[twitter-dev] Re: Search API: searching for Don and finding don't instead
Thanks Matt, Unless they've been updated lately, the docs are not clear as to how to handle contractions, so thanks for the -don't example. Given that don't is regarded as a word, we believe that search should _not_ return don't in a search for don... It's a bug in our opinion. Further, I'm not sure whether this is a problem only with contractions (that is the handling of single-quote characters), or if search reacts in weird/inconsistent/buggy ways when other special characters (e.g. single quotes, utf-8 stuff, etc) are used. Can you check whether there is consistent handling and spec for these from the search team? Thanks, Jeffrey http://www.tweettronics.com On Jun 7, 10:50 am, themattharris thematthar...@twitter.com wrote: Hi Jeffrey, Thanks for bumping this to our attention. Some of the threads fall off our radar so a prompt is always welcome. Search treats separate words as an AND search meaning a search for: Don SomeLastName will translate to: Don AND SomeLastName. For a complete phrase search you would instead want to search for: Don SomeLastName. The problem you are experiencing with Don matching Don't is, as you suggested, managed by appending -don't to the query. You don't need to escape the apostrophe and the quotes are not necessary, making your search query: Don SomeLastName -don't You can read more about the supported advanced search operators on the search site [1]. Hope that helps, Matt Harris Developer Advocate, Twitterhttp://twitter.com/themattharris 1.http://search.twitter.com/operators On Jun 7, 9:09 am, Jeffrey Greenberg jeffreygreenb...@gmail.com wrote: Hello Twitter, Anyone home? j On Jun 2, 11:28 pm, Jeffrey Greenberg jeffreygreenb...@gmail.com wrote: We have a user that is causing us to create a search of the form: Don SomeLastName which is returning tweets containing don't and SomeLastName. Thats a no good! Is there a decent workaround for this by modifying the search? e.g. Don SomeLastName -don't but how do you escape the single quote? Like this? Don SomeLastName -don't
[twitter-dev] Re: Search spam??
I'm wondering whether the search is getting popular tweets mixed in (the default behavior) and that those are what you are seeing. Can you give an example of one or two of the searches that are doing this? Thanks, Matt On May 27, 2:19 pm, M. Edward (Ed) Borasky zn...@borasky- research.net wrote: I just noticed this today - may have been going on for a while, though. I'm logged in on twitter.com. I have a few saved searches for some friends - about four of them with different groups of friends. What's in the search term is, for example, screen name 1 OR screen name 2. The screen names appear without @ signs. One of these searches is returning tweets that don't match either of the two screen names! They are returning tweets from the two screen names *plus* some tweets that appear to be from people trying to get me to click on links. These tweets do *not* have the characteristics of a Promoted Tweet. They aren't showing up at the top of the search - they're showing up in time sequence order. Has someone figured out how to game the search? Is Twitter testing something and not telling us? When I search for sn1 OR sn2 I do *not* want to receive tweets like this! http://twitter.com/rx8mall/status/14859299274
[twitter-dev] Re: Search api returning results based on walking shortened URLS: causing problems.
I've seen the same thing with some of my own searches, and I just figured the search algo was broken, because it returns results that have absolutely nothing to do with the phrase you searched for. On May 26, 6:24 pm, Jeffrey Greenberg jeffreygreenb...@gmail.com wrote: So we have customer that is searching, for example, for hotels.com. So we use the search api and we get from Twitter a tweet that has no such text in it, but it turns out that the shortened URL contains the string 'hotels.com': Here's the tweet: Siam Bayview Hotel Pattaya, Beach Rd. from THB 2,010 incl breakfast Special Ratehttp://bit.ly/295HOIThailand hotels He're the walked bit.ly url: http://www.r24.org/patong-beach-hotels.com/pattaya/siambayview/ In this case, this match isn't good. They don't want r24.org stuff, they want hotels.com stuff... On the other hand, it's great when it really shows hotels.com stuff.. I'm not sure what the 'right thing to do is at this moment, as I'm reacting to the customer's urgency and problem in getting unrelated stuff showing up in their search... I'm not sure how I should address this: 1. recommend that twitter do some sort of mod to the search api ( I don't have a good idea at the moment about what you should do: make such url walking optional? etc?) 2. do some sort of processing on our end, and communicating about better about what search does to our customers So: a. What's ya'll thoughts on this one? b. I believe that you (twitter) walk some shorteners but not all of them: e.g. bit.ly urls and your own shortener What is the current list that you do walk? This is related to entity parsing discussion here:http://groups.google.com/group/twitter-development-talk/browse_thread... Thanks, Jeffrey Greenberg tweettronics.com
[twitter-dev] Re: Search API or Streaming API?
Woops, my bad. I meant a meta search that would make use of all third party APIs to display the results. But I got your explanation. So if I intend to process the tweets and make sense of it, the Streaming API is what I would need to take a look at. But if I intend to get the search results and just display them on my site, then I guess the search API is what I should use! Pretty much clears everything, so cool! Thanks a lot! -Nischal On May 4, 3:27 am, John Kalucki j...@twitter.com wrote: 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 Kaluckihttp://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] Re: Search API or Streaming API?
Note that from GAE, your search rate will be throttled significantly, as you are sharing the Search API with every other GAE project on a single IP. -John Kalucki http://twitter.com/jkalucki Infrastructure, Twitter Inc. On Tue, May 4, 2010 at 12:34 AM, nischalshetty nischalshett...@gmail.com wrote: Woops, my bad. I meant a meta search that would make use of all third party APIs to display the results. But I got your explanation. So if I intend to process the tweets and make sense of it, the Streaming API is what I would need to take a look at. But if I intend to get the search results and just display them on my site, then I guess the search API is what I should use! Pretty much clears everything, so cool! Thanks a lot! -Nischal On May 4, 3:27 am, John Kalucki j...@twitter.com wrote: 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 Kaluckihttp://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?
[twitter-dev] Re: Search API or Streaming API?
Oh.. alright.. I thought GAE had multiple IP addresses... hmmm... then might have to look into Amazon Thanks a lot for the info :) -Nischal On May 4, 6:29 pm, John Kalucki j...@twitter.com wrote: Note that from GAE, your search rate will be throttled significantly, as you are sharing the Search API with every other GAE project on a single IP. -John Kaluckihttp://twitter.com/jkalucki Infrastructure, Twitter Inc. On Tue, May 4, 2010 at 12:34 AM, nischalshetty nischalshett...@gmail.com wrote: Woops, my bad. I meant a meta search that would make use of all third party APIs to display the results. But I got your explanation. So if I intend to process the tweets and make sense of it, the Streaming API is what I would need to take a look at. But if I intend to get the search results and just display them on my site, then I guess the search API is what I should use! Pretty much clears everything, so cool! Thanks a lot! -Nischal On May 4, 3:27 am, John Kalucki j...@twitter.com wrote: 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 Kaluckihttp://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?
[twitter-dev] Re: Search API - from:xxx not returning @ replies
Comcastbonnie confirms this is not unusual: http://twitter.com/ComcastBonnie/statuses/13083585494 That this error happens for some and not others is not surprising. With new focus on the Search API this type of issue can be addressed :)
Re: [twitter-dev] Re: Search API - from:xxx not returning @ replies
Probably related to this: http://groups.google.com/group/twitter-development-talk/msg/3af17ba93d66abbf On Thu, Apr 29, 2010 at 11:52, mikawhite mikawh...@me.com wrote: Comcastbonnie confirms this is not unusual: http://twitter.com/ComcastBonnie/statuses/13083585494 That this error happens for some and not others is not surprising. With new focus on the Search API this type of issue can be addressed :) -- 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.
[twitter-dev] Re: Search API - 420 increase at 17:01 PDT
This issue is now fixed. -- Subscription settings: http://groups.google.com/group/twitter-development-talk/subscribe?hl=en
[twitter-dev] Re: Search API Changes: Popular Tweets vs. Recency
Thanks, good feedback. Yep, it is always preferable to be explicit about specifying the intent. API versioning and explicit options are both good ways of doing that. The kerfuffle around the popular searches being injected happened exactly because there was previously no way to specify intent. Thus, there was an implicit intent in the search API behavior that the developers came to trust. Now we feel as if a rug is somewhat being pulled from under us. To be fair, though, if popular tweets being included by default BREAKS anybody's app in the technical sense, then maybe it's time to look in the mirror or your code. My app won't be affected by it and will continue to operate just fine. If I want, I could just add extra value to my users by presenting the popular search somehow differently, but if not, it continues to be just a bunch of results, all the same. Be liberal in what you accept (http://en.wikipedia.org/wiki/ Robustness_principle) is a good rule to follow with Twitter API as with any external data. J -- To unsubscribe, reply using remove me as the subject.
[twitter-dev] Re: Search Weirdness?
Hi Naveen
The quotes around your phrase search looks like they have been double
url-escaped.
this works for me:
/search.json?q=Socialscope+OR+%22social+scope%22rpp=200
- Steve
@melobubu
Digital Garage, Tokyo
On 3月27日, 午前4:08, Naveen knig...@gmail.com wrote:
I have a search request that doesnt seem to work properly. I noticed
when I was trying to refresh and no new posts were coming in, but it
appears to not be working even on first search
I have include the HTTP request and response, below, you can see that
no results are returned, however a max_id is returned indicating that
search believes it returned messages and hence any future refresh will
be missing anything that should have been delivered. Also, I know this
search should be returning results.
Request:
GET /search.json?q=Socialscope+OR+%2522social+scope%2522rpp=200 HTTP/
1.1
User-Agent: TestUserAgent
Response:
HTTP/1.1 200 OK
Date: Fri, 26 Mar 2010 19:05:30 GMT
Server: hi
Status: 200 OK
X-Served-From: b005
X-Runtime: 0.89185
Content-Type: application/json; charset=utf-8
X-Served-By: c005.twitter.com
X-Timeline-Cache-Hit: Miss
Cache-Control: max-age=15, must-revalidate, max-age=300
Expires: Fri, 26 Mar 2010 19:10:30 GMT
Content-Length: 230
Vary: Accept-Encoding
X-Varnish: 1840907505
Age: 0
Via: 1.1 varnish
X-Cache-Svr: c005.twitter.com
X-Cache: MISS
Connection: close
{results:[],max_id:11102103671,since_id:0,refresh_url:?
since_id=11102103671q=Socialscope+OR+%2522social+scope
%2522,results_per_page:100,page:1,completed_in:
0.879457,query:Socialscope+OR+%2522social+scope%2522}
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.
Re: [twitter-dev] Re: Search API from:username performance issues?
Hi Doug, I'm getting reports of this from:user delay happening again, so here are some relevant request/response headers and screengrabs of the results. There are some cases where it can be out of sync for up to 8-10 minutes. This is for the search query from:resourcefulmom Request Headers Host: search.twitter.com User-Agent: Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.5; en-US; rv:1.9.0.17) Gecko/2009122115 Firefox/3.0.17 Accept: text/html,application/xhtml+xml,application/xml;q=0.9,*/*;q=0.8 Accept-Language: en-us,en;q=0.5 Accept-Encoding: gzip,deflate Accept-Charset: ISO-8859-1,utf-8;q=0.7,*;q=0.7 Keep-Alive: 300 Connection: keep-alive Referer: http://search.twitter.com/ Cookie: __utma=43838368.580929392773971800.1239516392.1262479801.1267595157.514; __utmz=43838368.1267595157.514.159.utmcsr=push.ly|utmccn=(referral)|utmcmd=referral|utmcct=/home; __utmv=43838368.lang%3A%20en; __utma=110314503.2301945900846264600.1239516535.1262063897.1269652388.170; __utmz=110314503.1258388229.140.5.utmcsr=twitter.com|utmccn=(referral)|utmcmd=referral|utmcct=/; rpp=100; __qca=1239588110-79825009-53773698; lang=all; _twitter_sess=BAh7DToMY3NyZl9pZCIlZDY4ZTY2YjI5ZDRkODgxOGM2ZWZlMWUxM2Y2MDA5%250AYzQ6DnJldHVybl90byJeaHR0cDovL3R3aXR0ZXIuY29tL29hdXRoL2F1dGhv%250Acml6ZT9vYXV0aF90b2tlbj1CbTB6c1YwZGgxTGdRWXNIcGJjNG94bnV0SnRN%250AdzJXRG1nMUVXclR4ekU6E3Bhc3N3b3JkX3Rva2VuIi00OWU2MGRhMDdhZDBk%250AZWNlNzJjNGUwNjlkNjJhYmYyN2E5NmFhYzc4Ogl1c2VyaQNUOWUiCmZsYXNo%250ASUM6J0FjdGlvbkNvbnRyb2xsZXI6OkZsYXNoOjpGbGFzaEhhc2h7AAY6CkB1%250Ac2VkewA6B2lkIiU3YTlmZjBlY2EzNTc2MTczMGZlNTFmMjYxZTJiZWJmZDoP%250AY3JlYXRlZF9hdGwrCH0QjyInAToRdHJhbnNfcHJvbXB0MA%253D%253D--265270e77f05570f78d081813c118b21eee077b9; __utmc=43838368; __utmb=110314503.1.10.1269652388; __utmc=110314503 Response Headers Date: Sat, 27 Mar 2010 01:13:06 GMT Server: hi Status: 200 OK X-Served-From: b022 X-Runtime: 2.41047 Content-Type: text/html; charset=utf-8 X-Served-By: c070.twitter.com X-Timeline-Cache-Hit: Miss Cache-Control: max-age=15, must-revalidate, max-age=300 Expires: Sat, 27 Mar 2010 01:18:03 GMT Content-Encoding: gzip Content-Length: 16677 Vary: Accept-Encoding X-Varnish: 3015348245 Age: 0 Via: 1.1 varnish X-Cache-Svr: c070.twitter.com X-Cache: MISS Set-Cookie: rpp=100; path=/; expires=Sun, 27 Mar 2011 01:13:03 GMT lang=all; path=/; expires=Sun, 27 Mar 2011 01:13:03 GMT Connection: close Screengrab of Twitter Search results: http://grab.by/3ln7 Screengrab of Twitter profile page: http://grab.by/3ln8 Please let me know if you need more info to help debug. Thanks, -Chad On Mon, Mar 15, 2010 at 2:55 PM, twitterdoug dc...@twitter.com wrote: Hi Chad, I didn't get there in time, the results looked fine to me. Should you be able to reproduce this, could you please send more information? dumps of results would be most useful, with complete HTTP requests/ responses... best, doug On Mar 12, 6:22 pm, Chad Etzel jazzyc...@gmail.com wrote: Hi dev team, I've gotten progressively more complaints from TweetGrid users about searches in the form of from:username not updating in a timely fashion. I haven't changed my code in a while, so after investigating it appears that the search index does lag behind a bit for from: searches as compared to just keywords. Is this a bug, or intentional? Example (if you read this in time):http://twitter.com/resourcefulmom compared tohttp://search.twitter.com/search?q=from:resourcefulmom Thanks, -Chad 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: Search API fails with Chinese
Pretty odd, I am able to use curl to get http://search.twitter.com/search.json?q=^_^lang=zh but have the same problem as you fetching it through Firefox/Safari. On Mar 22, 12:51 pm, Irokez iro...@gmail.com wrote: http://search.twitter.com/search.json?q=^_^lang=en - works perfectlyhttp://search.twitter.com/search.json?q=^_^lang=zh - Twitter search has timed out Is there a way to solve the problem? 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: Search API fails with Chinese
This is most likely because there are extremely few results in chinese that match the query. Right now Twitter Search handles lang queries in a relatively inefficient way, so that queries for common terms that match extremely few results may time out. We can (and will) make this better, but the point is that you probably wouldn't have gotten many, if any, results for this query in any case. d On Mar 22, 12:51 pm, Irokez iro...@gmail.com wrote: http://search.twitter.com/search.json?q=^_^lang=en - works perfectlyhttp://search.twitter.com/search.json?q=^_^lang=zh - Twitter search has timed out Is there a way to solve the problem? 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: Search API from:username performance issues?
Hi Chad, I didn't get there in time, the results looked fine to me. Should you be able to reproduce this, could you please send more information? dumps of results would be most useful, with complete HTTP requests/ responses... best, doug On Mar 12, 6:22 pm, Chad Etzel jazzyc...@gmail.com wrote: Hi dev team, I've gotten progressively more complaints from TweetGrid users about searches in the form of from:username not updating in a timely fashion. I haven't changed my code in a while, so after investigating it appears that the search index does lag behind a bit for from: searches as compared to just keywords. Is this a bug, or intentional? Example (if you read this in time):http://twitter.com/resourcefulmom compared tohttp://search.twitter.com/search?q=from:resourcefulmom Thanks, -Chad
[twitter-dev] Re: Search tweets from users in list
That feature does not exist yet. -Doug On Mar 11, 10:32 am, Lukas Müller webmas...@muellerlukas.de wrote: Hello, is there any possibility to search tweets from users that are on list xyz/123 (as example ;-)) via the twitter search RSS feed? Already tried the following queries with no result: @xyz/123 from:xyz/123 Thank you and greetings from germany :-) Lukas
[twitter-dev] Re: Search API : Pagination is out of order
Looking into this. On Mar 10, 1:36 am, Hrishi bakshi.hrishik...@gmail.com wrote: Hello all, I collecting location based tweets. I am using max_id and page parameters for pagination. The ids of the tweets returned seem to be out of order. For example : Go to:http://search.twitter.com/search.json?geocode=40.70771%2C-73.948974%2... Then go to page 2 using next_page value The ids of last results from page 1 are much lower than top results of page 2. In other words page 1 returns older results than page 2. Is this a bug or am I doing it wrong? Thanks
[twitter-dev] Re: Search API rate limit IP address question
Thank you for your reply! If this were true then sometimes your request works and other times it doesn't. Is that the case? Yes, each time I run my app, it makes ~80 calls to the Search API. I can only run a full test of the app 2 or 3 times before I get the Stream Error. But if I run a partial test of only 10 or so calls, I can run it a bunch more times before getting the error. If I wait 30 minutes or so, I can continue testing...but that really affects my workflow! 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 Yes, this is correct. 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. I tried running it from a friend's computer. I get the same frequency of Error, but when he changes his computer's IP address, I'm suddenly able to run the app again... How can I shift the load to my webserver's IP (the one that's whitelisted) rather than each individual computer's IP? Is it possible with Search API? Thank you!
[twitter-dev] Re: Search crossdomain.xml accidentally deleted again?
I see it now too, but when I posted yesterday I was getting some error referring to Bucket does not exist or something like that. On Feb 27, 11:30 pm, Raffi Krikorian ra...@twitter.com wrote: My flash application is currently getting security errors from search.twitter.com. It would appear the crossdomain.xml file no longer exists. i still see it [ra...@tw-mbp13-raffi Desktop]$ wgethttp://search.twitter.com/crossdomain.xml --2010-02-27 20:29:27-- http://search.twitter.com/crossdomain.xml Resolving search.twitter.com... 168.143.162.59 Connecting to search.twitter.com|168.143.162.59|:80... connected. HTTP request sent, awaiting response... 200 OK Length: 206 [application/xml] Saving to: `crossdomain.xml' 100%[=] 206 --.-K/s in 0s 2010-02-27 20:29:27 (16.4 MB/s) - `crossdomain.xml' saved [206/206] And while we're at it... has the Twitter team thought more about loosening the restrictions in their crossdomain.xml files so that Flash developers can actually access the api without using a php or similar proxy? yup. we have a few thing we want to make sure we do first, and then the plan is to loosen restrictions on api.twitter.com. -- Raffi Krikorian Twitter Platform Teamhttp://twitter.com/raffi
Re: [twitter-dev] Re: Search crossdomain.xml accidentally deleted again?
hmm - its possible there was a S3 hiccup (bucket sounds like a S3 related term). On Sun, Feb 28, 2010 at 8:29 AM, Orian Marx (@orian) or...@orianmarx.comwrote: I see it now too, but when I posted yesterday I was getting some error referring to Bucket does not exist or something like that. On Feb 27, 11:30 pm, Raffi Krikorian ra...@twitter.com wrote: My flash application is currently getting security errors from search.twitter.com. It would appear the crossdomain.xml file no longer exists. i still see it [ra...@tw-mbp13-raffi Desktop]$ wgethttp:// search.twitter.com/crossdomain.xml --2010-02-27 20:29:27-- http://search.twitter.com/crossdomain.xml Resolving search.twitter.com... 168.143.162.59 Connecting to search.twitter.com|168.143.162.59|:80... connected. HTTP request sent, awaiting response... 200 OK Length: 206 [application/xml] Saving to: `crossdomain.xml' 100%[=] 206 --.-K/s in 0s 2010-02-27 20:29:27 (16.4 MB/s) - `crossdomain.xml' saved [206/206] And while we're at it... has the Twitter team thought more about loosening the restrictions in their crossdomain.xml files so that Flash developers can actually access the api without using a php or similar proxy? yup. we have a few thing we want to make sure we do first, and then the plan is to loosen restrictions on api.twitter.com. -- Raffi Krikorian Twitter Platform Teamhttp://twitter.com/raffi -- Raffi Krikorian Twitter Platform Team http://twitter.com/raffi
