Milliseconds That Matter; Vilistextum; Freedium Reborn
$WORK scheduled a last-minute offsite in D.C., which means the past few days have been travel days with a pit stop to see the grandkids (hence, the lateness of this Bonus Drop).
We’ve got at least two AI-free, web-oriented resources today (the first one may be AI-free, but you never know these days), and I was excited to see Vilistextum is still usable nearly 20 years after work on it seemed to go quiet.
TL;DR
(This is an LLM/GPT-generated summary of today’s Drop. Ollama and ornith:35b.)
- Pressing enter on a web request triggers a cascade of events from DNS through TLS, kernel scheduling, and database queries, all visualized as a scrollable timeline where distance equals elapsed time (https://200ms.thenodebook.com/#act-0-prologue)
- Vilistextum is a specialized HTML-to-ASCII converter that handles malformed tag-soup HTML from the late 90s and early 2000s, converting to clean text optimized for e-ink reading (https://github.com/bhaak/vilistextum)
- Freedium Mirror bypasses Medium’s paywall by proxying articles through a clean reader interface, using a subscription-sharing model after the original GraphQL approach was closed by Medium (https://freedium-mirror.cfd/)
Milliseconds That Matter

This is one of the best “this is what happens when you visit a web page” ’splainers I’ve seen in a while.
You press enter and ~200 milliseconds later, pixels appear on screen. Every single event that happens between those two events is the whole web stack, rendered as a scrollable timeline where time only moves when you scroll (and, it’s not the smoothest scrollytelling — on purpose — so try to be a bit forgiving).
The site’s conceit is fairly elegant: scroll distance equals elapsed time. If you stop scrolling, the request freezes in mid-flight. The overarching visualization traces a single HTTP request from a coffee shop click through DNS lookup, TCP handshake, TLS negotiation, the Linux kernel, Node’s event loop, a Postgres query, and back to the browser. Each layer gets its own “act” in the narrative, annotated with actual mechanisms – the exact byte sequence of a SYN-ACK, the kernel scheduling the network softirq, libuv picking up the async callback and handing it to V8, the Postgres parser planning a query.
This comes from the team behind The Node Book, and the framing forces you to absorb just how much machinery fires up every time a web page loads (which is a genuinely bonkers amount).
Vilistextum

Patric Mueller’s HTML-to-ASCII converter hit version 2.6.9 waaaay back in October 2006 and mostly stopped – which is fine! because the problem it solves hasn’t changed. The web is still full of malformed, tag-soup HTML that makes most converters choke or produce garbage. Vilistextum was built specifically for these broken bits.
It handles HTML 3.2 through 4.01 and XHTML 1.0, converts windows-1252 characters to their ISO-8859-1 equivalents, turns links into footnotes, collapses blank lines, and optimizes output for e-ink reading. Multibyte encoding support comes via libiconv.
It compiles from source with the ancient-but-dirable autotools, has a kaptain GUI frontend that carbon dates it precisely to 2006, and sits quietly on (alas) GitHub with a few hundred commits on a master branch that hasn’t moved in years.
Let me re-state that this tool still works, and works pretty darned well. If you’re processing HTML at the command line and lynx -dump feels too heavy or w3m too opinionated, Vilistextum is a good addition to the toolbox.
For the AI vegans out there, no AI has touched this repo and none likely ever will.
Freedium Reborn

Medium was and is a terrible concept, and their loginwall/paywall is quite porous. I thought Freedium-proper had died an untimely death a bit ago, but the Freedium Mirror is the latest in a long line of tools that make these walls utterly disappear.
The service proxies Medium articles through its own reader: paste a walled URL into the box, or prepend https://freedium-mirror.cfd/ to any medium.com link, and you get a clean, ad-free rendering of the full piece. The project spun up in mid-2023 when Medium changed its paywall method and broke every existing bypass.
The OG approach reverse-engineered Medium’s GraphQL API; Medium closed that hole. Now Freedium’s maintainers pay for subscriptions and share access through the service – which the README explains plainly, including what changed when the GraphQL loophole closed.
It’s unlocked over 540,000 articles. The frontend and backend are both open source, hosted on GitHub and Codeberg. There are browser extensions that auto-redirect Medium URLs, and an Android app if that’s your setup. If the paywall nags you more than a couple times a week, this is the simplest fix going.
FIN
Remember, you can follow and interact with the full text of The Daily Drop’s free posts on:
- 🐘 Mastodon via
@dailydrop.hrbrmstr.dev@dailydrop.hrbrmstr.dev - 🦋 Bluesky via
https://bsky.app/profile/dailydrop.hrbrmstr.dev.web.brid.gy
☮️
Leave a Reply