Answers inline: On Wed, Oct 28, 2009 at 1:14 PM, Tim Haines <[email protected]> wrote: > > Marcel, > > Great changes. A couple of questions: > > - How long can a list description be?
160 :-) > - A title can only be 15 chars - will that remain unchanged? Unchanged. > - Will there be a little overlap where memberships and subscribers > will still work while people migrate to followers/following? Yeah. There will be overlap for some period of time for those who might need to transition. > It would be awesome if there was a way to retrieve all member ids and > a separate call for subscriber ids - cursored if necessary. Right, I'll add that to the "list of things to consider" :-) > Also, filed an edge case bug around list error messages a couple of > days ago. > http://code.google.com/p/twitter-api/issues/detail?id=1145&sort=-opened&colspec=ID%20Stars%20Type%20Status%20Priority%20Owner%20Summary%20Opened%20Modified%20Component Thanks. > Cheers, > > Tim. > > > On Oct 29, 9:00 am, Marcel Molina <[email protected]> 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 Teamhttp://twitter.com/noradio > -- Marcel Molina Twitter Platform Team http://twitter.com/noradio
