v2.3.0

v2.1.1
🎁 biography language check! Now you can specify a list of biography languages you want to interact with. That's more powerful than the character_set but may be inconsistent if the bio is not a real text (such as a list of words without verbs). In any case, the bot does a best of 5 (BO5) and takes the most likely language.
for example: 'italian and russian devops engineer ️guitarist nerd ' returns 'nl' instead of 'en' most of the time
Add your list in your filter.json according to the file example in config-examples folder. For example: "biography_language": ["it", "en"], -> the full list here https://en.wikipedia.org/wiki/List_of_ISO_639-1_codes
That new feature needs a new library: 'pip3 install langdetect' if you installed with git, if you're with pip you don't have to do anything
🐈 check if IG is opened before start to botting, if not wait until is loaded (that problem may occur if you have an old phone). If doesn't open, stop.
🐈 a little bit of restyling and typo corrections
🐈 replace deprecated logger.warn() for logger.warning()
🐈 wait until a profile is loaded before pressing on following container
⬆️ Bumps urllib3 from 1.26.4 to 1.26.5

v2.2.1
🎁 telegram reports! you can send report at the end of the session using telegram (needs pandas: pip3 install pandas if with git)
https://github.com/GramAddict/docs/blob/main/configuration.md#telegram-reports
🐈 add posts and following to session records
🐈 save the session BEFORE performing the analytics / telegram-reports
🐈 some logging fix
🐈 if less than 3 posts, don't scroll down
🐈 lowered from 1 to 0.5 second the low bottom of random sleep
🐛 little "fix" if gap_view not found

v2.3.0
🐈 I've replaced the unfriendly filter.json with filters.yml. You can still use the old way, but I'll remove the support very soon..
🐛 the parse of followers was wrong from day one but only people with more then 10k followers were affected. In the sessions.json that number may be stored wrongly in this case (x10). That could create problems with the new feature telegram-reports. If this is your case, you can edit your sessions.json and remove a zero at the end for the sessions afflicted :)
🐈 random sleep will not be less than 0.3s from now
🐕 ported the features markdown from docs in the readme.md
🐛 fix a problem if analytics was false instead of commented