Thanks for the heads up and info on v2 Doug. Let me check again because
as of last night I was also seeing the "notifications" tag missing.
Josh
Doug Williams wrote:
Joshua,
I'm getting the followers element for both xml and json data. That
method is supposed to return the following element so if you are still
seeing this problem, please reply here and create a new issue to track
the defect.
Also, we know variability causes headaches and we are working towards
uniformity. It makes developing for and maintaining the API
challenging. Twitter is growing up fast and what is being learned now
will make it's way into future releases, like the v2 milestone on the
horizon.
Doug Williams
Twitter API Support
http://twitter.com/dougw
On Thu, Mar 19, 2009 at 4:08 PM, Joshua Perry <j...@6bit.com
<mailto:j...@6bit.com>> wrote:
I started getting errors in my client when retrieving extended user
information using the verify_credentials method. Suddenly the
<following>false</following> no longer appears in the returned
dataset.
Is this tag not being included any longer?
I know schemas are not RESTy but it is really annoying to have 13
different datasets and not know when to expect an element or not. An
actual schema would tell us if an element is optional (can be
missing/null).
I also know it is kind of silly for the data to tell me if I'm
following
myself, but I would rather have 3 or 4 uniform datasets than a mess of
sets of data.
Another place where this is kind of annoying is the status tag
under the
user info, the "schema" on the API site says that status will include
user info in the user element, but that tag is missing, I know it is
redundant in this situation since the status is IN the user but is
another discontinuity.
For uniformity I would prefer user and status to be siblings in the
responses...
