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

2024 Update for domain diher.solutions and rss.my.id #2128

Merged
merged 1 commit into from
Sep 4, 2024

Conversation

pereceh
Copy link
Contributor

@pereceh pereceh commented Sep 3, 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)
    • Cloudflare
    • Letsencrypt
    • <UPDATE THIS LIST WITH YOUR LIMITATIONS! REMOVE ENTRIES WHICH DO NOT APPLY! REMOVE THIS LINE!>
  • This request was not submitted with the objective of working around other third-party limits
  • 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, 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
  • 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

I am a blog writer. and I'm also the sole manager for the listed domains.

Organization Website: https://rss.my.id

Reason for PSL Inclusion

My firewall software cannot detect wildcard characters.

DNS Verification via dig

dig +short TXT _psl.diher.solutions "https://github.com/publicsuffix/list/pull/1393"

dig +short TXT _psl.rss.my.id "https://github.com/publicsuffix/list/pull/1393"

make test

All test passed.

@awsjulian
Copy link
Contributor

awsjulian commented Sep 3, 2024

Reason for PSL Inclusion
My firewall software cannot detect wildcard characters.

could you elaborate what exactly this means and what you want to achieve with the firewalls by including your domain in the PSL? It doesn't seem like a valid reason to add your domain to the PSL.

@pereceh
Copy link
Contributor Author

pereceh commented Sep 3, 2024

Reason for PSL Inclusion
My firewall software cannot detect wildcard characters.

could you elaborate what exactly this means and what you want to achieve with the firewalls by including your domain in the PSL? It doesn't seem like a valid reason to add your domain to the PSL.

the filter on my firewall uses data from this list to validate a domain.

@awsjulian
Copy link
Contributor

awsjulian commented Sep 3, 2024

> the filter on my firewall uses data from this list to validate a domain.

which firewall software you are using and how many users are impacted? how does including your domain in the PSL benefits a large number of users, given that the PSL is a globally utilized resource. The connection between your request and the PSL's broader purpose remains unclear. Please check https://github.com/publicsuffix/list/wiki/Guidelines

@awsjulian
Copy link
Contributor

awsjulian commented Sep 3, 2024

from "Validation and Non-Acceptance Factors" https://github.com/publicsuffix/list/wiki/Guidelines#validation-and-non-acceptance-factors

> We do not accept entries that have the objective of getting around limitations that have been put in place by a vendor to protect internet users. The PSL is not a 'workaround', and Pull Requests that appear to be doing this should expect to be declined. Be thorough and candid with the rationale furnished with the request.

@awsjulian
Copy link
Contributor

sorry for the confusion! I initially thought you were trying to add new domains to workaround firewall limitations, but I now realized you're simply trying to remove the *. from existing ones. In that case, your request makes sense.

@pereceh
Copy link
Contributor Author

pereceh commented Sep 3, 2024

sorry for the confusion! I initially thought you were trying to add new domains to workaround firewall limitations, but I now realized you're simply trying to remove the *. from existing ones. In that case, your request makes sense.

Yes, waiting for updates.

@groundcat
Copy link
Contributor

groundcat commented Sep 3, 2024

  • Expiration (Note: Must STAY >2y at all times)
    • rss.my.id expires 2030-07-24
    • diher.solutions expires 2031-03-15
  • DNS _psl entries (Note: Must STAY in place)
    • _psl.rss.my.id
    • _psl.diher.solutions
  • Tests pass
  • Sorting
  • Reasoning/Organization description
    • Updating existing entries
    • Submitter = original submitter
  • Non-personal email address

  • Please renew rss.my.id to extend it for more than 2 years from now. Completed
  • Please update _psl.rss.my.id and _psl.diher.solutions TXT records with the URL of this PR. Completed

@pereceh
Copy link
Contributor Author

pereceh commented Sep 3, 2024

  • Expiration (Note: Must STAY >2y at all times)

    • rss.my.id expires 2026-07-24
    • diher.solutions expires 2031-03-15
  • DNS _psl entries (Note: Must STAY in place)

    • _psl.rss.my.id
    • _psl.diher.solutions
  • Tests pass

  • Sorting

  • Reasoning/Organization description

    • Updating existing entries
    • Submitter = original submitter
  • Non-personal email address

  • Please renew rss.my.id to extend it for more than 2 years from now.

  • Please update _psl.rss.my.id and _psl.diher.solutions TXT records with the URL of this PR.

I have renewed my domain rss.my.id until 2030 .

@simon-friedberger simon-friedberger merged commit 790a5a5 into publicsuffix:master Sep 4, 2024
1 check passed
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.

4 participants