-
-
Notifications
You must be signed in to change notification settings - Fork 22
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
Script hangs if faces the user that cannot be mentioned #8
Comments
Hello, I've done a little research about that and I found out that the error's notification which Instagram sends you when you can't mention someone is the same as when you comment too much, reaching your account's rate limit. For now I'm very busy with work and so I can't contribute more to the project... But sure, once I finally have time to implement some features I will try finding a way around. Project is open-source if anyone would like to contribute. Thanks :) |
Thanks for the feedback! However I do not push, just friendly notice about possible feature. Also will do some research on this and if will have enough knowledge - will try to contrubute something. Thanks and have nice holidays 🎄 |
Thanks, you too :) |
I've been trying to find a way around the "Couldn't post comment". When clicking on the send comment button, you already defined the "couldn't post comment" exception, but it just has "sleep(60)". My logic was trying to make it skip that comment (or those two comments, depending on the user's choice in config.ini), like comment++, but that doesn't work. I tried calling the write_comment functon again, but it says it's undefined. |
Has anyone solved this issue? |
please fix? :\ |
Hi there! Using your script and facing the issue that if user in his privacy settings set that nobody can mention him so script hangs with "Could no post comment".
In this case my flow is following
I've seen that you're already thinking on mentions tracker, so not to mention twice. Please consider on checking if user can be mentioned.
Thanks
The text was updated successfully, but these errors were encountered: