Problem
In the response-gathering loop (scripts/telegram_extract.py, lines 52-71), when a non-message item is encountered (e.g. a service event), the loop does j += 1; continue before the ownership check. This means messages[j - 1] on the next iteration now points to the skipped service event, silently corrupting the time gap measurement and potentially breaking an otherwise valid response chain.
Steps to reproduce
Have a chat where a service event (e.g. a photo, pin, or call) appears between two of your consecutive messages. The second message may be incorrectly excluded from the response chain.
Expected behavior
Non-message entries should be skipped without affecting the time gap reference used for chaining.
Problem
In the response-gathering loop (
scripts/telegram_extract.py, lines 52-71), when a non-message item is encountered (e.g. a service event), the loop doesj += 1; continuebefore the ownership check. This meansmessages[j - 1]on the next iteration now points to the skipped service event, silently corrupting the time gap measurement and potentially breaking an otherwise valid response chain.Steps to reproduce
Have a chat where a service event (e.g. a photo, pin, or call) appears between two of your consecutive messages. The second message may be incorrectly excluded from the response chain.
Expected behavior
Non-message entries should be skipped without affecting the time gap reference used for chaining.