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

chore: add is-a-fullstack.dev under Open Domains #2018

Closed
wants to merge 1 commit into from

Conversation

wdhdev
Copy link
Contributor

@wdhdev wdhdev commented Jun 28, 2024

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:

  • We are listing any third-party limits that we seek to work around in our rationale such as those between IOS 14.5+ and Facebook (see Issue #1245 as a well-documented example)
  • This request was not submitted with the objective of working around other third-party limits
  • The Guidelines were carefully read and understood, and this request conforms
  • The submission follows the guidelines on formatting and sorting

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)

  • Yes, I understand. I could break my organization's website cookies etc. and the rollback timing, etc is acceptable. Proceed.

Description of Organization

Open Domains is a service where you can register subdomains on 5 different domains is-a-fullstack.dev, is-cool.dev, is-local.org, is-not-a.dev and localplayer.dev. We provide this service for completely free and users can register as many subdomains as they want.

I am an administrator for the Open Domains project.

Organization Website:

https://open-domains.net
https://github.com/open-domains/register

Reason for PSL Inclusion

This is an addition to our original PR #1672, which was merged.

The domain is-a-fullstack.dev should be included on the Public Suffix List since it is a public suffix available to everyone.

Some of the users' subdomains use name server records. These subdomains are unable to be used with services like Cloudflare as they are not classified as domains at the moment. We would like users to be able to use these certain services as it helps grow our service and continues to make users happy.

As every subdomain is separate and is owned by different people we require cookie separation to help separate login services, and provide cookie security.

We already have our 4 other public suffixes on this list under the same section, as well as our sister project who is also listed (https://www.is-a.dev).

Number of users this request is being made to serve:

Over 140 users and growing. This is current.

DNS Verification via dig

dig +short TXT _psl.is-a-fullstack.dev
"https://github.com/publicsuffix/list/pull/2018"

Results of Syntax Checker (make test)

All tests passed.

@simon-friedberger
Copy link
Contributor

Projects that are smaller in scale or are temporary or seasonal in nature will likely be declined. Examples of this might be private-use, sandbox, test, lab, beta, or other exploratory nature changes or requets. It should be expected that despite whatever site or service referred a requestor to seek addition of their domain(s) to the list, projects not serving more then thousands of users are quite likely to be declined.

I'm afraid 140 users do not meet the bar for adding another domain.

@wdhdev
Copy link
Contributor Author

wdhdev commented Jun 28, 2024

I'm afraid 140 users do not meet the bar for adding another domain.

Thanks for the review, when this specific domain we offer grows in size more, will we be able to reopen this PR?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants