Twitter automization test (4 factors, 32 accounts)

[kptpiotr]

Nice thread! Lots of useful info here. I did a try with the twitterdub before and all of the accounts were suspended - I will probably make some tests once again with your tips!

 

[AiintoGo]

Do you randomise your actions

 

[dohyung97022]

Nice thread! Lots of useful info here. I did a try with the twitterdub before and all of the accounts were suspended - I will probably make some tests once again with your tips!

Well thanks~

Do you randomise your actions

Not in this threads experiment.
It just finds a follow button and follows.
Planning on doing that soon though.

 

[caidcmno123]

Well, the cost is the main factor.
I have used multilogin and incognition, camelio before.

1. Multilogin is too costly, and is not great to scale, since it has limited account number per plan.

2. Incognition is not frequently updated.

3. Camelio gets caught and is not as great to be honest.

I do not think these anti-detect browsers are that complicated to make. (Except for multilogin with webgl and graphics card manipulation, I don't know how they pulled that off.)

They use different profiles, cookies, useragents, ips, and some cases, graphics, but if you use a common graphics card, that is hard to detect.

Cost is not a problem i think, try some antidetect from China, its cheap and good i think. Some name like Bitbrowser, adspower... Plz test it.

 

[dohyung97022]

Cost is not a problem i think, try some antidetect from China, its cheap and good i think. Some name like Bitbrowser, adspower... Plz test it.

Sorry to say,
I do not have the time to do so.

I am currently doing another test.
https://www.blackhatworld.com/seo/twitter-automation-test-300-accounts-6-control-groups.1505424/
but even so,
I think undetected chromedriver, puppeteer extra stealth or even firefox with multiple profiles is sufficient enough for most use cases.