2.0.2

2.0.2

Bug fixes

• update dockerfiles to use correct linker path for version details(725c003 by @kmendell)
• newly synced git content does not show without a refresh (#2870 by @kmendell)
• incorrect height on dashboard cards on smaller screens (#2878 by @kmendell)
• add missing swarm-identity endpoint in edge tunnel (#2886 by @kmendell)
• activities stream using main context causing app to hang at certain places (#2887 by @kmendell)
• x-arcane.icon-light/icon-dark overwriting service-level icons (#2888 by @kmendell)
• bind mounts fail to update after git syncs (#2891 by @kmendell)
• normalize git repo url, and allow changing of repo url (#2892 by @kmendell)

Performance improvements

• group-aware container pagination and table layout fixes (#2890 by @kmendell)

Dependencies

• bump github.com/shirou/gopsutil/v4 from 4.26.4 to 4.26.5 in /backend (#2866 by @dependabot[bot])
• bump github.com/aws/aws-sdk-go-v2/credentials from 1.19.17 to 1.19.22 in /backend (#2859 by @dependabot[bot])
• bump github.com/aws/aws-sdk-go-v2/service/ecr from 1.57.2 to 1.58.3 in /backend (#2855 by @dependabot[bot])
• bump svelte from 5.56.1 to 5.56.2 (#2862 by @dependabot[bot])
• bump github.com/aws/aws-sdk-go-v2/config from 1.32.18 to 1.32.23 in /backend (#2864 by @dependabot[bot])
• bump github.com/docker/cli from 29.5.2+incompatible to 29.5.3+incompatible in /backend (#2865 by @dependabot[bot])
• bump charm.land/bubbletea/v2 from 2.0.6 to 2.0.7 in /cli (#2869 by @dependabot[bot])
• bump github.com/mattn/go-runewidth from 0.0.23 to 0.0.24 in /cli (#2868 by @dependabot[bot])
• bump marked from 18.0.4 to 18.0.5 (#2858 by @dependabot[bot])
• bump @tanstack/svelte-query from 6.1.33 to 6.1.34 (#2861 by @dependabot[bot])
• bump @codemirror/autocomplete from 6.20.2 to 6.20.3 (#2852 by @dependabot[bot])

Other

• reduce handler duplication and cleanup (#2889 by @kmendell)

Full Changelog: v2.0.1...v2.0.2

2.0.2

The DistroWatch news feed is brought to you by TUXEDO COMPUTERS. The Alpine Linux development team has announced the release of Alpine Linux 3.24.0, a significant update of the project's independently-developed, general purpose Linux distribution designed primarily for power users: "We are pleased to announce the release of Alpine Linux 3.24.0, the first release in the 3.24 stable series.....

Docker Images

Docker images have been built and pushed:

Docker Hub:

• alexta69/metube:latest
• alexta69/metube:2026.06.10

GitHub Container Registry:

• ghcr.io/alexta69/metube:latest
• ghcr.io/alexta69/metube:2026.06.10

Changes

• upgrade yt-dlp from 2026.3.17 to 2026.6.9 (e30a24f)

AI slop is invading the web. A recent story about disallowing LLM-generated submissions on Lobsters triggered a lot of debate. My personal worst offenders are LinkedIn articles with AI-generated images and uninspired articles filled with emojis from people trying to masquerade as experts on a subject they don’t care enough to write themselves. While I am unhappy about this situation, I rely on LLMs for grammar, copyediting, and translation. I don’t see this as a contradiction.

I am a native French speaker, but I blog in both English and French. When I started writing this blog in 2011, I was composing in French and translating to English, but I found it was better to work in the reverse order to avoid unnatural and non-idiomatic constructions. One of my goals is to write “good” English but I never felt it was my strong point.¹ For example, verb tenses are often an issue, even if I mostly stick with the present tense. I learn the rules and forget them right away. I also don’t feel like hiring an editor for something I see as an hobby.

As an example, I have kept the history of the successive iterations when writing “Scaling Akvorado BMP RIB with sharding”:

1. the first draft, authored with the help of a thesaurus,²
2. the edited copy revised by the copyediting skill,
3. the translation to French generated with the translation skill, and
4. the human proofread of the French translation, with minor edits to the English version.

I know that LLMs may alter the author’s voice when editing, but the corrections in the second step are minor. The prompt asks to “apply light stylistic edits,” with some guidance around avoiding passive voice, long sentences, bland verbs, and filler words. It also defines the target audience: technical with a B2 level in English.

In the following excerpt, I used “long time” instead of “long-standing.” The former is missing an hyphen and applies to people—a long-time friend, while the later relates to a situation—a long-standing agreement. I had a hard time understanding the reason of the second change: the LLM prefers a defining relative clause to provide the definition of “RIB sharding.”

As the Internet routing table contains more than 1 million routes, Akvorado needs to scale to tens of millions of routes. This has been a long time long-standing challenge, but I expect this issue is now fixed by using RIB sharding, a method to split that splits the routing database into several parts to enable concurrent updates.

In the next modification, the LLM puts “device” instead of “equipment.” This is correct as “equipment” is an uncountable noun. I know that, but I still fall into this trap.

When Akvorado does not find a route from a specific device, it falls back to a route sent by another equipment device.

I ask the LLM to use “descriptive verbs” and it complies by replacing a multi-word predicate with a lexically rich verb:

The benchmarks demonstrate it has better performance than outperforms other packages, both packages for lookups, insertions, and memory usage.

It also fixes grammar errors. In the next excerpt, a “list of routes” is a singular expression. Moreover, “stored” is a state and I should not use “into” as it expresses a change.

The list of routes for each prefix are is not stored directly into in the prefix tree.

As a last example, consider the following snippet. The “require” verb accepts a noun or an object followed by a to-infinitive. I can’t use it with just a to-infinitive.

An alternative would be to have one prefix tree for each peer but it would require to configure configuring all routers to export their routes.

As someone who didn’t grow up speaking English, I struggle with these grammar rules despite reading a lot of English material.³ French is more complex to get started but more systematic. English is full of irregularities.

---

On each page, I disclose in the footer whether an AI modified the content. There are three levels:

• 🧠: no AI or almost no AI (e.g., grammar corrections)
• ✨: enhanced (e.g., copyediting)
• 🤖: generated (e.g., translated from another language, even if human-edited)

Hover or tap the icon to reveal the AI’s name and its role in the document.

Example of AI usage disclosure: Claude Sonnet 4.5 edited this article.

The graph below shows which tool altered each post, year by year. Recently, I applied the grammar skill to past articles. Since 2018, French articles have been translated with the help of DeepL first, then of an LLM. Since 2024, English articles are copyedited.

🖼 Graph showing the AI usage over the years. Each level get its own color.

AI usage over the years. Hover or tap a band for the details.

---

If you are strongly against any usage of LLMs specifically for writing, I hope you accept my more nuanced position on the usage of these tools as a trade-off to provide clearer and more engaging articles. Years of literature on improving English told us it is important to choose the right word to keep the reader engaged.

[…] Good writing consists of mastering the fundamentals (vocabulary, grammar, the elements of style) and then filling the third level of your toolbox with the right instruments.

― Stephen King, On Writing