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.