[twitter-dev] Is the home timeline dropping tweets?
I've noticed both on twitter.com and via the API that a tweet from a person I follow isn't showing up in my home timeline. I can see older tweets from this person in my home timeline and in my @ timeline, but not the latest one.
[twitter-dev] visiblitiy of @mentions in Tweets
Hello, I am new to Twitter development, I want to know is it possible to change visibility of mentions in my tweets. I want to mention somebody via @username in my Tweet x, but also I want Tweet x to be visible only for the user spesificed with username. I don't want to use direct message since as far as I know there should be at least one of the 'followed' or 'following' relation in order to send direct message. Thank you.
[twitter-dev] Re: API Rate Limit
Thanks for the reply, things are much clearer now, I assume that if a user on a white-listed IP has exhausted his 20k quota, then he is still entitled with 150/hour limit which he can use for authenticated requests on a non-whitelisted IP. Vikas On Dec 16, 9:26 pm, Abraham Williams 4bra...@gmail.com wrote: I've filed a bug to get the documentation updated. It could be phrased better as 20k per user per whitelisted IP. If you have N users on a whitelisted IP you should have N * 20k authenticated request every hour. Abraham On Tue, Dec 15, 2009 at 23:52, vikas cvika...@gmail.com wrote: Hi, The document says Each whitelisted entity, whether an account or IP address, is allowed 2 requests per hour. , in one of the twitter-development-talk i found this, What you all have been confirming is correct. The intended behavior is 20k per IP unauthenticated, and 20k per IP *per user* authenticated. This is not a bug. , what does 20k per IP Per User means ? If N number of users are using my application which communicates with Twitter over a whitelisted IP, then in total, how many GET-requests- credit my application will get from Twitter per hour for authenticated based requists? On Dec 15, 9:12 pm, Abraham Williams 4bra...@gmail.com wrote: Here is Twitter's documentation on rate limiting: http://apiwiki.twitter.com/Rate-limiting Abraham On Tue, Dec 15, 2009 at 09:21, vikas cvika...@gmail.com wrote: Hi, I went through the group lists searching for a clear understanding of API rate limit, but unfortunately could not able to get a clear idea. There are already many discussions about this but i am asking this again as i need this information to develop my product. I have few simple questions, the answers to which will solve my problem, any one please help, does the limit applies to IP only? ex, if N number of users are requesting through a whitelisted IP, then only IP's limit count is decreased and the individual users count is not changed or is it ip and also user based ? ex, if my IP is whitelisted, then for 20,000 users i will get 20k * 20k requests credit per hour. Please explain the exact way the rate limit is working thanks and regards, Vikas -- Abraham Williams | Awesome Lists |http://bit.ly/sprout608 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 Madison, WI, United States -- Abraham Williams | Awesome Lists |http://bit.ly/sprout608 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 Madison, WI, United States
[twitter-dev] Getting Popular Topics Today and This Week
It seems grouping and counting, then ranking the topics returned by Daily and Weekly trend API does not give the correct top topics shown in home page of twitter.com. Can anyone tell me how the Popular topics today and Popular topics this week works in http://twitter.com/? i.e. after parsing http://search.twitter.com/trends/daily.json, topics are simply counted and ranked. however, the result is about less than 50% accurate to what is displayed in the home page. Anyone knows the actual algorithm used in the site? I just noticed yesterday that Today and Weekly list no longer have hashtag topics? Am I correct on this observation? Thanks for any lead on this.
[twitter-dev] URLification
When adding a URL surrounded by parentheses or followed by a period, these marks are included in the resulting link. Is a trailing whitespace the only workaround? It's ugly and wastes a character. _ Windows Live Hotmail: Your friends can get your Facebook updates, right from Hotmail®. http://www.microsoft.com/middleeast/windows/windowslive/see-it-in-action/social-network-basics.aspx?ocid=PID23461::T:WLMTAGL:ON:WL:en-xm:SI_SB_4:092009
[twitter-dev] Retweet API methods returning 404
The following retweet methods have started returning 404's in our unit testes: http://api.twitter.com/1/statuses/retweeted_by_me.json http://api.twitter.com/1/statuses/retweeted_to_me.json http://api.twitter.com/1/statuses/retweets_of_me.json http://api.twitter.com/1/statuses/retweets/[any_status_id].json Anyone else having this issue, or know what happened to these API methods?
Re: [twitter-dev] Retweet API methods returning 404
Personally, my unit's testes don't call the Twitter API ... Seeing the same 404s on retweet calls however. ∞ Andy Badera ∞ +1 518-641-1280 Google Voice ∞ This email is: [ ] bloggable [x] ask first [ ] private ∞ Google me: http://www.google.com/search?q=andrew%20badera On Thu, Dec 17, 2009 at 7:05 AM, Dimebrain daniel.cre...@gmail.com wrote: The following retweet methods have started returning 404's in our unit testes: http://api.twitter.com/1/statuses/retweeted_by_me.json http://api.twitter.com/1/statuses/retweeted_to_me.json http://api.twitter.com/1/statuses/retweets_of_me.json http://api.twitter.com/1/statuses/retweets/[any_status_id].json Anyone else having this issue, or know what happened to these API methods?
Re: [twitter-dev] Retweet API methods returning 404
They are working for me, both on the API and the website - are they back for you, too? Or are just some users affected? Marco 2009/12/17 Abraham Williams 4bra...@gmail.com Retweets are disabled on twitter.com. I don't see any status message announcing it though. Abraham On Thu, Dec 17, 2009 at 06:05, Dimebrain daniel.cre...@gmail.com wrote: The following retweet methods have started returning 404's in our unit testes: http://api.twitter.com/1/statuses/retweeted_by_me.json http://api.twitter.com/1/statuses/retweeted_to_me.json http://api.twitter.com/1/statuses/retweets_of_me.json http://api.twitter.com/1/statuses/retweets/[any_status_id].jsonhttp://api.twitter.com/1/statuses/retweets/%5Bany_status_id%5D.json Anyone else having this issue, or know what happened to these API methods? -- Abraham Williams | Awesome Lists | http://bit.ly/sprout608 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 Madison, WI, United States
Re: [twitter-dev] Retweet API methods returning 404
okay - just noticed that they work on my whitelisted account, but not on a regular account. so yeah - looks as if RTs are down right now in general. Marco 2009/12/17 Marco Kaiser kaiser.ma...@gmail.com They are working for me, both on the API and the website - are they back for you, too? Or are just some users affected? Marco 2009/12/17 Abraham Williams 4bra...@gmail.com Retweets are disabled on twitter.com. I don't see any status message announcing it though. Abraham On Thu, Dec 17, 2009 at 06:05, Dimebrain daniel.cre...@gmail.com wrote: The following retweet methods have started returning 404's in our unit testes: http://api.twitter.com/1/statuses/retweeted_by_me.json http://api.twitter.com/1/statuses/retweeted_to_me.json http://api.twitter.com/1/statuses/retweets_of_me.json http://api.twitter.com/1/statuses/retweets/[any_status_id].jsonhttp://api.twitter.com/1/statuses/retweets/%5Bany_status_id%5D.json Anyone else having this issue, or know what happened to these API methods? -- Abraham Williams | Awesome Lists | http://bit.ly/sprout608 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 Madison, WI, United States
[twitter-dev] Re: Retweet API methods returning 404
I wish when they disabled features like this they told us! On Dec 17, 1:12 pm, Marco Kaiser kaiser.ma...@gmail.com wrote: okay - just noticed that they work on my whitelisted account, but not on a regular account. so yeah - looks as if RTs are down right now in general. Marco 2009/12/17 Marco Kaiser kaiser.ma...@gmail.com They are working for me, both on the API and the website - are they back for you, too? Or are just some users affected? Marco 2009/12/17 Abraham Williams 4bra...@gmail.com Retweets are disabled on twitter.com. I don't see any status message announcing it though. Abraham On Thu, Dec 17, 2009 at 06:05, Dimebrain daniel.cre...@gmail.com wrote: The following retweet methods have started returning 404's in our unit testes: http://api.twitter.com/1/statuses/retweeted_by_me.json http://api.twitter.com/1/statuses/retweeted_to_me.json http://api.twitter.com/1/statuses/retweets_of_me.json http://api.twitter.com/1/statuses/retweets/[any_status_id].jsonhttp://api.twitter.com/1/statuses/retweets/%5Bany_status_id%5D.json Anyone else having this issue, or know what happened to these API methods? -- Abraham Williams | Awesome Lists |http://bit.ly/sprout608 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 Madison, WI, United States
[twitter-dev] Re: URLification
Periods and parentheses are valid url characters. Assuming that an adjacent period or closing parenthesis is not part of the url is a gamble. The most sensible urlification includes all valid characters until it finds one that clearly delimits the url such as a space. http://www.ietf.org/rfc/rfc1738.txt On Dec 17, 7:13 am, Ken Dobruskin k...@cimas.ch wrote: When adding a URL surrounded by parentheses or followed by a period, these marks are included in the resulting link. Is a trailing whitespace the only workaround? It's ugly and wastes a character. _ Windows Live Hotmail: Your friends can get your Facebook updates, right from Hotmail®.http://www.microsoft.com/middleeast/windows/windowslive/see-it-in-act...
RE: [twitter-dev] Re: URLification
True, but Yahoo! Mail and others do get it right. It's been a few years I no longer worry sending an email with a URL at the end of a sentence. I wonder how they do it. Date: Thu, 17 Dec 2009 05:48:31 -0800 Subject: [twitter-dev] Re: URLification From: dba...@gmail.com To: twitter-development-talk@googlegroups.com Periods and parentheses are valid url characters. Assuming that an adjacent period or closing parenthesis is not part of the url is a gamble. The most sensible urlification includes all valid characters until it finds one that clearly delimits the url such as a space. http://www.ietf.org/rfc/rfc1738.txt On Dec 17, 7:13 am, Ken Dobruskin k...@cimas.ch wrote: When adding a URL surrounded by parentheses or followed by a period, these marks are included in the resulting link. Is a trailing whitespace the only workaround? It's ugly and wastes a character. _ Windows Live Hotmail: Your friends can get your Facebook updates, right from Hotmail®.http://www.microsoft.com/middleeast/windows/windowslive/see-it-in-act... _ Windows Live: Friends get your Flickr, Yelp, and Digg updates when they e-mail you. http://www.microsoft.com/middleeast/windows/windowslive/see-it-in-action/social-network-basics.aspx?ocid=PID23461::T:WLMTAGL:ON:WL:en-xm:SI_SB_3:092010
Re: [twitter-dev] hits, visits, etc to my tweets
no, unfortunately there isn't. there may be a third party service that does this, however. On Thu, Dec 17, 2009 at 2:55 AM, Frank gn...@windstream.net wrote: Is there any way the number of hits on my tweet? I am interested only in the number of folks who have viewed or visited ... not the names nor the numbers of posts? This might include mostly unregistered viewers -- Raffi Krikorian Twitter Platform Team http://twitter.com/raffi
Re: [twitter-dev] hits, visits, etc to my tweets
How might you envision a third party service delivering this, Raffi? Wouldn't it be a bit difficult without tracking code on-page? ∞ Andy Badera ∞ +1 518-641-1280 Google Voice ∞ This email is: [ ] bloggable [x] ask first [ ] private ∞ Google me: http://www.google.com/search?q=andrew%20badera On Thu, Dec 17, 2009 at 9:46 AM, Raffi Krikorian ra...@twitter.com wrote: no, unfortunately there isn't. there may be a third party service that does this, however. On Thu, Dec 17, 2009 at 2:55 AM, Frank gn...@windstream.net wrote: Is there any way the number of hits on my tweet? I am interested only in the number of folks who have viewed or visited ... not the names nor the numbers of posts? This might include mostly unregistered viewers -- Raffi Krikorian Twitter Platform Team http://twitter.com/raffi
Re: [twitter-dev] hits, visits, etc to my tweets
Frank == Frank gn...@windstream.net writes: Frank Is there any way the number of hits on my tweet? I am interested Frank only in the number of folks who have viewed or visited ... not the Frank names nor the numbers of posts? This might include mostly Frank unregistered viewers If your tweet includes a bit.ly link, you can go to the bit.ly URL with a + sign appended, and see stats there. Terry
Re: [twitter-dev] Getting Popular Topics Today and This Week
It seems grouping and counting, then ranking the topics returned by Daily and Weekly trend API does not give the correct top topics shown in home page of twitter.com. Can anyone tell me how the Popular topics today and Popular topics this week works in http://twitter.com/? i.e. after parsing http://search.twitter.com/trends/daily.json, topics are simply counted and ranked. however, the result is about less than 50% accurate to what is displayed in the home page. Anyone knows the actual algorithm used in the site? the front page is a curated version. I just noticed yesterday that Today and Weekly list no longer have hashtag topics? Am I correct on this observation. yup - the today and weekly list, on the front page, has had hashtags stripped out. -- Raffi Krikorian Twitter Platform Team http://twitter.com/raffi
[twitter-dev] Re: Retweet API methods returning 404
Yes, I'm getting 404 errors as well. This was not happening yesterday. http://twitter.com/statuses/show/5211439124.xml does not return a 404 http://api.twitter.com/1/statuses/retweets/5211439124.json returns a 404 So, obviously the status is there, but the retweet api isn't working; or maybe they have started returning 404s if there aren't retweets available for a status? On Dec 17, 6:05 am, Dimebrain daniel.cre...@gmail.com wrote: The following retweet methods have started returning 404's in our unit testes: http://api.twitter.com/1/statuses/retweeted_by_me.jsonhttp://api.twitter.com/1/statuses/retweeted_to_me.jsonhttp://api.twitter.com/1/statuses/retweets_of_me.jsonhttp://api.twitter.com/1/statuses/retweets/[any_status_id].json Anyone else having this issue, or know what happened to these API methods?
[twitter-dev] iPhone image uploading
Hello guys!
I have found on the twitter-site this faq:
The image update methods require multipart form data. They do not accept a
URL to an image not do they accept the raw image bytes. They instead require
the data to be delivered in the form of a file upload filed as defined in
RFC1867. The content-type attribute of the image field is checked for valid
image type. If you are using PHP/CURL there is a known bug that has since
been fixed in the CVS version of PHP. Most installations are not yet using
this version and therefore fail during image upload.
I wrote a little code to upload a profile image to my twitter, but
somethings wrong.
Here's my code:
- (void)uploadProfileImage {
UIImage *myImage = [UIImage imageNamed:@pic1.png];
NSData *myImageData = [[NSData alloc]
initWithData:UIImagePNGRepresentation(myImage)];
NSString *bodyString = [NSString stringWithFormat:@image=%@,
[[[NSString alloc] initWithData:myImageData
encoding:NSUTF8StringEncoding] autorelease]];
NSString *apiUrl = @http://twitter.com/account/
update_profile_image.json;
NSURL *url = [NSURL URLWithString:apiUrl];
NSMutableURLRequest *updateRequest = [NSMutableURLRequest
requestWithURL:url
cachePolicy:NSURLRequestReloadIgnoringCacheData
timeoutInterval:TWITTER_SEND_UPDATE_TIMEOUT];
[updateRequest setHTTPShouldHandleCookies:NO];
[updateRequest setHTTPMethod:@POST];
[updateRequest setValue:@application/x-www-form-urlencoded
forHTTPHeaderField:@Content-Type];
[updateRequest setHTTPBody:[bodyString
dataUsingEncoding:NSASCIIStringEncoding allowLossyConversion:YES]];
[updateRequest setValue:[NSString stringWithFormat:@%d, [bodyString
length]] forHTTPHeaderField:@Content-Length];
NSLog(@Trying to connect...);
NSURLConnection *theConnection = [[NSURLConnection alloc]
initWithRequest:updateRequest delegate:self];
if (theConnection) {
//_receivedData = [[NSMutableData data] retain];
NSLog(@Connected!);
} else {
NSLog(@Not connected!);
// Inform the user that the download could not be made
}
}
And one more method needed:
- (void)connection:(NSURLConnection *)connection
didReceiveAuthenticationChallenge:(NSURLAuthenticationChallenge *)
challenge {
if ([challenge previousFailureCount] == 0) {
NSURLCredential *newCredential = [NSURLCredential
credentialWithUser:@username password:@password
persistence:NSURLCredentialPersistenceNone];
[[challenge sender] useCredential:newCredential
forAuthenticationChallenge:challenge];
} else {
[[challenge sender] cancelAuthenticationChallenge:challenge];
NSLog(@Invalid username and password!);
}
}
And with this method I am receiving the information from twitter:
- (void)connection:(NSURLConnection *)connection didReceiveData:
(NSData *)data {
NSLog([[[NSString alloc] initWithData:data
encoding:NSASCIIStringEncoding] autorelease]);
}
But I am getting some strange error. The response isn't a json answer,
it is a html-like answer. Maybe do you have any idea why is that?
Re: [twitter-dev] iPhone image uploading
If that really a response from Twitter? Looks more like it's on your
app's side (SWAG) ...
∞ Andy Badera
∞ +1 518-641-1280 Google Voice
∞ This email is: [ ] bloggable [x] ask first [ ] private
∞ Google me: http://www.google.com/search?q=andrew%20badera
On Thu, Dec 17, 2009 at 9:54 AM, Infinity 320 infinity...@gmail.com wrote:
Hello guys!
I have found on the twitter-site this faq:
The image update methods require multipart form data. They do not accept a
URL to an image not do they accept the raw image bytes. They instead require
the data to be delivered in the form of a file upload filed as defined in
RFC1867. The content-type attribute of the image field is checked for valid
image type. If you are using PHP/CURL there is a known bug that has since
been fixed in the CVS version of PHP. Most installations are not yet using
this version and therefore fail during image upload.
I wrote a little code to upload a profile image to my twitter, but
somethings wrong.
Here's my code:
- (void)uploadProfileImage {
UIImage *myImage = [UIImage imageNamed:@pic1.png];
NSData *myImageData = [[NSData alloc]
initWithData:UIImagePNGRepresentation(myImage)];
NSString *bodyString = [NSString stringWithFormat:@image=%@,
[[[NSString alloc] initWithData:myImageData
encoding:NSUTF8StringEncoding] autorelease]];
NSString *apiUrl = @http://twitter.com/account/
update_profile_image.json;
NSURL *url = [NSURL URLWithString:apiUrl];
NSMutableURLRequest *updateRequest = [NSMutableURLRequest
requestWithURL:url
cachePolicy:NSURLRequestReloadIgnoringCacheData
timeoutInterval:TWITTER_SEND_UPDATE_TIMEOUT];
[updateRequest setHTTPShouldHandleCookies:NO];
[updateRequest setHTTPMethod:@POST];
[updateRequest setValue:@application/x-www-form-urlencoded
forHTTPHeaderField:@Content-Type];
[updateRequest setHTTPBody:[bodyString
dataUsingEncoding:NSASCIIStringEncoding allowLossyConversion:YES]];
[updateRequest setValue:[NSString stringWithFormat:@%d, [bodyString
length]] forHTTPHeaderField:@Content-Length];
NSLog(@Trying to connect...);
NSURLConnection *theConnection = [[NSURLConnection alloc]
initWithRequest:updateRequest delegate:self];
if (theConnection) {
//_receivedData = [[NSMutableData data] retain];
NSLog(@Connected!);
} else {
NSLog(@Not connected!);
// Inform the user that the download could not be made
}
}
And one more method needed:
- (void)connection:(NSURLConnection *)connection
didReceiveAuthenticationChallenge:(NSURLAuthenticationChallenge *)
challenge {
if ([challenge previousFailureCount] == 0) {
NSURLCredential *newCredential = [NSURLCredential
credentialWithUser:@username password:@password
persistence:NSURLCredentialPersistenceNone];
[[challenge sender] useCredential:newCredential
forAuthenticationChallenge:challenge];
} else {
[[challenge sender] cancelAuthenticationChallenge:challenge];
NSLog(@Invalid username and password!);
}
}
And with this method I am receiving the information from twitter:
- (void)connection:(NSURLConnection *)connection didReceiveData:
(NSData *)data {
NSLog([[[NSString alloc] initWithData:data
encoding:NSASCIIStringEncoding] autorelease]);
}
But I am getting some strange error. The response isn't a json answer,
it is a html-like answer. Maybe do you have any idea why is that?
Re: [twitter-dev] Re: Retweet API methods returning 404
Looks like RT is back up. Tom On Thu, Dec 17, 2009 at 3:39 PM, cadams500 ch...@emaildatasource.comwrote: Yes, I'm getting 404 errors as well. This was not happening yesterday. http://twitter.com/statuses/show/5211439124.xml does not return a 404 http://api.twitter.com/1/statuses/retweets/5211439124.json returns a 404 So, obviously the status is there, but the retweet api isn't working; or maybe they have started returning 404s if there aren't retweets available for a status? On Dec 17, 6:05 am, Dimebrain daniel.cre...@gmail.com wrote: The following retweet methods have started returning 404's in our unit testes: http://api.twitter.com/1/statuses/retweeted_by_me.jsonhttp://api.twitter.com/1/statuses/retweeted_to_me.jsonhttp://api.twitter.com/1/statuses/retweets_of_me.jsonhttp://api.twitter.com/1/statuses/retweets/[any_status_id].json Anyone else having this issue, or know what happened to these API methods?
[twitter-dev] Twitter Search cache or delayed data?
I built an application that aggregates data a few times per day based on a hashtag search term. My search results for tweets I've done as tests are not showing up in the search. What's the delay time before they show up? My client is asking and I have no idea what to tell them. The application is built and 100% working, and I've confirmed manually that Twitter is in fact not showing the tweets. I can search for other things like #gaza or #iphone and I get plenty. Thanks!
[twitter-dev] Problem signing for statuses/update
I'm having a problem signing status updates, but only when any of these characters is contained in the post: ! * ( ) ' For all other posts everything works fine. At first I noticed that these characters weren't being escaped, so I fixed that ( I used this: http://www.viera.info/URLEncode_Code_Chart.htm as a reference) and everything is now going out properly and the proxy debugger I'm using (Charles) decides the values properly so I think that's fine. The response I get back looks like this: hash request/statuses/update.xml/request errorIncorrect signature/error /hash Here is what my postdata looks like: oauth_consumer_key=**CONSUMER_KEY**oauth_nonce=2287oauth_signature_method=HMAC- SHA1oauth_timestamp=1261066215oauth_t oken=**OAUTH_TOKEN**oauth_version=1.0status=BAD%20CHARS%20%21%2a %28%29%27oauth_signature=LafAO6Fd1lfZ1I 6aaaGZqDKyhnA%3D Any clues as to what I'm doing wrong would help, thanks
Re: [twitter-dev] Twitter Search cache or delayed data?
I built an application that aggregates data a few times per day based on a hashtag search term. My search results for tweets I've done as tests are not showing up in the search. What's the delay time before they show up? My client is asking and I have no idea what to tell them. The application is built and 100% working, and I've confirmed manually that Twitter is in fact not showing the tweets. I can search for other things like #gaza or #iphone and I get plenty. Twitter searches are very fast normally -- I see search results in near real-time. The problem is right now, the timelines are very delayed. Twitter is aware of that; see status.twitter.com -- personal: http://www.cameronkaiser.com/ -- Cameron Kaiser * Floodgap Systems * www.floodgap.com * ckai...@floodgap.com -- When in doubt, take a pawn. -- Mission: Impossible (Crack-Up)
[twitter-dev] Re: Twitter Search cache or delayed data?
Okay. Do we at least know how delayed? I posted a test tweet as we launched the website yesterday with my publicly accessible Twitter account and that was at 3:40 PM PST yesterday. It's been almost 24 hours and I still don't see it come up in search. http://search.twitter.com/search?q=%23befantastic04 Thanks for your help. At least I have something to tell my client now.
RE: [twitter-dev] Re: URLification
A closing parenthesis followed by a space seems like a pretty safe bet too. I'm sure those rules have been worked out long ago - the RFC was published in '94. Date: Thu, 17 Dec 2009 07:55:14 -0800 Subject: [twitter-dev] Re: URLification From: dba...@gmail.com To: twitter-development-talk@googlegroups.com You can get pretty sophisticated and have lots of heuristics to guess what the user actually meant. For example, a period followed by a space and a word that starts with uppercase almost certainly means that the period was the end of a sentence and not part of the url. Twitter probably should do this, as it's quite conservative. Diego On Dec 17, 11:10 am, Ken Dobruskin k...@cimas.ch wrote: True, but Yahoo! Mail and others do get it right. It's been a few years I no longer worry sending an email with a URL at the end of a sentence. I wonder how they do it. Date: Thu, 17 Dec 2009 05:48:31 -0800 Subject: [twitter-dev] Re: URLification From: dba...@gmail.com To: twitter-development-talk@googlegroups.com Periods and parentheses are valid url characters. Assuming that an adjacent period or closing parenthesis is not part of the url is a gamble. The most sensible urlification includes all valid characters until it finds one that clearly delimits the url such as a space. http://www.ietf.org/rfc/rfc1738.txt On Dec 17, 7:13 am, Ken Dobruskin k...@cimas.ch wrote: When adding a URL surrounded by parentheses or followed by a period, these marks are included in the resulting link. Is a trailing whitespace the only workaround? It's ugly and wastes a character. _ Windows Live Hotmail: Your friends can get your Facebook updates, right from Hotmail®.http://www.microsoft.com/middleeast/windows/windowslive/see-it-in-act... _ Windows Live: Friends get your Flickr, Yelp, and Digg updates when they e-mail you.http://www.microsoft.com/middleeast/windows/windowslive/see-it-in-act... _ Keep your friends updated—even when you’re not signed in. http://www.microsoft.com/middleeast/windows/windowslive/see-it-in-action/social-network-basics.aspx?ocid=PID23461::T:WLMTAGL:ON:WL:en-xm:SI_SB_5:092010
[twitter-dev] app suspension
Hello All, I have basically a test oAuth account for an application. It has been suspended and I really am baffled as to why. My live app is not suspended, just this test app, used for a separate domain. My app does not broadcast, except in one very limited use-case and no users have been affected or were any accounts compromised. Obviously, this is a scary issue for developers and considering the app doesn't send tweets, etc, it seems pretty odd that it would flag the system for suspension. Thanks Peter
[twitter-dev] Oauth using api.twitter.com vs twitter.com
Hi all, The tweepy twitter client uses api.twitter.com for the host for oauth calls: REQUEST_TOKEN_URL = 'http://api.twitter.com/oauth/request_token' AUTHORIZATION_URL = 'http://api.twitter.com/oauth/authorize' AUTHENTICATE_URL = 'http://api.twitter.com/oauth/authenticate' ACCESS_TOKEN_URL = 'http://api.twitter.com/oauth/access_token' I've found that this works, until the user tries to sign out or sign up during the authorization; if this happens, they get a 404. If, however, twitter.com is used as the host: REQUEST_TOKEN_URL = 'http://twitter.com/oauth/request_token' AUTHORIZATION_URL = 'http://twitter.com/oauth/authorize' AUTHENTICATE_URL = 'http://twitter.com/oauth/authenticate' ACCESS_TOKEN_URL = 'http://twitter.com/oauth/access_token' then *everything*, including signout and signup, works. This also matches the instructions at http://twitter.com/oauth_clients/details/%d. However, it strikes me as odd that the oauth stuff half works at api.twitter.com. My question is: What is the bug? That the api.twitter.com oauth endpoints only partially work -- in which case tweepy is fine and I should file a bug with Twitter -- OR that the api.twitter.com oauth works at all -- in which case I should ping the author of tweepy and perhaps suggest to Twitter that they remove this partial functionality to prevent future confusion? Many thanks, Josh
[twitter-dev] Re: app suspension
Update on this item: Twitter responded and said the cause of suspension was because of the name of my app. It was named stats and twitter api deemed this could be confusing to users. So, something else to keep in mind if you incur an app suspension. Thanks! Peter On Thu, Dec 17, 2009 at 11:11 AM, Peter Denton petermden...@gmail.comwrote: Hello All, I have basically a test oAuth account for an application. It has been suspended and I really am baffled as to why. My live app is not suspended, just this test app, used for a separate domain. My app does not broadcast, except in one very limited use-case and no users have been affected or were any accounts compromised. Obviously, this is a scary issue for developers and considering the app doesn't send tweets, etc, it seems pretty odd that it would flag the system for suspension. Thanks Peter
Re: [twitter-dev] Oauth using api.twitter.com vs twitter.com
On Fri, Dec 18, 2009 at 2:22 AM, Josh Bleecher Snyder joshar...@gmail.com wrote: Hi all, The tweepy twitter client uses api.twitter.com for the host for oauth calls: REQUEST_TOKEN_URL = 'http://api.twitter.com/oauth/request_token' AUTHORIZATION_URL = 'http://api.twitter.com/oauth/authorize' AUTHENTICATE_URL = 'http://api.twitter.com/oauth/authenticate' ACCESS_TOKEN_URL = 'http://api.twitter.com/oauth/access_token' I've found that this works, until the user tries to sign out or sign up during the authorization; if this happens, they get a 404. If, however, twitter.com is used as the host: I think this happens due to cookie. People sign in twitter.com. not in api.twitter.com. When a user already signed in, the cookie's domain is twitter.com. Now if you redirect to http://api.twitter.com/oauth/authorize, browser wont load the cookie as its from twitter.com. It'll try to find cookies from api.twitter.com. But there is no cookie. So you have to sign in again I guess. Its better to use twitter.com instead of api.twitter.com when its one of those 4 oauth urls. -- Shiplu Mokaddim My talks, http://talk.cmyweb.net Follow me, http://twitter.com/shiplu SUST Programmers, http://groups.google.com/group/p2psust Innovation distinguishes bet ... ... (ask Steve Jobs the rest)
Re: [twitter-dev] Oauth using api.twitter.com vs twitter.com
Hey, Thanks for bringing this issue to my attention. I have opened an issue for it here [1]. I will look into this and see what I can do to help resolve it. Shiplu is probably on the right track about this being cookie related. Will post updates here and on the issue as I make progress. Thanks, Josh Roesslein Tweepy author On Thu, Dec 17, 2009 at 1:42 PM, shiplu shiplu@gmail.com wrote: On Fri, Dec 18, 2009 at 2:22 AM, Josh Bleecher Snyder joshar...@gmail.com wrote: Hi all, The tweepy twitter client uses api.twitter.com for the host for oauth calls: REQUEST_TOKEN_URL = 'http://api.twitter.com/oauth/request_token' AUTHORIZATION_URL = 'http://api.twitter.com/oauth/authorize' AUTHENTICATE_URL = 'http://api.twitter.com/oauth/authenticate' ACCESS_TOKEN_URL = 'http://api.twitter.com/oauth/access_token' I've found that this works, until the user tries to sign out or sign up during the authorization; if this happens, they get a 404. If, however, twitter.com is used as the host: I think this happens due to cookie. People sign in twitter.com. not in api.twitter.com. When a user already signed in, the cookie's domain is twitter.com. Now if you redirect to http://api.twitter.com/oauth/authorize, browser wont load the cookie as its from twitter.com. It'll try to find cookies from api.twitter.com. But there is no cookie. So you have to sign in again I guess. Its better to use twitter.com instead of api.twitter.com when its one of those 4 oauth urls. -- Shiplu Mokaddim My talks, http://talk.cmyweb.net Follow me, http://twitter.com/shiplu SUST Programmers, http://groups.google.com/group/p2psust Innovation distinguishes bet ... ... (ask Steve Jobs the rest)
Re: [twitter-dev] Oauth using api.twitter.com vs twitter.com
Sorry left off the link to the issue. [1] http://github.com/joshthecoder/tweepy/issues#issue/8 Josh On Thu, Dec 17, 2009 at 2:15 PM, Josh Roesslein jroessl...@gmail.com wrote: Hey, Thanks for bringing this issue to my attention. I have opened an issue for it here [1]. I will look into this and see what I can do to help resolve it. Shiplu is probably on the right track about this being cookie related. Will post updates here and on the issue as I make progress. Thanks, Josh Roesslein Tweepy author On Thu, Dec 17, 2009 at 1:42 PM, shiplu shiplu@gmail.com wrote: On Fri, Dec 18, 2009 at 2:22 AM, Josh Bleecher Snyder joshar...@gmail.com wrote: Hi all, The tweepy twitter client uses api.twitter.com for the host for oauth calls: REQUEST_TOKEN_URL = 'http://api.twitter.com/oauth/request_token' AUTHORIZATION_URL = 'http://api.twitter.com/oauth/authorize' AUTHENTICATE_URL = 'http://api.twitter.com/oauth/authenticate' ACCESS_TOKEN_URL = 'http://api.twitter.com/oauth/access_token' I've found that this works, until the user tries to sign out or sign up during the authorization; if this happens, they get a 404. If, however, twitter.com is used as the host: I think this happens due to cookie. People sign in twitter.com. not in api.twitter.com. When a user already signed in, the cookie's domain is twitter.com. Now if you redirect to http://api.twitter.com/oauth/authorize, browser wont load the cookie as its from twitter.com. It'll try to find cookies from api.twitter.com. But there is no cookie. So you have to sign in again I guess. Its better to use twitter.com instead of api.twitter.com when its one of those 4 oauth urls. -- Shiplu Mokaddim My talks, http://talk.cmyweb.net Follow me, http://twitter.com/shiplu SUST Programmers, http://groups.google.com/group/p2psust Innovation distinguishes bet ... ... (ask Steve Jobs the rest)
[twitter-dev] Current policy on following apps
I'm interested in building a following app for a specific vertical market. The api docs and tos seem to conflict with reality. These documents imply that all apps that automate following are forbidden, but there are many apps that do this listed in the Twitter app directories. I only want to build apps that meet with Twitter's approval, and I want to be a good citizen of the Twitter ecosystem, so I'd like some clarification on the current thinking about this subject. My goal is NOT to build a bulk follower that blindly follows and unfollows thousand of users each day. I understand the negative aspects of these. But I also realize that building a following is an essential part of being a productive Twitter user. Is there a middle ground that is allowed? My idea is to build an well behaved app that uses a procedure like this to build a following for a Twitter account: Select the most active Twitter users in a specific market. Follow a small number, perhaps 50, per day. If these follows are not followed back in a week, unfollow them. Log this attempt, and repeat it again after an interval of perhaps 30 days. If 2 or 3 follow attempts for an account fail to gain a follow back, then stop trying permanently for that account. So is this type of gradual following allowed, or is ANY type of automated following forbidden?
[twitter-dev] Getting Whitelisted For a Major Customer Of Ours
Hey Twitter Folks: 1. Working with a major customer of ours + live with marketing programs + promotions on your platform. 2. Could you help us get whitelisted? + there is a business opportunity for Twitter to acquire 500K-1Million users. 3. Who should we talk to figure things out? Thanks, Abir @Abir2
[twitter-dev] Re: URLification
I agree. I searched the issues db and didn't find it. Not sure if it belongs as an API issue but I submitted it anyway. http://code.google.com/p/twitter-api/issues/detail?id=1298 On Dec 17, 2:49 pm, Ken Dobruskin k...@cimas.ch wrote: A closing parenthesis followed by a space seems like a pretty safe bet too. I'm sure those rules have been worked out long ago - the RFC was published in '94. Date: Thu, 17 Dec 2009 07:55:14 -0800 Subject: [twitter-dev] Re: URLification From: dba...@gmail.com To: twitter-development-talk@googlegroups.com You can get pretty sophisticated and have lots of heuristics to guess what the user actually meant. For example, a period followed by a space and a word that starts with uppercase almost certainly means that the period was the end of a sentence and not part of the url. Twitter probably should do this, as it's quite conservative. Diego On Dec 17, 11:10 am, Ken Dobruskin k...@cimas.ch wrote: True, but Yahoo! Mail and others do get it right. It's been a few years I no longer worry sending an email with a URL at the end of a sentence. I wonder how they do it. Date: Thu, 17 Dec 2009 05:48:31 -0800 Subject: [twitter-dev] Re: URLification From: dba...@gmail.com To: twitter-development-talk@googlegroups.com Periods and parentheses are valid url characters. Assuming that an adjacent period or closing parenthesis is not part of the url is a gamble. The most sensible urlification includes all valid characters until it finds one that clearly delimits the url such as a space. http://www.ietf.org/rfc/rfc1738.txt On Dec 17, 7:13 am, Ken Dobruskin k...@cimas.ch wrote: When adding a URL surrounded by parentheses or followed by a period, these marks are included in the resulting link. Is a trailing whitespace the only workaround? It's ugly and wastes a character. _ Windows Live Hotmail: Your friends can get your Facebook updates, right from Hotmail®.http://www.microsoft.com/middleeast/windows/windowslive/see-it-in-act... _ Windows Live: Friends get your Flickr, Yelp, and Digg updates when they e-mail you.http://www.microsoft.com/middleeast/windows/windowslive/see-it-in-act... _ Keep your friends updated—even when you’re not signed in.http://www.microsoft.com/middleeast/windows/windowslive/see-it-in-act...
Re: [twitter-dev] Re: URLification
its not an API issue -- the API doesn't do any auto-URLification. however, i'll pass this thread off to the web client team. On Thu, Dec 17, 2009 at 1:13 PM, dbasch dba...@gmail.com wrote: I agree. I searched the issues db and didn't find it. Not sure if it belongs as an API issue but I submitted it anyway. http://code.google.com/p/twitter-api/issues/detail?id=1298 On Dec 17, 2:49 pm, Ken Dobruskin k...@cimas.ch wrote: A closing parenthesis followed by a space seems like a pretty safe bet too. I'm sure those rules have been worked out long ago - the RFC was published in '94. Date: Thu, 17 Dec 2009 07:55:14 -0800 Subject: [twitter-dev] Re: URLification From: dba...@gmail.com To: twitter-development-talk@googlegroups.com You can get pretty sophisticated and have lots of heuristics to guess what the user actually meant. For example, a period followed by a space and a word that starts with uppercase almost certainly means that the period was the end of a sentence and not part of the url. Twitter probably should do this, as it's quite conservative. Diego On Dec 17, 11:10 am, Ken Dobruskin k...@cimas.ch wrote: True, but Yahoo! Mail and others do get it right. It's been a few years I no longer worry sending an email with a URL at the end of a sentence. I wonder how they do it. Date: Thu, 17 Dec 2009 05:48:31 -0800 Subject: [twitter-dev] Re: URLification From: dba...@gmail.com To: twitter-development-talk@googlegroups.com Periods and parentheses are valid url characters. Assuming that an adjacent period or closing parenthesis is not part of the url is a gamble. The most sensible urlification includes all valid characters until it finds one that clearly delimits the url such as a space. http://www.ietf.org/rfc/rfc1738.txt On Dec 17, 7:13 am, Ken Dobruskin k...@cimas.ch wrote: When adding a URL surrounded by parentheses or followed by a period, these marks are included in the resulting link. Is a trailing whitespace the only workaround? It's ugly and wastes a character. _ Windows Live Hotmail: Your friends can get your Facebook updates, right from Hotmail®. http://www.microsoft.com/middleeast/windows/windowslive/see-it-in-act... _ Windows Live: Friends get your Flickr, Yelp, and Digg updates when they e-mail you. http://www.microsoft.com/middleeast/windows/windowslive/see-it-in-act... _ Keep your friends updated—even when you’re not signed in. http://www.microsoft.com/middleeast/windows/windowslive/see-it-in-act... -- Raffi Krikorian Twitter Platform Team http://twitter.com/raffi
Re: [twitter-dev] Getting Whitelisted For a Major Customer Of Ours
http://twitter.com/help/request_whitelisting On Thu, Dec 17, 2009 at 1:13 PM, Abir abstar...@gmail.com wrote: Hey Twitter Folks: 1. Working with a major customer of ours + live with marketing programs + promotions on your platform. 2. Could you help us get whitelisted? + there is a business opportunity for Twitter to acquire 500K-1Million users. 3. Who should we talk to figure things out? Thanks, Abir @Abir2 -- Raffi Krikorian Twitter Platform Team http://twitter.com/raffi
Re: [twitter-dev] Current policy on following apps
On Fri, Dec 18, 2009 at 3:57 AM, Adam Green a...@vibemetrix.com wrote: Select the most active Twitter users in a specific market. Follow a small number, perhaps 50, per day. If these follows are not followed back in a week, unfollow them. The above part seems abusive. My personal opinion though. Cause you starts to follow to get follower. Not to read their tweets. :P -- Shiplu Mokaddim My talks, http://talk.cmyweb.net Follow me, http://twitter.com/shiplu SUST Programmers, http://groups.google.com/group/p2psust Innovation distinguishes bet ... ... (ask Steve Jobs the rest)
[twitter-dev] Re: Getting Whitelisted For a Major Customer Of Ours
Thanks Raffi appreciate it. On Dec 17, 1:16 pm, Raffi Krikorian ra...@twitter.com wrote: http://twitter.com/help/request_whitelisting On Thu, Dec 17, 2009 at 1:13 PM, Abir abstar...@gmail.com wrote: Hey Twitter Folks: 1. Working with a major customer of ours + live with marketing programs + promotions on your platform. 2. Could you help us get whitelisted? + there is a business opportunity for Twitter to acquire 500K-1Million users. 3. Who should we talk to figure things out? Thanks, Abir @Abir2 -- Raffi Krikorian Twitter Platform Teamhttp://twitter.com/raffi
[twitter-dev] Re: Retweet API methods returning 404
Yeah it seems like app developers using retweets need to account for this in their designs since this isn't the first time RTs has gone down. On Dec 17, 12:23 pm, Xavier Grosjean xavier.grosj...@yoono.com wrote: Yoono is the only twitter client that switches back to old retweet mode when new RT feature is broken at Twitter :) 2009/12/17 Thomas Woolway tswool...@gmail.com Looks like RT is back up. Tom On Thu, Dec 17, 2009 at 3:39 PM, cadams500 ch...@emaildatasource.comwrote: Yes, I'm getting 404 errors as well. This was not happening yesterday. http://twitter.com/statuses/show/5211439124.xmldoes not return a 404 http://api.twitter.com/1/statuses/retweets/5211439124.jsonreturns a 404 So, obviously the status is there, but the retweet api isn't working; or maybe they have started returning 404s if there aren't retweets available for a status? On Dec 17, 6:05 am, Dimebrain daniel.cre...@gmail.com wrote: The following retweet methods have started returning 404's in our unit testes: http://api.twitter.com/1/statuses/retweeted_by_me.jsonhttp://api.twit...[any_status_id].jsonhttp://api.twitter.com/1/statuses/retweeted_by_me.jsonhttp://api.twit... Anyone else having this issue, or know what happened to these API methods?
Re: [twitter-dev] Re: Retweet API methods returning 404
I say I say I say, it was a joke, son. - Foghorn Leghorn Sent from my iPhone On Dec 17, 2009, at 6:07 PM, Dimebrain daniel.cre...@gmail.com wrote: Interesting, how do you approach API testing if not live? Wouldn't mind comparing notes. On Dec 17, 7:07 am, Andrew Badera and...@badera.us wrote: Personally, my unit's testes don't call the Twitter API ... Seeing the same 404s on retweet calls however. ∞ Andy Badera ∞ +1 518-641-1280 Google Voice ∞ This email is: [ ] bloggable [x] ask first [ ] private ∞ Google me:http://www.google.com/search?q=andrew%20badera On Thu, Dec 17, 2009 at 7:05 AM, Dimebrain daniel.cre...@gmail.com wrote: The following retweet methods have started returning 404's in our unit testes: http://api.twitter.com/1/statuses/retweeted_by_me.json http://api.twitter.com/1/statuses/retweeted_to_me.json http://api.twitter.com/1/statuses/retweets_of_me.json http://api.twitter.com/1/statuses/retweets/[any_status_id].json Anyone else having this issue, or know what happened to these API methods?
[twitter-dev] API Versioning Revisited
The yo-yo ride of the retweet API gave me this idea. It depends on proper versioning of the API by Twitter. Twitter creates an API call that returns the current working API version. We query that method and use that version of the API for our calls. If something goes down, Twitter simply pushes out the version number of an older API version, which is still working correctly. Our systems will then automatically fall back to using that older version, until Twitter again pushes out the new version number when it's back online. Dewald
Re: [twitter-dev] API Versioning Revisited
I am not sure how beneficial this would really be. Versioning from what I understand is for changes to the API that might break applications that have not yet updated. It wouldn't really provide any security against bugs/quirks in Twitter's backend which can cause downtime. So even older versions might be affected just as much as newer versions because down under they both use the same code, its just exposed differently from version to version. I have no idea how things work under the covers so maybe this could work. I'd take any security against down time I can get. :) Josh On Thu, Dec 17, 2009 at 8:35 PM, Dewald Pretorius dpr...@gmail.com wrote: The yo-yo ride of the retweet API gave me this idea. It depends on proper versioning of the API by Twitter. Twitter creates an API call that returns the current working API version. We query that method and use that version of the API for our calls. If something goes down, Twitter simply pushes out the version number of an older API version, which is still working correctly. Our systems will then automatically fall back to using that older version, until Twitter again pushes out the new version number when it's back online. Dewald
[twitter-dev] Re: Questions about opening the firehose
On Dec 15, 9:58 am, John Kalucki j...@twitter.com wrote: Bandwidth is likely to only be a small fraction of your total cost when consuming the firehose. If you want to focus on this small part and ignore all the other dominating costs, the prudent systems engineer would provision 2x to 3x daily peak to account for traffic spikes, growth, backlog retrieval, and to keep latency to a minimum. Not all have such requirements, though. So, somewhere between 5 and 15 mbit, very very roughly. Your requirements will certainly vary. The filtered and sampled streams are where virtually everyone will wind up. -John Kaluckihttp://twitter.com/jkalucki Services, Twitter Inc. I'm using the sampled stream at the moment and it's doing most of what I need. It's certainly more than enough for development and testing the algorithms. The filter stream, on the other hand, seems next to useless to me when compared with the stream coming out of Twitter search. For one thing, I do a lot of location-based processing. I'm quite interested in what's happening in Portland, Oregon, and not so much about the rest of the world. As far as I can tell, there's no geocode parameter for filter. In addition, I can do a search back in time with Twitter search - with filter, if I don't know what I'm looking for, it's going to go right by me. ;-) But really, I'm much more concerned about legal issues with the firehose than I am with technical issues. There are resellers of firehose data now. They have an advantage over random developers like myself, because they have a business relationship with Twitter and I don't. I can't make a credible business plan without knowing what I will and will not be able to legally do with firehose data, or how much it will cost me for access. -- M. Edward (Ed) Borasky http://borasky-research.net I've always regarded nature as the clothing of God. ~Alan Hovhaness
[twitter-dev] Re: API Versioning Revisited
Josh, This will not protect us against a case where something central to Twitter functioning malfunctions, but it will protect us against new or changed features malfunctioning. Dewald On Dec 17, 10:45 pm, Josh Roesslein jroessl...@gmail.com wrote: I am not sure how beneficial this would really be. Versioning from what I understand is for changes to the API that might break applications that have not yet updated. It wouldn't really provide any security against bugs/quirks in Twitter's backend which can cause downtime. So even older versions might be affected just as much as newer versions because down under they both use the same code, its just exposed differently from version to version. I have no idea how things work under the covers so maybe this could work. I'd take any security against down time I can get. :) Josh On Thu, Dec 17, 2009 at 8:35 PM, Dewald Pretorius dpr...@gmail.com wrote: The yo-yo ride of the retweet API gave me this idea. It depends on proper versioning of the API by Twitter. Twitter creates an API call that returns the current working API version. We query that method and use that version of the API for our calls. If something goes down, Twitter simply pushes out the version number of an older API version, which is still working correctly. Our systems will then automatically fall back to using that older version, until Twitter again pushes out the new version number when it's back online. Dewald
[twitter-dev] How to get Following count of user
Hello All, I am sending request to http://twitter.com/statuses/friends/'.$user.'.xml?cursor=-1 url for getting the following list. I am not able to get the count of the following. Also i had read that this url provide only 100 records so how can i get all the follwer count of twitter user ($user) ? How can i get it? Thank you in advance. -- Warm Regards, Gaurav Shaha 9823359549. Don't try to show off, just be youself and do what you ENJOY doing
Re: [twitter-dev] How to get Following count of user
Try using: http://apiwiki.twitter.com/Twitter-REST-API-Method:-users show there is a followers_count element. Abraham On Thu, Dec 17, 2009 at 22:03, Gaurav Shaha gauravshah...@gmail.com wrote: Hello All, I am sending request to http://twitter.com/statuses/friends/'.$user.'.xml?cursor=-1 url for getting the following list. I am not able to get the count of the following. Also i had read that this url provide only 100 records so how can i get all the follwer count of twitter user ($user) ? How can i get it? Thank you in advance. -- Warm Regards, Gaurav Shaha 9823359549. Don't try to show off, just be youself and do what you ENJOY doing -- Abraham Williams | Awesome Lists | http://bit.ly/sprout608 Project | Intersect | http://intersect.labs.poseurtech.com Hacker | http://abrah.am | http://twitter.com/abraham This email is: [ ] shareable [x] ask first [ ] private.
Re: [twitter-dev] Re: API Versioning Revisited
So say Geo is version 3, RT is version 4 and Lists is version 5. All of which are still in beta. If something goes wrong with Geo do they revert to 2 and disable RTs and Lists? Abraham On Thu, Dec 17, 2009 at 21:03, Dewald Pretorius dpr...@gmail.com wrote: Josh, This will not protect us against a case where something central to Twitter functioning malfunctions, but it will protect us against new or changed features malfunctioning. Dewald On Dec 17, 10:45 pm, Josh Roesslein jroessl...@gmail.com wrote: I am not sure how beneficial this would really be. Versioning from what I understand is for changes to the API that might break applications that have not yet updated. It wouldn't really provide any security against bugs/quirks in Twitter's backend which can cause downtime. So even older versions might be affected just as much as newer versions because down under they both use the same code, its just exposed differently from version to version. I have no idea how things work under the covers so maybe this could work. I'd take any security against down time I can get. :) Josh On Thu, Dec 17, 2009 at 8:35 PM, Dewald Pretorius dpr...@gmail.com wrote: The yo-yo ride of the retweet API gave me this idea. It depends on proper versioning of the API by Twitter. Twitter creates an API call that returns the current working API version. We query that method and use that version of the API for our calls. If something goes down, Twitter simply pushes out the version number of an older API version, which is still working correctly. Our systems will then automatically fall back to using that older version, until Twitter again pushes out the new version number when it's back online. Dewald -- Abraham Williams | Awesome Lists | http://bit.ly/sprout608 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 Bloomington, IN, United States
[twitter-dev] Trying to balance followers/ following/ seeking business development contact at Twitter
Hello: I know Twitter has rules about how many people an account is allowed to follow vs. followers. However, I've been getting more people to follow me, yet I can follow more people at this time. Is it possible for someone from the development team to take a quick look at my account and see if I'm doing something wrong? my handle is @steve8004. Can you link two twitter accounts together or will be able to do so in the future? I'm also interested in talking with a business development contact at Twitter regarding some new revenue generating opportunities. If you can tell me where to send some information or make a virtual introduction, I would really appreciate it. Sincerely, Steve Eisenberg Media Resource Networks
Re: [twitter-dev] Re: Questions about opening the firehose
For one thing, I do a lot of location-based processing. I'm quite interested in what's happening in Portland, Oregon, and not so much about the rest of the world. As far as I can tell, there's no geocode parameter for filter. In addition, I can do a search back in time with Twitter search - with filter, if I don't know what I'm looking for, it's going to go right by me. ;-) the geo-hose will be eventually available to help specifically with this feature - http://www.slideshare.net/raffikrikorian/whats-happening-here. -- Raffi Krikorian Twitter Platform Team http://twitter.com/raffi
[twitter-dev] Re: Questions about opening the firehose
Excellent! That's exactly what I need! If something gets past the filter, I can always backsearch for it. On Dec 17, 9:19 pm, Raffi Krikorian ra...@twitter.com wrote: For one thing, I do a lot of location-based processing. I'm quite interested in what's happening in Portland, Oregon, and not so much about the rest of the world. As far as I can tell, there's no geocode parameter for filter. In addition, I can do a search back in time with Twitter search - with filter, if I don't know what I'm looking for, it's going to go right by me. ;-) the geo-hose will be eventually available to help specifically with this feature -http://www.slideshare.net/raffikrikorian/whats-happening-here. -- Raffi Krikorian Twitter Platform Teamhttp://twitter.com/raffi
[twitter-dev] Regarding the search API based on Geo location
Hai, I was using search API to get tweets from Twitter. When i append geo code to the URL i got following error like this URL : http://search.twitter.com/search.json?q=%22holiday+list.+Pick+me%21%22phrase=rpp=100page=10geocode=36.778261%2C-119.4179324%2C500.0km .TwitterException: *Server returned HTTP response code: 502 for URL*: http://search.twitter.com/search.json?q=%22holiday+list.+Pick+me%21%22phrase=rpp=100page=10geocode=36.778261%2C-119.4179324%2C500.0km at com.netelixir.api.twitterSrc.http.HttpClient.httpRequest(HttpClient.java:274) at com.netelixir.api.twitterSrc.http.HttpClient.get(HttpClient.java:189) at com.netelixir.api.twitterSrc.Twitter.get(Twitter.java:279) at com.netelixir.api.twitterSrc.Twitter.search(Twitter.java:1125) at com.netelixir.api.twitter.DumpTweetsData.run(DumpTweetsData.java:119) at java.lang.Thread.run(Thread.java:619) If i try to pull tweets without geo code then its working fine , What is the wrong in the sending url and why its coming like this? Is there any other way to get tweets by using geocode from Search API? please give me reply as early as possible. Thanks Praveen
[twitter-dev] Reg Fetch tweets by append GEO Code to URL from Search API
Hai, I was using search API to get tweets from Twitter. When i append geo code to the URL i got following error like this URL : http://search.twitter.com/search.json?q=%22holiday+list.+Pick+me%21%22phrase=rpp=100page=10geocode=36.778261%2C-119.4179324%2C500.0km .TwitterException: *Server returned HTTP response code: 502 for URL*: http://search.twitter.com/search.json?q=%22holiday+list.+Pick+me%21%22phrase=rpp=100page=10geocode=36.778261%2C-119.4179324%2C500.0km at com.netelixir.api.twitterSrc. http.HttpClient.httpRequest(HttpClient.java:274) at com.netelixir.api.twitterSrc.http.HttpClient.get(HttpClient.java:189) at com.netelixir.api.twitterSrc.Twitter.get(Twitter.java:279) at com.netelixir.api.twitterSrc.Twitter.search(Twitter.java:1125) at com.netelixir.api.twitter.DumpTweetsData.run(DumpTweetsData.java:119) at java.lang.Thread.run(Thread.java:619) If i try to pull tweets without geo code then its working fine , What is the wrong in the sending url and why its coming like this? Is there any other way to get tweets by using geocode from Search API? please give me reply as early as possible. Thanks Praveen
Re: [twitter-dev] Oauth using api.twitter.com vs twitter.com
Hey Shiplu, I've found that this works, until the user tries to sign out or sign up during the authorization; if this happens, they get a 404. If, however, twitter.com is used as the host: I think this happens due to cookie. People sign in twitter.com. not in api.twitter.com. When a user already signed in, the cookie's domain is twitter.com. Thanks for the suggestion. However, this is definitely url/host/routing related, not cookie related. (a) I can reproduce after clearing all cookies. (b) The cookie api.twitter.com sets has .twitter.com as its domain. (c) http://api.twitter.com/signup?oauth_token=removed yields a 404; http://twitter.com/signup?oauth_token=removed does not. (d) The issue is not that it doesn't remember the user, but rather that the sign out and sign up links on the oauth page are broken (lead to 404s). -josh
[twitter-dev] Replies on user timeline
I am working on a twitter site and wanted to know if it makes sense to include @replies in a user's timeline. There can be a lot of noise if I try to show the last 20 tweets of a celebrity for example and all the tweets are @replies that are only relevant to the replied user. Do most sites just filter out @replies to show statuses/tweets that make more sense? Thanks, Quy
Re: [twitter-dev] Oauth using api.twitter.com vs twitter.com
Hey Josh, Good to see I reached you, albeit not through the channel I'd anticipated. :) I really think the issue is quite simple; sorry I haven't expressed it clearly enough. If you look at the source of the http://(api.)?twitter.com/oauth/authorize page, you'll see that the sign up link is a relative url: a href=/signup?oauth_token=removedSign up and Join the Conversation!/a And http://api.twitter.com/signup?oauth_token=removed yields a 404 but http://twitter.com/signup?oauth_token=removed does not. So either (1) one is only supposed to use twitter.com for oauth/authorize, or (2) Twitter ought to be using an absolute url to point to http://twitter.com/signup, or (3) http://api.twitter.com/signup oughtn't be a 404, but a signup page. All the same goes, mutatis mutandis, for the sign out page. Hope that clarifies the issue a little. Oh, and by the way, thanks for the awesome library. :) -josh On Thu, Dec 17, 2009 at 3:16 PM, Josh Roesslein jroessl...@gmail.com wrote: Sorry left off the link to the issue. [1] http://github.com/joshthecoder/tweepy/issues#issue/8 Josh On Thu, Dec 17, 2009 at 2:15 PM, Josh Roesslein jroessl...@gmail.com wrote: Hey, Thanks for bringing this issue to my attention. I have opened an issue for it here [1]. I will look into this and see what I can do to help resolve it. Shiplu is probably on the right track about this being cookie related. Will post updates here and on the issue as I make progress. Thanks, Josh Roesslein Tweepy author On Thu, Dec 17, 2009 at 1:42 PM, shiplu shiplu@gmail.com wrote: On Fri, Dec 18, 2009 at 2:22 AM, Josh Bleecher Snyder joshar...@gmail.com wrote: Hi all, The tweepy twitter client uses api.twitter.com for the host for oauth calls: REQUEST_TOKEN_URL = 'http://api.twitter.com/oauth/request_token' AUTHORIZATION_URL = 'http://api.twitter.com/oauth/authorize' AUTHENTICATE_URL = 'http://api.twitter.com/oauth/authenticate' ACCESS_TOKEN_URL = 'http://api.twitter.com/oauth/access_token' I've found that this works, until the user tries to sign out or sign up during the authorization; if this happens, they get a 404. If, however, twitter.com is used as the host: I think this happens due to cookie. People sign in twitter.com. not in api.twitter.com. When a user already signed in, the cookie's domain is twitter.com. Now if you redirect to http://api.twitter.com/oauth/authorize, browser wont load the cookie as its from twitter.com. It'll try to find cookies from api.twitter.com. But there is no cookie. So you have to sign in again I guess. Its better to use twitter.com instead of api.twitter.com when its one of those 4 oauth urls. -- Shiplu Mokaddim My talks, http://talk.cmyweb.net Follow me, http://twitter.com/shiplu SUST Programmers, http://groups.google.com/group/p2psust Innovation distinguishes bet ... ... (ask Steve Jobs the rest)
[twitter-dev] Re: Twitter Search cache or delayed data?
I'm checking out a tutorial I found for the stream API (having not worked with JSON much) and am getting an error. fgets(): supplied argument is not a valid stream resource This is happening when I run it locally under WAMP as a test and also on a live production server (Media Temple). Any ideas? The tutorial I found is here: http://hasin.wordpress.com/2009/06/20/collecting-data-from-streaming-api-in-twitter/ Thanks. Hopefully I'm getting closer to a better data collector :)
[twitter-dev] Re: Retweet API methods returning 404
Personally, my unit's testes don't call the Twitter API ... were you expecting them to? those would be some really amazing balls On Dec 17, 4:07 am, Andrew Badera and...@badera.us wrote: Personally, my unit's testes don't call the Twitter API ... Seeing the same 404s on retweet calls however. ∞ 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%20baderaOn Thu, Dec 17, 2009 at 7:05 AM, Dimebrain daniel.cre...@gmail.com wrote: The following retweet methods have started returning 404's in our unit testes: http://api.twitter.com/1/statuses/retweeted_by_me.json http://api.twitter.com/1/statuses/retweeted_to_me.json http://api.twitter.com/1/statuses/retweets_of_me.json http://api.twitter.com/1/statuses/retweets/[any_status_id].json Anyone else having this issue, or know what happened to these API methods?
Re: [twitter-dev] Re: Getting retweets in user timelines
As of today, I've noticed that retweets created via the new system are represented in user timelines as RT @username...--are others seeing this, and is this something new? Is this leftovers from the old to new retweeting transition, or is this going to be a permanent method for representing built-in tweets in the user timeline? I just checked it on a known newRT-crazy user, and I'm not seeing any newRTs in his user_timeline. -- personal: http://www.cameronkaiser.com/ -- Cameron Kaiser * Floodgap Systems * www.floodgap.com * ckai...@floodgap.com -- People are weird. -- Law Order SVU ---
[twitter-dev] Status update 11:27pm PDT
Just wanted to drop an email to everyone and let you know that we are investigating the issue and will follow up with more details as we determine the cause and are able to share information. Thanks for your patience, Ryan
Re: [twitter-dev] Re: URLification
Although not an API issue, it might be good to track it as such, because Twitter clients can then follow exactly the same policies that Twitter web interface does. If there is a standard regular expression that can be used for detecting a URL, it could be published as a guideline in the API documentation for consistency between all clients. cheers, Harshad On Fri, Dec 18, 2009 at 2:45 AM, Raffi Krikorian ra...@twitter.com wrote: its not an API issue -- the API doesn't do any auto-URLification. however, i'll pass this thread off to the web client team. On Thu, Dec 17, 2009 at 1:13 PM, dbasch dba...@gmail.com wrote: I agree. I searched the issues db and didn't find it. Not sure if it belongs as an API issue but I submitted it anyway. http://code.google.com/p/twitter-api/issues/detail?id=1298 -- Harshad RJ http://hrj.wikidot.com
