Experienced Specialists Who Know The Deal? (FollowLiker, Multiple Accounts, Proxies & Subnets)

Hi all -

Is there anybody battle-hardened who knows Twitter's tripwires?

These questions relate to Twitter accounts owned by others but then accessed, managed and automated by myself...

Scenario:
- FollowLiker running on VPS with dedicated, virgin proxies. Every Twitter account using a static unique proxy and unique subnet.
- Conservative settings applied in FollowLiker.
- Up to 1000 Twitter accounts accumulated over time in the same instance of FollowLiker.
- Tweets sent out to all Twitter accounts by me via a Business Buffer account (no proxy or VPS, same IP every time, Twitter accounts accessed and authorized by me) and tweet recycling system (Meet Edgar - no proxy or VPS, same IP every time, Twitter accounts accessed and authorized by me).
- Other parties possibly accessing the client Twitter accounts as normal (agencies or freelancers).
- Clients also accessing their Twitter accounts as normal.

Questions:
- Is there anything to watch out for including phone verification texts, 'accessing Twitter from a different location' messages or any other possible hiccups? Account suspension or bans are not an option.

- What would happen if a verified (blue tick) Twitter account manually removed their phone verification then re-added (to allow FollowLiker automation without receiving constant texts)? Would they lose their blue tick?

Looking forward to hearing from the pros.

Ninja Gab said:

Hi all -

Is there anybody battle-hardened who knows Twitter's tripwires?

These questions relate to Twitter accounts owned by others but then accessed, managed and automated by myself...

Scenario:
- FollowLiker running on VPS with dedicated, virgin proxies. Every Twitter account using a static unique proxy and unique subnet.
- Conservative settings applied in FollowLiker.
- Up to 1000 Twitter accounts accumulated over time in the same instance of FollowLiker.
- Tweets sent out to all Twitter accounts by me via a Business Buffer account (no proxy or VPS, same IP every time, Twitter accounts accessed and authorized by me) and tweet recycling system (Meet Edgar - no proxy or VPS, same IP every time, Twitter accounts accessed and authorized by me).
- Other parties possibly accessing the client Twitter accounts as normal (agencies or freelancers).
- Clients also accessing their Twitter accounts as normal.

Questions:
- Is there anything to watch out for including phone verification texts, 'accessing Twitter from a different location' messages or any other possible hiccups? Account suspension or bans are not an option.

- What would happen if a verified (blue tick) Twitter account manually removed their phone verification then re-added (to allow FollowLiker automation without receiving constant texts)? Would they lose their blue tick?

Looking forward to hearing from the pros.

Click to expand...

whats the idea behind that amount of accs doing the same ? Spam?

ot.jaime said:

whats the idea behind that amount of accs doing the same ? Spam?

Click to expand...

No, no spam at all Completely legit Twitter management for up to 1000 individual clients.

The accounts won't be performing any of the same tasks. Each will be uniquely set.

Ninja Gab said:

No, no spam at all Completely legit Twitter management for up to 1000 individual clients.

The accounts won't be performing any of the same tasks. Each will be uniquely set.

Click to expand...

the only thing i can think atm its the possibility of ban for the difference in ip with the twitter real owner, but you could fix that if you get proxies from the country of the owner (or area), and for the links i always use a shorter. call me paranoid but i use 358.dk because have a redirection of a couple of seconds and for me works fine

ot.jaime said:

the only thing i can think atm its the possibility of ban for the difference in ip with the twitter real owner, but you could fix that if you get proxies from the country of the owner (or area), and for the links i always use a shorter. call me paranoid but i use 358.dk because have a redirection of a couple of seconds and for me works fine

Click to expand...

Yeah that's what I was thinking too - so complicated. I wonder if same country but completely different area would trigger anything.....I guess it's extremely difficult to find a proxy supplier who can geo-target to that degree.....?

Thanks a lot for the 358.dk tip! It never hurts to be paranoid these days - I'd rather be that way than get caught out

Hopefully there's somebody here who has succeeded or failed with this sort of setup - will be great to know!

I've had a setup where 10 twitter accounts were working together. They would post non-duplicate filler content at full speed with basic text, no links or anything. Then the system would parse through tweets pulled via search term, filter out the spam and irrelevant, then use the remainder to directly reply to with a link. I was posting as fast as the API would allow (about 1 per 60 seconds) and putting out links just shy of the tripwire (3 content, 1 link, repeat.. 4 to be safe.. 2 to go fast for a few hours before your API gets write access removed). I found with a spacer of 3 tweets I could run safely but eventually my account would get the API keys locked and I would have to get new ones. No bans, just labor. Maybe once a week per account. After a few months of doing this mostly 24/7 they banned all the accounts in one sweep. They were all operating on the same IP and I expect they built up a number of spam reports. You can save yourself some proxy money and group some accounts together. That way if they ban accounts on a certain IP only one "basket" gets hit. Also avoid putting a users account on an IP in a different country. Keep US accounts in the US, etc. Depending on what you're doing you should be fine. If you are managing following / unfollowing check my post history for a writeup on tripwires regarding that (they are very picky about automation). Just don't get too aggressive or post too much duped/spun content and they wont care what you do. Check their TOS for clues.

If your application is whitehate and doesn't break the TOS, or if you aren't sure, I would suggest reaching out to Twitter about your service. They will happily tell you if your app is ok by them. Just maybe don't include links to your site/product/main accounts in case they don't like what you have to say. Having twitter whitelist your application can be a massive help.

Goodluck!

Thanks a lot for that in-depth response @StealthLeads!

The stuff going out from these accounts won't be spammy but helpful to audiences - only 20-30% of posts will contain links pointing to the client sites and they won't be promotional. The only social actions against the Twitter TOS will be automated following/unfollowing, liking and retweeting. But I'm talking max 300 follows/unfollows per day with good breathing space inbetween and only 10 - 30 likes and retweets per day.

Good to know about location of IPs...

So:

1) Use dedicated proxies that have the same country IP as where the client is based
2) Buy proxies that each have unique subnets (only 1x proxy subnet per client)
2) Use those same individual proxies on Firefox to authorise Buffer and any other scheduling tools that need to access client Twitter accounts, one-by-one
3) Apply conservative FollowLiker settings

Should that be all good? Even if other 100% whitehat agencies / teams (hired by the clients) access their accounts from other areas / countries?

I'm also wondering how this would work with verified Twitter accounts as I know to first run FollowLiker you have to turn off phone verification then re-enable. Worried if somebody with a verified account would lose their blue tick if they disabled phone verification

Nothing's ever simple is it