Instagram SPAM Filer - New update rolling out.

Redox123 said:
I did 1.400 Story Likes a day and also viewed the story. Thats how I gained a lot of Followers the last months. Now my Account is spam flagged.
Though Times I guess. We have to wait for new doors. Phone Automation is spam flagged aswell after time.
Click to expand...
Phone Automation is spam flagged aswell after time"



What Do you mean? Do you simulate iOS/android request or different ways?

curdoc said:
That's not true. We automate over 500 androids and we do not have spam flag. We are even running right now some accounts with over 1k story likes per day. So far no spam.
Click to expand...
Android leak a lot of data and send tò the app owner ,this jeopardizes accounts and results in bans and ghosted content.
How tò deal with it?
 
Advertise on BHW
vittorianicolosi1994 said:
Phone Automation is spam flagged aswell after time"
Click to expand...
There are many factors, so far once you mix actions, it do not mark your account as spam.

Using API, no metter what delays or max actions you will do.
Any action will makr you as spam.

On phones it do not happen. So far...
 
vittorianicolosi1994 said:
Android leak a lot of data and send tò the app owner ,this jeopardizes accounts and results in bans and ghosted content.
How tò deal with it?
Click to expand...
There are some work arounds.
 
Behaving like a normal user on IG would be the end of all your worries.
 
I'm spam flagged for 1 week now. Anyone could fix this issue? I rested my Account and so on.
 
DannyShaw88 said:
that's correct, but whats the difference? same calls.....
Click to expand...
You need to be able to replicate everything 1:1 and that's incredibly hard.

Main API is simple, the clusterfuck starts with logging_client_event calls for example, if you have reversed them, kudos. If not, thats one detection vector to think about.

Then there is a bunch of other, more technical ones. Instagram switched to http/3 so I can bet most of automation software there is that relays on API calls cant support that as because there simply isn't libraries that supports UDP.

Even finding proxies that support UDP and doesn't force you to install OpenVPN(lol) is hard.

Then there are simpler things like SSL chiper fingerprint stacks that can easily detect you are using specific libraries, e.g. node.js has unique fingerprint that differs from a regular chrome etc.

And when you have solved all that, then you need to be sure your timings and steps/order of those calls are correct too.

So.. if you want to only target Instagram and do it on enormous scale, then API is best and probably only sane way to do it. But to reverse everything will be extreme.

For anything smaller than 20-30k accounts, phone based automation is still better in my opinion, handling 2-3k phones will be a headache tho.
 
Last edited:
lucky.sparks said:
For anything smaller than 20-30k accounts, phone based automation is still better in my opinion, handling 2-3k phones will be a headache tho.
Click to expand...
Wouldn't it burn your brain if you entered a room like that with 2k enabled phones on lte? I heard it's not healthy.

From what I read those "API reverse engineerings" are nightmare. I've never done that and I don't want to try.
 
The problem is that with phone automation the limits are much higher to grow an account. Not to mention the optimization, management and management of slaves on phones. Any account that has gone through API suffers much more softblocks in phone automation.
 
What's all the hype with API on Instagram?

On YouTube nobody even tries to do that.
 
reaaski said:
Wouldn't it burn your brain if you entered a room like that with 2k enabled phones on lte? I heard it's not healthy.

From what I read those "API reverse engineerings" are nightmare. I've never done that and I don't want to try.
Click to expand...
Phones usually are wired when doing this kind of scale, wifi and mobile off.
 
API allows you to do mass stories, votings, etc. in a much more optimized way BUT with higher risk. We are already seeing it with all the spam flag, blocks, etc. The future is always phones and interacting like a real person. Who is going to be giving 3k likes and watching 5k stories per day?
 
When they ask about $1 a day, they should read THIS. And that's the way to do it.

Abuse when possible. Switch to normal when abuse potential gone. :D

Churn and burn isn't that bad if you want a little $5k day.
 
lucky.sparks said:
You need to be able to replicate everything 1:1 and that's incredibly hard.

Main API is simple, the clusterfuck starts with logging_client_event calls for example, if you have reversed them, kudos. If not, thats one detection vector to think about.

Then there is a bunch of other, more technical ones. Instagram switched to http/3 so I can bet most of automation software there is that relays on API calls cant support that as because there simply isn't libraries that supports UDP.

Even finding proxies that support UDP and doesn't force you to install OpenVPN(lol) is hard.

Then there are simpler things like SSL chiper fingerprint stacks that can easily detect you are using specific libraries, e.g. node.js has unique fingerprint that differs from a regular chrome etc.

And when you have solved all that, then you need to be sure your timings and steps/order of those calls are correct too.

So.. if you want to only target Instagram and do it on enormous scale, then API is best and probably only sane way to do it. But to reverse everything will be extreme.

For anything smaller than 20-30k accounts, phone based automation is still better in my opinion, handling 2-3k phones will be a headache tho.
Click to expand...

i'm using a private bot, I am hoping they have done this and ill look in to it, 100% not using http/3, http/2 is being used

I am still have semi success, they warm up for a while and then something eventually gets detected and its all through API, I have been using API since 2016 with thousands of accounts and this sort of issue comes around every 2 years or so. This is by far the longest blocking I have ever suffered though
 
I think it is the end to all the massive things we do like mass likes, mass dms, mass followers, etc.,
 
Was someone able to remove the spam filter? Any ideas what can help? Deactive acc for 48h maybe?
 
lucky.sparks said:
You need to be able to replicate everything 1:1 and that's incredibly hard.

Main API is simple, the clusterfuck starts with logging_client_event calls for example, if you have reversed them, kudos. If not, thats one detection vector to think about.

Then there is a bunch of other, more technical ones. Instagram switched to http/3 so I can bet most of automation software there is that relays on API calls cant support that as because there simply isn't libraries that supports UDP.

Even finding proxies that support UDP and doesn't force you to install OpenVPN(lol) is hard.

Then there are simpler things like SSL chiper fingerprint stacks that can easily detect you are using specific libraries, e.g. node.js has unique fingerprint that differs from a regular chrome etc.

And when you have solved all that, then you need to be sure your timings and steps/order of those calls are correct too.

So.. if you want to only target Instagram and do it on enormous scale, then API is best and probably only sane way to do it. But to reverse everything will be extreme.

For anything smaller than 20-30k accounts, phone based automation is still better in my opinion, handling 2-3k phones will be a headache tho.
Click to expand...
I saw that 3proxy supports UDP, do you know if it's working properly?
 
Advertise on BHW
You must log in or register to reply here.
Sign up now!

Main Menu

Home Main Forum List Black Hat SEO White Hat SEO BHW Newbie Guide Blogging Black Hat Tools Social Media Downloads

Marketplace

Account Selling Content / Copywriting EBooks / Methods Hosting Misc Proxies For Sale SEO - Link building SEO - Packages Social Media Social Media - Panels Web Design More

Making Money

Affiliate Programs Hire a Freelancer IM Journeys Making Money Pay Per Click Site Flipping Want to Buy

BlackHat World

Dispute Resolution Forum Suggestions & Feedback Introductions Lounge
Back
Top