INTELLEGIXNEWS ▶ Reels

Get news alerts

A notification when a new edition publishes.

Open Protocols, Digital Infrastructure, and the Web's Persistent Builders

Ask about this with Perplexity AI-written from the broadcast
▶ The reel · AI-generated from this story · watch full screen ↗
How this was made Verified AI

Every Intellegix briefing is generated from that day's broadcast and run through automated checks before it publishes — with a human paged on any flag. Here is the trail for this edition.

Sources 12 sources traced for this edition Traced
Guardrail Every figure and proper name traced back to the broadcast Pass
Fact-check 3 confirmed · 3 checked against live web sources Verified
Human loop Operator paged on every flag before publish On
A laptop screen displaying lines of open-source code in a darkened workspace.
Photo: kuszapro · pixabay

XMPP, the open messaging protocol originally known as Jabber, turned twenty-five this month, and primary developer Daniel Gultsch marked the occasion with a reflective essay on what the protocol got right, what it got wrong, and why it persists. The history is a cautionary study in the limits of technical merit: XMPP underpinned most major instant messaging services in 2003, including early Google Talk, but was progressively abandoned by Google, Facebook, and others over the following decade as WhatsApp, iMessage, and Telegram captured users through superior client experience and multi-device synchronization. A Nostr thread appearing in the same day's Hacker News lineup frames that protocol as attempting to learn from XMPP's trajectory — combining cryptographically verifiable identity with a relay network no single entity controls — while avoiding the centralization failure mode that eventually swallowed XMPP's user base.

The structural problem both protocols face is identical: open standards lose to network effects when users cannot be persuaded to switch simultaneously. Potential remedies include regulatory interoperability mandates — such as those beginning to emerge from the EU's Digital Markets Act — or a precipitating event that compels mass migration. Neither is reliably engineered in advance.

On the infrastructure side, developer Thijs published an interactive 3D model of San Francisco built from publicly available GIS data, building footprints, elevation models, and street-level information, accessible via browser at sf.thijs.gg. The engineering challenge is in the data pipeline: transforming a city's heterogeneous and voluminous GIS records into a performant web-based 3D experience required tiling, level-of-detail management, and texture compression across a toolchain described in the Hacker News thread as almost entirely open source and browser-native.

Walgit, a Git server that operates as a single binary backed by S3-compatible object storage, drew amused attention partly because its creator is Tobias Lütke, CEO of Shopify — an unusual Show HN contributor. The design is architecturally elegant: Git's internal data model is already content-addressed and object-based, making object storage a natural fit. Meanwhile, the seL4 formally verified microkernel reached a decade-in-the-making milestone with the completion of its full security proof on AArch64 — the 64-bit ARM architecture running most mobile devices, ARM servers, and Apple Silicon machines. Formal verification proves that every aspect of the kernel's behavior has been mathematically demonstrated correct within the proof's stated assumptions, eliminating an entire class of kernel-level exploits by construction, even if device drivers and user-space software remain outside the proof's scope.

▶ Listen to this story