[twitter-dev] Re: Tweet Streaming API - About temp Tweet Storage in the stream mid-way/Push Techniques
Also as the query limit is restricted for basic role, does it mean for high tweets arrival in those limited queries would somehow be rate- limited meaning track-limited status would appear, what should I do in that case? Does it somehow lead to BAN my client-app @ twitter forever? Do I need to hold my connections during track-limitation notice OR should I continue receiving tweets? --Deepak -- 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: Tweet Streaming API - About temp Tweet Storage in the stream mid-way/Push Techniques
Seems like this is the place to go for understanding this kind of situation handling http://dev.twitter.com/pages/streaming_api_concepts Thanks anyways, --Deepak -- 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: Conversation stream
I'd be really interested to know if this function becomes reliable and incorporated into the API. I can't actually get it to work at the moment though, I get Twitter's 'The page you were looking for doesn't exist' sent back... S. On Mar 31, 1:51 pm, George georgyy.koz...@gmail.com wrote: Hi Folks, My team is working on new Twitter client and we're interested in some specific options in Twitter API. Of course I know that some features already requested and this one was asked however I think we should rise up it again. I've found hidden call on Twitter which allows us to receive conversation tread between the users.http://search.twitter.com/search/thread/status ID The above call return correct data for some statuses but for another ones it may return nothing or even return wrong data, Does anybody know something about this call? Maybe we need to supply additional parameters? Is it possible to obtain conversation thread between two users somehow not using of above call. Thanks in advance, George -- 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] How to get the Friends ip address
Hi Team, We are integrating the Twetter api in one our site and we require to get the current location of the user who post the tweets. Any clues or suggestion ? Regards, -Mukesh Srivastav, India, Hyderabad. -- 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] How to get the Friends ip address
This is only possible if geotagging is enabled for the device where the tweet came from. Check this link for more details -: http://apiwiki.twitter.com/w/page/22554649/Geotagging-API-Best-Practices The API returns latitude and logitude not ip-addresses as you mentioned in the subject. Regards Umashankar Das On Fri, Apr 1, 2011 at 2:32 PM, Mukesh Srivastav mukicha...@gmail.comwrote: Hi Team, We are integrating the Twetter api in one our site and we require to get the current location of the user who post the tweets. Any clues or suggestion ? Regards, -Mukesh Srivastav, India, Hyderabad. -- 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] TwitterApi.1.3.swc
In process to create Twitter client App with GoogleTwitterApi.1.3.swc, I came across stream error. Pls take a look at the following Page I indicated wthat I did and messages that I'm facing. http://pengpeng.chips.jp/twitter/TwitterAPI.htm I made a same question to support Twitter API Policy. And their answer. But I can't figure out how I modify my code. QUOTE Based on your code, it looks like you are still trying to send basic auth credentials (username and password). Twitter no longer supports basic authentication in the API. You will need to convert your application to OAuth instead. For more information, please see http://dev.twitter.com/pages/basic_to_oauth . In addition, make sure you use the correct endpoints for API calls, such as http://api.twitter.com/1/statuses/friends_timeline/TOMIYASU_chan.xml instead of http://twitter.com/statuses/friends_timeline/TOMIYASU_chan.xml QUOTE END -- 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: Conversation stream
Hi Stu, I'm also interested in the mentioned question). Link that I've shared should work for you, just take a note that it will work only for replied statuses. I know the ID of my status (tweet) which was reply to another one, so if we'll pass this ID to the call: http://search.twitter.com/search/thread/53014618771165184 Twitter will show you a conversation page, however sometimes it works strange. Does anybody know right way how to obtain conversation thread from the Twitter? Regards, George On Apr 1, 11:33 am, Stu stuart.batter...@gmail.com wrote: I'd be really interested to know if this function becomes reliable and incorporated into the API. I can't actually get it to work at the moment though, I get Twitter's 'The page you were looking for doesn't exist' sent back... S. On Mar 31, 1:51 pm, George georgyy.koz...@gmail.com wrote: Hi Folks, My team is working on new Twitter client and we're interested in some specific options in Twitter API. Of course I know that some features already requested and this one was asked however I think we should rise up it again. I've found hidden call on Twitter which allows us to receive conversation tread between the users.http://search.twitter.com/search/thread/status ID The above call return correct data for some statuses but for another ones it may return nothing or even return wrong data, Does anybody know something about this call? Maybe we need to supply additional parameters? Is it possible to obtain conversation thread between two users somehow not using of above call. Thanks in advance, George -- 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] Reg: unauthorirzed error while getting profile url
Hi, Currently i am using oAuth to get the public profile of the twitter Details are: _oauth.oAuthWebRequest(oAuthTwitter.Method.GET, https:// api.twitter.com/account/verify_credentials.xml,string.Empty); this is the webrequest i am using to get the profile but this is working in an intermitten way. Its throwing error like : ?xml version=1.0 encoding=UTF-8? hash request/account/verify_credentials.xml? oauth_consumer_key=oX9ZTIjxulA1dTpWPk7HAamp;oauth_nonce=8868298amp;oauth_signature_method=HMAC- SHA1amp;oauth_timestamp=1301663655amp;oauth_token=PYg58LLcIlDFCFFHy0AAi9Z30k0dUKDSFrDAiTjnXkQamp;oauth_verifier=JzN6a5BIE0XCpCh7ER2YjVWkZIxVK4dAYwqYujRnOAamp;oauth_version=1.0amp;oauth_signature=njf2uxyVlBpclvvP4BOzOEF3orU %3d/request errorCould not authenticate you./error /hash Can anyone help me in resolving this issue. And is there any expiry of the access token that was obtained? Thanks, Yashwanth Konathala. -- 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] Reg: unauthorirzed error while getting profile url
Hi Yaswath, While you might have something else wrong additionally, I'll make a couple quick points: a) the URL (and all REST resource URLs) should have a version: you want https://api.twitter.com/1/account/verify_credentials.xml -- if you don't put the version there, your code will stop working completely one day. Without a version there today, you'll get weird behavior. b) Your OAuth query parameters includes an oauth_verifier -- you should only send this parameter to the oauth/access_token step and discard it -- by including it in the request here, you may be invalidating it. If it's possible for you to use HTTP header-based OAuth, I would highly recommend favoring it over this query string approach -- header-based auth is generally easier to debug and easier to get right. Finally, access tokens can be manually expired by the end-user at any time; they don't intrinsically have an expiration time though. @episod http://twitter.com/episod - Taylor Singletary On Fri, Apr 1, 2011 at 6:17 AM, yaswanth kumar yaswanth...@gmail.comwrote: Hi, Currently i am using oAuth to get the public profile of the twitter Details are: _oauth.oAuthWebRequest(oAuthTwitter.Method.GET, https:// api.twitter.com/account/verify_credentials.xml,string.Empty); this is the webrequest i am using to get the profile but this is working in an intermitten way. Its throwing error like : ?xml version=1.0 encoding=UTF-8? hash request/account/verify_credentials.xml? oauth_consumer_key=oX9ZTIjxulA1dTpWPk7HAamp;oauth_nonce=8868298amp;oauth_signature_method=HMAC- SHA1amp;oauth_timestamp=1301663655amp;oauth_token=PYg58LLcIlDFCFFHy0AAi9Z30k0dUKDSFrDAiTjnXkQamp;oauth_verifier=JzN6a5BIE0XCpCh7ER2YjVWkZIxVK4dAYwqYujRnOAamp;oauth_version=1.0amp;oauth_signature=njf2uxyVlBpclvvP4BOzOEF3orU %3d/request errorCould not authenticate you./error /hash Can anyone help me in resolving this issue. And is there any expiry of the access token that was obtained? Thanks, Yashwanth Konathala. -- 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] TwitterApi.1.3.swc
Hi there, As the good folks at a...@twitter.com said, the code you're using utilizes basic auth (a combination of username password) which is no longer supported with the API. You'll need to either adapt your library to use OAuth or find a new Twitter library that uses OAuth. There is at least one AS3-based OAuth library in existence: http://code.google.com/p/oauth-as3/ @episod http://twitter.com/episod - Taylor Singletary On Fri, Apr 1, 2011 at 5:53 AM, MANABUF pingping_hir...@yahoo.co.jp wrote: In process to create Twitter client App with GoogleTwitterApi.1.3.swc, I came across stream error. Pls take a look at the following Page I indicated wthat I did and messages that I'm facing. http://pengpeng.chips.jp/twitter/TwitterAPI.htm I made a same question to support Twitter API Policy. And their answer. But I can't figure out how I modify my code. QUOTE Based on your code, it looks like you are still trying to send basic auth credentials (username and password). Twitter no longer supports basic authentication in the API. You will need to convert your application to OAuth instead. For more information, please see http://dev.twitter.com/pages/basic_to_oauth . In addition, make sure you use the correct endpoints for API calls, such as http://api.twitter.com/1/statuses/friends_timeline/TOMIYASU_chan.xml instead of http://twitter.com/statuses/friends_timeline/TOMIYASU_chan.xml QUOTE END -- 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: Streaming API Rate Limiting
As a side note, currently only 3-4% of the total tweets (firehose) are geo-tagged and are eligible to be selected in a stream location bounding box. If the current firehose rate is about 140M tweets/day, that makes ~5M eligible tweets/day. I do not know what the proportion of tweets from the US is but I would think 50% seem reasonable and would result in ~2.5M tweets/day. Even if we lower that proportion, your 50 000 tweets/day seems way off. There are 3 possibilities, 1) you are being rate limited more than you think, 2) your bounding box is wrong or 3) your bounding box is too large and Twitter has reduced it somehow. I remember I read somewhere in the api doc that each bounding box could not be more than 1 degree square enough to cover most metropolitan areas - but I cannot find that back. Colin On Mar 31, 4:08 pm, Data Gatherer gatherer...@gmail.com wrote: We have a bounding box set for the United States. Even though it's a large box, we only receive about 50,000 tweets a day. However, I see that we get rate limited at least once a week already. The box is large, but the number of matching results is fairly low. Knowing how the rate limiting works more specifically would be important when trying to gather data for other projects (more bounding boxes, other keywords). On Mar 31, 3:50 pm, Jeremy Dunck jdu...@gmail.com wrote: On Thu, Mar 31, 2011 at 2:48 PM, Augusto Santos augu...@gemeos.org wrote: No it won't. Streaming has rate limit with around 1% of firehose, if your search term os too much generic. If your search term or bouding box get too many tweets, you will start receive 'limit' status message as doc said. http://dev.twitter.com/pages/streaming_api_concepts#parsing-responses Sure, I understand that, I just meant to say that 1% of all tweets is a lot (140M average per day now). If your terms are not very general, you have a lot of head room. -- 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: Does anyone has Javascript function to convert date into twitter time format
If you pull the full documented source for the rather excellent twitter
widgets (http://twitter.com/widgets), you'll find exactly the routine to do
this.
/**
* relative time calculator
* @param {string} twitter date string returned from Twitter API
* @return {string} relative time like 2 minutes ago
*/
var timeAgo = function(dateString) {
The file has a large comment at the top
* For full documented source see
http://twitter.com/javascripts/widgets/widget.js
* Hosting and modifications of the original source IS allowed.
It also contains gems such as the Twitalinkahashifyer - handy routines for
linking @user and the like
--
Tim
--
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: Conversation stream
Ah I see. I was appending .json to the status in an attempt to get that. I didn't expect HTML! I guess this probably won't stay around for long as it doesn't look like a method made specifically as an API method. The current solution is to follow the in_reply_to fields that the API sends back, stepping through the conversation as you go.. but unless you have the full streaming API this requires lots of calls to the REST api, and you'll get rate limited fairly soon. :-( S. On Apr 1, 10:39 am, George georgyy.koz...@gmail.com wrote: Hi Stu, I'm also interested in the mentioned question). Link that I've shared should work for you, just take a note that it will work only for replied statuses. I know the ID of my status (tweet) which was reply to another one, so if we'll pass this ID to the call:http://search.twitter.com/search/thread/53014618771165184 Twitter will show you a conversation page, however sometimes it works strange. Does anybody know right way how to obtain conversation thread from the Twitter? Regards, George On Apr 1, 11:33 am, Stu stuart.batter...@gmail.com wrote: I'd be really interested to know if this function becomes reliable and incorporated into the API. I can't actually get it to work at the moment though, I get Twitter's 'The page you were looking for doesn't exist' sent back... S. On Mar 31, 1:51 pm, George georgyy.koz...@gmail.com wrote: Hi Folks, My team is working on new Twitter client and we're interested in some specific options in Twitter API. Of course I know that some features already requested and this one was asked however I think we should rise up it again. I've found hidden call on Twitter which allows us to receive conversation tread between the users.http://search.twitter.com/search/thread/status ID The above call return correct data for some statuses but for another ones it may return nothing or even return wrong data, Does anybody know something about this call? Maybe we need to supply additional parameters? Is it possible to obtain conversation thread between two users somehow not using of above call. Thanks in advance, George -- 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: GET :user/lists/:id/statuses stopped working
The twitter widget used to call the old address, but a new version was posted a couple of days ago (without incrementing the version number in the comment at the top) that construct URLs of the 2nd form... guess they standardised this and I'm pretty sure it changed over only in the last week or so. Line 844 of the documented source changed from var listBase = http + domain + '/'; to var listBase = http + 'api.' + domain + '/1/'; What can be annoying is that Google Chrome incorrectly is overly aggressive about caching dynamically loaded javascript files (see http://code.google.com/p/chromium/issues/detail?id=37711) , so for some Chrome users list widgets won't display properly since the change unless you explicitly add a cache-buster or similar (yeah, spent an hour trying to figure what I'd done wrong just this morning) -- T -- 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] Is the documentation site outdated?
Hi, At http://dev.twitter.com/pages/libraries#php I'm under the impression that a few of the libraries that are listed don't use oAuth. As far as I know, support for authentication without oAuth has been dropped (quite a while ago), so those libraries which don't use oAuth won't work and are completely obsolete and useless. Why are they listed? Is there a more up-to-date list including only libraries that can be actually used today, so that one doesn't have to waste time discarding useless libraries? thanks m. -- 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] Raven Poster
Does anyone using raven poster? I'm working with this, but is bad.. I need to register callbacks to autorize accounts, but the user guide says that i can use a lot of account... but dev.twitter says i cannot register more than 5 domains.. someone can help me? PLEASE!! i've inverted a lot of money in raven poster.. -- 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] Is the documentation site outdated?
Yes, that list is slightly out of date. For PHP, use: https://github.com/jmathai/twitter-async or https://github.com/abraham/twitteroauth On 1 Apr 2011, at 17:52, Matteo Sisti Sette wrote: Hi, At http://dev.twitter.com/pages/libraries#php I'm under the impression that a few of the libraries that are listed don't use oAuth. As far as I know, support for authentication without oAuth has been dropped (quite a while ago), so those libraries which don't use oAuth won't work and are completely obsolete and useless. Why are they listed? Is there a more up-to-date list including only libraries that can be actually used today, so that one doesn't have to waste time discarding useless libraries? thanks m. -- 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 -- Scott Wilcox @dordotky | sc...@dor.ky | http://dor.ky +44 (0) 7538 842418 | +1 (646) 827-0580 -- 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] Raven Poster
If you're max'ing out on the domains, there isn't anything you can do about that. I'd also point out that you should check whether or not the 'application' you've purchased fits within the Twitter automation guidelines. On 1 Apr 2011, at 17:54, Josue Rodriguez wrote: Does anyone using raven poster? I'm working with this, but is bad.. I need to register callbacks to autorize accounts, but the user guide says that i can use a lot of account... but dev.twitter says i cannot register more than 5 domains.. someone can help me? PLEASE!! i've inverted a lot of money in raven poster.. -- 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 -- Scott Wilcox @dordotky | sc...@dor.ky | http://dor.ky +44 (0) 7538 842418 | +1 (646) 827-0580 -- 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] Is the documentation site outdated?
Thanks a lot! m. On 04/01/2011 06:59 PM, Scott Wilcox wrote: Yes, that list is slightly out of date. For PHP, use: https://github.com/jmathai/twitter-async or https://github.com/abraham/twitteroauth On 1 Apr 2011, at 17:52, Matteo Sisti Sette wrote: Hi, At http://dev.twitter.com/pages/libraries#php I'm under the impression that a few of the libraries that are listed don't use oAuth. As far as I know, support for authentication without oAuth has been dropped (quite a while ago), so those libraries which don't use oAuth won't work and are completely obsolete and useless. Why are they listed? Is there a more up-to-date list including only libraries that can be actually used today, so that one doesn't have to waste time discarding useless libraries? thanks m. -- 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 -- Scott Wilcox @dordotky | sc...@dor.ky | http://dor.ky +44 (0) 7538 842418 | +1 (646) 827-0580 -- 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] Raven Poster
Judging from the website, I cannot recommend that you proceed utilizing a tool like Raven Poster. That said, the registered domains feature of dev.twitter.com relates to usage in the @Anywhere API framework and has nothing to do with OAuth 1.0a-based integrations. If this application is making use of @Anywhere registered domains, it's likely doing something fishy. I imagine that you're probably missing something in the application's instructions. I would recommend staying away from any software that claims to have sophisticated human emulation modules or has to dedicate whole pages on its site explaining how legal safe the tool is. @episod http://twitter.com/episod - Taylor Singletary On Fri, Apr 1, 2011 at 10:01 AM, Scott Wilcox sc...@dor.ky wrote: If you're max'ing out on the domains, there isn't anything you can do about that. I'd also point out that you should check whether or not the 'application' you've purchased fits within the Twitter automation guidelines. On 1 Apr 2011, at 17:54, Josue Rodriguez wrote: Does anyone using raven poster? I'm working with this, but is bad.. I need to register callbacks to autorize accounts, but the user guide says that i can use a lot of account... but dev.twitter says i cannot register more than 5 domains.. someone can help me? PLEASE!! i've inverted a lot of money in raven poster.. -- 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 -- Scott Wilcox @dordotky | sc...@dor.ky | http://dor.ky +44 (0) 7538 842418 | +1 (646) 827-0580 -- 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] Is site API going to go live anytime soon
Hi There. We are building a Twitter application that need to stream all it users update and compute some metrics. After investigating, the Site Stream API seems t be the only viable way to do it. However, our team is reluctant on building something on it as it is in beta: - The service we are building will be very update hungry: it need to get all updates for all it users: As per the documentation, a stream should not serve more than 100 user. - An app that need to open more that a thousand connection need to coordinate with the the #devteam. This leave us only with: 100k users that we'll be able to serve out of the box. However this limit seems very small the service will need to service around 5M users if it work well. So my question is: Will the #devteam will grant access to such a service that need millions of user's feed to be streamed? Thanks. -- 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: Streaming API Rate Limiting
Sorry Colin, but where did you get this information? Doesn't match with the reality. Not at all. On Fri, Apr 1, 2011 at 12:35 PM, Colin Surprenant colin.surpren...@gmail.com wrote: As a side note, currently only 3-4% of the total tweets (firehose) are geo-tagged and are eligible to be selected in a stream location bounding box. If the current firehose rate is about 140M tweets/day, that makes ~5M eligible tweets/day. I do not know what the proportion of tweets from the US is but I would think 50% seem reasonable and would result in ~2.5M tweets/day. Even if we lower that proportion, your 50 000 tweets/day seems way off. There are 3 possibilities, 1) you are being rate limited more than you think, 2) your bounding box is wrong or 3) your bounding box is too large and Twitter has reduced it somehow. I remember I read somewhere in the api doc that each bounding box could not be more than 1 degree square enough to cover most metropolitan areas - but I cannot find that back. Colin On Mar 31, 4:08 pm, Data Gatherer gatherer...@gmail.com wrote: We have a bounding box set for the United States. Even though it's a large box, we only receive about 50,000 tweets a day. However, I see that we get rate limited at least once a week already. The box is large, but the number of matching results is fairly low. Knowing how the rate limiting works more specifically would be important when trying to gather data for other projects (more bounding boxes, other keywords). On Mar 31, 3:50 pm, Jeremy Dunck jdu...@gmail.com wrote: On Thu, Mar 31, 2011 at 2:48 PM, Augusto Santos augu...@gemeos.org wrote: No it won't. Streaming has rate limit with around 1% of firehose, if your search term os too much generic. If your search term or bouding box get too many tweets, you will start receive 'limit' status message as doc said. http://dev.twitter.com/pages/streaming_api_concepts#parsing-responses Sure, I understand that, I just meant to say that 1% of all tweets is a lot (140M average per day now). If your terms are not very general, you have a lot of head room. -- 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: Streaming API Rate Limiting
All of my experiences with geotagging show that about 0.3% to 0.5% of tweets have these codes. I'd be curious to know if that matches what others have found. On Fri, Apr 1, 2011 at 2:40 PM, Augusto Santos augu...@gemeos.org wrote: Sorry Colin, but where did you get this information? Doesn't match with the reality. Not at all. On Fri, Apr 1, 2011 at 12:35 PM, Colin Surprenant colin.surpren...@gmail.com wrote: As a side note, currently only 3-4% of the total tweets (firehose) are geo-tagged and are eligible to be selected in a stream location bounding box. If the current firehose rate is about 140M tweets/day, that makes ~5M eligible tweets/day. I do not know what the proportion of tweets from the US is but I would think 50% seem reasonable and would result in ~2.5M tweets/day. Even if we lower that proportion, your 50 000 tweets/day seems way off. There are 3 possibilities, 1) you are being rate limited more than you think, 2) your bounding box is wrong or 3) your bounding box is too large and Twitter has reduced it somehow. I remember I read somewhere in the api doc that each bounding box could not be more than 1 degree square enough to cover most metropolitan areas - but I cannot find that back. Colin On Mar 31, 4:08 pm, Data Gatherer gatherer...@gmail.com wrote: We have a bounding box set for the United States. Even though it's a large box, we only receive about 50,000 tweets a day. However, I see that we get rate limited at least once a week already. The box is large, but the number of matching results is fairly low. Knowing how the rate limiting works more specifically would be important when trying to gather data for other projects (more bounding boxes, other keywords). On Mar 31, 3:50 pm, Jeremy Dunck jdu...@gmail.com wrote: On Thu, Mar 31, 2011 at 2:48 PM, Augusto Santos augu...@gemeos.org wrote: No it won't. Streaming has rate limit with around 1% of firehose, if your search term os too much generic. If your search term or bouding box get too many tweets, you will start receive 'limit' status message as doc said. http://dev.twitter.com/pages/streaming_api_concepts#parsing-responses Sure, I understand that, I just meant to say that 1% of all tweets is a lot (140M average per day now). If your terms are not very general, you have a lot of head room. -- 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 -- Adam Green Twitter API Consultant and Analyst http://140dev.com, @140dev http://2012twit.com, @2012twit 781-879-2960 -- 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: Conversation stream
Yep, this is HTML end-point, I was also surprised ).
Solution with tons of requests for sake of one conversation is
inadmissible.
I also know about another solution which I've researched in Search
API.
We can call search with specific parameters which will also return us
conversation by one call.
http://search.twitter.com/search.json?result_type=recentq={screen_name1}%20{screen_name2}rpp=50
It works however result can be unexpected time to time.
Unfortunately Twitter can't follow replied theme, so conversation may
looks as random tweets of two users for some period of time.
Does anybody knows better solution? I suppose that there should be
performed some filtering and ordering within application.
Regards,
George
On Apr 1, 7:09 pm, Stu stuart.batter...@gmail.com wrote:
Ah I see. I was appending .json to the status in an attempt to get
that. I didn't expect HTML!
I guess this probably won't stay around for long as it doesn't look
like a method made specifically as an API method.
The current solution is to follow the in_reply_to fields that the API
sends back, stepping through the conversation as you go.. but unless
you have the full streaming API this requires lots of calls to the
REST api, and you'll get rate limited fairly soon. :-(
S.
On Apr 1, 10:39 am, George georgyy.koz...@gmail.com wrote:
Hi Stu,
I'm also interested in the mentioned question).
Link that I've shared should work for you, just take a note that it
will work only for replied statuses.
I know the ID of my status (tweet) which was reply to another one, so
if we'll pass this ID to the
call:http://search.twitter.com/search/thread/53014618771165184
Twitter will show you a conversation page, however sometimes it works
strange.
Does anybody know right way how to obtain conversation thread from the
Twitter?
Regards,
George
On Apr 1, 11:33 am, Stu stuart.batter...@gmail.com wrote:
I'd be really interested to know if this function becomes reliable and
incorporated into the API. I can't actually get it to work at the
moment though, I get Twitter's 'The page you were looking for doesn't
exist' sent back...
S.
On Mar 31, 1:51 pm, George georgyy.koz...@gmail.com wrote:
Hi Folks,
My team is working on new Twitter client and we're interested in some
specific options in Twitter API.
Of course I know that some features already requested and this one was
asked however I think we should rise up it again.
I've found hidden call on Twitter which allows us to receive
conversation tread between the
users.http://search.twitter.com/search/thread/status ID
The above call return correct data for some statuses but for another
ones it may return nothing or even return wrong data,
Does anybody know something about this call? Maybe we need to supply
additional parameters?
Is it possible to obtain conversation thread between two users somehow
not using of above call.
Thanks in advance,
George
--
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: Streaming API Rate Limiting
Clearer Information: From 10th Mar to 31th Mar the average was 1,1M/day and 860K/day of these with lat/long information. On Fri, Apr 1, 2011 at 4:03 PM, Augusto Santos augu...@gemeos.org wrote: Since 6th March setting location via Broswer has been disable, which correponded of around 50% geotagged tweets. And now I'am getting values very similar with you Adam. On Fri, Apr 1, 2011 at 3:56 PM, Adam Green 140...@gmail.com wrote: All of my experiences with geotagging show that about 0.3% to 0.5% of tweets have these codes. I'd be curious to know if that matches what others have found. On Fri, Apr 1, 2011 at 2:40 PM, Augusto Santos augu...@gemeos.org wrote: Sorry Colin, but where did you get this information? Doesn't match with the reality. Not at all. On Fri, Apr 1, 2011 at 12:35 PM, Colin Surprenant colin.surpren...@gmail.com wrote: As a side note, currently only 3-4% of the total tweets (firehose) are geo-tagged and are eligible to be selected in a stream location bounding box. If the current firehose rate is about 140M tweets/day, that makes ~5M eligible tweets/day. I do not know what the proportion of tweets from the US is but I would think 50% seem reasonable and would result in ~2.5M tweets/day. Even if we lower that proportion, your 50 000 tweets/day seems way off. There are 3 possibilities, 1) you are being rate limited more than you think, 2) your bounding box is wrong or 3) your bounding box is too large and Twitter has reduced it somehow. I remember I read somewhere in the api doc that each bounding box could not be more than 1 degree square enough to cover most metropolitan areas - but I cannot find that back. Colin On Mar 31, 4:08 pm, Data Gatherer gatherer...@gmail.com wrote: We have a bounding box set for the United States. Even though it's a large box, we only receive about 50,000 tweets a day. However, I see that we get rate limited at least once a week already. The box is large, but the number of matching results is fairly low. Knowing how the rate limiting works more specifically would be important when trying to gather data for other projects (more bounding boxes, other keywords). On Mar 31, 3:50 pm, Jeremy Dunck jdu...@gmail.com wrote: On Thu, Mar 31, 2011 at 2:48 PM, Augusto Santos augu...@gemeos.org wrote: No it won't. Streaming has rate limit with around 1% of firehose, if your search term os too much generic. If your search term or bouding box get too many tweets, you will start receive 'limit' status message as doc said. http://dev.twitter.com/pages/streaming_api_concepts#parsing-responses Sure, I understand that, I just meant to say that 1% of all tweets is a lot (140M average per day now). If your terms are not very general, you have a lot of head room. -- 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 -- Adam Green Twitter API Consultant and Analyst http://140dev.com, @140dev http://2012twit.com, @2012twit 781-879-2960 -- 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] Search API OR queries returning wrong results
Searches using OR where the result type is recent are returning wrong results. For example, if I search for (ipad kid), I see results from a minute ago. If I search for (ipad backseat), the most recent tweet is about 5 hours ago. Then, if I search (ipad kid) OR (ipad backseat), only the (ipad backseat) results are returned. Aaaron -- 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: Streaming API Rate Limiting
Well, first, In the Gnip Power Track documentation http://docs.gnip.com/w/page/35663947/Power-Track at the has:geo section they say Currently, 'has:geo' is about 2-4% of the full firehose. Also, I ran some tests a few weeks ago to see the difference in content between the search api and the streaming api for equivalent geolocalized searches. See this thread http://groups.google.com/group/twitter-development-talk/browse_thread/thread/a4bf3b7c6373657b# My results showed that the streaming API returns a very small fraction (3% in my tests) of what the search API returns. This is because the streaming API only uses the geotagging API to locate tweets, but the search API uses both the geotagging API and the user location field. For example, I can get around 250 000 tweets/day for San Francisco using the search api but the streaming api will return around 7000 tweets/day. At 7000 tweets/day for San Francisco, 50 000 for the whole US seems small. Colin On Apr 1, 2:40 pm, Augusto Santos augu...@gemeos.org wrote: Sorry Colin, but where did you get this information? Doesn't match with the reality. Not at all. On Fri, Apr 1, 2011 at 12:35 PM, Colin Surprenant colin.surpren...@gmail.com wrote: As a side note, currently only 3-4% of the total tweets (firehose) are geo-tagged and are eligible to be selected in a stream location bounding box. If the current firehose rate is about 140M tweets/day, that makes ~5M eligible tweets/day. I do not know what the proportion of tweets from the US is but I would think 50% seem reasonable and would result in ~2.5M tweets/day. Even if we lower that proportion, your 50 000 tweets/day seems way off. There are 3 possibilities, 1) you are being rate limited more than you think, 2) your bounding box is wrong or 3) your bounding box is too large and Twitter has reduced it somehow. I remember I read somewhere in the api doc that each bounding box could not be more than 1 degree square enough to cover most metropolitan areas - but I cannot find that back. Colin On Mar 31, 4:08 pm, Data Gatherer gatherer...@gmail.com wrote: We have a bounding box set for the United States. Even though it's a large box, we only receive about 50,000 tweets a day. However, I see that we get rate limited at least once a week already. The box is large, but the number of matching results is fairly low. Knowing how the rate limiting works more specifically would be important when trying to gather data for other projects (more bounding boxes, other keywords). On Mar 31, 3:50 pm, Jeremy Dunck jdu...@gmail.com wrote: On Thu, Mar 31, 2011 at 2:48 PM, Augusto Santos augu...@gemeos.org wrote: No it won't. Streaming has rate limit with around 1% of firehose, if your search term os too much generic. If your search term or bouding box get too many tweets, you will start receive 'limit' status message as doc said. http://dev.twitter.com/pages/streaming_api_concepts#parsing-responses Sure, I understand that, I just meant to say that 1% of all tweets is a lot (140M average per day now). If your terms are not very general, you have a lot of head room. -- 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] X-Ratelimit-Reset, Retry-After, and what the actual values mean
I've been looking at the ratelimiting response headers and have found some documentation, but nothing that provides me with sample values and what they mean. I'm developing an application in ColdFusion and using scribe (in java) for the OAuth library. I'm getting the headers back fine (at least X-RateLimit-Reset, I haven't hit the ratelimit for Search to see what it looks like yet) and I can read them in. That isn't the problem. What I'm having difficulty with is what the number that actually comes back. It appears to be a specific time in Seconds since 1/1/1970, but when I do the calculations, regardless of if i've hit the rate-limit I always get a time back that is 1 hour in the future. I feel like I'm just making a stupid mistake and overlooking something, but any help that you can provide would be much appreciated. Thanks, Tom McConlogue -- 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] Twitterizer2.Async.dll
Kindly find my question:- Where do i find Twitterizer2.Async.dll ? -- 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] Multi search type within API
Hi guys, This is pretty much a feeler question to see if its possible to achieve what I am aiming for... I am trying to retrieve a list of tweets which is a combination of hashtags and users. Its for a sports team so I want posts where people are discussing the sports team, but also posts from key people like players and the club twitter account. Is it possible within the api to retrieve this? -- Twitter developer documentation and resources: http://dev.twitter.com/doc API updates via Twitter: http://twitter.com/twitterapi Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list Change your membership to this group: http://groups.google.com/group/twitter-development-talk
[twitter-dev] Open www.twitter.com/home?status= in a frame error
Hi, All We are trying to open www.twitter.com/home?status= in a frame of the page and got the following error: This content cannot be displayed in a frame To help protect the security of information you enter into this website, the publisher of this content does not allow it to be displayed in a frame. What you can try: Open this content in a new window Seems that for security reason, twitter does not allow open its share page in a frame? Is that correct? Can someone please confirm or point to some official doc regarding this restriction? Thanks -- 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] Selecting tweets based on geo_enabled
Hi, I've given this question a fairly long search and not found an answer. In my first experiments with the search API I've been trying to obtain tweets from a specific lat/lon's radius. The responses however include those with geo_enabled = false. Is there a way to filter to obtain only tweets tagged with an actual lat/lon? I was thinking of obtaining first the geoid's nearby and then getting the tweets near those thinking that they would need to be from geo_enabled users. Also I was wondering if the streaming API might give me what I need. Some further playing around should yield an answer but if anyone's been down the path already I'd appreciate some advice. Thanks! -- 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] User mute, sounds reasonable?
I would like to what you think about integrating to the web interface a mute functionality. Yes, it would be similar to follow/unfollow at the end, but I think that having a small list somewhere (probably at the right of the time line right now) where I could unmute users with a single click without having to remember who I have muted (therefore having to look for them again, sometimes with the need of writing down the username first) can be useful. Examples: - You may want to mute some journalists commenting a match I don't care - You may want to mute certain people/TvChannels/etc during your work hours I say it's similar to follow/unfollow because I think it would add a third state in the relationship between two users, and thus probably change part of the API: - Not Following - Following - - Muted (which can only happen if following) The functionality can be done using the current API with an external application I guess (I haven't gone deep into the API), but we obtain to lists from the user: following and followers, and thus we don't know which users are actually muted. That is, we must store this information in an external place and that might not always be possible/ desired. May be when viewing someone's timeline it could be distinguish those tweets that happened while you had the user muted (so you know what you don't remember having read that :) Any comments? Do you think that this feature deserves a place in the API? -- 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
