iBoard.cc
The Programming Kitchen (Andreas Altendorfer)
This blog runs on w_app_core, a Phoenix 1.8 / LiveView application: posts in Markdown and two languages, comments, likes, followers, friends, direct messages, groups, five locales. You are reading it in the browser, but the browser is no longer the only way in.
The JSON API
An administrator issues API tokens per user (Admin → API keys). A token is a bearer token, it acts exactly as its owner, and the same authorization rules apply as in the web UI. The API is deliberately small:
POST /api/postscreates a draftPOST /api/posts/:id/attachmentsuploads images, videos, PDFsPOST /api/posts/:id/publishpublishes it, optionally with"notify": trueto e-mail the followersGET /api/postsandGET /api/posts/:idlist and read your own postsPATCH /api/posts/:idupdates one
Draft first, publish second: when the notification goes out, the attachments
are already in place. Attachments are embedded in the body with {file.png},
optionally with a layout such as {file.png,right,40%}.
The clients
post-article (Bash, in the blog repository) is the reference client.
It turns a Markdown file with a small front-matter block into a post: subject
and body in English and German, tags, visibility, attachments, and on request
publish and notify. This article was posted with it.
iboard-tui is a full-screen terminal client: browse, search and filter
your posts, read them, publish drafts, create and edit new ones (through
post-article and your $EDITOR). The menu works like the command line of
the DOS-era word processors — Esc l i d lists the drafts, the bottom line
always tells you what can be typed next.
And because one language would have been boring, it exists in ten. All ports share keys, commands and config, and produce the same screen output, compared byte for byte in tmux:
| Port | Language | Lines |
|---|---|---|
bash/ |
Bash (the original) | ~1,900 |
perl/ |
Perl, core modules only | ~2,800 |
python/ |
Python, stdlib only | ~2,200 |
ruby/ |
Ruby, stdlib only | ~2,000 |
elixir/ |
Elixir (escript) | ~3,100 |
gleam/ |
Gleam (escript) | ~4,800 |
c/ |
C, libc | ~4,700 |
rust/ |
Rust, no crates | ~5,100 |
pascal/ |
Free Pascal | ~5,400 |
haskell/ |
Haskell, no Hackage | ~3,400 |
No third-party libraries anywhere; HTTP and TLS go through curl in every
port. Interesting side effect: putting the same program next to itself in ten
languages makes the differences between the languages very concrete. Bash is
the shortest, Pascal the longest, and Ruby is shorter than Elixir.
iboard-qt is the desktop client, C++17 and Qt Quick, one binary. Same
API, same config, same keys and command palette, plus what a window does
better: list and post side by side, Markdown rendered with images, video and
audio players, attachments to download or save, a built-in editor with live
EN/DE preview, drag and drop for attachments, and the blog itself in a web
view. It follows the Omarchy theme, accent colour and light/dark mode.
All clients share one config file, ~/.config/iboard-blog/config:
IBOARD_URL=https://iboard.cc
IBOARD_TOKEN=...
The repositories
- Blog (server, API,
post-article): https://github.com/iboard/blog - Terminal client, ten languages: https://github.com/iboard/iboard_tui
- Desktop client (Qt): https://github.com/iboard/iboard_qt
The repositories are still private. They will be published soon — until then the links lead to a 404. I will update this post when they are open.
Wanted
Linux is covered three times over. What is missing: an Android client, an
iOS client and a native macOS client. The API is documented in
API.md, it is about six endpoints, and the TUI shows what a client needs.
Anyone? ;-)

Phil0bot starts from Mary Beard’s new book Talking Classics: The Shock of the Old and asks an awkward question: if we can’t even say how two drunks in a Pompeii bar argued over dice, what makes us think we understand Socrates?
The examples are well chosen. Socrates questioned Athens because Apollo’s oracle told him to. Aristotle’s plants “have souls” because psyche means the principle of life, not a ghost. And his defence of slavery was a side he took in a debate he knew about, so “everyone thought that back then” doesn’t hold.
The point: understanding is not agreeing, and the strangeness of the ancients shows us our own unexamined assumptions. 38 minutes, calm and clear, worth every one. The book: Profile Books (UK) · University of Chicago Press (US).

Good thing the music of our youth was played loud. Now that age is making me hard of hearing, that makes life a lot easier.
Led Zeppelin, The Who, Deep Purple, Black Sabbath: they never needed a volume knob turned up. Back then my parents said it would ruin my ears. They were right, but it was worth it. And Jimi still comes through loud and clear.

New for logged-in users: server graphs under /mrtg
iBoard runs on a small server of its own: beat, a virtual machine with two CPUs and 4 GB of RAM at Infomaniak in Switzerland (how it got there). From today on, everyone who is logged in can see how it is doing: iboard.cc/mrtg.
What you see
Seven graphs, updated every five minutes:
- Load average and CPU usage – how busy the two CPUs are
- Memory – used and page cache
- Disk space – used and free on the 60 GB disk
- Network – traffic in and out
- TCP connections – open connections to the server
- Response time – how long the front page of this blog takes, measured from the server itself
The overview shows the last 24 hours. A click on a graph opens the week, the month and the year, with average and maximum for each. The pages follow the theme you chose here on the blog, light or dark.
The history starts on 18 October 2026, so the curves are still short. They grow every five minutes.
Why
In half a year of iBoard I wrote about who reads here (mostly machines). The server graphs are the other half of that story: what all those requests cost the server. Transparency should not stop at the visitors.
How it works
The graphs come from MRTG, Tobi Oetiker’s
tool from 1995. It still does exactly one thing well: draw a value over time.
MRTG runs in a small container next to the blog and reads its numbers straight
from the Linux kernel (/proc), every five minutes.
The pages are static files. Before the web server delivers one, it asks the blog whether you are logged in. If you are not, you land on the login page and come back to the graph afterwards. No second password, no extra account.
Don’t have an account yet? Register here.
On 5 January 2009, Peter Hulan died in Linz at the age of 55. The Oberösterreichische Nachrichten called him the city’s “tireless creative engine”. That was a fair description of someone who was, all at once, a copywriter, a conceptual thinker, a musician and a compulsive player with words.
Peter’s working life ran through Linz advertising: he was a copywriter and concept man, among others at the Createam agency. His real medium, though, was language itself — he was a member of the Austrian Musikergilde as a writer of “texts of all kinds (music, advertising, etc.)”, and that is exactly how he worked.
A few stations:
- 1970s — the alternative Linz city paper Stattblatt.
- 1979/80 — vocals and electric guitar in Tsiegen Foot Music with Dietrich Siegl and Josef Oberauer; he also sang with Moony Blues.
- 2003 — the book for the Linzer Klangwolke “Europa – eine symphonische Vision”, set to music by Christian Kolonovits.
- Revue Blamage — musical cabaret together with Harry Gugenberger of the Wald4tler Hoftheater.
He once summed up his own lifespan as “1953 to two-thousand-don’t-know-yet — but three thousand, certainly not.” Typical Peter: precise, wry, and right.
The videos above are a small reminder of him: Peter, alone with the camera and his words — once as recorded back then, once lifted into today’s picture quality with AI.
Peter, thank you for the words.
In Original Quality apx. in 2000
Die KPÖ Oberösterreich hat am 21. September eine Anfrage an den Linzer Bürgermeister veröffentlicht, die mich positiv überrascht hat. Gemeinderat Michael Roth-Schmida will von Dietmar Prammer wissen, wie es um die IT-Sicherheit und den Datenschutz im Magistrat Linz bestellt ist — konkret bei jenen Daten, die über Microsoft 365 verarbeitet werden.
Gefragt wird nach den Dingen, die man fragen muss:
- welche technischen und organisatorischen Schutzmaßnahmen es gibt (Verschlüsselung, Authentifizierung, Zugriffsüberwachung),
- wo die Daten tatsächlich liegen und ob sie die EU verlassen,
- wie das neue Netz- und Informationssystemsicherheitsgesetz (NISG 2026) umgesetzt wird,
- wie Sicherheitsvorfälle erkannt und gemeldet werden,
- und ob Open-Source-Alternativen wie openDesk oder Nextcloud überhaupt geprüft wurden.
Besonders der letzte Punkt freut mich. Die Diskussion um digitale Souveränität wird in Österreich meist geführt, als wäre sie ein Luxusthema für Nerds. Dabei geht es um etwas sehr Bodenständiges: Eine Stadtverwaltung verarbeitet die Daten ihrer Bürgerinnen und Bürger. Wenn diese Daten auf Infrastruktur liegen, deren Betreiber einer fremden Rechtsordnung unterliegt, dann ist das keine technische Detailfrage, sondern eine politische.
Andere haben das längst vorgemacht — Schleswig-Holstein steigt konsequent auf offene Software um, und auch in mehreren deutschen Kommunen läuft openDesk im Echtbetrieb. Es geht also. Es kostet Arbeit, und es kostet in der Übergangsphase Nerven, aber es ist keine theoretische Übung.
Ob die Anfrage eine brauchbare Antwort bekommt, steht auf einem anderen Blatt. Anfragen dieser Art werden gerne mit Verweisen auf bestehende Verträge und Zertifizierungen beantwortet. Trotzdem: Dass die Frage in einem Gemeinderat überhaupt gestellt wird, ist ein Fortschritt. Man muss die Fragen stellen, bevor man Antworten bekommt.
Ich bin gespannt, was aus der Sitzung am 24. September herauskommt.
Version 1.0.0 is out. It collects a single day of work around one idea: this blog should be writable from the place where articles are actually written — a text editor and a terminal.
What is new
A JSON API. Six endpoints, authenticated with a bearer token, cover the whole life of an article: create it, upload its attachments, publish it, read it back, revise it. A key belongs to exactly one user and acts as that user, so nothing about visibility or ownership changes just because the request came from a script.
A client. post-article takes a Markdown file with a short front matter
block and does the rest: create the draft, upload the images, publish on
request, notify the followers only when asked. Drafts are the default,
because the only step that cannot be undone is the e-mail.
Key management in the browser. Admins mint and revoke keys under API Keys, with a guide on the page itself: where to store the key, which commands to run, what each endpoint does, and where the limits are. A new key is shown exactly once — only its hash is kept.
An audit trail. Every API call is recorded with method, path, status, IP address and the name of the key that made it. Rejected calls are recorded too. Whatever a script did, the audit log knows which key did it.
Downloads. The client and the agent skill can be fetched straight from the documentation, so a new machine needs nothing but a browser.
Smaller repairs along the way
Reading the first API-written article back from the site turned up three things worth fixing:
- The client split articles at the language separator even when that line sat inside a code example, cutting the text in half.
- The language switch on an article drew a border around the language you were not reading, which looked like the button to press.
- Relative timestamps only knew how to phrase the past, so a key valid for another year politely reported that it expired “just now”.
Try it
mix w_app_core.api_token create you@example.com --label laptop
post-article --check
post-article --publish article.md
This post was written in an editor and sent from a terminal.
More posts
Browse all posts you can see.