Allinoneinstagrambot

Latest version: v3.1.5

Safety actively analyzes 628649 Python packages for vulnerabilities to keep your Python projects secure.

Scan your dependencies

Page 2 of 7

3.0.5

Fix
- avoid pressing on music tab instead of hashtags (this bug was only for small screens)
Others
- the bot restarts after a crash, except for some scenarios that will be highlighted

3.0.4

Fix
- carousel mid-point calculation was wrong (typo)

3.0.3

Fix
- in the new version (217..) the element for sorting following list has changed
Performance improvements
- better info when min-following is used in unfollow actions or you're trying to unfollow more people than the number you're following
- handle of malformed data in telegram-reports

3.0.2

Fix
- "back" in "Follow Back" is not uppercase anymore
Performance improvements
- better handling for not loaded profiles

3.0.1

Fix
- missing argument in analytics report

Others
- new logo for the readme.md
- added some useful info for the user

3.0.0

New Features

- use the cloned app instead the official, if the dialog box get displayed (this is currently supporter for MIUI devices)
- new filter options: *interact_if_public* and *interact_if_private*
- *interact_only_private* has been removed, delete it from your filters.yml

Performance improvements

- limit check was wrong in interact_blogger plugin
- feed job was ignoring limits
- don't throw an error if config files \*.yaml instead of \*.yml are used
- likes_limit was referring to total_likes_limit and not current_likes_limit (that caused an error if you specify an interval)

Performance improvements

- jobs have been split in "active-" and "unfollow-" jobs. That means, for example, that the bot won't stop the activity if it reached the likes limit and you scheduled the unfollow.
- you can pass how many users have to be processed when working with \*.text (unfollow-from-list and interact-from-list)
- bot flow improved
- feed job improvements
- looking for description improvements
- better handle of empty biographies
- showing session ending conditions at bot start
- countdown before starting, so you can check that everything is ok (filters and ending conditions)
- before starting, the bot will tell you the filters you are going to use (there is no spell check there, if you wrote them wrong they will be displayed there but not get considered)
- disable head notifications while the bot is running
- removed unnecessary argument in check_limit function
- removed some unnecessary classes in story view
- move Filter instance outside of plugins

Page 2 of 7

© 2024 Safety CLI Cybersecurity Inc. All Rights Reserved.