The Lost Art of Internet Protocols
This post was written in early 2012, when the internet landscape was quite different. At the time, websites were becoming increasingly bloated with Flash content and heavy JavaScript, mobile responsiveness was still a major challenge, and SOPA/PIPA legislation threatened internet freedom. Social media was dominated by Facebook and Twitter, and "Web 2.0" was still a meaningful term.
Since then, many of the author's concerns proved prescient. We've seen the rise of platform monopolization, continued protocol stagnation despite technologies like WebRTC and HTTP/2, and growing awareness of how much the modern web's complexity costs users. The recent interest in decentralized protocols (ActivityPub, IPFS, Nostr) and the push for simpler, faster web experiences echoes many arguments made here over a decade ago.
A long time ago, on an operating system far, far away...
It was a period of protocol war.
Raw text connections sent
over the internet had
gained a strong following.
During this time, greater
needs and complexity arose
eventually leading to the
wide adoption of the hyper
text transport protocol
Knowledge of how the web worked
on these lower levels soon
vanished. It is up to you to
learn the old ways and restore
freedom to the internet...
There's something we lost when HTTP became the only game in town. Before the web browser dominated everything, the internet was a diverse ecosystem of protocols, each designed for specific purposes. We had telnet for raw connections, Gopher for clean content delivery, and text-based worlds that fostered creativity in ways the modern web struggles to match.
Understanding these "old ways" isn't just nostalgia. It reveals how much richer the internet could be, and why our current web-centric approach may be holding us back.