Twitter automization test (4 factors, 32 accounts)

dohyung97022 said:
What was your experience when you automated? How much retweets and or follows resulted in a ban?

Does your automation tool use the webs requests? Or the apps http requests?

Did you try 200+ retweets in the app?
Does manual retweet make you get banned?

I have not done a retweet limit test,
This is my first test on twitter XD
I look like an expert, but I am not.

However, if manual app retweets does not ban you in twitter,
It is possible.
Click to expand...
When I suddenly started doing a lot more traffic than before I got banned.

first I was doing 2-3 follows, likes and retweets per day
then suddenly I was doing 30 follows, likes and retweets per day and in 3 days I got banned.

I was using twitterdub, which uses http requests

But it also might be the account quality and proxies fault (havent done enough isolated testing to say for sure that I found the reason)

I manually did 50 retweets 4 days in a row on my mobile app on 4G and have not got blocked or suspended
(but then again it was only one account, so it is not enough to say any things for certain)

I wonder if these accounts are somehow making use of twitter app,
but I am not sure if twitter mobile app automation can even be made successfully.
 
Advertise on BHW
Bakidaki said:
When I suddenly started doing a lot more traffic than before I got banned.

first I was doing 2-3 follows, likes and retweets per day
then suddenly I was doing 30 follows, likes and retweets per day and in 3 days I got banned.

I was using twitterdub, which uses http requests

But it also might be the account quality and proxies fault (havent done enough isolated testing to say for sure that I found the reason)

I manually did 50 retweets 4 days in a row on my mobile app on 4G and have not got blocked or suspended
(but then again it was only one account, so it is not enough to say any things for certain)

I wonder if these accounts are somehow making use of twitter app,
but I am not sure if twitter mobile app automation can even be made successfully.
Click to expand...

I cannot say any bogus claims because I do not know anything about twitterdub,
did not buy it before, I do not know the inner workings of it.
Even if I did know, I do not know what caused the ban.

I can give you some actions to 200+ retweets. (If it is possible)
I thought of 3 actions you can take.

1. Add more accounts in twitterdub.

So, what you want is more actions, yes?
I have checked twitterdubs website, and they do not limit the amout of accounts you can use.

2-3 -> 30 was a bit drastic change,
so I will asume you can do 10 retweets and get away with it.
Add 20 accounts in twitterdub.

What is your bottlekneck not making you do so?

Account creation?
I would not consider it to be a bottlekneck
It is a limited resource yes,
But if you create one account and can use it for years, you need to create it first, but do nothing afterwards.

4G proxys?
Yes this is a bottlekneck, but is the same even if you can do 200+ retweets on one account.
If 1 retweet took 1 minutes,
1 account * 200 retweets = 200 minutes.
20 accounts * 10 retweets = 200 minutes.

You need the same time to use 4G proxies.
Login time and 4G rotation would need to be considered,
but it would be like 10 seconds max per account change.

2. Appium

If you have manually tested in the app, and got away with it,
(For at least 1 week with different testcases)
you can program with appium.

Appium is a mobile app automation tool.

But still they could have created security measures to block this as well,
so if you do not test this or try it, we will never know.


3. Learn programming (BEST)

But I know nobody wants to chose option 3. :weep:
 
Last edited:
Test Report 3


Today,
no abnormality was found.



TEST RESULTS

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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


Logs if you are paranoid.
https://drive.google.com/file/d/14vV6eywau6w11b_qIEmyYgaRTNsf3rCq/view?usp=share_link
You might see some different follow actions,
but that is just because my code is shit.


Thoughts
Really not much to say about the results today.


Additional Tests
Gogol said:
That could be the same with your results too op. Perhaps keep an account with no activity as another case, and see if gets banned.
Click to expand...

Test cases did not have a problem when performing action.

Condition
Default chrome
No automation attached
New chrome profile
No action after creation
Opened after 3 days

CASE
https://twitter.com/25blackhatworldhttps://twitter.com/26blackhatworld
Maybe something leaked in your case on creation? But again you said that you did it on a device.
Twitter definitely goes on hardcore mode when account creation.


PS.
If you used my code and added the GIF creation function,
it may not seem smooth enough.

In programming, there is a thing called Thread and Process.
Think of them as a program running in the background of a main program.

So while the main program is automating the browser, the background program is capturing the pictures.

So the code would be

Python: 
class ThreadJob(threading.Thread):
    def __init__(self, method, interval: float, method_args: list = [], daemon: bool = True, *args, **kwargs):
        self.method = method
        self.method_args = method_args
        self.event = threading.Event()
        self.interval = interval
        super(ThreadJob, self).__init__(target=method, daemon=daemon, *args, **kwargs)

    def run(self):
        while not self.event.wait(self.interval):
            self.method(*self.method_args)

Add this after the driver has booted.
Python: 
ThreadJob(method=capture_picture_log, interval=0.5).start()

capture_picture_log would be the function that captures the browser.
interval is the time you want the sub program to wait until it acts again.


Also Funny thing was inspected,
스크린샷 2022-12-26 오후 2.51.03.png


스크린샷 2022-12-26 오후 2.50.43.png


Because the new view functionality was implemented by Elon,
Some tests could not click on the "People who liked" button because of a UI error.
Reran the program if this happened XD

Anyways,
If nothing happens until the 4th test,
I will crank up the follow amount to 20 in the 5th.

We do not want too much change on our test,
If we kill all the accounts at once, we learn less.

The best case would be is when only a portion gets banned.
For example, if manual actions are not banned and automated actions are banned,
we know that twitter detects automated button clicks.


Thanks for the support.
 
Last edited:
Test Report 4


Another day with no abnormalities.
I do have a additional test that was quite interesting in case you get bored.


TEST RESULTS

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

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

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

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

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

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

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

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

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

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

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

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

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

{REAL_CHROMEDRIVER}_{MANUAL}_{PROFILED}_{NON_HEADLESS}
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

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

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

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

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

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

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

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

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


GIF logs for nerds.
https://drive.google.com/file/d/1GXPfyvy88M-zVuyXoTxrTFXvxJ3OzXv7/view?usp=share_link

Thoughts


Additional Tests

I was playing around with the additional accounts that I have made, and found out something interesting.

So my motivations was to do as much suspicious actions as possible until twitter bans you.

I have used surfshark VPN on this account.
Using public VPNs on accounts is a extremely stupid idea,
it is like a criminal going into a police station.
(Porn sites are different, Koreans or Chinese people needs VPNs to access)

Of course I was blocked when first accessing twitter.com.


But when I checked the profile https://twitter.com/21blackhatworld twitter did not actively block the account.

Alright, I thought twitter only blocked the ip address of the VPN upon access.

But when I have turned off the VPN, It still would not go into twitter.

Interestingly, when I removed the profile and cookies, It worked like nothing ever happened. Did not ask for anything, did not show any popup, nothing.

So what is happening?

As I have told you in Test report 2,
twitter has security code on first access.

So whats happening is,
VPN -> twitter security code -> Block access -> set Profile, cookies as untrustworthy

When I have set VPN off,
Untrustworthy Profile, cookies -> twitter security code -> Block access

Twitter is tweaking some settings in profiles or cookies that this is not to be trusted, or most likely saving it in their database or cache in order to block it.

But why did nothing happen to this account?

Lets say, I want to be a hacker.
I want to hack the shit out of your computer, and I had access to your computer with a malware that you installed.

I can grab your keytypes, but most operating systems catch this on install.
I can grab your internet signals but that is encrypted.
Or, I can send your chrome profile folder to my server.

Twitter in this situation, would want to block only the hacker, not the user wouldn't they?

So twitter is thinking this profile is hacked, and therefor only blocks the profile but not the account.

So what?

If twitter keeps showing you this for some reason,


They might flagged your profile, cookies as untrustworthy.
Delete your profiles, cookies and try loging in again.

They could flag your profile as untrustworthy for different reasons than using a VPN.


PS.

Hope everything works out for you.
 
Last edited:
Love that you are doing this work and publishing it here publicly available and asking for opinions and discussion from people with similar experience,
since most social media managing agencies also do this investigative type work for their use,
but they dont publish it anywhere, so they keep the edge above the competition (which makes sense business wise)

this way you are helping yourself with getting other peoples input and experience to help you do even better and deeper testing for twitter limits
and others by making all this testing public to the whole forum.

keep it up champ :D
 
DropVS said:
Very good thread! Keep doing that!
Click to expand...
Thanks mate.

Bakidaki said:
Love that you are doing this work and publishing it here publicly available and asking for opinions and discussion from people with similar experience,
since most social media managing agencies also do this investigative type work for their use,
but they dont publish it anywhere, so they keep the edge above the competition (which makes sense business wise)

this way you are helping yourself with getting other peoples input and experience to help you do even better and deeper testing for twitter limits
and others by making all this testing public to the whole forum.
Click to expand...
When I keep it to myself, I tend to become more and more lazy.
I forgot a lot of things, and thought I was losing my mind.

And the claims I am making and sharing is actually shit quality. :p

Some are facts, and I try to be as fact driven as possible,
but most is guesswork. (me trying to sound like a smartass)

Telling others just because 1 in 30 accounts had some strange effect once is too small as a dataset.

Also 30 accounts is like a drop of water in a ocean to twitter.
No wonder I don't get banned.
Heck, I did not even change my user-agent in all the cases.


I thought of shortening this test and come back with a different test with 1000+ accounts.
I cannot do tests write reports and code semi automated register methods at the same time.

I will put less opinions and guesswork on each tests.
And only speak when I am certain.
I did say that I will do 10+ days of testing, but I am leaning towards 7.

Sorry about that.

Bakidaki said:
keep it up champ :D
Click to expand...

And thanks~ XD
 
Last edited:
Nice stuff here!

Are you having any issues with the captcha? I was automating retweets a few months back and using DBC for it without issues.

Keep it up, following!
 
SERPkiller said:
Are you having any issues with the captcha? I was automating retweets a few months back and using DBC for it without issues.
Click to expand...

Holy smokes I am a fool...
I was just searching DBC, and saw the use of proxies.

  • The proxy parameter is optional, but we strongly recommend to use one to prevent token rejection by the provided page due to inconsistencies between the IP that solved the captcha (ours if no proxy is provided) and the IP that submitted the Funcaptcha for verification (yours).
    Note: if proxy is provided, proxytype is a required parameter.

I did not use proxies when automating registers with 2captcha.

And thought it was the geolocations fault.

Xd
 
dohyung97022 said:
Holy smokes I am a fool...
I was just searching DBC, and saw the use of proxies.

  • The proxy parameter is optional, but we strongly recommend to use one to prevent token rejection by the provided page due to inconsistencies between the IP that solved the captcha (ours if no proxy is provided) and the IP that submitted the Funcaptcha for verification (yours).
    Note: if proxy is provided, proxytype is a required parameter.

I did not use proxies when automating registers with 2captcha.

And thought it was the geolocations fault.

Xd
Click to expand...
yea I forgot to mention to you that twitterdub has the option to assign proxies for solving captchas with 2captcha :D

that is what makes it work probably,
hopefully you will find a way to solve them this way.
 
Test Report 5


Did crank up the follow amounts to 20.
Surprisingly no abnormalities was found.


TEST RESULTS

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

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

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

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

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

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

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

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

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

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

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

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

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

{REAL_CHROMEDRIVER}_{MANUAL}_{PROFILED}_{NON_HEADLESS}
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

{DEFAULT_CHROMEDRIVER}_{AUTOMATION}_{PROFILED}_{HEADLESS}
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

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

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

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

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

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

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


Logs for nerds.
https://drive.google.com/file/d/1SIe-9y4q1OxeU-lzjLKfnSHmRsu0spBT/view?usp=share_link


You might see case 1 acting strangely,
but that is just my code. I think...?
 
what way do the accounts choose to follow someone?

do you give them a list to follow or maybe follow suggested accounts on the right or a different way?


also do you supply them with links to tweets to retweet or do you make them retweet random tweets on their timeline?

interested to know, if it isnt a secret ofc.


amazing results, even tho the amount tested is only 30 accounts its still nice that young accounts can do 20 follows without any issues.


also what is your useragent? is it the same on all accounts or did you do some randomizing?

this is the useragent I am using on all my accounts, and I am not sure if I should start randomizing it because I plan to use about a 1000 accounts in the near future.


Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/108.0.0.0 Safari/537.36
 
Bakidaki said:
what way do the accounts choose to follow someone?

do you give them a list to follow or maybe follow suggested accounts on the right or a different way?


also do you supply them with links to tweets to retweet or do you make them retweet random tweets on their timeline?
Click to expand...

My accounts cick on the first post -> clicks the 'People who liked button' -> follows
But if any of the steps fails, it just goes and does the next step.
No retweets, no links, no likes just follows.

Bakidaki said:
also what is your useragent? is it the same on all accounts or did you do some randomizing?
Click to expand...

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.
https://github.com/ultrafunkamsterdam/undetected-chromedriver/issues/689
Might be different in your case because twitterdub uses web requests.

Abitotop said:
Interesting, I'm following
Click to expand...

Thanks~ will try to keep it up.
 
Last edited:
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!
 
Advertise on BHW
You must log in or register to reply here.
Sign up now!

Main Menu

Home Main Forum List Black Hat SEO White Hat SEO BHW Newbie Guide Blogging Black Hat Tools Social Media Downloads

Marketplace

Account Selling Content / Copywriting EBooks / Methods Hosting Misc Proxies For Sale SEO - Link building SEO - Packages Social Media Social Media - Panels Web Design More

Making Money

Affiliate Programs Hire a Freelancer IM Journeys Making Money Pay Per Click Site Flipping Want to Buy

BlackHat World

Dispute Resolution Forum Suggestions & Feedback Introductions Lounge
Back
Top