Photo Management

Here’s a problem that sounds harder than it is. New files arrive on the cutting board every hour. I sort them in passes, over several days. The automatic check keeps copying. So how does the same photo never get imported twice? No database. One small ledger, plus a cheap shortcut, do the whole job. The Ledger Does the Real Work When the hourly check copies a file onto the cutting board, it writes one line in a small record — a plain text ledger I’ve been calling R throughout this series. ...

There’s no database behind my daughter’s archive. No table of photos, no index, no metadata store. When the app needs to know what’s in “July 2026,” it opens the July 2026 folder and looks. That sounds lazy. I’d argue it’s the opposite — it’s the one decision that keeps the whole system simple enough for one person to maintain. How It’s Organized The archive is just folders on the NAS: ...

By this point in the pipeline, the boring parts are done. New files have been copied to the cutting board. I’ve picked out the ones that are my daughter. What’s left is the step that turns “a pile of selected files” into “a browsable month in her archive.” That’s one button. By now the picker has already moved my chosen files into a hand-off folder. In the app’s My Records tab, there’s a count of what’s waiting in that folder, and next to it a button that says, in effect, bring these in. I press it, and the rest happens on its own. ...

Here’s the plan I was sure would work: point an AI at a folder of thousands of mixed photos, give it a few pictures of my daughter, and let it pull out every photo of her automatically. No more manual sorting. It didn’t work. And the reason it didn’t work is interesting enough that I want to tell it straight, including the part where I was wrong. The Idea Face recognition is a solved problem, right? Phones do it. The plan was: ...

Everything else in this pipeline runs by itself. This is the one part that needs me: looking at the day’s new files and choosing which ones are actually my daughter, worth keeping in her archive. For that I built a small browser gallery. It shows the files waiting on the cutting board, I tap the keepers, and press a button. That’s the whole job. But a few small choices made it pleasant enough to actually use every day. ...

There’s a boring step in the middle of this pipeline, and it’s the step that used to kill the whole thing. Photos land on the NAS from two phones. Before I can sort them, someone has to copy the new ones onto the working folder — the cutting board — while skipping everything already handled. That’s dull, repetitive, and easy to forget. For two years, “I’ll copy them over later” was where the process died. ...

This is the post the whole series turns on. Everything before it is the problem; everything after it is possible because of the idea here. For two years I couldn’t sort my daughter’s photos. Not because there were too many — because I was trying to do it in the wrong place: inside the backup folder itself. Why Sorting Inside a Backup Is a Trap My phone auto-backs up to a folder on my NAS. My wife’s phone backs up to another. Those folders are my only copies of my daughter’s baby years. Naturally, I wanted to open them and pick out her best moments. ...

My daughter was born in 2024. By the time she turned two, my wife and I had taken about 10,000 photos and videos of her. Every one of them was safely backed up to my home NAS. And every one of them was, in practice, lost. Not lost like deleted. Lost like a box in the attic you keep meaning to open. The files were there — I just could never find the ones I wanted, because they were mixed in with screenshots, receipts, memes, and every other photo two adults take in two years. “Backed up” had quietly become “buried.” ...