A best practices page would be nice. Could include tips like make calls using user_id instead of screen_name incase the screen_name changes.
On Thu, Apr 16, 2009 at 10:43, Adrian <spiritpo...@gmail.com> wrote: > > Would love to see something about OAuth, to help in the migration > process. > > On Apr 14, 2:11 am, Doug Williams <d...@twitter.com> wrote: > > Coderz, > > I am refactoring the API documentation [1] to make it friendlier on the > eyes > > and easier on new developers. Please give it a once over and reply with > any > > of errors, addition requests, or suggestions. We will be using these new > > docs officially in a few days (linked from the apiwiki.twitter.com) once > any > > glaring omissions and/or errors are addressed. > > > > My goal is to make the documentation more robust and example laden to > help > > new developers get going without needing help. Suggestions and critism > along > > those lines is welcome. > > > > A final plea for help: > > If you have some spare time and examples to borrow from, please send > > a...@twitter.com any code/instructions that I can then paste into method > body > > to help new devs get started. Basic Hello World! style usage examples for > > each method would go a long way to curbing new developer problems. Be > sure > > to include a link to any libraries your example is using. Working full > > length example code hosted on github would be preferred. > > > > 1.http://apiwiki.twitter.com/Twitter-API-Documentation > > > > Thanks, > > Doug Williams > > Twitter API Supporthttp://twitter.com/dougw > -- Abraham Williams | http://the.hackerconundrum.com Hacker | http://abrah.am | http://twitter.com/abraham Web608 | Community Evangelist | http://web608.org This email is: [ ] blogable [x] ask first [ ] private. Sent from Madison, Wisconsin, United States
