There's another idea that just hit me. If a url in the original status text is longer than 10 chars eg.:
Yo, totally check out http://www.google.co.in/search?hl=en&client=firefox-a&rls=org.mozilla:en-US:official&hs=3Sx&ei=tN7GSuSzM4rosQOAkJGABg&sa=X&oi=spell&resnum=0&ct=result&cd=1&q=ZOMGitsCriss&spell=1 It's awesome!!! statusnet should convert it to: Yo, totally check out www.googl… It's awesome!!! Where "www.googl…" links to the long scary URL. Getting smarter, if the links is thisbloghasalongname.wordpress.com/2009/09/09/post.html rendering it as "thisblogh…" will make less sense than making it "http://th…"; This can also be made optional in the "others" settings tab. So, the upsides: 1. You don't have to rely on url circumcising services. Unreliable and DoS friendly. 2. A link will only take upto 10 chars of the notice (please notice that the three dots together make one unicode char. [ellipsis]) 3. You can spare the title attrib of <a> for other awesomer things from the future. 4. You can make the javascript char-count script pick up long URLs and count them as 10 chars allowing the notice to be its fullest :) 5. And for those who use bit.ly for hit counting. Who asked them not to! And the downsides: 1. The plain-text raw content of the post (which is used in the api and other places) will be greater than 140 chars (may be any length!) But there is no way to stop this without resorting to url shorteners. 2. Hmm... Anyone? -- Shashi Gowda identi.ca/g0 _______________________________________________ StatusNet-dev mailing list [email protected] http://lists.status.net/mailman/listinfo/statusnet-dev
