Project Diary

A short busy week with no time for the project, support still silent, the network on pause — and some thoughts about eggs, baskets, and diversification.

Unexpected trouble with hosting after migration: servers in Japan suspended without explanation.

The blog turns one month old — a good time to look back and admit it: I got a bit carried away with project chronicles. Time to switch gears.

Yesterday I launched the subscription microservice and wrote ‘deployed itself, without a single manual action.’ This morning users couldn’t connect. Not a single one.

Ten days ago I wrote ’the scheme is ready, all that’s left is to implement it.’ Today the subscription microservice is live.

The support system I’d been dreaming of since February is finally built — in a single evening. Tickets, bot-mediated dialogue, handoffs between admins, and broadcasts.

Today was a cleanup day. No new features, no forward movement on the map. But now several things work the way they were supposed to from the start.

A microservice task — and a long-overdue reason to finally try Go in practice. Especially since our project is already soaked in it.

Our financial operator announced an account freeze — so I decided to honestly calculate what the project actually costs. Spoiler: cheaper than it seems.

The /trial command is up and running: a guest gets a link, a QR code, and an hour of open internet. Here’s how it works under the hood.