Hi Doug, I had a look at the SEARCH section of the documentation (not the trends) since the application I am developing primarily uses the search API.
First I do like the extra use of examples and I think this will help the new developers out. I have a few observations. 1 - It says that the maximum number of ORs allowed in search is 5. Currently my app uses 13 ORs and it seems to be working fine. Is this an error in the documentation, or is it a planned change to the API? I hope that this is an error, since I would then need to make more calls to the API to achieve the same result. 2 - I believe one thing that should be in the documentation is the fact that the from_user_id is different than the actual twitter user_id. This is fairly important information that I only discovered when browsing through the support tickets. 3 - The new document does not mention that we have access to 4 months of data from search like the current doc does. Is this still the case? 4 - In the current document the Optional URL parameters are very clear. However in the new document they are under the heading Limitations which for someone looking at it for the first time, will surely be confused. 5 - The optional URL parameters under limitations seem to be inaccurate. Isn't SINCE deprecated? and there is no mention of since_id, rpp, page etc. Thanks On Apr 13, 4:11 pm, Doug Williams <[email protected]> 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 > [email protected] 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
