Re: [twitter-dev] Poor documentation. For example, regarding lists. Suggestions for improvement.

2011-06-24 Thread Correa Denzil
Matt : I suggest in the Example Requests you add the URL for the call. It will prevent much of the What URL to call? queries. --Regards, Denzil On Fri, Jun 24, 2011 at 4:55 AM, Matt Harris thematthar...@twitter.comwrote: Hi Dave, Thanks for your feedback, it's important for us to know

Re: [twitter-dev] Poor documentation. For example, regarding lists. Suggestions for improvement.

2011-06-24 Thread Matt Harris
Hi Denzil, Thanks for the suggestion. Do you think that would help or would it be better to try and link to the console? Just curious about alternative ideas. The reason I say this is POST and DELETE requests are difficult to write as single example URLs. When we had them in the past they led to

Re: [twitter-dev] Poor documentation. For example, regarding lists. Suggestions for improvement.

2011-06-23 Thread Matt Harris
Hi Dave, Thanks for your feedback, it's important for us to know when developers are not finding the information they are looking for. I have responded to your specific points inline: Issue #1: Valid version numbers I was unable to locate valid values for version. I tried 1.1.14, which I

[twitter-dev] Poor documentation. For example, regarding lists. Suggestions for improvement.

2011-06-22 Thread Dave Aaron Smith
I'm using this call for my website. http://dev.twitter.com/doc/get/lists/statuses The documentation states that the url works like this: http://api.twitter.com/**version**/lists/statuses.**format** Issue #1: Valid version numbers I was unable to locate valid values for version. I tried