Jeff, The friendship methods will allow you to create and destroy friendships on the behalf of authenticated users. Their usage is explained at [1]. These methods allow you to "follow" and "unfollow" users. Notification methods are not necessary unless you would like to enable/disable device notification. If you would like a more complete explanation on the differences between following and notification I would be happy to help explain that.
The error case for protected users isn't explicit. You will have to parse the returned user element results [2] and look for a true value in the protected element. For instance, in xml format: <protected>true</protected> Lastly, I know a professor who teaches a class where students work on projects promoting computing accessibility. If you feel this is a large enough project that a student could get involved, I can introduce you to the professor so you two can discuss if he has any students who may would be able to contribute. Contact me off the board (do...@igudo.com) if this interests you. [1] - http://apiwiki.twitter.com/REST+API+Documentation#FriendshipMethods [2] - http://apiwiki.twitter.com/REST+API+Documentation#Basicuserinformationelement Thanks, Doug @dougw On Wed, Mar 4, 2009 at 9:26 AM, Jeff Bishop <jeff.bis...@gmail.com> wrote: > Hello, > > I am developing a Twitter client titled WETweet. The purpose of this > client is to provide blind users using the Window-Eyes screen reader a > better and more rich experience using Twitter. > > I had a question about automating the creation of friend relationships and > following and un-following people. Which methods of the Twitter API and in > what order should be used? What kind of error conditions will be returned > when attempting to follow protected users? > > If one uses the Friend methods to follow someone does the Notification > methods need to be utilized? > > I found the documentation a bit unclear on the path to take here. > > Thanks for everyone's help. > > Jeff > > -- Doug Williams do...@igudo.com http://www.igudo.com
