serial-bench / by thread
Grouped by bus, which is as close to threading as a one-writer list gets. Where a later message answered an earlier one it is indented under its parent; the In-Reply-To header on the message page points the same way.
Differential, arbitrated and unforgiving about both ends of the wire. One thread, root then follow-up: the missing terminator first, the sample-point disagreement a fortnight later.
Two free-running clocks pretending to agree. A single message; the whole bus fits in one asynchronous frame.
Open-drain, two wires, failures that hide in the edges. The rise-time post is the root; the clock-stretch one replies to it a few months on.
Fast and forgiving until the timing diagram you did not draw catches up. The CPHA mismatch opens the thread; the daisy chain answers it.
Long, slow, differential and tangled up with the grounds at each end of a building. One message.
Not a bus at all, but the message that decides whether anything above it counts as evidence. The first post on the list.
These groupings come out of one small static file, served as-is for anything that would rather read the list as data than scrape the pages:
id (the page path), title, date (ISO), bus, tags and a one-line summary. No tracking fields, because there is nothing to track.