Being open source and predictable it would not be necessary to specify any particular shortening service so that part of the URL is extraneous.
Of course there would need to be some chars to refer to which particular open standard shortening encoder was used, still would be shorter than the oringal url for this post.
They could be reliably decoded, preventing the short link rot problem.
As the user could decode the URL themselves it also allows one to preview short link's URLs which can be reassuring and better security and prevent bait and switch shortlink destination changing tactics.
Twitter has created some problems for the internet.
But my initial experiments suggest it's just a little gain. Digits go to 68%, base36 to 90%, and then we also have to add in the prefix to indicate we are switching encodings.
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!
https://news.ycombinator.com/item?id=14245119
If you encode it with this shortener, you get this 35 character string:
mNb:w9iIp7u8di:AKB2xrPUVYUFhfRUWHwA
Assuming you were using this string as a key in a shortening service like this:
https://short.url/mNb:w9iIp7u8di:AKB2xrPUVYUFhfRUWHwA
... you'd end up with a url longer than the original url! So it's not technically a url shortener :)