Definitely happy to make it more clear which methods require authentication and which do not. However, to get the effect that's most intuitive from calling the API methods, calling them as the user whose data you're interested in is the most straightforward approach.
On Mon, Jan 5, 2009 at 09:47, Nicole Simon <[email protected]> wrote: > > > Usually api are to complicated to programm without knowledge and although it > is said so in the documentation that you only need a account (not the users > account), this api is 'too easy' to attract people without much knowledge > and you see the result. > > (The users of course are not any better). > > It might be best to add to the wiki a flag saying > > "this command needs a authentification" auth:any > "this command needs authentification from the user in question" - auth:user > > linked to a mini explanation. > Nicole > > -- > Suche Beta-Tester für Experiment: > "Journalisten suchen Blogger" - http://bloxpert.de/ > > Kontakt: > http://twitter.com/NicoleSimon // http://mit140zeichen.de/ > http://crueltobekind.org // http://beissholz.de > > skype: nicole.simon / mailto:[email protected] > phone: +49 451 899 75 03 / mobile: +49 179 499 7076 > > > -- Alex Payne - API Lead, Twitter, Inc. http://twitter.com/al3x
