POSTs to :user/:list_id/create_all returning HTTP status 404 for all requests

[sferik]

This was reported as an issue in the twitter gem. Upon investigation, it appears to be a bug in the Twitter API.

[Taylor Singletary]

It's a documentation error at the moment, the proper path is: POST :user/:list_id/members/create_all

@episod - Taylor Singletary - Twitter Developer Advocate

On Mon, Feb 28, 2011 at 7:42 AM, sferik <sfe...@gmail.com> wrote:

This was reported as an issue in the twitter gem. Upon investigation, it appears to be a bug in the Twitter API.

--
Twitter developer documentation and resources: http://dev.twitter.com/doc
API updates via Twitter: http://twitter.com/twitterapi
Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list
Change your membership to this group: http://groups.google.com/group/twitter-development-talk

[sferik]

On Monday, February 28, 2011 8:05:09 AM UTC-8, Taylor Singletary wrote:
> It's a documentation error at the moment, the proper path is: POST :user/:list_id/members/create_all

When was the old resource deprecated? Were there any other resources that changed at the same time? I try to pay close attention to the Twitter API Announcements list, but don't recall seeing anything about this. Could you direct me to the relevant post?

I'm disappointed that the documentation is not keeping up with the API. If anything, the documentation should be coming ahead of changes, not trailing them.

[Taylor Singletary]

There's obviously no good excuse I can tell you for the documentation being wrong.

In this case, the old resource was never deprecated and never existed -- the documentation was wrong from the beginning.

We're very aware of documentation bugs and are actively working towards allowing their modification with more fluidity than we have today. Thanks for your patience while we get there.

@episod - Taylor Singletary - Twitter Developer Advocate

[Ken D.]

Mistakes are a fact of life, no excuses necessary. What is hard to
understand is not being able to change a few characters in the
documentation, while developers continue to fall into this silly
trap.

Is the doc generated from the code? Doesn't look like it.

Of course, this documentation bug - and the FAQ about getting a user's
email address, which could also be laid to rest by improving the doc -
keeps this list alive, so I shouldn't complain.

On Mar 3, 7:24 pm, Taylor Singletary <taylorsinglet...@twitter.com>
wrote:

> There's obviously no good excuse I can tell you for the documentation being
> wrong.
>
> In this case, the old resource was never deprecated and never existed -- the
> documentation was wrong from the beginning.
>
> We're very aware of documentation bugs and are actively working towards
> allowing their modification with more fluidity than we have today. Thanks
> for your patience while we get there.
>

> @episod <http://twitter.com/episod> - Taylor Singletary - Twitter Developer