Skip to content
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

awto.js.org #3342

Closed
wants to merge 2 commits into from

Conversation

@theabbie
Copy link
Contributor

commented Sep 3, 2019

I want to host awto.js.org on zeit with support for subdomains so i want to add zeit nameservers

@MattIPv4

This comment has been minimized.

Copy link
Member

commented Sep 3, 2019

Does this PR not need to also remove your CNAME entry: https://github.com/js-org/js.org/blob/master/cnames_active.js#L183 ?

@theabbie

This comment has been minimized.

Copy link
Contributor Author

commented Sep 3, 2019

@MattIPv4 sorry, i forgot that

@theabbie

This comment has been minimized.

Copy link
Contributor Author

commented Sep 3, 2019

@MattIPv4

This comment has been minimized.

Copy link
Member

commented Sep 3, 2019

Please make both changes in this PR, we don't need a second PR.

@theabbie

This comment has been minimized.

Copy link
Contributor Author

commented Sep 3, 2019

@MattIPv4 okay

@theabbie theabbie closed this Sep 3, 2019

@theabbie theabbie reopened this Sep 3, 2019

@theabbie

This comment has been minimized.

Copy link
Contributor Author

commented Sep 3, 2019

@MattIPv4 changing multiple files in a single PR is such a complicated process

@MattIPv4

This comment has been minimized.

Copy link
Member

commented Sep 3, 2019

@theabbie Head to the branch that this PR is merging: https://github.com/theabbie/js.org/tree/patch-5
Make the relevant change.
Commit that change to that branch.
Done.

@theabbie

This comment has been minimized.

Copy link
Contributor Author

commented Sep 3, 2019

@MattIPv4 i think i did what you said

@MattIPv4
Copy link
Member

left a comment

lgtm.

@MattIPv4 MattIPv4 added change NS labels Sep 3, 2019

@theabbie

This comment has been minimized.

Copy link
Contributor Author

commented Sep 3, 2019

@MattIPv4 i can't see the changes in the respective files though, neither was domain verified

@indus

This comment has been minimized.

Copy link
Member

commented Sep 3, 2019

Your request is not processed yet. We have an internal discussion abou it. Support for services other then Github Pages or at least NS records may be discontinued...

@theabbie

This comment has been minimized.

Copy link
Contributor Author

commented Sep 3, 2019

@indus why are nameservers limited, what if someone like you needs more?

@indus

This comment has been minimized.

Copy link
Member

commented Sep 3, 2019

Not nameservers are limited but records in JS.ORGs zonefile in gerneral are limited and NS records need 4 of them.
But there are other reasons why I don't like to add them:

  • They make more work for me to add
  • They give people the chance to send emails from a js.org adress (in the worst case - use them for sending spam mails etc. bringing bad reputation to JS.ORG)

You on the other hand haven't aswered my question why YOU need NS records - while almost 2000 other users can live without them. The page you created on Github Pages has almost no content and you don't have a history on GitHub.

So there is not much that convinces me that I should add them.

@theabbie

This comment has been minimized.

Copy link
Contributor Author

commented Sep 3, 2019

@indus the 2000 other users are serving static content which is almost useless nowadays, zeit is all about nodejs and i am okay with txt records,

nameserver will only allow me to add sub subdomain to awto.js.org, and it's your choice if you want to give it it not

secondly, nameservers don't allow sending emails

thirdly, making websites is not my field of interest, that is why there is no content, i am interested in making APIs for helping people out, awto.js.org is just to showcase them, when i will have a working and useful API i will add content to it,

Thus, zeit would allow me to create API from this awto.js.org subdomain which sounds nice, thus i was insisting to do so

@MattIPv4

This comment has been minimized.

Copy link
Member

commented Sep 3, 2019

secondly, nameservers don't allow sending emails

Name servers give you full control over the DNS for that subdomain, which would absolutely allow you to send and receive emails. Please don't make false statements when defending your use-case, it doesn't help the situation.

Thus, zeit would allow me to create API from this awto.js.org subdomain which sounds nice, thus i was insisting to do so

Have you started work on this yet, do you have anything to show you have a legitimate use for the NS records? As indus stated, your current site has almost no content and I see nothing on your GitHub to indicate you have content/API code ready to be used with this request?

@indus

This comment has been minimized.

Copy link
Member

commented Sep 3, 2019

secondly, nameservers don't allow sending emails

They allow to add MX records and you can point them to whatever mailserver you like.

@theabbie

This comment has been minimized.

Copy link
Contributor Author

commented Sep 3, 2019

@MattIPv4 my repo does have content, check out https://theabbie.github.io/awto/ai, all all files inside files folder, i have api code in other repos, if you see, if it's not in home page it doesn't mean it's not there

@theabbie

This comment has been minimized.

Copy link
Contributor Author

commented Sep 3, 2019

@indus suppose you add my nameserver how would i be able to add MX records without your help?

@MattIPv4

This comment has been minimized.

Copy link
Member

commented Sep 3, 2019

suppose you add my nameserver how would i be able to add MX records without your help?

The fact that you do not understand how nameservers & DNS works makes me very inclined to suggest your request for NS records shouldn't be accepted...

@theabbie

This comment has been minimized.

Copy link
Contributor Author

commented Sep 3, 2019

@MattIPv4 there is no mail service which uses nameserver for email configuration neither is it possible without MX records whose full authority is with you guys

@theabbie

This comment has been minimized.

Copy link
Contributor Author

commented Sep 3, 2019

@MattIPv4 and please don't say no content in my repo it has more content than 90% of .js.org sites you already approved

@theabbie

This comment has been minimized.

Copy link
Contributor Author

commented Sep 3, 2019

@indus seeing this #3338 (comment) i think you are okay with nameserver now

@indus

This comment has been minimized.

Copy link
Member

commented Sep 3, 2019

Lets bing this to an end, too.
I wont accept the NS records you are adding in this PR.

@theabbie do you want...

A) a CNAME pointing to alias.zeit.co and a TXT for verification
B) back to the CNAME pointing to Github
or C) delete your records at JS.ORG and look for another free or paid domain service to get full control

There are no other options.

@theabbie

This comment has been minimized.

Copy link
Contributor Author

commented Sep 3, 2019

@indus just now you added ns records for #3338 for the same reason i wanted it

@indus

This comment has been minimized.

Copy link
Member

commented Sep 3, 2019

We are negotiating this case. And I'm just feed up by this PR (and you last 16). So don't compare it to another.
A, B or C?

@theabbie

This comment has been minimized.

Copy link
Contributor Author

commented Sep 3, 2019

@indus ain't that unfair? i know it's legal (all this belongs to you) but it's unfair, please consider and if not option (A) seems fine

@theabbie

This comment has been minimized.

Copy link
Contributor Author

commented Sep 3, 2019

@indus what does this mean then #3338 (comment)?

@indus

This comment has been minimized.

Copy link
Member

commented Sep 3, 2019

@theabbie A is the current state.

@indus indus closed this Sep 3, 2019

@indus indus removed NS change labels Sep 3, 2019

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
3 participants
You can’t perform that action at this time.