-
Notifications
You must be signed in to change notification settings - Fork 1.2k
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
Removal of blog.kg
from private section
#1840
Conversation
blog.kg
from private section
Running the unit tests on this - it appears that you'll need to make this change against a new snapshot of the PSL - you can open a new PR with a fresh branch and reference this PR, or you can update the base used. Can't walk you through the second option |
OK looks like that's sorted out |
Yep, I had just rebased (or merged, I don't know for sure as I used the GH interface) the branch today. Do I need to do anything else? |
|
|
Working this out with the volunteers - would love to just delete all these but want to make sure there is no 'friendly fire' scenarios that occur unintentionally from pulling the entirety of them. Your individual domain name and not having you held up in the whole batch dialog is part of the discussion. I also created #1866 about this |
it took a lot of review to ensure low impact, which required reviewing all impacted domains for each of the inter-connected pull requests, one by one. The current plan is to process #1741 and #1755 which will solve your issue, but we need the author of #1755 to update theirs, perhaps you can nudge them? |
Thanks a lot for letting me know. I checked #1755 but that domain doesn't satisfy the registration duration requirement anyway, is there any point in trying to get the author to update it? In fact it never satisfied that requirement, and on their website it's not listed as a service as well, so I have a fair guess of that PR (and the domain as well) dying down. |
I dug deeper into #1755 a bit more and it gets weirder. While https://nic.us.kg exists, it's not managed by the author's non-profit but an alleged company called EdgeAlpha Ltd: https://nic.us.kg/terms-of-service/ Almost the same thing was mentioned before in the PR, but with an entirely different alleged company name. The author acknowledged this but didn't do any changes in their PR, which poses yet another issue on top of the registration duration requirement. At this point it feels like a child's play to me, does it really make sense to hold all the other invalid entries just because of this? |
fair point. will review more when additional volunteer cycles are available again |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
- Sorted to Guidelines
- DNS TXT = Pull Request URL
- Tests Pass
- No conflict with base
APPROVED
Thank you! |
I would like to remove my domain
blog.kg
from PSL (related: #1753).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
I am acting on my own behalf as an individual.
Organization Website: N/A
Reason for PSL Inclusion
N/A, I would like to remove my domain from PSL.
Number of users this request is being made to serve: N/A
DNS Verification via dig
Results of Syntax Checker (
make test
)