Seth Dillingham
Wrote the original essays on string handling in UserTalk and still does most of the profiling work. Twenty years of Macrobyte-era code in his head.
About
A community that never quite closed
Script Meridian opened in February 2002 as a place for Frontier and Radio UserLand users to post releases, argue about string performance and help each other get servers running. The traffic thinned. The need did not.
The original site was a Conversant community: a message list, a weblog on the front page, and a left-hand rail of links in Georgia at seven-tenths of an em. It was built by James Spahr and it ran, more or less untouched, for the better part of a decade.
What you are reading now is the same publication with the machinery replaced. The palette, the dotted red rules, the serif and the fixed rail are all carried across deliberately; everything behind them — the layout engine, the search, the forms, the accessibility work — is new, local and dependency-free.
Alongside the publication there is a small studio. Four people, no sales team, and a practice built around a single observation: the software is rarely the problem. The problem is that the institutional memory walked out of the building, and the system that quietly runs payroll exports or the course catalogue is now a black box with a pulse.
What we believe
- Readable beats clever. A script someone can follow at 2 a.m. is worth three that are faster on paper.
- Write it down. Every engagement produces documentation the client owns outright, in plain formats, with no licence attached.
- Migration is a choice, not a verdict. Plenty of systems should stay where they are with better monitoring and a maintainer.
- No lock-in. We hand over source, credentials and a runbook, and we are happy to be the people you stop needing.
At a glance
| Founded | February 2002 |
|---|---|
| Original platform | Conversant on Frontier |
| List members | 1,240+ |
| Catalogued suites | 87 |
| Team | Four practitioners |
| Working hours | 09:00–18:00 UTC, Mon–Fri |
| Response time | One working day |
History
Twenty-four years, abbreviated
Frontier ships
UserLand releases a scripting environment built around a persistent object database and an outliner. Almost nothing else at the time looks like it.
Frontier goes web-shaped
The built-in web server and website framework turn a scripting tool into a publishing platform, and Manila follows.
Radio UserLand
Desktop weblogging with upstreaming, aggregation and XML-RPC. The MetaWeblog API arrives out of the same conversation.
Script Meridian opens
A Conversant community for people using all of the above. James Spahr designs the front page you are still looking at.
The tool years
Formz, pySlice, AttSearchEngine, the Tracer Suite, the ODBC and PostgreSQL extensions, the Patch tool and TLS all land within about thirty months.
The quiet
Attention moves on. The systems do not. Most of what was built in the tool years keeps running, unattended, in places nobody writes about.
Maintenance as a practice
The studio forms around the work that keeps arriving: audits, migrations, and getting a 2002 server onto a certificate that a 2020 browser accepts.
The site, rebuilt
Same design language, new foundation: responsive, accessible, self-contained, and with the archive finally indexed and searchable.
The people
Four practitioners
No account managers. The person who scopes your work is the person who does it.
James Spahr
Designed the 2002 Script Meridian layout that this site still wears. Works on publishing pipelines and the parts of a CMS that editors actually touch.
André Radke
Database extensions, TLS, and the unglamorous business of keeping a 2002 server answering requests in 2026 without embarrassing anybody.
Brent Simmons
Contextual-menu plugins, editors, and a long-held conviction that the object database was a genuinely good idea that arrived early.
Want to talk it through?
Tell us what the system does, who depends on it and what is worrying you. The first conversation costs nothing and usually clarifies more than a proposal would.