[Twitter.h] ERROR--Your computer may be sending automated queries.

Hello community,

I just had this problem after some months of working without any problem.

My project sends status information through the twitter library 3 times a day (each message containing slightly different information). After 3 days without recieving any notification I checked the debbug and the following info appeared:

HTTP/1.0 403 Forbidden
Content-Length: 1103
Content-Type: text/html; charset=UTF-8

<html><head><meta http-equiv="content-type" content="text/html;
charset=utf-8"/><title>Sorry...</title><style> body { font-family: verdana, arial, sans-serif; background-color: #fff; color: #000; }</style></head><body><div><table><tr><td><b><font face=sans-serif size=10><font color=#4285f4>G</font><font color=#ea4335>o</font><font color=#fbbc05>o</font><font color=#4285f4>g</font><font color=#34a853>l</font><font color=#ea4335>e</font></font></b></td><td style="text-align: left;
vertical-align: bottom; padding-bottom: 15px; width: 50%"><div style="border-bottom: 1px solid #dfdfdf;">Sorry...</div></td></tr></table></div><div style="margin-left: 4em;"><h1>
We're sorry...</h1><p>... but your computer or network may be sending automated queries. To protect our users, we can't process your request right now.</p></div><div 
style="margin-left: 4em;">See <a href="https://support.google.com/websearch/answer/86640">Google Help</a> for more information.

</div><div style="text-align:
 center; border-top: 1px solid #dfdfdf;"><a href="https://www.google.com">Google Home</a></div></body></html>failed : code 0

We're sorry...

... but your computer or network may be sending automated queries. To protect our users, we can't process your request right now.

<div

I tried sending a message with completely different content; Sending it to a different twitter account...but no solution

Anyone has suffered from this problem?

Thank you in advance.

INFO: I am using an Android Mega with an Ethernet Shield v2

If I were you based on the information provided I would start and check to see if Twitter changed anything.
Maybe now they need cookie acceptance or similar ?

Thank you for your answer!

I have been wondering and the only thing that could have sense is that the library Twitter.h uses a OAuth (http://arduino-tweet.appspot.com/)procedure. As I always use that service at the same time it detects me as a bot.

In PC when this occurs a Captcha is displayed. However, I cannot solve any captcha from the arduino :frowning:
I am kind of stuck

Yes getting past a CRAPTCHA with an Arduino is almost impossible.

Do they have any other API's / ports / etc. you could use for authentication ?
Clearly its a twitter issue and I am sure they are also aware of automated usage and have an option for it.

Thanks again for helping!

I looked at the rules of usage of Twitter (Twitter-Limits) and the daily limit is 2500 Twits/day. As I am sending 3 a day I don`t exceed this limit.

Therefeore, I think the ban is not from the Twitter web but from the OAuth stuff.

Anyway I am very confuse as I haven't read from people having the same problem! I will stay a hole week without trying to automatically post on twitter and I will try again after. I will post my results.

I have been posting tweets without problems with the arduino for several years, but since December 5 my arduino can not post tweets.

INFO: I am also using an Android Mega with an Ethernet Shield v2

sorry for my english

error:
connecting ...
connection failed.
connecting ...
HTTP/1.0 403 Forbidden
Content-Length: 1103
Content-Type: text/html; charset=UTF-8

Sorry... body { font-family: verdana, arial, sans-serif; background-color: #fff; color: #000; }
Google
Sorry...

We're sorry...

... but your computer or network may be sending automated queries. To protect our users, we can't process your request right now.

See Google Help for more information.
Google Home
failed : code 403

@satbranigan

It does seem TWITTER specific.
You might want to check there for starters as mentioned previously.

Hi, I have the same problem since Dec 5. This seems to be the date when the problem occurred for @satbranigan and for @Dimeruben as well. So something seems to have changed on that date, however I have no clue what this could be. Posting the same request from my PC using curl works fine:

curl --location --request POST "http://arduino-tweet.appspot.com/update" --data "token=1234567890-abcdefghijklmnopqrstuvwxyzabcdefghijklm&status=xdxdxdxdssss" --header "content-length: 71"

(I do not post my real token here :wink:

My code is
#define LIB_DOMAIN "arduino-tweet.appspot.com"

if (int ret=client.connect(LIB_DOMAIN, 80)) {
client.println("POST http://" LIB_DOMAIN "/update HTTP/1.0");
client.print("Content-Length: ");
client.println(strlen(msg)+strlen(token)+14);
client.println();//POST
client.print("token=");//POST
client.print(token);
client.print("&status=");
client.println(msg);
} else {
return false;
}

Any ideas what has changed on Dec. 5 and what we can do to fix the issue?

It's almost as if Twitter don't want bots on their system.

Note that you cannot re-tweet the same message, it will be rejected.
When I did this stuff I added an incrementing number to each tweet and that worked fine.

There is some good code examples held by me Google

GoForSmoke:
It's almost as if Twitter don't want bots on their system.

that is why I used DWEET.io and not twitter
dweet.io is for bots. twitter from carbon units.

Sounds like twitter tightened up their restrictions on automated posts, and may now prohibit them entirely, or subject them to new restrictions. This is probably a response to widespread abuse of twitter by bots, for example the stuff related to US election meddling.

Get the latest twitter library from Neocat's github. It incorporates the fix from Jack Christensen.

Worldwide election meddling, it turns out.

thank you so much @Duckie58 this library works again GitHub - JChristensen/Twitter: NeoCat's Twitter library, updated to fix an issue.

i don't have Teensy boards. Is there a update or fix for "NeoCat's Twitter library"?

Thank you @Duckie58 - this worked for me.
Changes to http 1.1 and extra elements in the http post to the appspot.com address in Twitter.cpp seems to be the fix.