Re: [twitter-dev] Re: ? API method to get popular hashtags
Have you considered the trends api? Popular hashtags for many locations are included in the trends. You can then use the search api to find examples of those trends. http://dev.twitter.com/doc/get/trends http://dev.twitter.com/doc/get/search Jonathan On Sun, Nov 14, 2010 at 5:12 PM, b3zra1y agregwil...@gmail.com wrote: Thanks for the response. I'll check out your code. I should have clarified a bit more. I'm looking for the most popular hashtags within the Twitter DB. I would then like to be able to obtain a reference to the tweets that use these popular hashtags. Ideally, I would be able to obtain the text of each of those tweets, but I'm suspecting that this would far outweigh the Twitter API limit will. On Nov 14, 4:21 pm, Adam Green 140...@gmail.com wrote: Are you looking for the most popular hashtags out of all tweets or within a set of tweets about a specific subject? If it is the later, what I do is use the streaming API to collect all tweets for certain keywords, parse out the hashtags within them, and store them in a MySQL database. Then I can use straight-forward SQL commands to find the most frequent tags over any period of time. As you'd expect, it is a steep power curve with a very long tail. The top 100 to 200 hashtags in any subset get about 80% of the use. I have a set of simple source code in PHP that creates this type of database. You can use this as a starting point.http://bit.ly/a1CsZE On Sun, Nov 14, 2010 at 8:37 AM, b3zra1y agregwil...@gmail.com wrote: Hi all - I'm looking for an API method that will return a list of popular hashtags. I'm new to the API, but at first glance I don't see such a method. Can you point the way ? THANKS -- Adam Green Twitter API Consultant and Trainerhttp://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 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] Wrong GEOCODE results
Daniel, The search index only cover 7 days worth of content, and a tweet from July 17th is older than 7 days. This has nothing to do with your geocode and is an issue with the depth of the index. Geo is not the only signal used for location and you may also have place ids other sources. Jonathan On Tue, Aug 10, 2010 at 5:26 AM, Daniel daniel.a...@gmail.com wrote: Hi! This is the thirth time I post this problem and no body may help me. This is a very important problem than only occurs in some countries of South America as Chile, Argentina, Peru. This is a clear problem related to the geocode query... I'm trying to make a search query with GEOCODE params but this is not working propperly. I created this geolocalizated tweet with echofon: http://twitter.com/DanielAtik/status/18794641441 As you may see here is the lat, lon of this tweet: http://maps.google.com/maps?q=-33.437790,-70.635895 But if I make a search with search API this tweet does not appears as you can see: http://search.twitter.com/search.json?geocode=-33.437790,-70.635895,2km or for delimeted more: http://search.twitter.com/search.json?geocode=-33.437790,-70.635895,2... As you may see at returned JSON, the tweets has not GEO values. Is there anything wrong?? Any help may be appreciated ;) Daniel
Re: [twitter-dev] Twitter Search API: tweet Source search
It should be source:mastercard_marketplace™_homeward_bound but not finding anything with that source. I.e. spaces are replaced with underscores. Jonathan On Fri, Aug 6, 2010 at 8:03 PM, Sunny gayam.ashwin.re...@gmail.com wrote: Hi There, I am having an issue with the twitter search api. As you know, there is a provision to search for tweets originating from a certain source say q=landing+source:tweetie will search within all tweets coming from tweetie as a source. however when the source looks complex (not just one word), then I'm unable to phrase it like the above. See for e.g the source for the below tweet http://twitter.com/lydiamarieng/status/20453857430 I am unable to search for the source Mastercard Marketplace there please advise and thanks a lot for your help here. -ashwin
Re: [twitter-dev] GEOCODE search problem [URGENT]
Simple answer is that the tweet isn't in the index as a search with no geocode value i.e. http://search.twitter.com/search?q=Prueba1 Tweet is from 3:15 PM Jul 17thhttp://twitter.com/DanielAtik/status/18794641441 The index doesn't go back that far. Jonathan On Tue, Aug 3, 2010 at 7:26 AM, Daniel daniel.a...@gmail.com wrote: Hi! I'm trying to make a search query with GEOCODE params but this is not working propperly in Chile. I created this geolocalizated tweet with echofon: http://twitter.com/DanielAtik/status/18794641441 As you may see here is the lat, lon of this tweet: http://maps.google.com/maps?q=-33.437790,-70.635895 But if I make a search with search API this tweet does not appears as you can see: http://search.twitter.com/search.json?geocode=-33.437790,-70.635895,2km or for delimeted more: http://search.twitter.com/search.json?geocode=-33.437790,-70.635895,2kmq=prueba As you may see at returned JSON, the tweets has not GEO values. Is there anything wrong?? Any help may be appreciated ;) You must make tests in http://metaki.com Daniel
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 ?
Re: [twitter-dev] Are search results ordered by creation date?
result_type=mixed will give you a combination of popular and recent tweets.
Currently the 0-3 popular tweets are first followed by the recent tweets.
I.e. look at the in the results set
metadata: {result_type: recent},
What you are seeing is the mixing of the result types. If you only want
recent then use result_type=recent
https://search.twitter.com/search.json?q=%22Roman%20Polanski%22result_type=recentshow_user=truerpp=100
Jonathan
On Mon, Jul 12, 2010 at 12:07 PM, Harshad RJ harshad...@gmail.com wrote:
Hi,
I just noticed that some search queries have results that seem to be in
order, while others have results that seem to be either unordered or
reversed.
Based on a few sample queries, it looks like popular queries (such as for
trending topics) have results in ascending order of creation date. While
less popular ones are either unordered or descending order.
Is there any order guaranteed by the search API?
Two example queries each with a different order of results:
https://search.twitter.com/search.json?q=%22Roman%20Polanski%22show_user=trueresult_type=mixedrpp=100
https://search.twitter.com/search.json?q=holyshow_user=trueresult_type=mixedrpp=100
thanks,
--
Harshad RJ
http://hrj.wikidot.com
Re: [twitter-dev] Search?
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.
Re: [twitter-dev] How can I search Twitter for tweets containing an exact phrase
The issue here is that the characters around the $t are considered whitespace from parser we use. $t will work, but if it is surrounded by ignored characters then you will get what you consider junk. The streaming API will work better for just following a single topic, but the specific query here for $t was created for stock search years ago. We likely need to think about this case and and maybe improve the parser. Jonathan @jreichhold On Sun, Jun 27, 2010 at 8:21 PM, John Kalucki j...@twitter.com wrote: You may need to do some post-processing on your end to get exactly what you want. You could search for t, then discard all tweets that don't contain $t. But, it sounds like you are doing a repetitive automated search. You should be using the Streaming API for this. Try using track for $t, it might work. If not, track for t, then post-process. If you use search, you will miss some tweets, due to relevance filtering. -John Kalucki http://twitter.com/jkalucki Infrastructure, Twitter Inc. On Sun, Jun 27, 2010 at 3:09 PM, Zhami stu...@yellowhelium.com wrote: I need to search Twitter for tweets containing the phrase $T (T being the trading symbol for ATT). When I perform a search for this, I get back oodles of results where $t is not a complete phrase, but the characters in some larger phrase, which isn't what I want. Alas, $t is quite common in 1337 (leet) phraseology. The Web interface for search.twitter.com advanced offers an entry for This exact phrase but I can't get that to work. I have tried specifying spaces on either side of the $t text, as in: http://search.twitter.com/search?phrase=%20%24t%20 But the search engine ignores the spaces and returns non-exact phrase matches. Is there any way to inform the search engine that I want exact-exact matches, or whole-word matches?
Re: [twitter-dev] Search API returns only 15 results, even if rpp=100?
There are plenty of results for this, but your url is encoded incorrectly http://search.twitter.com/search.atom?q=microsoft+OR+%23ms+OR+lnk.ms+OR+msft+OR+%23surfacerpp=100 # is %23 in url-encoded form As the query exists it is microsoft OR with a page reference. Jonathan On Tue, Jun 22, 2010 at 6:34 AM, John Kalucki j...@twitter.com wrote: Try a less complex query, and you should get more results. On Mon, Jun 21, 2010 at 8:39 PM, Josh Santangelo j...@endquote.com wrote: For example, this query: https://search.twitter.com/search.atom?q=microsoft+OR+#ms+OR+lnk.ms+OR+msft+OR+#surfacepage=1rpp=100result_type=recent Is there any way to get a larger number of results per page? thanks, -josh
Re: [twitter-dev] Saerch API and Twitter Live Search Results disparity
This is actually an artifact of how retweets are displayed between search.twitter.com and twitter.com The tweets are there, but the display is different. Jonathan On Fri, Jun 4, 2010 at 10:10 AM, Brian Maso br...@blumenfeld-maso.comwrote: Last night I collected tweets through the search API for the hashtag #glossgreen, and got a sizeable number of tweets. This morning I did the equivalent thing through the search box on my Twitter homepage (the URL that appears in my browser is http:// twitter.com/#search?q=%23glossgreen), and got different results. More specifically, I found that there were a few users who's tweets appeared when doing the search through the search box in the browser who do not appear at all through the search API results. For example, the user @gloss had many tweets using the #glossgreen hashtag in the time period around 6-8 pm PDT 6/2 -- none of these appear in the twitter search results, but many appear in results through the twitter search box on my personal twitter homepage. I just re-performed both searches this morning to make sure this isn't a temporary issue, but got the same disparity, What expectation should I have about search API accuracy? Shold I expect the search API results to eventually repair, or is are the @gloss tweets permanently missing from the search API's database? I don't want to have to use multiple different APIs/screen-scrapes/ streams just to make sure I get accurate search results, but if that's what I have to do then please let me know. Brian Maso
Re: [twitter-dev] Re: Saerch API and Twitter Live Search Results disparity
This has nothing to do with the cache. Speaking as a engineer in the search group I can state that this has nothing to do with the cache. Jonathan @jreichhold On Fri, Jun 4, 2010 at 9:12 PM, Bess bess...@gmail.com wrote: This is related to cache. Search API results are from cache to improve performance? Search API is not getting the same results as Stream API? On Jun 4, 3:12 pm, Jonathan Reichhold jonathan.reichh...@gmail.com wrote: This is actually an artifact of how retweets are displayed between search.twitter.com and twitter.com The tweets are there, but the display is different. Jonathan On Fri, Jun 4, 2010 at 10:10 AM, Brian Maso br...@blumenfeld-maso.com wrote: Last night I collected tweets through the search API for the hashtag #glossgreen, and got a sizeable number of tweets. This morning I did the equivalent thing through the search box on my Twitter homepage (the URL that appears in my browser is http:// twitter.com/#search?q=%23glossgreen), and got different results. More specifically, I found that there were a few users who's tweets appeared when doing the search through the search box in the browser who do not appear at all through the search API results. For example, the user @gloss had many tweets using the #glossgreen hashtag in the time period around 6-8 pm PDT 6/2 -- none of these appear in the twitter search results, but many appear in results through the twitter search box on my personal twitter homepage. I just re-performed both searches this morning to make sure this isn't a temporary issue, but got the same disparity, What expectation should I have about search API accuracy? Shold I expect the search API results to eventually repair, or is are the @gloss tweets permanently missing from the search API's database? I don't want to have to use multiple different APIs/screen-scrapes/ streams just to make sure I get accurate search results, but if that's what I have to do then please let me know. Brian Maso
Re: [twitter-dev] Re: Saerch API and Twitter Live Search Results disparity
The stream API will have more results and will give all results versus the search API which will sample popular results (high-velocity), but for this case all results are available for both systems. Jonathan On Fri, Jun 4, 2010 at 9:12 PM, Bess bess...@gmail.com wrote: This is related to cache. Search API results are from cache to improve performance? Search API is not getting the same results as Stream API? On Jun 4, 3:12 pm, Jonathan Reichhold jonathan.reichh...@gmail.com wrote: This is actually an artifact of how retweets are displayed between search.twitter.com and twitter.com The tweets are there, but the display is different. Jonathan On Fri, Jun 4, 2010 at 10:10 AM, Brian Maso br...@blumenfeld-maso.com wrote: Last night I collected tweets through the search API for the hashtag #glossgreen, and got a sizeable number of tweets. This morning I did the equivalent thing through the search box on my Twitter homepage (the URL that appears in my browser is http:// twitter.com/#search?q=%23glossgreen), and got different results. More specifically, I found that there were a few users who's tweets appeared when doing the search through the search box in the browser who do not appear at all through the search API results. For example, the user @gloss had many tweets using the #glossgreen hashtag in the time period around 6-8 pm PDT 6/2 -- none of these appear in the twitter search results, but many appear in results through the twitter search box on my personal twitter homepage. I just re-performed both searches this morning to make sure this isn't a temporary issue, but got the same disparity, What expectation should I have about search API accuracy? Shold I expect the search API results to eventually repair, or is are the @gloss tweets permanently missing from the search API's database? I don't want to have to use multiple different APIs/screen-scrapes/ streams just to make sure I get accurate search results, but if that's what I have to do then please let me know. Brian Maso
Re: [twitter-dev] Twitter Search request failed. error 420
420 is a rate limit. The actual error message in the response does state this. Requesting things more than every 20 seconds will not help your results be any fresher. Jonathan On Thu, May 27, 2010 at 6:29 AM, Karolis pkaro...@gmail.com wrote: Hello i was sending this request via php: status:http://search.twitter.com/ search.json?geocode=55.6762944,12.5681157,10mirpp=100http://search.twitter.com/%0Asearch.json?geocode=55.6762944,12.5681157,10mirpp=100 the reply i get is: 420 unused. failed to open stream: HTTP request failed! HTTP/1.1 Is this problem with my code or reliability of api?
Re: [twitter-dev] Twitter search API
The first one should likely be BBC1 OR Cash in the Attic which translates to (BBC1) OR (Cash AND in AND the AND Attic) instead of BBC1 OR Cash in the Attic which translates to (BBC1) OR (CASH) AND (in) AND (the) AND (Attic) Jonathan On Wed, May 26, 2010 at 1:43 AM, Nick nvan...@gmail.com wrote: Hello all, The search API is giving me strange results, for instance http://search.twitter.com/search.atom?q=BBC1+OR+Cash+in+the+Atticresult_type=recent vs http://search.twitter.com/search.atom?q=BBC1result_type=recent Shouldn't all the results from the second URL also be available in first URL? Or am I doing something wrong!
Re: [twitter-dev] Twitter Search API (boolean operators)
Quotes should be used on all phrases. I.e. http://search.twitter.com/search?q=%22life+before+death%22+OR+%22palliative+care%22+OR+dying+OR+%22end-of-life+care%22 Jonathan On Tue, May 11, 2010 at 8:35 AM, taipan541 taipan...@gmail.com wrote: Hello. :) I have several keywords that I would like to search on Twitter. The keywords are life before death, palliative care, dying, end-of- life care. I have tried to use the boolean operators to form up the search query as stated below. http://search.twitter.com/search.atom?q=life%20before%20death+OR+palliative%20care+OR+dying+OR+end-of-life%20care (multiple keywords) Firstly, did I build the query string correctly? If yes, I only could retrieve very little results with the query above. If I only include one keyword, which is life before death, it would return me more results. http://search.twitter.com/search.atom?q=life%20before%20death (one keyword) I believed that if I use the boolean operators, It would have return me much more results which includes the results of life before death. Please help me on how should I proceed to retrieve the results from all keywords. Thank You For Your Help :) Best Regards, Anis Year 3 - Student Nanyang Polytechnic, Singapore
Re: [twitter-dev] Re: Twitter Search API (boolean operators)
Frequency of the words are highly time dependent and all terms are working. See: helenlowell life before death OR palliative care OR dying OR end-of-life care http://search.twitter.com/search?q=helenlowell+%22life+before+death%22+OR+%22palliative+care%22+OR+dying+OR+%22end-of-life+care%22 Jonathan On Tue, May 11, 2010 at 7:10 PM, taipan541 taipan...@gmail.com wrote: Erm, I dont think it is working correctly if using the link below (as what described in Jonathan's post) http://search.twitter.com/search?q=%22life+before+death%22+OR+%22palliative+care%22+OR+dying+OR+%22end-of-life+care%22 It only retrieve results that is based on the dying keyword. The other keywords (life before death, palliative care) which contain spaces doesnt return any results. :( Best Regards, Anis Year 3 - Student Nanyang Polytechnic, Singapore On May 11, 11:44 pm, Jonathan Reichhold jonathan.reichh...@gmail.com wrote: Quotes should be used on all phrases. I.e. http://search.twitter.com/search?q=%22life+before+death%22+OR+%22pall... Jonathan On Tue, May 11, 2010 at 8:35 AM, taipan541 taipan...@gmail.com wrote: Hello. :) I have several keywords that I would like to search on Twitter. The keywords are life before death, palliative care, dying, end-of- life care. I have tried to use the boolean operators to form up the search query as stated below. http://search.twitter.com/search.atom?q=life%20before%20death+OR+pall. .. (multiple keywords) Firstly, did I build the query string correctly? If yes, I only could retrieve very little results with the query above. If I only include one keyword, which is life before death, it would return me more results. http://search.twitter.com/search.atom?q=life%20before%20death (one keyword) I believed that if I use the boolean operators, It would have return me much more results which includes the results of life before death. Please help me on how should I proceed to retrieve the results from all keywords. Thank You For Your Help :) Best Regards, Anis Year 3 - Student Nanyang Polytechnic, Singapore- Hide quoted text - - Show quoted text -
Re: [twitter-dev] Authenticated Search:Version 2.1.2
You are also using api.twitter.com/v1/search when you should be using search.twitter.com/search The low rate limit is a side affect of the incorrect endpoint. Jonathan On Mon, May 10, 2010 at 4:32 AM, seshu suresh.kal...@gmail.com wrote: Hi, Twitter api supports maximum of 150 requests per hour for an unauthenticated request from an ip. So when i hosted it on GAE i was getting response code as 420. Does basic authentication for the search api work? I can see we are passing null for auth in Twitter.java. I tried passing auth also.(I created an extra method). After creating an authenticated instance of Twitter from Factory class by passing userId/password. But still seems it was not working as i was getting 420 status for GAE. But was working fine locally. Any workarounds for this? Or are there any gaps in my understandings? Best Regards, Suresh
Re: [twitter-dev] Differences between docs and Search API behavior
First off, the address for search is currently search.twitter.com i.e. the documentation and the information should use the following url: http://search.twitter.com/search.json?q=recipe See http://dev.twitter.com/doc/get/search All of your other issues are a result of not using the proper URL. At some point we look to combine the 2 API,, but issues like you have noted will cause this to be painful. Jonathan @twittersearch On Tue, Apr 27, 2010 at 8:45 PM, Adam Green 140...@gmail.com wrote: I've found a number of things that don't seem to behave as documented on either the old API wiki or the new Dev site. I'm writing a tutorial on this portion of the API, so I'd like to know if the docs are correct, and I'm just getting weird results, or if the docs are wrong. I'm using PHP and cURL to test this. I'm sending a very simple search request of: http://api.twitter.com/1/search.json?q=recipe 1. Docs say 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. When I try calling the Search API, the rate limit shown in the header is 150. Exceeding 150 in an hour does cause a rate limit failure, so this number does seem to be 150. 2. Docs say Consumers using the Search API but failing to include a User Agent string will receive a lower rate limit. I got the same rate limit of 150 whether or not I use the cURL user agent option. I tried an application name of twitter app tutorial and a standard Mozilla user agent string. 3. Docs say An application that exceeds the rate limitations of the Search API will receive HTTP 420 response codes to requests. When I exceed 150 requests, I get a 400 HTTP response code, not 420. 4. Docs say 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. When I exceed 150 requests, I don't see a retry-After header value. Thanks for your help with this.
Re: [twitter-dev] Search for certain users Twits yields no results
Fixed. Should have been searchable and now is. On Sun, Apr 25, 2010 at 1:40 PM, guytom guy.to...@gmail.com wrote: For some reason: http://search.twitter.com/search?from=Lakers While http://search.twitter.com/search?from=Celtics Works well Ideas anyone? -- Subscription settings: http://groups.google.com/group/twitter-development-talk/subscribe?hl=en
Re: [twitter-dev] Re: High frequency of search API timeouts
There is a known issue with source and the search api that will be fixed on the search deploy next week. Jonathan On Wed, Apr 14, 2010 at 8:24 PM, Ryan W rwilli...@gmail.com wrote: Thanks for confirming. Glad I'm not alone! Are you using the source keyword in your queries? The more I try, the more I think that seems to be the problem since I can't recreate timeouts/long query times when I don't use it. But again, maybe not I'll work on not using it for now. But, thought I'd mention in case anybody from the twitter search team is out there. Nice app BTW, looks cool. rw On Apr 14, 8:56 am, Pykler hnass...@gmail.com wrote: I am a member of a team working on a new startup to classify twittersearchresults into various categories. Kinda cool, check itouthttp:// twecan.com/. However, not all queries may work, and sometimes you would have to resubmit them as mentioned by Ryan. On Apr 12, 7:04 pm, Ryan W rwilli...@gmail.com wrote: Is anybody else seeing a high frequency ofsearchtimeouts? ... Seemed to be working fine until yesterday. YES! same thing. Here's the weird part though. First case: - execute complexsearchdirectly in browser and it timesoutlike my app gets on App Engine Second case: - run a simple, single word,searchin a browser - then run the complexsearchimmediately after and it works It's almost like it has to be primed? It also seems like the -source parameter is the problem, but that could just be anecdotal and clouded by my second case example above. To me it looked random, re-running the same query seems to work sometimes and then fail. We thought it was our caching strategy which we worked all night yesterday optimizing so that we don't hit twittersearchas much, yet we often get timedout. Wonder if someone is looking into this. -- Hatem Twecan Developerhttp://twecan.com- Twecan - Making sense of twittersearch -- To unsubscribe, reply using remove me as the subject.
Re: [twitter-dev] Search API - 420 increase at 17:01 PDT
420 is a rate limit. Are you in shared hosting or have you changed the access pattern? On Wed, Apr 14, 2010 at 7:24 PM, mikawhite mikawh...@me.com wrote: The Search API is returning 420 code this afternoon. Did something change at twitter? To my knowledge, nothing has changed at my location. -- To unsubscribe, reply using remove me as the subject.
