Instagram Botting PSA

Borilla said:

That's 100% not the problem.
I myself and a lot of other people still run accounts on non resi ips.

Click to expand...

Yes, I do too, but the root issue seems to be non resi ips. I'm inclined to believe the theory that Instagram has us in their crosshairs and is just having fun at this point. For reference, how many accounts are you running and how many have been looped?

Lets take a scientific approach to this and eliminate some assumptions -

I have noticed all this upon countless hours of research-
1. It does not have to do at all with proxies ALONE. The update/bug is NOT dependent on this factor.
Reason - You can try yourself. Login via browser using VPN. I doubt you will face a loop. I have done this with 17 accounts so far and I put each account via different multiple proxies around the world. One time I get check. Next time I'm free. I am able to do every action with no errors.
END

2. It does not have to do with bots ALONE. If you host a bot on your local computer and execute your scripts it seems to work.
Reason - You can try yourself first. I ran bot via API login for an account that is already signed within home IP - bot working 100% in this case. Local hosted bots on Resident Proxy is working.
END

3. Changing user agents is not working. This would have been such an easy fix if this was the case. Everyone would do it. All bots would update this within minutes as this fix doesn't take more than few seconds. So it is not ENTIRELY dependent on type of user agent you are using.
REASON - Obvious. All bots would have come up with update if this was the case.
I have myself tried various web + mobile + FAKE agents. No consistency so far.
END

4. It doesn't have to do with aged / fresh / botted / handgrown accounts. I have tried logging in every type of accounts. Even handgrown accounts that NEVER were botted are unable to bypass the verification loop.
END

Beyond this - if there is anything - let us discuss and work out how to crack this.

My methods (working on these currently)(will update soon)
1. Update bot to make verification within the script. So that I enter the 6 digit code within the bot itself while fully logged out of the IG account everywhere. Bot does the verification by its own. This is the ONLY way out for me.
2. Possible - Crack latest version of API and then try.

Yeehaw22 said:

While I haven't been able to prove anything exhaustively, I misstated findings in my original post and it seems that one misstatement has been accepted as fact by them.

Click to expand...

Yeehaw22 said:

- If you are running a business on top of FollowLiker, give your customers their money back once you hit the infinite loop and close down your business

Click to expand...

Dude that is exactly the problem here.
You are giving out horrible advice as facts and people take you seriously as you already noticed.

Yeehaw22 said:

The one thing I will say is that there is no evidence anywhere on the internet that people with resi IPs and whitehat accounts are affected. Since basically everyone bots (and the people who pay for these services have no idea what's going on), it's likely that seemingly legit people who signed up for services like mine are just complaining because they don't understand what the service they've purchased is doing.
I understand the motivation behind raining on my parade, but I see nothing of value from anyone criticizing me. A lot of the clueless selfish people on the forum fishing for answers could learn a lot from the way engineers handle problems on open source projects, even ones who apparently see us as the enemy.

Click to expand...

The value is in stopp spreading fake facts.
There is evidence and even the post that no one else could have that problem is sheer dumb.
Just because you don't have acces to information doesn't mean it can't exist.

Points:
Non botting people are affected
People with residential ips are affected
panels are still working
Not all non-residential-proxies are affected

I am not interested in to flaming this thread but its important not to spread fake theory as facts.
As it already backfired on you like you stated before.
I have no problem with you as a person so no point in keeping this going.


xWGx is doing a great job at testing this out and already disproving some of your theory.
So lets focus on facts.

Borilla said:

Dude that is exactly the problem here.
You are giving out horrible advice as facts and people take you seriously as you already noticed.


The value is in stopp spreading fake facts.
There is evidence and even the post that no one else could have that problem is sheer dumb.
Just because you don't have acces to information doesn't mean it can't exist.

Points:
Non botting people are affected
People with residential ips are affected
panels are still working
Not all non-residential-proxies are affected

I am not interested in to flaming this thread but its important not to spread fake theory as facts.
As it already backfired on you like you stated before.
I have no problem with you as a person so no point in keeping this going.


https://www.blackhatworld.com/members/xwgx.1113632/ is doing a great job at testing this out and already disproving some of your theory.
So lets focus on facts.

Click to expand...

Partner, I'm having a rip-roaring good time here. Half the fun of running a small business is dealing with conflict. When handling with my herd of cattle, sometimes I end up bruised, battered... sometimes even gored. I will not apologize for my itchy trigger finger in this arena.

Maybe nothing has backfired on me. Maybe the rascals on Github went to sleep thinking they were winners because I am the only player of note making these claims with hundreds of accounts under my belt. Maybe I just get off on fibbin' while taking pulls from my flask.

I have reached out to some of my customers who have been caught in the loop, explained the situation, and have processed two refunds for this month as a result. Because I am a god-fearing man. I see no evidence anywhere that non-botting people are affected, or that people with residential ips are affected. It's farcical. I said in the other thread I am running 175ish right now on non-residential proxies and have been for several hours with none getting stuck in the loop. I don't have an explanation for panels but I find it impossible that some weren't affected.

Yeehaw22 said:

Partner, I'm having a rip-roaring good time here. Half the fun of running a small business is dealing with conflict. When handling with my herd of cattle, sometimes I end up bruised, battered... sometimes even gored. I will not apologize for my itchy trigger finger in this arena.

Maybe nothing has backfired on me. Maybe the rascals on Github went to sleep thinking they were winners because I am the only player of note making these claims with hundreds of accounts under my belt. Maybe I just get off on fibbin' while taking pulls from my flask.

I have reached out to some of my customers who have been caught in the loop, explained the situation, and have processed two refunds for this month as a result. Because I am a god-fearing man. I see no evidence anywhere that non-botting people are affected, or that people with residential ips are affected. It's farcical. I said in the other thread I am running 175ish right now on non-residential proxies and have been for several hours with none getting stuck in the loop. I don't have an explanation for panels but I find it impossible that some weren't affected.

Click to expand...

5+ hours now of running 175ish accounts. Non-residential proxies. No additional accounts of mine were "picked off" after that initial scare.


YEE HAW!

Yeehaw22 said:

5+ hours now of running 175ish accounts. Non-residential proxies. No additional accounts of mine were "picked off" after that initial scare.


YEE HAW!

Click to expand...

Where are you buying non-residential proxies?

xWGx said:

I think I'm close to understanding the issue.
PLEASE NOTE THIS IS ALL TRIAL AND ERROR AND I MIGHT BE COMPLETELY WRONG.
Here is what I can conclude upon 72 hours continuous testing by myself and a team of coders.

1. API Login + Local Hosted Bot (Local IP/Home IP)= SUCCESS
2. Web/App Direct Login + ANY PROXY (Any freaking proxy) = SUCCESS

3. API Login (Server hosted bot) + Proxy of ANY SORT (Any freaking proxy) = FAIL

I can conclude this pattern time and time again. I can fuck around with proxies when logging in via browser. As I said - able to login to same account on 3 proxies via browser without any issues. Able to login (API) via FL when using home IP.

A dozen people over Git Hub having no problem with self hosted local bots. Only when they go on server it raises the verification loop. Hence my conclusion.

The only way moving forward is to find a provider for stable clean Residential IPs that are static. Lets see. Going to give this a try. If this works then this might be the only way out.

I still feel this is some sort of bug. I pray it is.

Eitherways if the Russian panels have fixed it without a hiccup and are able to stay logged in to 500k+ accounts then this is not an anti-spam update to me.

Click to expand...

this i disagree, i used a fresh account on one of my proxies. Works perfect. Use the same ip for another account which has not been botted before, got the verification loop.

Yeehaw22 said:

Partner, I'm having a rip-roaring good time here. Half the fun of running a small business is dealing with conflict. When handling with my herd of cattle, sometimes I end up bruised, battered... sometimes even gored. I will not apologize for my itchy trigger finger in this arena.

Maybe nothing has backfired on me. Maybe the rascals on Github went to sleep thinking they were winners because I am the only player of note making these claims with hundreds of accounts under my belt. Maybe I just get off on fibbin' while taking pulls from my flask.

I have reached out to some of my customers who have been caught in the loop, explained the situation, and have processed two refunds for this month as a result. Because I am a god-fearing man. I see no evidence anywhere that non-botting people are affected, or that people with residential ips are affected. It's farcical. I said in the other thread I am running 175ish right now on non-residential proxies and have been for several hours with none getting stuck in the loop. I don't have an explanation for panels but I find it impossible that some weren't affected.

Click to expand...

i use residential ip for one of the accounts and its affected

Noel Tan said:

this i disagree, i used a fresh account on one of my proxies. Works perfect. Use the same ip for another account which has not been botted before, got the verification loop.

Click to expand...

Same.

Hey guys, any news? I run a small agency, added 15 accounts to followliker. No problems at all for a few months. Now my accounts cant get passed the verifications..
I tried several dedicated proxies. Didn't help. I run followliker on a vps. I tried followliker on my own laptop, with no proxy it worked there. It is weird.
Does anyone know how to get passed this issue? I read about residential proxies, where can i get good ones? I want my clients to get some growth.

Hopefully this is a bug on the side of instagram and hopefully it will be fixed. But than once again.. Why would they fix it. This has the good outcome for them. isnt it?

Please would love an answer on how to solve this temporarily. You guys are amazing!

Howdy,

Sorry for the dead air. I have many vocations in addition to cattle ranching. All of my accounts ran fine for almost three full days then today about 10 got stuck in the loop all in quick succession. My new hypothesis is that it might not have a whole lot to do with proxies (though only my non-residentials have been affected) and might just be better general bot detection. For as much of a cash cow as this business is, I have to be out on the ranch at 6 most mornings and don't return until well after dusk so it's been impossible for me to test to the fullest extent. I have spoke with people who run operations much larger than mine and either everyone is playing their cards close to their chests or there is no viable solution. I think that any of the sites claiming that this is an error on Instagram's side are telling big fat fibs. I'm not convinced in any direction, though I have paused my recurring billing and am processing more refunds now.

To those who criticize my vocation--tears trickle down my leathery cheeks. But I cry because I was raised in the great US of A. My pappy taught me to pursuit any opportunity that came my way with the vigor of a red-haired sonofabitch. And, by the grace of god, I did.

YEE HAW!

@Yeehaw22 Hi mate, what activity were you doing on the 3 accounts? follows? likes? and at what rate?

Anyone discovered the solution for this?

Yeehaw22 said:

As I referenced many months ago, I have built a program that rivals some of the best out there

Click to expand...

Yeehaw22 said:

We stand outsmarted by Instagram.

Click to expand...

Lol'd

It's all good in YellowCat Labs