Were you unable to attend Transform 2022? Check out all of the summit sessions in our on-demand library now! Watch here.
In the beginning, there were protocols…
Rather than write about Web3 again, I want to write about Web1: the 90s. At that time, I used something called Communicator. You can think of it as a suite of internet clients and applications. Of course, it had Navigator, a web browser, but also a messenger for emails, a news client and even a push system. It was a good example of how the early web worked: multiple protocols for different purposes. You may remember FTP, SMTP, Gopher and Archie, but also XMPP and many, many more.
The cool thing about these protocols is that they made the computer you used irrelevant. They abstracted away the underlying operating system and hardware. Similarly, these protocols embraced the Unix philosophy and only focused on one thing to do it well: file sharing, email transmission, push messaging and so forth.
Then, HTTP and HTML won
2. The browser “executes” these to render them as fancy websites and applications.
This meant that other, more specialized protocols could just become applications on top of HTTP and HTML. If you’re using Gmail and sending an email to another person using Gmail, you’re probably not using POP, SMTP or IMAP, but only HTTP and HTML. FTP and XMPP are now known as Megaupload and WhatsApp, for better or worse.
What might surprise you is how hacky HTTP and HTML are. After all, the HTTP spec uses Referer inste …