gzl.dev/blog
field notes, mostly
18 posts
August 27, 2026
7 min
Nine ways to say yes
I taught a Light Phone to speak an Oura ring's protocol over BLE. Then I spent a week failing to tap a button that doesn't exist.
Light PhoneBrightOuraBluetoothAndroid
August 21, 2026
6 min
Field notes on LightOS
What the Light Phone III's OS actually is underneath: Android with the Google removed, hardware that talks in key events, and conventions nobody voted on.
Light PhoneLightOSAndroid
August 21, 2026
1 min
A tape recorder, not a voice recorder
BrightRecorder: clips named for where and when, tapes that are just folders of WAVs, and the wheel finally doing the job it was born for.
Light PhoneBrightRecorder
August 18, 2026
2 min
Why I put an app store on a phone designed to have none
Yes, I see the irony. The argument for building it, why there's no server behind it, and the afternoon I accidentally dropped everyone's apps from the index.
Light PhoneBrightMarket
August 14, 2026
2 min
A good fork says thank you
A lot of what I ship is other people's work with my name nearer the top than it deserves. Some rules I try to fork by.
Light Phoneopen source
August 11, 2026
2 min
My bug reports file themselves
Shake the phone three times and the app files its own GitHub issue. Then an AI triages the queue every hour — under strict instructions that guessing is worse than waiting.
Light PhoneAItooling
August 8, 2026
2 min
Fifteen copies of the same file
The least interesting code I maintain is the code I'd save first in a fire. On finally building the shared library.
Light PhoneKotlin
August 8, 2026
2 min
BrightMarket is out
The app store ships: browse on a desktop, install by QR, track updates on the phone, and get your own app into the catalog.
Light PhoneBrightMarket
August 7, 2026
2 min
One column of scores
Twenty-two leagues from four keyless public APIs, in one grayscale column. How BrightSports gets scores with no account and no push.
Light PhoneBrightSports
August 6, 2026
3 min
The MetroCard inside my phone
I dissolved a transit card in acetone and moved its nervous system into the battery compartment. Tap-to-pay is back, sort of.
Light PhonehardwareNFC
August 6, 2026
2 min
Every button does what you tell it to
The follow-up to the keylayout post: BrightControl itself, why the defaults took longer than the code, and the trust problem with accessibility services.
Light PhoneBrightControldesign
August 5, 2026
1 min
Roll is out
The camera app ships: a filter wheel on real hardware, purikura with four-shot strips, date backs, and a privacy lesson from launch day.
Light PhoneRoll
August 4, 2026
2 min
The keylayout file Light left behind
The scroll wheel is just key events. Everything I learned reading Generic.kl off the phone, and the accessibility service that became BrightControl.
Light PhoneAndroid
August 2, 2026
3 min
Rewriting the camera
Roll's whole design is one gesture, stolen from a contact sheet. Plus the filters that got away from me — purikura on a monochrome phone, and datamoshing experiments that mostly produce mud.
Light Phonedesign
July 29, 2026
1 min
A QR scanner, and its desktop twin
The modern world hands you addresses as QR codes and the Light Phone couldn't read them. A scanner for the phone, a generator page for every other screen.
Light PhoneLightQR
March 22, 2026
1 min
BasilNet, a year later
What broke, what I'd trim, and how the media server quietly became infrastructure for everything else I build.
Dockerhomelabself-hosting
March 8, 2026
1 min
I built a bad DSLR on purpose
It took worse pictures than my phone. It's one of the most useful things I've ever built.
hardwarephotography
January 10, 2025
1 min
Building BasilNet: My Home Server Stack
How I built a 15-service media server with Docker Compose, Gluetun VPN, and Home Assistant integrations.
Dockerhomelabself-hosting
← all posts
March 8, 2026 · 1 min

I built a bad DSLR on purpose

hardwarephotography

In late 2020 I built a DSLR from a Raspberry Pi, a sensor board, and a lens mount, and I want to be honest about the results: it took worse pictures than the phone already in my pocket. Slower to focus, worse in low light, heavier, uglier. By every measure that matters to a photograph, a failure.

It’s one of the most useful things I’ve ever built.

The point was never the pictures

The internet is full of Raspberry Pi cameras. I wasn’t first, I wasn’t best, and the build wasn’t even hard by maker standards — the Pi camera module does the genuinely difficult part, and my contribution was everything around it: the enclosure, the controls, the software, an interchangeable lens mount, and the hundred small decisions between “parts on a desk” and “object you can hold.”

What I wanted was to stop treating a camera as a sealed appliance. You can read about exposure all day, but writing the code that turns a sensor readout and a shutter time into a stored image installs the knowledge somewhere deeper. After the build, every camera I picked up felt legible. Menus became a UI over ideas I’d implemented badly myself.

The same winter logic produced a stranger sibling: a four-lens stereoscopic rig made from security cameras, synchronized in software to fire together, producing those wiggling 3D GIFs — wobblegrams. Built from what was in the house, because in 2020 that was the supply chain. It’s held together with more hot glue than I’ll admit to in person. It also made images no phone could, which the DSLR never managed, and there’s probably a lesson in the fact that the joke camera beat the serious one.

What the bad camera paid for later

Years later I ended up writing a camera app for the Light Phone III, and the fingerprints of that Pi build are all over it. The conviction that a camera should be operable by feel. The wheel as a physical control instead of a screen slider. The gallery as part of the camera instead of a separate app — a decision I’d first made in 2020 for the unromantic reason that I didn’t want to write two programs.

I couldn’t have told you at the time what the build was for. It cost a few months of evenings and produced a bad camera. But some projects are tuition. You don’t get the artifact; you get to be the person who made it, and that person turns out to know things.