A thin-client Linux experiment
A network-boot question became a comparison of separate remote desktops and shared physical desktops, ending with a usable Linux thin-client session and working audio.
What happens if…
Small tests, rough prototypes, and the occasional dead end. An experiment doesn’t have to work to be worth keeping.
Nothing matches those filters.
Try a broader term, or follow a topic link in the archive.
Browse the notebook →A network-boot question became a comparison of separate remote desktops and shared physical desktops, ending with a usable Linux thin-client session and working audio.
A local AI setup narrowed to a concrete Docker-to-host networking problem: the model answered directly, while the container path needed a firewall change.
A proposed technology-mod stack became a practical test of what was installed, enabled for a world, and actually visible in the workbench.
A worn generation ship became the setting for an automation game built around machine networks, repair detours, and a small playable Godot workshop.
A skyblock base grew from an unbuilt floor plan into automation, a cramped service layer, a room retrofit, and recurring power constraints.
A one-task-at-a-time development workflow exposed gaps in task authority, then changed direction toward a reusable project template.
The Long Wake tried a Svelte command interface, achieved working drill-down panels, and then returned to a Godot desktop-workstation direction after repeated layout failures.
A browser pixel experiment grew into a C++ ecology sandbox with inherited traits, grazing, local nutrients, CSV telemetry, and measured performance bottlenecks.
A personal lab for watching how an ordinary sudo-capable agent handled normal Linux tasks, including malformed actions and a suspected loop.
From a short image-to-video reel to a basic text-to-image graph, with the actual nodes, settings, and failures that shaped the experiment.
A Python prototype explored identity through player actions, while schema mismatches exposed the need to validate the links between actions and projects.
An archive design that preserves topic drift, separates transcripts from concept notes, and keeps source dates distinct from import dates.
A failed coating led to the corrected flour–egg–crumb method, a thin-chop recipe, and a cooking-time table.
The peach-syrup formula, a batch that stayed thin, and the ratios discussed for an eight-cup pitcher of iced tea.
A blue wildflower photograph led to a tentative Penstemon identification and a list of alternatives to compare.
A turn-by-turn science-fiction story changed from surveillance and resistance into unstable realities, time travel, loss, and an altered future.
Two small assistant-generated guitar sketches: a repeated single-note riff and a sixteen-bar jazz chord sequence.