Re: Sorry
Re: Sorry
- Subject: Re: Sorry
- From: Walter Ian Kaye <email@hidden>
- Date: Fri, 2 Jul 2004 17:27:49 -0700
At 12:06a +0100 07/03/2004, Martin Orpen didst inscribe upon an
electronic papyrus:
on 2/7/04 11:35 pm, Dave Balderstone at email@hidden wrote:
> On Jul 2, 2004, at 4:01 PM, Martin Orpen wrote:
>
>> Somebody explain the logic of this position?
>
> Sure. Say you post a URL like:
>
> http://www.somedomain.com/directory1/directory2/
> somefilenameindicator.php
Yeah, thanks for proving my point - it's broken in my mail software.
Actually it was broken when he posted it, but only because he failed
to follow the guidelines in RFC 2396. Here, try this:
<
http://www.somedomain.com/directory1/directory2/somefilenameindicator.php>
Workee in your mail software now?
Perhaps *you* could write a script to fix it?
He just needs to read his RFCs. You might do likewise.
<
ftp://ftp.rfc-editor.org/in-notes/rfc2396.txt>
> If I don't recognize the domain, I have the option of starting at
>
> http://www.somedomain.com
>
> to see what the site appears to be. Then I can make a decision as to
> whether I proceed or not. I can also do a search for domain details,
> find out where it's located, who the admin and technical contacts are,
> etc.
>
> Y'know... information. Metadata.
Yeah, it's the stuff that none of us have time to go through when we're
clicking on links in Google trying to find information quickly.
Google lets you see the URL; TinyURL does not.
While the rest of us are reading the latest information on the web pages
you're still waiting for the results of a whois on the primary domain...
> A tinyurl tells me jacksh*t about where I'm about to go, so I won't go
> there. "I'll give you some candy if you'll get in the car and go for a
> ride with me, little girl..."
>
> Why is that so difficult to understand?
I *do* understand it alright - it's a lame *policy*.
Have you no policies which others might consider lame?
Let he who is without cinnamon cast the first stone.
And what's lame about "better safe than sorry"?
AFAICT, it's been a very respected policy for many years.
>> The ridiculously long URLs generated by many PHP/mySQL solutions are
>> making this sort of redirection a necessity.
>
> Nonsense. Long URLs are trivial to deal with. Why, I bet you could even
> write a script to do it!
Yeah one in PHP that does the same thing that TinyURL does - haven't you
every stopped to think why these services are popular?
These services are lame. If you're going to create an alternate URL,
make it a PERMANENT one, and one that's not mnemonically challenged.
Preferably using your own server/domain.
These services are popular with people that don't share *your* unique powers
to detect redirects by knowledge of every URL on the web
His point was about trusting the domain. Can you trust person X?
Without knowing who X is? Perhaps *you* are the one with unique
powers.
- and by people who find long URLs (like the one you managed to post
in the second sentence) a PITA.
The only PITA is when you have to trim whitespace for a copy/paste,
but software is *supposed* to take care of that. If it doesn't, then
get the software fixed. And vote with your wallet if you think some
PHP/mySQL "solution" is generating needlessly long URLs. And read
your RFCs.
We all have our own preferences. Can't we respect each other's?
-boo
whose browser window width preference is ~500 pixels;
if a site don't fit, it ain't worth readin'.
_______________________________________________
applescript-users mailing list | email@hidden
Help/Unsubscribe/Archives:
http://www.lists.apple.com/mailman/listinfo/applescript-users
Do not post admin requests to the list. They will be ignored.
- Follow-Ups:
- Re: Sorry
- From: Martin Orpen <email@hidden>
- Re: Sorry
- From: Dave Balderstone <email@hidden>
| References: | |
| | >Re: Sorry (From: Martin Orpen <email@hidden>) |