Joshua Juran <[EMAIL PROTECTED]> writes: > On Sep 23, 2005, at 3:47 AM, Leopold Toetsch wrote: > >> On Sep 23, 2005, at 7:51, Ross McFarland wrote: >> >>> i was planning on playing around with gtk+ bindings and parrot and went >>> about looking around for the work that had already been done and didn't turn >>> anything up. if anyone knows where i can find it or who i should talk to i >>> would appreciate that info as well. >> >> Google for "NCI gtk". There is also a weekly summary entry but the xrl.us >> shortcut seems to have expired. > > I was wondering about that. I Googled for "tinyurl considered harmful" and > was > surprised to find only one message, discussing the phishing risks. I found no > mention of the risk of outsourcing a bottleneck to a third party who has zero > obligation or direct interest to continue providing the service. > > From <http://metamark.net/about#expire>: > >> Do Metamark links expire? >> >> The Metamark urls expire after five years or two years after the last usage - >> whichever comes later. However, if a link is never used, it will expire after >> two years. This should mean that as long as a link is on a public page, some >> search engine will visit it and keep it alive. >> >> Of course, this is subject to change and is no promise but just my intentions >> as of this writing. If you want guarantees you can make your own service. > > To be quite frank, I'm astonished the practice exists here in the first place. > In my opinion it goes directly against the spirit of the Web envisioned by Tim > Berners-Lee. A better practice would be to post long URL's within angled > brackets. And there's no reason you can't do both, either.
Which is why the archived summaries at deve.perl.org and perl.com all use the long form URLs. The metamarked URLs only ever appear as a convenience for readers on the mailing list. I am not about to start polluting my mailed summaries with such monstrosities as <http://groups.google.com/[EMAIL PROTECTED]> any time soon. You're welcome to write your own summaries that do use the full URLs of course. Or, if it bothers you that much, write something to run from cron once a month or so that grabs shortened summary URLs and does a simple GET on them. -- Piers Cawley <[EMAIL PROTECTED]> http://www.bofh.org.uk/
