__/ [ Peter Jensen ] on Tuesday 14 March 2006 16:30 \__
> Roy Schestowitz wrote:
>> ( ugly M$ URL: http://today.reuters.com/sponsoredby/amex/article.aspx ...
>> ?type=innovationNews&storyID=2006-03-13T184438Z_01_L104 ...
>> 36201_RTRUKOC_0_US-MEDIA-FRANCE-COPYRIGHTS.xml )
> Sorry to bring this off-topic, but I have a comment about the way you
> post long URLs. First, why not just all of it on one line? Surely that
> is not breaking with netiquette, and I know of no news-reader that will
> stop it (though some may complain). Second, if you must break, could
> you perhaps do it without adding the space and dots at the end? A
> regular broken-line URL can just be piped through 'tr -d \\n; echo' to
> make it look nice. Not so for those lines. I know that you also
> provide short-link versions, but I prefer not to use those for a variety
> of reasons.
You're quite right. There are arguments that go in both direction, but I'll
take your preferred approach from now on.
They are long essay that explain why long URL's should be avoided by Web
sites. I think a good example of short URL's is the BBC. It gives context
(section) while avoiding mysterious, excessively-long addresses that say
plenty about the underlying CMS rather than the story.
Roy S. Schestowitz | "These characters were randomly picked"
http://Schestowitz.com | SuSE Linux ¦ PGP-Key: 0x74572E8E
5:30pm up 6 days 10:07, 7 users, load average: 0.81, 0.78, 0.43
http://iuron.com - help build a non-profit search engine