When running checks over multiple accounts, and especially when trying to find sleepers, I will run checks on all the accounts that I can check and also all the accounts I find through checkuser results. This means I can find all the IPs that were used. Because a very large majority of IPs have checkuser log entries, the absence of the green link is usually not useful for this particular use case. Having a different background colour for the link to indicate whether the last entry in the log was for the same case would be very useful.
The way I see this happening could be by looking at the last log entry if log entries exist and checking that:
- The performer of the check is the user running the script
- The check was made within the last X hours / minutes (a couple of hours should be good for that)
- (maybe) The check links to the same SPI case that is linked to in the reason for the check being currently run
A combination of those conditions could work, but I would recommend at least the first two. The third would be useful in cases of a check of a large range for a case and then running a check on the same large range for a different case. There are several sockmasters who will use similar ranges, due to proxies or other reasons. Ideally I'd like to keep this different colour representing only that the last check on this IP was a part of the checks still being run.
When running checks over multiple accounts, and especially when trying to find sleepers, I will run checks on all the accounts that I can check and also all the accounts I find through checkuser results. This means I can find all the IPs that were used. Because a very large majority of IPs have checkuser log entries, the absence of the green link is usually not useful for this particular use case. Having a different background colour for the link to indicate whether the last entry in the log was for the same case would be very useful.
The way I see this happening could be by looking at the last log entry if log entries exist and checking that:
A combination of those conditions could work, but I would recommend at least the first two. The third would be useful in cases of a check of a large range for a case and then running a check on the same large range for a different case. There are several sockmasters who will use similar ranges, due to proxies or other reasons. Ideally I'd like to keep this different colour representing only that the last check on this IP was a part of the checks still being run.