Rebuilding The Foundation Of The Internet — Why It Matters

The apps change. The foundation of the internet does not. Every browser, every wallet, every call, every image thumbnail still sits on a stack of shared primitives written in C and C++ decades ago — codecs, allocators, parsers, identity libraries, the databases that pretend a data center is the source of truth. Those primitives are load-bearing. When they crack, they crack everywhere at once.

Rebuilding the foundation of the internet means replacing those primitives, not putting a nicer UI on top of them. Remade with Rust is MATA's public program for that work: ground-up rebuilds in a language where whole classes of memory-corruption exploit do not compile. This article is the thesis. The inventory of what already ships lives in The Importance of Remade With Rust and on the Remade with Rust catalog. The reason to care is simpler: Digital Freedom is a story about keys and ownership, and that story is fiction if the libraries underneath still speak C.

Why The Foundation Of The Internet Keeps Failing

Ask a security team where the serious CVEs still come from and you get the same answer, year after year. Buffer overflows. Use-after-free. Out-of-bounds reads in parsers that touch untrusted bytes — a PNG, an H.264 frame, a font, a packet. Microsoft has said for years that roughly seventy percent of the vulnerabilities in their products are memory-safety bugs. Google publishes the same shape of number for Chromium. This is not a talent shortage. It is the cost of a foundation poured in a language that cannot refuse those bugs at compile time.

The NIST Secure Software Development Framework has been pushing organizations toward memory-safe languages for exactly this reason: the defect class does not age out. You can patch FFmpeg forever. You cannot patch "C will let you write past the end of the buffer" out of C. The foundation of the internet is that class of code, reused so widely that a single library CVE is an internet-wide event. One flaw in an image decoder is every OS thumbnail, every chat app, every browser tab.

Trust, Security, and Incentive all fail at that layer. You cannot trust a wallet that links a memory-unsafe codec. You cannot call the stack secure while the allocator silently accepts a double-free. And there is no incentive to migrate if the only alternatives are GPL-encumbered or still FFI into the original C. Rebuilding the foundation of the internet is how those three primitives become properties of the substrate, not slogans in a landing page.

What Rebuilding The Foundation Of The Internet Actually Means

It does not mean rewriting Twitter. It does not mean a new JavaScript framework. It means the boring, shared parts — the internet primitives every product already depends on — get a memory-safe, permissively licensed twin that speaks the same file formats and wire protocols. Drop-in at the boundary. New code underneath.

The Internet Primitives Everyone Already Depends On

A "primitive" here is a library so common you forget it is a decision. JPEG and PNG. H.264 and Opus and AV1. The malloc your process actually uses. The zstd compressor on the wire. The identity token your backend verifies. The database that is supposed to work when the network does not. One vulnerability in any of those is not an app bug. It is a class of apps.

That is why Remade with Rust aims at FFmpeg-class media, at Whisper-class speech, at mimalloc-class allocation, at OAuth-class identity, at Firebase-class data — not at a MATA-only toolkit. The Electronic Frontier Foundation has argued for decades that a free internet needs infrastructure you can inspect, fork, and run without asking permission. Rebuilding the foundation of the internet in the open is that argument with a compiler in the loop.

Memory-Safe Rebuilds, Not Wrappers Around The Old C

A Rust crate that calls libpng over FFI has not rebuilt anything. It has added a typesafe handshake in front of the same heap. The Remade with Rust rule is the opposite: the hot path is Rust. Bounds-checked slices. A borrow checker that makes use-after-free a compile error. When a project must speak to hardware or an existing ABI, that seam is small, reviewed, and not the product.

The payoff is deterministic security posture. You are not hoping the next fuzz run is quiet. You are shipping a program in which that entire CVE class is unrepresentable. That is the same instinct as the Foundation of Trust stack — AES-256-GCM, Argon2id, keys in a secure chip — applied one layer down, to the internet's shared code rather than only to your vault.

Permissive Licenses So The Foundation Stays Free

Copyleft at the bottom of the stack gates who can ship. A startup embedding a media pipeline should not have to choose between a vendor license, GPL obligations, or rolling their own C. MIT, BSD, and Apache-2.0 rebuilds mean any team can embed the same primitives MATA uses, inspect them, and patch them. The IETF has spent decades putting protocols in the open so no one company owns the rails. Permissive memory-safe implementations are how those rails stay open in the decades after the original C libraries become unmaintainable.

Rebuilding the foundation of the internet this way is also an incentive design. If the safer library is slower, proprietary, or legally sharp, nobody moves. If it is faster or matched, permissively licensed, and drop-in, the migration pays for itself. That is the only adoption story that works at internet scale.

Why Rebuilding The Foundation Of The Internet Matters For You

You do not have to compile a codec to be downstream of this. Every time a camera pipeline, a voice note, a login, or a file sync runs on your hardware instead of a vendor cloud, it is running somebody's primitive. The question is whether that primitive is still the C one with the CVE cadence, or a rebuild that can live on a device you hold.

Digital Freedom Sits On That Foundation

Digital Freedom is ownership of finances, identity, passwords, contacts, files, and the home — Trust, Security, Incentive as the scoreboard. None of that holds if "local" still means "we shipped Whisper.cpp and a pile of *-sys crates." A local-first Freedom Guide on a memory-unsafe media stack is a contradiction with extra steps. Rebuilding the foundation of the internet is how the product story and the dependency graph agree.

When OCR is Carmenta on your machine, the document never left. When speech is Mercury, the voice note never boarded a Python runtime in a data center. When identity is a Sovereign ID keypair verified in-process, no OAuth provider gets a log of every login. Those are user-facing outcomes of foundation work, not separate marketing tracks.

Distributed Cloud Instead Of Rented Racks

Centralized cloud is a business model that consolidates storage, compute, and identity into someone else's building and meters your access to your own data. The NIST Zero Trust Architecture already tells operators to stop trusting the network perimeter. Distributed cloud is the architectural version of that advice: encrypt everything, treat every device as a trust boundary, share with capabilities instead of firewall holes.

That architecture is only honest if the database, the identity layer, and the codecs can run at the edge without dragging a C toolchain and a cloud SDK with them. SpaceDB, mID, remade_ffmpeg_rs — the names are in the catalog. The point of rebuilding the foundation of the internet is that those names can exist without a region in us-east-1 pretending to be the source of truth. The Eras of Digital Freedom sequence that from a personal vault out to a home computer; the Rust rebuilds are what make the later eras feel like software instead of a science project.

Where To Go From This Foundation

If you want the program and the repo list, read The Importance of Remade With Rust and browse github.com/remade-with-rust. If you want the product that sits on top, start with Era 1 and the vault — including Friends backup so self-custody is survivable. If you want to watch a single primitive move, pick one catalog card on Remade with Rust and read the README until the claim is a number, not a vibe.

Rebuilding the foundation of the internet is slow on purpose. Shared libraries are slow to replace because everyone already linked the old ones. That is also why the work compounds: one memory-safe JPEG, one memory-safe allocator, one in-process identity verifier, reused by every app that adopts them. The internet you want to own is not an app. It is a stack. The stack is what we are replacing.