AllOutAnime
Power Member
- Oct 15, 2007
- 589
- 502
So you started out with iPhones, then sniffed the requests from the App and replicated them using code?Forgive my language but there is no other way to express this: It was a shitty solution. Beyond shit. & A huge pain in the ass for the entire duration we ran it for. It's a novice solution for people that don't know how to do it right, especially if you're trying to scale to fill / send tens of millions of instagram likes or tens of millions of instagram followers using them.
It just doesn't work or make sense to do using iPhones. The reason we stopped is because we became more advanced and switched to using Pi's, and then eventually, switched to 4x Ubuntu 32-core servers which now perform and send the same amount of actions equivalent to thousands of iPhones. So 1x server = roughly 1452 iphones.
Our evolution chain was:
- Bypassing SSL Pinning and hooking the Instagram iOS app via tweaks to intercept and replicate requests. That way 1x iPhone would become 5-6x iPhones because it would run 5-6 accounts at the same time and simply replace the POST / GET data relative to simultaneous account data. AutoTouch would be active on runtime. & we even hooked certain functions to disable post loading and used uiopen:// to speed up the load posts process. Ex: uiopen://instagram?mediaid=1
- Eventually got rid of all iPhones, switched to a ton of raspberry PI 4b+'s. Horrible solution and investment. The code would run on each pi and it would virtualize all of the requests, however, each pi could barely support more than 2-3x dongles and would constantly need daily reboots.
- Present day. We got rid of all PI's and all iPhones. We no longer run our own proxy farm and have setup strategic deals with good 4G proxy providers. We use a custom web & iOS API back-end that I built. All requests are sent through it and we're scaling creation / setup / fulfillment to run around 1,300,000 Instagram accounts per month. Hoping to simultaneously control / run 10,000,000+ IG accounts at the same time in the next 3-6 months max.
We've wasted $400k+ USD trying to figure the above out ^ It's definitely nostalgic to hear people talking about using physical iPhone automation lol.
This is quite interesting for me as I have come the other way around.
I started in 2013 with Instagram when certificate pinning was not really a thing and you could easily intercept network traffic.
I built an iOS based bot that would create and run accounts. I was a noob at that time still but it worked.
As things got more complicated, I hired more and more skilled people to keep it working.
Then last February we couldn't keep it up. Instagram added something that detected our operations, periodically logged-out all the accounts and eventually disabled them for use.
The only solution to this was to deploy an Android farm and I stopped development on the bot because I didn't see any future.
All in all I invested over $1M+ into development of that Instagram iOS requests bot.
If you still can pull it off to run a requests based bot then you must be geniuses.
All those requests that the App sends, it is insane to replicate and you never know what counts.
I don't really like the Android solution because the amount of devices limit the amount of accounts that can run.