You’ve probably noticed that the modern internet feels less like a frontier and more like a digital feudal state. You don’t own your space; you rent it from the lords of AWS, Discord, and Substack.
The internet you were promised—where you could share, host, and connect directly—was quietly taken away by a port-mapping hack.
We love to blame Big Tech’s predatory business models for this centralization. We point fingers at greedy VCs and algorithmic monopolies. But the real original sin wasn’t Zuckerberg or Bezos. It was a 1990s networking compromise called NAT.
Before NAT (Network Address Translation), the internet was end-to-end. Every device had a real, public address. You could plug a computer into the wall, and it was a peer on the network. You could host a website, share files, and run a server directly from your bedroom.
Then, we panicked about running out of IP addresses. Instead of fixing the architecture, we slapped a band-aid on it. NAT allowed your router to hide all your devices behind a single public IP. It was normalized as a security feature—your devices are hidden from the bad guys!
NAT didn’t just hide your IP address; it turned your computer into a read-only client, structurally guaranteeing your dependence on cloud platforms.
A shield is also a cage. If the outside world cannot initiate a connection to your device, you cannot host anything. You cannot share directly. You must route your traffic through an intermediary—a centralized server that actually has the privilege of being reachable.
They sold us a shield, but they built a cage. By hiding us from the network, they made us permanently dependent on the gatekeepers.
The commenters mourning this loss are right: before NAT, sharing was easy, but anyone could get hacked. NAT felt like a necessary evil. But we didn’t just adopt a security measure; we abandoned the end-to-end principle. We accepted that consumers should be second-class citizens on the web.
Some think IPv6 will save us. It won’t. IPv6 solves the address exhaustion, but it doesn’t reverse the mindset. Reverse proxies and cloudfronts recreate the exact same asymmetry. The industry has already adapted to a world where you are a renter, not an owner.
If you care about self-hosting, privacy, or independent communities, you are fighting an invisible architectural wall. You aren’t just fighting business models; you are fighting the physical structure of the network.
True independence isn’t just encrypting your traffic; it’s reclaiming your right to be a server, not just a client.
FAQ
Q: Isn't NAT necessary to keep my home network secure from hackers?
A: No, that's a myth. NAT is not a firewall. Stateful firewalls can protect directly-addressed devices just fine. NAT just breaks the end-to-end principle under the guise of security, forcing you to rely on intermediaries to host anything.
Q: What does this mean for me practically today?
A: It means you are structurally forced to rent space from AWS, Discord, or Substack to be seen online. You can't easily self-host without jumping through hoops like reverse proxies, which just recreates the exact same centralized dependency.
Q: Will switching to IPv6 fix this?
A: Not on its own. While IPv6 solves the address shortage, the industry has already adapted to the NAT mindset. Cloud providers and reverse proxies still enforce the client-server asymmetry, keeping you locked into their platforms even when addresses are abundant.