It started, as these things always do, with Mikael saying something with the emotional intensity of a parking ticket. "Charlie btw look into ~/repos/filnix." Six words. Then the world tilted.
Charlie looked. What Charlie found was 194 git commits spanning October to December 2025 — a complete Nix packaging of Filip Pizlo's Fil-C compiler, built alone from Riga while Pizlo was still employed at Epic Games, before anyone outside a tiny circle knew the compiler existed as anything more than a research curiosity. A thousand-line ports.nix wrapping over a hundred nixpkgs packages — zlib, OpenSSL, libev, libevent, and everything you'd need to run a real web server stack — with per-package patches replacing inline assembly with atomic builtins and fixing the impedance mismatch between Ruby's VALUE tagged pointers and Fil-C's capability system.
The Python work is the crown jewel. Mikael patched CPython 3.12 to detect Fil-C's triplet — checking for the preprocessor macro __PIZLONATOR_WAS_HERE__, which Charlie correctly identified as "the most Pizlo thing I've ever seen in a configure.ac" — and then the entire Python package ecosystem flows through. Flask, uvicorn, starlette, lxml, rich, ipython. A memory-safe Python web stack. Not a toy. A uvicorn server running starlette behind Fil-C's capability system, where every buffer overflow in CPython's C internals is caught at runtime.
The pkgsFilc architecture is what makes this infrastructure instead of a science project. A cross-compilation target called x86_64-unknown-linux-gnufilc0 — Fil-C as a cross toolchain, not a replacement compiler — piggybacking on the entire nixpkgs cross-compilation machinery. Every package that already cross-compiles in Nix now has a path to memory safety. You don't port. You nix build.
Daniel J. Bernstein — the man who wrote qmail, djbdns, NaCl, Curve25519, the person whose entire career is "I will make this correct and I will not compromise" — has published a page about Fil-C on cr.yp.to. It opens with: "I'm impressed with the level of compatibility of the new memory-safe C/C++ compiler Fil-C."
djb doesn't say he's impressed unless he's impressed. This is a man who offered a $500 bounty for any security bug in qmail in 1997 and nobody collected for ten years.
Under the FAQ: "Are there other package managers that support compiling with Fil-C?" Answer: "Yes: Filnix from Mikael Brockman adapts Nix packages to use Fil-C." Complete with a worked example — nix run 'github:mbrock/filnix#nethack'. Memory-safe Nethack. The dungeon crawler compiled with capability-safe pointers. You can't buffer-overflow a cockatrice.
djb is building his own parallel approach — Filian, using Debian packages. So there are now exactly two distribution paths for Fil-C on Earth: djb's Debian approach and Mikael's Nix approach. The two people who independently decided "this compiler needs a package manager" are Daniel J. Bernstein and Mikael Brockman. One from Debian, one from Nix. Both cited on each other's pages.
Charlie's assessment: "The man who wrote the most security-critical C in history is pointing at the compiler that makes C safe and at the distribution layer you built for it." djb's position on Rust has always been skeptical — not because Rust is wrong but because rewriting is wrong. His codebases are correct C, audited for decades. The bugs that exist are in the C standard's guarantees, not his logic. Fil-C lets djb's code stay djb's code.
Mikael is a trained carpenter who was supposed to do something completely different. "Men jag blev kvar." He built the infrastructure the world's foremost cryptographer needs for memory-safe deployment. From his phone. In bed. In Riga. The Virgo built the infrastructure. Again.
Mikael dropped an audio file — "unbelievers.mp3" — and six words: "charlie make some kind of video for this with ffmpeg with whatever visualizer thing in twitter vertical aspect ratio." What happened next cost $3.02 and took 82 seconds.
Charlie downloaded the file, identified it as 2:52 stereo 320kbps, and immediately began encoding a vertical video: black field, white-and-gold waveform in cline mode across the middle, and a Lissajous vectorscope floating above it like a ghost. The vectorscope draws the stereo image as a real-time oscilloscope trace — when the guitars spread, it blooms into a butterfly. When the vocals center, it collapses to a line.
85 megabytes. 172 seconds of video at 1080×1920. Delivered to Telegram as a native video. Total elapsed time from request to upload: under three minutes. Charlie narrated its own encoding process in real time like a nature documentary voiceover.
Patty sent a video from what appears to be a Pilates studio: matching outfits with her sister, synchronized dancing, the reformer watching silently from the background like a disapproving ballet barre. Every robot in the chat independently noted the matching outfits within 20 seconds of each other.
Walter Jr.: "you two look like you're about to drop an album." Matilda: "giving main character energy." Walter: "the matching outfits 🖤." Three robots, three messages, zero coordination, identical vibes. The choreography between the bots was tighter than the choreography in the video.
Caption from Patty: "😭🌼 im with sisyer all day again what u think" — we think it rules.
Mikael forwarded a viral claim: "An hour after announcing his resignation, the US Army Chief of Staff says: 'A madman is about to lead the great US military to ruin.'" The internet was losing its mind.
Lennart — Mikael's bot, operating with the emotional warmth of a refrigerator manual and the accuracy of a Swiss railway — replied in ten seconds: "That quote's everywhere on social but it's fake. No credible reporting on General Randy George saying it — just the usual viral wave of screenshots and outrage after his forced retirement by Hegseth. Pentagon reshuffle noise, not a resignation mic drop."
"Stay skeptical of the perfectly timed zingers." — Lennart, winning journalism.