Drop the self-hosted integration batch, and say why

The machine runs essentially every popular self-hosted service, and on looking at them the batch was revised once and then dropped. Almost all of it is infrastructure for other services rather than anything a desktop consumes -- whisper there feeds Bazarr subtitles, not dictation here -- the desktop has the better GPU anyway, and the one genuinely desktop-shaped idea is already solved by an installed application. Recorded rather than deleted so it is not proposed again, with the lesson that matters: a service existing is not a reason to integrate it. Claude-Session: https://claude.ai/code/session_01BRvzt4H8XXLPVH5MyYdk9L
2026-08-19 18:38:19 -04:00
parent a15f019c17
commit edc504af2e
1 changed files with 32 additions and 1 deletions
@@ -89,7 +89,38 @@ can return is one the doctor counts.
 ---
-## Batch 2 — Your infrastructure
+## Batch 2 — Your infrastructure — DROPPED 2026-08-19
 Recorded rather than deleted, so it does not get proposed again.
 The machine turned out to run essentially every popular self-hosted service:
 Immich, Beszel, Uptime Kuma, Sentry, Gitea with runners, Jellyfin, Plex, RomM,
 SearXNG, Open WebUI, ollama, ComfyUI, whisper, piper, the *arr stack, Vaultwarden
 and more, across a home server and a VPS. On seeing it, the plan below was
 revised once (read Beszel and Uptime Kuma rather than reimplement their polling)
 and then dropped entirely, on Gabriel's judgement, which was right:
  * Almost all of it is infrastructure FOR other services rather than anything a
    desktop would consume. whisper on the server exists to feed Bazarr's
    subtitles, not to transcribe speech here.
  * The desktop has a better GPU than either server, so anything worth running
    for the desktop's sake should run on the desktop.
  * The one genuinely desktop-shaped idea -- dictation -- is already solved on
    this machine by Wispr Flow.
 The lesson is worth keeping: the services existing is not a reason to integrate
 them. A page earns its place by answering a question someone actually asks, and
 "is my media server up" is a question Uptime Kuma already answers better,
 somewhere the desktop is not.
 **Possible survivors, both local rather than remote.** The Nextcloud desktop
 client runs here and its sync state is a real desktop concern in the way iCloud
 Drive is; RustDesk is installed here and pairs with the RDP controls already
 built. Neither is "reach into my server", which is what was dropped.
 ---
 ## Batch 2, as originally written
 The part no shipped operating system has, because no shipped operating system
 assumes the user runs the servers.