Follow Block On EB & API - Help

Firstly you cannot assume "what was working still is". Your proxies COULD be the issue. They did work, that we can say. They might not now. IG is not static, you not botting a static target, but a dynamic target that is always improving. Blocking new IPs, new ranges. That is where I would first look.

Not always, but nearly always, proxies are the issue. People will swear to me I am wrong, their proxies are good. But usually it is the proxies.

Same with your settings, seem reasonable, but again all we can see is "this used to work" maybe it doesn't know for your pattern (accounts + proxy).

That said, I know many customers still hitting limits like you state (apart from unfollows, not sure how you can unfollow 160 a day when only follow 20-80... but that is a maths problem not a bot problem) so it is most definitely possible.

Just 2 options 1: you settings and 2: your proxy.
Get a 4G proxy and test! .. AND DO NOT USE ACCOUNT THAT HAS BEEN SPAMMED ALREADY FOR YOUR TEST!

rootjazz said:

Firstly you cannot assume "what was working still is". Your proxies COULD be the issue. They did work, that we can say. They might not now. IG is not static, you not botting a static target, but a dynamic target that is always improving. Blocking new IPs, new ranges. That is where I would first look.

Not always, but nearly always, proxies are the issue. People will swear to me I am wrong, their proxies are good. But usually it is the proxies.

Same with your settings, seem reasonable, but again all we can see is "this used to work" maybe it doesn't know for your pattern (accounts + proxy).

That said, I know many customers still hitting limits like you state (apart from unfollows, not sure how you can unfollow 160 a day when only follow 20-80... but that is a maths problem not a bot problem) so it is most definitely possible.

Click to expand...

Thanks for your reply.

I've heard that private bots are working, or working better than public bots - so maybe it is an API issue.

My unfollow settings are different for each account (as well as all my settings, they differ slightly for each). I have my unfollows set higher than my followers, but the unfollow action stops if there's not enough scraped accounts for my settings.

I'm fairly certain my proxies are fine. All users of the bot I am using are facing the same issue and everyone's proxy provider and type is different. The team behind the bot has also acknowledged the issue so we're hoping for updates. I just wanted to check if other public bots are having the same issues.

If it is a public bot issue, I will have to develop a private bot, but wanted to make sure before I invest the time and resources to develop a whole new bot on my own.

On Jarvee, always make sure that you put Nightmode on + randomize your automation actions.
Use HQ proxies, test multiple times until you figure the best settings which last longer without blocks.

SocialMediaNetwork said:

Just 2 options 1: you settings and 2: your proxy.
Get a 4G proxy and test! .. AND DO NOT USE ACCOUNT THAT HAS BEEN SPAMMED ALREADY FOR YOUR TEST!

Click to expand...

Boy.. your signature, it remind me someone else

IG Professor said:

Boy.. your signature, it remind me someone else

Click to expand...

May i ask to who?

RokitFocusrite said:

I am using Jarvee for all my client accounts. How do they screw you? Everyone is on EB.

Click to expand...

What is EB ?

homeriscool said:

What is EB ?

Click to expand...

Embedded Browser.

chrysanthemum said:

Thanks for your reply.

I've heard that private bots are working, or working better than public bots - so maybe it is an API issue.

My unfollow settings are different for each account (as well as all my settings, they differ slightly for each). I have my unfollows set higher than my followers, but the unfollow action stops if there's not enough scraped accounts for my settings.

I'm fairly certain my proxies are fine. All users of the bot I am using are facing the same issue and everyone's proxy provider and type is different. The team behind the bot has also acknowledged the issue so we're hoping for updates. I just wanted to check if other public bots are having the same issues.

If it is a public bot issue, I will have to develop a private bot, but wanted to make sure before I invest the time and resources to develop a whole new bot on my own.

Click to expand...

You can always try the other public bots. Most (all?) should give a trial / refund period, that way you can know whether it is your bot or not.

As for going the privately developed bot, that can be a very very big undertaken. Leveraging a public bot, you know there are 100s / 1000s of other users testing / finding bugs. With a personal bot, there is just you. Hiding in a crowd is a good way not to stand out. Personal bot and you "may" stick out like a sore thumb

Gazza_571 said:

My accounts run only on API, EB gave persistent blocks to accounts. Jarvee provides API UserAgents, but very old/incorrect API agents for phones that shouldn't have that API that Jarvee has given. Rather edit those with updated API's found on the net. Instagram generally blocks bad API UserAgents. Like, I saw on mine that the device is from 2012, discontinued, last Android version on the phone was 4.0, screen is 720x440 with 246 DPI but UserAgent Jarvee gave was Android 8.0 with 1990x1440 and 540 DPI? Not gonna work. Updated API's have proven to work for my accounts.

Click to expand...

With the latest update jarvee has renewed all user agents, now it has all recent android.
However, through my tests, I found some problems.
Jarvee hides many types of fingerprints, but does not hide everything.
The problem that is most frequently revealed by analyzing with web sites like whatleaks.com is what a second windows operating system is detected, and this is inconsistent with jarvee's fake android user agent.
do any of you have a solution?

rootjazz said:

You are having issues with client accounts? What proxies are you using? I know people still have some trouble with spammy crappy accounts (expected) but real accounts should be working fine through automated API requests (unless you are still trying to bot like 2018 and pushing 800+ follows a day

Click to expand...

Do you think it is better to work via API or Embed browser?

manureverse said:

Do you think it is better to work via API or Embed browser?

Click to expand...

I assume you mean the jarvee embedded browser? I have no experience of that or of how well it is implemented to avoid fingerprinting

manureverse said:

With the latest update jarvee has renewed all user agents, now it has all recent android.
However, through my tests, I found some problems.
Jarvee hides many types of fingerprints, but does not hide everything.
The problem that is most frequently revealed by analyzing with web sites like whatleaks.com is what a second windows operating system is detected, and this is inconsistent with jarvee's fake android user agent.
do any of you have a solution?

Click to expand...

I feel you bruv, I did found out a few more metrics that Insta uses to track, PM if you're keen on finding out. From what I've seen, jarvee doesn't actually emulate everything that's needed/asked for by Insta's API, I'm trying to look like a 'decent' botter now. Like, yes, I'm botting, no, I'm not spamming people dick pics or being a general nuisance.

Gazza_571 said:

If you're using Jarvee, pay attention to the API and EB UserAgents, they screw you around heavily.

Click to expand...

Hey Gazza I just noticed all the API UserAgent Settings on my 15 accounts are the same... Is this right? All experiencing API Blocks :/

agentollie said:

Hey Gazza I just noticed all the API UserAgent Settings on my 15 accounts are the same... Is this right? All experiencing API Blocks :/

Click to expand...

Well, no, I wouldn't say that's right. I suggest reset Device ID's, that'll knock your accounts off and back to pending. Edit the API (new ones can be found) just copy pasta over and add to proxy, then verify. I'll be making a post during this long weekend about what I've found.

chrysanthemum said:

Thanks for your reply.

I've heard that private bots are working, or working better than public bots - so maybe it is an API issue.

My unfollow settings are different for each account (as well as all my settings, they differ slightly for each). I have my unfollows set higher than my followers, but the unfollow action stops if there's not enough scraped accounts for my settings.

I'm fairly certain my proxies are fine. All users of the bot I am using are facing the same issue and everyone's proxy provider and type is different. The team behind the bot has also acknowledged the issue so we're hoping for updates. I just wanted to check if other public bots are having the same issues.

If it is a public bot issue, I will have to develop a private bot, but wanted to make sure before I invest the time and resources to develop a whole new bot on my own.

Click to expand...

This isn't an API issue. Since Instagram has to support old clients in the wild, these APIs will always have to work one way or the other.

We develop our own custom bot and have found that proxies, IPs, and user agents are critical in getting around blocks.

Tommy T said:

This isn't an API issue. Since Instagram has to support old clients in the wild, these APIs will always have to work one way or the other.

We develop our own custom bot and have found that proxies, IPs, and user agents are critical in getting around blocks.

Click to expand...

@Tommy T do you think it is better to use API or embed browser?
In your opinion is it better to use direct hotspots from the phone or proxy 4g?
Maybe API with Hotspot?
what is the option that allows you to more disguise yourself among the mass of average users?

manureverse said:

@Tommy T do you think it is better to use API or embed browser?
In your opinion is it better to use direct hotspots from the phone or proxy 4g?
Maybe API with Hotspot?
what is the option that allows you to more disguise yourself among the mass of average users?

Click to expand...

I'm not familiar with the embed browser. How does that work?

If you can use a direct hotspot from the phone, that would definitely work better than a purchased 4g proxy. I'm assuming that the hotspot is connected to a cell tower or something similar.

Tommy T said:

I'm not familiar with the embed browser. How does that work?

If you can use a direct hotspot from the phone, that would definitely work better than a purchased 4g proxy. I'm assuming that the hotspot is connected to a cell tower or something similar.

Click to expand...

Embed browser is like a normal browser, the question I ask myself is what types of fingerprints are left using an API version?

Outside Jarvee (in Chrome), analyzing the IP masked with a proxy, you will notice that some website like http://www.f.vision/ are able to read the real IP address to which you are connected, through WebRTC they are able to bypass the proxy and read the real IP.
The result is that the site detects two different IP addresses, the first given by the proxy and the second IP local which is the real IP address from which we are connected.
But if you use Hotspot the resulting IPs are the same, so there is consistency.

Instead within Jarvee (in embed browser) the situation changes, and is more consistent in tests using proxy 4g, since the passive os fingerprint is linux / linux, instead with Hotspot it results Windows / linux.
If the API mode emulates the app perfectly it would probably be better via hotspots, as it is certainly less strange for istagram than using proxies.
But I doubt the API mode is perfectly the same as the instagram app.
The Jarvee technicians will have taken security measures to allow their users to use Proxy, exactly as they did with the Embed Browser mode.
In embed browser Jarvee tries to hide many types of fingerprints, but unfortunately it does not do it very well, so it is visible in various tests.
Do you understand my point?
I think the only real solution to this story is to find a way to be as similar as possible to the average user.
And probably if the API mode perfectly emulated the smartphone and the instagram app, one would use hotspots and get stuck in the middle of the mass.

manureverse said:

Embed browser is like a normal browser, the question I ask myself is what types of fingerprints are left using an API version?

Outside Jarvee (in Chrome), analyzing the IP masked with a proxy, you will notice that some website like www.f.vision are able to read the real IP address to which you are connected, through WebRTC they are able to bypass the proxy and read the real IP.
The result is that the site detects two different IP addresses, the first given by the proxy and the second IP local which is the real IP address from which we are connected.
But if you use Hotspot the resulting IPs are the same, so there is consistency.

Instead within Jarvee (in embed browser) the situation changes, and is more consistent in tests using proxy 4g, since the passive os fingerprint is linux / linux, instead with Hotspot it results Windows / linux.
If the API mode emulates the app perfectly it would probably be better via hotspots, as it is certainly less strange for istagram than using proxies.
But I doubt the API mode is perfectly the same as the instagram app.
The Jarvee technicians will have taken security measures to allow their users to use Proxy, exactly as they did with the Embed Browser mode.
In embed browser Jarvee tries to hide many types of fingerprints, but unfortunately it does not do it very well, so it is visible in various tests.
Do you understand my point?
I think the only real solution to this story is to find a way to be as similar as possible to the average user.
And probably if the API mode perfectly emulated the smartphone and the instagram app, one would use hotspots and get stuck in the middle of the mass.

Click to expand...

I see. Does the embed browser just load instagram.com and automate actions that way? Do you have to open it every time you want automation to run?

Using the production Instagram app or web will always be safer than using a custom written API solution. Like you said, the API mode will always lag behind the Instagram app and may miss hidden Instagram security mechanisms.

I also remain very skeptical of the "Passive OS Fingerprints" theory. The truth is that Instagram APIs speak HTTP and you can inspect and spoof every part of the request when you're sending (e.g. things such as user agent / any headers / cookies involved).

Being able to inspect low level TCP packets on requests that proliferate throughout a complicated network stack like Instagram is a ridiculous expectation.