Journal

I updated the “Approach to Work and the Role of AI” section on the About page.

The section now reflects my understanding of the role of AI code generation in work on complex projects.

I dived into eBPF.

It is a Linux kernel technology: it lets you run your own code inside the kernel without rewriting the kernel itself and without building kernel modules. Before such code runs, it passes a verifier, so it cannot break the system by design.

For the Edge node this is a clear win in exactly the two places we need it: security and speed. Traffic observation and control, filtering and statistics all move from user space into the kernel, without extra copies and without extra processes.

In short: with eBPF you get a smart network coprocessor right inside the Linux kernel that takes on the grunt work — balancing priorities between MQTT and MoQ, cutting the CPU load from UDP packets, and giving you transparent diagnostics of QUIC traffic.

Right now I am working out which parts of this apply to our architecture, where eBPF genuinely pays off, and where a plain solution stays simpler and more predictable.

After expanding the “Five New Paradigms” section, I realized the article has become very large.

It is one of the most important articles on the portal, and it demands careful organization and structure. In the future it will need to be split into two articles and, quite possibly, restructured.

Added two endpoints for AI agents: GET /llms.txt and GET /llms-full.txt.

GET /llms.txt serves as the index, while GET /llms-full.txt provides the full content dump.

Additionally, I placed agents.md and .well-known/security.txt into the public directory alongside robots.txt. The agents.md file contains instructions for AI agents on how to navigate the portal, along with a general overview of its structure. The .well-known/security.txt (RFC 9116) file is for white-hat hackers, giving them a clear channel to report vulnerabilities)

I also optimized structured data (Schema.org in JSON-LD format) across the portal’s core pages.

I decided to create a Journal section on the portal.

It seemed better both for myself and for the reader: to keep a record of when and what changed across the articles and the portal.

I settled on three tags. Alongside “Portal development” and “Material updates”, a new tag appears — “Thoughts and insights”. It adds a personal dimension, showing the course of my thinking and what motivates the changes.

Expanded the “Five New Paradigms” section of the article “Edge Node Architecture: The Walking Skeleton and Operating in Chaos”.

It now covers five paradigms rather than the three covered before.