Systems are
made to be
understood.
Clear, tested thinking for Linux, self-hosting, privacy and the web that connects them. Read the reasoning before you run the command.
EXPLORE THE NOTESA guide earns its place when a reader can see what to check, what might break, and how to recover.
Nine questions worth asking.
Old questions. New checks. Each note begins with the state of the tools today.
Design an encrypted, impermanent root
A storage map and recovery checklist before the first reboot.
READ THE NOTE ↗ 02 / GRAPHICSROCm and Resolve: verify compatibility first
Separate driver, runtime, packaging and application problems.
READ THE NOTE ↗ 03 / WEB OPSRead bot traffic without guessing
Turn request logs into a measured response, not a reflexive blocklist.
READ THE NOTE ↗ 04 / NETWORKBuild for the slow connection
Measure the bottleneck and design pages that remain useful when the link barely works.
READ THE NOTE ↗ 05 / LINUXShould you keep NixOS?
A decision framework for reproducibility, recovery and daily friction.
READ THE NOTE ↗ 06 / PRIVACYWhat encrypted email protects
Distinguish transport, storage and end-to-end protection before choosing a service.
READ THE NOTE ↗ 07 / MOBILEEvaluate GrapheneOS first
Check support, essential apps and recovery before changing your daily phone.
READ THE NOTE ↗ 08 / TOOLSChoose apps you can leave
Keep notes, files and accounts portable when your default tools change.
READ THE NOTE ↗ 09 / WEBChoose the stack by constraint
A decision method for static files, server rendering and necessary state.
READ THE NOTE ↗10 / METHODSBcachefs kernel history: how to check an old merge prediction
A source-led method to verify dated claims about bcachefs and Linux kernel releases before repeating them.
READ THE NOTE ↗11 / METHODSV1T CTF 2025: a map of the former write-up and how to read it
An independent guide to the challenge categories covered by the former V1T CTF 2025 write-up and a reproducible way to study them.
READ THE NOTE ↗12 / METHODSThe modern web: a practical privacy and resilience checklist
Evaluate browser privacy, ad blocking and site dependencies with a threat model instead of a single perfect-browser claim.
READ THE NOTE ↗13 / METHODSHow to test political bias in AI without inventing a score
A reproducible protocol for comparing AI responses across prompts, dates, models and languages without claiming a universal bias score.
READ THE NOTE ↗14 / METHODSLinux desktop share: what a milestone number actually measures
A method note on browser-based operating-system share, historical Linux milestones and the limits of global percentages.
READ THE NOTE ↗Evidence first.
Then the fix.
Many old technical posts preserve a good question while the exact command has expired. We keep the question, check current primary documentation and explain the failure modes.
SEE OUR EDITORIAL METHOD ↗This domain previously hosted a personal technical blog. Open Systems Fieldbook is an independent publication by a new operator. It does not claim the former author's identity or work.
About the transition ↗