diff --git a/content/blog/gps-ntp-pi.md b/content/blog/gps-ntp-pi.md
index 0459ab7..0697aa2 100644
--- a/content/blog/gps-ntp-pi.md
+++ b/content/blog/gps-ntp-pi.md
@@ -1,6 +1,7 @@
 +++
 title = "A stratum-1 NTP server on a Raspberry Pi with GPS and 1PPS"
 date = 2026-04-27
+draft = false
 +++
 
 Internet NTP is fine. Polling pool.ntp.org over a residential link gets you within a few milliseconds of UTC, which is enough to keep TLS certificates from looking like they're from the future and enough to make `tail -f` across two machines look mostly sensible. It is not enough to do anything interesting with timestamps. Below the millisecond floor, the network jitter eats everything: the kernel queueing the packet, the NIC waking up, the path through your ISP's gear, the upstream NTP server's own scheduling latency. You can stack more peers, you can pick lower-latency ones, you cannot make the network honest.