--
Alex Payne - API Lead, Twitter, Inc.
http://twitter.com/al3x
--
Sorry for the delayed reply on this issue. We deployed code yesterday
that should resolve this issue. You may get a 500 on an initial
request for a user, but subsequent requests should be fine. These
errors are due to - you guessed it - some caching issues. We're
tracking a related issue that may effect other API methods, and we're
working to resolve it as quickly as possible.
--