twitter now suspends all bots runs by backend requests

rlaclrk1

Junior Member
Joined
Jan 3, 2023
Messages
119
Reaction score
28
seems that they are now suspending all bots running by backeend requests using curl cliff or reuqests
 
The detection could definitely be more precise, but I’d try to test that out on a small scale first before assuming that everything is being detected. It could be something to do with the pattern of the backend requests instead.
 
The detection could definitely be more precise, but I’d try to test that out on a small scale first before assuming that everything is being detected. It could be something to do with the pattern of the backend requests instead.
do you also feel same like me? that they suspend all requests bot
 
Backend requests can trigger suspensions if they look automated or bypass X's normal access patterns. I'd check the suspension notices and use the official X API where possible, since changing request headers alone may not fix the issue.
 
dude raw HTTP requests haven't been safe on X for a while now. I used to sending actions without dynamic transaction tokens, those accounts get flagged for instant suspension. u need to switch to emulated browser setup or mobile API endpoints using real proxies
U need to extract attest token from real phone if you want to use mobile api which is impossible or do you know any service who provides mobile api? No I don't do raw http I am using curl cliff
 
curl only solves the TLS/AJ3 layer mate. X still catch u on client transaction IDs and JS telemetry tokens that u can't properly mimic (without executing the actual web app bundle). btw, u can use Android ADB hardware automation if u need mobile endpoints
I can't use browser automation or phone automation it uses too much proxy traffic. can you please let me know good ways?
 
X has been tricky for some time now, android phone automation is the way to go !
 
Raw requests just look kinda off to X. It can tell when youre not using a real browser since youre missing all the background calls and other stuff that happens naturally. Had this happen a bunch with backend scripts. If its a proxy issue, try getting the tokens from your local browser first, raw requests alone usually dont cut it.
 
Could be stricter enforcement against unofficial automation, but I'd be careful assuming all backend bots are affected. Using X's official API and following its automation rules is the safer approach.
What is this ai generated answer lol
 
Real browser or phone automation is the only safe way, all platforms can surely detect raw requests if they want. It does eat traffic, but you can block media or switch to ISP proxies for like 4$/pc. What do you need the automation for?
 
Automation is supposed to go through the official X API. Screen scraping, browser automation, and unofficial APIs are prohibited
 
Automation is supposed to go through the official X API. Screen scraping, browser automation, and unofficial APIs are prohibited
Everyone just gonna ignore those AI or whatever replies?
 
it's getting more strict with all profiles (even if you use it manually), so it's not automation problem
 
Were the suspended ones mostly new accounts or aged ones too? If old accounts got hit as well, that sounds more like the wider crackdown #17 mentioned than just the request method.
 
a mobile proxy won't make curl_cffi behave like a real mobile app though. you're still sending the same backend requests, just from a different IP. if X is detecting the requests themselves, moving from residential to 4G/5G won't really solve that.
 
Its nothing new; they’ve been doing this for a while. They’re just checking more frequently now.
 
Back
Top