How the anarchive hosts voice recordings — the audio wing of Anarchive Hosting. Recordings are captured on a private wiki on the Pi5, transcribed and summarised locally, then archived to the public federation with the audio content-addressed on IPFS. The design follows the house rule: cheap origin, zero-egress front, names that outlive any host.
## The Canonical Archive voice.anarchive.earth is the archive of record. Each recording's page carries the player and transcript sidecars; the audio file is named by the Filename Convention — cid_<CID>_<slug>.m4a — so the file identifies itself wherever it lands. One farm copy lives on the Pi5's X9 drive (the Mirror Farm master), synced up through Nextcloud to the live servers; the same bytes are pinned on the Homebase IPFS node and remote-pinned to Filebase, so the caption's ipfs link resolves from any gateway.
## The Journey of a Recording Capture (private Pi wiki, whisper transcript, AI synopsis) → archive (ipfs add, rename to the cid_ name, one move into the canonical assets) → a topical home in the federation, found by searching the whole farm galaxy — the page forks there, its red links get stub pages, and fork journal events twin everything back so links resolve across the neighbourhood.
## Deletion Is Deliberate Trashing the capture page retires every twin into its own site's recycler and parks the audio in recycle-assets — recoverable, pins intact. Only deleting the page a second time from the capture wiki's recycler confirms the purge: pins are released on the Homebase and Filebase and the recycler copies deleted. Unpinning withdraws our commitment to host; copies already cached by other peers stay wherever they are — that is the nature of a content-addressed commons.
## Links
- voice.anarchive.earth 
— the archive itself
- Filename Convention and IPFS Pinning — the conventions this follows
# See - Anarchive Hosting — the cost survey this belongs to - Federated Pinning Service and Cheap Object Storage - Anarchive Media Plan — the video-side parallel