~ > intercept record --name "Homelab-Night_Reclaiming-the-Family-Photo-Library" --analysis-prompt "I want to move two decades of family photos off a cloud account and onto hardware I own. What setup did the speaker recommend, and what should I plan for backups and for sharing with family?" --desktop-only --chat
⚠ Point 53 Intercept is now recording.
Consent requirements vary by jurisdiction — one-party vs two-party
(all-party). Not accounting for your local law could be detrimental to
you; check it before recording.
Beginning Setup...
Loading transcription model… (first run downloads it)
⚠ faster-whisper GPU init failed (RuntimeError); falling back to CPU. Install CUDA 12 + cuDNN 9 for GPU acceleration — run `intercept doctor` for details.
Setup done.
🔌 Checking ollama connectivity...
✅ Ollama connected at http://localhost:11434.
📁 Session dir: /home/user/.local/share/point53/intercept/sessions/2026-06-07T18-19-54_homelab-night-reclaiming-the-family-photo-library
🖥️ Starting continuous recording — desktop only. [q] stop [s] interim summary
📡 Signal: ✅ Strong (548 words, 205 wpm)
🔍 Possible queries:
1. Immich self-hosted photo server
2. photo service original quality export
3. used mini PC homelab idle power draw
============================================================
📡 Signal: ✅ Strong (561 words, 210 wpm)
🔍 Possible queries:
1. ZFS mirror two disk setup
2. 3-2-1 backup rule
3. restic encrypted offsite backup
============================================================
⋮ 2 more segments · queries follow the talk as it moves on ⋮
📡 Signal: ✅ Strong (529 words, 198 wpm)
🔍 Possible queries:
1. WireGuard access for family devices
2. Immich shared albums partner account
3. photo metadata JSON sidecar merge
============================================================
⏭️ Finishing current chunk, then stopping...
📡 Signal: ✅ Strong (517 words, 194 wpm)
🔍 Possible queries:
1. verify photo export checksums
2. exiftool merge sidecar metadata
============================================================
🧠 Summarizing using cogito:32b
Here's a summary of the homelab meetup talk on self-hosting a family photo library:
Key Points:
1. The speaker moved roughly twenty years of family photos (~340 GB) off a cloud photo service and onto a used mini PC running Immich. The framing throughout is data ownership rather than cloud avoidance for its own sake: phones still auto-upload — they just upload to hardware the family owns.
2. Recommended setup:
- Used NUC-class mini PC; put the savings into two good disks in a ZFS mirror
- Immich for the library itself — mobile auto-upload, shared albums, face and place search, all indexed locally
- Export from the old provider at original quality first, before canceling anything
3. Backups:
- The mirror is availability, not a backup — the 3-2-1 rule still applies
- Nightly restic snapshots, encrypted before they leave the machine, to one offsite target
- A yearly restore drill: pull one month of photos back and actually open them
4. Sharing:
- Family phones reach the server over WireGuard; nothing is exposed to the public internet
- Grandparents get shared albums through the same tunnel rather than a public link
Practical details:
1. Keep the export's JSON metadata sidecars — dates, locations, and album structure live there, and tools can merge them back into the image files
2. Verify file counts and checksums against the cloud library before deleting anything at the source
3. Total cost was under $300 plus disks; the machine idles around 12 W
🧠 Completing post-analysis with gemma4:31b
Based on the transcript and summary, here is the setup the speaker recommended and what you should plan for, given your goal of moving two decades of photos onto hardware you own.
### 1. The Migration Comes First
* **Export at original quality, with sidecars.** Your dates, locations, and album structure live in the JSON sidecar files that ride along with the export. Losing them was the most common regret raised in the talk's Q&A.
* **Verify before you delete.** Compare file counts and spot-check checksums between the export and the cloud library. Cancel the subscription only after the photos open from *your* disk.
### 2. Hardware and Software
* **A used mini PC is enough.** Serving a photo library is light work; the speaker's machine idles around 12 W. Put the budget into the disks instead.
* **Two disks, mirrored (ZFS).** One disk failing should be an errand, not an emergency.
* **Immich** keeps the parts of the cloud experience worth keeping — phone auto-upload, shared albums, search — with the index built and stored locally, on your machine.
### 3. What to Plan For
* **Backups:** the mirror protects against a disk failure, not a mistake. Nightly snapshots, encrypted on your machine before they go anywhere (restic), to one offsite target completes 3-2-1.
* **Family access:** WireGuard from every family device to the server; shared albums travel inside the tunnel instead of over a public link.
* **A restore drill:** once a year, restore one month of photos somewhere fresh and open them. A backup you have never restored is a hope, not a plan.
⋮ metadata merge walkthrough · a first-90-days checklist — condensed for display ⋮
✅ Session saved to: /home/user/.local/share/point53/intercept/sessions/2026-06-07T18-19-54_homelab-night-reclaiming-the-family-photo-library
💬 Chat session with qwen3.6:27b — Ctrl+C to exit.
Session transcript and analysis loaded. Ask away — the migration, the backups, or the sharing setup.
…