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.
Explore the mess / 25 entries
Projects, experiments, and notes involving programming. Follow a topic across otherwise unrelated rabbit holes.
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 closer reading of the saved generation engine, configuration state, source rules, manual-draft recovery, and browser storage.
From a two-column prompt composer to the saved implementation: controls, generation rules, presets, manual edits, and the character budget.
A one-task-at-a-time development workflow exposed gaps in task authority, then changed direction toward a reusable project template.
Separating reusable graph structure from Crushline recipes, consequences, rendering, and runtime evaluation.
A Linux-native C11 platform layer grew out of custom node-graph UI work, with narrow contracts for windows, input, drawing, files, and replay.
Exploring a self-hosted AI workspace led to authorization hardening, blocking CI, local release checks, and a first-run setup test that exposed a missing-directory problem.
A node-based factory game built around competing production routes, useful waste, machine upgrades, and the freedom to build an inefficient line.
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.
The M3 simulation panel became visible, then exposed a separate problem: its command editor could not be edited.
A generation-ship simulation built around fragile knowledge, followed by a long interface search from command board to a clearer Godot workstation.
A browser pixel experiment grew into a C++ ecology sandbox with inherited traits, grazing, local nutrients, CSV telemetry, and measured performance bottlenecks.
A Rust simulator for explicit authority, with capability and policy checks, atomic audit rules, replay experiments, and a concrete Stage 1A failure.
A local AI desktop concept developed around Linux identities, a trusted broker, staged outputs, and evidence that could actually support its security claims.
Building Linux From Scratch in a VM: host checks, the cross-toolchain, chroot, package corrections, and test results that were not uniformly clean.
An Obsidian archive design that splits conversations into durable ideas and keeps productive drift visible.
A compact project-instruction platform explored exact manual edits, source fingerprints, validation gates, and self-contained project capsules.
A Python prototype explored identity through player actions, while schema mismatches exposed the need to validate the links between actions and projects.
A spreadsheet and web-app concept connecting transaction records to priorities, with a three-sheet starting point and a concrete review workflow.
An archive design that preserves topic drift, separates transcripts from concept notes, and keeps source dates distinct from import dates.
A general decision framework became a game about balancing usable possibilities, with weighted priorities, signals, dials, and explicit prototype equations.
A card-driven village concept with concrete resources, relationships, story templates, and an AI-generated Godot prototype structure.
A single-file C/SDL2 draft models one hundred moving agents with position, velocity, and simple boundary bounces.
Three generated game sketches moved from a console character to an SDL rectangle and a rough C++ room-and-combat model.
An oversized operating-system request narrowed into a small C++ wrapper that opened an SDL window and drew one rectangle.