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

add lgbt.sh #2304

Closed
wants to merge 2 commits into from
Closed

add lgbt.sh #2304

wants to merge 2 commits into from

Conversation

cvyl
Copy link

@cvyl cvyl commented Dec 2, 2024

Public Suffix List (PSL) Submission

Checklist of required steps

  • Description of Organization

  • Robust Reason for PSL Inclusion

  • DNS verification via dig

  • Test results included

  • 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).

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).

We are not submitting this request to bypass any third-party limitations. Specifically:

  • Cloudflare: No issues or rate limits are being addressed through this request. lgbt.sh operates independently of Cloudflare's systems.
  • Let's Encrypt: We are not seeking to circumvent Let's Encrypt rate limits. Certificates for lgbt.sh and its subdomains are issued within standard limits and policies.
  • Other third parties: This request is not intended to address issues related to iOS, Facebook, or any other third-party systems.

This submission is being made solely to ensure that lgbt.sh is recognized as a public suffix for proper handling of cookies, cross-origin policies, and security isolation.

  • The submitter acknowledges that it is their responsibility to maintain the domains within their section. This includes removing names which are no longer used, retaining the _psl DNS entry, and responding to e-mails to the supplied address. Failure to maintain entries may result in removal of individual entries or the entire section.

  • The Guidelines were carefully read and understood, and this request conforms to them.

  • The submission follows the guidelines on formatting and sorting.

Abuse Contact:


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

Description of Organization

Organization Name: LGBT.SH
Organization Website: https://lgbt.sh
Description: LGBT.SH is a public subdomain registry that provides domain name services specifically tailored to the global LGBTQ+ community. The platform allows users to register subdomains under lgbt.sh for personal, organizational, or advocacy purposes.

Subdomain registrations are available through two methods: email requests or by opening a GitHub issue. This ensures transparency and ease of access for a wide range of users. Abuse reporting mechanisms are in place to address any misuse.


Reason for PSL Inclusion

The inclusion of lgbt.sh in the Public Suffix List is requested to ensure proper handling of cookies, security, and cross-origin policies. Being a public subdomain registry, lgbt.sh allows independent registration of subdomains by users, which makes its behavior closer to a TLD than a typical domain.

This inclusion will enhance compatibility with browsers and applications, enabling subdomain users to implement independent security policies without cross-origin interference from other subdomains.

Number of users this request is being made to serve:
Approximately 180 active subdomains, with potential for continued growth as registrations increase.


DNS Verification

The following DNS verification records have been added:

dig +short TXT _psl.lgbt.sh
"https://github.com/publicsuffix/list/pull/2304"

Test Results

The make test command was run as part of the submission process, and all tests passed successfully:

https://pastebin.com/raw/CLJnfQ5s


Thank you for considering this submission. I am happy to provide additional information or address any concerns the reviewers might have.

@wdhdev
Copy link
Contributor

wdhdev commented Dec 2, 2024

180 users/subdomains is generally top little to be approved, I would recommend closing this and reopening it when you reach around 1,000 users.

@cvyl
Copy link
Author

cvyl commented Dec 2, 2024

180 users/subdomains is generally top little to be approved, I would recommend closing this and reopening it when you reach around 1,000 users.

Thank you for taking the time to review my submission. I appreciate the feedback and the opportunity to learn more about the criteria for inclusion. I was under the impression that there wasn't a specific user minimum for submissions, so I apologize for any misunderstanding on my part.

Would the current size of my user base make LGBT.SH ineligible, or is it simply a matter of scaling the project further before reapplying? This is a project I’m actively reworking to make registration and usage even easier, and I'm hopeful it will continue to grow in the coming year.

Again, thank you for your time. I'm happy to follow any recommendations to improve my chances for approval in the future.

@wdhdev
Copy link
Contributor

wdhdev commented Dec 2, 2024

As per our guidelines:

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 requests. 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.

Would the current size of my user base make LGBT.SH ineligible, or is it simply a matter of scaling the project further before reapplying?

The current user base size is likely ineligible, we normally require a minimum of 1,000 users, as per my previous comment. You would need to scale the project further before you will be accepted.

Once you have around 1,000 users, you should be good to be approved.

@groundcat
Copy link
Contributor

groundcat commented Dec 3, 2024

I agree with @wdhdev that the project typically cannot accept submissions for smaller-scale projects, as each entry in the PSL (Public Suffix List) must demonstrate substantial user impact - typically at least thousands of users - to merit inclusion. I do appreciate the free subdomain registries like the ones you are operating, though.

However, please note that subdomain count is just one metric for evaluating a project's scale, not the sole criterion. If you can provide additional metrics or evidence demonstrating your service's current scale, we will evaluate those as part of the consideration process.

@cvyl
Copy link
Author

cvyl commented Dec 3, 2024 via email

@groundcat
Copy link
Contributor

groundcat commented Dec 3, 2024

@cvyl Perhaps I was not clear enough - we are seeking any form of quantitative evidence that supports the claim regarding how many users would benefit from having your domain included in the PSL. While the number of subdomains is a significant indicator, we also consider other factors. These could potentially include the number of users within multiple individual subdomains who may benefit indirectly, or tunneling use cases that are not visible to external sources such as search engines, etc. We are not interested in non-quantitative narratives or marketing materials, but rather focus on technical aspects that can be quantified and verified. As previously indicated, 180 subdomains (assuming it indicates 180 users) does appear insufficient, and it might be best to close this one and in the future submit a new PR after your service has gained a sufficient user base.

@cvyl
Copy link
Author

cvyl commented Dec 3, 2024

@cvyl Perhaps I was not clear enough - we are seeking any form of quantitative evidence that supports the claim regarding how many users would benefit from having your domain included in the PSL. While the number of subdomains is a significant indicator, we also consider other factors. These could potentially include the number of users within multiple individual subdomains who may benefit indirectly, or tunneling use cases that are not visible to external sources such as search engines, etc. We are not interested in non-quantitative narratives or marketing materials, but rather focus on technical aspects that can be quantified and verified. As previously indicated, 180 subdomains (assuming it indicates 180 users) does appear insufficient, and it might be best to close this one and in the future submit a new PR after your service has gained a sufficient user base.

Thank you for the clarification! I understand now. I will close this PR and re-submit it once the requirements are met.
Wishing you a good rest of the week.

@cvyl cvyl closed this Dec 3, 2024
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.

3 participants