Updated the logic for following a message's thread_back/thread_next &...
Updated the logic for following a message's thread_back/thread_next & thread_id matching (using the ( and ) keys): Now first checks to see if thread_id is available (it checks to see if running Synchronet 3.16 and thread_id exists in the headers), and uses thread_id if available; if thread_id is not available, then it falls back on using the thread_back & thread_next fields.
Please register or sign in to comment