Pass Muster Media My Social Feed

The Tech

Part 4. Being a good guest

Deciding when to look is half the job. The other half is keeping every look gentle.

3 min read

This is the last part of Fresh when it matters. The first three decided when to look. These guardrails make sure looking stays polite.

What a bad day looks like

Say Substack starts answering 429 to the live-show reads. The run that sees it stops reading Substack feeds, and writes a 10 minute pause into the database. The next run, and any other copy of the function, reads that pause before it makes a single Substack request, and skips the reads while it lasts. Meanwhile pages keep working. Posts and shows already stored are served as they were, so a reader sees slightly older data instead of an error.

When the pause ends, the normal order resumes. Open pages go first, then whoever is overdue. There is no pile-up of retries to make things worse, because we never queued any.

The rule behind all of it is that a platform telling us to slow down is information. We would rather be a few minutes behind for a while than argue with it.

Did we invent this? No, and that's the point

Every piece has a long history. Many web apps pause background tabs when nobody is looking. Feed readers check popular feeds more often than quiet ones. Search engines visit busy sites more often and slow down when a server pushes back. HTTP caching has had "serve it if it's fresh enough" for decades.

We are not claiming a new trick. What we like is the fit. Reader attention drives server effort, and learned habits fill the gaps when nobody is looking. The result: live shows appear within minutes, and the whole thing runs on small pieces. If you want the money side of that, see What it costs to run.

If you're building anything that reads someone else's data, here's our takeaway: let attention set the schedule. Check hard where people are looking, gently everywhere else, and keep a memory so you know when to look again.

← All posts