Via Twitter I came across A post showing how easy it is to interface with Twitter using WCF 3.5.
Dariusz hypothesizes that it would be cool to do
TwitterStatusProxy proxy = new TwitterStatusProxy( "username", "password" );
// retrieve friends timeline
XElement timeline = proxy.GetFriendsTimeline();
// do whatever you want to do with the dataand proceeds to show how to implement TwitterStatusProxy. All very cool with bindings, channel factories, service contracts and operation contracts.

The only problem I see is that with only .Net 2.0 the same can be achieved with the following:
WebClient wc = new WebClient();
wc.Credentials = new NetworkCredential("username","password");
XmlDocument doc = new XmlDocument();
doc.Load(wc.OpenRead("http://twitter.com/statuses/friends_timeline.xml"));Seems kind of crazy to pile the whole WCF infrastructure on top of something so simple in the first place.





