Thanks for that Marcel, well if it's decided to completely abandon slugs I'll have to go down that route.
Any idea on whether both call types will be allowed yet? Obviously the main lookups will are quick to switch between, just this @screen_name/list_name that'll take more work if we can't use the slug. On Nov 2, 6:12 pm, Marcel Molina <mar...@twitter.com> wrote: > There is, in a sense, an API for resolving a list id by passing in a > slug. It's the show resource for a list. You'll either get a 404 > (which means the slug no longer exist) or you'll get the list payload > which will include the id. > > > > > > On Sun, Nov 1, 2009 at 11:29 PM, Rich <rhyl...@gmail.com> wrote: > > > Using ID only for me is fine, except in the case we mention. If there > > was a REST api to find a list ID based on a slug then it would mean we > > could still resolve @screen_name/list_name links otherwise we wouldn't > > be able to replicate it, except by brute force which would use yet > > more API calls. > > > On Nov 1, 6:14 pm, Marcel Molina <mar...@twitter.com> wrote: > >> Resolving a @screen_name/list_name reference in a tweet is a > >> compelling argument for making the url parameter polymorphic and not > >> deprecating the use of slugs. I will cogitate. > > >> On Sun, Nov 1, 2009 at 10:09 AM, <kaiser.ma...@gmail.com> wrote: > >> > I have to second Rich on this - ID-only is flawed, as twitter supports > >> > hotlinking lists by name (@username/slug) in tweets, and links that to > >> > the list page. If clients want to offer the same behavior, this is not > >> > possible if the API only supports IDs (or would require a potentially > >> > large number of additional requests to get the user's lists and page > >> > through them to find the one mentioned). > > >> > Marco > >> > ------------------------ > > >> > -----Original Message----- > >> > From: Marcel Molina <mar...@twitter.com> > >> > Date: Sun, 1 Nov 2009 10:02:31 > >> > To: <twitter-development-talk@googlegroups.com> > >> > Subject: [twitter-dev] Re: Subscribed Lists > > >> > Currently it's still slug. It hasn't been updated yet. When it is > >> > updated it will for some period of transition accept a slug or an id > >> > but eventually support for the slug in the url will be removed > >> > entirely. > > >> > On Sun, Nov 1, 2009 at 2:14 AM, Rich <rhyl...@gmail.com> wrote: > > >> >> Can we get some form of confirmation on the list slug/id issue. At > >> >> the moment calling by ID doesn't work anyway so it's only using the > >> >> slug. > > >> >> My preference would be to allow either (in a similar way to the other > >> >> REST api's where you can use user id or screenName) > > >> >> On Oct 31, 10:04 pm, twittelator <and...@stone.com> wrote: > >> >>> :user/lists/subscriptions.:format > > >> >>> gets the lists that the user has subscribed to. > > >> >>> Andrew Stone > >> >>> Twitter / @twittelatorhttp://www.stone.com > >> >>> got iPhone? > >> >>> http://tinyurl.com/twitpro > >> >>> http://tinyurl.com/intentionizer > >> >>> http://tinyurl.com/gesture-buy > >> >>> http://tinyurl.com/igraffiti > >> >>> http://tinyurl.com/talkingpics > >> >>> http://tinyurl.com/mobilemix > >> >>> http://tinyurl.com/soundbite > >> >>> http://tinyurl.com/icreated > >> >>> http://tinyurl.com/pulsar-app > > >> >>> On Oct 30, 5:00 am, "David Neubauer" <davidneubauer.gro...@gmail.com> > >> >>> wrote: > > >> >>> > Has any figured out how to get a the lists I'm subscribed to. I > >> >>> > didn't > >> >>> > realize how much I'd want this part of it. Please say it's coming... > > >> >>> > -----Original Message----- > >> >>> > From: twitter-development-talk@googlegroups.com > > >> >>> > [mailto:twitter-development-t...@googlegroups.com] On Behalf Of > >> >>> > Jeremy Felt > >> >>> > Sent: Thursday, October 29, 2009 8:16 PM > >> >>> > To: Twitter Development Talk > >> >>> > Subject: [twitter-dev] Re: Updates to the List API (list > >> >>> > descriptions, > >> >>> > cursoring lists of lists, finding by list id rather than slug & more > >> >>> > consistent names) > > >> >>> > It appears that user/lists.xml only shows lists that are created by > >> >>> > the user and not those that they follow. > > >> >>> > Any change coming to that or am I missing a way to see all lists that > >> >>> > a user follows? > > >> >>> > Thanks, > >> >>> > Jeremy > > >> >>> > On Oct 28, 3:00 pm, 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 Teamhttp://twitter.com/noradio > > >> > -- > >> > Marcel Molina > >> > Twitter Platform Team > >> >http://twitter.com/noradio > > >> -- > >> Marcel Molina > >> Twitter Platform Teamhttp://twitter.com/noradio > > -- > Marcel Molina > Twitter Platform Teamhttp://twitter.com/noradio
