[twitter-dev] Search API : Pagination is out of order
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%2C15kmrpp=100q=page=1 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
Re: [twitter-dev] Re: Tracking number of users for an OAuth app
Didn't previous conversations on similar topics leads to the concept that every client needs its own key? And if so, how do you aggregate stats on that? If you give out a client with a single key, and you give away that key, who is then responsible for the behavior of the application? Who does Twitter contact when some douchenozzle starts sending spam or injects a worm using your key? And how do you, the developer of the app, then fix those problems, if everyone has your key, without re-issuing a new key and invalidating all previous installs? You should proxy your OAuth requests through a web app. Problems solved. ∞ Andy Badera ∞ +1 518-641-1280 Google Voice ∞ This email is: [ ] bloggable [x] ask first [ ] private ∞ Google me: http://www.google.com/search?q=andrew%20badera On Wed, Mar 10, 2010 at 12:53 AM, SM sanja...@gmail.com wrote: It's a desktop app, not a web app. Is there an easy way to do this for desktop apps? I would think Twitter could provide usage stats for OAuth apps. On Mar 9, 5:24 pm, Michael Steuer mste...@gmail.com wrote: Wouldn't you yourself know best how to calculate how many people are actively using your app? On 3/9/10 5:14 PM, SM sanja...@gmail.com wrote: On the application detail page there is a stat that shows how many users your app has. How is this stat calculated? Is it the number of authorized tokens or does it reflect some rolling count of accesses using an authorized token? Or some other calculation? If someone uses my app once and then forgets about it, will that person continue to be counted as a user since tokens never expire? I'm hoping it is a stat that actually tracks how many people are actively using your app. Thanks.
Re: [twitter-dev] Application based on Search API
Not sure about the REST/Search API, but on the Streaming side: http://twitter.com/pdfs/streaming_api_eula.pdf ... see Restrictions ... ∞ Andy Badera ∞ +1 518-641-1280 Google Voice ∞ This email is: [ ] bloggable [x] ask first [ ] private ∞ Google me: http://www.google.com/search?q=andrew%20badera On Tue, Mar 9, 2010 at 5:33 PM, Will Fleming wflemin...@gmail.com wrote: Are the various terms and agreements that currently disallow this published anywhere? After a brief look (perhaps I missed it) at: http://twitter.com/apirules http://twitter.com/tos http://help.twitter.com/forums/26257/entries/18311 As far as I can tell there isn't anything that explicitly disallows resyndicating or making Twitter data available via an API. The TOS also states: Tip: This license is you authorizing us to make your Tweets available to the rest of the world and to let others do the same. Tip: We encourage and permit broad re-use of Content. The Twitter API exists to enable this. thanks On Mon, Mar 8, 2010 at 10:06 PM, John Kalucki j...@twitter.com wrote: Not at the moment, as we expect that the number of services that this will apply to is small. We'll be clarifying data access and licensing over the next few months. -John Kalucki http://twitter.com/jkalucki Infrastructure, Twitter Inc. On Mon, Mar 8, 2010 at 9:57 PM, Abraham Williams 4bra...@gmail.com wrote: Is the specific set of requirements published anywhere? Abraham On Mon, Mar 8, 2010 at 06:50, John Kalucki j...@twitter.com wrote: Your application description sounds like resyndication, which is not allowed under various terms and agreements. You cannot make Twitter data available via an API unless a very specific set of requirements are adhered to. Contact a...@twitter.com to start this process. -John Kalucki http://twitter.com/jkalucki Infrastructure, Twitter Inc. On Mon, Mar 8, 2010 at 3:37 AM, Diz sitov.crist...@gmail.com wrote: For the last 3 months I am experimenting the Search API. I'm focusing on the geo-location searching capabilities. For the beginning I started with my own city, but my intents are to extend to the major cities of my country: that will be at most ten. My idea of application is to offer real-time activity on each major city, through a proxy that caches all tweets and then serves them further to clients, filtered or non-filtered. Frequency of requests should be between 5 to 10 seconds, and that means I should do between 400 to 800 requests per hour just for one city, and probably between 4000 to 8000 requests for the whole application. My questions are: 1). Should I use Search API, or should I move to the Streaming API?! 2). To whom I should request whitelisting: the usual Search API or the Streaming API?! Thanks! -- Abraham Williams | Community Advocate | http://abrah.am TwitterOAuth | http://github.com/abraham/twitteroauth This email is: [ ] shareable [x] ask first [ ] private.
Re: [twitter-dev] Tips to avoid hitting rate limits for my movie monitoring application.
thanks - I need to put more thought into this - I am inclined to feel that at the moment that the search api will probably deliver better resuls - as the cost of filtering thousands and thousands of records for even something as basic as a movie called New York or Independence Day split into independent words will probably be cost intensive and might end up being looking for a needle in the haystack. Having said that I think Twitter has surely come up with this API with good thought - it's just needs further analysis from my end with regards to whether the cost of filtering outweigh the benefits from getting real time streaming resuls. thanks rahul. On Tue, Mar 9, 2010 at 9:10 PM, Mark McBride mmcbr...@twitter.com wrote: This is correct. The general advice is to choose the most specific keyword to track (probably locker and blind in this case), then run an additional layer of filtering on your side. There are higher access levels available that grant you more than 200 keywords to track. ---Mark http://twitter.com/mccv On Tue, Mar 9, 2010 at 12:36 PM, Rahul Dighe rsdigh...@googlemail.comwrote: Hello, Correct me if I am wrong but doesn't the streaming API has limitation that allow me to only track 200 keywords.. and also with the added caveat that - *Track keywords are case-insensitive logical ORs. Terms are exact-matched, and also exact-matched ignoring punctuation. Phrases, keywords with spaces, are not supported. Keywords containing punctuation will only exact match tokens. Some UTF-8 keywords will not match correctly- this is a known temporary defect.* If this is the case how will the api track keywords such as The Hurt Locker or The Blind Side? Thanks Rahul Dighe On Mon, Mar 8, 2010 at 11:42 PM, Mark McBride mmcbr...@twitter.comwrote: This sounds like a perfect use case for the streaming API. The rate limits there are different, but in general more permissive. And because you're doing primarily OR queries, the current track functionality seems sufficient. ---Mark http://twitter.com/mccv On Mon, Mar 8, 2010 at 3:21 PM, Rahul rsdigh...@googlemail.com wrote: Hello, I am building an application that monitors tweets about movies(for now with... other interesting things planned). I have my id whitelisted but I want to avoid overusing it. The challenge that I face is that ideally I want to make full use of the opportunity to retrieve 100 tweets per call and for that I need information on the frequency with which users are tweeting about a movie and then set my call frequency (to call twitter search api) accordingly so that I maximize the number of tweets returned per call or atleast. Since I presume there is no way to know what frequency is someone tweeting about a movie - I need help is what is the best way to optimize for such a situation. The challenge is complicated by the fact that users tweet about different movies at different rates and the rates generally decrease overtime. I have tried combining searches - but the challenge is that lets say I search for (Movie A OR Movie B) (Movie C OR Movie D) it could be the case that people tweet about Movie A B a lot and litle to none about C or D or there is a combination in which they continue to tweet about A but not about B - So I still can end up in a situation where I am not optimizing my calls. Also situations such as Oscars can dramatically change what people talk about even about movies out months ago. I have thought of writing something such as a variable frequency caller that can check the frequency of tweets for the last 3 calls in order to appreciate the frequency of tweets for a given search and then continuously vary the time between calls so that I can get as close to 100 tweets as possible in a call. Any ideas suggestions that can suggest ways to alleviate the above will be highly appreciated. Thanks Rahul.
Re: [twitter-dev] Facing problem with rate-limit.
Hi, Thank you for the reply. I understand what you are saying, but is it possible to get more than one user account whitelisted? When I looked at the whitelisting form, it suggests to add IPs and not user accounts. Let me know please, Thank you. On Tue, Mar 9, 2010 at 10:19 PM, Abraham Williams 4bra...@gmail.com wrote: If you make the requests authenticated as your users each one will have 20k hits per hour. Each whitelisted entity, whether an account or IP address, is allowed 2 requests per hour. This means that two authenticated users using the same IP address would each get 2 requests per hour. - http://apiwiki.twitter.com/Rate-limiting Depending on your application you can cache all the user objects and then use the Social Graph APIs to find missing profiles. Abraham On Tue, Mar 9, 2010 at 02:37, Rushikesh Bhanage rishibhan...@gmail.comwrote: Hi , We are building a twitter application which needs to collect all the followers of the user to show him results. Now when we looked at following user's: user Followers ev - 1,172,553 aplusk -4,627,964 Kim Kardashian - 3,144,680 such users through our application it turns out 20,000 calls per white-listed IP without breaking operation, are not sufficient to collect all the followers of these users. Because every cursor id gives only 100 follower's data which means 20,000 calls are not sufficient for some users with extensive followers. Eagerly looking for solution, Thank you. Regards, Rushikesh. -- Abraham Williams | Community Advocate | http://abrah.am TwitterOAuth | http://github.com/abraham/twitteroauth This email is: [ ] shareable [x] ask first [ ] private.
[twitter-dev] Re: Application based on Search API
Okie, closing the Pandora's box! I never specified that my app will generate an API! I also didn't specify anything about resyndicating content. I just want to offer real-time activity on a web interface, and beside that analyze cached tweets to generate statistics. Anyone, following me?! On Mar 10, 12:33 am, Will Fleming wflemin...@gmail.com wrote: Are the various terms and agreements that currently disallow this published anywhere? After a brief look (perhaps I missed it) at:http://twitter.com/apiruleshttp://twitter.com/toshttp://help.twitter.com/forums/26257/entries/18311 As far as I can tell there isn't anything that explicitly disallows resyndicating or making Twitter data available via an API. The TOS also states: Tip: This license is you authorizing us to make your Tweets available to the rest of the world and to let others do the same. Tip: We encourage and permit broad re-use of Content. The Twitter API exists to enable this. thanks On Mon, Mar 8, 2010 at 10:06 PM, John Kalucki j...@twitter.com wrote: Not at the moment, as we expect that the number of services that this will apply to is small. We'll be clarifying data access and licensing over the next few months. -John Kalucki http://twitter.com/jkalucki Infrastructure, Twitter Inc. On Mon, Mar 8, 2010 at 9:57 PM, Abraham Williams 4bra...@gmail.comwrote: Is the specific set of requirements published anywhere? Abraham On Mon, Mar 8, 2010 at 06:50, John Kalucki j...@twitter.com wrote: Your application description sounds like resyndication, which is not allowed under various terms and agreements. You cannot make Twitter data available via an API unless a very specific set of requirements are adhered to. Contact a...@twitter.com to start this process. -John Kalucki http://twitter.com/jkalucki Infrastructure, Twitter Inc. On Mon, Mar 8, 2010 at 3:37 AM, Diz sitov.crist...@gmail.com wrote: For the last 3 months I am experimenting the Search API. I'm focusing on the geo-location searching capabilities. For the beginning I started with my own city, but my intents are to extend to the major cities of my country: that will be at most ten. My idea of application is to offer real-time activity on each major city, through a proxy that caches all tweets and then serves them further to clients, filtered or non-filtered. Frequency of requests should be between 5 to 10 seconds, and that means I should do between 400 to 800 requests per hour just for one city, and probably between 4000 to 8000 requests for the whole application. My questions are: 1). Should I use Search API, or should I move to the Streaming API?! 2). To whom I should request whitelisting: the usual Search API or the Streaming API?! Thanks! -- Abraham Williams | Community Advocate |http://abrah.am TwitterOAuth |http://github.com/abraham/twitteroauth This email is: [ ] shareable [x] ask first [ ] private.
Re: [twitter-dev] Re: Application based on Search API
So you want to use the Streaming API, primarily, for anything realtime. Maybe the Search API in a supplementary fashion ... is there whitelisting for the Search API specifically? --ab On Wed, Mar 10, 2010 at 5:21 AM, Diz sitov.crist...@gmail.com wrote: Okie, closing the Pandora's box! I never specified that my app will generate an API! I also didn't specify anything about resyndicating content. I just want to offer real-time activity on a web interface, and beside that analyze cached tweets to generate statistics. Anyone, following me?! On Mar 10, 12:33 am, Will Fleming wflemin...@gmail.com wrote: Are the various terms and agreements that currently disallow this published anywhere? After a brief look (perhaps I missed it) at:http://twitter.com/apiruleshttp://twitter.com/toshttp://help.twitter.com/forums/26257/entries/18311 As far as I can tell there isn't anything that explicitly disallows resyndicating or making Twitter data available via an API. The TOS also states: Tip: This license is you authorizing us to make your Tweets available to the rest of the world and to let others do the same. Tip: We encourage and permit broad re-use of Content. The Twitter API exists to enable this. thanks On Mon, Mar 8, 2010 at 10:06 PM, John Kalucki j...@twitter.com wrote: Not at the moment, as we expect that the number of services that this will apply to is small. We'll be clarifying data access and licensing over the next few months. -John Kalucki http://twitter.com/jkalucki Infrastructure, Twitter Inc. On Mon, Mar 8, 2010 at 9:57 PM, Abraham Williams 4bra...@gmail.comwrote: Is the specific set of requirements published anywhere? Abraham On Mon, Mar 8, 2010 at 06:50, John Kalucki j...@twitter.com wrote: Your application description sounds like resyndication, which is not allowed under various terms and agreements. You cannot make Twitter data available via an API unless a very specific set of requirements are adhered to. Contact a...@twitter.com to start this process. -John Kalucki http://twitter.com/jkalucki Infrastructure, Twitter Inc. On Mon, Mar 8, 2010 at 3:37 AM, Diz sitov.crist...@gmail.com wrote: For the last 3 months I am experimenting the Search API. I'm focusing on the geo-location searching capabilities. For the beginning I started with my own city, but my intents are to extend to the major cities of my country: that will be at most ten. My idea of application is to offer real-time activity on each major city, through a proxy that caches all tweets and then serves them further to clients, filtered or non-filtered. Frequency of requests should be between 5 to 10 seconds, and that means I should do between 400 to 800 requests per hour just for one city, and probably between 4000 to 8000 requests for the whole application. My questions are: 1). Should I use Search API, or should I move to the Streaming API?! 2). To whom I should request whitelisting: the usual Search API or the Streaming API?! Thanks! -- Abraham Williams | Community Advocate |http://abrah.am TwitterOAuth |http://github.com/abraham/twitteroauth This email is: [ ] shareable [x] ask first [ ] private.
Re: [twitter-dev] Tips to avoid hitting rate limits for my movie monitoring application.
We'd like to offer phrase search, or at least AND search on the Streaming API, but we've had other priorities recently. Note that Search is not intended for repeated automated keyword queries, and that Search results are filtered for relevance. If you need all the Tweets, or if you need them in real-time, the Streaming API is the best answer. The Search API is mostly intended for complex, historical backfill, ad hoc, and direct-display-to-user queries. -John Kalucki http://twitter.com/jkalucki Infrastructure, Twitter Inc. On Wed, Mar 10, 2010 at 12:23 AM, Rahul Dighe rsdigh...@googlemail.comwrote: thanks - I need to put more thought into this - I am inclined to feel that at the moment that the search api will probably deliver better resuls - as the cost of filtering thousands and thousands of records for even something as basic as a movie called New York or Independence Day split into independent words will probably be cost intensive and might end up being looking for a needle in the haystack. Having said that I think Twitter has surely come up with this API with good thought - it's just needs further analysis from my end with regards to whether the cost of filtering outweigh the benefits from getting real time streaming resuls. thanks rahul. On Tue, Mar 9, 2010 at 9:10 PM, Mark McBride mmcbr...@twitter.com wrote: This is correct. The general advice is to choose the most specific keyword to track (probably locker and blind in this case), then run an additional layer of filtering on your side. There are higher access levels available that grant you more than 200 keywords to track. ---Mark http://twitter.com/mccv On Tue, Mar 9, 2010 at 12:36 PM, Rahul Dighe rsdigh...@googlemail.comwrote: Hello, Correct me if I am wrong but doesn't the streaming API has limitation that allow me to only track 200 keywords.. and also with the added caveat that - *Track keywords are case-insensitive logical ORs. Terms are exact-matched, and also exact-matched ignoring punctuation. Phrases, keywords with spaces, are not supported. Keywords containing punctuation will only exact match tokens. Some UTF-8 keywords will not match correctly- this is a known temporary defect.* If this is the case how will the api track keywords such as The Hurt Locker or The Blind Side? Thanks Rahul Dighe On Mon, Mar 8, 2010 at 11:42 PM, Mark McBride mmcbr...@twitter.comwrote: This sounds like a perfect use case for the streaming API. The rate limits there are different, but in general more permissive. And because you're doing primarily OR queries, the current track functionality seems sufficient. ---Mark http://twitter.com/mccv On Mon, Mar 8, 2010 at 3:21 PM, Rahul rsdigh...@googlemail.com wrote: Hello, I am building an application that monitors tweets about movies(for now with... other interesting things planned). I have my id whitelisted but I want to avoid overusing it. The challenge that I face is that ideally I want to make full use of the opportunity to retrieve 100 tweets per call and for that I need information on the frequency with which users are tweeting about a movie and then set my call frequency (to call twitter search api) accordingly so that I maximize the number of tweets returned per call or atleast. Since I presume there is no way to know what frequency is someone tweeting about a movie - I need help is what is the best way to optimize for such a situation. The challenge is complicated by the fact that users tweet about different movies at different rates and the rates generally decrease overtime. I have tried combining searches - but the challenge is that lets say I search for (Movie A OR Movie B) (Movie C OR Movie D) it could be the case that people tweet about Movie A B a lot and litle to none about C or D or there is a combination in which they continue to tweet about A but not about B - So I still can end up in a situation where I am not optimizing my calls. Also situations such as Oscars can dramatically change what people talk about even about movies out months ago. I have thought of writing something such as a variable frequency caller that can check the frequency of tweets for the last 3 calls in order to appreciate the frequency of tweets for a given search and then continuously vary the time between calls so that I can get as close to 100 tweets as possible in a call. Any ideas suggestions that can suggest ways to alleviate the above will be highly appreciated. Thanks Rahul.
Re: [twitter-dev] Re: Application based on Search API
There is whitelisting for the search API specifically. ---Mark http://twitter.com/mccv On Wed, Mar 10, 2010 at 5:48 AM, Andrew Badera and...@badera.us wrote: So you want to use the Streaming API, primarily, for anything realtime. Maybe the Search API in a supplementary fashion ... is there whitelisting for the Search API specifically? --ab On Wed, Mar 10, 2010 at 5:21 AM, Diz sitov.crist...@gmail.com wrote: Okie, closing the Pandora's box! I never specified that my app will generate an API! I also didn't specify anything about resyndicating content. I just want to offer real-time activity on a web interface, and beside that analyze cached tweets to generate statistics. Anyone, following me?! On Mar 10, 12:33 am, Will Fleming wflemin...@gmail.com wrote: Are the various terms and agreements that currently disallow this published anywhere? After a brief look (perhaps I missed it) at: http://twitter.com/apiruleshttp://twitter.com/toshttp://help.twitter.com/forums/26257/entries/18311 As far as I can tell there isn't anything that explicitly disallows resyndicating or making Twitter data available via an API. The TOS also states: Tip: This license is you authorizing us to make your Tweets available to the rest of the world and to let others do the same. Tip: We encourage and permit broad re-use of Content. The Twitter API exists to enable this. thanks On Mon, Mar 8, 2010 at 10:06 PM, John Kalucki j...@twitter.com wrote: Not at the moment, as we expect that the number of services that this will apply to is small. We'll be clarifying data access and licensing over the next few months. -John Kalucki http://twitter.com/jkalucki Infrastructure, Twitter Inc. On Mon, Mar 8, 2010 at 9:57 PM, Abraham Williams 4bra...@gmail.com wrote: Is the specific set of requirements published anywhere? Abraham On Mon, Mar 8, 2010 at 06:50, John Kalucki j...@twitter.com wrote: Your application description sounds like resyndication, which is not allowed under various terms and agreements. You cannot make Twitter data available via an API unless a very specific set of requirements are adhered to. Contact a...@twitter.com to start this process. -John Kalucki http://twitter.com/jkalucki Infrastructure, Twitter Inc. On Mon, Mar 8, 2010 at 3:37 AM, Diz sitov.crist...@gmail.com wrote: For the last 3 months I am experimenting the Search API. I'm focusing on the geo-location searching capabilities. For the beginning I started with my own city, but my intents are to extend to the major cities of my country: that will be at most ten. My idea of application is to offer real-time activity on each major city, through a proxy that caches all tweets and then serves them further to clients, filtered or non-filtered. Frequency of requests should be between 5 to 10 seconds, and that means I should do between 400 to 800 requests per hour just for one city, and probably between 4000 to 8000 requests for the whole application. My questions are: 1). Should I use Search API, or should I move to the Streaming API?! 2). To whom I should request whitelisting: the usual Search API or the Streaming API?! Thanks! -- Abraham Williams | Community Advocate |http://abrah.am TwitterOAuth |http://github.com/abraham/twitteroauth This email is: [ ] shareable [x] ask first [ ] private.
[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] Non-finite values in Geo Location bounding_box.coordinates
Hi,
Some of the tweets are causing my JSON parser (Json-Lib) to throw
JSON does not allow non-finite numbers exception. Looking at the
tweet, only likely suspect is the new Geo Location field
'bounding_box'.
bounding_box: {
type: Polygon,
coordinates: [
[
[
1.79769313486232e+308,
1.79769313486232e+308
],
[
-1.79769313486232e+308,
1.79769313486232e+308
],
[
-1.79769313486232e+308,
-1.79769313486232e+308
],
[
1.79769313486232e+308,
-1.79769313486232e+308
]
]
]
},
JSON verifiers say they are valid so it's kinda confusing.
Nevertheless, I thought Twitter API team should be aware that some of
the JSON parsers are barfing on tweets like above.
Best,
Don Park
Re: [twitter-dev] Non-finite values in Geo Location bounding_box.coordinates
hi! thanks for the heads up - its a known issue, and we're gunning to have
this rectified ASAP.
On Wed, Mar 10, 2010 at 9:51 AM, Don Park super...@gmail.com wrote:
Hi,
Some of the tweets are causing my JSON parser (Json-Lib) to throw
JSON does not allow non-finite numbers exception. Looking at the
tweet, only likely suspect is the new Geo Location field
'bounding_box'.
bounding_box: {
type: Polygon,
coordinates: [
[
[
1.79769313486232e+308,
1.79769313486232e+308
],
[
-1.79769313486232e+308,
1.79769313486232e+308
],
[
-1.79769313486232e+308,
-1.79769313486232e+308
],
[
1.79769313486232e+308,
-1.79769313486232e+308
]
]
]
},
JSON verifiers say they are valid so it's kinda confusing.
Nevertheless, I thought Twitter API team should be aware that some of
the JSON parsers are barfing on tweets like above.
Best,
Don Park
--
Raffi Krikorian
Twitter Platform Team
http://twitter.com/raffi
Re: [twitter-dev] More Streaming API data, please
Noted. In the plan. [Wait a second, is this Mark McBride on a fake account?] -John Kalucki http://twitter.com/jkalucki Infrastructure, Twitter Inc. On Tue, Mar 9, 2010 at 9:59 PM, Marc Mims marc.m...@gmail.com wrote: The Streaming API is great. It would be better if it included more events. I'd love to see favorites and social graph changes (new friends/followers in the Streaming API. It would drastically reduce the number of polling requests apps need to make to Twitter. @semifor
[twitter-dev] Re: Non-finite values in Geo Location bounding_box.coordinates
Boy, that was fast Raffi. Thx! :-)
Re: [twitter-dev] More Streaming API data, please
* John Kalucki j...@twitter.com [100310 09:56]: Noted. In the plan. [Wait a second, is this Mark McBride on a fake account?] No. Haven't met Mark McBride, yet, but I'm sure I'm not him. And I'm real---at least I think so. But you've got me worried, now. :) @semifor, Marc-with-a-cee, the Net::Twitter guy
Re: [twitter-dev] Facing problem with rate-limit.
Probably. But the text I referenced means each non-whitelisted account on a whitelisted IP gets 20k/hour. Abraham On Wed, Mar 10, 2010 at 02:19, Rushikesh Bhanage rishibhan...@gmail.comwrote: Hi, Thank you for the reply. I understand what you are saying, but is it possible to get more than one user account whitelisted? When I looked at the whitelisting form, it suggests to add IPs and not user accounts. Let me know please, Thank you. On Tue, Mar 9, 2010 at 10:19 PM, Abraham Williams 4bra...@gmail.comwrote: If you make the requests authenticated as your users each one will have 20k hits per hour. Each whitelisted entity, whether an account or IP address, is allowed 2 requests per hour. This means that two authenticated users using the same IP address would each get 2 requests per hour. - http://apiwiki.twitter.com/Rate-limiting Depending on your application you can cache all the user objects and then use the Social Graph APIs to find missing profiles. Abraham On Tue, Mar 9, 2010 at 02:37, Rushikesh Bhanage rishibhan...@gmail.comwrote: Hi , We are building a twitter application which needs to collect all the followers of the user to show him results. Now when we looked at following user's: user Followers ev - 1,172,553 aplusk -4,627,964 Kim Kardashian - 3,144,680 such users through our application it turns out 20,000 calls per white-listed IP without breaking operation, are not sufficient to collect all the followers of these users. Because every cursor id gives only 100 follower's data which means 20,000 calls are not sufficient for some users with extensive followers. Eagerly looking for solution, Thank you. Regards, Rushikesh. -- Abraham Williams | Community Advocate | http://abrah.am TwitterOAuth | http://github.com/abraham/twitteroauth This email is: [ ] shareable [x] ask first [ ] private. -- Abraham Williams | Community Advocate | http://abrah.am TwitterOAuth | http://github.com/abraham/twitteroauth This email is: [ ] shareable [x] ask first [ ] private.
[twitter-dev] Re: 502 errors on user timelines
I am also facing the same issue, https://twitter.com/vsr/status/10199624984 On Mar 10, 3:09 am, Brendan brender...@gmail.com wrote: I've noticed that when trying to get the entire status timeline for some users (user ID 49777412 was one such user), requesting a page (say the first page) of 200 tweets results in a 502 error. Retrying the request a several seconds (5 seconds, in my case) later succeeds. When requesting the second page of statuses, it again fails, but a few seconds later it succeeds. It seems as though there's some caching issue happening in which the initial request will take too long to return so Twitter returns a 502 error, and by the time the second request happens the data has been retrieved and is ready to serve the request. How should I go about avoiding or reducing the occurrence of these errors? Thanks, Brendan
[twitter-dev] Re: More Streaming API data, please
+1 to more event types but in its own stream if not in addition to the firehose. Applications interested only in these events should not have to drink from the firehose to get those events.
Re: [twitter-dev] Changing the Content-Type header for OAuth token exchanges
This change has been deployed. Let us know if things get wonky. On Mon, Mar 8, 2010 at 3:39 PM, Mark McBride mmcbr...@twitter.com wrote: All - Per issue 1263 (http://code.google.com/p/twitter-api/issues/detail?id=1263) (and the OAuth spec), we're looking to change the Content-Type header for OAuth token exchanges to 'application/x-www-form-urlencoded'. To date it has been 'text/html'. We want to ensure that this will not break existing applications, so if you have any qualms please voice them here. ---Mark http://twitter.com/mccv -- Marcel Molina Twitter Platform Team http://twitter.com/noradio
[twitter-dev] cannot add status to favories with API
Hello!
I want to add a status to another user's favories but apparantly the
api cannot do that.
I want to add message created by one user to favorites of another
user.
When doing it from api it refuses to add favorite probably because the
status id was not created by the same user to whom I want to add this
favorite.
I am looking at instructions here
http://apiwiki.twitter.com/Twitter-REST-API-Method%3A-favorites%C2%A0create
It does not let you specify the username of status creator.
I am using this url with a POST method:
http://api.twitter.com/1/favorites/create/2147483647.json
The status 2147483647 was created by different user (not the same user
to whom I want to add this to favorite)
but then getting this error 404 with this message:
{request:/1/favorites/create/2147483647.json,error:Not found}
How can I change the request in order for this to work?
Re: [twitter-dev] Twitter API Request to Get the List of Friends Who have not followed you back
I think its the simplest of features to implement using existing Twitter API as Scott suggest. Just write a method in your service to fetch friends ids and followers ids and then compare these ids to separate the list of followers ids who are not friends. Then provide links to unfollow these ids on interface. Is that difficult? Not at all. Some client side programming is needed only. Cheers, Alam Sher On Tue, Mar 9, 2010 at 8:46 PM, Dean Collins d...@cognation.net wrote: www.mypostbutler.com does that, basically in the unfollow feature it separates out who follows you back or not you can then see who has no return love for you :( Cheers, Dean -Original Message- From: twitter-development-talk@googlegroups.com [mailto:twitter-development-t...@googlegroups.com] On Behalf Of Scott Wilcox Sent: Tuesday, March 09, 2010 9:58 AM To: twitter-development-talk@googlegroups.com Subject: Re: [twitter-dev] Twitter API Request to Get the List of Friends Who have not followed you back There is no API endpoint for this. You will need to build it clientside yourself. Get your list of followers and friends and then compare. Scott. On 9 Mar 2010, at 10:51, Durrab wrote: Hello, My name is Durrab and I want Twitter to Provide one more API Request as those Friends who have not followed your. For Example: http://api.twitter.com/1/friends/notfollowed/ids.format Thanks Regards: Durrab -- ___ Alam Sher Khan +92 331 505 5549
[twitter-dev] Re: Introduce yourself!
I am Pranav Bhat, Masters student, Software developer ( prefers programming in C#) and currently working on a web based and desktop based twitter client using JQuery for the web and WPF for the desktop :) Have used Twitter since the mid of 2007 but only as a user; developing on Twitter for the first time as my hobby project :) Hoping to get involved in this group and have some good conversations around ;) @pranavbhat On Feb 19, 3:20 pm, Abraham Williams 4bra...@gmail.com wrote: We have not had an introductions thread in a long time (or ever that I could find) so I'm starting one. Don't forget to add an answer to the tools thread [1](Gmail link [2]) as well. I'm Abraham Williams, I've been working with the Twitter API and this group since early 2008. I do mostly freelance Drupal and Twitter API integration and personal projects. I love seeing the creative projects developers build or integrate with the API and look forward to meeting many of you at Chirp. TwitterOAuth [3] the first PHP library to support OAuth is built and maintained by me, and will hopefully see a new release soon. I also built a fun Chrome extension [4] that integrates common friends and followers into Twitter profiles. The feature I would most like added to the API is a conversation method to get replies to a specific status. So. Who are you, what do you do, what have you built, and what feature do you most want to see added? @Abraham [1]http://groups.google.com/group/twitter-development-talk/browse_thread... [2]https://mail.google.com/mail/#inbox/12680cd0fa59011e [3]https://chrome.google.com/extensions/detail/npdjhmblakdjfnnajeomfbogo... [4]http://code.google.com/p/twitter-api/issues/detail?id=142 -- Abraham Williams | Community Advocate |http://abrah.am Project | Out Loud |http://outloud.labs.poseurtech.com This email is: [ ] shareable [x] ask first [ ] private. Sent from Seattle, WA, United States
[twitter-dev] how do we get the via Client name on Tweets
Hello all, I wanted to know how do we get our client name at the end of every tweet. Like for eg: At the end of a tweet, the website says via API or via TweetDeck. I wanted to know how do we get that to be our client name like Tweetdeck did? Thanks, Pranz B
Re: [twitter-dev] how do we get the via Client name on Tweets
You have to use OAuth. http://apiwiki.twitter.com/FAQ#HowdoIget“fromMyApp”appendedtoupdatessentfrommyAPIapplication http://apiwiki.twitter.com/FAQ#HowdoIget“fromMyApp”appendedtoupdatessentfrommyAPIapplication Ryan On Wed, Mar 10, 2010 at 4:02 PM, pranzb bhatpra...@gmail.com wrote: Hello all, I wanted to know how do we get our client name at the end of every tweet. Like for eg: At the end of a tweet, the website says via API or via TweetDeck. I wanted to know how do we get that to be our client name like Tweetdeck did? Thanks, Pranz B
Re: [twitter-dev] how do we get the via Client name on Tweets
It has to be a registered app which uses OAuth. (Existing non-OAuth apps were grand-fathered in when this policy was adopted) On Wed, Mar 10, 2010 at 4:02 PM, pranzb bhatpra...@gmail.com wrote: Hello all, I wanted to know how do we get our client name at the end of every tweet. Like for eg: At the end of a tweet, the website says via API or via TweetDeck. I wanted to know how do we get that to be our client name like Tweetdeck did? Thanks, Pranz B
Re: [twitter-dev] cannot add status to favories with API
There is no status with that ID:
https://api.twitter.com/statuses/show/2147483647.xml
Abraham
On Wed, Mar 10, 2010 at 12:41, Dmitri Snytkine d.snytk...@gmail.com wrote:
Hello!
I want to add a status to another user's favories but apparantly the
api cannot do that.
I want to add message created by one user to favorites of another
user.
When doing it from api it refuses to add favorite probably because the
status id was not created by the same user to whom I want to add this
favorite.
I am looking at instructions here
http://apiwiki.twitter.com/Twitter-REST-API-Method%3A-favorites%C2%A0create
It does not let you specify the username of status creator.
I am using this url with a POST method:
http://api.twitter.com/1/favorites/create/2147483647.json
The status 2147483647 was created by different user (not the same user
to whom I want to add this to favorite)
but then getting this error 404 with this message:
{request:/1/favorites/create/2147483647.json,error:Not found}
How can I change the request in order for this to work?
--
Abraham Williams | Community Advocate | http://abrah.am
TwitterOAuth | http://github.com/abraham/twitteroauth
This email is: [ ] shareable [x] ask first [ ] private.
Re: [twitter-dev] Re: 404 Errors on friends and followers using cursors
And by soon I mean today. It should be fixed now. Let me know if this recurs. ---Mark http://twitter.com/mccv On Tue, Mar 9, 2010 at 6:54 PM, Mark McBride mmcbr...@twitter.com wrote: Very soon. ---Mark http://twitter.com/mccv On Tue, Mar 9, 2010 at 5:02 PM, Shannon Whitley shannon.whit...@gmail.com wrote: I've been hitting this a lot lately with data for my own id. It's a huge issue. I'm happy to see that it's been marked as a high priority, but it's been around for months. Do we have an estimate for a fix? Thanks!
Re: [twitter-dev] Tips to avoid hitting rate limits for my movie monitoring application.
thanks john - I have not considered the implication of search results being returned by relevance - I will give the streaming API a shot - On Wed, Mar 10, 2010 at 2:28 PM, John Kalucki j...@twitter.com wrote: We'd like to offer phrase search, or at least AND search on the Streaming API, but we've had other priorities recently. Note that Search is not intended for repeated automated keyword queries, and that Search results are filtered for relevance. If you need all the Tweets, or if you need them in real-time, the Streaming API is the best answer. The Search API is mostly intended for complex, historical backfill, ad hoc, and direct-display-to-user queries. -John Kalucki http://twitter.com/jkalucki Infrastructure, Twitter Inc. On Wed, Mar 10, 2010 at 12:23 AM, Rahul Dighe rsdigh...@googlemail.comwrote: thanks - I need to put more thought into this - I am inclined to feel that at the moment that the search api will probably deliver better resuls - as the cost of filtering thousands and thousands of records for even something as basic as a movie called New York or Independence Day split into independent words will probably be cost intensive and might end up being looking for a needle in the haystack. Having said that I think Twitter has surely come up with this API with good thought - it's just needs further analysis from my end with regards to whether the cost of filtering outweigh the benefits from getting real time streaming resuls. thanks rahul. On Tue, Mar 9, 2010 at 9:10 PM, Mark McBride mmcbr...@twitter.comwrote: This is correct. The general advice is to choose the most specific keyword to track (probably locker and blind in this case), then run an additional layer of filtering on your side. There are higher access levels available that grant you more than 200 keywords to track. ---Mark http://twitter.com/mccv On Tue, Mar 9, 2010 at 12:36 PM, Rahul Dighe rsdigh...@googlemail.comwrote: Hello, Correct me if I am wrong but doesn't the streaming API has limitation that allow me to only track 200 keywords.. and also with the added caveat that - *Track keywords are case-insensitive logical ORs. Terms are exact-matched, and also exact-matched ignoring punctuation. Phrases, keywords with spaces, are not supported. Keywords containing punctuation will only exact match tokens. Some UTF-8 keywords will not match correctly- this is a known temporary defect.* If this is the case how will the api track keywords such as The Hurt Locker or The Blind Side? Thanks Rahul Dighe On Mon, Mar 8, 2010 at 11:42 PM, Mark McBride mmcbr...@twitter.comwrote: This sounds like a perfect use case for the streaming API. The rate limits there are different, but in general more permissive. And because you're doing primarily OR queries, the current track functionality seems sufficient. ---Mark http://twitter.com/mccv On Mon, Mar 8, 2010 at 3:21 PM, Rahul rsdigh...@googlemail.comwrote: Hello, I am building an application that monitors tweets about movies(for now with... other interesting things planned). I have my id whitelisted but I want to avoid overusing it. The challenge that I face is that ideally I want to make full use of the opportunity to retrieve 100 tweets per call and for that I need information on the frequency with which users are tweeting about a movie and then set my call frequency (to call twitter search api) accordingly so that I maximize the number of tweets returned per call or atleast. Since I presume there is no way to know what frequency is someone tweeting about a movie - I need help is what is the best way to optimize for such a situation. The challenge is complicated by the fact that users tweet about different movies at different rates and the rates generally decrease overtime. I have tried combining searches - but the challenge is that lets say I search for (Movie A OR Movie B) (Movie C OR Movie D) it could be the case that people tweet about Movie A B a lot and litle to none about C or D or there is a combination in which they continue to tweet about A but not about B - So I still can end up in a situation where I am not optimizing my calls. Also situations such as Oscars can dramatically change what people talk about even about movies out months ago. I have thought of writing something such as a variable frequency caller that can check the frequency of tweets for the last 3 calls in order to appreciate the frequency of tweets for a given search and then continuously vary the time between calls so that I can get as close to 100 tweets as possible in a call. Any ideas suggestions that can suggest ways to alleviate the above will be highly appreciated. Thanks Rahul.
[twitter-dev] Re: cannot add status to favories with API
Hah, apparently PHP doesn't understand integers larger than
2147483647,
so when casting larger number to integer, it automatically becomes
2147483647
This is something new, but that's how it is: in php $status =
'10279397649'; $status = (int)$status;
php chokes on any number larger than 2147483647 and instead of
throwing an error in quietly returns
the largest integer in it knows, 2147483647
I did not expect this from a fairly new version of php 5.2.9
On Mar 10, 4:27 pm, Abraham Williams 4bra...@gmail.com wrote:
There is no status with that
ID:https://api.twitter.com/statuses/show/2147483647.xml
Abraham
On Wed, Mar 10, 2010 at 12:41, Dmitri Snytkine d.snytk...@gmail.com wrote:
Hello!
I want to add a status to another user's favories but apparantly the
api cannot do that.
I want to add message created by one user to favorites of another
user.
When doing it from api it refuses to add favorite probably because the
status id was not created by the same user to whom I want to add this
favorite.
I am looking at instructions here
http://apiwiki.twitter.com/Twitter-REST-API-Method%3A-favorites%C2%A0...
It does not let you specify the username of status creator.
I am using this url with a POST method:
http://api.twitter.com/1/favorites/create/2147483647.json
The status 2147483647 was created by different user (not the same user
to whom I want to add this to favorite)
but then getting this error 404 with this message:
{request:/1/favorites/create/2147483647.json,error:Not found}
How can I change the request in order for this to work?
--
Abraham Williams | Community Advocate |http://abrah.am
TwitterOAuth |http://github.com/abraham/twitteroauth
This email is: [ ] shareable [x] ask first [ ] private.
Re: [twitter-dev] twitter application in flex
I use the coldfusion stuff that is in the twitter api page. great place to learn coldfusion and of coarse works well with Flex On Tue, Feb 16, 2010 at 12:17 PM, Geo Paul geopa...@gmail.com wrote: hi I recently started learning flex and some sort of api programming. I found the twitter api for actionscript so simple so that I made an application and updated myself using it. I am thinking of adding some more features to it. Is there a way to make a TwitterUser instance with our userid?...(the persone who is logged in). Is there a way?.I find that there is no good documentation for TwitterScript anywhere.. So If anybody find a solution please mail me!! Geo Paul
Re: [twitter-dev] twitter application in flex
On Tue, Feb 16, 2010 at 1:17 PM, Geo Paul geopa...@gmail.com wrote: hi I recently started learning flex and some sort of api programming. I found the twitter api for actionscript so simple so that I made an application and updated myself using it. I am thinking of adding some more features to it. Is there a way to make a TwitterUser instance with our userid?...(the persone who is logged in). Is there a way?.I find that there is no good documentation for TwitterScript anywhere.. So If anybody find a solution please mail me!! I use Classic ASP. It is very easy to find Classic ASP code for use with twitter. PHP code for Twitter is also very easy to find.
Re: [twitter-dev] Non-finite values in Geo Location bounding_box.coordinates
hi! thanks for the heads up - its a known issue, and we're gunning to have this rectified ASAP. This hit TTYtter as well, although I'm just rolling out a change to make it accept the numbers, since they are syntactically valid. -- personal: http://www.cameronkaiser.com/ -- Cameron Kaiser * Floodgap Systems * www.floodgap.com * ckai...@floodgap.com -- The things which hurt, instruct. -- Benjamin Franklin --
[twitter-dev] Search and 502 bad gateway status
I notice that I sometimes get a bad gateway status 502 error. When I replicate the search using the Advanced search page, say with only a 'from user', and geocode and since date specified, I also get the 502 error with the Twitter unavailable page. However, if I simply remove some of the undefined query parameters from the search stringit works. Is there a limit in the number of search query parameters??
