When trying to translate a list slug to a list ID, we make a call
against the API endpoint https://api.twitter.com/1/STLT_Business/lists/tech.xml
(where STLT_Business is the Twitter Screen name and tech is the list
slug)
This returns a nice valid XML like this:
list
id7866001/id
Thanks for your good-humored analysis of the issue. This is a new
feature we haven't documented or announced yet, and causes a conflict
we should have obviously thought more deeply about in advance.
Here's a work around to access the same end point you know and love
for lists named all:
