That absolutely seems like a bug, or at least an inconsistency - we generally return a 404 when things are missing. Please file an issue and we'll fix it up early next week.
On Fri, Sep 25, 2009 at 17:51, Dewald Pretorius <dpr...@gmail.com> wrote: > > API folks, could you please, please NOT return 401 "Not authorized" > when an authenticated call with a perfectly valid username and > password requests a /queryusername.json where that queryusername > happens to be a username that does not exist. > > Rather return 404. > > By returning 401 you are making it impossible for me to tell where the > actual problem lies and inform the user. Is it with the user's > password, or is it because the user wanted information about a Twitter > account that does not exist? > > Dewald > -- Alex Payne - Platform Lead, Twitter, Inc. http://twitter.com/al3x
