Closed madshansens closed 4 years ago
@madshansens how to get it?
i found this
config.IG_SIG_KEY = 'c36436a942ea1dbb40d7f2d7d45280a620d991ce8c62fb4ce600f0a048c32c11' config.REQUEST_HEADERS['X-IG-Capabilities'] = '3brTvw=='
but it blocks too
also i patched APP_VERSION
i_devices.INSTAGRAM_VERSION = '112.0.0.18.152'
and its not helpful...
this fixed story view for nextpost we should implement Version 4.5.2 - 10.10.2019
We should burp app for new endpoints.
Any expected solution yet for Account Compromise challenge for story views?
yes there are many solutions but if it becomes public i will be blocked again within 24 hours.
Has instagram threatened you for that...😅 Please share your solution.
yes they block every solution when it's made public. So no don't share.
We should make a reinforcement learning antiblock system to fix block system.
You can also just do bot.change_password("newpassword") on each time you get challenge required.
@reliefs I think the reason is that instagram is using big data to analyse bot behaviour there are a lot of ppl using instabot to promote their accounts so, once we make an update here, there are thousands of accounts implement the solution to pass through the block. And thus, instagram can detect it.
I will suggest that we shouldnt make a pull request to the master rather, we should update it in the dev branch or just type the code here in the discussion. So, the majority of ppl is still using the old script which those real developers can have idea and the right direction on how to beat instagram detection and thus, better fix can come out.
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.
https://github.com/instagrambot/instabot/blob/966bf7f6355e03f32129618069cb18809a60571b/instabot/api/config.py#L22