@rappidjs about redirects to non-gh-pages

[indus]

the GitHub Pages approach works like a "double-opt-in" contract. Let me explain: I actively add a CNAME to the host of js.org to forward a request like foo.js.org to foo.github.io. And the owner of the foo GitHub page actively adds a CNAME file to his repo to make GitHub pick up the request and maps it to foo.github.io. If the owner decides to cancel this "contract" at any time he just has to delete/changes the CNAME, the chain brakes and the forwarding stops, or results in a 404 to be exact (thats an important aspect for me; and I will explain in a second why)

What you want is a normal redirect from foo.js.org to foojs.com. I could set this up and it would work. But what happens if you want to quit this. You have to contact me (you probably live in a different timezone then me (MEZ)), I have to verify that you are the person in charge to file such a cancelation, and I have to actually do it.

Now imagine: I´m in holidays, you sold your domain to someone else. The new owner doesn´t like the forwarding and wants to stop it. He can´t contact me, and even if, I wont be able to verify he is authorized to request a deletion of the forwarding. I´m back from my holidays and face a lawsuit.

So I feel more comfortable with GitHub Pages.

Also I don´t think you would use foo.js.org but stick to foojs.com. And I totally understand this (all kind of links, browserbookmarks, known and trusted by revisiting users). In my conception it is not a goal of JS.ORG to give everyone a nice secondary domain but to put unfunded open source projects with a lack of a good primary domain on an equal footing with esteblished ones. That and to start collaborative pages to generic JS topics (pages like learn.js.org, docs.js.org, es2015.js.org, news.js.org) in the long term.

But I´m open for a disscussion - on both topics: the binding to GitHub and the perspective of JS.ORG.

[it-ony]

Thanks @indus for the good explanation. You're right, your domain is fancy and for me with the existing domain it would be just a 2nd domain which I would redirect.

I think with the CNAME itself it won't be an legal issue at any time. So if you would create a CNAME for foo.js.org pointing to foojs.com, it's just the domain name to ip resolutions. E.g. lookup foo.js.org -> CNAME to foojs.com -> lookup foojs.com - ... -> resulting finally in the IP address.

Then the browser is sending a request to the IP with the http header Host: foo.js.org. The web server at the end of the IP can decided based on the host header if it delivers a web page, do a redirect or just respond with a 404 or do not even respond.

In my conception it is not a goal of JS.ORG to give everyone a nice secondary domain but to put unfunded open source projects with a lack of a good primary domain on an equal footing with esteblished ones.

I like. Keep it like this and maybe make it the rule for getting such a domain.

[indus]

Ich hab gesehen, dass du Mitglied bei leipzigjs bist. Genau für solche user groups kann JS.ORG ne gute Option sein.