[GH-ISSUE #41] Inconsistency in how follow counts are treated #28

New issue

Closed

opened 2026-02-27 20:05:04 +03:00 by kerem · 1 comment

kerem commented

2026-02-27 20:05:04 +03:00

Owner

Originally created by @tomballgithub on GitHub (Jan 17, 2026).
Original GitHub issue: https://github.com/misiektoja/instagram_monitor/issues/41

With the introduction of DETAILED_FOLLOWER_LOGGING, I think there should be consistency in how follows counts are tracked/printed.

My proposal:

When using DETAILED_FOLLOWER_LOGGING, always use the actual counts of what is in the JSON
-- We are in a mode of always knowing the exact amount, so the Instagram untrustworthy # should not be used
-- And an 'actual' count is never needed
Otherwise, use the count that Instagram reports
-- I am OK with leaving current printing as-is, but also good with removing 'actual' counts to have one consistent sent of print statements

Goal is one set of logic, but just consistency in how the counts are assigned and tracked.

Example 1:

DETAILED_FOLLOWER_LOGGING, Instagram reports 190, I edited the JSON file to have a # of 188, but with 187 accounts
I think the 1st line should show Followers (187) and not show an actual
I think the 2nd line below should be from 187 to 190 (+3)

* Followers (188) actual (187) loaded from file 'XXX.json' (16 Jan 26  22:00)
* Followers number changed for user XXX from 188 to 190 (+2)

This is what is in the client mode dashboard for this same event -> 187
22:16:15 [XXX] Followers loaded from file: 187

Example 2:

This type of line should be avoided (0 change):
* Followers number changed for user tomballrunner from 129 to 129 (0)

Same thing in web dashboard:
[XXX] Followings changed: 374 -> 374

Example 3:

With DETAILED_FOLLOWER_LOGGING, would the #'s ever be shown not matching here? Doesn't seem like there is a point in showing the Instagram # vs the real # in this mode
* Followers (190) actual (190) saved to file 'instagram_kara.elaine.long_followers.json'

Originally created by @tomballgithub on GitHub (Jan 17, 2026). Original GitHub issue: https://github.com/misiektoja/instagram_monitor/issues/41 With the introduction of DETAILED_FOLLOWER_LOGGING, I think there should be consistency in how follows counts are tracked/printed. My proposal: - When using DETAILED_FOLLOWER_LOGGING, always use the actual counts of what is in the JSON -- We are in a mode of always knowing the exact amount, so the Instagram untrustworthy # should not be used -- And an 'actual' count is never needed - Otherwise, use the count that Instagram reports -- I am OK with leaving current printing as-is, but also good with removing 'actual' counts to have one consistent sent of print statements Goal is one set of logic, but just consistency in how the counts are assigned and tracked. ----------------------- **Example 1:** DETAILED_FOLLOWER_LOGGING, Instagram reports 190, I edited the JSON file to have a # of 188, but with 187 accounts I think the 1st line should show Followers (187) and not show an actual I think the 2nd line below should be from 187 to 190 (+3) ``` * Followers (188) actual (187) loaded from file 'XXX.json' (16 Jan 26 22:00) * Followers number changed for user XXX from 188 to 190 (+2) ``` This is what is in the client mode dashboard for this same event -> 187 `22:16:15 [XXX] Followers loaded from file: 187` ----------------------- **Example 2:** This type of line should be avoided (0 change): `* Followers number changed for user tomballrunner from 129 to 129 (0)` Same thing in web dashboard: `[XXX] Followings changed: 374 -> 374` ----------------------- **Example 3:** With DETAILED_FOLLOWER_LOGGING, would the #'s ever be shown not matching here? Doesn't seem like there is a point in showing the Instagram # vs the real # in this mode `* Followers (190) actual (190) saved to file 'instagram_kara.elaine.long_followers.json'`

kerem closed this issue

2026-02-27 20:05:04 +03:00

kerem commented

2026-02-27 20:05:04 +03:00

Author

Owner

@tomballgithub commented on GitHub (Jan 18, 2026):

Here's more from the live activity log on the dashboard.
It is showing following and follower 'changed' but to same values
I verified in the log that there were no changes detected

│ 21:06:12 [XXX] Fetching updates (hour: 21)       
│ 21:06:19 [XXX] Followings changed: 4385 -> 4385
│ 21:43:04 [XXX] Followers changed: 190 -> 190      
│ 22:03:26 [YYY] Fetching updates (hour: 22)            
│ 22:03:31 [YYY] Followings changed: 374 -> 374    
│ 22:06:45 [YYY] Followers changed: 129 -> 129

@tomballgithub commented on GitHub (Jan 18, 2026): Here's more from the live activity log on the dashboard. It is showing following and follower 'changed' but to same values I verified in the log that there were no changes detected ``` │ 21:06:12 [XXX] Fetching updates (hour: 21) │ 21:06:19 [XXX] Followings changed: 4385 -> 4385 │ 21:43:04 [XXX] Followers changed: 190 -> 190 │ 22:03:26 [YYY] Fetching updates (hour: 22) │ 22:03:31 [YYY] Followings changed: 374 -> 374 │ 22:06:45 [YYY] Followers changed: 129 -> 129 ```

kerem referenced this issue

2026-02-27 20:05:13 +03:00

[PR #28] [MERGED] During script initialization, show info around loading the two profil… #59