BitSpeed Inspect Explains HTTP Transfers and Compares Saved Runs

Tue, 20 Oct 2026 00:00:00 +0000

A slow request gives you a duration. The next question is where that duration came from, and whether the same interval changed after you adjusted something. BitSpeed Inspect records the client events behind one HTTP transfer and turns them into an explanation you can revisit.

Inspect 0.1.1 is available as an independent Go command. It saves JSON, explains one recording and compares two sets of samples. Transfer has its own release and delivery checks, and neither command depends on the other.

BitSpeed Transfer Resumes Interrupted File Transfers From Verified Chunks

Tue, 20 Oct 2026 00:00:00 +0000

An interrupted transfer should not make you guess which bytes arrived. BitSpeed Transfer 0.1.0 starts with a saved snapshot, splits it into hashed chunks and asks the receiver to substantiate its progress after restart. Repeat the send command with the same snapshot and ID, and it sends the chunks still missing. The original source can stay out of the recovery path.

Completion has a separate gate. The receiver assembles the file, checks its full digest and publishes a fixed destination without replacing an unrelated file. A retained witness and stable receipt let the next request verify that same output after a lost final response. The sender checks the receipt against its manifest and saves it locally before saying transferred true. A staging result alone is not enough.

Releases on BitSpeed.org

BitSpeed Inspect Explains HTTP Transfers and Compares Saved Runs

BitSpeed Transfer Resumes Interrupted File Transfers From Verified Chunks