Twitter automization test (4 factors, 32 accounts)

Test Report 6


Well, did have some abnormalities today,

2 CONNECTION_ERROR in case
{REAL_CHROMEDRIVER}_{AUTOMATION}_{PROFILED}_{NON_HEADLESS}
{REAL_CHROMEDRIVER}_{AUTOMATION}_{NON_PROFILED}_{NON_HEADLESS}

But I wouldn't be too worried about it,
I did not delete cookies or profiles, when retrying and it was a success.
They did all happen in AUTOMATION so still, I would keep an eye on it.

Other then that most cases was a success.

Test Results

{UNDETECTED_CHROMEDRIVER}_{AUTOMATION}_{PROFILED}_{HEADLESS}
SUCCESS
SUCCESS
SUCCESS
SUCCESS
SUCCESS
SUCCESS

{UNDETECTED_CHROMEDRIVER}_{AUTOMATION}_{PROFILED}_{NON_HEADLESS}
SUCCESS
CONNECTION_ERROR + SUCCESS
SUCCESS
SUCCESS
SUCCESS
SUCCESS

{UNDETECTED_CHROMEDRIVER}_{AUTOMATION}_{NON_PROFILED}_{HEADLESS}
CONNECTION_ERROR
SUCCESS
SUCCESS
SUCCESS
SUCCESS
SUCCESS

{UNDETECTED_CHROMEDRIVER}_{AUTOMATION}_{NON_PROFILED}_{NON_HEADLESS}
UNEXPECTED_REGISTER_SIGNS + SUCCESS
SUCCESS
SUCCESS
SUCCESS
SUCCESS
SUCCESS

{UNDETECTED_CHROMEDRIVER}_{MANUAL}_{PROFILED}_{HEADLESS}
PASS

{UNDETECTED_CHROMEDRIVER}_{MANUAL}_{PROFILED}_{NON_HEADLESS}
SUCCESS
SUCCESS
SUCCESS
SUCCESS
SUCCESS
SUCCESS

{UNDETECTED_CHROMEDRIVER}_{MANUAL}_{NON_PROFILED}_{HEADLESS}
PASS

{UNDETECTED_CHROMEDRIVER}_{MANUAL}_{NON_PROFILED}_{NON_HEADLESS}
SUCCESS
SUCCESS
SUCCESS
SUCCESS
SUCCESS
SUCCESS

{REAL_CHROMEDRIVER}_{AUTOMATION}_{PROFILED}_{HEADLESS}
PASS

{REAL_CHROMEDRIVER}_{AUTOMATION}_{PROFILED}_{NON_HEADLESS}
SUCCESS
SUCCESS
SUCCESS
SUCCESS
SUCCESS
CONNECTION_ERROR + SUCCESS

{REAL_CHROMEDRIVER}_{AUTOMATION}_{NON_PROFILED}_{HEADLESS}
PASS

{REAL_CHROMEDRIVER}_{AUTOMATION}_{NON_PROFILED}_{NON_HEADLESS}
SUCCESS
SUCCESS
SUCCESS
SUCCESS
SUCCESS
CONNECTION_ERROR + SUCCESS

{REAL_CHROMEDRIVER}_{MANUAL}_{PROFILED}_{HEADLESS}
PASS

{REAL_CHROMEDRIVER}_{MANUAL}_{PROFILED}_{NON_HEADLESS}
SUCCESS
SUCCESS
SUCCESS
SUCCESS
SUCCESS
SUCCESS

{REAL_CHROMEDRIVER}_{MANUAL}_{NON_PROFILED}_{HEADLESS}
PASS

{REAL_CHROMEDRIVER}_{MANUAL}_{NON_PROFILED}_{NON_HEADLESS}
UNEXPECTED_REGISTER_SIGNS + SUCCESS
SUCCESS
SUCCESS
SUCCESS
SUCCESS
SUCCESS

{DEFAULT_CHROMEDRIVER}_{AUTOMATION}_{PROFILED}_{HEADLESS}
BROWSER_BLOCKED
BROWSER_BLOCKED
BROWSER_BLOCKED
BROWSER_BLOCKED
BROWSER_BLOCKED
BROWSER_BLOCKED

{DEFAULT_CHROMEDRIVER}_{AUTOMATION}_{PROFILED}_{NON_HEADLESS}
SLOW + SUCCESS
SLOW + SUCCESS
SLOW + SUCCESS
SLOW + SUCCESS
SLOW + SUCCESS
SLOW + SUCCESS

{DEFAULT_CHROMEDRIVER}_{AUTOMATION}_{NON_PROFILED}_{HEADLESS}
BROWSER_BLOCKED
BROWSER_BLOCKED
BROWSER_BLOCKED
BROWSER_BLOCKED
BROWSER_BLOCKED
BROWSER_BLOCKED

{DEFAULT_CHROMEDRIVER}_{AUTOMATION}_{NON_PROFILED}_{NON_HEADLESS}
SPIN
SUCCESS
SUCCESS
SUCCESS
SUCCESS
SUCCESS

{DEFAULT_CHROMEDRIVER}_{MANUAL}_{PROFILED}_{HEADLESS}
PASS

{DEFAULT_CHROMEDRIVER}_{MANUAL}_{PROFILED}_{NON_HEADLESS}
SUCCESS
SPIN
SUCCESS
SUCCESS
SUCCESS
SUCCESS

{DEFAULT_CHROMEDRIVER}_{MANUAL}_{NON_PROFILED}_{HEADLESS}
PASS

{DEFAULT_CHROMEDRIVER}_{MANUAL}_{NON_PROFILED}_{NON_HEADLESS}
SUCCESS
SUCCESS
SUCCESS
SUCCESS
SUCCESS
SUCCESS


Logs for nerds
https://drive.google.com/file/d/1mOgmlFK5pwCofwTCelXfkTUX7u-R2dKc/view?usp=sharing
PS.
Well, tomorrow is our last test, and we did not get a single account banned.
Cranking up the follow amounts to 30 next time.

I will do a summary of the useful facts that we learned since it will be our last.

Good luck on your ventures!
looking forward to it
 
Mozilla/5.0 (Macintosh; Intel Mac OS X 10_15_7) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/108.0.0.0 Safari/537.36
No randomizing, all the accounts are the same.

there are some claims by the creators of undetectable-chromedriver that changing useragents makes you get caught.
nice, we use the same useragents, only difference is you are on MAC and im on Windows.

excited for round 2 testing :D
I wanna see those numbers ramped up :)

you will use 30 accounts, 30 follows per day in ROUND 2 right?
 
Are you using proxies or just one vpn and IP for all these accounts?? I am looking to get started and testing with 10-20 accs. I have some ideas i want to use as to grow them organically also. Def need to just start testing. I think user agents, IP and age of accs // fully verified or just email veirfied ( what email domains used...such as shit throwaway email services are likly blocked or banned quickly) is a big thing.
 
How ist your Follow Back Ratio at your Accounts?
Account name
Follow/Followers

Account 1
134/2
Account 2
111/1
Account 3
99/0
Account 4
117/0
Account 5
pass
Account 6
111/2
Account 7
pass
Account 8
112/1
Account 9
pass
Account 10
110/3
Account 11
pass
Account 12
114/2
Account 13
pass
Account 14
113/1
Account 15
pass
Account 16
110/0
Account 17
pass
Account 18
111/0
Account 19
pass
Account 20
107/4
Account 21
pass
Account 22
104/1
Account 23
pass
Account 24
109/5

All the accounts are created for testing purposes so there was no profile pictures or tweets created in the accounts.

I did heard that female profile pictures have a better follow back ratio,
Or maybe I am just be sexist XD
 
Last edited:
Are you using proxies or just one vpn and IP for all these accounts??

I am using my own 4G proxy. ip rotates, so they all have a different ip.
https://www.blackhatworld.com/seo/diy-how-to-create-your-own-4g-proxy.1234185/
I think user agents, IP and age of accs // fully verified or just email veirfied ( what email domains used...such as shit throwaway email services are likly blocked or banned quickly) is a big thing.

Most definitely is.
I did get banned on my first try in account creation, so I would advise you to be careful when signing up.
 
Last edited:
How are you planning to monetize Twitter? That's the bigges difficulty for me

To monetize it? I have no idea.
Maybe created a porn website? affiliate links?
I am a bit behind you, I have no accounts with mass followers nor a system to get traffic. so I need to catch up first.

I did also heard that twitter bans when the same url is tweeted repeatedly.
But I am sure there is a loophole for that.
 
Test Report 7

Final test, did crank up the follows to 30,
but no accounts were banned. Xd
No abnormalities either.
Just one CONNECTION_ERROR and the retry was a success.


TEST RESULTS

{UNDETECTED_CHROMEDRIVER}_{AUTOMATION}_{PROFILED}_{HEADLESS}
SUCCESS
SUCCESS
SUCCESS
SUCCESS
SUCCESS
SUCCESS
SUCCESS

{UNDETECTED_CHROMEDRIVER}_{AUTOMATION}_{PROFILED}_{NON_HEADLESS}
SUCCESS
CONNECTION_ERROR + SUCCESS
SUCCESS
SUCCESS
SUCCESS
SUCCESS
SUCCESS

{UNDETECTED_CHROMEDRIVER}_{AUTOMATION}_{NON_PROFILED}_{HEADLESS}
CONNECTION_ERROR
SUCCESS
SUCCESS
SUCCESS
SUCCESS
SUCCESS
SUCCESS

{UNDETECTED_CHROMEDRIVER}_{AUTOMATION}_{NON_PROFILED}_{NON_HEADLESS}
UNEXPECTED_REGISTER_SIGNS + SUCCESS
SUCCESS
SUCCESS
SUCCESS
SUCCESS
SUCCESS
SUCCESS

{UNDETECTED_CHROMEDRIVER}_{MANUAL}_{PROFILED}_{HEADLESS}
PASS

{UNDETECTED_CHROMEDRIVER}_{MANUAL}_{PROFILED}_{NON_HEADLESS}
SUCCESS
SUCCESS
SUCCESS
SUCCESS
SUCCESS
SUCCESS
SUCCESS

{UNDETECTED_CHROMEDRIVER}_{MANUAL}_{NON_PROFILED}_{HEADLESS}
PASS

{UNDETECTED_CHROMEDRIVER}_{MANUAL}_{NON_PROFILED}_{NON_HEADLESS}
SUCCESS
SUCCESS
SUCCESS
SUCCESS
SUCCESS
SUCCESS
SUCCESS

{REAL_CHROMEDRIVER}_{AUTOMATION}_{PROFILED}_{HEADLESS}
PASS

{REAL_CHROMEDRIVER}_{AUTOMATION}_{PROFILED}_{NON_HEADLESS}
SUCCESS
SUCCESS
SUCCESS
SUCCESS
SUCCESS
CONNECTION_ERROR + SUCCESS
CONNECTION_ERROR + SUCCESS

{REAL_CHROMEDRIVER}_{AUTOMATION}_{NON_PROFILED}_{HEADLESS}
PASS

{REAL_CHROMEDRIVER}_{AUTOMATION}_{NON_PROFILED}_{NON_HEADLESS}
SUCCESS
SUCCESS
SUCCESS
SUCCESS
SUCCESS
CONNECTION_ERROR + SUCCESS
SUCCESS

{REAL_CHROMEDRIVER}_{MANUAL}_{PROFILED}_{HEADLESS}
PASS

{REAL_CHROMEDRIVER}_{MANUAL}_{PROFILED}_{NON_HEADLESS}
SUCCESS
SUCCESS
SUCCESS
SUCCESS
SUCCESS
SUCCESS
SUCCESS

{REAL_CHROMEDRIVER}_{MANUAL}_{NON_PROFILED}_{HEADLESS}
PASS

{REAL_CHROMEDRIVER}_{MANUAL}_{NON_PROFILED}_{NON_HEADLESS}
UNEXPECTED_REGISTER_SIGNS + SUCCESS
SUCCESS
SUCCESS
SUCCESS
SUCCESS
SUCCESS
SUCCESS

{DEFAULT_CHROMEDRIVER}_{AUTOMATION}_{PROFILED}_{HEADLESS}
BROWSER_BLOCKED
BROWSER_BLOCKED
BROWSER_BLOCKED
BROWSER_BLOCKED
BROWSER_BLOCKED
BROWSER_BLOCKED
BROWSER_BLOCKED

{DEFAULT_CHROMEDRIVER}_{AUTOMATION}_{PROFILED}_{NON_HEADLESS}
SLOW + SUCCESS
SLOW + SUCCESS
SLOW + SUCCESS
SLOW + SUCCESS
SLOW + SUCCESS
SLOW + SUCCESS
SLOW + SUCCESS

{DEFAULT_CHROMEDRIVER}_{AUTOMATION}_{NON_PROFILED}_{HEADLESS}
BROWSER_BLOCKED
BROWSER_BLOCKED
BROWSER_BLOCKED
BROWSER_BLOCKED
BROWSER_BLOCKED
BROWSER_BLOCKED
BROWSER_BLOCKED

{DEFAULT_CHROMEDRIVER}_{AUTOMATION}_{NON_PROFILED}_{NON_HEADLESS}
SPIN
SUCCESS
SUCCESS
SUCCESS
SUCCESS
SUCCESS
SUCCESS

{DEFAULT_CHROMEDRIVER}_{MANUAL}_{PROFILED}_{HEADLESS}
PASS

{DEFAULT_CHROMEDRIVER}_{MANUAL}_{PROFILED}_{NON_HEADLESS}
SUCCESS
SPIN
SUCCESS
SUCCESS
SUCCESS
SUCCESS
SUCCESS

{DEFAULT_CHROMEDRIVER}_{MANUAL}_{NON_PROFILED}_{HEADLESS}
PASS

{DEFAULT_CHROMEDRIVER}_{MANUAL}_{NON_PROFILED}_{NON_HEADLESS}
SUCCESS
SUCCESS
SUCCESS
SUCCESS
SUCCESS
SUCCESS
SUCCESS


Logs for nerds
https://drive.google.com/file/d/1w8Z7PNXaYBrbrMP-pi3wO2j6CCeJj5et/view?usp=share_link

CONCLUSION

The last 2 days of testing did not end up with any bans even if we cranked up the follows to 10 -> 20 -> 30.

So not a lot was to be learned, but still, in the first 4 tests, we did get some valuable information. Some are theories but some are certain enough that I would state them as facts.

FACTS

1. Twitter has a security code on access.


I have stated this numerous times in this test, and this was occurred in multiple abnormalities so you would agree me that this is true.

We do not have enough test cases and accounts to analyze its whole behavior.
But still, we can see some actions take place.

When you access with default chromedriver in headless mode ->

When you access with a public VPN ->

When it has a error on boot ->

In test report 4, additional tests, I have stated that when twitter blocked me after accessing with a public VPN, and I needed to delete the profiles and cookies.

So this security code can also flags your profiles / cookies if they seem malicious.


2. Twitter is willing to catch headless.

In test report 1, case
{DEFAULT_CHROMEDRIVER}_{AUTOMATION}_{NON_PROFILED}_{HEADLESS}

always results in a BROWSER_BLOCKED.


Twitter detects DEFAULT_CHROMEDRIVER for sure, and blocks if you go headless.

But twitter did not block us if it was the real browser, or undetected-chromedriver.
So I am asuming twitter could not detect us.

The creators of undetected-chromedriver states that,
https://github.com/ultrafunkamsterdam/undetected-chromedriver/issues/824
Headless does make chromedriver more detectable try usng pyvirtualdisplay if you are on linux. otherwise on windows, there is a high chance that chromedriver will be detected in headless mode.

So, the HEADLESS factor is definately a thing to be considered if you are getting blocked.

They cannot get us yet, but they are strongly willing to.
So lets be prepared for it.


3. Twitter slows down, or does not respond if you are suspicious.

SLOW / SPIN happened in all of DEFAULT_CHROMEDRIVER.

This might just seem like bad news, but now you know that if your accounts are slow, there is something wrong with your methods.

Twitter knows you are doing something fishy.

I would consider this a pre-warning from twitter, and check if anything is leaking.

(GUESSWORK)
If you do know programming,
I can explain my suspisions of why this is happening.

Whenever we program a function, we tend to add the validation methods on the start of the function.
This is to prevent any errors from happening in the middle of the request itself.
But this is also true because we want as less traffic and lag in our servers.
When the request is not finished, we are using threads in our server, and if an SQL is in place, it can be a nightmare.

So I am guessing that twitter is trying to reduce server lags that is comming from bots.


4. Twitter goes paranoid mode on account creation.

I have had problems when I was trying the first batch of accounts,

I suspected some factors
1. the email address
2. the user-agent
3. unexpected amounts of traffic.
4. Automated process
5. The chromium browser itself

changing the factors when creating the accounts did make this work, but still, I kept all the security measures when creating. (changing ips, non headless, undetectable chromedriver)

We do not know what was the specific reason for the 200 accounts to get banned, but one thing we do know for sure is that twitter is paranoid when creating accounts.


PS.
I would strongly advise you to take my words with a grain of salt.
The test cases are too small, 7 days of testing is too short of a time period to know anything.
And there is a LOT of gesswork in my words.


Tempted to brag with motivational speech, and say stuff like 'you can do it' but we are all grown men and need to take care of ourself on our own.


If you are interested in my work,

I am currently trying to create a micro service architecture with ODROID machines in the hopes of automating it with bots.

I did previously create a proxy server with raspberry pi but had some problems with it, so I am switching to ODROID.

I am also creating a account automation method,
if I fail, I will share my failures with you.
If I succeed, I want to come back with a test of 1000+ accounts.


I am also extremly interested in,

puppeteer-extra-plugin-stealth,
https://www.npmjs.com/package/puppeteer-extra-plugin-stealthA lot of people claim that puppeteer is more stealthier than selenium. Would love to test that.

Appium, and adb
Some people are also claiming that they are using android VMs to automate their tasks. This is extremely interesting.
https://github.com/sickcodes/dock-droid


Thanks
Did have a lot of fun sharing with you guys, and hope to come back again!
GLHF and happy new year.
 
Last edited:
Interesting project, why you use browser instead of twitter API?

I was inspired by lucky.sparks.

And even if you were to create the bot, it would be quite hard to maintain it, because twitter would change their apis. Some would be deprecated.

But in my case, I only need to change the xpath.
 
thanks bro i learn a lot from those test you've done
keep going, i'm on a similar journey but on instagram using puppeteer and antidetect browser
tested 3 aged account no ban so far
 
thanks bro i learn a lot from those test you've done
keep going, i'm on a similar journey but on instagram using puppeteer and antidetect browser
tested 3 aged account no ban so far

Well thanks mate,
glad you found this helpful!
Good luck~
 
How can you rotate the IP? Just Turn off and Turn on ?
you gotta follow the guide and correct the mistakes in the guide (the guide is outdated and not complete).
you will need programing skills for this one (believe me I spent a lot of time doing it without any previous skills, learned quite a few things along the way)
 
Thanks mate,
Wish I would be able to create 1000+ accounts. It wont be easy though.

Good lucks to you too. XD
im sure you will find a way to do so :D

would you consider buying accounts?
you can find pretty cheap accounts that need confirmation via sms verifications or email (im currently doing this now with my old accounts)

I have about 1k aged accounts that need verifications via email
(I am manually loging in with antidetect browser,
logging into email then sms verify the email and then confirm the twitter email request,
login into the twitter account, do some manual actions,
then export the cookies into my automation software)

Then I will try to do high volume actions on those accounts and see how it goes.
Im very inpired by those indonesian accounts that do 1,000 actions per day :D,
but highly doubt that my accounts will be able to do a lot of actions since im using my own 4g proxies
and I live in a town of 1 million people (which is not a lot, considering densely populated areas are easier to not get detected,
since there is a lot more real traffic mixed with bot traffic)
 
A lot of useful info here. Are you going to try to just mass create tons of bot accounts, or are you just simply planning to automate some tasks en masse?
 
Back
Top