Posted on

Ancient Web: The Lighthouse Directory Has 24,800 Lights and Keeps Counting

The Lighthouse Directory is what happens when a useful list refuses to stop growing for twenty-seven years.

Visit the Lighthouse Directory

The project was founded in 1999, during the famous relocation of North Carolina’s Cape Hatteras Lighthouse. Its purpose was straightforward: collect reliable information about lighthouses and connect researchers to other good sources on the Web.

It now covers more than 24,800 lighthouses around the world.

That number is not a static brag buried on an abandoned homepage. The site is still being maintained. Regional pages are checked and revised, new photographs are added, restoration news appears on the front page, and the directory continues correcting the slow decay that happens when thirty thousand outbound links meet the real Internet.

The entries are compact but practical.

A listing can include when a light was established, tower height, focal-plane height, flash pattern, construction, current status, ownership, access information, photographs, maps, and links to preservation groups or official light lists. Destroyed lighthouses remain in the directory rather than disappearing simply because the tower did.

That last part is important.

A lighthouse directory eventually becomes a directory of absence too.

The site also defines its terms instead of assuming everyone already knows them. What counts as a lighthouse? How is it different from a beacon? What is a light station? What does focal plane mean? The Directory settles on a practical definition: a substantial tower, at least four meters tall, built to carry a navigational light.

By February 2009, after the Hainan page was added, the listings covered the entire world. “Entire world” did not mean finished. New lights are found, structures are demolished, access changes, towers are automated, restorations begin, links rot, and countries revise their own records.

So the work continues.

This is one of the best kinds of old Web project: narrow enough for one person’s editorial judgment to matter, broad enough to become infrastructure for everybody else studying the subject.

It is hosted by ibiblio at the University of North Carolina, another long-running corner of the Internet built around keeping useful information publicly reachable.

CacheRat’s 1,967 Ancient Web Domains research list includes pages like this because a hand-maintained specialist directory can quietly become more durable than services with vastly larger budgets.

The Web loves replacing directories with search boxes.

Sometimes the directory was better.

Browse the world’s lighthouses

Posted on

Ancient Web: Don Eyles Explains What the Apollo 11 Computer Alarms Actually Meant

The Apollo 11 computer alarms are usually told as a thirty-second story: alarms appeared, Mission Control said continue, and the landing succeeded. Don Eyles’s version takes about as long as it should.

Read Tales from the Lunar Module Guidance Computer

Eyles was one of the programmers who developed software for the Lunar Module guidance computer at the MIT Instrumentation Laboratory. His paper, presented to an American Astronautical Society conference in 2004 and expanded online with illustrations and comments, explains the system from the perspective of somebody who had actually lived inside the code.

The famous Apollo 11 alarms are only part of it.

During powered descent, an interface problem involving the rendezvous radar consumed roughly 13 percent of the computer’s duty cycle. The overloaded computer issued program alarms and restarted work in a controlled way, discarding lower-priority tasks while preserving the important ones.

That distinction matters.

The computer was not simply “crashing.” Its executive system was doing something recognizably modern: managing scarce processing time under overload and keeping the critical work alive.

Eyles also describes a less famous problem involving the Lunar Module’s descent-engine throttle control. Erroneous assumptions and a marginally stable control algorithm could produce violent throttle oscillations. His account reaches backward to Apollo 5 and forward through changes made after the early lunar missions, showing how flight software evolved because the spacecraft kept teaching the programmers things the simulations had not.

Then there is the hardware.

The Apollo Guidance Computer worked with 36K words of fixed memory and 2K words of erasable memory. The Lunar Module and Command Module each carried one. Eyles notes that, counted together, the Moon landing was accomplished with about 152 kilobytes of onboard computer memory.

That number is fun trivia until you read what the software actually did.

Navigation. Guidance. Engine sequencing. Displays. Radar interfaces. Crew interaction through the DSKY. Real-time task scheduling. Failure recovery. All while flying a machine that could not be rebooted by walking over to it.

The page matters in 2026 because it is not a retrospective assembled from simplified quotations. It is a technical witness explaining the architecture, mistakes, fixes, naming conventions, people, and operational pressure in enough detail that the old software becomes engineering again instead of mythology.

CacheRat’s 1,967 Ancient Web Domains research list keeps finding pages like this: documents sitting quietly on personal domains that are better than the summaries built on top of them.

Apollo had plenty of heroes.

One of them was a scheduler that knew which jobs could wait.

Read Don Eyles’s complete Apollo paper

Posted on

Ancient Web: This Dorothea Lange Gallery Keeps the Original FSA Captions

Everybody knows Migrant Mother. Far fewer people have sat with forty-two Dorothea Lange photographs and read the government field captions attached to the people standing inside them.

Visit the Dorothea Lange gallery

The History Place’s Migrant Farm Families page does exactly that.

The photographs were made before World War II for the U.S. Farm Security Administration while Lange documented the living conditions of migrant agricultural workers and their families across the American West. The gallery keeps the images grouped by circumstance rather than celebrity: Dust Bowl farms, highways west, roadside camps, tents, harvest work, relief lines, sick children, cooperative farms, and families still moving.

The captions are the part worth slowing down for.

They identify places, wages, routes, illnesses, failed farms, family histories, and temporary jobs. One family abandoned its Oklahoma farm after drought and kept moving toward Bakersfield by picking cotton for enough money to buy food and gasoline. Another worker had spent thirteen years traveling from crop to crop with his family. A group of carrot workers described making barely enough in half a day to call it wages.

That information changes the photographs.

Without the captions, a viewer sees hardship.

With them, the photographs become records of how hardship actually moved through geography, labor markets, weather, debt, residency rules, transportation, and family life.

The page itself is also a good example of an older editorial Web. There is no infinite scroll, recommendation engine, animated timeline, or attempt to turn the photographs into a multimedia experience. The site gives you the pictures, the captions, some basic organization, and enough empty space to look at them.

That restraint works particularly well here.

The Internet has spent years rediscovering old public-domain and government photography one viral image at a time. Pages like this preserve the set instead of just the icon.

That matters because Lange’s power was not limited to one mother looking away from the camera. It was cumulative. Roads, camps, children, broken cars, work crews, relief checks, dust, and temporary shelter form a system when seen together.

CacheRat’s 1,967 Ancient Web Domains research list includes old reference pages like this because the surviving value is often not fancy presentation. It is the fact that somebody assembled the material and left the context attached.

Forty-two photographs are a gallery.

Forty-two photographs with their original captions are evidence.

Read through the complete Lange gallery

Posted on

Ancient Web: Siphonophores.org Explains the Ocean Animal Made of Animals

A siphonophore looks like the ocean started assembling one animal and then decided a committee would work better.

Visit Siphonophores.org

The site explains a group of marine animals that are colonial in the literal biological sense. A siphonophore begins from a single embryo, then produces many genetically identical bodies that remain physically integrated. Those bodies specialize: some catch prey, some swim, some reproduce, and others handle different parts of keeping the colony alive.

The Portuguese man o’ war is the famous relative, but the stranger examples live deep offshore.

Siphonophores.org grew out of specialist research rather than general-interest science publishing. Casey Dunn and collaborators have used field observations, morphology, development, molecular data, and deep-sea imaging to study how these animals evolved their extreme division of labor.

That background matters because siphonophores are unusually difficult animals to understand from preserved specimens alone.

They are fragile. They can be long. Their parts separate easily. A net can turn a coherent colony into a bag of pieces before anyone has a chance to understand how those pieces functioned together.

Remote-operated vehicles changed that. Researchers could finally watch intact colonies drifting, swimming, extending tentacles, and hunting hundreds of meters down.

Some species are enormous. Footage associated with the site has shown Apolemia colonies tens of meters long. Others, including Erenna, use bioluminescent structures as lures. The weirdness is not decorative. It is functional anatomy operating at a scale and organization that does not map neatly onto our usual idea of an individual animal.

The site’s value in 2026 is its narrowness.

A general encyclopedia can tell you what a siphonophore is. A specialist site can spend pages on body organization, life cycles, terminology, species, phylogeny, and the historical confusion produced by trying to describe colonies from fragments.

That depth is exactly what the independent Web used to be unusually good at producing. One person or research group could build the reference they wished existed and leave it online for the next curious stranger.

CacheRat’s 1,967 Ancient Web Domains research list keeps turning up pages like this: not famous destinations, but deep holes dug by people who know exactly where the interesting layer is.

Siphonophores.org happens to be one of the holes with glowing tentacles in it.

Explore the siphonophore reference site

Posted on

Ancient Web: NebraskaAirCrash Maps the Places Where Planes Never Came Home

NebraskaAirCrash.com is what happens when local history is treated as something you can still go stand on.

Visit NebraskaAirCrash.com

The site, researched by Jerry Penry, documents fatal military and civilian aircraft crashes in Nebraska with an unusual combination of archival material and field work. Accident reports sit beside photographs of present-day fields, memorial signs, wreckage fragments, newspaper clippings, maps, crew lists, and notes from visits to the actual locations.

That changes the scale of the history.

A wartime loss that might otherwise survive as an aircraft serial number becomes a pasture, a date, a flight crew, a weather report, a cemetery marker, and a set of names.

One of the site’s most striking entries covers the August 3, 1944 crash near Naper. A C-47 carrying a crew of four and twenty-four P-47 pilots went down during a thunderstorm, killing all 28 aboard. Penry’s page includes the crash location, memorial material, photographs from a 2007 visit, and the iron cross that marks the site.

Elsewhere the project extends into civilian aviation. Its page on Braniff Airways Flight 250 documents the 1966 BAC One-Eleven crash near Falls City that killed 42 people. The page combines the official investigation with contemporary newspaper material, passenger and crew information, photographs, and later memorial events.

This is not a slick database.

It is closer to a researcher’s workbench that happens to be public.

The site also wanders into the physical debris surrounding the crashes. There are pages identifying World War II .50-caliber ammunition headstamps and manufacturers because spent casings and links still turn up at former training areas. That sort of material is easy to dismiss until you are standing in a field holding an object with two stamped letters and trying to determine what happened there eighty years ago.

Then the obscure reference page is suddenly the useful one.

That is why NebraskaAirCrash belongs in the Ancient Web series. It demonstrates what small independent sites can do particularly well: stay narrow, accumulate details for years, accept corrections, revisit physical locations, and preserve information that is too local for a general encyclopedia to maintain at this depth.

CacheRat’s 1,967 Ancient Web Domains research list contains a lot of sites built by people who decided one subject deserved far more attention than the rest of the Internet was willing to give it.

Sometimes that obsession is the archive.

Explore Nebraska’s documented crash sites

Posted on

Ancient Web: TEXTFILES.COM Saved the Under Construction GIF

There was a time when admitting your website was unfinished required a tiny animated construction worker, a striped barricade, several flashing lights, and perhaps a bulldozer that looked like it had been drawn during lunch.

Visit the Under Construction collection

TEXTFILES.COM preserved thousands of these graphics in one gloriously unreasonable pile.

The Under Construction banner was one of the defining visual habits of the personal Web. A page owner would add one while building a new section, redesigning a homepage, or simply acknowledging that whatever was there was not yet done.

Which, in retrospect, was refreshingly accurate.

Modern websites silently change underneath users. The old Web put on a hard hat and announced the mess.

Archivist Jason Scott discussed this collection during his DEF CON 19 talk about web preservation. He described having around ten thousand Under Construction images and joked that putting all of them on one page could crash browsers. The absurd scale is the point: these were not one standard icon copied everywhere. People remixed the idea endlessly.

There were workers digging. Workers hammering. Rotating road signs. Blinking warning lights. Skeletons. Cartoon characters. Heavy equipment. Flaming text. Objects of uncertain purpose moving back and forth forever because animated GIF technology had arrived and restraint had not.

What looks like kitsch now was also a shared visual language.

A newcomer did not need instructions. Yellow-and-black stripes meant the page was still being built. The graphic connected millions of unrelated homepages through a visual convention that nobody’s design system had approved.

That is why the collection matters in 2026.

An archive of page graphics preserves a part of Internet history that screenshots and text dumps miss. HTML tells you what links existed. The GIFs tell you what the place felt like.

The same little files continue turning up in modern retro sites, software documentation, art projects, and essays about early web culture. They survived because people remember them immediately even when they cannot remember the homepage where they first saw one.

CacheRat’s 1,967 Ancient Web Domains research list exists for this same reason: the interesting material is often not the famous site itself but the strange supporting ecosystem around it.

The Internet is permanently under construction now.

We just stopped putting up the sign.

Enter the Under Construction GIF pile

Posted on

Ancient Web: Electronixandmore Grew Out of an AOL Antique Radio Page

Electronixandmore has the sort of origin story that used to be normal on the Web: a kid liked antique radios, AOL gave him a few megabytes and a page builder, and twenty-seven years later the thing had become an electronics museum.

Visit Electronixandmore

Jon Stanley says the site began in late 1999 as Jon’s Antique Radios, built with AOL 5.0’s Easy Designer to show his small radio collection. The original version had the fixed tables and download-time problems that came with page generators of the period, so in 2000 he rebuilt it by hand.

Using Notepad.

That detail tells you nearly everything about the site.

The collection expanded from radios into televisions, computers, test equipment, vacuum tubes, calculators, telephones, electronic components, and homebuilt projects. Schematics and graphics were often made with simple tools such as Microsoft Paint because small files mattered when people were still measuring web pages against dial-up connections.

The AOL storage eventually became too small. Electronixandmore.com was registered in August 2002, and the site continued growing under its own name.

Then something especially Ancient Web happened: it stayed recognizable.

Stanley says the general look remained largely unchanged for about ten years. By 2012 the quantity of material had finally become difficult to maintain, so he learned PHP and moved much of the collection into server-generated pages backed by a database. The automation improved. The basic purpose did not.

There is a useful distinction here between a retro-styled website and an old website that simply kept working.

Electronixandmore belongs to the second category.

The site also documents the way expertise used to accumulate online. Stanley’s interest in vacuum tubes led him into vintage radios, then repair work, then engineering. The website expanded alongside that learning process instead of appearing later as a polished portfolio explaining it in reverse.

You can see the sediment layers.

That makes the site valuable beyond the individual radios. It preserves one person’s transition from AOL homepage tools to hand-coded HTML to PHP while simultaneously preserving the hardware he was studying.

CacheRat’s 1,967 Ancient Web Domains research list is full of pages where the subject matter and the website aged together. Those are often better historical records than a modern article written after everything has already become “vintage.”

Electronixandmore started by documenting old electronics.

Eventually the website became one of them.

Explore the Electronixandmore collection

Posted on

Ancient Web: Karl Sims Evolved Creatures Before Generative AI Had a Name

Long before “generative” became a product category, Karl Sims was letting populations of blocky virtual organisms mutate until some of them figured out how to swim, walk, jump, follow targets, and fight over a green cube.

Visit Karl Sims’s site

The centerpiece for anyone arriving from the Ancient Web is Evolved Virtual Creatures, Sims’s 1994 work. The creatures were not animated one limb at a time by an artist. Their bodies and control systems were encoded, varied, tested, selected, copied, combined, and mutated across generations inside a simulation.

Give the population a task and evolution did the rest.

The results still look strange because evolution has no obligation to produce a sensible character rig. Some creatures crawl. Some tumble. Some discover motions that are effective without looking remotely like anything a human animator would have designed.

That is the interesting part.

Sims was working at the intersection of computer graphics, artificial life, and evolutionary computation when those fields still required an explanation before the demonstration. His site preserves not only videos but the technical trail behind them: the SIGGRAPH 1994 paper “Evolving Virtual Creatures,” earlier work on artificial evolution for graphics, procedural models, particle animation, and interactive evolution.

The surrounding career makes the archive even better. Sims studied computer graphics at the MIT Media Lab, worked at Thinking Machines Corporation, founded visual-effects software company GenArts, and created interactive museum installations including Genetic Images and Galápagos. The latter let museum visitors become the selection pressure by choosing which forms reproduced.

A quarter-century of AI marketing has made it easy to forget how old the underlying urge is: build a system that can search a possibility space humans would never explore manually, then see what crawls out.

Sims was doing that with creatures in 1994.

The page matters in 2026 because it leaves the papers, demonstrations, and artwork together. You can move directly from a bizarre walking pile of blocks to the actual research describing how it was generated. That continuity is increasingly rare. Modern summaries tend to clip the video, call it an early AI experiment, and sever it from the engineering that made it interesting.

CacheRat’s 1,967 Ancient Web Domains research list includes sites like this because sometimes an old homepage is not nostalgia at all. It is the lab notebook for an idea that became fashionable decades later.

The creatures are still weird.

The future just caught up with them.

Explore Karl Sims’s original work and papers

Posted on

Ancient Web: MedievalWarfare.info Built a Giant Reference Maze

MedievalWarfare.info feels like somebody took a shelf of medieval-history books, cut the index cards loose, and connected every subject with blue hyperlinks.

Visit MedievalWarfare.info

The site covers a huge spread of material: battles, fortifications, sieges, armour, crusades, military organization, logistics, communications, re-enactment, historical figures, and related source material. Individual pages keep branching into narrower subjects, which branch again into castles, campaigns, equipment, documents, and external references.

This is not minimalism.

It is the old specialist Web approach to information: if another page might help, link it.

The result is a site that rewards wandering.

A reference site built sideways

Modern publishing tends to organize history as a sequence of articles optimized around individual search queries.

MedievalWarfare.info behaves more like a cross-referenced handbook.

A page about siege warfare does not exist by itself. It points toward fortifications, water supply, logistics, mining, communications, military organization, historical battles, and surviving castles. Other sections jump sideways into crusaders, armour, books, re-enactment, and medieval life.

That structure matters because history is mostly relationships.

A castle design makes more sense when you understand the problems it was meant to solve. A campaign makes more sense when you understand transport and supplies. A piece of armour makes more sense when placed beside the weapons and tactics of the same period.

The site’s dense link structure tries to preserve those connections.

It is also visibly from an earlier web-design generation. Tables, text links, small images, old navigation conventions, and pages that assume the reader will tolerate a lot of information on one screen are all part of the experience.

Some of the historical claims are broad enough that a careful reader should verify them against stronger academic sources. That is normal for a hobbyist reference site and worth saying explicitly. The value here is not that every sentence should be treated as final authority.

The value is the scale of the hand-built subject map.

Sites like this show how enthusiast publishing worked before every topic was compressed into the same content-management template. Somebody could build a sprawling reference work with its own internal logic, keep expanding it, and let readers discover subjects through links rather than an algorithmic feed.

CacheRat’s 1,967 Ancient Web Domains research list includes specialist sites like this because the architecture itself is part of what is being preserved.

The old Web did not always give you an article.

Sometimes it gave you a rabbit hole with battlements.

Explore MedievalWarfare.info

Posted on

Ancient Web: NTSC-TV.com Explains Why Analog Color Television Was So Weird

NTSC-TV.com is a reminder that analog color television was not one invention. It was a truce between physics, bandwidth, patents, broadcasters, regulators, and millions of black-and-white televisions that nobody wanted to make obsolete overnight.

Visit NTSC-TV.com

The site presents itself as a set of color-television tutorials with more than 300 links across more than 90 subjects. Its table of contents covers scanning, timing and synchronization, gamma, resolution, bandwidth, color physics, encoding, decoding, digital video, VCR signals, and practical circuits.

Then it drops into history.

A major section reproduces a 1981 SMPTE historical paper by Donald G. Fink describing the forces behind the NTSC standards. The story is less “engineers discovered the correct answer” and more “an industry full of competing interests had to agree on something television stations and consumers could actually use.”

Compatibility won because installed hardware mattered

The first NTSC established American monochrome standards around 1941. By the time color arrived, the central problem was brutal: a new color system could not simply strand every existing black-and-white receiver.

CBS pushed an incompatible field-sequential color system. RCA and others pursued compatible approaches. The FCC briefly authorized the CBS system, but the public had little reason to embrace broadcasts their existing sets could not receive properly.

The second NTSC eventually approved the compatible color standard in 1953.

That solution is the source of much of analog television’s beautiful ugliness. Color information had to coexist with an older monochrome signal inside a six-megahertz channel while preserving reasonable reception on existing sets.

NTSC-TV.com does not simplify that into a cute diagram and stop. It walks through the compromises: scanning structure, subcarriers, luminance and chrominance, bandwidth, timing, color-difference signals, interference, and why PAL and SECAM later made different tradeoffs.

The site’s footer dates back to 1999, and the page design feels like the engineering Web of that period: dense text, tiny navigation, diagrams, technical references, and an assumption that the visitor is willing to sit down and learn how the thing actually works.

That assumption is refreshing.

Modern video hides astonishing complexity behind HDMI cables and software APIs. NTSC exposed much more of the machine. If the sync was wrong, the picture rolled. If the color phase was wrong, faces went green. If the bandwidth was limited, detail vanished. You could practically watch the engineering compromises misbehave in real time.

CacheRat’s 1,967 Ancient Web Domains research list includes pages like this because specialist technical websites often preserve not just specifications, but the arguments that produced them.

A standard looks inevitable after everybody forgets the fight.

Read the NTSC television tutorials