Summary
The packet list shows only the first resolved source/destination candidate, even when the server returns multiple nodes with ambiguous confidence. Its native title repeats that single name. This can make an arbitrary short-hash match look like the actual sender/recipient.
The detail view already shows all candidates through PathData's popover. I will reuse that behavior in list endpoint chips, show the additional-match count, and cover hover, keyboard and touch interaction without triggering row selection. Preserve direction, confidence colors, unresolved states, advert/ACK/trace summary fallback and the existing API shape.
Found while investigating the supplied TXT_MSG screenshot; current server decoding follows destination byte then source byte correctly. This issue is the list presentation of ambiguous matches.
Summary
The packet list shows only the first resolved source/destination candidate, even when the server returns multiple nodes with ambiguous confidence. Its native title repeats that single name. This can make an arbitrary short-hash match look like the actual sender/recipient.
The detail view already shows all candidates through PathData's popover. I will reuse that behavior in list endpoint chips, show the additional-match count, and cover hover, keyboard and touch interaction without triggering row selection. Preserve direction, confidence colors, unresolved states, advert/ACK/trace summary fallback and the existing API shape.
Found while investigating the supplied TXT_MSG screenshot; current server decoding follows destination byte then source byte correctly. This issue is the list presentation of ambiguous matches.