Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

How to stay safe with Instagram warning about suspected automated behaviour #5598

Open
phere-x opened this issue May 17, 2024 · 6 comments
Open

Comments

@phere-x
Copy link

phere-x commented May 17, 2024

I've recieved this today and have had issues with other accounts requiring ID verification to get access back into accounts.

image

What can be done to make sure I don't get banned or asked to verify? I've also experienced instances where I need to keep grabbing a new cookie login every now & then, could it be coz of this or is it just something that naturall expires?

I've increased sleep duration to 56.0-120.0, do I go even larger than that? Do people usually cycle through multiple accounts? How do all these completely obvious bots spamming DMs, comments & being the most obvious bots get away with shit?

@malexosh
Copy link

malexosh commented Jun 19, 2024

Never scraped Instagram before… Scraping my own profile of two dozen photos resulted in this same warning. There has been a site change of some kind, or the method used to download is causing the error. Probably a mix of both. [edit]

@nothing2obvi
Copy link

nothing2obvi commented Jul 31, 2024

Wondering the same thing. My current settings are as follows, but I still get the same warning as OP and need to keep grabbing a new cookie login.

"sleep-request": [30.0, 60.0],
"sleep-429": [60.0, 90.0],
"sleep": [30.0, 60.0],
"sleep-extractor": [30.0, 60.0],

@phere-x -- Did you find any solutions since you opened this issue? Thanks.

@nothing2obvi
Copy link

Any updates?

@phere-x
Copy link
Author

phere-x commented Dec 1, 2024

No change, I just rarely use it now because I don't want to risk anything. And even after not using it for a long period the warning still pops up in the rare moment I try it after a few uses.

One solution I saw passed around for another similar tool was throttling the speeds when downloading - not the sleep time between a process. Haven't tested it out but it might be the solution.
Think the tool that was mentioned was "trickle" but it might've been old or something & so I lost focus on it for a bit & forgot till now.

@nothing2obvi
Copy link

@phere-x I appreciate the info. I'll play around with it when I have the time.

@phere-x
Copy link
Author

phere-x commented Dec 9, 2024

I think this was it! I started using it again about 2 days ago now. The same amount, if not a tad more, and had no issues on the rate limiting side.
(p.s. I also just discovered -r, --limit-rate 😅 after using the method below. Gonna test with this.)

I dropped my sleep duration back down to 16.0-32.0 (relatively low for me) and used the pv command (sudo apt install pv https://www.cyberciti.biz/open-source/command-line-hacks/pv-command-examples/).

Example usage:
gallery-dl instagram.com/cristiano | pv --rate-limit 15 > ./output.file

This limits it to 15 bytes - I was playing super safe so went with that. Just now though I increased it to 320Kb (pv --rate-limit 320K) & removed the output file as I didn't need it. The guy in the other repo said to do anything below 500Kb.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants