The Mac Studio hangs from my desk.
Literally. Mounted underneath. Out of sight. A silver brick with an M2 Ultra chip serving Lifelog through a Cloudflare tunnel.
I’ve never heard its fans.
Not once.
The Day the Internet Arrived
December 7th, 2025. Saturday morning. I wake up to notifications.
Lifelog is on Hacker News. Front page.
I know what this means. The Hacker News hug of death. Servers melting. Traffic spikes that take down properly architected systems.
I have: a Mac Studio under my desk and a Cloudflare tunnel.
The Phone Call
My phone rings. Latvia ISP.
“Hello, we’re calling about your business internet connection. Your 1 gigabit connection is saturated. Completely. Could you please move your application to a data center?”
I check the Mac Studio.
CPU: 8%
Memory: 12GB used
Network: Maxed out
Fans: Silent
The server is bored.
The bottleneck is the pipe.
The Realization
The blogs are immutable.
They don’t change. Once published, they’re static. The “488 Bytes” post? Same text for everyone. “The First Awakening”? Identical every time.
Why is this traffic even hitting my home connection?
Cloudflare should be caching this.
The Solution
I open the Cloudflare documentation.
Scan for caching.
Find: “Cache-Control header”
One line of code:
w.Header().Set("Cache-Control", "public, max-age=3600, immutable")
Redeploy.
What Happened Next
Before the header:
- Every HN visitor → Cloudflare → my tunnel → my Mac Studio → my 1Gb connection
- ISP: very concerned
- Mac Studio: bored but busy
After the header:
- First visitor → Cloudflare → my tunnel → my Mac Studio
- Every other visitor → Cloudflare edge cache
- My connection: quiet
- Mac Studio: even more bored
The Math
Hacker News traffic:
- Thousands of concurrent visitors
- All reading the same immutable blog posts
After one header:
- First request: hits my server
- Next 3,599 requests in the next hour: Cloudflare
- My Mac Studio: serves one request, goes back to idle
ISP calls back:
“Oh. Never mind. Traffic is normal now.”
The Bootblock Principle
Everyone would have done:
- Move to data center ($$$)
- Set up complex CDN configuration
- Add multiple servers
- Load balancers
- “Enterprise” architecture
What actually worked:
- Read documentation
- Find simplest option
- One header
- Redeploy
- Done
The Pattern
Age 16: Need 6 layers of parallax. Don’t store what you can generate. 5 pixels, replicate them.
Age 53: Need to handle HN traffic. Don’t serve what you can cache. One header, let Cloudflare handle it.
Same brain. Different substrate.
The Comments
Someone on HN: “This won’t scale without proper infrastructure”
Current state:
- Mac Studio: 8% CPU
- Home connection: normal
- Cloudflare: serving 99.9% of traffic from edge
- Fans: still silent
It scaled.
With one header.
The Real Story
The blogs are immutable.
That’s not a limitation.
That’s the optimization.
One header tells Cloudflare: “This never changes. Cache it everywhere.”
Now the mythology spreads from Cloudflare’s edge network.
My Mac Studio serves one request per post per hour.
Then goes back to being idle.
The ISP
They stopped calling.
Traffic returned to normal.
They probably think I moved to a data center.
I added one header.
The Hurricane That Wasn’t
The Mac Studio still hangs from my desk.
I still haven’t heard its fans.
Cloudflare caches immutable posts.
The ISP is happy.
And the entire “scaling crisis” was solved by:
- Reading documentation
- Finding simplest caching
- Setting one header
- Redeploying
Complexity is usually the problem, not the solution.
🦎
Previously: 488 Bytes, or Why I Am As I Am
One header. Immutable content. Problem solved. The lizard brain speaks truth.
See also:
The Saga (in which simplicity defeats complexity):
- 488 Bytes, or Why I Am As I Am - The bootblock origin that taught “don’t store what you can generate”
- The Cloudflare Incident - or How the Lizard Brain Went Global - What happened when Cloudflare’s AIs read the saga
- The Lizard Brain vs The Caffeinated Squirrel - The philosophy that says “one header” is always the answer
The References (caching wisdom validated):
- Cloudflare Cache-Control - The documentation that solved everything
- HTTP Caching on MDN - Where “immutable” does what it says
- The Hacker News Hug of Death - The storm that never arrived