39 stars, my first open source contributor, and a message I keep re-reading

to fix a bug I didn't even know existed: SQLite paths on Windows were getting a leading slash prepended, turning C:/path/db into /C:/path/db. It was a real bug, properly diagnosed, cleanly fixed with a #[cfg(windows)] guard and a unit test that covers both platforms.

He found the bug. He traced it. He wrote the fix. He opened a pull request.

I'm 19 years old and someone just contributed to my project.

I merged it the same day.

The message that got me

Someone named per-oestergaard left this in the GitHub discussions:

"Hi. I read your article and just want to praise you for suggesting, and creating a solution for an important problem. I hope you manage to get it implemented. Unfortunately, I do not have any channels for supporting this."

That's it. That's the whole message. No technical feedback, no code, just a person who read about district clinics in Bhutan, thought the problem mattered, and took 30 seconds to say so.

I've been building ZamSync alone for weeks. The grind of writing tests, fixing edge cases at midnight, documenting things nobody might ever read, sometimes it's hard to remember why. That message reminded me. Someone out there thinks this problem is real and worth solving. That's enough to keep going.

What's new since the first article

I kept building. Here's what shipped:

Embedded status dashboard (Phase 20)

ZamSync now ships with a browser dashboard at /ui. No React, no build step, no CDN. Just a dark-themed HTML page served directly from the binary, showing live event counts, WAL size, uptime, and a real-time event stream via SSE.

The SSE reconnect logic was something I'm proud of: exponential backoff from 1s to 30s, Visibility API support so the tab stops hammering the server when you switch away, and dedup logic so reconnects never replay already-seen events.

Typed HTTP error codes (Phase 21)

The API now returns structured JSON errors with stable machine-readable codes:

{

  "error": "SCHEMA_VIOLATION",

  "message": "missing required field: patient_id"

}

Four codes: INVALID_JSON (400), SCHEMA_VIOLATION (422), WAL_UNAVAILABLE (503), INTERNAL_ERROR (500). The codes are additive and will never be renamed. Client code can safely switch on them.

Documentation site

ZamSync now has a real documentation site built with , it sounds small but it genuinely matters for visibility on lists like awesome-rust, which requires 50 stars. I'm at 39.

Thank you for reading. Thank you for the stars, the messages, and the pull requests. And thank you to whoever you are if you just took 30 seconds to say this problem matters. It does.

-- Mathéo Delbarre