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. On Dec 11, 4:18 pm, Cameron Kaiser <[email protected]> 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. > > -- > ------------------------------------ personal:http://www.cameronkaiser.com/-- > Cameron Kaiser * Floodgap Systems *www.floodgap.com* [email protected] > -- I went to San Francisco. I found someone's heart. Now what? > ----------------
