Releases: alexal1/Insomniac
v3.6.0
💥 Huge News:
1️⃣ User Switching. Configure multiple accounts, specify one of your accounts names and Insomniac will switch to it at start. Read more in the blogpost
2️⃣ Sessions Flows. Instruct the bot to do interaction, then unfollowing, then another interaction – in any sequence you like. It's simple and clear, see for yourself in the post
3️⃣ Commenting. You asked for it and finally it's done! Just provide a list of comments and specify how often you wanna comment, detailed info in the blogpost
4️⃣ More config examples! We found that a lot of users have issues with configs, and since this is the key for simplicity & readiness-for-use, we have created a lot of configs examples for different usecases. Just check config-examples and config-examples-extra folders.
5️⃣ Specify a sort order of following-list when unfollowing. --following-sort-order
– sort the following-list when unfollowing users from the profile-following list. Can be one of values: default / latest / earliest
. Default sorting is by earliest
6️⃣ Unfollow-Non-Followers cache. When running unfollow with the --unfollow-non-followers
parameter, Insomniac checks if the account is following us, and only if not it will be unfollowed.
This follow-status check takes time, and if you are running this kind of unfollow every day, there is no point of checking the same profiles again and again.
We've added a new mechanism that caches the follow status of a profile from the following list. You can handle the caching time using a new parameter called:
--recheck-follow-status-after 72
– set a time (in hours) to wait before re-check follow status of a profile, disabled by default (will check every time when needed). It can be a number (e.g. 48) or a range (e.g. 50-80)
7️⃣ Share scrappers' DB (patrons only). --scrapping-main-db-directory-name
– when using this parameter the scrapper will use a database file that's located under the directory-name provided. Use this parameter if you have multiple scrappers, and you want them to be synchronized within the same database in order to not scrape the same account multiple times. By default using scrapper account-directory to store the scrapping history.
8️⃣ Scripts Hooks (patrons only). A lot of users are running their own automation and scripts around Insomniac. Now there's a built-in possibility to connect your own script, read an explanation in the post
9️⃣ Interact/Scrape by Location. Now it's possible to interact not only by username/hashtag, but also by a location! Welcome to the post
Enhancements:
# Like & Follow action order - instead of always liking and only then follow, Insomniac will randomly decide (50%) which action should be first, in order to add more randomness to the session.
# Follow-action time enhanced dramatically - from ~20 seconds to ~5 seconds for a single follow
# Unfollow from following list itself - instead of getting into a profile page to do an unfollow action, if a follow-status check is un-needed, Insomniac will decide randomly (50%) if the unfollow should be from the following-list itself or from inside the profile page.
# When interacting with targets, the interaction time & target name will be written into new files called interacted_targets.txt (can give you a sense of how many targets been interacted)
# There is an option to scrape into multiple targeted-profiles using the same --scrape-for-account
parameter. Instead of providing just a string of your real-profile-name, provide a list of strings, and Insomniac will add the targets to all of the accounts in that list (a single account scraping using a string is still supported).
Bugfixes and small enhancements:
# For scrapping – added short session-report during session when a new profile scrapped
# For unfollowing – added short session-report during session when a profile been unfollowed
# Searching users under account tab instead of top
# Unfollow-non-followers – support new instagram pop-up dialogs
# Sessions report – back to print all of the sessions
# Added the session username to a single-session report message
# Backward compatability to old "total_removed_mass_followers" on json migration
# Fixed bio-expand when there is a link in bio
# Fixed image-liking when image ratio is 1:2 or less
v3.5.7 - Hotfix
Merge pull request #229 from alexal1/3.5.7-update Updated to version 3.5.7
v3.5.4 - Hotfix
- Fixed targeted-session issue combined with already-filtered & blacklisted profile
- Added the ability to scrape from one scrapper into multiple profiles-databases (parameter name
scrape_for_account
remains the same)
For this release we've worked a lot on stability and performance, but didn't forget about new features too!
🚀 Here is what we've done to improve performance:
- Single database per account instead of multiple .json files. When you launch v3.5.0 it will copy all data to this database, so nothing will be lost. Main benefits are speed and robustness. Also it makes possible to "scrape" and interact with "targets" from two accounts simultaneously.
- Most of filters are executed before entering to a user's profile. It makes the whole process much faster and saves you from making too many profile views.
- When looking for shop-profiles the lookup is much quicker now.
- When looking for unfollow-option in somebody's profile the lookup is much quicker too.
🐞 Stability fixes:
- Softban Indicator – a new core feature of Insomniac, will check from time to time if there is an empty profile or empty followers list. If there are too many of them, that's a good indication for a soft ban, and Insomniac will stop its session immediately (use
--dont-indicate-softban
to turn it off) - "Action blocked" dialog detection was also improved and included into Softban Indicator.
- Before searching for main tab-bar, now makes sure that the keyboard is closed (if is opened – closing it).
- Bugfixes around hashtag-interaction.
🤓 New features as promised:
--app-id
com.cloned.package – when using this parameter, you are able to use Insomniac on a cloned Instagram application. Just provide the new package name.--wait-for-device
– when using that flag, Insomniac will wait for an ADB device to be available before continuing its session (instead of quit when there is no device available). If a device id is provided using--device
, Insomniac will wait for that specific device id to be available before continuing.--debug
– flag for extra-informative logs.- All logs are now saved in .log files (even when not crashed).
🏗 Some changes that we've made in existing features:
--unfollow 50
is now the only available unfollow command. You can add these flags to specify which users to unfollow:--unfollow-followed-by-anyone
or--unfollow-non-followers
. First one says to unfollow users who were followed both by the bot and not by the bot. Second one says to unfollow only profiles that are not following your profile.--total-successful-interactions-limit 70-80
– this limit allows you to specify the maximum amount of successful interactions during a session. This limit has been known in past as--total-interactions-limit
.--total-interactions-limit 200-250
– allows you to specify the maximum amount of any interaction (successful & unsuccessful) during a session.- Targets are now marked as "interacted" once you interact with them, so you won't interact with the same target twice.
Fixed Internet Speed Check
v3.4.2 Update to v3.4.2
Bugfixes
Interact instructions, Internet speed test and more
New features
1. Interact instructions – the new way to interact with users!
Today we are announcing a new way to tell the bot with which users we want to interact with.
Until today, the bot always interacted with profile followers & hashtags recent-likers.
From today, we have two more options of interaction with users: 1. interact with profile followings and 2. interact with hashtags top-likers.
How should the interaction list be provided to the bot? As mentioned, 4 interaction instructions are supported:
@profile-followers
@profile-following
hashtag-top-likers
hashtag-recent-likers
You can combine all of the above in the interact list, for example:
python start.py --interact @natgeo-followers @natgeo-followings amazingtrips-top-likers amazingtrips-recent-likers
2. --likes-precentage 50
– this new parameter lets you to set the percentage of like action, in order to add more randomness to the bot's activity (and not to like every picture it's opening).
3. --reinteract-after 72
. Today if the bot recognizes a profile that has already beed interacted by the bot, it won't interact with it second time. Using this parameter, you will allow the bot to interact with an already interacted profile after X hours (for example, --reinteract-after 72
will allow the bot to reinteract with an already interacted profile after 3 days from the last interaction).
4. Internet Speed Check. A lot of people are getting crashes due to low bandwidth of internet connection. From now on the bot will check your internet connection speed and calculate the needed amount of time to sleep between actions. You can skip this check by using --no-speed-check
.
New limits
-
--max-following 500
– allowes you to specify the maximum amount of following you want to have while using the bot. When your following value will reach the limit value, the bot will stop following profile (will continue do other actions such as liking and watching stories). -
--session-length-in-mins-limit
– by using this limit you are able to stop the bot after X minutes, regardless of other session limits. This limit will add extra safity to your sessions :)
New filters
"skip_already_following_profiles": true
– will tell the bot to skip interaction with profiles that have already been followed (even if not followed by the bot).
Enhancements & Changes:
- Shop profiles are now supported
- Files usage enhancements: multi-platform file path is supported now
- Added app-version to the session-state for debugability
- Added "total-successfull-interaction" number to session progress loggings
- Changed
max-following
parameter name of "remove-mass-followres" action to bemass-follower-min-following
Bugfixes
- Interacting with self profile: fixed a crash
- Fixed scrapping-limit bug (didn't work properly)
Bugfixes, new limits and new filters
3.3.2 release notes:
New limit
total-get-profile-limit: Use that limit in order to be safer than ever while using insomniac! this limit will limit the amount of times that the bot is clicking on a profile name and getting into its profile page. This is the most common reason for a soft ban.
New filters:
- max_potency_ratio: skip accounts with ratio (followers/followings) higher than given value (decimal values can be used too)
- blacklist_words: provide a list of words, skip accounts that contains one of the words in the list in the profile biography
- mandatory_words: provide a list of words, skip accounts that doesn't have one of the words in the list in the profile biography
- specific_alphabet: provide a list of alphabet types (i.e. ['LATIN', 'GREEK', 'ARABIC', 'HEBREW', ...]), skip accounts that contains text in their biography/username which different alphabet than the provided alphabet list
Enhancments:
- Accounts that getting filtered during the session will be appended to 'filtered_users.json' file.
- On target-sessions, the 'targets.txt' file is reloading during the session runtime so you can scrape & target in the same time
- Added filters caching mechanism in order to check the filters much quicker than before
- From now on, interaction considered to be success-interaction event if not all likes-count been satisfied (as long as there is at least 1 like during interaction, it will be counted as success)
Bugfixes:
- During unfollow session, handling the opoped-up unfollow-confirmation dialog
- Opening Instagram app issue (from version 3.2.0) has been fixed
- On hashtags-interaction, if there is no 'recent' tab, using popular instead (thanks to @ClarityCoder PR)
- Fixed stories-interaction logic with sessions-limits
Bugfixes and Improvements
- Profiles that were filtered once won't be opened anymore
- Fixed bug with
--follow-percentage
not working in some conditions - Fixed getting Instagram app version when device id provided
Meet a brand new feature – watching stories!
• --stories-count 3-6
– how many stories to watch. A user may have less stories, that won't be a problem
• --total-story-limit 100
– limit of story-watches per session
• New filter parameter "skip_profiles_without_stories
" – set to "true
" to skip profiles that do not have stories
Other fixes and improvements:
• Added short report after each interaction (was lost during the work on v3.2.0
)
• Fixed not working --follow-limit
• Fixed not working --old
flag when specified in a configuration file
• Saving crash data in zip folders when exceptions occur