mirror of
https://github.com/misiektoja/instagram_monitor.git
synced 2026-04-25 22:35:49 +03:00
[GH-ISSUE #49] Can someone clarify this (skipping follower stuff) for me? #36
Labels
No labels
Stale
Stale
bug
enhancement
pull-request
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/instagram_monitor#36
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @YouveGotMeowxy on GitHub (Jan 18, 2026).
Original GitHub issue: https://github.com/misiektoja/instagram_monitor/issues/49
In the config:
From my understanding, if I DON'T want any follower/following info I MUST use a login session instead of anonymous? Why? Why can't I skip that info if I'm anon?
Reason I'm asking is because at least for now I'm doing everything anon/not logged into a session, and the logs are all still showing follower count updates, which I'm not interested in, so it seems like added unnecessary script processing as well as log noise. I'd like to simply be able to set those to True and not see any of that follower stuff; like it could skip those routines entirely. :)
@tomballgithub commented on GitHub (Jan 18, 2026):
I think you are fine. In anonymous mode, you can get the follower and following counts, but not the actual list of followers or followings. That's why the settings you mention don't apply, Instagram won't let you fetch that information in the mode you are in.
@misiektoja commented on GitHub (Jan 18, 2026):
Yes, @tomballgithub is correct. Those settings only affect fetching the followers/followings list, which does not work in anonymous mode anyway, but they don't affect the count changes. It is always reported.
I'll add a config option or flag to turn it off.
@misiektoja commented on GitHub (Jan 22, 2026):
I implemented a new
SKIP_FOLLOW_CHANGES/--skip-follow-changesoption which allows to disable it. You can also disable it via Web Dashboard.