The work is less a Utilities/Games filing cabinet than a family tree. Follow the protocols, patterns, worlds, infrastructure, and mistakes that moved from one project into the next.
A connection may be a protocol, an operational dependency, a reused application shape, shared fictional material, or simply a lesson carried forward. Every line says which one and links to the evidence behind the claim.
A modern reimagining of WASTE — encrypted P2P chat and file sharing over WebRTC, with no server in the data path.
Project write-up →Ephemeral, end-to-end encrypted file transfer between your own devices. AirDrop for people who self-host.
Project write-up →Short-lived, end-to-end encrypted file sharing. Upload once, the recipient retrieves it later, and then it's gone for good.
Project write-up →Self-hosted private image gallery for browsing large photo collections organized in a flexible hierarchy.
Project write-up →Self-hosted read-later. Click 'Send to stash' in the browser, the article's content is extracted and stored on your own server — full-text searchable, no third party ever sees your reading list.
Project write-up →A phone-photo editor with a 'develop it later' option. Film-style effects in the browser, then download instantly or send it off to develop behind a randomized hours-to-days delay.
Project write-up →A fun little roguelike experiment — quick runs, weird builds, and learning-by-doing.
Project write-up →A Slay-the-Spire-style deckbuilder set in the Delve universe — same lore, different combat. Build a deck, descend three acts, fight the Pale King.
Project write-up →Reusable narrative, bestiary, characters, and places kept outside any single combat system.
Art, creature identity, locations, and the asset pipeline shared across presentations of the world.
A self-hosted, end-to-end encrypted secrets store for deploy scripts. keep pull myapp/production gets you a decrypted .env — the server never sees plaintext, or the key that would let it.
Project write-up →The build, registry, secret retrieval, Compose, health, and receipt path shared by deployed projects.
The sanitized public explanation of how source becomes a running, observable deployment.
An in-progress private incident notebook designed to correlate evidence, commits, and deployment receipts.
Reviewed public accounts of bugs, dead ends, and wrong assumptions—never an automatic error feed.
A small service that reads proxy hosts from Nginx Proxy Manager and HTTP-checks them on a schedule. Serves a live status page and a JSON API.
Project write-up →The operational view combining service health, metrics, and deliberately public status.