History of the Internet

Website Moved Its Filing Cabinet. It Sent the Moving Bill to Every Link.

The Website Moved Its Filing Cabinet. It Sent the Moving Bill to Every Link.

A publisher renovates its site. The document is still there, the staff still believe in it, and the new menu looks splendid. The old address now leads nowhere. In a 1998 essay, Tim Berners-Lee treated this familiar renovation as a choice about who does the work. A site can move files, replace software and change departments behind a stable public URI. When it changes the URI instead, every reader, bookmark and distant publisher must rediscover the document. The office got its fresh floor plan; the rest of the Web inherited its missing address.

WebCrawler Had a Robot for Each Query. Pinkerton Kept It Behind the Gate.

The public WebCrawler in 1994 answered questions from a shared index. Brian Pinkerton had built another mode: start with likely results, send a robot down their unexplored links and add whatever it found before answering. That sounds like the perfect cure for a search index with holes. Pinkerton kept it out of public hands. A shared crawl could serve thousands of queries; a fresh crawl for every curious user would ask the young Web to pay the network bill again and again.

OpenStreetMap Shut Off Edits to Give Changes a Name.

In April 2009, OpenStreetMap contributors could not save new edits through the project API while the service moved to version 0.6. The online editor was disabled. When editing returned, every change had to belong to a changeset, and clients had to check which version of a map element they were replacing. A community map paid for a better account of its own making with a conspicuous pause in the act of making it.

Webmention Delivered the Reply. The Other Site Kept the Door.

A blog author could write a reply on her own site and still want it seen beside the article she answered. The old choices made her pick a house: put the comment on someone else's page, or keep the reply at home and hope readers followed the link. Webmention gave the link a messenger. In its 2017 W3C Recommendation, the sending site tells the receiving site where the reply lives. The receiver checks the link and decides what appears on its page. The messenger crossed the street; the front door stayed with the owner.

Site Was Down. Google Had a Copy. Then the Link Vanished.

The Site Was Down. Google Had a Copy. Then the Link Vanished.

For years, a Google result could offer two doors to one page: the publisher's site and a snapshot stored by Google. If the site failed, the snapshot might still open. The publisher could ask Google to remove that copy. In 2024 Google removed the reader-facing cached link itself. A little secondary doorway had exposed a long argument about who controlled a page after it left its own server.

Internet Explorer Made the Reader Click. The Patent Case Was Offscreen.

In 2006, some embedded content in Internet Explorer appeared on the page but waited for a manual activation before a reader could use it. Microsoft connected that change to its Eolas patent case. A legal and engineering decision had acquired a user interface: click, or use the keyboard, and only then interact. Two years later another Microsoft update removed the extra step.

Creative Commons Made Licenses Machine-Readable. Then It Hid the Label in a Comment.

On 16 December 2002, Creative Commons launched licenses that could speak to three audiences: a human reader, a lawyer and a machine. The machine was supposed to find works offered for reuse without making every person negotiate permission from scratch. The first recommended web markup carried RDF/XML inside an HTML comment. Six years later, Creative Commons' own ccREL paper called that choice cumbersome and replaced the recommendation. The legal permission was only one part of the work. A machine also had to find the label attached to the right object.

Web SQL Had Two Implementations. They Shared One Engine.

The Web SQL Database draft offered web apps a local database and a familiar query language. By 2010, the W3C had two implementations to point at. Both depended on SQLite. That made the standardization test almost comic: two browsers could agree because they were asking the same engine, while the rule they were supposed to implement independently remained unwritten.

CSS Zen Garden Locked the HTML. Designers Made the Same Page Fight Itself.

In 2003, the case for CSS had a sales problem. A stylesheet could separate a page's appearance from its markup, but clients and designers still saw late-1990s table layouts as the practical route to an interesting site. Dave Shea offered a sharper argument: everyone could design the same page, provided nobody touched its HTML. CSS Zen Garden turned a standard's promise into a public contest of visible results. The restriction gave designers room to show their craft, and gave the keeper of the common page control over the field they had to play on.

Persona Left Sites the Email Address. Then Its Verifier Went Dark.

Mozilla Persona promised websites a login without collecting another password. It deliberately gave them the user's email address, a useful account key. When Mozilla retired its hosted service in 2016, that key remained on the website. The machinery that proved the visitor owned it had an end date.

An IRC Bot Needed One Exchange Rate. curl Became a Library.

In late 1996, Daniel Stenberg wanted a bot in an IRC channel to answer currency questions. The rates were already on the web. The missing piece was a small program that could fetch them without a person opening a browser. He found Rafael Sagula's HttpGet and started changing it. Four years later, that narrow errand had become curl and then libcurl: a transfer engine other programs could call. The names changed as the job outgrew each one.

Google Wave Invited the Room Before It Built the Exit

In September 2009, Google prepared more than 100,000 invitations to Wave, its live conversation and document editor. The same announcement admitted a host could not yet remove a participant or configure editing permissions. The invitation was a finished product. The exit was still on the work list.

`scp` Command Kept Its Name. OpenSSH Replaced the Machinery.

The `scp` Command Kept Its Name. OpenSSH Replaced the Machinery.

For years, `scp` looked like the simplest way to move a file across an SSH connection. The command was familiar; the old SCP/RCP transfer protocol beneath it asked a remote shell to expand wildcards and made some filenames a quoting puzzle. In April 2022, OpenSSH 9.0 kept the command and changed its default engine to SFTP. The same parcel counter opened onto a different conveyor. Old servers and old scripts made the switch less tidy than a release-note headline.

Google Built an Offline Web. Then Reader Lost Its Offline Switch.

Gears gave a web app its own local database and kept stories available when the network went away. Google Reader was the launch example. Three years later, the Reader team removed offline access while Gears was still alive. A year after that, Chrome removed Gears itself. The pieces of the technology moved into browsers; the reader's feature did not travel with them.

Git Chose SHA-256. Its Repositories Still Could Not Shake Hands.

Git's object names look like labels pasted onto a filing cabinet. They are closer to the bolts holding the cabinet together. A tree names its contents; a commit names a tree and its parents. Change the hash used for those names and the references inside the objects change too. Git chose SHA-256 in a 2018 transition design, but its 2026 manual still says repositories using the two object formats cannot interoperate. The cryptographic decision was the short meeting. Moving a connected history was the long job.

FCC Gave AOL Three Exits. The One Without Interoperability Opened in 2003.

The FCC Gave AOL Three Exits. The One Without Interoperability Opened in 2003.

A merger condition put a gate between AOL Time Warner and a particular kind of video messaging. The company could build an interoperable presence system, sign agreements to connect rival systems, or persuade regulators that the market had changed. It chose the third route. The bridge between messaging networks stayed on the drawing board while the gate came down.

rsync Asked the Receiver What It Already Had. The Slow Link Got a Break.

In 1996, Andrew Tridgell and Paul Mackerras described a file update problem with two machines and a slow link. One held the new file; the other held an older, similar copy. Sending the new file whole was the obvious move and often the expensive one. Their algorithm made the receiving machine send a compact map of the blocks it already owned. The sender then shipped references to those blocks and only the missing bytes. The bandwidth bill shrank; the computers took on the work.

Ticketmaster Fought a Link to Its Own Checkout. The Copyright Claim Fell.

A buyer looking for one concert did not need to tour a ticket seller’s home page first. Tickets.com could show the event, then send the buyer straight to Ticketmaster’s event page when Ticketmaster held the sale. Ticketmaster took that shortcut to court. Its filings trace four years of attempts to make the route itself part of its control over ticketing.

OpenTelemetry Merged Two Projects. Four Years Later, One Still Needed a Retirement Plan.

In May 2019, the leaders of OpenTracing and OpenCensus agreed to join their instrumentation projects as OpenTelemetry. They called the existence of two similar projects the biggest problem. They also wanted the old code in read-only mode before year-end. By May 2023, OpenTelemetry was still publishing a specific OpenCensus exit plan, complete with bridge libraries, a July archive date and an exception for Python. A merger can settle where new work belongs. It does not pull old libraries out of running services.

Wikipedia Moved the Pages. Their Old Edits Missed the Train.

On 25 January 2002, English Wikipedia switched from files to a PHP and MySQL system built for the project. The encyclopedia kept its current pages. The converter carried each page’s latest version, leaving much of its earlier editing trail for a different job. Eight years later, an old backup would reveal that some of the trail had been waiting in logs all along.