[ { code: 226,
2019-08-02T12:21:26.616302+00:00 app[web.1]: message:
2019-08-02T12:21:26.616304+00:00 app[web.1]: ‘This request looks like it might be automated. To protect our users from spam and other malicious activity, we can't complete this action right now. Please try again later.’ } ],
2019-08-02T12:21:26.616305+00:00 app[web.1]: twitterReply: { errors: [ [Object] ] },
2019-08-02T12:21:26.616306+00:00 app[web.1]: statusCode: 403 }
One part of my app enables users to send commands to my twitter account and the twitter account responds appropriately. I have just seen one instance where a user send one of these commands, but when trying to send an automated response the app was met with the above error message.
- Yes, it is automated, thats the point
- Why would it be spam if the user sent a message first?
Is there a best practice or guidance to prevent this? Not just in DM’s I’ve had this error happen after somebody sends a tweet to the account and the account attempts to respond.
system
Closed
#2
This topic was automatically closed 14 days after the last reply. New replies are no longer allowed.