Incorrect token, 403 and 429 error

[ArtanisTheOne]

Incorrect token's are currently being generated by the @vitalets/google-translate-token which result in a 403 error (forbidden request)

When modifying my branch to put in client: 'gtx' instead of client: 't' it worked for a little while but now stops nearly every request with a 429 error (too many requests)

How can the token generator be fixed to not be producing incorrect tokens? For example, if i get a 403 error the token will be the same numbers on either side of the period (11111.11111 , 45678.45678, 96389.96389 ) meaning only 5/10 numbers are correct.

[figoso90]

I also have the same problem, or rather, I just can't create the token, instead for the 429 error I would know how to avoid it I think

[ArtanisTheOne]

After a few requests you receive a 429 error (due to not having a token thus they're monitoring you more closely) , I have no idea where to start on how to fix this repo to avoid the 111119.111119 tokens which are causing a lot of problems.

[Mrshulan]

I found that the source code requested the translate domain name of .com or .cn and then used the tkk: field. This field has been returning null for the time being. It seems that Google has fixed this security vulnerability. I don't know how to solve it I tried to use charles to find the pattern, but I didn't succeed!

[ArtanisTheOne]

I found a branch recently updated by @vkedwardli which fixes the issue and has been updated to fit the new systems of Google Batch Execute, I am experiencing 0 errors

https://github.com/vkedwardli/google-translate-api

@matheuss and @vitalets please update your branches with the PR he has made

[ken107]

#20 version 2.0.0 complete rewrite