NOTE: use Perl; is on undef hiatus. You can read content, but you can't post it. More info will be forthcoming forthcomingly.
All the Perl that's Practical to Extract and Report
I pour myself a cup of strong coffee. :-)
-- Jarkko Hietaniemi
Stories, comments, journals, and other submissions on use Perl; are Copyright 1998-2006, their respective owners.
This xrl.us business just doesn't have a future (Score:1)
* will eventually break (see xrl.us TOS)
* are another point of failure anyway
* are a privacy liability
* give no hint at destination (ph1sh, much?)
* contain no identifying information, so when they do expire, you're totally hosed
* are not a permanent, unique identifier
Besides, there's no actual rationale for using them here. URLs can be as long as you wish in this medium.
Re:This xrl.us business just doesn't have a future (Score:2)
We haven't actually ever deleted any URLs, and when we do we'll make sure that the expiration logic doesn't expire any of the links used in the summaries. Likely then the web crawlers will keep them "in use" for us.
> are another point of failure anyway
The reason we made the service in the first place was so the Perl community would have one that'd be as dependable (or not
> are a privacy liability
That's sorta goofy. If you feel that way then you should probably unsubscribe from the perl.org lists, disable your cpan.org email address and not use any of the perl.org sites we host anymore. (The httpd running Metamark is on the same server as www.perl.org and many other sites).
(I should add a note to http://metamark.net/about [metamark.net] on our privacy policy though...)
- ask
-- ask bjoern hansen [askbjoernhansen.com], !try; do();
Reply to This
Parent
Re:This xrl.us business just doesn't have a future (Score:2)
- ask
-- ask bjoern hansen [askbjoernhansen.com], !try; do();