Tag: webhistory

Posted on by

Ancient Web: Silkqin Built a Personal Library Around One Ancient Instrument

Some personal websites grow until they stop looking like homepages and start looking like somebody quietly built a research library in public.

Visit Silkqin

Silkqin is John Thompson’s long-running site devoted to the guqin, the ancient Chinese seven-string zither. The domain dates to the early 2000s, but the material represents decades of performance, translation, historical research, reconstruction, and collecting.

The site is enormous in the old-Web sense of the word.

There are sections on historical handbooks, instruments as physical objects, paintings, poetry, songs, tunings, performance practice, ideology, biographies, recordings, and the process of reconstructing music from old tablature. Navigation is dense because the subject is dense.

One particularly important theme is right in the site’s name: silk strings.

Modern guqin players often use metal-nylon strings, but Thompson has spent years documenting and advocating historically informed performance with traditional silk strings. His pages discuss how the material changes the sound and playing technique, along with the historical shift away from silk during the twentieth century.

The Web as a working notebook

Silkqin is not arranged like a museum exhibit designed to give a visitor five facts and send them onward.

It behaves like a scholar-performer’s working archive.

A page may contain historical quotations, Chinese text, translation notes, tuning details, links to related essays, audio, references to old qin handbooks, and corrections accumulated over time. Other pages provide recordings and reconstructed performances of pieces whose notation survives from centuries ago.

That makes the site particularly suited to the Web as it originally worked: many small documents joined by links, allowed to grow independently, with the reader free to disappear down whichever path becomes interesting.

It is also a reminder that the early independent Web was global in a way that gets lost when Internet history is reduced to American browser companies and dot-com startups.

A personal domain could become a publishing platform for extremely specialized cultural knowledge that would otherwise be scattered across books, manuscripts, recordings, personal correspondence, and classrooms.

Silkqin is still being used and cited by musicians and researchers. That longevity is part of its value. The site is not merely preserved; it remains useful.

CacheRat’s 1,967 Ancient Web Domains research list includes sites like this because the most valuable old pages are often the ones built by somebody who cared far more about the subject than about whether the site looked modern.

Twenty-three years of domain age is impressive.

A musical tradition measured in millennia is less easily impressed.

Explore John Thompson’s Silkqin archive

Posted on by

Ancient Web: Mercury Arc Rectifiers Glowed Before Silicon Took Over

Before a few slabs of semiconductor could quietly convert serious electrical power, engineers sometimes did the job with glass vessels full of mercury vapor glowing an alarming shade of blue.

Visit the Mercury Arc Rectifiers page

Mike’s Electric Stuff documents mercury arc rectifiers, or MARs, with the enthusiasm of somebody who correctly realizes that obsolete industrial hardware is much more interesting when you can actually see how strange it was.

These devices converted alternating current to direct current at power levels ranging from kilowatts into the megawatt range. Their operation depended on an electrical arc between a mercury pool and metal anodes, with multiple anodes commonly used for multiphase power.

The site explains both the principle and the hardware: glass bulbs, large steel tanks, ignitors, transformers, cooling systems, and the eerie arc itself.

It also preserves the kind of practical detail that rarely survives in a clean textbook diagram.

One retired engineer described how large glass rectifiers were shipped upside down. The mercury had to be carefully moved into the base during installation without allowing its weight to enter and break one of the glass arms. Apparently “quart of mercury escaping from shattered industrial glassware” was a problem best assigned to the experienced crew.

Industrial electronics with visible drama

The photographs are the heart of the page.

There are small rectifier bulbs, museum examples, huge multi-anode units, steel-tank rectifiers, control gear, circuit diagrams, and installations that remained in service long after semiconductor rectifiers had made the technology obsolete.

The page records examples still operating in the early 2000s, including equipment used for lifts, mills, tram power, and battery systems. One restored system had reportedly worked for more than fifty years before retirement.

That longevity makes the transition to solid-state electronics easier to appreciate. Semiconductor rectifiers are smaller, safer, simpler, and dramatically less theatrical.

A silicon diode does not contain a visible pool of mercury with an electric arc leaping through vapor above it.

Progress has costs.

The site also links scanned technical articles and maintenance manuals, turning a collector page into a small practical archive of a technology that most electrical workers will never encounter alive.

CacheRat’s 1,967 Ancient Web Domains research list includes specialist pages like this because obsolete hardware often survives physically after the knowledge needed to recognize it has started disappearing.

The semiconductor won.

The mercury arc rectifier absolutely won the appearance contest.

See the mercury arc rectifier collection

Posted on by

Ancient Web: JWZ’s Tent of Doom Fought the Open Office With Camouflage Netting

The early Web did not merely document software. It also documented what programmers did after spending too many hours inside the offices where that software was being written.

Visit Jamie Zawinski’s Tent of Doom

Jamie Zawinski’s Tent of Doom is one of those tiny Web artifacts that survives because the story is too specific to disappear cleanly.

During the Netscape era in the mid-1990s, Zawinski transformed his cubicle by surrounding it with camouflage netting. Contemporary and later references describe the result as an improvised enclosure inside the office: part privacy screen, part joke, part protest against the visual and acoustic openness of cubicle life.

The page was already circulating as a curiosity while the commercial Web was still young. Old bookmark lists included it alongside other strange destinations people passed around before social feeds made “viral” a normal noun.

Years later, Slashdot commenters still invoked the Tent of Doom whenever somebody built an unusually elaborate cubicle modification. The page had escaped its original workplace and become part of programmer folklore.

A homepage-sized monument to office resistance

The appeal is easy to understand.

Open offices and cubicles are designed around organizational efficiency. Workers experience them from the inside as light, noise, interruptions, lack of privacy, and the vague knowledge that anyone walking past can see what is on the monitor.

Zawinski’s answer was not a productivity framework.

It was camouflage netting.

That is exactly the kind of thing old personal pages preserve well. A company history of Netscape will discuss browsers, IPOs, Microsoft, Mozilla, and the browser wars. Those things matter.

But they will not necessarily tell you what one programmer physically did to his desk because the office itself was irritating him.

The Web page does.

It also captures something about early technical culture: programmers documented jokes, office hacks, grudges, experiments, and personal fixes with the same instinct they used to document code. If it happened and somebody had disk space, it could become a page.

CacheRat’s 1,967 Ancient Web Domains research list includes odd survivors like this because company history makes more sense when the humans are allowed back into it.

Netscape helped define the commercial Web.

One of its programmers apparently still wanted a door.

See the Tent of Doom

Posted on by

Ancient Web: psDooM Let Sysadmins Shoot Processes

Somebody looked at ps, renice, and kill and decided the obvious missing feature was a shotgun.

Visit the psDooM screenshots page

psDooM is a Unix process monitor built on Doom. Running processes appear inside the game as monsters labeled with a process ID and part of the process name.

The joke goes considerably further than a visual skin.

The program periodically checks the machine’s process table and spawns or removes monsters as processes appear and disappear. Damage to a process-monster corresponds to changing that process’s priority with renice. Killing the monster can kill the associated Unix process.

This is therefore one of those rare pieces of software where “shooting the runaway process” can be technically accurate documentation.

The project grew from the release of Doom’s source code in the late 1990s. The psDooM site traces its lineage through XDoom and a University of New Mexico proof of concept called “Doom as a tool for system administration.”

A GUI nobody asked for

A conventional process monitor turns machine state into rows, numbers, percentages, and sortable columns.

psDooM turns the same abstraction into physical space.

Processes occupy a level. They can be approached. Their labels float in front of them. Administrative actions become game actions. The metaphor is ridiculous, but it is also understandable almost immediately to anyone who has played Doom.

That is what makes the project more interesting than a one-line programming gag.

Interface design is largely the business of choosing metaphors for invisible state. Desktop systems use files and folders. Network tools use graphs. psDooM uses demons.

The screenshots page preserves the proof that this really existed, while the main project documentation explains the process-monitoring behavior, supported Doom versions, custom levels, user filtering, and other details.

It is also a snapshot of a specific open-source moment. Once id Software released Doom’s source, programmers did not merely preserve the game. They treated it as reusable infrastructure and started asking increasingly strange questions about what else its engine could represent.

CacheRat’s 1,967 Ancient Web Domains research list includes artifacts like this because software history gets much more interesting when you keep the experiments that were never supposed to become products.

Modern process managers are cleaner, safer, and more useful.

None of them let you circle-strafe Apache.

See psDooM in action

Posted on by

Ancient Web: Roger Russell Documented McIntosh From the Inside

There are corporate product histories, collector databases, and engineering memoirs. Roger Russell’s McIntosh pages manage to be all three at once.

Visit Roger Russell’s site

Russell’s McIntosh History section covers the company from its early years through decades of amplifiers, preamplifiers, tuners, receivers, loudspeakers, equalizers, car audio, home theater gear, drivers, accessories, and test equipment.

The unusual part is who assembled it.

Russell was not merely looking at McIntosh equipment from the outside. His pages discuss work he personally did, including loudspeaker development and the C26 preamplifier. That puts technical descriptions, company history, product listings, and personal recollection in the same archive.

The site also preserves the culture around the hardware.

One section covers the McIntosh Amplifier Clinics, which began in 1962. Dave O’Brien traveled to dealers and tested customers’ amplifiers in front of them, eventually testing more than a million amplifiers over roughly three decades. It was marketing, engineering demonstration, customer service, and live theater for people who cared very deeply about distortion figures.

The details collectors actually need

Russell’s product-history pages list model names, sales dates, original prices, and technical notes. Other sections collect magazine reviews, patents, advertising material, speaker-wire history, acoustic test equipment, and restoration information.

That is the level of detail that becomes more valuable as hardware ages.

A glossy retrospective can tell you that McIntosh made famous amplifiers. A specialist archive can help identify which amplifier, when it was sold, how it differed from a neighboring model, and what somebody who worked there remembers about why it existed.

The site also has the unmistakable structure of a long-lived personal Web project. Information accreted where it was useful. Pages became deep. Navigation grew around the collection instead of being redesigned every few years to satisfy a branding committee.

That is not pretty in the modern product-design sense.

It is excellent archival behavior.

CacheRat’s 1,967 Ancient Web Domains research list includes sites like this because specialist knowledge often survives on personal pages long after the people, companies, and hardware involved have moved on.

The blue meters get the attention.

The old HTML remembers why they were there.

Explore Roger Russell’s McIntosh history

Posted on by

Ancient Web: Zompist Tried to Prove English Spelling Has Rules

English spelling has spent centuries earning its reputation as a practical joke, and Mark Rosenfelder’s old Zompist page responds with the deeply Internet-era reaction: fine, let’s model the damn thing.

Visit Zompist’s English spelling page

The page, dated 2000, is titled “Hou tu pranownse Inglish.” Its argument is not that English spelling is elegant. It is that the system contains far more regularity than people usually give it credit for.

Rosenfelder lays out sound values, dialect assumptions, letter combinations, vowel rules, consonant rules, exceptions, historical leftovers, and the famous troublemakers such as gh and ough.

He also takes a swing at George Bernard Shaw’s famous “ghoti” joke, arguing that the proposed pronunciation only works by ignoring where English spelling rules actually permit those letter values.

The page then does something that makes it especially interesting as an old Web artifact: it turns the argument into a computational test.

Make the computer pronounce it

Rosenfelder assembled a sample lexicon of more than 5,000 English words and a set of rules for his Sound Change Applier. According to the page, the rules generated 59 percent of pronunciations perfectly and 85 percent either perfectly or with only relatively minor errors.

That does not make English spelling sane.

It does demonstrate that “English spelling is completely random” is not a particularly useful explanation.

The page is also full of old-browser archaeology. It discusses Unicode support as something the reader’s browser may or may not handle correctly and explains notation choices partly in terms of what HTML could reliably display.

That mixture is classic early specialist Web publishing: a serious subject, a personal voice, hand-built technical notation, downloadable data, and the assumption that an interested reader will happily scroll for a very long time.

Modern search results tend to chop questions like this into isolated answers: why is ough weird, why is knight spelled that way, why does c have two sounds?

Rosenfelder tried to put the machinery in one place.

CacheRat’s 1,967 Ancient Web Domains research list includes pages like this because old personal sites often preserve the full argument instead of optimizing each paragraph into a separate answer box.

English spelling is still a mess.

At least this mess comes with documentation.

Read the full spelling system

Posted on by

Ancient Web: KeyHut Still Turns Old PCs Into Cash Registers

KeyHut’s cash-register software is a reminder that an old computer does not become useless just because Silicon Valley has stopped admiring it.

Visit the KeyHut POS page

The program, maintained by Dale Harris, turns a DOS or Windows PC into a point-of-sale terminal. It handles the things an actual small shop needs: receipts, inventory, taxes, employee access, scanners, cash drawers, customer information, sales history, ticket sales, scales, networking, and assorted retail hardware.

What it deliberately does not require is almost more interesting.

The documentation says the program does not need a mouse. It does not process credit cards itself. It does not need a modern graphical interface. Keyboard navigation is treated as an advantage because cash-register work consists largely of repeating known actions quickly.

The site is equally direct about price: the software is free.

Harris’s donation pitch asks satisfied users for five dollars, donated equipment, a link from their Web site, or helper software. It reads less like a software company funnel and more like somebody keeping a useful machine alive because people keep using it.

Software that refuses to become obsolete

KeyHut is valuable as old-Web archaeology because the page and the program reinforce each other.

The site explains parallel-port printers, serial devices, pole displays, receipt printers, scanners, DOSBox, older Windows versions, networking, and file-based register configuration. It assumes the reader might still have hardware that most modern software has forgotten exists.

That is not purely nostalgic. Old retail equipment can be durable, cheap, and perfectly adequate for a small operation. A computer that would be miserable at running a modern browser can be extremely competent at adding prices, printing receipts, and opening a cash drawer.

The documentation even explains that the .POS file effectively is the register configuration, a wonderfully concrete contrast with modern cloud software where the important state may live somewhere the user cannot see.

The result is an odd kind of longevity. The interface looks ancient because the job did not require reinvention.

CacheRat’s 1,967 Ancient Web Domains research list includes sites like KeyHut because old software sometimes survives for the best possible reason: it still solves the problem.

A touchscreen, subscription, analytics dashboard, and animated onboarding sequence would certainly make this more modern.

They would not necessarily make the cash drawer open any better.

See the KeyHut cash-register system

Posted on by

Ancient Web: The Lurker’s Guide to Babylon 5 Made Fandom Searchable

Before fandom had giant wikis, searchable social platforms, recap podcasts, and databases maintained by companies, Babylon 5 fans built something remarkably close by hand.

Visit The Lurker’s Guide to Babylon 5

The Lurker’s Guide was maintained by Steven Grimm and grew alongside the television series during the 1990s. It collected episode information, analysis, schedules, interviews, background material, online discussion, and links into one organized reference system.

Contemporary Babylon 5 FAQs pointed readers to the Guide as the place to go for detailed information. That alone says quite a bit about what the site represented at the time. Usenet could contain enormous amounts of useful discussion, but finding the right message again was another matter. The Guide acted as memory.

It also existed unusually close to the production itself.

Babylon 5 creator J. Michael Straczynski participated directly in online fan discussion, which made the show’s Internet culture unusually rich but also created practical problems. Fans were repeatedly warned not to post story ideas where Straczynski might encounter them, because unsolicited ideas could create legal complications.

The Web page became a useful boundary layer between conversation and reference.

Fandom before the wiki template

The Guide is interesting now because its structure feels familiar even though the machinery underneath it is not.

Episode pages were assembled from static files. Mirrors existed in multiple countries. FTP material sat beside Web content. Fans consulted Usenet FAQs that pointed toward the Web site, while the Web site itself linked back into the larger online ecosystem.

That was normal Internet architecture in the mid-1990s: several protocols and communities loosely stitched together by people rather than one platform owning the entire experience.

The Guide eventually became significant enough that it was cited in books and magazines as an unusually strong television fan resource. Its real achievement, though, is simpler. It made a sprawling conversation navigable.

Modern fandom sites often begin with a software platform and then accumulate information.

The Lurker’s Guide began with information that was already scattered everywhere and built the platform around the need to preserve it.

CacheRat’s 1,967 Ancient Web Domains research list includes pages like this because fan sites can become primary records of how a work was experienced while it was still unfolding.

You can read about Babylon 5 anywhere now.

This site shows what it looked like when the audience was still waiting for next week’s episode.

Explore The Lurker’s Guide

Posted on by

Ancient Web: Mark Pesce’s 1994 Homepage Still Points Toward Cyberspace

Mark Pesce’s old homepage feels less like a personal profile and more like somebody left a door open into the moment when the Web still thought it might become a navigable three-dimensional universe.

Visit Mark Pesce’s original homepage

The page identifies itself plainly as Pesce’s original homepage, created in 1994. That date matters because several of the documents gathered there were not retrospectives about early cyberspace. They were written while people were still trying to decide what cyberspace was going to be.

Pesce was deeply involved in the early development and promotion of VRML, the Virtual Reality Modeling Language. His page preserves conference talks, essays, technical proposals, Wired pieces, experimental media, and a remarkable amount of period vocabulary: noosphere, cyberspace, virtual worlds, distributed simulations, visualization, collective space.

Some of it reads like engineering. Some reads like philosophy. Some reads like a person who had just discovered that the Internet existed and immediately decided the next obvious step was to rebuild reality inside it.

That was not an unusual mood in 1994.

Before the Web settled down

One of the most useful things on the page is Pesce’s paper from the First International Conference on the World Wide Web in Geneva in May 1994. It describes a visualization system called Labyrinth and introduces an early proposal for a language intended to describe shared three-dimensional spaces on the Web.

The site also preserves talks from SIGGRAPH, VRML conferences, Stanford, MIT, and other venues, alongside writings about cryptography, games, mapping the Earth, networked audio, and virtual communities.

What makes the page valuable in 2026 is not that every prediction came true. Quite a few did not.

The value is seeing what technically serious people thought might happen before browsers, social networks, search engines, smartphones, and app stores narrowed the public imagination of what “online” meant.

Pesce’s page belongs to an Internet where HTML was still small enough that a person could reasonably imagine adding another language and turning the whole network into a shared 3D environment.

CacheRat’s 1,967 Ancient Web Domains research list includes pages like this because old predictions become more useful after enough time has passed to see what reality kept, discarded, or quietly reinvented under another name.

The Web did not become the world Pesce’s homepage imagined.

But three decades later, people are still trying to build that world.

Explore the original Hyperreal homepage

Posted on by

Ancient Web: The Mozilla Museum Kept Netscape’s Green Dinosaur Alive

Before Mozilla became a foundation, a browser engine, Firefox’s family tree, and a word permanently lodged in Web history, Mozilla was a little green monster attached to Netscape.

Visit Tilman Hausherr’s Mozilla Museum

Tilman Hausherr built the Mozilla Museum after the original Netscape mascot began disappearing from Netscape’s own pages. His personal homepage describes Mozilla simply as the little green monster from Netscape and explains that he created the museum because the character had vanished from the company’s site.

That turned out to be unexpectedly useful preservation.

The original mascot belonged to Netscape’s earliest period, when “Mozilla” was already being used internally around the browser project. The name is commonly explained as a playful combination of Mosaic and Godzilla: the browser that intended to become a Mosaic killer.

Later, the word Mozilla would be reused for the open-source organization and browser code released around Netscape’s 1998 open-source turn. The visual identity changed too. The familiar green creature gave way to the red dinosaur associated with the Mozilla project.

But the old mascot did not completely disappear because people had copied it.

Tiny graphics can become historical evidence

The Museum preserves a part of browser history that corporate redesigns are particularly good at deleting.

Logos, mascots, joke graphics, T-shirt art, and internal visual culture rarely receive the same preservation attention as source code or product releases. Yet those things tell us how a company understood itself and how early Internet users experienced the brand.

Mozilla was not merely a technical codename. It was a personality.

Old bug discussions and later Mozilla histories still point back to Hausherr’s museum when explaining the early mascot. References from the early 2000s treat the page as the place to see the green dinosaur that had already become difficult to find on official Netscape properties.

That is wonderfully circular Internet archaeology: later browser developers using an individual’s old homepage to remember imagery from an earlier browser company whose own pages had moved on.

Hausherr’s broader site is itself a classic personal-Web mixture—technical software, anti-Scientology material, magic tricks, jokes, computing definitions, and whatever else interested its owner. The Mozilla Museum fits naturally into that world because early personal sites were not brands with content strategies. They were shelves.

You put the thing there because you thought somebody should be able to find it.

CacheRat’s 1,967 Ancient Web Domains research list includes pages like this because corporate history often survives in places the corporation never controlled.

Netscape moved on.

Some guy in Germany kept the dinosaur.

Explore the original Mozilla Museum