Profile
Research
Research profile intelligence connects person, company, institution, and other entity coverage for readers comparing the subjects behind BTW.MEDIA reporting. The page helps compare public profiles, related events, evidence packs, role changes, operating footprints, governance exposure, organisational links, and market relevance while keeping organisation and people records distinct from ordinary news chronology. Readers can understand the subject behind the headline, the evidence supporting that profile, and the infrastructure or market relationships that make the profile relevant. They can see who or what the profile represents, which public sources support it, how it connects to companies, markets, governance bodies, or events, and what changes may deserve continued attention as the subject evolves.
History
The Web Learned to Ask: How HTML Forms Turned Pages into Requests
By 1995, HTML could describe controls, collect a user’s chosen values, and direct a browser to submit them to a service. The page named an action and method; the service still decided what the data meant and what to do with it.
History
1,752 Adults, 14 Cabinas: Who Shared Peru’s Internet in 2000?
A 2000 study counted users at fourteen public Internet rooms, not households across Peru. Its figures show how a paid shared session lowered the cost of getting online—and how much the survey could not say about people the rooms never reached.
Story
ASO opens Seat 9 search for full term as Oscar Robles completes vacancy service
The ASO’s 15 September call starts the regular search for a three-year ICANN Board term expected to begin after the 2027 annual meeting. Oscar Robles remains in Seat 9 only to complete the separate term left vacant by Alan Barrett.
History
The 1987 Protocol List Could Classify Standards. Hosts Still Had to Run Them
In May 1987, a short field in a protocol list could say “Required.” That word expressed an Internet-wide expectation for hosts, but it could not install a single line of code. RFC 1011 is revealing because its status labels sit beside implementation comments, dependencies and…
History
The First HTTP Reply Had No Status Line
A browser could receive a complete page and still have no protocol-level answer to a basic question: had the request succeeded? In the Web’s first HTTP implementation, the server returned the document itself, then closed the connection. The body was the reply; the closing socket…
History
FTP Needed a Second Connection. Firewalls Changed Who Called Whom
A file could be requested over one TCP connection and still arrive over another. In 1994, a firewall memo showed that this split made the direction of the second call matter as much as the command that asked for the file.
Story
ARIN asks how a new policy platform would connect to PPML
After a policy-specific survey on Draft Policy ARIN-2026-2, the Advisory Council working group is asking how a possible discussion platform should fit the existing process.
History
How CERN’s Line-Mode Browser Took the Web Beyond the NeXT
The first Web clients did not share one kind of screen. CERN’s NeXT browser/editor offered a graphical workspace; Nicola Pellow’s line-mode browser made the same linked Web readable from terminals that had no windows. Its reach came from a small interface plus the work of…
History
Abilene Used Qwest’s Fiber; Campuses Still Had to Reach It
Abilene’s headline was a national backbone built at a speed universities could not buy off the shelf. Its quieter engineering fact was that a backbone did not connect a campus by itself: regional GigaPoPs, campus circuits and an operations team had to complete the path.
History
Usenet Sent the Duplicate Anyway. NNTP Let a Peer Ask First
Usenet’s 1980s network links did not all work the same way. RFC 977 made a narrow, useful distinction: negotiate article transfers on interactive links, but keep batch-and-discard behavior where a dial-up session made it faster.
History
The PX Record Mapped Addresses, Not Mail: RFC 1664’s Experimental Proposal
An Internet mail gateway needed to translate between two address systems; it did not need DNS to deliver the message. RFC 1664 proposed a way to distribute those mappings, while explicitly leaving SMTP delivery to MX and the gateway.
History
The .nz Handover Happened in 1996. IANA Caught Up in 2004.
The Internet Society of New Zealand took over management of the country’s domain space in 1996. Eight years later, its annual meeting said the IANA database for .nz had only then become correct for the first time since that handover. That mismatch is a history of the record as…
History
RFC 1591 Promised a Binding Review Board. It Was Never Established.
In 1994, the DNS delegation memo gave interested parties a voice and named a panel whose decisions would bind contending sides. Later records say that panel was never created. The distance between a procedure on paper and an institution able to hear a dispute is the story.
History
Tanzania’s .tz Registry Ran Before the Country Had a Full-Time Internet Link
The .tz namespace became operational in 1994 while Tanzania still lacked a full-time Internet connection. The registry could function because domain administration, DNS hosting, mail relay and live IP connectivity were separate layers.
Story
AFRINIC Academy’s Calendar Still Lists a Past Event as Upcoming
In a response dated 13 October, AFRINIC Academy’s events page still placed Botswana’s 6–9 October Deployathon under “Upcoming Events”, while its “Up Next” cards had advanced to later dates. The page records a schedule mismatch; it does not establish what happened at the Botswana…
History
The First IP Link to Tanzania Ran at 9.6 Kbps: CyberTwiga, 1996
A 9.6 kbps path made a new kind of connection operational in Tanzania, but its reach and service envelope were narrower than the phrase “the Internet arrived” suggests. The surviving record separates a working link, a university test and the first visible traceroute.
History
When Experiments Changed, Org Charts Fell Short: CERN’s 1989 Hypertext Proposal
In March 1989, Tim Berners-Lee proposed a way for CERN to keep knowledge about experiments and accelerators from disappearing into disconnected files and institutional memory. The document called its tentative project “Mesh”; the Web’s name and working prototype came later.
Story
RIPE’s RRC07 Archive Shows a Catch-Up, Not a Completeness Proof
Thirty consecutive update-file names now span the interval after RIPE’s last reported RRC07 file, with directory timestamps clustered around the stated resolution. That shows a visible catch-up in the listing; it does not establish that every BGP record was complete or replayed.
History
The Database Was Already There: How SLAC Put SPIRES on the Web, 1991
The first server outside Europe did not introduce the Web to physics. It gave an established literature service a new doorway—and showed how a useful application could make a young medium legible to a specialist community.
Leaders
Ellen Zegura and the Multicast Core That Could Move
When a multicast group’s receivers spread across a network, the router chosen as the group’s shared core can become a poor fit. A 1996 paper coauthored by Ellen Zegura and Michael J. Donahoo treated moving that core as part of the routing problem—and also asked how to measure its…