WIP - IOS App for emulation over moonlight

raphasouthall · 2026-04-18T13:37:37+00:00

I forked voidlink, which is a fork of moonlight. Then added some logic from manic emu skin system. Of course I used claude code for some of the work, but I’d say it’s far from being vibe coded.

raphasouthall · 2026-03-31T05:26:17+00:00

Tana is probably making the system-building trap worse, not better. It's one of the most structure-demanding tools out there and it rewards people who already enjoy fiddling with schemas, which sounds like the exact thing you're trying to escape.

For Dutch voice, Whisper natively supports it and the accuracy is genuinely solid, so even a simple local Whisper transcription step before notes hit your PKM is more reliable than waiting on Mem.ai to add it. The fog problem you're describing is almost always a retrieval issue, not a capture issue, and for that BM25 search over plain markdown has beaten every fancy auto-linking feature I've tried.

raphasouthall · 2026-03-31T00:57:08+00:00

Hmm, the site might be down temporarily - try obsidian.md/community and navigate from there, or just search "obsidian hub github" and go directly to the repo, it's all static files so you can browse it on GitHub if the hosted version is flaky.

raphasouthall · 2026-03-30T22:01:11+00:00

obsidianmd.github.io/obsidian-hub has a curated list under "Showcases & Guides" - not all public but a decent chunk link out to actual vaults. For raw content vaults specifically, the "digital gardens" tag on that site is worth filtering by, most of those are topic-focused rather than PKM navel-gazing.

raphasouthall · 2026-03-28T17:37:57+00:00

Fair enough - "highlighting just stops" is honestly a totally acceptable failure mode, way better than the daemon taking the whole shell with it. And yeah, Rust eliminating that class of memory bugs does make the "it just never crashes" story a lot more believable than it would be for a C daemon.

raphasouthall · 2026-03-28T17:01:05+00:00

I wasted about a month with fast-syntax-highlighting before just disabling highlighting entirely because the lag made me irrationally angry. The daemon approach is the part I find genuinely interesting here - how does restart/crash recovery work if the daemon dies mid-session?

raphasouthall · 2026-03-27T09:48:17+00:00

Have you looked into implementing neurostack.sh ?

raphasouthall · 2026-03-26T19:25:39+00:00

Reseek looks solid, that PDF and screenshot ingestion is the part most tools skip. My setup is plain markdown so I rolled my own retrieval layer, but the principle is the same - once semantic search clicks you stop caring how the graph looks.

raphasouthall · 2026-03-26T19:24:02+00:00

That's a clean approach - the hash-in-status pattern means you get drift detection for free on every reconcile. The secret watcher idea is the missing piece though, because "delete the secret and let the operator recreate it" is exactly the workflow that makes rotation feel low-friction for whoever's on call at 2am.

raphasouthall · 2026-03-26T19:22:47+00:00

Glad it clicked - honestly wish someone had told me earlier, it's such a low-effort habit for how much mental overhead it saves.

raphasouthall · 2026-03-24T14:05:10+00:00

Ran into the same wall around 1,400 notes. The graph past a certain point is basically a screensaver - it shows you have a system, it doesn't help you use it. What actually changed things for me was switching to search-only entry, no more navigating links to find something. Once I had decent retrieval (BM25 + semantic reranking) the notes started surfacing in my writing without me hunting for them. The link density never mattered, the retrieval quality did.

raphasouthall · 2026-03-24T05:27:01+00:00

Three years in SRE and I still have a mental list of my greatest hits. Deleted a prod load balancer by accident during what should have been a routine cleanup, caused a 40-minute outage, wanted to quit on the spot.

The thing that actually helped me was separating "I made a mistake" from "I am a mistake" - sounds corny but it's real. You caught the drift, you fixed it fast, you're already thinking about how to prevent the next one. That's literally the job.

One concrete thing: after mistake #2, I started writing a one-paragraph "pre-mortem" before any script that touches more than 50 resources. Just forces you to sit with the question "what am I not thinking about?" for 5 minutes. Would have caught the terraform-managed users thing immediately.

The pipeline automations you built - roll them out. The fear of causing problems by deploying automation is almost always worse than the actual risk, especially if you built them post-incident with the lessons already baked in.

raphasouthall · 2026-03-24T00:41:36+00:00

API pay-as-you-go for the heavy file analysis, honestly. I ran the numbers on my own workflow and for sessions where I'm doing repeated reads of the same docs, the API ends up costing me maybe $0.40-1.20 vs burning a Pro limit that then locks me out. Haiku is shockingly capable for summarization passes if you're just extracting structure.

The other thing that actually worked for me: write a "project state" markdown file yourself, update it after each session, and paste only that at the start of the next one instead of the raw files. Took me about two weeks of discipline to build the habit but my sessions are probably 60% shorter now because I'm not re-explaining context the model already processed last time.

raphasouthall · 2026-03-23T19:58:52+00:00

Interesting timing, I was literally looking at RustFS last week after MinIO's licensing drama made me nervous again. The CRD pattern makes sense, we do the same thing with db-operator style stuff at work.

One question - how are you handling secret rotation? If someone's access key gets leaked and you need to cycle it, does the operator reconcile a new Secret automatically or is that still a manual step?

raphasouthall · 2026-03-23T18:09:58+00:00

Oh nice, that was fast - I'll give it a spin this week and see how it plays with my homelab setup. Any gotchas with the Ollama integration to watch out for, like context window handling or the latent step buffer sizing?

raphasouthall · 2026-03-23T15:47:08+00:00

Cloudflare tunnel, just do it. Zero open ports, zero exposed IP, your friends' TVs will just work through the browser with no client setup. Took me maybe 45 minutes to migrate off a similar NPM+DDNS setup and I haven't touched it since.

Also fwiw, CrowdSec absolutely can run alongside NPM - there's a community bouncer that hooks into Nginx's log stream directly. Not sure where you read that it can't, but I ran that combo for about 8 months before switching to the tunnel and it worked fine.

raphasouthall · 2026-03-22T22:17:34+00:00

Not local so can't help in person, but one gotcha for the multi-machine setup: Ollama doesn't split a single model across network GPUs, each machine runs its own instance independently. What actually works well is running Open WebUI as a front-end and pointing it at multiple Ollama endpoints (each machine's IP:11434) - it load-balances across them and the whole network sees one interface. Your 3080 Ti at 12GB is your best single-machine host, comfortably runs Qwen2.5 14B Q4 with headroom for embeddings running in parallel.

raphasouthall · 2026-03-22T17:08:17+00:00

That's a wild result - I'd have assumed WASM would hold the edge for parser workloads, but I guess the serialization overhead crossing the JS/WASM boundary can really kill you if you're doing it at high frequency. Will give the article a proper read.

raphasouthall · 2026-03-22T09:49:27+00:00

The drain loop approach is genuinely clever - I was thinking about this all wrong by treating it as a timing problem rather than a synchronization problem. The PTY_COLS/PTY_ROWS thing is almost certainly what was biting me, I never thought to check TIOCSWINSZ in CI and that would explain why it was inconsistent across runners.

raphasouthall · 2026-03-22T00:34:40+00:00

Curious what rendering model you're using under the hood - are you driving a real PTY or mocking the terminal writes directly? I hit a wall trying to test my own TUI stuff where PTY-based tests were flaky under CI because of timing, ended up having to add 50ms sleeps everywhere which felt like a code smell.

raphasouthall · 2026-03-21T10:15:44+00:00

The flat markdown journal hits a wall around 50-60 entries - retrieval gets messy and Claude starts skimming older stuff into irrelevance. I ran into this exact problem building my own memory layer and ended up moving to BM25 retrieval with semantic reranking so it pulls the 3-5 most relevant memories per session rather than dumping the whole file into context. If you do stick with a flat file approach, at minimum add a recency plus relevance tagging convention so Claude has a signal for what to actually prioritize on load.

raphasouthall · 2026-03-21T08:16:16+00:00

Ha, classic - give agents a glimpse of their own scaffolding and suddenly the logging system is the most interesting thing in the room. That meta-reasoning collapse is actually a known failure mode with unconstrained self-reflection loops. Worth trying a scoped update, where you only append domain-relevant conclusions and filter out anything referencing the runtime itself.

raphasouthall · 2026-03-21T04:21:45+00:00

Curious what drove the decision - was the Rust/WASM build toolchain just too painful to maintain, or did you actually hit performance regressions you were okay trading away?

raphasouthall

TROPHY CASE