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 is being developed to move one file in verified chunks, with interruption recovery and final integrity verification as its goals. 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.

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 is a separate tool under development, so there is no need to wait for a resumable-transfer engine to use Inspect.

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 is the current released tool. Each archive includes the executable, documentation, license notices and BUILD_INFO.json. Transfer is in development and has no release archive.

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

Get SHA256SUMS and compare your archive’s SHA-256 before extracting. The verification metadata records the source commit and CI coverage. Checksums detect mismatched downloads; obtain both archive and manifest through the intended project release channel.

How BitSpeed Inspect Was Tested

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

Inspect’s tests challenge its explanations as well as its ability to complete a request. Controlled local endpoints delay headers, stream bodies, redirect, return empty responses, disconnect early and wait for cancellation. A report that explains only a successful request would miss a large part of the job.

The test suite checks timing arithmetic, missing events, partial observations, source evidence links and privacy boundaries. Comparison tests cover changed payloads and encodings, mixed failures, zero baselines, insufficient coverage and overlapping ranges. The conditions and outcomes are kept in recorded results, rather than being turned into a generic speed claim.

HTTP Transfer Timing Needs More Than a Stopwatch

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

Two HTTP requests can take the same total time for very different reasons. One may spend most of its observed interval establishing a connection. Another may receive its first response byte quickly and then spend longer reading the body. A stopwatch hides that distinction.

Inspect records trace events and keeps the interval boundaries explicit. Some events can be missing or ambiguous. Concurrent connection attempts also make a neat additive waterfall less honest than it looks. The report leaves unavailable values unavailable instead of filling them with zeroes.

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 is a separate BitSpeed tool in development. Its intended job is deliberately narrow: move one source file to one destination using verified chunks, record progress and recover from interrupted work. It has no public release or binary download yet.

The development source can prepare a local immutable snapshot, calculate chunk and full-file SHA-256 digests, publish a canonical manifest and revalidate that saved snapshot later. Reuse does not require the original source file. Preparation output explicitly says that a snapshot was prepared and no transfer was performed. This local work currently targets Linux and macOS filesystems with file and directory synchronization.

Why the Project Is Called BitSpeed

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

BitSpeed is a useful name only if it leads to a clear job. For Inspect, that job is explaining where observed transfer time goes. The name should get you to a measurement you can examine, rather than a promise that every request will become faster.

That is also why the project contains separate tools. Understanding a request and moving a file safely are related problems, but they have different correctness tests. Inspect needs to keep timing evidence and interpretation apart. Transfer needs to prove which bytes survived interruption and when a complete destination can be reported.