Primary Domain
Internet Infrastructure
Within the Primary Domain facet, Internet Infrastructure intelligence groups reporting by primary domain so readers can follow a focused area of internet infrastructure, governance, connectivity markets, or digital capital. The page brings together related articles, public evidence, institutions, companies, people, regional exposure, operating dependencies, and market context that may otherwise sit across separate category pages. It explains the domain, the likely actor class, the market or governance context, and the source material readers should use when comparing signals. Operators, analysts, and governance readers can see how the same domain appears across events, profiles, market shifts, public-source evidence, regional dependencies, and longer-cycle infrastructure decisions over time.

History
Congratulations, Your Spam Has Reached a Very Interested Inbox
Project Honey Pot opened to volunteers in 2004 with a small trick: show a crawler an address nobody else had seen, then wait for the mail to explain where it had been.

History
The Blue Blob Would Like a Word With the Astronomers
Galaxy Zoo asked volunteers to sort galaxies. In 2007, Hanny van Arkel used its forum to ask about something beside one—and gave the researchers a new observing problem.

History
The HTML Tag Applied for a Job. The Browser Put It to Work.
For years, a web page could invent a tag name and the browser would politely carry it around like an employee badge with no employee attached. Custom Elements gave that badge a job description. An author registers a definition; the browser can upgrade matching elements and call…

History
The Library’s Backup Plan Was an Old PC
In 1999, LOCKSS began testing a way for libraries to keep electronic journals in their own care. Its machines checked one another’s copies; somebody still had to check the plug.

History
The Page Changed a Node. The Browser Delivered the Mail.
A busy page changes its mind constantly. It adds a card, removes a button, edits a label, then does it all again before the reader has blinked. Old mutation events treated every adjustment like a doorbell. Mutation Observer offered the page a mailroom: choose which changes…

History
Going Away? Ask Someone to Water Your Website.
Telegarden put a living plot within reach of a web browser in 1995. The robot handled distance; the gardeners still had to arrange holiday cover.

History
The Sidebar Moved. The Widget Asked for a Tape Measure.
A page can stay exactly the same width while a widget gets squeezed half to death. A sidebar opens, a grid column narrows, a caption grows. The window has nothing interesting to report; the little card in the middle needs to know whether its own frame still fits. Resize Observer…

History
Your Signature Could Go to Saturn. Your Email Could Not.
Cassini's 1996 invitation promised a digital souvenir in deep space. The first leg of the journey required a postcard, a stamp and people willing to scan the mail.

History
The Widget Built a Room. The Page Kept Bringing Guests.
Every reusable widget wants a room of its own. Its buttons should keep their shape when the rest of the page changes coats; the page should still be able to bring a headline, a portrait or a link to the party. Shadow DOM gave the widget a separate tree and then made everyone…

History
The Comments Box Was the Wrong Desk
Open WorldCat helped people find library holdings on the web. In 2005, it gave their follow-up questions a better destination than the feedback form.

Story
RIPE’s New IP Family Tree Has One Useful Rule: Odd Is Not Broken
An address hierarchy can look untidy for perfectly ordinary reasons. RIPE NCC’s new resource checks are most useful when they show what they found before announcing what an operator should fix.

History
You Could Type ‘Six-Dan.’ Then the Server Changed the Rules.
In 1993, the Internet Go Server gave many self-declared high ranks a brisk edit. A number beside a player's name was becoming somebody else's responsibility.

History
Two Tabs Wanted the Same Job. The Browser Issued One Ticket.
Open the same web app twice and the two tabs may become colleagues who never met. Both see a document to save, a cache to tidy, or a queue to synchronize. Without a shared turnstile, each can begin a job whose other half assumes it is alone. The Web Locks API gave cooperating…

History
The Exam Was on Monday. MIT Still Had Boxes to Unpack.
MIT put course materials on the web for free. Behind the generous promise sat a publishing crew, a pile of mixed formats and one student in a considerable hurry.

History
The Page Yelled ‘Urgent.’ The Browser Kept the Queue.
Every page has a favorite child: the image it wants you to see first, the script it cannot live without, the decorative flourish it could survive without until Tuesday. The browser sees a pile of requests and a finite connection. The history of priority hints is the history of a…

History
Your PC Did the Homework. The Server Had Called In Sick.
Folding@home recruited volunteers to lend their computers to science. Accepting the finished work required a less glamorous invention: somewhere else to hand it in.

Leaders
Stephen Suess Mapped Local Routes. Fifty Probes Got the Spotlight.
A map can make the Internet look wonderfully tidy. Stephen Suess’s Region Meshes offers a more interesting story: RIPE Atlas measures a whole region’s public probes, then picks up to 50 of them for the richly annotated picture. The view is useful because somebody chose what fits…

History
The Browser Reserved a Table Before It Knew the Order.
A page knew the next server it would need, but not which file it would ask for. Waiting until the order was settled would make the browser do name lookup and connection setup just as the guest was ready to eat. `preconnect` let the page suggest an earlier appointment. The browser…

History
The Download Button Had a Scanning Bill
EThOS put British doctoral theses on the web. Behind the promise of instant access stood a less glamorous question: who would pay to turn the next heavy volume into a file?

History
The Other Site Had Data. The Browser Wanted an Invitation.
The weather page wanted a neighbor's data. The neighbor was happy to share with some callers, wary of others and entirely uninterested in explaining itself to every script on the street. CORS turned that choice into response headers the browser could check before handing the data…
