One Small Step Towards Scheme Diversity

(learn about this date format)

According to its most official definition, The World Wide Web (WWW, or simply Web) is an information space in which the items of interest, referred to as resources, are identified by global identifiers called Uniform Resource Identifiers (URI). Web addresses (or URIs as that document prefers to call them) are what truly make the Web stand out. Putting something as flexible as Web addresses at the center of the World Wide Web has made it uncensorable. Every time content at one Web address gets taken down, that same content can be reposted at two new ones. What I’m trying to say is: Web addresses are important. That’s why I’ve been thinking about them.

That same document goes on to say:

In the URI "", the "http" that appears before the colon (":") names a URI scheme. Each URI scheme has a specification that explains the scheme-specific details of how scheme identifiers are allocated and become associated with a resource. The URI syntax is thus a federated and extensible naming system wherein each scheme's specification may further restrict the syntax and semantics of identifiers within that scheme.

— The W3C’s Architecture of the World Wide Web, Volume One, section 2.4. URI Schemes

Today, the most common URI scheme is https. That scheme is very similar to the http URI scheme which was one of the first URI schemes. Those two facts lead me to one conclusion: https probably isn’t the best scheme. Surely someone has come up with something better in the past 30 years.

The question remains though: if https isn’t the best scheme, then which one is? That is a difficult question to answer, and it’s almost certainly a subjective one. Even if https was the best scheme, it’s still a good idea to give it something to compete against. With that in mind, I’ve decided that I want this site to promote scheme diversity. In other words, I want this site to be available under a variety of schemes.

Early on, I made sure that this site supported the file URI scheme. After this site launched, I made it available at Today, I’m proud to announce that the site is now available at

To be clear, FTP is almost certainly inferior to modern HTTPS. In fact, the only browser that I found that still supports it is Pale Moon, a browser that I do not recommend. I’m only really using FTP because I wanted to start with something that is more established and less experimental. In the future I plan to support some more interesting protocols