-
Notifications
You must be signed in to change notification settings - Fork 1.3k
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
chore: add is-a.dev
#1949
chore: add is-a.dev
#1949
Conversation
Whoever approves this PR is extremely based. |
Let's hope it gets approved |
REALLY GOOD SERVICE. i hope it gets approved |
Hope this gets approved |
approve please |
He listed every possible reason it SHOULD be added, please approve |
approve this service please |
Can you please contact Netlify and Vercel? Or provide a link to their docs? |
|
If these are all "you". Why are they not under the same organization? |
They are "Similar" to what subdomains we provide. We do not come from the name owner nor the same orginization. |
Vercel checks the apex domain even if you are using a subdomain and no one else is using the root domain. If is-a.dev was listed on the PSL it will fix this as it will recognise With Netlify, I cannot find a doc page however, I can tell you that it does the same as Vercel regarding domain ownership. |
Just as a note, comments of the form "+1" or "approve this" really don't add any value. ;) |
Yeah I know. I didn't ask people to do that if that's what you're thinking. People just did that after I announced we applied for the PSL. |
approve this |
piling on comments is actually slowing approval / merging as it all gets reviewed holistically, and may start the review over, so unless there is interest in delay, please stop 'nudging' |
@dnsguru Can you lock the conversation? (Once again, I'm not asking people to do this.) |
Public Suffix List (PSL) Pull Request (PR) Template
Each PSL PR needs to have a description, rationale, indication of DNS validation and syntax checking, as well as a number of acknowledgements from the submitter. This template must be included with each PR, and the submitting party MUST provide responses to all of the elements in order to be considered.
Checklist of required steps
Description of Organization
Robust Reason for PSL Inclusion
DNS verification via dig
Run Syntax Checker (make test)
Each domain listed in the PRIVATE section has and shall maintain at least two years remaining on registration, and we shall keep the _PSL txt record in place in the respective zone(s) in the affected section
Submitter affirms the following:
For Private section requests that are submitting entries for domains that match their organization website's primary domain, please understand that this can have impacts that may not match the desired outcome and take a long time to rollback, if at all.
To ensure that requested changes are entirely intentional, make sure that you read the affectation and propagation expectations, that you understand them, and confirm this understanding.
PR Rollbacks have lower priority, and the volunteers are unable to control when or if browsers or other parties using the PSL will refresh or update.
(Link: about propagation/expectations)
Description of Organization
is-a.dev is a free subdomain service for developers. We offer subdomains on the domain
is-a.dev
to all developers for their personal websites and portfolios.Organization Website:
https://www.is-a.dev
https://github.com/is-a-dev/register
Reason for PSL Inclusion
Original PR: #1327
We are seeking to get our domain
is-a.dev
added to the Public Suffix List since it is a public domain service available to everyone.I am an administrator of the is-a.dev project.
One of the main reasons we would like to be included on this list is cookie separation, cookie separation will allow all cookies across our users subdomains to remain separate and to prevent potential security risks between subdomains.
Another reason for why we should be added is, users are unable to use services such as Vercel and Netlify due to those services requiring root domain verification even when using a subdomain on their service. This is because the services use the Public Suffix List (as far as I'm aware) and do not recognise our domain as a public suffix.
This project is very similar in what we offer to services such as https://eu.org and https://js.org which are already on the PSL.
Number of users this request is being made to serve:
Currently over 2,660 individuals, with the count growing everyday.
DNS Verification via dig
Results of Syntax Checker (
make test
)All tests passed.
Please note, the submitter email is the service owner's email address, not mine. I am using that email address as he is the one to contact if there is any issues.