Yeah it's a challenge if we want to serve the code from a short domain name and prefix compressed strings with the domain name and on the client have the path

Yeah it's a challenge if we want to serve the code from a short domain name and prefix compressed strings with the domain name and on the client have the path section automatically decompressed and redirected. Even a 1 letter host at a 2 letter tld like .co .in .ws .tk introduces 7 or 8 for the scheme, one for the slash, and 4 for the host. So a minimum of 14 to put it on a domain. I haven't decided whether to put it on a domain or to use a scheme prefix like zurl: our something else. The other possibility is this if not really about shortest, or Twitter, but more about, transport encoding and an efficient binary format, and something fun. Thanks for commenting! If you have any ideas how to improve the compression or other things, please submit a PR!