> Hey folks. As some of you have likely read we're starting to do some > private beta testing of our new lists feature. We're not quite ready > to open it up to everyone but we've made some headway on the API and > wanted to share some details of what we've got so far.
Thanks for the list API description. I like the general appearance. One request: > DELETE '/:user/lists/:list_slug.:format' > Delete the specified list owned by the authenticated user. > > Parameters: > * list_slug: the slug of the list you want to delete. (required) > > Supported formats: > xml, json > > e.g. > curl -u USERNAME:PASSWORD -X DELETE > http://twitter.com/noradio/lists/tall-people.xml This is slightly pedantic but currently the entirety of the API can be accessed with GET and POST methods, even tweet and DM deletion (DELETE is supported facultatively but not obligatorily), which happily allows old clients like Lynx to still be used for API access. Could a delete stub method via POST be added to the API to maintain consistency? It would make sense to mandate a full and proper REST implementation using the full breadth of HTTP methods in API v2, but I think for consistency there should be a POST-accessible delete method at least in this implementation unless Lists API is going to be an API v2 feature only. Otherwise, I am very much looking forward to supporting lists in TTYtter (and, when you get around to the next wave, trying it out on the Web). -- ------------------------------------ personal: http://www.cameronkaiser.com/ -- Cameron Kaiser * Floodgap Systems * www.floodgap.com * [email protected] -- When in doubt, use brute force. -- Ken Thompson ----------------------------
