Re: [twitter-dev] Re: When will delete list members and delete list be fixed?
You are not alone. There are some open issues like http://code.google.com/p/twitter-api/issues/detail?id=1274 that make the retweet functionality unusable as well. Twitter always claims that it uses the same api for its web interface as well which is not true. On Mon, Jan 18, 2010 at 10:11 PM, Orian Marx (@orian) or...@orianmarx.comwrote: Dear Team Twitter, I don't mean to be rude about this, but how can we expect that Twitter will role out an all new developer support center that's going to be more responsive when inquiries about a major defect in the API are left hanging for months on end? There is an open issue that is making list functionality completely unusable for a lot of people and has received zero comment from Twitter staff: http://code.google.com/p/twitter-api/issues/detail?id=1239 On Jan 11, 12:22 pm, Orian Marx (@orian) or...@orianmarx.com wrote: There has been an accepted defect in the issue tracker which really should be a high priority and there has been no word of any status on a fix. The defect is that any developers who cannot use a DELETE request were supposed to be able to make a POST request with a _method=DELETE param, but that has never actually worked. This leaves list management functionality *complete broken* for any client that cannot issue a DELETE request. This was first noted in November, and the defect was accepted one month ago: http://code.google.com/p/twitter-api/issues/detail?id=1239
[twitter-dev] Net::Twitter::Stream - Sudden JSON issues
About 4 hours ago, I started getting bizarre JSON errors from Net::Twitter::Stream - Does anyone know if there has been a change at the stream end?
[twitter-dev] temporarily overloaded 503 Service Unavailable
Noticing quite a few ' temporarily overloaded 503 Service Unavailable messages when trying to log in lately. I assume Twitter is aware of and trying to correct this, but in the meantime, when building applications, are there any guidelines or best practices to follow when your application is presented with a 503 status? SImple tell the user 'the service is unavailable, please try again later'? Or perhaps a more detailed message, explaining why the service is unavailable?
[twitter-dev] favourites_count on user profile is not updated !
Hi, Twitter team! I'm @ono_matope I made a fav-crawler that fetches favourite-feeds only when favourite_count of the user profile information (whitch is retrieved by or list members API) get increased. This mechanism will lat me crawl your data in less resouces. But I've noticed that the user's favourites_count attribute that retrieved by user/show or some other API does NOT to be updated even though he created a new favourite. Through some experiments, I found out following specifics. 1. When user created new favorites, his user info does NOT update. 2. That will be updated only when he tweets, follows someone or do some other activities but creates favourites. ...My new crawler development has been stuck : ( I would like to request that favourite_count attribute to be updated without any other activities, please. Thank you. @ono_matope
Re: [twitter-dev] temporarily overloaded 503 Service Unavailable
I don't think they user cares why Twitter is overloaded, so simply telling them that its overloaded should be enough. Ryan Sent from my DROID On Jan 20, 2010 7:13 AM, eco_bach bac...@gmail.com wrote: Noticing quite a few ' temporarily overloaded 503 Service Unavailable messages when trying to log in lately. I assume Twitter is aware of and trying to correct this, but in the meantime, when building applications, are there any guidelines or best practices to follow when your application is presented with a 503 status? SImple tell the user 'the service is unavailable, please try again later'? Or perhaps a more detailed message, explaining why the service is unavailable?
[twitter-dev] thank you
Thank you, Twitter team, for updating the status blog relatively promptly this morning. That's a welcome change. ∞ 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
[twitter-dev] Is There any way of getting pending request users list.
Is There any method of getting pending request users list, like getting blocked users list. Regards, jahir
[twitter-dev] Getting Pending Request list
I have followed one user. but this user account had protected. So i am sending the request to that user. Is There any method of getting pending request users list, like getting blocked users list. Regards, Jahir
Re: [twitter-dev] Re: Any iPhone Twitter apps with OAuth login ?
and can we contrib/help? On Tue, Jan 19, 2010 at 11:07 AM, joepwro joep...@gmail.com wrote: We are also developing an iPhone app that uses Twitter's OAuth. Posting this just to add more momentum to the request that the Twitter OAuth login page should be made mobile friendly. I believe doing so would have a significant usability impact. Raffi, can you provide input is this thread if this is something Twitter is considering doing in the short term? Long term? Thanks, Joe On Jan 17, 3:12 am, jeff.enderw...@gmail.com jeff.enderw...@gmail.com wrote: Hi, we're releasing an app that has a twitter-based sharing component in a couple of weeks. Does Twitter have any interest in making a mobile friendly version of theoauthallow/deny/pin pages? Could one of us on the outside just gin it up and give it to Twitter? On Jan 12, 7:15 am, funkatron funkat...@gmail.com wrote: Just FWIW, this isn't really aniPhone-specific issue – there are a lot of rich mobile devices out there. One reason (excuse?) for not usingOAuthin Spaz on webOS is the poor functionality on mobile. I'm really reluctant to move toOAuthuntil the flow for mobile is improved. The data from heypic.me is just what I was afraid of. -- Ed Finklerhttp://funkatron.com Twitter:@funkatron AIM: funka7ron ICQ: 3922133 XMPP:funkat...@gmail.com xmpp%3afunkat...@gmail.com On Dec 6 2009, 3:08 am, Ram group...@cascadesoft.net wrote: As a followup to the mobileOAuthdiscussions from October (seehttp:// groups.google.com/group/twitter-development-talk/browse_thread...) Does anyone know of any (publicly released)iPhoneor other mobile Twitter apps that useOAuth? I'm partly curious to know/confirm whether our app is the onlyiPhone (or mobile) app that uses TwitterOAuthlogin for posting tweets, but I also want to know what you think of the UI, if you've used TwitterOAuthlogin in any publicly released mobile app. Thanks Ram
[twitter-dev] Getting Replies to A Message
Hello,
Questions regarding how to get replies to a tweet
What is the recommended way to do this properly?
A few things I have tried
{I am aware that there is no current way to use the search API and
grab all responses to a tweet (i.e by reply_to_status_id) [bummer].}
1. The search API using a to:someUsersince_id=
[theIdOfTweetIAmWatching]: this does not work since I have no
reply_to_status_id in the results to match up with.
2. API -- home_timeline: Requires the credentials for the user who
created the tweet [Which I may or may not have]
3. API -- user_timeline with the user_id from the tweet I am
watching: this does not include the tweets to the user
4. Cheat and have twitter to the work
http://search.twitter.com/search/thread/[theIdOfTweetIAmWatching] :
does not seem to support JSON or anything other than HTML or ATOM
5. Searched the list :)
I am just trying to get a handle on how to take a tweet that I get in
via a stream and go look [poll] for replies.
It seems I would need to follow the user using the streaming API and
match based on the in_reply_to_status_id but that would get quite out
of hand due to incoming tweet volume [i.e would need to follow a large
amount of users that may or may not ever produce a valid reply].
Thanks in advance,
Rob
Re: [twitter-dev] Re: search api results down by a factor of ten since Jan 15, 2010
So, any news on the matter. This probably means that the number of search results has deliberately been reduced to give people an incentive to move to the streaming api's? -M -- Dr. Mikio Braun, Beckerstr. 11, 12157 Berlin Privat: 030 / 42 10 56 42, Büro: 030 / 314 78627, Handy: 0172 / 97 45 676
[twitter-dev] Beginner question : How to get the user ID after authorize OAuth step?
Hi, I'm trying to implement a browser app and Im just blocking at the first step... After the user granted the access to his data (OAuth authorize step), I want to get the user's profile (users/show) but I don't know how to recover the user's id or screen_name... Sorry if I missed something in the API documentation but I really searched... ...And thank you in advance! :) Pitt
Re: [twitter-dev] thank you
agreed. On 20 Jan 2010, at 12:25, Andrew Badera wrote: Thank you, Twitter team, for updating the status blog relatively promptly this morning. That's a welcome change. ∞ 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 smime.p7s Description: S/MIME cryptographic signature
[twitter-dev] Possibility to link to the user page not by the name but by the id.
Hi. I tried to find the similar question here (in google groups), in the FAQ and in the API, but couldn't find anything. The problem: Cross-posting the links to the user page and to some his statuses in the web become more and more popular. But, as i understood, you can't guarantee that this links not long after would not change the logical destination. For example I create some post about some twitter-user aaa and give the link twitter.com/aaa After that user “aaa” changed name to bbb and user ddd changed name to aaa. So my old link now points to the different person. This problem becomes more serious for the aggregators that don't know what content they might approve after a while. The simplest decision would be providing the possibility to link to the user not by name but also by id. That pages might be just redirections to the original user pages, it doesn't matter. For example if the user “aaa” have id 11, the following two links should point to the same page: twitter.com/aaa and twitter.com/id/11 This mechanism should also be applied for the statuses: twitter.com/id/11/statuses/22 Ivan.
Re: [twitter-dev] Beginner question : How to get the user ID after authorize OAuth step?
The screen_name is returned in the querystring along with the oauth_token and the oauth_token_secret values. Ryan On Wed, Jan 20, 2010 at 6:26 AM, Pitt pierre.mar...@gmail.com wrote: Hi, I'm trying to implement a browser app and Im just blocking at the first step... After the user granted the access to his data (OAuth authorize step), I want to get the user's profile (users/show) but I don't know how to recover the user's id or screen_name... Sorry if I missed something in the API documentation but I really searched... ...And thank you in advance! :) Pitt
Re: [twitter-dev] Re: search api results down by a factor of ten since Jan 15, 2010
Search results are altered to improve result quality. The Streaming API exists as a full-fidelity alternative for large-scale integrations. -John Kalucki http://twitter.com/jkalucki Infrastructure, Twitter Inc. On Wed, Jan 20, 2010 at 3:20 AM, Mikio Braun mikiobr...@googlemail.comwrote: So, any news on the matter. This probably means that the number of search results has deliberately been reduced to give people an incentive to move to the streaming api's? -M -- Dr. Mikio Braun, Beckerstr. 11, 12157 Berlin Privat: 030 / 42 10 56 42, Büro: 030 / 314 78627, Handy: 0172 / 97 45 676
Re: [twitter-dev] Net::Twitter::Stream - Sudden JSON issues
No change that I'm aware of, but we push dozens of changes on most business days, many of which could change the format of a message. If this client doesn't use a full JSON parser, but instead tries to pick things apart with Regexp, problems will result. If you are having connection problems, ensure that you aren't getting rate limited and that you haven't been black-listed. -John Kalucki http://twitter.com/jkalucki Infrastructure, Twitter Inc. On Wed, Jan 20, 2010 at 2:26 AM, Nigel Cannings nigelcanni...@googlemail.com wrote: About 4 hours ago, I started getting bizarre JSON errors from Net::Twitter::Stream - Does anyone know if there has been a change at the stream end?
[twitter-dev] Obtaining access token WITHOUT using a PIN
Hi According to the offcial OAuth spec, in order to obtain an access token, the consumer request MUST contain the following parameters 1 oauth_consumer_key:The Consumer Key. 2 oauth_token:The Request Token obtained previously. 3 oauth_signature_method: The signature method the Consumer used to sign the request. 4 oauth_signature: The signature as defined in Signing Requests (Signing Requests). 5 oauth_timestamp: As defined in Nonce and Timestamp (Nonce and Timestamp). 6 oauth_nonce: As defined in Nonce and Timestamp (Nonce and Timestamp). I'm developing a web application in Flash and hence, NOT using the extra pin handshake. (at least I've been told it wasn't necessary, my Application Type is defined as 'Browser'). So far, I've been unsuccessful, 'verified'= false in my access token request handler. Can someone cofirm for me that I in fact don't need the PIN, and if so, do I need to explicitly define all six parametres above in my request? Thanks for any feedback!
Re: [twitter-dev] Obtaining access token WITHOUT using a PIN
You DO NOT need the PIN for a browser app. It is ONLY REQUIRED for desktop apps. 1. oauth_consumer_key = Consumer key given to you by Twitter 2. oauth_token = The token 3. oauth_signature_method = HMAC-SHA1 4. oauth_signature = computed HMAC-SHA1 hash value of the other parameters 5. oauth_timestamp = the number of seconds since Jan 1 1970 6. oauth_nonce = a unique value. I would suggest using a GUID. For the signature, here is an example of what needs to be hashed: this is a GET request to rate_limit_status GEThttp%3A%2F%2Ftwitter.com%2Faccount%2Frate_limit_status.xmloauth_consumer_key%3DYourConsumerKey%26oauth_nonce%3D0f419e62-8680-468f-a647-0532706af529%26oauth_signature_method%3DHMAC-SHA1%26oauth_timestamp%3D126354%26oauth_token%3D36116361-8YRR4w9rRwz7HOc0nYTMmNWjCDrQdFYtnPwsiP7jm%26oauth_version%3D1.0 You would take this value and hash it. The KEY to the hash would be yourConsumerSecrettokenSecret, and tokenSecret is allowed to be blank for the cases where you don't have the secret. Even though the documentation says the oauth_version is optional, I include it anyway. Ryan On Wed, Jan 20, 2010 at 9:59 AM, eco_bach bac...@gmail.com wrote: Hi According to the offcial OAuth spec, in order to obtain an access token, the consumer request MUST contain the following parameters 1 oauth_consumer_key:The Consumer Key. 2 oauth_token:The Request Token obtained previously. 3 oauth_signature_method: The signature method the Consumer used to sign the request. 4 oauth_signature: The signature as defined in Signing Requests (Signing Requests). 5 oauth_timestamp: As defined in Nonce and Timestamp (Nonce and Timestamp). 6 oauth_nonce: As defined in Nonce and Timestamp (Nonce and Timestamp). I'm developing a web application in Flash and hence, NOT using the extra pin handshake. (at least I've been told it wasn't necessary, my Application Type is defined as 'Browser'). So far, I've been unsuccessful, 'verified'= false in my access token request handler. Can someone cofirm for me that I in fact don't need the PIN, and if so, do I need to explicitly define all six parametres above in my request? Thanks for any feedback!
[twitter-dev] Streaming ENGLISH Tweets
I have a Stream Sample and Stream Filter that I need to pull only English Tweets. How should I do this?
[twitter-dev] Please update doc examples to point to api.twitter.com/1
Hello to my Twitter overlords, Since you'd like developers to use api.twitter.com/1 instead of just twitter.com, it would behoove you to udpate the examples in the docs on apiwiki.twitter.com. Copy n paste is probably causing people to use plain ol' twitter.com unknowingly. For example I knew about api.twitter.com/1 but even so I almost unwittingly used twitter.com when I started using an API I hadn't used yet (friendships/create) because the example has twitter.com. Thought I'd try out a new word on you. I used behoove in a sentence. Brian Morearty
[twitter-dev] please help - sporadic '403 Forbidden:' error message when using OAuth Sign-In process
Building an actionscript Twitter client and using OAuth for the sign in process. Having an extrememely frustrating issue with a sporadic error message. '403 Forbidden: The server understood the request, but is refusing to fulfill it.' I'm using, of necessity, a php proxy to get to the Twitter oauth authenticate page at twitter.com/oauth/authenticate/ I get here no problem so I'm assuming there's nothing wrong with my proxy script. However, immediately AFTER clicking 'Sign In' I sometimes get the error message. Also, when I am getting the message, I can even leave the username and password fields blank and click 'Sign In'. I still get the error message, instead of a correct message indicating that the username- password fields are missing. Because this error only seems to happen sporadically, without me having changed anything in my code, it makes it difficult to troubleshoot properly. Anyone else experience this?
Re: [twitter-dev] please help - sporadic '403 Forbidden:' error message when using OAuth Sign-In process
Isn't this the same problem that you posted about yesterday? http://groups.google.com/group/twitter-development-talk/browse_thread/thread/90cb64e3706e1337# http://groups.google.com/group/twitter-development-talk/browse_thread/thread/90cb64e3706e1337#Why create a new post? Ryan On Wed, Jan 20, 2010 at 10:29 AM, eco_bach bac...@gmail.com wrote: Building an actionscript Twitter client and using OAuth for the sign in process. Having an extrememely frustrating issue with a sporadic error message. '403 Forbidden: The server understood the request, but is refusing to fulfill it.' I'm using, of necessity, a php proxy to get to the Twitter oauth authenticate page at twitter.com/oauth/authenticate/ I get here no problem so I'm assuming there's nothing wrong with my proxy script. However, immediately AFTER clicking 'Sign In' I sometimes get the error message. Also, when I am getting the message, I can even leave the username and password fields blank and click 'Sign In'. I still get the error message, instead of a correct message indicating that the username- password fields are missing. Because this error only seems to happen sporadically, without me having changed anything in my code, it makes it difficult to troubleshoot properly. Anyone else experience this?
[twitter-dev] Re: Getting Replies to A Message
You should add your thoughts to
http://code.google.com/p/twitter-api/issues/detail?id=142
This would be a hugely beneficial addition to the API but of course
it's being completely ignored.
On Jan 20, 4:41 am, rob robert.bag...@gmail.com wrote:
Hello,
Questions regarding how to get replies to a tweet
What is the recommended way to do this properly?
A few things I have tried
{I am aware that there is no current way to use the search API and
grab all responses to a tweet (i.e by reply_to_status_id) [bummer].}
1. The search API using a to:someUsersince_id=
[theIdOfTweetIAmWatching]: this does not work since I have no
reply_to_status_id in the results to match up with.
2. API -- home_timeline: Requires the credentials for the user who
created the tweet [Which I may or may not have]
3. API -- user_timeline with the user_id from the tweet I am
watching: this does not include the tweets to the user
4. Cheat and have twitter to the
workhttp://search.twitter.com/search/thread/[theIdOfTweetIAmWatching] :
does not seem to support JSON or anything other than HTML or ATOM
5. Searched the list :)
I am just trying to get a handle on how to take a tweet that I get in
via a stream and go look [poll] for replies.
It seems I would need to follow the user using the streaming API and
match based on the in_reply_to_status_id but that would get quite out
of hand due to incoming tweet volume [i.e would need to follow a large
amount of users that may or may not ever produce a valid reply].
Thanks in advance,
Rob
[twitter-dev] Re: please help - sporadic '403 Forbidden:' error message when using OAuth Sign-In process
Hi Ryan yeah but didn't get any response so thought my question was not clear enough and required more detailed information, hence the new post. Will make an effort to be more parsimonious moving forward... Actually in testing in Firefox I additionally get a 'Service Temporarily Unavailable' 503 as well as the 403 Forbidden error, so I'm wondering if this is in fact a server issue...
[twitter-dev] List counts
User objects should have counts added to them for number of lists owned by, followed by and following the user. This does not seem to exist anywhere in the API currently, though clearly Twitter.com has access to the information (notice the counts at http://twitter.com/username/lists). Is this on the roadmap? No response from Twitter at either http://code.google.com/p/twitter-api/issues/detail?id=1176 or http://code.google.com/p/twitter-api/issues/detail?id=1186 (posted two months ago and which should probably be merged).
[twitter-dev] Need Help on posting Message
Hello Frenz,
I'm building an application in C#.Net 3.5. My Requirement is to post
message to twitter user, defined by me in text box, on button click
i'm passing my credentials and user name with message but i' m getting
following error:-
the remote server returned an error 403 forbidden
My Code is Below:-
try
{
HttpWebRequest messageRequest = (HttpWebRequest)
WebRequest.Create(http://twitter.com/direct_messages/new.xml?user=; +
sendTo + text= + message);
messageRequest.Method = POST;
messageRequest.Credentials = new NetworkCredential
(username, password);
messageRequest.ContentLength = 0;
messageRequest.ContentType = application/x-www-form-
urlencoded;
WebResponse response = messageRequest.GetResponse();
}
catch(Exception ex)
{
MessageBox.Show(ex.Message);
}
any Help is Appreciated,
Re: [twitter-dev] Re: search api results down by a factor of ten since Jan 15, 2010
Dear John, thanks for the reply. We've already started to look into the migration to the streaming API. Looks very nice so far! -M On Wed, Jan 20, 2010 at 3:41 PM, John Kalucki j...@twitter.com wrote: Search results are altered to improve result quality. The Streaming API exists as a full-fidelity alternative for large-scale integrations. -John Kalucki http://twitter.com/jkalucki Infrastructure, Twitter Inc. -- Dr. Mikio Braun, Beckerstr. 11, 12157 Berlin Privat: 030 / 42 10 56 42, Büro: 030 / 314 78627, Handy: 0172 / 97 45 676
Re: [twitter-dev] Beginner question : How to get the user ID after authorize OAuth step?
Pitt, Oauth token will contain the userid, else you can use also use account verify_credentials from your client library to get the details of the user. API Url: http://apiwiki.twitter.com/Twitter-REST-API-Method%3A-account%C2%A0verify_credentials Lalit http://www.twitsfb.com - Twitter Facebook Integration http://www.ezinearticles.biz - Article Submission Directory On Wed, Jan 20, 2010 at 6:26 AM, Pitt pierre.mar...@gmail.com wrote: Hi, I'm trying to implement a browser app and Im just blocking at the first step... After the user granted the access to his data (OAuth authorize step), I want to get the user's profile (users/show) but I don't know how to recover the user's id or screen_name... Sorry if I missed something in the API documentation but I really searched... ...And thank you in advance! :) Pitt
Re: [twitter-dev] Need Help on posting Message
You need to add this
messageRequest.ServicePoint.Expect100Continue = false;
so your code should look like this...
http://codepaste.net/ababkc
Ryan
On Wed, Jan 20, 2010 at 10:22 AM, Atul atul101...@gmail.com wrote:
Hello Frenz,
I'm building an application in C#.Net 3.5. My Requirement is to post
message to twitter user, defined by me in text box, on button click
i'm passing my credentials and user name with message but i' m getting
following error:-
the remote server returned an error 403 forbidden
My Code is Below:-
try
{
HttpWebRequest messageRequest = (HttpWebRequest)
WebRequest.Create(http://twitter.com/direct_messages/new.xml?user=; +
sendTo + text= + message);
messageRequest.Method = POST;
messageRequest.Credentials = new NetworkCredential
(username, password);
messageRequest.ContentLength = 0;
messageRequest.ContentType = application/x-www-form-
urlencoded;
WebResponse response = messageRequest.GetResponse();
}
catch(Exception ex)
{
MessageBox.Show(ex.Message);
}
any Help is Appreciated,
[twitter-dev] Re: please help - sporadic '403 Forbidden:' error message when using OAuth Sign-In process
also think it may have something to do with the HTTP_REFERER header not being explicitly defined in my simple php proxy $url = $_GET['path']; readfile($path); Unfortunately not a php guru so will need more detective work.. Once I resolve will suggest adding to the wiki to benefit other developers...
Re: [twitter-dev] Beginner question : How to get the user ID after authorize OAuth step?
On 1/20/2010 4:26 AM, Pitt wrote: Hi, I'm trying to implement a browser app and Im just blocking at the first step... After the user granted the access to his data (OAuth authorize step), I want to get the user's profile (users/show) but I don't know how to recover the user's id or screen_name... Sorry if I missed something in the API documentation but I really searched... ...And thank you in advance! :) Pitt http://apiwiki.twitter.com/Twitter-REST-API-Method%3A-account%C2%A0verify_credentials
Re: [twitter-dev] Streaming ENGLISH Tweets
For now, you should do the language detection on your end. You can use the user reported language as an initial filter, but it isn't all that useful until nearly all languages are available -- a lot of non-English speakers are still in the English bucket. -John Kalucki http://twitter.com/jkalucki Infrastructure, Twitter Inc. On Wed, Jan 20, 2010 at 7:26 AM, Mark Mason idtw...@gmail.com wrote: I have a Stream Sample and Stream Filter that I need to pull only English Tweets. How should I do this?
[twitter-dev] Re: cannot edit registered application
Hello Abraham, Thanks for your reply.I tried that and it is not working, but there another problem even more annoying - I tried to create new application and I am getting Unable to register this application. Check your registration settings. It does not say if the captcha is wrong or if by chance the callback url is not valid ori do not know... It just pull out this message out of nowhere without obvious reason. I am a bit worried about this since I am trying to migrate my mobile twitter site to OAuth , but I cannot event start doing it. Any help is appreciated. On Jan 20, 2:11 am, Abraham Williams 4bra...@gmail.com wrote: I've been getting some fail whales while viewing my application pages but not when editing them. Tryhttp://twitter.com/oauth_clients/edit/27instead ofhttp://twitter.com/oauth_clients/details/27 Abraham On Tue, Jan 19, 2010 at 09:32, twittme_mobi nlupa...@googlemail.com wrote: Hello, every time i try to edit my application settings , i would get Unable to register this application. Check your registration settings. Isn't it supposed to point me to the exact value that might be wrong.If i new what is it i wouldn't put wrong value in the first place. Is this page working at all.I really think that this basic auth deprecation in june is a very bad idea -- Abraham Williams | Moved to Seattle | May cause email delays Project | Intersect |http://intersect.labs.poseurtech.com Hacker |http://abrah.am|http://twitter.com/abraham This email is: [ ] shareable [x] ask first [ ] private. Sent from Seattle, WA, United States
Re: [twitter-dev] favourites_count on user profile is not updated !
Ono, I think it's been this way for 8+ months? Tim. On Thu, Jan 21, 2010 at 1:14 AM, ono_matope matope@gmail.com wrote: Hi, Twitter team! I'm @ono_matope I made a fav-crawler that fetches favourite-feeds only when favourite_count of the user profile information (whitch is retrieved by or list members API) get increased. This mechanism will lat me crawl your data in less resouces. But I've noticed that the user's favourites_count attribute that retrieved by user/show or some other API does NOT to be updated even though he created a new favourite. Through some experiments, I found out following specifics. 1. When user created new favorites, his user info does NOT update. 2. That will be updated only when he tweets, follows someone or do some other activities but creates favourites. ...My new crawler development has been stuck : ( I would like to request that favourite_count attribute to be updated without any other activities, please. Thank you. @ono_matope
[twitter-dev] Re: cannot edit registered application
This may be an issue with your account. Please write to a...@twitter.com from the email address associated with your Twitter account and we can look into it. Thanks, Brian On Jan 20, 10:25 am, twittme_mobi nlupa...@googlemail.com wrote: Hello Abraham, Thanks for your reply.I tried that and it is not working, but there another problem even more annoying - I tried to create new application and I am getting Unable to register this application. Check your registration settings. It does not say if the captcha is wrong or if by chance the callback url is not valid ori do not know... It just pull out this message out of nowhere without obvious reason. I am a bit worried about this since I am trying to migrate my mobile twitter site to OAuth , but I cannot event start doing it. Any help is appreciated. On Jan 20, 2:11 am, Abraham Williams 4bra...@gmail.com wrote: I've been getting some fail whales while viewing my application pages but not when editing them. Tryhttp://twitter.com/oauth_clients/edit/27insteadofhttp://twitter.com/oauth_clients/details/27 Abraham On Tue, Jan 19, 2010 at 09:32, twittme_mobi nlupa...@googlemail.com wrote: Hello, every time i try to edit my application settings , i would get Unable to register this application. Check your registration settings. Isn't it supposed to point me to the exact value that might be wrong.If i new what is it i wouldn't put wrong value in the first place. Is this page working at all.I really think that this basic auth deprecation in june is a very bad idea -- Abraham Williams | Moved to Seattle | May cause email delays Project | Intersect |http://intersect.labs.poseurtech.com Hacker |http://abrah.am|http://twitter.com/abraham This email is: [ ] shareable [x] ask first [ ] private. Sent from Seattle, WA, United States
[twitter-dev] Re: twitter whitelisting
Hi Cube, I don't see any whitelist requests under your email address. What was the Twitter account you were logged into when you submitted it? Brian On Jan 19, 8:36 am, Cube Whidden lxx.septuag...@gmail.com wrote: Hi, I have submitted a request to be whitelisted by twitter almost two weeks ago. I googled around and found that it normally takes 1 week in the past. Does anyone know the average time it takes to get whitelisted these days? Also, if you get rejected, will I get an email with the reason so that I can correct what is lacking? thanks, Cube Whidden
[twitter-dev] Re: favourites_count on user profile is not updated !
Has this been logged in the issue tracker? Seems like something that should be fixed. On Jan 20, 2:38 pm, Tim Haines tmhai...@gmail.com wrote: Ono, I think it's been this way for 8+ months? Tim. On Thu, Jan 21, 2010 at 1:14 AM, ono_matope matope@gmail.com wrote: Hi, Twitter team! I'm @ono_matope I made a fav-crawler that fetches favourite-feeds only when favourite_count of the user profile information (whitch is retrieved by or list members API) get increased. This mechanism will lat me crawl your data in less resouces. But I've noticed that the user's favourites_count attribute that retrieved by user/show or some other API does NOT to be updated even though he created a new favourite. Through some experiments, I found out following specifics. 1. When user created new favorites, his user info does NOT update. 2. That will be updated only when he tweets, follows someone or do some other activities but creates favourites. ...My new crawler development has been stuck : ( I would like to request that favourite_count attribute to be updated without any other activities, please. Thank you. @ono_matope
[twitter-dev] API Limit of 150 is Obsolete
I will come straight to the point: we need to an increase to the API limit to properly implement Twitter within a desktop client application given the addition of: 1) three retweets timelines; 2) checking the account's saved searches; and 3) up to 10-20 Twitter Lists timelines. Twitter Lists alone are causing real problems if a user follows more than 5 or so. We cant poll Twitter List subscriptions with one API call that combines them altogether, which we could then split apart client-side with some attached meta-data. That alone would have been a big help, and without it we are left polling each List as if it was a separate timeline, since that is what they are. Implementing proper Lists management is a non-starter within this limit, so is regular confirmation of a relationship between two users when asked for by the user (on Lists or search results). There is simply a lot of stuff I cannot do properly that is standard on twitter.com, all because I am subject to the API limit while twitter.com is not. Users simply do not understand this distinction in possibilities. I would like to formally ask on behalf of all client developers that the API limit increase to 250, from 150, for all applications whether they use OAuth or HTTP Basic Authentication. We are simply not able to implement Twitter properly within a limit of 150, but dont need a lot more, only another 100-200 API calls or so. If Twitter can even technically contemplate a 10x API limit increase to 1,500 for OAuth applications, surely an increase to 250 based on the addition of core features like official retweets and Lists is a reasonable request. A limit of 150 is simply obsolete, and has been for a long time. I do not want to wait for the UX repairs around OAuth for desktop applications, and I dont like being forced into OAuth sooner than we are ready just because we need the extra API hits just to do basic features properly. And besides, that was announced as two weeks away three weeks ago. I dont want to wait any longer. I want to properly implement the basics, like Lists polling, now. This is a considered email because I care about the quality of our Twitter implementation and I care about the Twitter ecosystem. I would appreciate a considered reply. --ejw Eric Woodward Email: e...@nambu.com
Re: [twitter-dev] API Limit of 150 is Obsolete
Yeah an increase in API requests would be nice to have with the addition of new API features. I would almost like a solution where twitter sets a guaranteed hits/hour soft limit. By soft limit I mean if you go above this limit you may be rate limited if the twitter cluster is currently under heavy load or you are being too rough with the API. If the cluster has unused capacity, why start limiting users? For non-whitelisted applications a guarantee of 250 would be nice. Whiltelisted apps would get a higher guaranteed limit still to meet their demands. I'm sure twitter has floated this idea around. Not sure how big of a technical hurdle it would be to implement. Just my two cents on the subject of API rate limits. Josh On Wed, Jan 20, 2010 at 4:48 PM, Eric Woodward e...@nambu.com wrote: I will come straight to the point: we need to an increase to the API limit to properly implement Twitter within a desktop client application given the addition of: 1) three retweets timelines; 2) checking the account's saved searches; and 3) up to 10-20 Twitter Lists timelines. Twitter Lists alone are causing real problems if a user follows more than 5 or so. We cant poll Twitter List subscriptions with one API call that combines them altogether, which we could then split apart client-side with some attached meta-data. That alone would have been a big help, and without it we are left polling each List as if it was a separate timeline, since that is what they are. Implementing proper Lists management is a non-starter within this limit, so is regular confirmation of a relationship between two users when asked for by the user (on Lists or search results). There is simply a lot of stuff I cannot do properly that is standard on twitter.com, all because I am subject to the API limit while twitter.com is not. Users simply do not understand this distinction in possibilities. I would like to formally ask on behalf of all client developers that the API limit increase to 250, from 150, for all applications whether they use OAuth or HTTP Basic Authentication. We are simply not able to implement Twitter properly within a limit of 150, but dont need a lot more, only another 100-200 API calls or so. If Twitter can even technically contemplate a 10x API limit increase to 1,500 for OAuth applications, surely an increase to 250 based on the addition of core features like official retweets and Lists is a reasonable request. A limit of 150 is simply obsolete, and has been for a long time. I do not want to wait for the UX repairs around OAuth for desktop applications, and I dont like being forced into OAuth sooner than we are ready just because we need the extra API hits just to do basic features properly. And besides, that was announced as two weeks away three weeks ago. I dont want to wait any longer. I want to properly implement the basics, like Lists polling, now. This is a considered email because I care about the quality of our Twitter implementation and I care about the Twitter ecosystem. I would appreciate a considered reply. --ejw Eric Woodward Email: e...@nambu.com
[twitter-dev] CrisisCommons.org Project Involving Twitter and Haiti
There is a project called Tweak-the-Tweet that has grown out of the CrisisCommons.org response to the earthquake in Haiti. It's a fascinating project, which you can read about here. http://epic.cs.colorado.edu/helping_haiti_tweak_the_twe.html There will be a conference call at 9 PM Pacific time tonight (midnight Eastern - haven't translated to UTC yet) to discuss all Twitter- related projects in this effort. I'll post the details as soon as I get them, and I've invited the organizers of the project to join us here. I'm planning to be at the Portland, Oregon CrisisCamp this weekend http://crisiscamphaitipdx.eventbrite.com/ and would love to see fellow PDX Twitter folks help out if they can. -- M. Edward (Ed) Borasky http://borasky-research.net/smart-at-znmeb I've never met a happy clam. In fact, most of them were pretty steamed.
[twitter-dev] Re: API Limit of 150 is Obsolete
I've discovered that the API rate limit is 450 per hour for pages/ cursors within a followers_ids or friends_ids call, if that helps. But I really think that increasing the API rate limit for basic HTML auth is a bad idea - let's make oAuth work! On Jan 20, 3:04 pm, Josh Roesslein jroessl...@gmail.com wrote: Yeah an increase in API requests would be nice to have with the addition of new API features. I would almost like a solution where twitter sets a guaranteed hits/hour soft limit. By soft limit I mean if you go above this limit you may be rate limited if the twitter cluster is currently under heavy load or you are being too rough with the API. If the cluster has unused capacity, why start limiting users? For non-whitelisted applications a guarantee of 250 would be nice. Whiltelisted apps would get a higher guaranteed limit still to meet their demands. I'm sure twitter has floated this idea around. Not sure how big of a technical hurdle it would be to implement. Just my two cents on the subject of API rate limits. Josh On Wed, Jan 20, 2010 at 4:48 PM, Eric Woodward e...@nambu.com wrote: I will come straight to the point: we need to an increase to the API limit to properly implement Twitter within a desktop client application given the addition of: 1) three retweets timelines; 2) checking the account's saved searches; and 3) up to 10-20 Twitter Lists timelines. Twitter Lists alone are causing real problems if a user follows more than 5 or so. We cant poll Twitter List subscriptions with one API call that combines them altogether, which we could then split apart client-side with some attached meta-data. That alone would have been a big help, and without it we are left polling each List as if it was a separate timeline, since that is what they are. Implementing proper Lists management is a non-starter within this limit, so is regular confirmation of a relationship between two users when asked for by the user (on Lists or search results). There is simply a lot of stuff I cannot do properly that is standard on twitter.com, all because I am subject to the API limit while twitter.com is not. Users simply do not understand this distinction in possibilities. I would like to formally ask on behalf of all client developers that the API limit increase to 250, from 150, for all applications whether they use OAuth or HTTP Basic Authentication. We are simply not able to implement Twitter properly within a limit of 150, but dont need a lot more, only another 100-200 API calls or so. If Twitter can even technically contemplate a 10x API limit increase to 1,500 for OAuth applications, surely an increase to 250 based on the addition of core features like official retweets and Lists is a reasonable request. A limit of 150 is simply obsolete, and has been for a long time. I do not want to wait for the UX repairs around OAuth for desktop applications, and I dont like being forced into OAuth sooner than we are ready just because we need the extra API hits just to do basic features properly. And besides, that was announced as two weeks away three weeks ago. I dont want to wait any longer. I want to properly implement the basics, like Lists polling, now. This is a considered email because I care about the quality of our Twitter implementation and I care about the Twitter ecosystem. I would appreciate a considered reply. --ejw Eric Woodward Email: e...@nambu.com
Re: [twitter-dev] Getting Pending Request list
Currently there is no such method. ---Mark http://twitter.com/mccv On Wed, Jan 20, 2010 at 12:35 AM, jahir jagi...@greatinnovus.com wrote: I have followed one user. but this user account had protected. So i am sending the request to that user. Is There any method of getting pending request users list, like getting blocked users list. Regards, Jahir
[twitter-dev] internal lists
is there a way to separate topic of my tweets? let's say i tweet about more then one subject, for example my userid is EXAMPLE and i tweet about SUBJECT1 and SUBJECT2 ultimately i'd want to have following http://twitter.com/EXAMPLE/SUBJECT1 http://twitter.com/EXAMPLE/SUBJECT2 or http://twitter.com/EXAMPLE/lists/SUBJECTx
[twitter-dev] streaming rate limit question
Hi, it seems the max per account to do statuses/filter is 400. Is there a limit to the number of accounts per IP? Can I have 100 accounts using the same ip? thanks Joel
[twitter-dev] twitter and cake/curl- Rate limit exceeded
hi. i am building an api for a project, and a portion implements
twitter. Cakephp is my framework. The problem i am having is despite
my approach, i am getting
{request:\/statuses\/user_timeline.xml?
screen_name=user_screen_name_example,error:Rate limit exceeded.
Clients may not make more than 150 requests per hour.}
However, if i query the twitter api to see how many requests i truly
have left, i am no where near 150. I have in my controller var
$cacheAction = 1800; and i am using the Cache helper so as to limt
the hits on the request...
[[ the approaches]]
The first attempt was to use the Twittersource from the bakery(http://
bakery.cakephp.org/articles/view/twitter-datasource).
The second approach was to curl the results through a custom method.
function _getCurrentTweets($user = NULL)
{
$tw = curl_init();
curl_setopt($tw, CURLOPT_GET, 1);
if (!$user) {
curl_setopt($tw, CURLOPT_URL, $this-Tweet-tweets);//
ie:
http://twitter.com/statuses/friends.xml?my_screen_name=101010
curl_setopt($tw, CURLOPT_USERPWD, $this-Tweet-login);
}else
{
$t_url = $this-Tweet-tweetsWithUser.$user; // ie:
http://twitter.com/statuses/user_timeline.xml?screen_name=$user
curl_setopt($tw, CURLOPT_URL, $t_url);
}
curl_setopt($tw, CURLOPT_RETURNTRANSFER, TRUE);
$twi = curl_exec($tw);
curl_close($tw);
$tweeters = new SimpleXMLElement($twi);
return $tweeters;
}
perhaps there is a bigger picture i am missing? I had thought this was
a caching issue, but now i am not so sure.
[twitter-dev] Re: twitter whitelisting
Oh, it seems like it just went through, but it was under organizedwis...@organizediwsdom.com, under the organizedwisdom twitter name. Thanks so much for helping with this, It was nice to pry my boss out of my butt. Cube On Wed, Jan 20, 2010 at 4:58 PM, Brian Sutorius bsutor...@twitter.comwrote: Hi Cube, I don't see any whitelist requests under your email address. What was the Twitter account you were logged into when you submitted it? Brian On Jan 19, 8:36 am, Cube Whidden lxx.septuag...@gmail.com wrote: Hi, I have submitted a request to be whitelisted by twitter almost two weeks ago. I googled around and found that it normally takes 1 week in the past. Does anyone know the average time it takes to get whitelisted these days? Also, if you get rejected, will I get an email with the reason so that I can correct what is lacking? thanks, Cube Whidden -- μῆνιν ἄειδε θεὰ Πηληϊάδεω Ἀχιλῆος οὐλομένην...
[twitter-dev] Re: API Limit of 150 is Obsolete
On top of all that, AFAIK the 1500 limit for OAuth is still vaporware at this point, so everybody is capped at 150. To inform the discussion, I wonder if Twitter could share any figures like what's the actual API use distribution? Like what combination of users/apps hit the cap regularly and cause massive load? If it was an equal distribution (i.e most users/apps are around the same level) that gives them heavy load, then I would see why they need to be careful about raising limits (any increase would bring more fail whales). But I suspect that it's highly asymmetrical... i.e there are very few users/apps who actually cause any meaningful load. Another hunch: desktop apps are negligible and the real load comes from web apps who spider asynchronously 24/7. Should the load be differentiated across client and web apps? Client apps are typically only one user per device at a time, whereas the web app may be spidering on behalf of who knows how many people. On Jan 20, 5:48 pm, Eric Woodward e...@nambu.com wrote: I will come straight to the point: we need to an increase to the API limit to properly implement Twitter within a desktop client application given the addition of: 1) three retweets timelines; 2) checking the account's saved searches; and 3) up to 10-20 Twitter Lists timelines. Twitter Lists alone are causing real problems if a user follows more than 5 or so. We cant poll Twitter List subscriptions with one API call that combines them altogether, which we could then split apart client-side with some attached meta-data. That alone would have been a big help, and without it we are left polling each List as if it was a separate timeline, since that is what they are. Implementing proper Lists management is a non-starter within this limit, so is regular confirmation of a relationship between two users when asked for by the user (on Lists or search results). There is simply a lot of stuff I cannot do properly that is standard on twitter.com, all because I am subject to the API limit while twitter.com is not. Users simply do not understand this distinction in possibilities. I would like to formally ask on behalf of all client developers that the API limit increase to 250, from 150, for all applications whether they use OAuth or HTTP Basic Authentication. We are simply not able to implement Twitter properly within a limit of 150, but dont need a lot more, only another 100-200 API calls or so. If Twitter can even technically contemplate a 10x API limit increase to 1,500 for OAuth applications, surely an increase to 250 based on the addition of core features like official retweets and Lists is a reasonable request. A limit of 150 is simply obsolete, and has been for a long time. I do not want to wait for the UX repairs around OAuth for desktop applications, and I dont like being forced into OAuth sooner than we are ready just because we need the extra API hits just to do basic features properly. And besides, that was announced as two weeks away three weeks ago. I dont want to wait any longer. I want to properly implement the basics, like Lists polling, now. This is a considered email because I care about the quality of our Twitter implementation and I care about the Twitter ecosystem. I would appreciate a considered reply. --ejw Eric Woodward Email: e...@nambu.com
Re: [twitter-dev] Re: API Limit of 150 is Obsolete
Another hunch: desktop apps are negligible and the real load comes from web apps who spider asynchronously 24/7. Should the load be differentiated across client and web apps? Client apps are typically only one user per device at a time, whereas the web app may be spidering on behalf of who knows how many people. The problem here is distinguishing the two. OAuth doesn't (and I was told this by one of the people on the OAuth committee) specifically allow you to unambiguously and securely identify an application just because it has a certain app key, and Twitter's Basic Auth implementation uses source keys pretty much purely cosmetically. -- personal: http://www.cameronkaiser.com/ -- Cameron Kaiser * Floodgap Systems * www.floodgap.com * ckai...@floodgap.com -- BOND THEME NOW PLAYING: Die Another Day --
Re: [twitter-dev] Re: twitter whitelisting
It was nice to pry my boss out of my butt. Usually it's the other way around, no? ;-) -- personal: http://www.cameronkaiser.com/ -- Cameron Kaiser * Floodgap Systems * www.floodgap.com * ckai...@floodgap.com -- BOND THEME NOW PLAYING: Goldfinger ---
Re: [twitter-dev] streaming rate limit question
Hi, it seems the max per account to do statuses/filter is 400. Is there a limit to the number of accounts per IP? Can I have 100 accounts using the same ip? If they are separately authenticated, I am aware of no limit. -- personal: http://www.cameronkaiser.com/ -- Cameron Kaiser * Floodgap Systems * www.floodgap.com * ckai...@floodgap.com -- I, for one, welcome our new C64 overlords. -- John Floren --
Re: [twitter-dev] streaming rate limit question
If you need more predicates, you must apply for a higher level of access, not open more connections. The default limits are set to allow experimentation while preventing scraping. Excessive connections are considered attempts to work around the rate limits and your IP address will be banned. This is documented and emphasized in the Pre-Launch Checklist: http://apiwiki.twitter.com/Streaming-API-Documentation#PreLaunchChecklist -John Kalucki http://twitter.com/jkalucki Infrastructure, Twitter Inc. On Wed, Jan 20, 2010 at 4:51 PM, Cameron Kaiser spec...@floodgap.com wrote: Hi, it seems the max per account to do statuses/filter is 400. Is there a limit to the number of accounts per IP? Can I have 100 accounts using the same ip? If they are separately authenticated, I am aware of no limit. -- personal: http://www.cameronkaiser.com/ -- Cameron Kaiser * Floodgap Systems * www.floodgap.com * ckai...@floodgap.com -- I, for one, welcome our new C64 overlords. -- John Floren --
Re: [twitter-dev] twitter and cake/curl- Rate limit exceeded
Are you perhaps making authenticated calls to the API but
calling account/rate_limit_status unauthenticated? or vis versa?
Abraham
On Wed, Jan 20, 2010 at 13:55, mlecho saltlessbr...@gmail.com wrote:
hi. i am building an api for a project, and a portion implements
twitter. Cakephp is my framework. The problem i am having is despite
my approach, i am getting
{request:\/statuses\/user_timeline.xml?
screen_name=user_screen_name_example,error:Rate limit exceeded.
Clients may not make more than 150 requests per hour.}
However, if i query the twitter api to see how many requests i truly
have left, i am no where near 150. I have in my controller var
$cacheAction = 1800; and i am using the Cache helper so as to limt
the hits on the request...
[[ the approaches]]
The first attempt was to use the Twittersource from the bakery(http://
bakery.cakephp.org/articles/view/twitter-datasource).
The second approach was to curl the results through a custom method.
function _getCurrentTweets($user = NULL)
{
$tw = curl_init();
curl_setopt($tw, CURLOPT_GET, 1);
if (!$user) {
curl_setopt($tw, CURLOPT_URL,
$this-Tweet-tweets);// ie:
http://twitter.com/statuses/friends.xml?my_screen_name=101010
curl_setopt($tw, CURLOPT_USERPWD,
$this-Tweet-login);
}else
{
$t_url = $this-Tweet-tweetsWithUser.$user; // ie:
http://twitter.com/statuses/user_timeline.xml?screen_name=$user
curl_setopt($tw, CURLOPT_URL, $t_url);
}
curl_setopt($tw, CURLOPT_RETURNTRANSFER, TRUE);
$twi = curl_exec($tw);
curl_close($tw);
$tweeters = new SimpleXMLElement($twi);
return $tweeters;
}
perhaps there is a bigger picture i am missing? I had thought this was
a caching issue, but now i am not so sure.
--
Abraham Williams | Moved to Seattle | May cause email delays
Project | Intersect | http://intersect.labs.poseurtech.com
Hacker | http://abrah.am | http://twitter.com/abraham
This email is: [ ] shareable [x] ask first [ ] private.
Sent from Seattle, WA, United States
Re: [twitter-dev] internal lists
Not really. You could add #hashtags to your statuses and use search to filter the them. https://twitter.com/#search?q=from%3AEXAMPLE%20%23SUBJECT1 https://twitter.com/#search?q=from%3AEXAMPLE%20%23SUBJECT2 You would be searching for from:EXAMPLE #SUBJECT1. Abraham On Wed, Jan 20, 2010 at 09:01, alexus ale...@gmail.com wrote: is there a way to separate topic of my tweets? let's say i tweet about more then one subject, for example my userid is EXAMPLE and i tweet about SUBJECT1 and SUBJECT2 ultimately i'd want to have following http://twitter.com/EXAMPLE/SUBJECT1 http://twitter.com/EXAMPLE/SUBJECT2 or http://twitter.com/EXAMPLE/lists/SUBJECTx -- Abraham Williams | Moved to Seattle | May cause email delays Project | Intersect | http://intersect.labs.poseurtech.com Hacker | http://abrah.am | http://twitter.com/abraham This email is: [ ] shareable [x] ask first [ ] private. Sent from Seattle, WA, United States
Re: [twitter-dev] Re: Getting Replies to A Message
You might also check out http://twitoaster.com/api/conversation-show/
I don't know how large their database is though.
Abraham
On Wed, Jan 20, 2010 at 07:37, Orian Marx (@orian) or...@orianmarx.comwrote:
You should add your thoughts to
http://code.google.com/p/twitter-api/issues/detail?id=142
This would be a hugely beneficial addition to the API but of course
it's being completely ignored.
On Jan 20, 4:41 am, rob robert.bag...@gmail.com wrote:
Hello,
Questions regarding how to get replies to a tweet
What is the recommended way to do this properly?
A few things I have tried
{I am aware that there is no current way to use the search API and
grab all responses to a tweet (i.e by reply_to_status_id) [bummer].}
1. The search API using a to:someUsersince_id=
[theIdOfTweetIAmWatching]: this does not work since I have no
reply_to_status_id in the results to match up with.
2. API -- home_timeline: Requires the credentials for the user who
created the tweet [Which I may or may not have]
3. API -- user_timeline with the user_id from the tweet I am
watching: this does not include the tweets to the user
4. Cheat and have twitter to the work
http://search.twitter.com/search/thread/[theIdOfTweetIAmWatching] :
does not seem to support JSON or anything other than HTML or ATOM
5. Searched the list :)
I am just trying to get a handle on how to take a tweet that I get in
via a stream and go look [poll] for replies.
It seems I would need to follow the user using the streaming API and
match based on the in_reply_to_status_id but that would get quite out
of hand due to incoming tweet volume [i.e would need to follow a large
amount of users that may or may not ever produce a valid reply].
Thanks in advance,
Rob
--
Abraham Williams | Moved to Seattle | May cause email delays
Project | Intersect | http://intersect.labs.poseurtech.com
Hacker | http://abrah.am | http://twitter.com/abraham
This email is: [ ] shareable [x] ask first [ ] private.
Sent from Seattle, WA, United States
[twitter-dev] Re: CrisisCommons.org Project Involving Twitter and Haiti
I have some more information. *Conference Call Number* for CrisisCamp Planning (619) 276-6333 PIN is 411911, 5:00EST European Rondee Bridge (Germany): +49 157-02488180 On Wed, Jan 20, 2010 at 9:10 AM, Jeannie Stamberger jeannie.stamber...@gmail.com wrote: Hi All, Heather wanted to let me know that we are going to have a conference call tonight at 9pmPT/10MT/11CT/12amET, to do a wrap-up and update on all Twitter-related projects. This will use the same conference call information as the 5pm call today. Please forward this on to anyone working on a Twitter-related project. Cheers, Jeannie -- Jeannie A. Stamberger, PhD cell: (650) 380-1158 -- Jeannie A. Stamberger, PhD cell: (650) 380-1158 If you want to help out on this, please join the Google Group http://groups.google.com/group/tweak-the-tweet. There may be another more generic Google Group, but this one is definitely Twitter related. -- M. Edward (Ed) Boraskyhttp://borasky-research.net I've never met a happy clam. In fact, most of them were pretty steamed. On Jan 20, 3:59 pm, M. Edward (Ed) Borasky zzn...@gmail.com wrote: There is a project called Tweak-the-Tweet that has grown out of the CrisisCommons.org response to the earthquake in Haiti. It's a fascinating project, which you can read about here. http://epic.cs.colorado.edu/helping_haiti_tweak_the_twe.html There will be a conference call at 9 PM Pacific time tonight (midnight Eastern - haven't translated to UTC yet) to discuss all Twitter- related projects in this effort. I'll post the details as soon as I get them, and I've invited the organizers of the project to join us here. I'm planning to be at the Portland, Oregon CrisisCamp this weekend http://crisiscamphaitipdx.eventbrite.com/ and would love to see fellow PDX Twitter folks help out if they can. -- M. Edward (Ed) Boraskyhttp://borasky-research.net/smart-at-znmeb I've never met a happy clam. In fact, most of them were pretty steamed.
Re: [twitter-dev] Possibility to link to the user page not by the name but by the id.
I remember this topic coming up before and it seems like someone built an application that handled this but I can't find any references to it. Maybe somebody else can? Abraham On Wed, Jan 20, 2010 at 06:29, Ivan gli.w...@gmail.com wrote: Hi. I tried to find the similar question here (in google groups), in the FAQ and in the API, but couldn't find anything. The problem: Cross-posting the links to the user page and to some his statuses in the web become more and more popular. But, as i understood, you can't guarantee that this links not long after would not change the logical destination. For example I create some post about some twitter-user aaa and give the link twitter.com/aaa After that user “aaa” changed name to bbb and user ddd changed name to aaa. So my old link now points to the different person. This problem becomes more serious for the aggregators that don't know what content they might approve after a while. The simplest decision would be providing the possibility to link to the user not by name but also by id. That pages might be just redirections to the original user pages, it doesn't matter. For example if the user “aaa” have id 11, the following two links should point to the same page: twitter.com/aaa and twitter.com/id/11 This mechanism should also be applied for the statuses: twitter.com/id/11/statuses/22 Ivan. -- Abraham Williams | Moved to Seattle | May cause email delays Project | Intersect | http://intersect.labs.poseurtech.com Hacker | http://abrah.am | http://twitter.com/abraham This email is: [ ] shareable [x] ask first [ ] private. Sent from Seattle, WA, United States
[twitter-dev] Re: API Limit of 150 is Obsolete
On Jan 20, 4:50 pm, Cameron Kaiser spec...@floodgap.com wrote: The problem here is distinguishing the two. OAuth doesn't (and I was told this by one of the people on the OAuth committee) specifically allow you to unambiguously and securely identify an application just because it has a certain app key Huh? Can you translate this into either English or pseudo-code? I fill out a form. The app gets a name, which must be unique. And I choose between a desktop exclusive-or server app (PIN workflow exclusive-or callback workflow) with a radio button. I get a consumer key and consumer secret, also, I'm assuming, unique. So now I run that app. I send packets back and forth between the app / my IP address and Twitter's servers / Twitter's IP addresses. Are you saying Twitter can't distinguish my oAuth app running on my IP address from another oAuth app running on a different IP address? You don't know where I am and what I'm running? You don't know which of 30 users of my app from different machines is acting abusively?
Re: [twitter-dev] CrisisCommons.org Project Involving Twitter and Haiti
Kudos! Here are two similar humanitarian services, which are collaborating with CNN and two of its Anchor(s) http://relief4haiti.com http://relief4haiti.net -E Gpro.ws On Wed, Jan 20, 2010 at 6:59 PM, M. Edward (Ed) Borasky zzn...@gmail.comwrote: There is a project called Tweak-the-Tweet that has grown out of the CrisisCommons.org response to the earthquake in Haiti. It's a fascinating project, which you can read about here. http://epic.cs.colorado.edu/helping_haiti_tweak_the_twe.html There will be a conference call at 9 PM Pacific time tonight (midnight Eastern - haven't translated to UTC yet) to discuss all Twitter- related projects in this effort. I'll post the details as soon as I get them, and I've invited the organizers of the project to join us here. I'm planning to be at the Portland, Oregon CrisisCamp this weekend http://crisiscamphaitipdx.eventbrite.com/ and would love to see fellow PDX Twitter folks help out if they can. -- M. Edward (Ed) Borasky http://borasky-research.net/smart-at-znmeb I've never met a happy clam. In fact, most of them were pretty steamed.
Re: [twitter-dev] Re: API Limit of 150 is Obsolete
Not really that hard to distinguish between 5 IPs making 20k API hits and 20k IPs making 5 API hits each... Abraham On Wed, Jan 20, 2010 at 16:50, Cameron Kaiser spec...@floodgap.com wrote: Another hunch: desktop apps are negligible and the real load comes from web apps who spider asynchronously 24/7. Should the load be differentiated across client and web apps? Client apps are typically only one user per device at a time, whereas the web app may be spidering on behalf of who knows how many people. The problem here is distinguishing the two. OAuth doesn't (and I was told this by one of the people on the OAuth committee) specifically allow you to unambiguously and securely identify an application just because it has a certain app key, and Twitter's Basic Auth implementation uses source keys pretty much purely cosmetically. -- personal: http://www.cameronkaiser.com/ -- Cameron Kaiser * Floodgap Systems * www.floodgap.com * ckai...@floodgap.com -- BOND THEME NOW PLAYING: Die Another Day -- -- Abraham Williams | Moved to Seattle | May cause email delays Project | Intersect | http://intersect.labs.poseurtech.com Hacker | http://abrah.am | http://twitter.com/abraham This email is: [ ] shareable [x] ask first [ ] private. Sent from Seattle, WA, United States
Re: [twitter-dev] Re: API Limit of 150 is Obsolete
Another hunch: desktop apps are negligible and the real load comes from web apps who spider asynchronously 24/7. Should the load be differentiated across client and web apps? Client apps are typically only one user per device at a time, whereas the web app may be spidering on behalf of who knows how many people. The problem here is distinguishing the two. OAuth doesn't (and I was told this by one of the people on the OAuth committee) specifically allow you to unambiguously and securely identify an application just because it has a certain app key, and Twitter's Basic Auth implementation uses source keys pretty much purely cosmetically. Not really that hard to distinguish between 5 IPs making 20k API hits and 20k IPs making 5 API hits each... But it's not a guaranteed one either. Also, it doesn't allow you to distinguish between equally popular services, one which might be kosher and the other not. -- personal: http://www.cameronkaiser.com/ -- Cameron Kaiser * Floodgap Systems * www.floodgap.com * ckai...@floodgap.com -- BOND THEME NOW PLAYING: The James Bond Theme from Dr. No -
Re: [twitter-dev] Twitter visualization tool
Interesting. Well go for it then. On Tue, Jan 19, 2010 at 21:34, Mark McBride mmcbr...@twitter.com wrote: Why would you have to run your own server to use the streaming API from the iPhone? ChirpFlow seems to be doing just fine with iPhone+Streaming ---Mark http://twitter.com/mccv On Tue, Jan 19, 2010 at 5:29 PM, Abraham Williams 4bra...@gmail.comwrote: For an iPhone application Streaming does not make much sense. You would have to run your own server and have your application check for updates from it. Which might make sense depending on your app. You should be able to just display a notice to users if they run into rate limiting. Abraham On Tue, Jan 19, 2010 at 09:35, John Kalucki j...@twitter.com wrote: If you are doing repeated automated searches, you must be on the Streaming API, not the Search API. http://groups.google.com/group/twitter-api-announce/browse_thread/thread/c8c713bb63fac24c -John Kalucki http://twitter.com/jkalucki Infrastructure, Twitter Inc. On Tue, Jan 19, 2010 at 6:11 AM, Carl Knott carl.kn...@gmail.comwrote: Hi, I have written an application for the iPhone that sends a request to the Twitter search API every 2 seconds, I am concerned that this is too frequent. I have looked on the internet and I cant find a definite answer - How many search requests can I make per minute and is limiting imposed on the application or the IP address of the user? Thanks, Carl. -- Abraham Williams | Moved to Seattle | May cause email delays Project | Intersect | http://intersect.labs.poseurtech.com Hacker | http://abrah.am | http://twitter.com/abraham This email is: [ ] shareable [x] ask first [ ] private. Sent from Seattle, WA, United States -- Abraham Williams | Moved to Seattle | May cause email delays Project | Intersect | http://intersect.labs.poseurtech.com Hacker | http://abrah.am | http://twitter.com/abraham This email is: [ ] shareable [x] ask first [ ] private. Sent from Seattle, WA, United States
Re: [twitter-dev] Re: API Limit of 150 is Obsolete
The problem here is distinguishing the two. OAuth doesn't (and I was told this by one of the people on the OAuth committee) specifically allow you to unambiguously and securely identify an application just because it has a certain app key Huh? Can you translate this into either English or pseudo-code? I fill out a form. The app gets a name, which must be unique. And I choose between a desktop exclusive-or server app (PIN workflow exclusive-or callback workflow) with a radio button. I get a consumer key and consumer secret, also, I'm assuming, unique. Didn't we just get done with a thread where people complained, correctly, that a desktop app containing a consumer key/secret can't keep those things secret? -- personal: http://www.cameronkaiser.com/ -- Cameron Kaiser * Floodgap Systems * www.floodgap.com * ckai...@floodgap.com -- Of course, what I really want is total world domination. -- Linus Torvalds -
Re: [twitter-dev] OAuth Authorization login page
http://code.google.com/p/twitter-api/issues/detail?id=1050 On Mon, Jan 18, 2010 at 06:23, Michael J. Ditto di...@progressnowcolorado.org wrote: I think I've seen this mentioned before, but I'll add one vote to getting it fixed... When logging in via a web app, the default action is Deny. So on my iPhone when I put in my username and password and hit Go it denies access. Quite counterintuitive. Cheers, Mike Sent from my iPhone -- Abraham Williams | Moved to Seattle | May cause email delays Project | Intersect | http://intersect.labs.poseurtech.com Hacker | http://abrah.am | http://twitter.com/abraham This email is: [ ] shareable [x] ask first [ ] private. Sent from Seattle, WA, United States
Re: [twitter-dev] Re: Getting Replies to A Message
Thanks for the link Abraham, I had look at them, most of the time their API
from my experience timed out and never responded (e.x.
http://api.twitoaster.com/conversation/show.json?id=7968304579).
Plus from looking at the eery similarities (rate limits, user agent
requirement, returned JSON structs, etc) it looks like a wrapper around the
twitter API (even if I am off base on that assumption they [twitoaster] must
be pulling some of their data from the API [Unless they are riding the
firehose and storing a arseload of data])
That being said, I really don't want to code to two API's for my application
and if they [twitoaster] can get/thread the replies then dang-it my inner
nerd says So can I :)
Thanks,
Rob
On Wed, Jan 20, 2010 at 6:46 PM, Abraham Williams 4bra...@gmail.com wrote:
You might also check out http://twitoaster.com/api/conversation-show/
I don't know how large their database is though.
Abraham
On Wed, Jan 20, 2010 at 07:37, Orian Marx (@orian) or...@orianmarx.comwrote:
You should add your thoughts to
http://code.google.com/p/twitter-api/issues/detail?id=142
This would be a hugely beneficial addition to the API but of course
it's being completely ignored.
On Jan 20, 4:41 am, rob robert.bag...@gmail.com wrote:
Hello,
Questions regarding how to get replies to a tweet
What is the recommended way to do this properly?
A few things I have tried
{I am aware that there is no current way to use the search API and
grab all responses to a tweet (i.e by reply_to_status_id) [bummer].}
1. The search API using a to:someUsersince_id=
[theIdOfTweetIAmWatching]: this does not work since I have no
reply_to_status_id in the results to match up with.
2. API -- home_timeline: Requires the credentials for the user who
created the tweet [Which I may or may not have]
3. API -- user_timeline with the user_id from the tweet I am
watching: this does not include the tweets to the user
4. Cheat and have twitter to the work
http://search.twitter.com/search/thread/[theIdOfTweetIAmWatching]http://search.twitter.com/search/thread/%5BtheIdOfTweetIAmWatching%5D:
does not seem to support JSON or anything other than HTML or ATOM
5. Searched the list :)
I am just trying to get a handle on how to take a tweet that I get in
via a stream and go look [poll] for replies.
It seems I would need to follow the user using the streaming API and
match based on the in_reply_to_status_id but that would get quite out
of hand due to incoming tweet volume [i.e would need to follow a large
amount of users that may or may not ever produce a valid reply].
Thanks in advance,
Rob
--
Abraham Williams | Moved to Seattle | May cause email delays
Project | Intersect | http://intersect.labs.poseurtech.com
Hacker | http://abrah.am | http://twitter.com/abraham
This email is: [ ] shareable [x] ask first [ ] private.
Sent from Seattle, WA, United States
[twitter-dev] 403 Forbidden: error solved....sort of
I'm using the OAuth Sign In process with a flash browser-based application The following 2 steps ALWAYS work after I click my 'Sign In with Twitter' button, I make it to the Twitter OAuth sign in page so I have the correct request token, etc 1 successfully retrieve request token 2 navigate to Twitter's OAuth login page (following url isn't my actual URL but represents the actual path visible in the browser) http://www.mydomain.com/twitter/proxy.php?path=http%3A%2F%2Ftwitter.com%2Foauth%2Fauthenticate%3Foauth_token%3DiANj2mAYxOwSw9jf1868XmDSSeNZH2UFyB3mioyX5Q But the ONLY way I can proceed further (ie clicking 'Sign In' on the Twitter Oauth sign in page) without getting the 403 error is if the browser has just launched BEFORE navigating to the Twitter OAuth sign in page. Let me explain... ie I have a separate duplicate compiled version of my application on my desktop where I click the 'Sign In with Twitter' button to start the login process. It targets the same php proxy script, retrieves the request token, then issues a navigate to URL command which launches a new browser window, or in this case, launches the browser. Clicking signIn now works correctly, no 403 error Other wise(if the browser has ALREADY been open BEFORE I get to the twitter OAuth Sign In page) I get the 403 forbidden message, even if the username-password fields are blank. What gives? I am totally stumped This occurs in BOTH Safari and Firefox in OSXso I can assume its NOT a browser issue Perhaps a cookie issue...or something to do with my php proxy??? any suggestions welcome...
Re: [twitter-dev] Re: Best way to test success/failure for a status update
2010/1/16 M. Edward (Ed) Borasky zzn...@gmail.com Is this in fact a valid assumption, and is it documented anywhere? I'm anal about that sort of thing for a variety of reasons. ;-) Yes. I'm not sure if it is documented anywhere other then emails from Twitter to the group. Abraham -- Abraham Williams | Moved to Seattle | May cause email delays Project | Intersect | http://intersect.labs.poseurtech.com Hacker | http://abrah.am | http://twitter.com/abraham This email is: [ ] shareable [x] ask first [ ] private. Sent from Seattle, WA, United States
Re: [twitter-dev] authenticity_token same as access token?
I would hope not. access_tokens should be unique to each consumer token/user combination. Abraham On Sun, Jan 17, 2010 at 14:32, ryan alford ryanalford...@gmail.com wrote: Trying to screen_scrape? I don't believe they are the same. Ryan Sent from my DROID On Jan 17, 2010 5:20 PM, eco_bach bac...@gmail.com wrote: Hi Can someone confirm or deny whether the authenticity_token returned is the same as 'access_token' referred to in the documentation? Thanks in advance! -- Abraham Williams | Moved to Seattle | May cause email delays Project | Intersect | http://intersect.labs.poseurtech.com Hacker | http://abrah.am | http://twitter.com/abraham This email is: [ ] shareable [x] ask first [ ] private. Sent from Seattle, WA, United States
Re: [twitter-dev] statuses/friends - Reverse navigation
You might try opening a feature request: http://code.google.com/p/twitter-api/issues/list This will at least let Twitter keep track of it. Abraham On Mon, Jan 18, 2010 at 04:23, Serdar Kiliç ski...@gmail.com wrote: Hello, I would like to make a request for an additional element in statuses/ friends that returns the id of the last page when using cursor based pagination. Suggested element could be named last_cursor. This could then allow for reverse navigation of a users friends list without the need to page forward 100 records at a time to get to their oldest friend, so to speak. Thanks, Serdar -- Abraham Williams | Moved to Seattle | May cause email delays Project | Intersect | http://intersect.labs.poseurtech.com Hacker | http://abrah.am | http://twitter.com/abraham This email is: [ ] shareable [x] ask first [ ] private. Sent from Seattle, WA, United States
[twitter-dev] Disappearing / Reappearing Social Graph Lists
I noticed an issue tonight where a user's Friends, Followers, and Lists counts randomly goes down to zero. For example, I can refresh http://twitter.com/TastyTracy a few times and her Friends, Followers, and Lists counts randomly drop to zero and come back on the next refresh. It also happens in the API. If I refresh the following method a few times, it will return the correct Friends array, but sometimes it will return an empty array, with a status of 200. http://api.twitter.com/1/statuses/friends.xml?screen_name=TastyTracycursor=-1 Can anyone confirm this is happening to them as well. Hopefully this won't magically be fixed by the time someone tries it on this example account.
Re: [twitter-dev] Disappearing / Reappearing Social Graph Lists
I've noticed this all day, across many accounts, both via the API and twitter.com . On Jan 20, 2010, at 10:57 PM, DustyReagan dustyrea...@gmail.com wrote: I noticed an issue tonight where a user's Friends, Followers, and Lists counts randomly goes down to zero. For example, I can refresh http://twitter.com/TastyTracy a few times and her Friends, Followers, and Lists counts randomly drop to zero and come back on the next refresh. It also happens in the API. If I refresh the following method a few times, it will return the correct Friends array, but sometimes it will return an empty array, with a status of 200. http://api.twitter.com/1/statuses/friends.xml?screen_name=TastyTracycursor=-1 Can anyone confirm this is happening to them as well. Hopefully this won't magically be fixed by the time someone tries it on this example account.
[twitter-dev] Re: API Limit of 150 is Obsolete
I would also like to request the API limit to be raised as soon as possible. I am not able to roll out an update for my desktop Twitter client, simply because the API limit is too low for the features I have implemented. The new version of my client utilizes Lists related APIs, which consumes a lot of API calls. Moreover, multiple API calls are currently required to get a chain of replies (conversation), which consumes significant number of API calls. The previously discussed features were implemented, because there was an official announcement to change the API limit to 1500. I know it is expected to happen in few weeks, but it would be good to know the estimated date for this, so the developers can make appropriate decisions on the application deployment timeline. -- Aki On Jan 21, 9:48 am, Eric Woodward e...@nambu.com wrote: I will come straight to the point: we need to an increase to the API limit to properly implement Twitter within a desktop client application given the addition of: 1) three retweets timelines; 2) checking the account's saved searches; and 3) up to 10-20 Twitter Lists timelines. Twitter Lists alone are causing real problems if a user follows more than 5 or so. We cant poll Twitter List subscriptions with one API call that combines them altogether, which we could then split apart client-side with some attached meta-data. That alone would have been a big help, and without it we are left polling each List as if it was a separate timeline, since that is what they are. Implementing proper Lists management is a non-starter within this limit, so is regular confirmation of a relationship between two users when asked for by the user (on Lists or search results). There is simply a lot of stuff I cannot do properly that is standard on twitter.com, all because I am subject to the API limit while twitter.com is not. Users simply do not understand this distinction in possibilities. I would like to formally ask on behalf of all client developers that the API limit increase to 250, from 150, for all applications whether they use OAuth or HTTP Basic Authentication. We are simply not able to implement Twitter properly within a limit of 150, but dont need a lot more, only another 100-200 API calls or so. If Twitter can even technically contemplate a 10x API limit increase to 1,500 for OAuth applications, surely an increase to 250 based on the addition of core features like official retweets and Lists is a reasonable request. A limit of 150 is simply obsolete, and has been for a long time. I do not want to wait for the UX repairs around OAuth for desktop applications, and I dont like being forced into OAuth sooner than we are ready just because we need the extra API hits just to do basic features properly. And besides, that was announced as two weeks away three weeks ago. I dont want to wait any longer. I want to properly implement the basics, like Lists polling, now. This is a considered email because I care about the quality of our Twitter implementation and I care about the Twitter ecosystem. I would appreciate a considered reply. --ejw Eric Woodward Email: e...@nambu.com
[twitter-dev] Re: twitter and cake/curl- Rate limit exceeded
i am sure that both are being rendered with auth.
On Jan 20, 6:30 pm, Abraham Williams 4bra...@gmail.com wrote:
Are you perhaps making authenticated calls to the API but
calling account/rate_limit_status unauthenticated? or vis versa?
Abraham
On Wed, Jan 20, 2010 at 13:55, mlecho saltlessbr...@gmail.com wrote:
hi. i am building an api for a project, and a portion implements
twitter. Cakephp is my framework. The problem i am having is despite
my approach, i am getting
{request:\/statuses\/user_timeline.xml?
screen_name=user_screen_name_example,error:Rate limit exceeded.
Clients may not make more than 150 requests per hour.}
However, if i query the twitter api to see how many requests i truly
have left, i am no where near 150. I have in my controller var
$cacheAction = 1800; and i am using the Cache helper so as to limt
the hits on the request...
[[ the approaches]]
The first attempt was to use the Twittersource from the bakery(http://
bakery.cakephp.org/articles/view/twitter-datasource).
The second approach was to curl the results through a custom method.
function _getCurrentTweets($user = NULL)
{
$tw = curl_init();
curl_setopt($tw, CURLOPT_GET, 1);
if (!$user) {
curl_setopt($tw, CURLOPT_URL,
$this-Tweet-tweets);// ie:
http://twitter.com/statuses/friends.xml?my_screen_name=101010
curl_setopt($tw, CURLOPT_USERPWD,
$this-Tweet-login);
}else
{
$t_url = $this-Tweet-tweetsWithUser.$user; // ie:
http://twitter.com/statuses/user_timeline.xml?screen_name=$user
curl_setopt($tw, CURLOPT_URL, $t_url);
}
curl_setopt($tw, CURLOPT_RETURNTRANSFER, TRUE);
$twi = curl_exec($tw);
curl_close($tw);
$tweeters = new SimpleXMLElement($twi);
return $tweeters;
}
perhaps there is a bigger picture i am missing? I had thought this was
a caching issue, but now i am not so sure.
--
Abraham Williams | Moved to Seattle | May cause email delays
Project | Intersect |http://intersect.labs.poseurtech.com
Hacker |http://abrah.am|http://twitter.com/abraham
This email is: [ ] shareable [x] ask first [ ] private.
Sent from Seattle, WA, United States
