TSA does not have a sense of humour. neither do i, anymore. this is the placeholder body — the real post lives in content/blog/2025-01-15_we-have-to-call-the-police-flying-with-flipper-zero.md and will render via @nuxt/content once that integration ships.
the setup
here's the thesis. i had a problem, i refused to leave the house, and i had a half-charged thinkpad. you can guess what happened next.
i'd been running this exact stack for about six months — nuxt 4, cloudflare workers, @nuxt/content, tailwind, daisyui — and the thing that finally broke me was the build pipeline. specifically, the part where it lies about whether content has changed.
> wrangler deploy
✘ [ERROR] you tried something
the worker is fine. you are not.
i lost the file. i'm not sorry.what changed
the fix, as is tradition, was three lines of yaml. but the journey there involved prometheus, grafana, a misconfigured tailnet, two pots of coffee, and a brief out-of-body experience.
"the kernel panics, but romantically."
that's an error message i would die for. instead i get "something went wrong, our team has been notified." nothing went wrong. somebody wrote a bad query and capitalism happened. say so.
what to do
- build a personal site. make it weird.
- don't put your linkedin on it.
- don't optimize for the algorithm.
- write your own 404. swear, occasionally.
- link to a friend.
that's it. that's the post. there's no call to action. there's no "if you liked this, consider subscribing." you got here. you read it. that's the contract. thanks.