All the usual HN nitpicking and obscure edge case discussion should probably be done in the light of ehamberg's own comment: "This is a horrible idea in many ways and was a quick hack for fun." [0]<p>[0] <a href="https://github.com/ehamberg/9m" rel="nofollow">https://github.com/ehamberg/9m</a>
<a href="http://tinyarrows.com/" rel="nofollow">http://tinyarrows.com/</a> has existed for years and is actually shorter, i.e. <a href="http://➡.ws/鷇" rel="nofollow">http://➡.ws/鷇</a>
While this is pretty neat, is there still a market for URL shorteners? It's been mentioned in this discussion already that Twitter does it automatically already - iirc, that was the main use case for shortened URLs. The other use case is gathering statistics (how many people clicked on my link), but the URL doesn't need to be short for that, a simpler redirect service would work just fine for that.<p>The final one is simple printable URLs which people can enter easily. That's also a valid use case I think, but mainly if you can create your own URL, i.e. shorturl.com/hackernews; a random collection of numbers and letters is hard to type in on a cell phone and easy to mistype.
Short URL's have two purposes for me:<p>- They are easier to spell on the phone (This is not.)
- I like to track the clicks (Which I can't do with this.)<p>But, as a proof of concept, this is nice.<p>OT: Oh, I'm turning into a real HNer with this comment.
From the source code README <<a href="https://github.com/ehamberg/9m>" rel="nofollow">https://github.com/ehamberg/9m></a>:<p><i>9m Unicode URL Shortener. Generates a shortcut from <a href="http://9m.no" rel="nofollow">http://9m.no</a> using two unicode characters, e.g. <a href="http://9m.no/പ湛" rel="nofollow">http://9m.no/പ湛</a>.<p>The server will choose two characters at random from the all the printable characters and then cross its finger and hope you use a great font.<p>(This is a horrible idea in many ways and was a quick hack for fun.)</i>
Personally, I think this is awesome. If widely adopted it might to help ferret out all the software which still can't properly handle unicode urls (which is probably why it <i>won't</i> be widely adopted). :)
Back when Gruber tried to do something like that in his @daringfireball Twitter feed, it was so incredibly annoying to have the links fail on all my mobile devices that I set up a Python script to convert the links and re-post them under a @darlingfireball account...<p>He recently posted about that not making sense anymore due to Twitter's URL shortener, but I don't have the link handy offhand.
I got <a href="http://9m.no/𑂜൭" rel="nofollow">http://9m.no/𑂜൭</a> for my daughter's website, but I'm wondering whether this helps shrink character count when used for services like twitter. It's not at all readable, but since it's two (I think) 4-byte unicode characters, will that URL be counted as 13 characters or 21 characters?
<a href="http://9m.no/؞雅" rel="nofollow">http://9m.no/؞雅</a>
⇩
<a href="http://www.google.com" rel="nofollow">http://www.google.com</a><p>Kind of disappointed I got a two character code. Has he used up all the one character ones yet? Time to start a new domain!
Added to Ohloh: <a href="https://www.ohloh.net/p/nine_m" rel="nofollow">https://www.ohloh.net/p/nine_m</a>, or to stay stylistically consistent: <a href="http://9m.no/ꋅ곁" rel="nofollow">http://9m.no/ꋅ곁</a>
I tried shortening a vanity domain of mine, and the asian characters can roughly be translated as "produce fire from the rays of the sun and break wind". I don't think I'll market that shortcut.
Probably should block the same domain from shortening.else you'll get something like <a href="http://9m.no/婀蒾" rel="nofollow">http://9m.no/婀蒾</a> (multiple redirects)