Hey all, I wanted to bring bad news for those who automate Instagram. They have for a month or two now quietly added in updates to support QUIC / HTTP3. I do not believe many people across the world have noticed this change.
If you use the API you will notice increased bans despite doing normal and low actions (read 10 follows) as of recent.
For those of you that do not know why HTTP3 is relevant:
https://www.blackhatworld.com/seo/proxies-will-die-in-2023.1448749/
The solutions listed in that that video do not work, because if you use HTTP2 traffic IG thinks something is wrong with the account.
Since Instagram is app based, they control the SSL library, they can do whatever they want and know for sure a normal request should act like x, y, z, instead of a, b, c.
It is normal that some requests will land as HTTP2, so IG doesn't instant ban you. Your account is flagged if you get too many however.
You can confirm my words with https://github.com/Eltion/Instagram-SSL-Pinning-Bypass/issues/19
Though they only noticed later on, and do not realize the implications of HTTP3. Disabling HTTP3 will not help.
At current, it seems not any of the big proxy providers support UDP through socks5. Proxidize is not a solution either. @BetterKnow, if you can add UDP support people will pay.
If you use the API you will notice increased bans despite doing normal and low actions (read 10 follows) as of recent.
For those of you that do not know why HTTP3 is relevant:
https://www.blackhatworld.com/seo/proxies-will-die-in-2023.1448749/
The solutions listed in that that video do not work, because if you use HTTP2 traffic IG thinks something is wrong with the account.
Since Instagram is app based, they control the SSL library, they can do whatever they want and know for sure a normal request should act like x, y, z, instead of a, b, c.
It is normal that some requests will land as HTTP2, so IG doesn't instant ban you. Your account is flagged if you get too many however.
You can confirm my words with https://github.com/Eltion/Instagram-SSL-Pinning-Bypass/issues/19
Though they only noticed later on, and do not realize the implications of HTTP3. Disabling HTTP3 will not help.
At current, it seems not any of the big proxy providers support UDP through socks5. Proxidize is not a solution either. @BetterKnow, if you can add UDP support people will pay.