How the anarchive's media survives on one node — the Kubo mechanics of the Homebase: a self-hosted node on the Pi5 plus Filebase remote pinning, with content addresses (CIDs) recorded on every media page. The ring strategy, allocation policy and budget live on Anarchive Pinning; this page is the node mechanics. Part of the Anarchive Media Plan.
## Kubo on the Pi5
The Pi5 hosts the X9 drive at `/mnt/wikimedia` and already runs the public farm mirror — macOS blocks external-volume access over SSH, so the Mac is the wrong host. The Pi's node pins everything: full 420px videos, clips and sidecars.
# on the Pi5 — the repo lives on the X9 drive export IPFS_PATH=/mnt/wikimedia/ipfs KUBO=v0.36.0; ARCH=$(dpkg --print-architecture) wget -qO- "https://dist.ipfs.tech/kubo/$KUBO/kubo_${KUBO}_linux-${ARCH}.tar.gz" | tar -xz sudo bash kubo/install.sh ipfs init --profile=server nohup ipfs daemon >/tmp/ipfs.log 2>&1 & # wrap in a systemd unit for boot
## The Running Node
Live since 15 July 2026. Kubo 0.36.0 installed to `~/.local/bin` (sha512-verified, no sudo), repo at `/mnt/wikimedia/ipfs` on the X9, run by the systemd user service `ipfs.service` (linger on, survives reboot). - peer ID `12D3KooWRzGtcyEFDbWJNVHgjFrv7v2BAnKLoz6aHrxt9LYhfUpj` - gateway `127.0.0.1:4281`, API `127.0.0.1:4282` — 42xx per the house port policy - first pinset: the referenced media of the David-owned public sites, CID-verified against the Nextcloud originals
## Filebase Remote Pinning
Filebase's free tier is the best on offer: 5 GB storage, 1,000 pinned files, 5 GB egress, and the standard IPFS Pinning Service API alongside an S3-compatible API. The budget rule: remote-pin fair-use clips and sidecars — transcripts, thumbnails, metadata — never full videos. Filebase is the first member of the pin ring; the full ring lives on Anarchive Pinning.
# token from filebase.com → Access Keys — keep it in the environment, # never inline on a wiki page ipfs pin remote service add filebase \ https://api.filebase.io/v1/ipfs "$FILEBASE_TOKEN" ipfs pin remote add --service=filebase \ --name="$SLUG-clip" "$CID"
## Recording the CID
Every pinned file is recorded three ways: a machine-readable `cid` field inside the media item JSON — the Media Plugin contract; a human-readable gateway link in the page's links section; and the file's own name, which carries the CID itself per the Filename Convention. Playback falls back through gateways in order: the Pi5's own gateway first, then `dweb.link`.
## Links
- Filebase 
— the remote pinning service
- Kubo CLI reference
- IPFS Pinning Service API spec
## See
- Anarchive Pinning and Homebase — the strategy and the role this node plays - Anarchive Media Plan — the architecture this survivability layer serves - Media Plugin — where the CID is recorded and resolved - Fair Use Clip — the discipline that keeps remote pinning within the free tier
# Assets
ipfs-pinning