in reply to Warn people who have perlmonks in a URL?

With the .com, .net, and .org, this can be annoying. I did notice that most sections (but not all) had the "standard set" of reminder links to where to post, the approved tags, how to link (which has a link to the linking shortcuts), and display escape characters and code, but that the initial reply form does not (the preview, however, does). Do you think it would be best to do it in the initial preview, or perhaps maybe on submit, sending them instead to the preview if present with the explanation? (Incidentally, most of the times I see this actually seem to occur in the CB, but that appears to be my limited experience, however.)

And, out of curiousity, are there ever valid times to send them to such a link?

Actually, I may have found an answer to the last of my questions as I was composing this, since I found it very difficult to link to an anchor (#wheredoipost, #linking, and $code) via id shortcut (id:9953) for a node (Site How To) that comes back with a large number of search results when I tried to use "site how to;#anchor" or "id://9953#anchor".

  • Comment on Re: Warn people who have perlmonks in a URL?

Replies are listed 'Best First'.
Re: Re: Warn people who have perlmonks in a URL?
by bart (Canon) on Nov 08, 2003 at 21:13 UTC
    It's not just .com, .org and .net, there's also with or without www. (for example http://perlmonks.org and http://www.perlmonks.org/) and finally, monkads. That makes for 7 different domains total all pointing to the same site, the latter not even at the root — and no two of them can use the same cookie.
[reply]

      If www.perlmonks.org and perlmonks.org cannot share the same cookie, even though one is a CNAME for the other and they are in the same domain, this strikes me as either a browser bug or possibly a design flaw in the cookie specification. Many systems have multiple machine names and yet should be considered the same system. I would understand if they were in different domains (e.g., www.foo.org and cgi.bar.org), but such is not the case.

      However, doesn't Apache have a feature that will fix this, by rewriting the URI to have a certain machine name? (I'm thinking something about canonical names, but my memory is a little hazy on the details.) Or am I confused about that?

      As far as the .com and .net domains... I'd be interested in hearing the reasoning behind why those TLDs don't just do a refresh/redirect to the .org domain. I can sort-of understand the reasoning behind registering perlmonks.com, because of people who get all their ideas about the internet from television (do such people read sites like perlmonks, though?), but I have difficulty believing *anyone* would think perlmonks would belong in the .net TLD, and it seems to me that even given that you want people who type in those domains to get to the right place, a refresh would accomplish that, and still land everyone's URIs in the same TLD, which would have more benefits than just making absolute links work better. What am I missing? 

      $;=sub{$/};@;=map{my($a,$b)=($_,$;);$;=sub{$a.$b->()}}
split//,".rekcah lreP rehtona tsuJ";$\=$ ;->();print$/

      [download]
[reply]
[d/l]
        this strikes me as either a browser bug or possibly a design flaw in the cookie specification.

        It's neither. If anything, it's a bug in the way perlmonks is implemented. Apparently, the cookie sent is dependent on the server requested. It might be better to always send a cookie for the domain instead.

        Note that if you are logged into perlmonks.org and a link takes you to www.perlmonks.org it will work just fine. It's only the other direction that breaks.

        As far as the .com and .net domains... I'd be interested in hearing the reasoning behind why those TLDs don't just do a refresh/redirect to the .org domain.

        That's a good question. I'll be interested in hearing the answer to that as well. I suspect it is an attempt to be friendly to clients that don't handle redirects transparently (or at all.) But, I think redirecting the other domains makes sense.

        -sauoq
"My two cents aren't worth a dime.";
[reply]
        However, doesn't Apache have a feature that will fix this, by rewriting the URI to have a certain machine name?
        That won't help if you don't do tell the client to go to a different URL - it's the user agent which decides which cookies to send along with a request to what host.

        Makeshifts last the longest.

[reply]
Re: Re: Warn people who have perlmonks in a URL?
by BUU (Prior) on Nov 08, 2003 at 20:08 UTC
    What about <a href='/index.pl?node=12345#foo'>my link</a>
[reply]
[d/l]
      That doesn't always work (like when DNS goes whacky). The safest way is something like <a href="?&node=10277">crazyinsomniac</a> => crazyinsomniac

      MJD says "you can't just make shit up and expect the computer to know what you mean, retardo!"
      I run a Win32 PPM repository for perl 5.6.x and 5.8.x -- I take requests (README).
      ** The third rule of perl club is a statement of fact: pod is sexy.

[reply]
[d/l]

In Section Perl Monks Discussion