Hi, thank you for the answer, this is an example of a sentence that
works and is tweeted correctly:
"setting up my twitter 私のさえずりを設定する"
and now an example of a sentence that is not tweeted because of
"incorrect signature":
"setting up my twitter"
I find it interesting because it is a substring of the first sentence.
On May 27, 10:28 am, Taylor Singletary <taylorsinglet...@twitter.com>
wrote:
> Can you share an example of what your signature base string looks like in
> the case of you sending the plain English tweet?
>
> There are some cases when we're under load where we're send a "Cannot
> authenticate you" error, but it doesn't look like that's what is going on
> here.
>
> Taylor Singletary
> Developer Advocate, Twitterhttp://twitter.com/episod
>
> 2010/5/27 Alvaro Montoro <alvaromont...@gmail.com>
>
> > Hi,
>
> > I follow the example athttp://dev.twitter.com/pages/authin order to
> > authenticate and tweet and it works fine with their example: I tweet
> > successfully the sentence "setting up my twitter 私のさえずりを設定する". But
> > then I try to tweet the just the sentence in plain English: "setting
> > up my twitter" and it fails, I get this message:
>
> > {"request":"/1/statuses/update.json","error":"Incorrect signature"}
>
> > I have tested and basically the idea is: if the sentence I want to
> > tweet has UTF-8 characters, it will work fine, posting everything; if
> > it doesn't have them, then I'll get the error message displayed.
>
> > Why can this happen? It seems an error with the URLEncode but, why
> > would it work in one string and not in a substring? Also, could anyone
> > tell me how accurate that error message is? Could it be something
> > different from the signature being incorrect?
>
> > Thanks
