Instapy: Sleep delay between each follow

[Edhim]

Hello,
how to increase the delay between each follow ?

any idea @uluQulu

Thanks

[AvocadoStyle]

@uluQulu +1!!!! Thanks.

[uluQulu]

Hi all

@Edhim
Why you would want to do it?

There is a Quota Supervisor with the capability of controlling the follow actions smartly in both- hourly & daily intervals if you have not heard of.

If you have a specific reason, then I will ask 2 questions:

• Do you want to have a delay after every follow in the program?
  _e.g. like_by_tags() can also follow people, etc._

• OR do you want to have a delay after follows in follow based features in the program?
  _e.g. follow_likers() or follow_user_followers(), etc._

---

Cheers 😁

[Edhim]

@uluQulu
i am using follow_user_followers
and between each follow i want put some delay

[uluQulu]

Right, @Edhim

Why you would want to do it?

[Edhim]

@uluQulu each time i am shadow banned from my mac (i need to change ip each time)
so i think increasing the delay between each follow (like 40s) would avoid this

[uluQulu]

@Edhim
That's clear.
I think you should add that delay after every follow you do.

Open up unfollow_util.py file and find the follow_user() definition and at the end of that function, put the desired sleep time.

    sleep(40)   # earlier it was: `sleep(3)`    ## YOU WILL MODIFY THIS LINE

    return True, "success"

Now it will sleep 40 seconds after each follow but it is a big amount I would say 🤔 (_maybe put 15 seconds?_)

---

Cheers 🤩

[Edhim]

@uluQulu thaaanks.

i will do some tests and see the best delay amount.

Many thanks!

[AvocadoStyle]

@uluQulu
This will help me get rid of this shadow ban too!
Thanks!

[AvocadoStyle]

i will do some tests and see the best delay amount.

Many thanks!

@Edhim
tell us if it stopped shadow ban you with the settings (sleep 40 seconds)

[stale[bot]]

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. > If this problem still occurs, please open a new issue