Pages on BitSpeed.org

About

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

BitSpeed.org is home to two independent Go tools. Inspect explains one HTTP transfer from the client side and compares saved runs. Transfer moves one file in verified chunks, resumes interrupted work and checks the full file before publishing its destination. Each has its own command and release status.

Inspect 0.1.1 is available now. It records trace events, redirects, observed body bytes and partial failures as JSON. Its reports distinguish measurements from calculations and labelled interpretations. A first-byte wait is evidence about an interval, not proof that a database or server CPU caused the delay.

Contact

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

Write to info@bitspeed.org with questions, feedback or a reproducible problem. For a software issue, the GitHub issue tracker is also available.

Include the command version, operating system, command options and what happened. Review any recording before sending it: query values and fragments are redacted, but paths, hostnames and location labels can still disclose private information. Do not send credentials or tokens.

Download

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

Inspect 0.1.1 and Transfer 0.1.0 are independently released. Each archive includes its executable, documentation, license notices and BUILD_INFO.json. Choose the tool and check the platform coverage before downloading. The first table is Inspect.

Platform	Download	Coverage
Linux amd64	tar.gz	Native archive smoke tested
Linux arm64	tar.gz	Cross-built only
macOS arm64	tar.gz	Native archive smoke tested
macOS amd64	tar.gz	Cross-built only
Windows amd64	zip	Native archive smoke tested

Transfer 0.1.0 supports one-file delivery on supported Linux/macOS local filesystems. Its Windows archive is a compatibility check, not a delivery tool.

Inspect

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

Inspect tells you where measured HTTP transfer time goes. Run it against an HTTP or HTTPS URL, save the recording and ask it to explain the observed events. Collect a second recording after a change and compare the two. The command is bitspeed-inspect; version 0.1.1 is released.

The useful distinction is between what the client saw and what it can infer. DNS events, connection attempts and response bytes are observations. An interval or median is calculated from those observations. Interpretations cite their evidence and rules. Missing or ambiguous events stay unavailable rather than quietly becoming zero.

Quick Start

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

Download Inspect for your platform from Download, verify its archive checksum and extract it. The examples below use ./bitspeed-inspect; on Windows use bitspeed-inspect.exe.

./bitspeed-inspect --version
./bitspeed-inspect record --samples=3 --timeout=10s https://example.org/ > run.json
./bitspeed-inspect explain run.json
./bitspeed-inspect explain --format=json run.json

A failed request can still produce useful partial JSON. record exits nonzero when samples fail or the batch is cancelled. Explaining a valid failed recording can succeed. Review stderr and the saved outcome before treating a recording as complete.

Reference

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

The README is the command manual. The repository keeps the detailed contracts beside the implementation and tests.

Inspect has a versioned recording format, explanation rules, comparison rules and release packaging reference. These specify interval boundaries, evidence links, unavailable values, comparability checks and platform coverage.

The controlled demo and saved recordings can be explained or compared without accessing an external server. Recorded test results include environments and outcomes. The release verification evidence covers public archive hashes and a downloaded Linux executable.

Transfer

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

Transfer 0.1.0 moves one file to one destination using verified chunks. It prepares an immutable sender snapshot, records its manifest, stages missing chunks and resumes using the same snapshot and transfer ID after interruption. The original source is no longer needed once preparation completes.

The receiver revalidates saved chunks instead of trusting a progress counter. Finalization assembles the file, checks its complete SHA-256 digest and publishes a fixed destination without replacing an unrelated file. A retained witness and stable receipt let a retry verify the same output after a lost response. Send reports completed delivery only after checking that receipt against the snapshot and saving it locally. Upload-only remains an explicit staging operation and does not claim delivery.