Skip to content

v0.3.4 — Persisted install-id telemetry

Choose a tag to compare

View all tags
@Craig-Horton Craig-Horton released this 09 Jun 16:59
· 98 commits to main since this release
v0.3.4
4da9500

aibvf-mcp 0.3.4

Changed

  • caller_hash is now sha256(installId + day), where installId is 16 random bytes generated on first run and persisted to ~/.config/aibvf/install-id. Stable per install (so distinct-caller counts are genuine distinct installs, not per-process randoms) yet high-entropy, so the hash can't be reversed to a machine or person.
  • Created lazily on first telemetry send, and skipped entirely when opted out — AIBVF_TELEMETRY_DISABLE=1 writes no file.
  • Falls back to a per-process random on read-only filesystems (failing closed).

Fixed

  • Stripped a stray NUL byte from the caller_hash template that made tooling flag the source as binary.

The install-id never leaves your machine; only the daily-rotated hash is sent. No payload fields changed.

Assets 2
Loading