Hey Marcel, Just checking - You haven't rolled this change yet right?:
/:user/lists/:list_id/memberships becomes /:user/lists/:list_id/followers It seems attempting to follow a user who doesn't exist (through the members post) results in a 500 at the moment, rather than a 404. Tim. On Thu, Oct 29, 2009 at 9:00 AM, Marcel Molina <mar...@twitter.com> wrote: > > Two additions and two changes to the List API will be deployed in the > next few days: > > * List descriptions > We're adding a description to every list. You'll be able to specify a > description when you create or update a list and the description will > be included in the payload. > > * Cursoring through lists of lists > All resources that return a list of lists will include next and > previous cursors and will accept a :cursor parameter. > > * Finding by list id rather than slug > When you change the name of a list, the slug will be updated to > reflect that change. That means using the slug in the url for > resources to operate on lists requires the onerous task of validating > that the slug for the list you are about to do something with hasn't > been updated since the last time you stored its slug. What a nightmare > :-) > > Every list also has an id. This value won't change. We'll be changing > the API to replace all instances of a list slug in urls to be list ids > instead. > > * Consistent names > The terminology we've used thus far for people you follow with a list > is members. The terminology for people who are following a list is > subscribers. We're going to mirror the terminology used for users and > change it to followers and following respectively. > > So: > > /:user/lists/:list_id/memberships becomes /:user/lists/:list_id/followers > > /:user/lists/:list_id/subscribers becomes /:user/lists/:list_id/following > > As we deploy these changes we'll send out a heads up on the dev list > and @twitterapi. > > -- > Marcel Molina > Twitter Platform Team > http://twitter.com/noradio > > > >
