Safest & Easiest Way To Use Twitterdub
Posted: Thu Sep 16, 2021 1:59 am
Hi Martin,
First of all congrats on what looks like a brilliant piece of software, wish I had given this a try earlier.
However, I feel that the videos are quite hard to follow and difficult to understand, as the sound quality is quite poor in some of them.
So I've been trying to play around a bit but it's not clear what is the best and safest route and I'd like to share my thoughts and maybe you can point me in the right direction?
1. Looking at the log it looks like there is quite a bit of scraping going on, especially when setting tight filters. I wonder how safe this is with Twitter and if it would be better to separate the scraping part altogether?
I'm thinking that maybe I'd hire someone to scrape say:
"All followers of these 20 accounts that have been active in the last 14 days and either liked or commented on that person's tweet(s) and speaks English and is of x gender."
2. I would then end up with a fairly large userlist of 10s of thousands of profiles, and I could manually check some of these randomly to see that the profiles match my criteria.
Now my question is basically this
3. Would it be safer for me to upload a big list of users like this to Twitterdub and instead of having a very extensive scraping process inside Twitterdub my main accounts can simply go to these thousands of target profiles one by one and like a few of their last tweets and then follow them.
Or does it actually look more suspicious to Twitter if a user heads straight to a profile to like a few tweets and then follow?
Basically I'm trying to find the best way to use what seems to be a very complex piece of software with the ability to filter in a very granular way, but without all that filtering and scraping looking like a bot?
ALTERNATIVELY...
4. Would it be possible to pay extra for some support and give you the criteria we are looking for, and you to simply do a step-by-step walk through of every setting we should use that will likely be safe for new'ish accounts on good proxies?
What I mean is, would it be possible for us to say for example:
"a) These are the 10 target accounts.
b) We would like to follow users of those accounts who fit the following criteria (filtering?) and randomly like 1-3 tweets of those followers.
c) After randomly liking we would also like to randomly follow 30% of those profiles we liked (pre-action?).
c) These are the 4 filters we would like to use for all accounts that we like and follow from the above target accounts....
d) We would also like our accounts to also tweet randomly 3-5 times per day from this list (one list for each account) between these hours.
e) We would like to send a DM with the following spintax to all our followers on each account at these select times.
f) We will only use one account per proxy and we only want the program to do one action on each account at any one time.
g) We would like to do a max of say 140 tweets for any one profile per day, but increase with 5% per day until reaching 275 likes per day/account.
h) We would like to follow a max off say 90 accounts per day, but increase with 5% per day until reaching 180 follows per day.
i) Once every 3 days each account should take a 22 hour break.
j) Account 1 has the following "working hours" that it can bot, Account 2 these, Account 3 these and so on. Bot never works outside hours."
Something like that, where we basically come up with a custom list that suits us and you/your team makes a PDF (or video) or something going over each setting we need to achieve the above reults? Of course I understand that this would come at extra cost and be outside the normal support, but that's fine.
I just feel that with the current instructions and it being rather difficult to hear some of the videos, and without a user guide that details each function related to each module (and how the settings in each may affect each other) there is a lot of room for error, and if we can pay say $150 for someone to do a simple step-by-step guide for JUST the functions we need/want that would help a lot and save us two weeks of trying to learn, test and lose a number of accounts and burn proxies because we ran things too fast or too many processes were running at once etc.
Any advice on the best way forward would be appreciated, but the software looks amazing and you have really thought of every detail anyone could want in a Twitter bot it seems!
First of all congrats on what looks like a brilliant piece of software, wish I had given this a try earlier.
However, I feel that the videos are quite hard to follow and difficult to understand, as the sound quality is quite poor in some of them.
So I've been trying to play around a bit but it's not clear what is the best and safest route and I'd like to share my thoughts and maybe you can point me in the right direction?
1. Looking at the log it looks like there is quite a bit of scraping going on, especially when setting tight filters. I wonder how safe this is with Twitter and if it would be better to separate the scraping part altogether?
I'm thinking that maybe I'd hire someone to scrape say:
"All followers of these 20 accounts that have been active in the last 14 days and either liked or commented on that person's tweet(s) and speaks English and is of x gender."
2. I would then end up with a fairly large userlist of 10s of thousands of profiles, and I could manually check some of these randomly to see that the profiles match my criteria.
Now my question is basically this
3. Would it be safer for me to upload a big list of users like this to Twitterdub and instead of having a very extensive scraping process inside Twitterdub my main accounts can simply go to these thousands of target profiles one by one and like a few of their last tweets and then follow them.
Or does it actually look more suspicious to Twitter if a user heads straight to a profile to like a few tweets and then follow?
Basically I'm trying to find the best way to use what seems to be a very complex piece of software with the ability to filter in a very granular way, but without all that filtering and scraping looking like a bot?
ALTERNATIVELY...
4. Would it be possible to pay extra for some support and give you the criteria we are looking for, and you to simply do a step-by-step walk through of every setting we should use that will likely be safe for new'ish accounts on good proxies?
What I mean is, would it be possible for us to say for example:
"a) These are the 10 target accounts.
b) We would like to follow users of those accounts who fit the following criteria (filtering?) and randomly like 1-3 tweets of those followers.
c) After randomly liking we would also like to randomly follow 30% of those profiles we liked (pre-action?).
c) These are the 4 filters we would like to use for all accounts that we like and follow from the above target accounts....
d) We would also like our accounts to also tweet randomly 3-5 times per day from this list (one list for each account) between these hours.
e) We would like to send a DM with the following spintax to all our followers on each account at these select times.
f) We will only use one account per proxy and we only want the program to do one action on each account at any one time.
g) We would like to do a max of say 140 tweets for any one profile per day, but increase with 5% per day until reaching 275 likes per day/account.
h) We would like to follow a max off say 90 accounts per day, but increase with 5% per day until reaching 180 follows per day.
i) Once every 3 days each account should take a 22 hour break.
j) Account 1 has the following "working hours" that it can bot, Account 2 these, Account 3 these and so on. Bot never works outside hours."
Something like that, where we basically come up with a custom list that suits us and you/your team makes a PDF (or video) or something going over each setting we need to achieve the above reults? Of course I understand that this would come at extra cost and be outside the normal support, but that's fine.
I just feel that with the current instructions and it being rather difficult to hear some of the videos, and without a user guide that details each function related to each module (and how the settings in each may affect each other) there is a lot of room for error, and if we can pay say $150 for someone to do a simple step-by-step guide for JUST the functions we need/want that would help a lot and save us two weeks of trying to learn, test and lose a number of accounts and burn proxies because we ran things too fast or too many processes were running at once etc.
Any advice on the best way forward would be appreciated, but the software looks amazing and you have really thought of every detail anyone could want in a Twitter bot it seems!