Good luck! Wish it works for you, I recommend to my clients that are using my scrapers to only scrape full api no eb and they are doing well as eb scraping killed them like flies. Hope it works well for you.
Everything is each to their own experience
Good luck!
Not sure if I understand correctlyâŚ
So if we just stop scraping, IG will not get data to learn how to stop us from scraping?
If only 20 people did automation and used scrapers IG would never have found out about it.
But considering how many people do automation they deff are trying to stop it, itâs not a small problem they have, itâs massive, in some cases these tools can be used as weapons to spread fake news and cause havoc.
If everyone stopped scraping and doing automation then instagram wouldnât have to deal with this, but when there is a problem this size they have to fight back in order to keep their platform somewhat useable.
There are other tools out there that are not as popular as jarvee and they work fine, why? you donât have as many people using it, so they have less data on how those bots work, and in return they donât get affected.
As long as this community exists, at least at such a large scale, IG is going to keep fighting it tll it stops, or at least till just a few people remain to the point it doesnât bother them.
He is pointing out that letting scrapers die and not recover them, gives Instagram more machine learning model data to take out future scrapers with better accuracy, without hurting real users.
Donât worry, SMM panels and custom bots are an overall bigger threat than Jarvee related things, thankfully.
You should have âuse only api to save bandwidthâ unchecked, and keep the âAPI Full emulationâ option checked on your scraper accounts.
gracias ossi appreciate the help will give this a try!
The only result i got was my scrapers death! I was working with very low api calls (10/100) for some accounts. I just realized that are those account who die when âScrape with Embedded BrowserâŚâ is checked. Accounts with high api calls limits are still alive.
Alright, this setting alone plus making sure Iâm logged in on EB didnât seem to have done the trick for me. But you say you have seen an improvement with the accounts life right? Iâll flick this on all of them and see if it improves at all. Cheers
haha really. Iâm hesistant to believe the eb scraping is even a thing, as my mains run on EB and I can see Jarvee doing every action of each tool when I have it open. When I did the same test on the scrapers I see nothing done at all on the EB and itâs not moved once. Instead, API calls kept going up basically telling me it was only using API. Ofc it was a short test and may not be the case in the longer term but thatâs what Iâve seen.
So your accounts with higher limits last longer? how many days? If I am doing 300-500 calls per day they also seem to die within 500-700 API calls. Which is 1-2 days.
As of this moment Iâve only lost only 1 scraper since Dec 29th, with this EB scraping setup. Iâm stunned. Sure, I only run 9 live scrapers and rotate them via binary export/import to keep 14-20 scraper accounts live. So they donât get over-used (this might be a factor).
But previous to this I was routinely losing a scraper or two every day. I made no other setup changes.
I see that others have a worse result with this EB scraping setting, so I shouldnât be too confident. Possibly I get a wave of EV/PV requests soon?
I can confirm this. I watched the scraper EB browser windows for a bit, left them open for a couple hours, and saw no movement (not even logged in). Itâs not a thorough conclusive test, but I would have expected to see action. Iâll send JV support a question about this.
thatâs a good idea! let us know what they say
EB Scraping is not done âthrough the visible Ebâ it hidden under the hood
I like your reply, but JV support sent conflicting info, it should be visible. So I donât know. Iâm not seeing action on the EB browser.
Did you come up with this yourself or you got some supporting info to back it up?
Either way, if this helps someone then happy days, letâs use it. Just weird that it wouldnât work and count API calls when scraping which strongly suggests API is being used and not the browser.
Would be nice if JV support would develop this further tho so it would be more reliable.
Accounts with lower api limits lasts less when the scrape via EB is checked. Which make me think that when an account reach its api limits, tries to scrape via EB which require an EB login. I guess this is what kill them. Usually accounts with low api limits lasts more than others.
However iâm still making tests by using more or less filters, sources, etc; trying to find the best setting for me.
Accounts with lower api limits lasts less when the scrape via EB is checked.
How low?
I donât want to add unnecessary confusion, but my low-API scrapers are lasting longer since Dec 29th, when EB scraping was activated.
Also there are multiple API/EB check-boxes, and any different combination of those could possibly cause a different result. we might need to get specific to compare results.
These are my API limits, and the scrapers are not coming anywhere close to those limits (they were in early December when I was losing scrapers more quickly).
I said before in my previous post. 10/100 was my settings when a realized that the EB scraping was checked and my accounts were death!
+1
I have similar set up on scrapers⌠and run EB only on mains - do you get lots of PV or EV on mains? I have 2 accounts that always gets them dont know why
Iâm not a good comparison, Iâm small-time. 1 main (EB only), 9 scrapers with âscrape with EBâ turned on. Iâve only had 1 EV in early December, but I donât have a lot of actions per day.
(fyi Iâve only had one scraper expire in a week, which is a long streak for me)
About your problem: Do you have other users/devices logged into your Main, perhaps from a different IP? Multiple logins active, maybe follow and unfollow simultaneously from the same IP?
