Any update on possibly supporting bulk add / remove actions for list
memberships? What about the request to fetch all list member IDs in a
single call?

On Nov 5, 2:01 pm, Marcel Molina <mar...@twitter.com> wrote:
> We will support specifying alistby bothidand slug indefinitely.
> Though we recognize the short comings of finding by slug since they
> are prone to changing, there are use cases where finding by slug is a
> lot more convenient. So we'll be supporting both. You never *have* to
> search by slug :-)
>
>
>
> On Thu, Nov 5, 2009 at 7:05 AM, Milen <mi...@thecosmicmachine.com> wrote:
>
> > I think that all methods which refer to lists should use theid, not
> > the slug. As people have mentioned, the slug can change, so in order
> > to reliably delete alist, you will have to fetch its slug and then
> > issue a delete (or you risk getting an error as the slug might have
> > changed in the meantime).
>
> > I also tried to "page" through the statuses in alistbut it seemed
> > that:
> > - next_cursor / previous_cursor had no effect on what was returned
> > - cursor=-1 or anything else didn't have an effect
>
> > Can anyone shed some light on how we're supposed to do paging?
>
> > Thanks,
> > M
>
> > On Oct 16, 7:04 am, Marcel Molina <mar...@twitter.com> wrote:
>
> >>GET'/:users/lists/:list_slug/statuses.:format'
> >> Show tweet timeline for members of the specifiedlist.
>
> >> Parameters:
> >>  * list_slug: the slug of thelistyou want the member tweet timeline
> >> of. (required)
> >>  * next/previous_cursor: used to "page" through results (optional)
>
> >> Supported formats:
> >> xml, json
>
> >> e.g.
> >>  curl -u 
> >> USERNAME:PASSWORDhttp://twitter.com/noradio/lists/tall-people/statuses.xml
>
> --
> Marcel Molina
> Twitter Platform Teamhttp://twitter.com/noradio

Reply via email to