Category: Ancient Web

The most ancient times of the internet: 90s, early 2000s.

Posted on by

Ancient Web: BFRO Has Been Cataloging Bigfoot Reports Online Since 1995

You do not have to believe in Bigfoot to recognize that somebody built a remarkably persistent database about people who do.

Visit the Bigfoot Field Researchers Organization

The BFRO says its website launched in 1995, making it one of the earliest large online collections of reports about an elusive phenomenon. The site is still organized around a geographical sightings database covering U.S. states, Canadian provinces and international reports.

The interesting part is the structure.

Reports are not simply dumped into one giant story pile. The BFRO uses a Class A, B and C system based on how much opportunity there was for misidentification.

Class A generally means a clear visual encounter where ordinary-animal confusion is considered less likely. Class B covers more ambiguous circumstances such as poor lighting, long distance or sound-only incidents. Class C is mostly second- or third-hand material and is rarely included in the public database unless it has historical documentation.

The organization is explicit that this classification describes the circumstances, not how exciting the story sounds.

A 1995 crowdsourcing machine before that word existed

The workflow feels surprisingly modern.

People submit reports. Volunteer investigators contact witnesses, conduct interviews and sometimes perform field follow-up. If the witness permits publication and the report passes the organization’s own credibility screening, notes can be added to the database.

Again, none of that proves the creature described in a report exists. Eyewitness accounts are anecdotal evidence, and the BFRO itself distinguishes them from testable scientific evidence.

What the archive unquestionably documents is the reporting culture.

The database lets a researcher see how alleged encounters are described across geography and time: road crossings, vocalizations, tracks, nighttime incidents, daylight sightings, camping reports and older newspaper accounts.

It also preserves an early-Web model that predates modern social platforms. Instead of posts being sorted by engagement, the information is organized by location, date, classification and investigation notes.

That structure is why the site belongs in an Internet-history collection even for a complete skeptic.

The Web did not only digitize established institutions. It allowed communities built around unresolved questions, fringe subjects and disputed evidence to create their own long-running databases.

BFRO has been doing exactly that for more than three decades.

Browse the BFRO sightings database and its classification system

Posted on by

Ancient Web: Hogranch Froze a Personal Homepage with CP/M, Windows 95 and Stale Links

Hogranch is the kind of personal homepage that accidentally became more interesting by not being redesigned.

Visit John R. Pierce’s Hogranch homepage

The page says it was last modified, barely, in December 2010. What survives is a layered record of one person’s family, cameras, software career, favorite links and Internet-era interests accumulated over years.

There are family photographs, music-festival references and digital photo albums stretching back to the period when owning a digital camera was still worth identifying by model.

Pierce lists a Nikon Coolpix 950, Canon PowerShot S300, Canon S70, Canon 350D and photos taken by his children on a Canon A510.

The hardware names turn an ordinary family-photo section into a small timeline of consumer digital photography.

CP/M, Windows 95 and a pile of stale links

The computing material is even better.

Pierce links to photographs from the period when he worked at Digital Research, adding the parenthetical reminder: “Can YOU say CP/M?”

He also preserved snapshots from Microsoft’s Windows 95 launch event in Redmond, which he attended back when he thought Windows 95 was, in his words, pretty cool stuff.

Then comes a section explicitly labeled “Some of my favorite stale links.”

That heading may be the most honest navigation label on the old Web.

The list points toward Mersenne prime hunting, NASA mission pages, weather imagery, astronomy resources, experimental aircraft photos, live coastal cameras and old Internet humor. Some links survived. Some moved. Some are dead enough that the page comments on their death.

Near the bottom, Hogranch preserves part of a 1996 federal court decision striking down provisions of the Communications Decency Act. The quoted passage praises the Internet’s chaos and cacophony as part of its strength.

Placed on a page like this, the argument feels almost illustrated by the site itself.

Nothing here fits a content strategy. Family pictures sit beside CP/M memories, space links, weather maps, Windows 95, music and constitutional law.

That was the point of a homepage.

You did not need a niche. You needed somewhere on the Internet that was yours.

Explore the frozen-in-place Hogranch homepage

Posted on by

Ancient Web: RossVW Built Registries for Volkswagens the Factory Records Didn’t Explain

Car manufacturers are good at documenting the models they wanted to sell. Enthusiasts often end up documenting the strange versions that fell through the cracks.

Visit RossVW

RossVW is a personal Volkswagen site built around one owner’s growing collection of classic and unusual VWs. The cars range from early postwar models through later water-cooled Volkswagens, but the most useful material is the registry work.

The site’s owner bought a 1996 Golf Harlequin in 1997 after seeing one at a local dealer and researching the unusual multicolored model on Volkswagen’s early corporate website.

In 2002 he started a Harlequin Registry to bring owners together and help determine how many were actually produced.

That is exactly the kind of problem personal websites solve well.

A factory brochure can tell you what a model was supposed to be. A registry can tell you which cars actually survived, what color combinations exist, where they turned up and how production details vary in the real world.

The odd Volkswagens are the interesting ones

RossVW eventually expanded beyond Harlequins.

The homepage points to registries for the 1973 Type 2 “Wild Westerner” and a limited triple-black 1979 Super Beetle convertible. It also preserves a photograph of a 1979 Vanagon prototype obtained from the Volkswagen AutoMuseum during a Type 2 anniversary event in Wolfsburg.

The personal gallery is equally useful because it records cars the owner actually had in hand.

At one point the collection included five Golf Harlequins covering all four base-color variations. The site also documents a 1999 Mexican Beetle body mounted on a 1971 chassis, low-mileage Rabbits, Eurovans, GTIs and other projects that would normally disappear into classified ads after they changed hands.

The writing is not museum prose. It is owner prose: what was bought, what was sold, what needs work, what seems rare and what somebody hopes to build next.

That makes it valuable.

Old-car history survives through factory manuals and official museums, but it also survives because somebody bothered to make a page for a weird paint scheme and kept updating it for years.

A registry is just a list until the official records are incomplete.

Then it becomes evidence.

Browse the Volkswagen collection and registries at RossVW

Posted on by

Ancient Web: Zhongwen.com Turned 4,000 Chinese Characters into Genealogy Trees

The CacheRat source list landed on a small Zhongwen.com page that transliterates English given names into Chinese. The rabbit hole behind it is much bigger.

Visit Zhongwen.com’s English-name page

Zhongwen.com was built by Rick Harbaugh around a project he called Chinese character genealogies: diagrams showing how characters are related through their component parts.

The site’s web edition dates to the 1990s, and Harbaugh’s Chinese Characters: A Genealogy and Dictionary was self-published in 1998 before publication was later taken over by Yale University Press.

The central idea is computationally elegant.

Traditional Chinese dictionaries often organize characters through a fixed list of section headings commonly called radicals. Harbaugh’s system instead uses computerized cross-referencing to connect characters through all of their meaningful components.

The site says more than 4,000 characters can be arranged into these graphical family trees.

A dictionary that behaves like a graph

Harbaugh’s explanation is that every component of a character can itself be treated as a character or historical component, allowing the reader to trace relationships backward toward a relatively small set of roots.

That makes the site useful in two ways.

First, a student who recognizes part of a complicated character has another route to finding it. Second, the structure makes relationships visible rather than reducing every character to an isolated dictionary entry.

The web edition also preserves classical reading material, character FAQs, etymology pages and other language resources. Some pages proudly recommend Netscape Navigator 3.0 or higher, which is the kind of sentence that now functions as its own timestamp.

The project is also unusually transparent about its limits.

Harbaugh notes that the genealogies are based mainly on traditional etymologies derived from ancient seal-script evidence and do not represent the final word in modern historical linguistics.

That caveat makes the project more useful, not less. It tells the reader what kind of map this is.

The little English-name transliteration page is still handy, but it is almost incidental compared with the deeper accomplishment: a 1990s website using hypertext and computer cross-referencing to make a writing system’s internal structure visible.

That is exactly the sort of thing early web enthusiasts were good at doing—building a specialized tool because the medium suddenly made it possible.

Explore Zhongwen.com starting from the original name-transliteration page

Posted on by

Ancient Web: Old Shipbuilder Preserved 65,000 Great Lakes Maritime Photographs

A private archive can begin with something as small as a few family photographs and end up preserving an industry’s paper trail.

Visit Old Shipbuilder

Keith M. Steffke’s site documents the Steffke Memorial Maritime Collection, a research archive focused on shipbuilding and maritime life around southeast Michigan, the Detroit and St. Clair rivers, and the Saginaw River valley.

The scale is startling.

The collection page says it contains more than 65,000 original photographs, over 3,000 rare maritime reference books, blueprints and linen positives, maps, charts, diaries, corporate records, artifacts, films and recordings.

Steffke also maintains more than 3,500 individual files on builders and vessels.

Family history turned into industrial history

The archive grew out of family connections to maritime work.

Steffke’s great-grandfather worked for the Detroit Shipbuilding Company and Great Lakes Engineering Works and had collected photographs of vessels he helped build during the World War I shipbuilding boom. Research into those family ties expanded into a much broader effort to document the yards, workers, companies and technologies that shaped the region.

The collection covers both famous and nearly forgotten builders.

Names include the Detroit Dry Dock Company, Great Lakes Engineering Works, F.W. Wheeler & Company, James Davidson, Detroit Boat Works and smaller family yards that might have built only one or two vessels from an open patch of shoreline.

That breadth is important. Industrial history usually remembers the giant firms because their records survive in bulk. Small builders are easier to erase.

Steffke’s files also reach beyond finished ships into the machinery of the industry: construction techniques, engineering changes, corporate records, lighthouse and lifesaving services, commercial fishing, steamship lines and the people behind them.

The website adds another layer through galleries of Steffke’s scale models. Some models reproduce specific Great Lakes vessels at museum quality, using archival research to reconstruct details that photographs alone may not show clearly.

This is a good example of why independent specialist sites matter.

A regional archive does not need to become a giant institution before it becomes historically useful. Sometimes one person’s obsessive collecting preserves the letterhead, yard rules, photographs and blueprints that a later researcher will discover were the only surviving copies.

The Web page is only the front door.

Behind it is a lifetime of boxes, files and photographs that kept a vanished industrial landscape from disappearing completely.

Explore the Old Shipbuilder maritime archive

Posted on by

Ancient Web: Titanic Breakup Reconstructs the Ship’s Failure from the Keel Up

The most interesting Titanic arguments are no longer about whether the ship broke in half. They are about exactly how several thousand tons of riveted steel failed in the dark.

Read Roy Mengot’s Titanic breakup analysis

This page approaches the problem like a forensic engineering exercise.

Roy Mengot lays out survivor testimony, the condition of the wreck, finite-element stress studies, construction plans, debris locations and later mapping of the double bottom. His central argument is that Titanic’s breakup began from the bottom, with compression failure in the keel structure, rather than as the familiar clean top-down crack behind the third funnel.

The page is careful to explain why the sequence matters.

If the ship simply tore downward from the top, Mengot argues, much of the bending energy would be released too early. That creates problems when trying to explain the additional torn hull sections, the rapid flooding of the stern and the physical arrangement of wreckage on the seabed.

A web page built like a technical notebook

The article walks through tension, compression and the neutral axis of a bending structure before applying those ideas to Titanic.

It discusses the 1996 Gibbs & Cox finite-element model, later structural work, Harland & Wolff construction details and two sections of double bottom documented during later expeditions. One key detail is a structural discontinuity around Frame 25 aft, where the double bottom changes thickness beneath the machinery spaces.

Mengot describes bent keel material and crushed internal structures as evidence consistent with severe compression.

The page then maps the failure upward through decks and shell plating, trying to explain why the stern could briefly change attitude before sinking and why so much side plating separated from the stern.

This is an interpretation, not a neutral encyclopedia entry, and the site says so through the structure of its argument. That is part of what makes it useful.

Researchers can see the assumptions, diagrams, evidence and reasoning instead of receiving one polished animation with the uncertainty removed.

The page also preserves an interesting history of Titanic analysis itself. Ideas changed as new wreck imagery, construction drawings and engineering studies became available. A scenario that seemed persuasive in the 1990s could be challenged by evidence documented a decade later.

That is exactly the kind of technical discussion the old Web was good at hosting: long, specific, diagram-heavy and uninterested in whether the subject could be summarized in thirty seconds.

Explore the full Titanic breakup argument and wreck diagrams

Posted on by

Ancient Web: Carabiner Collection Treats Climbing Hardware Like Industrial Archaeology

A carabiner looks simple until somebody puts 540 of them next to each other.

Visit Carabiner Collection

Sam Johnson’s site turns climbing hardware into a study of mechanical design. The collection is organized by locking system, gate type, historical pattern and oddball engineering choices rather than treating every aluminum loop as basically the same object.

The site lists more than 540 photographed carabiners, with additional pieces still being processed. Categories include screw locks, twist locks, triple-action locks, slide locks, multi-gate models, non-locking carabiners, gated hooks and accessory hardware.

That classification makes the collection useful well beyond collecting.

A climbing tool has to solve several competing problems at once: it must be strong, light, easy to operate, resistant to accidental opening, and ideally not snag ropes or webbing at the nose. Different eras and disciplines solve those problems differently.

The dead ends are often the best part

Johnson explicitly says he is interested in interesting design dead ends.

That gives the site personality. A museum organized only around successful designs can make engineering history look inevitable. It was not.

The collection documents milled noses, recessed pins, hot-forged bodies, odd gate geometry, multiple locking sleeves, unusual spine shapes and safety concepts that either became standard or quietly disappeared.

One virtual exhibit follows snagless nose designs. Another part of the site documents the evolution of compact Black Diamond screwgates. Individual entries can include old catalog advertisements, patents and notes about manufacturing methods.

A 1990s MSR I-beam line, for example, becomes a snapshot of an industry just before keylock noses, wiregates and hot forging changed what modern carabiners looked like.

The site’s author is careful about scope. He has professional experience in tree climbing and ropes work, but repeatedly warns that the collection is not safety instruction and should not be used as a substitute for proper training.

That disclaimer actually makes the archival purpose clearer.

This is not a gear-review site trying to tell you what to buy this season. It is a personal catalog showing how a mature tool evolved through hundreds of small engineering decisions.

The Web needs more collections like this: somebody notices that ordinary objects contain a design history, then documents them before the older examples and paper catalogs disappear.

Explore the photographed carabiner collection

Posted on by

Ancient Web: M2Museum Cataloged 6,258 Micro Machines by Color, Set and Year

Micro Machines are exactly the kind of collectible that becomes impossible to identify once the original packaging is gone.

Visit the Micro Machines Museum

M2Museum attacks that problem with collector-level stubbornness. Its homepage lists a collection count of 6,258 pieces and describes the site as a free reference guide for Micro Machines collectors.

The useful part is not the raw number. It is the granularity.

The gallery breaks the collection into categories such as construction equipment, military vehicles, aircraft, NASA and space pieces, fantasy lines, promotional pieces, movie tie-ins and many more. Individual pages frequently show several versions of what appears at first glance to be the same miniature.

That distinction matters because Galoob reused bodies constantly.

The museum’s want-list pages make the problem explicit: the same vehicle casting can exist in different colors, sets and years, and a collector looking for one particular release does not necessarily need another body that merely looks similar.

Tiny objects require big metadata

One of the site’s strengths is that it leaves the collecting logic visible.

A 1987 want list, for example, does not just say “P-51.” It may need a particular color variation from a particular pack. Other sections separate original and revised castings, generic Hasbro-era designs, special anniversary issues and vehicles from licensed sets.

The NASA and space section alone distinguishes lunar capsules, lunar modules, rovers, shuttle configurations and color variants.

That turns a personal collection into a working identification tool.

The site’s structure also reflects an older Web instinct: if a category becomes complicated, make another HTML page for it. There is a gallery, search form, recent-changes page, want list and long chains of subcategories instead of a single app trying to hide everything behind filters.

Collectors benefit because the URLs themselves become useful references.

The homepage says the collection was last updated in October 2020, so this is not a continuously refreshed database. But as a snapshot of one collector’s effort to identify and photograph thousands of Micro Machines, it remains valuable.

Toy history is full of things that look trivial until two nearly identical objects turn out to have completely different production histories.

M2Museum preserves those differences.

Browse the 6,258-piece Micro Machines reference

Posted on by

Ancient Web: Bjarne Stroustrup’s Homepage Still Explains C++ in His Own Words

Most programming languages eventually accumulate so much secondary explanation that the original designer becomes just another citation.

Visit Bjarne Stroustrup’s homepage

Bjarne Stroustrup’s site avoids that problem. It is still one of the best places to read C++ history from the person who actually designed and implemented the language.

The homepage is almost aggressively straightforward: C++, FAQ, technical FAQ, publications, WG21 papers, books, interviews, videos, compiler links and biographical material. It behaves more like a researcher’s desk than a marketing site.

That matters because the FAQ contains details that are usually flattened into trivia elsewhere.

Stroustrup says he began work on what became C++ in 1979 under the name “C with Classes.” The first version called C++ was used internally at AT&T in 1983, and the first commercial implementation arrived in 1985 alongside the first edition of The C++ Programming Language.

He also explains why C compatibility mattered. The goal was not to bolt object-oriented syntax onto C for fashion. He wanted the performance and systems-programming flexibility of C while gaining stronger abstraction tools, and he was working down the hall from people such as Dennis Ritchie, Brian Kernighan and other Bell Labs researchers.

The FAQ is historical evidence

The site’s best feature may be that it preserves arguments programmers have been having for decades.

Why is C++ so large? Why is it compatible with C? Is there such a thing as “C/C++”? Why didn’t it start as a pure object-oriented language? What was the first compiler written in?

Stroustrup answers these in his own voice, including the occasional irritation that comes from having the same misconception repeated for thirty years.

The site also links directly to his papers on C++ from 1979 through later standardization work, along with material on C++11, coding guidelines and the evolution of the language.

That is unusually valuable for software history. Technical history often gets rewritten through product documentation, tutorials and retrospective blog posts. Here, the designer’s explanations remain connected to the actual language evolution and the papers behind it.

The layout has changed less than the language.

Good.

For researchers, programmers and anyone trying to understand why C++ looks the way it does, a direct answer from the person who made the tradeoffs beats another summary written forty years later.

Explore Stroustrup’s C++ history, FAQs and papers

Posted on by

Ancient Web: Molossia Built a Navy in the Desert and Documented Every Voyage

The Republic of Molossia is landlocked in Nevada, which naturally means it has a navy.

Visit the Molossian Navy

The site explains the logic itself. Molossia tried having an army, then an air force, but the air force’s plane did not fly and was apparently too small to fit anyone inside. The solution was obvious: create a navy in the desert.

What makes the page worth preserving is not the joke alone. It is the commitment.

The Molossian Navy has vessels, missions, officers, monuments and a long list of expeditions to western lakes and reservoirs. The archive includes voyages to Lake Tahoe, Donner Lake, Cave Rock, Emerald Bay, Monterey Bay and various wonderfully overpromoted destinations such as the Mysterious Island and Rocket Island.

There are also pages for a diving bell, an unmanned surface vehicle and other homemade maritime hardware.

The bureaucracy is part of the art

Micronations work best when nobody breaks character.

Molossia’s naval pages apply the language of state institutions to small boats, inland expeditions and recreational engineering projects. A lake outing becomes a naval mission. A homemade vessel becomes part of a fleet. A trip report becomes an official record.

The humor lands because the site documents everything with a straight face.

It is also a very old-Web kind of project. Instead of compressing the joke into a viral post, the creators kept expanding the world over years through linked pages, photographs, mission reports and invented institutions.

That accumulated structure is what gives the site texture.

The navigation lists voyage after voyage: a coastal study, a mission under the ice, a trip across a border, a journey through a lagoon, joint operations with another micronation and repeated expeditions around Lake Tahoe.

There is even a monument to the navy.

This is not efficient content production.

It is much better than that.

It is a private mythology maintained long enough to become Internet history.

The Ancient Web corpus contains plenty of serious museums, technical archives and scholarly references. Molossia earns its place for a different reason: the old Web also gave people room to build absurd little countries and then spend years documenting their imaginary institutions as if the paperwork mattered.

Sometimes the paperwork is the point.

Explore the Molossian Navy archive