Re: Incomplete list of friends being returned
It's possible that the missing users are suspended users. It seems that this issue has not been completely resolved, and a user might show in a member's friends even though they are suspended, and be fixed with the API. -Greg On Wed, Dec 10, 2008 at 5:15 PM, DustyReagan [EMAIL PROTECTED] wrote: I often see message's like this in summize: bobke: Mr. Tweet, FriendorFollow and Twitter Karma don't work. All 3 have bad information. Has anyone else tried them? As far as I can tell it's due to the API data having inconsistencies. *shrug* On Dec 10, 5:02 pm, DustyReagan [EMAIL PROTECTED] wrote: I've noticed the same sorta' thing. Getting a user's list of followers and followings has been really flaky. Would love for it to be more reliable. Dusty On Dec 10, 3:46 pm, Carter Rabasa [EMAIL PROTECTED] wrote: I doubt it, because I am authenticating with the user's credentials. You'd think the authenticated user would get a complete list of their friends. On Dec 10, 3:32 pm, Brian Gilham [EMAIL PROTECTED] wrote: Perhaps it is not returning protected users? -Original Message- From: Carter Rabasa [EMAIL PROTECTED] Date: Wed, 10 Dec 2008 13:27:57 To: Twitter Development Talktwitter-development-talk@googlegroups.com Subject: Incomplete list of friends being returned I am currently developing an application to bridge Twitter and FriendFeed (http://twitter2ff.appspot.com) and I am having a problem retrieving a complete list of a user's friends. For example, using the command-line (curl), I retrieved all the friends for davewiner. His profile (http://twitter.com/davewiner) indicates he has 741 friends. When I count the number of screen_names returned (over 8 pages of results) I only see 733 friends. I've double-checked this with several other public accounts. Any ideas? Thanks, Carter Rabasa -- [EMAIL PROTECTED] 920.941.0399
Re: Change to Twitter API?
I am having problems with My Tweeple as well.
Re: direct_messages new NOT working
Try grabbing the HTTP request and response with a debugging proxy like
Charles. That will let us know what's really being sent and received.
--
Ed Finkler
http://funkatron.com
AIM: funka7ron
ICQ: 3922133
Skype: funka7ron
On Thu, Dec 11, 2008 at 1:14 AM, sMan [EMAIL PROTECTED] wrote:
Oops, sorry for the lack of detail. Here is the body of the
postTwitter method (as i said, I'm able to post to other twitter URLs
within the API with this same piece of code):
def postTwitter(url, hashParams)
url = URI.parse(url)
req = Net::HTTP::Post.new(url.path)
req.basic_auth($username, $password)
req.set_form_data(hashParams, ';')
res = Net::HTTP.new($twitter, $twitPort).start {|http| http.request
(req) }
puts res
case res
when Net::HTTPSuccess, Net::HTTPRedirection
return 'true'
else
return 'false'
end
end
On Dec 10, 5:00 pm, Alex Payne [EMAIL PROTECTED] wrote:
If you provide the full request/response output from your call to the
method, I'm sure somewhat can tell you what's going on. Thanks!
On Wed, Dec 10, 2008 at 16:36, sMan [EMAIL PROTECTED] wrote:
Hi guys, I just started kicking the tires on the API (thanks, btw!)
and am having a horrendous time posting to /direct_messages/new.xml.
The response that comes back is invalid request which doesn't give
me much to debug or go off of. I am able to post to the udpate/status
urls just fine so I dont think its my code. here is how I'm doing the
post in Ruby:
postTwitter(http://twitter.com/direct_messages/new.xml;, {text =
'this is a test', user = 'saumil})
postTwitter is my wrapper method to execute the http request and works
for other urls, just not this one.
Thanks!
--S
--
Alex Payne - API Lead, Twitter, Inc.http://twitter.com/al3x
Re: Incomplete list of friends being returned
I second Greg's problem, I was having this problem too, but after looking through all my users, 4 were suspended and thus didn't show up in the API.
Re: weird case: user returns blank json for users/show but works for xml
Did you just create your account? It seems that Twitter has been having some user problems and all the data is cached from 24 hours ago. It might be that the xml file updated but not the json yet? Also, I have tried a few other usernames and they all seem to return fine.
Re: Incomplete list of friends being returned
You can fix this by reviewing each of the users - if you try to do anything with the user it returns a message saying the account is suspended. It's a pain in the neck to deal with though, and a waste of bandwidth to return those people. Suspended accounts shouldn't appear in the list of friends anywhere. It has been a headache for me as well. On Thu, Dec 11, 2008 at 8:17 AM, fastest963 [EMAIL PROTECTED] wrote: I second Greg's problem, I was having this problem too, but after looking through all my users, 4 were suspended and thus didn't show up in the API.
verify_credentials response changed
It used to be that calling http://twitter.com/account/verify_credentials.xml would return a simple authorizedtrue/authorized answer when given a correct username and password. Now it appears to be returning an entire serialized user object. This change has broken the authentication process for the existing releases of my application. Is this change permanent, or is it a temporary glitch?
Re: verify_credentials response changed
Permanent. See posts on the list about a week ago, and issue in tracker. -- Ed Finkler http://funkatron.com AIM: funka7ron ICQ: 3922133 Skype: funka7ron On Dec 11, 11:20 am, JakeS [EMAIL PROTECTED] wrote: It used to be that callinghttp://twitter.com/account/verify_credentials.xml would return a simple authorizedtrue/authorized answer when given a correct username and password. Now it appears to be returning an entire serialized user object. This change has broken the authentication process for the existing releases of my application. Is this change permanent, or is it a temporary glitch?
Re: verify_credentials response changed
On 11 Dec 2008, at 16:20, JakeS wrote: It used to be that calling http://twitter.com/account/verify_credentials.xml would return a simple authorizedtrue/authorized answer when given a correct username and password. Now it appears to be returning an entire serialized user object. This change has broken the authentication process for the existing releases of my application. Is this change permanent, or is it a temporary glitch? Plenty of notice was given for this change... http://groups.google.com/group/twitter-development-talk/browse_thread/thread/fd3a63597f6d0d3c -Stut -- http://stut.net/
Re: verify_credentials response changed
On 11 Dec 2008, at 16:32, JakeS wrote: Really, I don't get emails from this group because it's often full of people's questions that do not relate to me. Is there a better way we can be notified of API changes without all the extra conversation from the group? I believe API changes will be announced by @twitterapi but I dunno if they'll be mentioned with any meaningful notice period there. Your best bet is to get a daily digest of the emails to this list and scan through them every day. -Stut -- http://stut.net/ On Dec 11, 10:30 am, Stut [EMAIL PROTECTED] wrote: On 11 Dec 2008, at 16:20, JakeS wrote: It used to be that callinghttp://twitter.com/account/verify_credentials.xml would return a simple authorizedtrue/authorized answer when given a correct username and password. Now it appears to be returning an entire serialized user object. This change has broken the authentication process for the existing releases of my application. Is this change permanent, or is it a temporary glitch? Plenty of notice was given for this change... http://groups.google.com/group/twitter-development-talk/ browse_thread... -Stut --http://stut.net/
Re: verify_credentials response changed
I do hope you'll continue to use @twitterapi and give us fair warning there. While appreciate the google groups as a resource, I am concerned it's not the best means of communicating breaking API changes to the large number of third-party developers out there. Thank you for your help. On Dec 11, 10:40 am, Matt Sanford [EMAIL PROTECTED] wrote: Hi Jake, For only change announcements and things form the API team check out the twitter users @twitterapi (http://twitter.com/twitterapi). We've had it for some time but just started making updates to it a priority. You may also want to follow @twitter for outage announcements. Thanks; — Matt Sanford On Dec 11, 2008, at 08:32 AM, JakeS wrote: Really, I don't get emails from this group because it's often full of people's questions that do not relate to me. Is there a better way we can be notified of API changes without all the extra conversation from the group? On Dec 11, 10:30 am, Stut [EMAIL PROTECTED] wrote: On 11 Dec 2008, at 16:20, JakeS wrote: It used to be that callinghttp://twitter.com/account/verify_credentials.xml would return a simple authorizedtrue/authorized answer when given a correct username and password. Now it appears to be returning an entire serialized user object. This change has broken the authentication process for the existing releases of my application. Is this change permanent, or is it a temporary glitch? Plenty of notice was given for this change... http://groups.google.com/group/twitter-development-talk/ browse_thread... -Stut --http://stut.net/
Re: verify_credentials response changed
We'll try to find other avenues for communicating these changes. On Thu, Dec 11, 2008 at 08:47, JakeS [EMAIL PROTECTED] wrote: I do hope you'll continue to use @twitterapi and give us fair warning there. While appreciate the google groups as a resource, I am concerned it's not the best means of communicating breaking API changes to the large number of third-party developers out there. Thank you for your help. On Dec 11, 10:40 am, Matt Sanford [EMAIL PROTECTED] wrote: Hi Jake, For only change announcements and things form the API team check out the twitter users @twitterapi (http://twitter.com/twitterapi). We've had it for some time but just started making updates to it a priority. You may also want to follow @twitter for outage announcements. Thanks; — Matt Sanford On Dec 11, 2008, at 08:32 AM, JakeS wrote: Really, I don't get emails from this group because it's often full of people's questions that do not relate to me. Is there a better way we can be notified of API changes without all the extra conversation from the group? On Dec 11, 10:30 am, Stut [EMAIL PROTECTED] wrote: On 11 Dec 2008, at 16:20, JakeS wrote: It used to be that callinghttp://twitter.com/account/verify_credentials.xml would return a simple authorizedtrue/authorized answer when given a correct username and password. Now it appears to be returning an entire serialized user object. This change has broken the authentication process for the existing releases of my application. Is this change permanent, or is it a temporary glitch? Plenty of notice was given for this change... http://groups.google.com/group/twitter-development-talk/ browse_thread... -Stut --http://stut.net/ -- Alex Payne - API Lead, Twitter, Inc. http://twitter.com/al3x
Re: Change to Twitter API?
We've got a fix for it in the works. On Thu, Dec 11, 2008 at 07:16, itcn [EMAIL PROTECTED] wrote: I think this should be evelated to bug status -- I've been seeing this for 3 days now. Sometimes http://twitter.com/users/show/(screen_name).xml shows full info, but most of the time it doesn't. Very erratic behavior. On Dec 11, 9:50 am, Shannon Whitley [EMAIL PROTECTED] wrote: I am having problems with My Tweeple as well. -- Alex Payne - API Lead, Twitter, Inc. http://twitter.com/al3x
Re: Testing URL
We'd like to provide something like this. Please file an enhancement request: http://code.google.com/p/twitter-api/issues/entry. On Wed, Dec 10, 2008 at 21:17, Hamish Campbell [EMAIL PROTECTED] wrote: Hi all, Perhaps this already exists, but if not it would be great: a URL or flag for API testing. Eg, all requests to this service would process the queries for only for validity of the message (and ignore whether the status/user/ favorite etc exists) and return an sample dataset as would be expected of a successful request. Malformed requests would return the expected failure notice, and perhaps a 'return false' flag could be added to tell the api to send the relevant negative response for a particular request. Since it would have no effect on any actual data, it would not need to be rate limited (or at least the rate could be extremely high and only by I.P.). This would be great for unit testing. At the moment it's difficult to create a testing framework that works reliably. Especially if you want other people to be able to run the tests, but not see your twitter password :P. For example, you have to generate a random status message to avoid the 'ignore repeated messages' issue, and create and destroy friendships and notifications that you've manually set up. It's not a biggie, but would be a very useful developer tool. Thanks! -- Alex Payne - API Lead, Twitter, Inc. http://twitter.com/al3x
Re: Incomplete list of friends being returned
I've had the exact same problem. The difference was somewhere in the ballpack of 20%. On Dec 11, 10:17 am, fastest963 fastest...@gmail.com wrote: I second Greg's problem, I was having this problem too, but after looking through all my users, 4 were suspended and thus didn't show up in the API.
API Versioning?
The Twitter ecosystem has grown quite a bit, and a lot of users are relying on the API (and third party software) nowadays. Small API changes can break these applications, and could possibly affect thousands of Twitter users. I understand that the API will need to evolve - but can you please consider a versioning policy similar to: http://www.google.com/support/adwordsapi/bin/answer.py?answer=33152topic=8400 Thanks.
Re: API Versioning?
That would be awesome! Our entire Twitter-based website and application has been dead in the water since the API was changed abruptly 3 days ago and stopped supporting users/show XML requests. It was working fine before Tuesday; had we had some advance notice that the Twitter API would no longer support XML we could have switched to JSON or found another solution. On Dec 11, 3:05 pm, Alex aybarb...@gmail.com wrote: The Twitter ecosystem has grown quite a bit, and a lot of users are relying on the API (and third party software) nowadays. Small API changes can break these applications, and could possibly affect thousands of Twitter users. I understand that the API will need to evolve - but can you please consider a versioning policy similar to:http://www.google.com/support/adwordsapi/bin/answer.py?answer=33152t... Thanks.
Re: API Versioning?
That would be awesome! Our entire Twitter-based website and application has been dead in the water since the API was changed abruptly 3 days ago and stopped supporting users/show XML requests. It was working fine before Tuesday; had we had some advance notice that the Twitter API would no longer support XML we could have ^^^ switched to JSON or found another solution. Uh, how do you figure that? -- personal: http://www.cameronkaiser.com/ -- Cameron Kaiser * Floodgap Systems * www.floodgap.com * ckai...@floodgap.com -- Life's tough. It's tougher if you're stupid. -- John Wayne -
Re: Status updates ignored, even though statuses not identical?
Just to clarify, here is an example of the request we are sending and
the json that's returned:
REQUEST
http://twitter.com/statuses/update.json?status=%40sixuntilme%2C+you+were+nominated+by+%40jakerutter+for+a+%23personal+Shorty+Award+http%3A%2F%2Fbit.ly%2FLAIv
STATUS CODE
200
RETURNED
data={in_reply_to_user_id:11676742,truncated:false,text:@HughBriss,
you were nominated by @AgingBackwards (and 5 others) for a #design
Shorty Award http:\/\/bit.ly\/SMcZ,user:{description:The best
short content creators on twitter in
2008,url:http:\/\/shortyawards.com,name:Shorty
Awards,protected:false,profile_image_url:http:\/\/s3.amazonaws.com\/twitter_production\/profile_images\/66792558\/logo_normal.png,screen_name:shortyawards,followers_count:750,location:,id:17663756},in_reply_to_screen_name:HughBriss,favorited:false,created_at:Thu
Dec 11 16:20:11 +
2008,in_reply_to_status_id:1051493141,id:1051503605,source:web}
In the JSON, the 'text' field is a status from 2 hours ago. It
completely ignored the update.
How Do I Replace from web with from MySite.com?
I have the API working just fine, messages are posting from my web site no problem.. but I'd like to replace from web with from MySite.com like Appcelerator is doing with their new desktop twitter client. Any suggestions of what is required here much appreciated - I tried searching for a solution on the Twitter API site but the word from is too common to return any results.
Re: How Do I Replace from web with from MySite.com?
I have the API working just fine, messages are posting from my web site no problem.. but I'd like to replace from web with from MySite.com like Appcelerator is doing with their new desktop twitter client. Any suggestions of what is required here much appreciated - I tried searching for a solution on the Twitter API site but the word from is too common to return any results. http://twitter.com/help/request_source -- personal: http://www.cameronkaiser.com/ -- Cameron Kaiser * Floodgap Systems * www.floodgap.com * ckai...@floodgap.com -- It is the business of the future to be dangerous. -- Hawkwind --
Status updates ignored, even though statuses not identical?
I have a twitter bot running at http://twitter.com/shortyawards for the site http://shortyawards.com. I'm noticing in our logs that many of our status updates using the json API are being ignored. The 'text' field of the json response comes back with the previous status, ignoring the new status message, but no error code or message is being returned. This problem seems to come and go at different times of the day. Has anyone ever experienced this? Is this due to the rate of status updates, or is there a bug in the API? Our account has already been whitelisted so this is not due to the API rate limit.
Re: Testing URL
Something close to a sandbox? Sounds cool. On Dec 11, 10:17 am, Hamish Campbell hn.campb...@gmail.com wrote: Hi all, Perhaps this already exists, but if not it would be great: a URL or flag for API testing. Eg, all requests to this service would process the queries for only for validity of the message (and ignore whether the status/user/ favorite etc exists) and return an sample dataset as would be expected of a successful request. Malformed requests would return the expected failure notice, and perhaps a 'return false' flag could be added to tell the api to send the relevant negative response for a particular request. Since it would have no effect on any actual data, it would not need to be rate limited (or at least the rate could be extremely high and only by I.P.). This would be great for unit testing. At the moment it's difficult to create a testing framework that works reliably. Especially if you want other people to be able to run the tests, but not see your twitter password :P. For example, you have to generate a random status message to avoid the 'ignore repeated messages' issue, and create and destroy friendships and notifications that you've manually set up. It's not a biggie, but would be a very useful developer tool. Thanks!
Re: verify_credentials response changed
yes, follow the api bot @twitterapi On Dec 11, 9:32 pm, JakeS jakesteven...@gmail.com wrote: Really, I don't get emails from this group because it's often full of people's questions that do not relate to me. Is there a better way we can be notified of API changes without all the extra conversation from the group? On Dec 11, 10:30 am, Stut stut...@gmail.com wrote: On 11 Dec 2008, at 16:20, JakeS wrote: It used to be that callinghttp://twitter.com/account/verify_credentials.xml would return a simple authorizedtrue/authorized answer when given a correct username and password. Now it appears to be returning an entire serialized user object. This change has broken the authentication process for the existing releases of my application. Is this change permanent, or is it a temporary glitch? Plenty of notice was given for this change... http://groups.google.com/group/twitter-development-talk/browse_thread... -Stut --http://stut.net/
Re: Status updates ignored, even though statuses not identical?
You're not the first to report this issue, I'm afraid. This crops up
from time to time due to some low-level, complicated caching logic in
our system. We're constantly ironing out this code, but I'll
double-check the update method and see if there's any glaring issues
there.
On Thu, Dec 11, 2008 at 10:05, Lee Semel lse...@gmail.com wrote:
Just to clarify, here is an example of the request we are sending and
the json that's returned:
REQUEST
http://twitter.com/statuses/update.json?status=%40sixuntilme%2C+you+were+nominated+by+%40jakerutter+for+a+%23personal+Shorty+Award+http%3A%2F%2Fbit.ly%2FLAIv
STATUS CODE
200
RETURNED
data={in_reply_to_user_id:11676742,truncated:false,text:@HughBriss,
you were nominated by @AgingBackwards (and 5 others) for a #design
Shorty Award http:\/\/bit.ly\/SMcZ,user:{description:The best
short content creators on twitter in
2008,url:http:\/\/shortyawards.com,name:Shorty
Awards,protected:false,profile_image_url:http:\/\/s3.amazonaws.com\/twitter_production\/profile_images\/66792558\/logo_normal.png,screen_name:shortyawards,followers_count:750,location:,id:17663756},in_reply_to_screen_name:HughBriss,favorited:false,created_at:Thu
Dec 11 16:20:11 +
2008,in_reply_to_status_id:1051493141,id:1051503605,source:web}
In the JSON, the 'text' field is a status from 2 hours ago. It
completely ignored the update.
--
Alex Payne - API Lead, Twitter, Inc.
http://twitter.com/al3x
Re: API Versioning?
That makes sense. In the mean time, can you give us some kind of heads up (ideally a couple days warning or something) if you are planning to make a change that could, as soon as it goes live, break an app? So we can try to be ready for it when you flip the switch :) Thanks. Appreciate all that you're doing. Alex On Dec 11, 3:34 pm, Alex Payne a...@twitter.com wrote: Versioning is a major part of the design of the next version of the Twitter API (a rewrite, essentially). We know it's been long since missing from the API, and we're eager to fix that. Making life hard for developers definitely isn't our goal. On Thu, Dec 11, 2008 at 12:05, Alex aybarb...@gmail.com wrote: The Twitter ecosystem has grown quite a bit, and a lot of users are relying on the API (and third party software) nowadays. Small API changes can break these applications, and could possibly affect thousands of Twitter users. I understand that the API will need to evolve - but can you please consider a versioning policy similar to: http://www.google.com/support/adwordsapi/bin/answer.py?answer=33152t... Thanks. -- Alex Payne - API Lead, Twitter, Inc.http://twitter.com/al3x
Re: API Versioning?
In the mean time, can you give us some kind of heads up (ideally a couple days warning or something) if you are planning to make a change that could, as soon as it goes live, break an app? So we can try to be ready for it when you flip the switch :) But they *do* do this. Stuff slips through, but the API staff has been trying to keep ahead of future compatibility breaks, even with aggressive subject lines line INCOMPATIBILITY WARNING: x, at least from my third-party I-don't-work-for-Twitter perspective. -- personal: http://www.cameronkaiser.com/ -- Cameron Kaiser * Floodgap Systems * www.floodgap.com * ckai...@floodgap.com -- I went to San Francisco. I found someone's heart. Now what?
Re: API Versioning?
Sure can. In fact, we gave people nine days notice for the change to the response body of /account/verify_credentials. But I don't predict any more changes of this sort to the API in this version, looking at our list of outstanding issue requests. On Thu, Dec 11, 2008 at 13:14, Alex aybarb...@gmail.com wrote: That makes sense. In the mean time, can you give us some kind of heads up (ideally a couple days warning or something) if you are planning to make a change that could, as soon as it goes live, break an app? So we can try to be ready for it when you flip the switch :) Thanks. Appreciate all that you're doing. Alex On Dec 11, 3:34 pm, Alex Payne a...@twitter.com wrote: Versioning is a major part of the design of the next version of the Twitter API (a rewrite, essentially). We know it's been long since missing from the API, and we're eager to fix that. Making life hard for developers definitely isn't our goal. On Thu, Dec 11, 2008 at 12:05, Alex aybarb...@gmail.com wrote: The Twitter ecosystem has grown quite a bit, and a lot of users are relying on the API (and third party software) nowadays. Small API changes can break these applications, and could possibly affect thousands of Twitter users. I understand that the API will need to evolve - but can you please consider a versioning policy similar to: http://www.google.com/support/adwordsapi/bin/answer.py?answer=33152t... Thanks. -- Alex Payne - API Lead, Twitter, Inc.http://twitter.com/al3x -- Alex Payne - API Lead, Twitter, Inc. http://twitter.com/al3x
Re: API Versioning?
In the mean time, can you give us some kind of heads up (ideally a couple days warning or something) if you are planning to make a change that could, as soon as it goes live, break an app? _So we can try to be ready for it when you flip the switch :) But they *do* do this. Stuff slips through, but the API staff has been trying to keep ahead of future compatibility breaks, even with aggressive subject lines line INCOMPATIBILITY WARNING: x, at least from my third-party I-don't-work-for-Twitter perspective. Cameron, this has already been mentioned in several other threads, but compare a couple of XML results: http://twitter.com/users/show/id.xml http://twitter.com/users/show/twitterapi.xml You'll see the behavior is erratic and we can't get consistent results for any ids; the entire XML version of the API seems to have crashed over the past couple days. Did you also see Alex's replies where they're working on it? -- personal: http://www.cameronkaiser.com/ -- Cameron Kaiser * Floodgap Systems * www.floodgap.com * ckai...@floodgap.com -- Spotted on a coffee mug: Say NO to drugs -- Chuck Reiman, r.h.f --
Re: API Versioning?
Yes I did, that's why I wish you would have read the other threads where it was mentioned before questioning me on it. On Dec 11, 4:30 pm, Cameron Kaiser spec...@floodgap.com wrote: In the mean time, can you give us some kind of heads up (ideally a couple days warning or something) if you are planning to make a change that could, as soon as it goes live, break an app? _So we can try to be ready for it when you flip the switch :) But they *do* do this. Stuff slips through, but the API staff has been trying to keep ahead of future compatibility breaks, even with aggressive subject lines line INCOMPATIBILITY WARNING: x, at least from my third-party I-don't-work-for-Twitter perspective. Cameron, this has already been mentioned in several other threads, but compare a couple of XML results: http://twitter.com/users/show/id.xml http://twitter.com/users/show/twitterapi.xml You'll see the behavior is erratic and we can't get consistent results for any ids; the entire XML version of the API seems to have crashed over the past couple days. Did you also see Alex's replies where they're working on it? -- personal:http://www.cameronkaiser.com/-- Cameron Kaiser * Floodgap Systems *www.floodgap.com* ckai...@floodgap.com -- Spotted on a coffee mug: Say NO to drugs -- Chuck Reiman, r.h.f --- Hide quoted text - - Show quoted text -
Re: API Versioning?
To lighten the mood Twitter can you give us at least 48 hours notice before new bugs are created so we know what unexpected responses to expect? KTHXBI! On Thu, Dec 11, 2008 at 15:30, Cameron Kaiser spec...@floodgap.com wrote: In the mean time, can you give us some kind of heads up (ideally a couple days warning or something) if you are planning to make a change that could, as soon as it goes live, break an app? _So we can try to be ready for it when you flip the switch :) But they *do* do this. Stuff slips through, but the API staff has been trying to keep ahead of future compatibility breaks, even with aggressive subject lines line INCOMPATIBILITY WARNING: x, at least from my third-party I-don't-work-for-Twitter perspective. Cameron, this has already been mentioned in several other threads, but compare a couple of XML results: http://twitter.com/users/show/id.xml http://twitter.com/users/show/twitterapi.xml You'll see the behavior is erratic and we can't get consistent results for any ids; the entire XML version of the API seems to have crashed over the past couple days. Did you also see Alex's replies where they're working on it? -- personal: http://www.cameronkaiser.com/ -- Cameron Kaiser * Floodgap Systems * www.floodgap.com * ckai...@floodgap.com -- Spotted on a coffee mug: Say NO to drugs -- Chuck Reiman, r.h.f -- -- | Abraham Williams | Web Developer | http://abrah.am | Brazen Careerist | Pro Hacker | http://www.brazencareerist.com | PoseurTech LLC | Mashup Ambassador | http://poseurte.ch | Web608 | Community Evangelist | http://web608.org | This email is: [] blogable [x] ask first [] private
Re: API Versioning?
On 11 Dec 2008, at 21:56, itcn wrote: shrugs I love when people wander into a discussion without having read any of the history, ask a question specifically to start a fight, and then act like they're the hero for stopping the drama they started. kthxbai I love it when someone doesn't remember what they themselves have said. From your first message in this thread... Our entire Twitter-based website and application has been dead in the water since the API was changed abruptly 3 days ago and stopped supporting users/show XML requests. It was working fine before Tuesday; had we had some advance notice that the Twitter API would no longer support XML we could have switched to JSON or found another solution. Cameron was simply pointing out that the issue you called an API change is a bug, was not foreseeable and that the Twitter guys have acknowledged it and are working on a fix. Yet you continue to complain about it. And nobody has ever suggested that the Twitter API will stop supporting XML, you pulled that out of your ...! -Stut -- http://stut.net/ On Dec 11, 4:48 pm, Cameron Kaiser spec...@floodgap.com wrote: You'll see the behavior is erratic and we can't get consistent results for any ids; the entire XML version of the API seems to have crashed over the past couple days. Did you also see Alex's replies where they're working on it? Yes I did, that's why I wish you would have read the other threads where it was mentioned before questioning me on it. With all due respect, they're aware of the bug, they're fixing the bug, and you still want to complain about it. This is degenerating into noise, so yes, I'm not sure what the point of continuing to complain about it is. -- personal:http://www.cameronkaiser.com/-- Cameron Kaiser * Floodgap Systems *www.floodgap.com* ckai...@floodgap.com -- I'd love to go out with you, but I need to clean my toilet brush.
Re: API Versioning?
Calm it down or I will turn this thread around SO FAST ;) I think the discussion's over, all. On Thu, Dec 11, 2008 at 14:09, Stut stut...@gmail.com wrote: On 11 Dec 2008, at 21:56, itcn wrote: shrugs I love when people wander into a discussion without having read any of the history, ask a question specifically to start a fight, and then act like they're the hero for stopping the drama they started. kthxbai I love it when someone doesn't remember what they themselves have said. From your first message in this thread... Our entire Twitter-based website and application has been dead in the water since the API was changed abruptly 3 days ago and stopped supporting users/show XML requests. It was working fine before Tuesday; had we had some advance notice that the Twitter API would no longer support XML we could have switched to JSON or found another solution. Cameron was simply pointing out that the issue you called an API change is a bug, was not foreseeable and that the Twitter guys have acknowledged it and are working on a fix. Yet you continue to complain about it. And nobody has ever suggested that the Twitter API will stop supporting XML, you pulled that out of your ...! -Stut -- http://stut.net/ On Dec 11, 4:48 pm, Cameron Kaiser spec...@floodgap.com wrote: You'll see the behavior is erratic and we can't get consistent results for any ids; the entire XML version of the API seems to have crashed over the past couple days. Did you also see Alex's replies where they're working on it? Yes I did, that's why I wish you would have read the other threads where it was mentioned before questioning me on it. With all due respect, they're aware of the bug, they're fixing the bug, and you still want to complain about it. This is degenerating into noise, so yes, I'm not sure what the point of continuing to complain about it is. -- personal:http://www.cameronkaiser.com/-- Cameron Kaiser * Floodgap Systems *www.floodgap.com* ckai...@floodgap.com -- I'd love to go out with you, but I need to clean my toilet brush. -- Alex Payne - API Lead, Twitter, Inc. http://twitter.com/al3x
Re: Fixes deployed Nov 14th
Looks like this is fixed. I just did an unauthenticated /users/show on a protected user and I got all 4 counts and the created_at: followers_count36/followers_count friends_count67/friends_count created_atSat Mar 10 21:53:19 + 2007/created_at favourites_count2/favourites_count statuses_count345/statuses_count Sweet. Thanks guys! -damon On Mon, Nov 24, 2008 at 3:36 PM, Damon Clinkscales sca...@pobox.com wrote: Btw everybody, I've just added an issue for the issue describe in this thread from last week. Essentially, /users/show on protected profiles should also include friends_count (or following_count). It already includes followers_count. http://code.google.com/p/twitter-api/issues/detail?id=167
API Updates for December 11, 2008
Feature: new API method /account/update_profile to update name, location, email, url, description attributes. Fix: /users/show should now return all attributes of a user object in XML. Fix: /statuses/replies should return fresher data in the case that a user that you do not follow has replied to you. See http://apiwiki.twitter.com/REST+API+Documentation#AccountMethods for details on the new method. -- Alex Payne - API Lead, Twitter, Inc. http://twitter.com/al3x
Re: simple tweet this implementation
Hi. I guess this feature was added a week ago. Thanks! I'm having a bit of trouble with it though. I tried the url http://twitter.com/home?status=testsource=isitfunnytodaycom (my source paramter was approved over 48 hours ago) and my post is still 'from web'. I also tried using the source parameter twitterific, which also showed up as 'from web'. Is feature not deployed yet? On Nov 21, 5:01 pm, scottjgo scott...@gmail.com wrote: http://code.google.com/p/twitter-api/issues/detail?id=163 On Nov 21, 2:51 pm, Alex Payne a...@twitter.com wrote: We recently had another request to allow messages posted from the web to define their own source parameters. We'll consider it. Please file an issue athttp://code.google.com/p/twitter-api/issues/entry. On Fri, Nov 21, 2008 at 01:36, scottjgo scott...@gmail.com wrote: Bummer. I don't suppose you'd be willing to add a simple appid= or something to the url that lets you modify the posted from link (given that the link was already approved for your app id)? On Nov 20, 5:03 pm, Alex Payne a...@twitter.com wrote: Yes, you'll need to make a proper API request to have your update attributed. -- Alex Payne On Nov 20, 2008, at 10:05, scottjgo scott...@gmail.com wrote: Hi. I want to add a tweet this link to my website. The idea is that you would click the button, and it would prepopulate the message field on twitter with a link. Ideally, you would authenticate through twitter.com so I can avoid handling passwords. I understand you can use a link like:http://twitter.com/home?status=Putyourmessagehere but is it possible to replace the from web with a link to my website? Without that, it sort of eliminates the cool viral advertising. Is the only alternative to use the real api (and handle passwords)? Thanks. -sjg -- Alex Payne - API Lead, Twitter, Inc.http://twitter.com/al3x
