New

The etcd cluster is up and waiting for data. Here’s why copying everything over as-is didn’t work out — and how the migration turned into a full rethink of the data schemas.

First component: the management cluster on Kubernetes.

Architecture 2.0 is taking shape — time to build. First component: a Kubernetes management cluster. But before any logic or services, there’s one question that comes first: security.

How I got hacked, had my CI/CD taken down, and had tokens vacuumed across the entire core cluster — in fifteen minutes.

The fire is out — but the aftertaste remains. I reflect on hosting selection criteria: why I avoid European hosting, and why my choice is fourth-tier providers from third-world countries.

Five principles for building a detection-resistant network: from protocol selection and client configuration to rotation, layer isolation, and horizontal scaling.

The technical side of the project hasn’t been standing still — I structured the data, chose storage formats, and laid the groundwork for future automation.

I barely launched a Telegram channel before they started throttling Telegram. A story about news aging faster than I can write about it.

The taxonomy is a consequence. Behind it lies something more serious: the project’s content strategy.

No posts doesn’t mean no progress. The project hasn’t gone quiet — quite the opposite. More on that in the upcoming posts.