js-org
Is my semi-redirection use valid?
I run https://code-input-js.org for a JavaScript library/custom element. Understandably, people sometimes expect it to be at https://code-input.js.org. Am I allowed to (potentially manually) redirect from the .js.org to the -js.org? I have full control of the Apache VPS hosting the website and can add a Let's Encrypt TLS-enabled virtual host then noCF-connect it from this repository.
I see that your policy states:
No automatic redirects away from the js.org domain. Redirects must require user interaction.
I see several solutions I would be happy with:
- Automatically redirect to https://code-input-js.org (probably banned)
- Serve the same page to https://code-input.js.org but with less search engine optimisation (potentially even preventing indexing) and with all page links going to https://code-input-js.org.
- Serve a page explaining https://code-input-js.org is the correct website. (I wouldn't like this)
- Serve a clone of https://code-input-js.org with all links leading to https://code-input.js.org. (I wouldn't like this)
Could I do (2), and if not which of the above am I allowed, if any? Thank you for hosting this valuable service!
After a yes from you, I will sort out the pull request.
A page similar to what is served at node.js.org or vue.js.org would likely be best
Every one of your options except #1 is acceptable to me. We prefer not to allow automatic redirects because users might start requesting secondary subdomains for every even slightly related page. This would create a lot of unnecessary work, and JS.ORG would gain nothing from it. Keeping the JS.ORG subdomain visible in the address bar at least provides some promotional value for the project.
Regarding the other options, I agree with Matt that a minimal landing page (like https://vue.js.org or https://node.js.org) works best in my opinion, as it can’t be confused with the actual source of the content (e.g. no one would bookmark the .js.org page). Ultimately, though, the decision is yours.
