-
Notifications
You must be signed in to change notification settings - Fork 10
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Make vim.org a thing #8
Comments
This has been requested for years: Personally, I think it it better to redirect vim.org to www.vim.org, though. |
Yeah, silly me, I was looking at the closed issues, but hadn't thought of looking at vim/vim. As mentioned in the other issues, for redirection to even work, vim.org should first be able to be resolved, so either an A or a CNAME record is needed for that. In the other issues, it has been answered 'browsers just try out putting www. in front', and time and time again people mention that it is dependent on how a browser has been configured and even show a screenshot where it isn't working, mentioning they have a current version of the browser. In one issue I even see the answer of Bram Moolenaar himself: 'the maintainer of the DNS records says it doesn't work'. Then, respectfully, either the maintainer of the DNS records doesn't know how to do his/her/their job or the hosting or DNS provider is being unwilling to help with setting up something that is pretty easy to set up. I don't know which is more unfortunate. |
I can't remember if this was an issue with the previous vim.org, but it definitely is an issue with the current vim.org, if you ask me.
The website is hosted at www.vim.org. Using that instead of vim.org is of course a matter of taste and apparently www.vim.org has been chosen. However, at least make it so vim.org can also be resolved to an IP address, just like with www.vim.org, and set up a redirection from vim.org to www.vim.org if you're so inclined, but please, don't leave it as it is now where typing in vim.org in the address bar of your web browser leaves you only with a DNS error instead of a website. That is really unhelpful.
The text was updated successfully, but these errors were encountered: