http://groups.google.com/group/vim_dev/browse_thread/thread/36b81acf60548c20
I pointed out that it is a simple DNS issue, and gave some
examples of Sourceforge sites that have chosen to add an
A record for the domain (vim.org for us) in their DNS.
...
216.34.181.97 vim.org
Turns out you're right, John, though I couldn't find any actual evidence
in your mail or the thread you cited to prove it. :-)
However, this page does prove it:
http://sourceforge.net/apps/trac/sourceforge/wiki/Custom%20VHOSTs
Since SF recommend it, putting an A record for the bare domain must be
OK and not mess up their load balancing or anything (though without
checking their docs, we couldn't have known that; another project's
doing it doesn't make it right).
IMHO, it would be wise to update our config so that it matches SF's
recommendation.
I agree with the DNS admin that people *should* use www. I don't really
think people should use Chrome either, which is where the problem rears
its head because Chrome doesn't automatically add the www for you if it
has a failure. But that doesn't necessarily mean we shouldn't support
it. In fact, IMHO, "I have an opinion" is a pretty poor reason not to do
something, and other good reasons not to do this seem to be vanishing.
Might as well take a few seconds to update the config and help these
guys out.
Ben.
--
You received this message from the "vim_dev" maillist.
Do not top-post! Type your reply below the text you are replying to.
For more information, visit http://www.vim.org/maillist.php
