Thanks - the silence is strange.

On May 26, 12:38 pm, hax0rsteve <[email protected]> wrote:
> I don't think it's a silly question, just that no one knows except twitter.
>
> +1 for an answer from the twitter team is possible, because it's easier to
> parse and react to '39' than the equivalent strings.
>
> Anyone ? Bueller, Bueller, Bueller ?  :-)
>
> On 26 May 2011, at 08:57, Maomor wrote:
>
> > I guess this is a silly question then. Sorry to have bothered you with
> > it.
>
> > On May 25, 9:59 am, Maomor <[email protected]> wrote:
> >> I do not understand why this information is not available, in the
> >> documentation or as a reply to my question here ?
>
> >> Is there some reason for it ?
>
> >> On May 23, 12:05 pm, Maomor <[email protected]> wrote:
>
> >>> Is there a list of the Twitter errors we get back ?
> >>> That is, not the HTTP errors like 401 etc, but errors like this ( in
> >>> JSON ) :
>
> >>>   {
> >>>   "errors":
> >>>     [
> >>>       {
> >>>       "code":39,
> >>>       "message":"Creation token is missing or invalid -- call
> >>> similar_places to get a valid creation token"
> >>>       }
> >>>     ]
> >>>   }
>
> > --
> > Twitter developer documentation and resources:https://dev.twitter.com/doc
> > API updates via Twitter:https://twitter.com/twitterapi
> > Issues/Enhancements 
> > Tracker:https://code.google.com/p/twitter-api/issues/list
> > Change your membership to this 
> > group:https://groups.google.com/forum/#!forum/twitter-development-talk

-- 
Twitter developer documentation and resources: https://dev.twitter.com/doc
API updates via Twitter: https://twitter.com/twitterapi
Issues/Enhancements Tracker: https://code.google.com/p/twitter-api/issues/list
Change your membership to this group: 
https://groups.google.com/forum/#!forum/twitter-development-talk

Reply via email to