Re: New Link Tags

[tommyw]

Sorry for attacking what's obviously an improvement. Obviously the requirement for having the extra destination exists, and this does solve it. But I can't help thinking there's a cleaner solution.

Regarding the kobe:// tag: this means the article's author gets to pick which site the reader goes to. Or they include two tags, and the reader picks one. Either mechanism has its problems.

Instead, would it be possible to store the preferred site in user settings and have the server dynamically expand the cpan:// tag to point to the readers chosen site?

I've no idea whether this is possible, or how hard it would be...

[$code or die]

If you think it's a good idea, then what about changing [google://] to point to your search engine of choice?

It would be a lot more work - extending the database, providing a mechanism for people to choose their search engine through user settings, etc

But far more importantly, it is pointless - why provide a link to something, if the reader might end up somewhere where the content is different? "CPAN" ne "KOBE". While Randy Kobe's site mirrors the modules and metadata, it doesn't mirror the site content - it is presented in a different way. Perhaps if I use the [cpan://] link, I WANT you to go to CPAN, not some other site.

On the other hand, there are a lot of tags now to remember, and these will grow, but it seems meaningless to me to have a link in a Perlmonks post that could lead to a number of different sites.

Simon Flack ($code or die)
$,=reverse'"ro_';s,$,\$,;s,$,lc ref sub{},e;$,
=~y'_"' ';eval"die";print $_,lc substr$@,0,3;

[tommyw]

Ah, based on the description given above, I thought kobe:// was simply a mirror of cpan://, to be used when communications to cpan itself were decided to be too slow.

Ok, in that case, I retract the particular suggestion (although will happily leave it around if anybody does want to implement a similar option