Unlike session cookies, the Identification cookie (CHOCOLATECHIP) is sent to the client with each Page Response.
It is also decrypted and re-encrypted with every page response because the process does not record any of its attributes in the server session.
Without server side recording, the process is forced to open the cookie with every page request, only to find out whether it needs re-writing when approaching expiry. This is a waste of computer resources.
The process does not check whether the cookie is approaching expiry, it just re-writes it anyway.
An improvement would be to track the state of the cookie in the server session without having to decrypt it for session handling.
Or, write something new.
Postponed
3.0
Code
Not all content is available!
It's likely this issue predates Contrib.social: some issue and comment data are missing.