js-org / js.org Goto Github PK

Hey, I noticed a potential typo on line 171 of cnames_restricted.js https://github.com/js-org/dns.js.org/blob/master/cnames_restricted.js#L171

Should that be professional(s) instead of rofessional(s)?

I've just added my CNAME file and issued a pull request. Soon after that I received a mail from [email protected] with the following content:

The page build completed successfully, but returned the following warning:

Your site's DNS settings are using a custom subdomain, my-repo.js.org, that's not set up with an correct CNAME record. We recommend you set this CNAME record to point at my-user.github.io. Instructions on configuring a subdomain for use with GitHub Pages can be found at: https://help.github.com/articles/setting-up-a-custom-domain-with-github-pages/

I've just followed the instructions. In case this is a normal warning, it would be nice to add it to the wiki pages.

Hi! I'm writing on behalf of the Adelaide JavaScript community. We meet up every couple of months to discuss all things JavaScript, mostly front-end JS frameworks.

We're looking to set up a forum so that we can continue discussion of ideas between meetups and distribute resources more effectively. I'm wondering if this kind of thing is within the scope of JS.ORG subdomains? We would love to be able to use adelaide.js.org.

If it is acceptable, would it be possible to configure dns.js.org directly with the IP address of the server we host on? Otherwise we have adelaidejs.com so we can go through that if necessary.

/cc @rahult

reference #6

@scottcorgan Surge.sh would be ok for me. As I understand this they have a similar system where a CNAME file in the folder is necessary to make the forwarding work. I like the idea that you as the owner can end the "contract" at any time (and that the existance of a CNAME autorizes you as the owner in the first place; see: #94)

Everything else would stay as stated in the ToS; e.g. "Communication (if necessary) over GitHub" (So you would need to keep your GitHub account as long as you use the service).
Your request would get handled the same as others; e.g. no subdomains for pages without reasonable content and a minimum of correspondence between your requested subdomain and the content you provide would be necessary (both to prevent excessive name grabbing):

fantastic.js.org for <h1>Hello World</h1> is something I would reject,
but scott.js.org for your personal blog would be fine.

We can discuss this ahead or when you have set up your page.

I am having an issue accessing my website (https://timothyle.github.io/) which keeps redirecting to https://timothyle.js.org/

I have decided that I will stay with the github domain; however, now my website cannot be accessed at all. I tried to delete the CNAME files from my master and gh-pages branches but there is still an issue with accessing my website.

How can I stop the JS address and revert back to my github address?

Is aplyer.js.org link to diygod.github.io/APlayer/demo possible?

When you have opted-in for Cloudflares "Universal SSL" or you didn´t opted out after it became default serving you Site now enforces SSL. (all other subdomains shouldn´t see changes)

I realy hope this doesn´t break someones page - but there is the chance that some pages will see a mixed content warning or something similar. I think it is better to make this step now and not to wait any longer.

FYI: webpack/webpack.js.org#124

I was reading this page, and looking at the instructions, it wasn't really clear to me what was a link and what wasn't. It took me a bit of moving my mouse around until I realized that "here" was a link (since it changed color on hover).

On the other pages all links are wrapped with a strong tag. I'm not a design person so I'm not sure if it'd be better to change the link color or to add an underline, but a small tweak would definitely help usability.

Please, check it out.
Thanks.

Hi @indus
I pushed my updates on https://ajaxable.js.org/ and can't see them online. I guess is related to CF DNS. Do you know how should I purge the cache?

I was going through the list in cnames_active.js and see a few that are either missing or the pages have no content. How should we report these?

I was curious if you might be willing to share your server configuration with DNS for this? I've been doing something similar with bbs.io using freedns.afraid.org, but have been wanting to do a bit more with it.

I didn't know where to put this, so I put it here. The SSL cert has expired.
https://light-theme-hurts.my-ey.es/d277de.png

I think those should be restricted, unless, of course, their official contributors want to use it or if you may use those to redirect to their project pages.

Original issue: #2

In the moment JS.ORG is using a standard plan of GoDaddy (where the domain is hosted) and their nameservers to make the DNS service possible. I just add all the requested and approved subdomains as CNAME records to the zonefile in the GoDaddy DNS-Manager.
I have been asked if SSL (https://) would be possible. I can see the need, but I don´t see a chance to make it possible with the current setup (For a free service, it would be hard to pay the bills to run a self hosted DNS nameserver, or pay for all the certificates and manage them).

I made some tests using CloudFlares free plan (as @SVincent suggested to me) and tried to make a custom domain for a github page work with https: (CloudFlare provides Universal SSL). And it looks very promissing, with some drawbacks:

PRO CloudFlare:

• allows SSL
• allows browser caching (GitHub has a fixed expiration of 60s)
• high speed, high reliability

CONTRA CloudFlare:

• new entries in the Zonefile take much longer to propagate
• forces browser caching (at least 2 hours)
• changes in a GitHub repo take longer to go live

update: looks like "page rules" allows fine-grained control to avoid the two remaining drawbacks, but may add some extra work to the process of adding a subdomain when we don´t find "one fits all" settings.

CloudFlare also has a very easy way to decide about using its caching or forward the request directly to GitHub for every subdomain.

Before I come to a decision about it, I wanted to hear from the users of DNS.JS.ORG what you are thinking about moving JS.ORG to CloudFlare and using their nameservers (and if you want to SSL and Caching)?

Did I missed some PROS/CONS?

Is it possible to have a "subdomain" (e.g. "foo.bar.js.org")? I don't really want to buy my own domain but I need to link to multiple servers.

Hello, I'm wondering if it is possible to simply point a js.org domain to my own self-hosted site?

My current site is at http://infamous.io, but I want to rename it and then move it to a new domain (along with added docs and demos), to <something>.js.org. I haven't come up with the new name yet, but would like to do it soon.

Would it be possible that you can simply apply name servers to the subdomains or something (not sure if subdomain name servers are even possible). Maybe there some other way to do it, by forwarding the subdomain to my server IP address?

While there is a note in the readme-section of the subdomain-list that SSL support is possible, this is hardly ever used.
At the moment requested subdomains are getting added to JS.ORGs zonefile in a way that they get redirected to GitHub directly and don´t get touched by Cloudflare. Only requesting with the opt-in flag //CF gives me a hint to enable CFs Universial SSL service for a subdomain.

Given the fact that SSL is getting more important - not only to get more security (maybe not that important for a static website) but also to be treated well by search-engines and browsers - it could be good move to make the SSL option the default (keeping the ability for the requester to opt-out).

But SSL doesn´t come alone when CF handling is enabled. The biggest difference would be that browser caching would change from 60s (default for GitHub Pages) to 30min (Cloudflares minimum TTL).

While browser cacheing could be seen as a benefit for visitors (and for servers, but we don´t worry about that ;-), it may be annoying when you build up a fresh page and want to ckeck it frequently on mobile device or in situations when you release a new version of your lib together with a fresh documentation.

So I´m interrested to hear from the users of this service what the default should be.

For people with some Cloudflare experience - here the current "Page Rule" settings that affect all URLs that match the pattern *.js.org\* when CF handling is turend on (more explanations on Page Rules here):

• Custom caching: Bypass cache
• Browser cache expire TTL: 30 minutes
• Always Online: Default
• Apps: On
• Performance: On
• Rocket Loader: Default
• Security: Off
• SSL: Default
• Security Level: Default
• Browser Integrity Check: Default

Besides the opt-in opt-out discussion, I´m also willing to change the settings shown above if we find a better "one-fits-all" combination

I´m on vacation for about two weeks. I probably won't be able to process pull requests for new subdomains in that time.
Of course you can still make pull request that will be processed later. But if you request for a user- or organisation-page you should rename "CNAME" to something else (e.g. "CNAME_") to turn off GitHubs forwarding. Otherwise your page will become unavailable in the meantime.

See you!

Can we use [project].js.org as email address?
Example: "[email protected]" redirect to "mx.zohomail.com" mail server.
Maybe we can use mail.js.org for email forwarding? :)

Hi Stefan,

functions.js.org sounds to me like a place where you can search for an existing function for a specific task that you can copy and paste into your project.

I know that this sub-domain is reserved, but I will give it a try :)

Would you be willing to allow this community-driven website I'm working on hosted under this domain?

It is a collection of JavaScript functions to be used in AWS Lambda, Azure Functions or Google Cloud Functions, where you can find functions like this - a function that monitors order queue, and whenever a new order comes, the function sends a confirmation email to the user who placed the order.

Recently I started a community focused project to provide free documentation hosting for JavaScript projects based on JSDoc conventions and using documentation.js to process and render documentation.

The project is strongly inspired by GoDoc and RubyDoc, so the idea is essentially the same, but for the JavaScript community.

The project is totally open for collaborations and contributors and recently I'll start adding new members that want to contribute actively to the project.
Here it's the Github organization.

I roughly invested around one productive day building the project, so it's in alpha stage.
Take a look to the preview version here: http://jsdocs.herokuapp.com

Officially it's not public yet, but before moving forward I would like to post this request in order to assign a proper domain for the project.

Some subdomains that would be great (at least one):

• doc.js.org
• docs.js.org
• pkgdoc.js.org

Thoughts?

hi there, i am the owner of js.cool domain, and i want to provide free subdomains too (make a Chinese Version).

could you help me build it up?

Hi Stephan,

I'm currently working on wiki app, built in Node.js, named Wiki.js which is nearing completion. I was hoping I could use the wiki.js.org subdomain, even though it's in on the reserved names list.

You can see the current website for the project:
http://wiki.requarks.io/

(which points to the https://github.com/Requarks/wiki-site repository)

The actual project repository can be found here: https://github.com/Requarks/wiki

In addition to this website, I'm using the actual Wiki.js software for all the documentation. It is hosted on an external server as GitHub doesn't run Node.js obviously. Would a docs.wiki.js.org second level subdomain be possible as well? This one wouldn't require any cloudflare handling of ssl or caching.

Thanks!
Nick

Screenshot:

Hi! What do you think about creating some badge for repo that use your project?

Hi, is it possible to get a subdomain that is different from your username or repo name?

In this specific case the repository is called two.js, two.js.js.org would be a bit weird wouldn't it?

See this issue

@indus are you interested in public.cachegit.com being hosted at cdn.js.org?

I've just started a community-focused project to provide a place for JavaScript users to easily find the plugins/libraries/frameworks/whatever they need to help with their projects. You can find it here: tools-js.github.io repo

I've put about a full day's work into it, though it doesn't have many commits because I only uploaded it to GitHub an hour ago. You can preview it at https://tools-js.github.io. As of this writing, it only has data on jQuery, AngularJS, JSHint, and JSLint.

Though it's barely in the alpha stage, I'd like to set it up on the tools.js.org subdomain. I think that with a cleaner domain name (https://tools.js.org compared to https://tools-js.github.io), it will gather more attention and hopefully better serve its purpose.

Here's my ideal subdomains for this project, in descending order:

• tools.js.org
• tool.js.org
• toolsearch.js.org and variants
• findtools.js.org and variants

Thoughts?

I recently claimed algebra.js.org, but algebra is taken on npm so I'm thinking about changing the name of my project. So my questions are:

1. how annoying would this be for you?
2. if it's not a terrible inconvenience, how would I go about this? Would I submit a pull request where I remove the algebra entry to make it available to someone else and add an entry for my new to-be-determined project name?

Currently the Object in cnames_active.js is formatted with trailing commas, e.g.

"finder": "applait.github.io/finderjs",
"happy": "e24.github.io/happy",

which means when you want to add a single entry you'll have to rewrite two lines.

I propose to change the formatting to leading commas, i.e.

, "finder": "applait.github.io/finderjs"
, "happy": "e24.github.io/happy"

which is also the style many JS projects use.

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.

Would be great if i.e. https://www.deck-of-cards.js.org would redirect to https://deck-of-cards.js.org since many people always starts to write URL's with "www"-prefix. Now just fails to show anything.

I would like to ask about chances to get a restricted domain compare.js.org for the project hosted at starratio.js.org.

The project helps to compare javascript opensource projects by different of stats.

Testimonials:
http://survivejs.com/blog/starratio-interview/
https://twitter.com/shanselman/status/775956034229678080

With commit bc55b69 and cssjanus/cssjanus.github.io@c9c030205c, cssjanus is now supported by the js.org proxy for GitHub Pages.

Since then, https://cssjanus.github.io/ now redirects to http://cssjanus.js.org/ which is undesirable. (Note, HTTP, not HTTPS)

Please disable the redirect, or ensure it redirects to HTTPS directly.

At the moment, the HTTP endpoint also doesn't enforce HTTPS so the user stays on HTTP. Effectively a downgrade from secure to insecure. Whilst redirecting back to HTTPS would be nice, but that requires making HTTPS the default which we may not want to do yet. But at least incoming HTTPS should maintain HTTPS all the way through to avoid leaking the url and other client details to third parties.

I suspect this may be caused by how GitHub Pages redirects, not js.org. As such, I've filed an issue with them as well, pointing here.

I want to request one *.js.org DNS, but I've read the instructions and it's only for gh-pages branch, but my page it's under branch MASTER with the option /docs folder. It's not my root username.github.io page.

Can I add my CNAME under /docs?

Thanks!

Hi, I'm looking through the wiki in https://github.com/js-org/dns.js.org/wiki/Naming-Conflicts, and "GitHub stars" do not sound like fraud-protected parameter. I mean, it's good, but I probably can create some kind of botnet to increase stars count. I mean, we're all good guys here, but just to ensure, maybe some more protected measurement should be provided? Or simply add some details about the fact that facts of stars manipulation will be checked.

Can we have emails in js.org? for example I would like to have [email protected] as my email

Replace js for cname files with csv format. Github has interface to show csv in more humanized way.

I'm would like to move my thundercats.js repo to its own org /thundercatjs.

What's the process for this? Hopefully its not too much of a hassle.

Since subdomains under js.org are user content, I'd suggest having js.org added to publicsuffix.org. The list is among other things responsible for domain highlighting in Firefox. Currently when visiting "stats.js.org", Firefox is highlighting "js.org" as the main part of the URL. With "js.org" on the list, Firefox would highlight "stats.js.org" instead.

"github.io" is on the list, so should "js.org".

See:
https://publicsuffix.org/
https://publicsuffix.org/submit/
https://wiki.mozilla.org/Public_Suffix_List
https://github.com/publicsuffix/list

If not, can it? Or is that a restriction of GitHub Pages?

@graingert it looks like you forked a unlicenced project from @matthieua ("wow") put an MIT licence to it and requested a subdomain from JS.ORG for it. He already asked me to take it down on Twitter. Would you please make a statement?

Hi,

I recently moved my project webpage to a private server to gain more control over my site (Redirects started to become a big problem), and I was wondering if it was possible to make a record or a redirect to my new location ?

Hey, I just saw that core is a restricted subdomain. Does that mean you can't use it? Because I just thought about registering it for github.com/corejavascript/typeahead.js/, as corejs.js.org doesn't sound and look good in my opinion. But then is stumbled over github.com/js-org/dns.js.org/cnames_restricted.js as stated above. And now I am unsure wether how to proceed with this.

The subdomain node.js.org seems too similar to nodejs.org, and I think it should either point directly to there or be restricted.

Hello.

I have a repository I am going to transfer to an organizational github account. I'm also planning to rename the repository.

Domain in question is: http://os.js.org/ which is currently reciding at https://github.com/andersevenrud/OS.js-v2, it will most likely end up as https://github.com/os-js/OS.js

Is there anything I need to do except for editing my CNAME file ?

Like github, can you provide services to bitbucket.org? Even they serve static pages with bitbucket.io domains.
https://confluence.atlassian.com/bitbucket/publishing-a-website-on-bitbucket-cloud-221449776.html

Can I use custom subdomain for user pages?

I have my own site: randsonjs.com. It will be great if I can use randson.js.org.

Ah, my username js is a nickname ;)

This issue is a place to report broken links and pages without content. Owners of pages with requested subdomains can use it to replay on a pending removal notifications. #367