In order to decrease the number of requests to the server, the action/whois request should be merged with the action/refresh request. The ACP option needs to be adjusted for this:
Either it needs to explain that the who is chatting update interval is merely an estimate and will happen with the next refresh.
Or the setting needs to be changed from who is chatting update interval (which it currently says) to some kind of update multiplier. With a refresh interval of 10 seconds and a who is chatting update multiplier of 6, every 6th action/refresh also includes a who is chatting update, i.e. once a minute.
In order to decrease the number of requests to the server, the
action/whoisrequest should be merged with theaction/refreshrequest. The ACP option needs to be adjusted for this:Either it needs to explain that the who is chatting update interval is merely an estimate and will happen with the next refresh.
Or the setting needs to be changed from who is chatting update interval (which it currently says) to some kind of update multiplier. With a refresh interval of 10 seconds and a who is chatting update multiplier of
6, every 6thaction/refreshalso includes a who is chatting update, i.e. once a minute.