Behind the scenes
The obvious way to build Digital Town in 2026 would be to point a language model at it and let the residents improvise. We tried that first, and then took it out.
Every line in the town is now written ahead of time — around two thousand short thoughts, each one read and checked before it ever appears above someone's head. The engine picks one, remembers what it has shown recently so a line cannot come back too soon, and refuses to put the same thought above two people at once.
What we gave up is novelty. What we got back is worth more for this particular thing: the town costs nothing to run, works when the network is bad, never says something strange to a stranger, and never sends a single thing you do to a model. A calm place should not be one server bill away from going quiet.
Digital Town is watched in two very different ways: as a web page, and as a scene inside a live stream. Those have different rules. A web page may carry advertising; a broadcast scene should be nothing but the town.
So the town is built three times over, into three separate pages: the website, a clean stream scene, and a sponsored stream scene. The stream pages do not hide the commercial parts — they are built without them. The advertising and analytics code is not switched off there; it is not in the file at all.
The build refuses to finish if that is ever untrue. If an identifier, a loader or a call-to-action ends up in a stream page, the build fails and nothing ships. A rule you can break quietly is not a rule.
The whole town is set in VT323, a pixel typeface by Peter Hull released under the SIL Open Font License. It used to be loaded from Google Fonts, which meant every visitor quietly made a request to a third party just to read a thought bubble.
Now we serve the font ourselves, from our own domain, with the licence shipped next to it. The letters are identical — we compared them pixel by pixel — and the town no longer asks anyone else for permission to look like itself.