My guess is that when variables aren’t upto date on Apis, The api keeps doing actions which might earlier been liking etc. , but since the interface has changed, you may actually be repeatedly doing a sorten action which isn’t necessarely your intention?
Again at this point this is my guess
2 Likes
It kinda does. I have noticed they implement those updates in batches - some accounts to get it earlier then others thats why the block could hit once they update the version of the interface on that specific account.
3 Likes
Exactly my point if I understand you correct.
2 Likes
What do you mean by change the finger print?
This might be logical with EB, but via API it’s only code no visual involved and if it was true even 1 follow will not get executed!!
What seems more probable is that IG find patterns to identify ‘‘false’’ Devices call and blacklist them to do actions at certain points, this explains why we can do actions over and over again everytime we reset the device ID!
2 Likes
This is exactly what I meant. If the api does actions which results in repeated fails, insta algo blocks down the profile. Isn’t this a possibility?
1 Like
Guys above wrote really wise things, that someone from IG can read the messages, can we make the convo private?
If it was the case we would got notifications in jarvee, I have some exception accs running VIA API for days now with no issue, I’m trying to figure out why that but nothing for now, I will update as soon as I get something relevant!
Your theory could be true if we think of gateways the a APIs calls but nothing to back up this for the moment!
2 Likes
Please do. Atleast we have found an extra thing to keep an eye on, which could eventually save us from speculations. Then we can concentrate on breaking the code.
If Jarvee is programmed to observe, identefy and announce the recent fails occuring due to new interface of IG, we will be notified. But if these matters aren’t considered yet the bot just believes it is doing the correct thing asual and therefor does not react to to new errors?
But please keep us updated. Would be a great step forward
2 Likes
What do you mean ? Instagram employee knows how to create an mpsocial account i think
1 Like
BOTTOM LINE
Should we stop automation for now ?
Should we only like feed and story watch ?
I know I am on a test for 3 different types of bots beside Jarvee, which is of course harmed.
One of them is a chrome non headless simulation which I have “only” 10% follow block (been using for over 2 years) while jarvee have much more.
I do think it is a combination of API issues and some bot detection - IG implemented it all at once so we will get confused.
5 Likes
Instagram new like block? I ran likes on my accounts 1-2/day to get some other actions in for the past month everything was fine. Starting this weekend, more like blocks on accounts.
I also see that a large part of companies have a problem with adding likes.
Anyone can tell which proxy application they are using ? maybe some new test for DNS LEAK or HEADERS leak in ccproxy or squid ?
3proxy is used by most!
Has anyone checked the observations on a captivate application etc.?
It’s ok with me and you can follow.
I did not check all accounts, just a pair.
What this? (what software do you mean)
Spent a lot of tests in recent days. The problem arises not because of the device ID, but only because of the API used. If you change the API account, the problem goes away for a while. This is equivalent to logging out of the account and re-logging within the same device. Such a combination of logic actions is much safer than a continuous change of technical data.
8 Likes
Mobile software.
Automatic observation.
1 Like
Just to clarify - Are you suggesting that if you logout of Jarvee and log back in, that it will change the API?