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
The Website Wanted the Whole Screen. The Browser Kept the Exit Door.
A page can be a modest guest in a browser window until its video, game or presentation decides it deserves the entire room. The Fullscreen API gave that ambition an address: an element could ask to fill the display. The awkward question was who owned the door once the lights went…
History
Parliament Changed the Law. The Website Had a Queue.
Britain brought its legal texts together online in 2010. Behind the convenient address stood a less convenient job: finding every amendment, putting it in the right place and keeping up with Parliament's enthusiasm for producing more.
History
The Public Register Lost Its Coin Slot
In 2015, Companies House made more than 170 million digital records free to inspect. The useful part was what happened after the first question: people could keep looking, and software could join in.
Story
ARIN wants a five-year IPv6 plan. The next block still waits on 75%.
ARIN’s draft swaps several utilization tests for a network plan, then makes that same plan the clock on an LIR’s next request. The percentage sounds familiar. Its denominator is new—and the draft leaves one piece of the arithmetic on the table.
History
The Play Button Got a Mixing Desk. The Browser Did the Heavy Lifting.
A play button can start a song. Ask it to make a game explosion fade behind a character, pan a passing car across a room, or shape a note into a new instrument, and the button stares back. W3C's Web Audio API gave web applications a different piece of furniture: a graph of…
History
NOAA’s Chart Website Needed a Map
In 2013, NOAA put about a thousand nautical charts online as free PDFs. The first entrance was a list of chart numbers. Even a mapmaker could leave the visitor looking for directions.
History
The Website Asked for One Photo. The Browser Kept the Filing Cabinet.
A reader picks a photograph to show a web page. The page would like the picture; it has no business browsing the tax returns in the next drawer. W3C's File API gave the browser a way to represent the chosen file and let the page work with its bytes. That small handoff turned the…
History
The Library’s $24.95 Account Came with Homework
In 2008, a Flickr account brought old photographs new names, family memories and an eager audience. Turning that enthusiasm into a better catalogue kept the librarians busy.
History
The Map Wanted Your Location. The Browser Asked You First.
Lost in an unfamiliar city, a traveler opens a map and finds the little blue dot more useful than another heroic guess at the street names. The site would like to know where to place it. In 2008, W3C's first Geolocation API draft described a browser interface for exactly that…
History
The Grant Application Met a Software Bouncer
Grants.gov promised a common front door to federal funding. Between 2006 and 2009, getting through it could depend on the forms software—and on which clock the agency believed.
Story
RIPE’s Abuse Clock Has Three Timers. The Exit Test Changes Halfway Through.
Fourteen days can start the process, seven business days can end the grace period, and RIPE NCC has one working day to lift restrictions. The schedule is crisp. The proposal’s definition of a successful repair changes between the notice and the exit.
History
The Library’s Donate Button Was Generous with the Word “Donor”
An early web fundraiser promoted visitors to donors before the money arrived. The promotion came with a perk: fewer appeals.
History
The Browser Was Late. This Time It Brought an Itemized Bill.
A page that opens slowly can blame the network, the server, the browser, or whatever is least likely to answer back. In 2010, W3C's Navigation Timing draft gave the page a better prop than an excuse: timestamps for the trip from navigation to the load event. By the 2012…
History
The Hidden Tab Kept Checking Mail. Someone Told It to Relax.
A webmail tab that has slipped behind another page can behave like a clerk checking the post every few seconds in an empty office. The 2011 Page Visibility draft gave the browser a way to tell the page that nobody could see it. The page could then slow its checks, pause a game…
History
The Official Time Is Stuck in Traffic
When time.gov brought the clock to the web, even the correct time needed time to arrive. Its engineers put the delivery problem on the page, just below the big digits.
History
The Stock Ticker Lost the Line. It Called Back with a Number.
A live feed has a small social problem: once the line drops, where does the conversation resume? The 2009 Server-Sent Events draft gave the browser a way to remember an event's ID and present it on reconnection. The server still had to decide what came next. That modest division…
History
The Browser Counted Primes. The Button Still Worked.
A page doing heavy arithmetic can develop the manners of a locked door: click all you like, it has decided to finish thinking first. The 2009 Web Workers draft moved that calculation into a parallel script and made the page hear about progress through messages. Its prime-number…
History
NASA Gave Away the Planet. Its Servers Noticed.
World Wind offered a wonderfully unreasonable bargain: install a free program and go exploring. Behind the spinning globe, somebody still had to serve the pictures.
History
Two Tickets, One Cookie. The Browser Needed Better Drawers.
A traveller opens two windows to compare flights. Each window has a different trip in progress, but the site's cookie remembers one booking at a time. Web Storage gave the browser two drawers for that problem: one per window for a live transaction, and one per site for data meant…
History
The Footnotes Wanted Their Luggage
Zotero put a research collection inside the browser. In 2006–2007, making that collection useful meant teaching it to keep the notes, find the attachments and accompany its owner elsewhere.