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.
Which is what brought us into this mess (and I am telling you that is not getting better) I'd rather have the user 'learn' which actions require the access to my password. Which basically should be just two areas: sending tweets / DM and changing settings. Most apps should not require the password and like childreen people like Chris Brogan and co will make them learn that this is all they should share. It is like childreen and fire. The viral effect most devs wish for (oh they should tweet about me!) can be reached without the users login data by encouraging the users to spread the news. See this result from http://twtpoll.com/r/49jw9z as an example of how it is done in a way that I as a user am happy to spread the news in comparison to the most often stupid automated messages. hth 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
