Closed alonkochba closed 2 months ago
@shahata
@alonkochba Please order your block correctly. Entries are ordered by TLD first and then by the SLD (so-called right-to-left sorting). So wixstudio.com
should follow after wixsite.com
.
Also, the whole block for Wix.com, Inc.
is in the wrong spot. It should be located below WISP
but is actually located below WP Engine
.
Sorting looks good to me now.
Thanks, I am only adding wixstudio.com here, the rest is refactoring, but I will reach out to make sure the others are extended as well and PSL is readded.
@alonkochba Any updates?
Hi, all comments done
PR check seems to fail on someone else's entry, any idea why?
Checking TXT entry for _psl.emrnotebooks-prod.ap-south-2.amazonaws.com. DNS answer: "https://github.com/publicsuffix/list/pull/1919" -> PR 1919
PR check seems to fail on someone else's entry, any idea why?
Checking TXT entry for _psl.emrnotebooks-prod.ap-south-2.amazonaws.com. DNS answer: "#1919" -> PR 1919
I'm working on it, don't worry about it. It's not your fault. :)
Please tick the box saying that you will keep the 2 years validity.
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
[x] Description of Organization
[x] Robust Reason for PSL Inclusion
[x] DNS verification via dig
[x] Run Syntax Checker (make test)
[x] 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)
[x] Yes, I understand. I could break my organization's website cookies etc. and the rollback timing, etc is acceptable. Proceed.
Description of Organization
Wix is a website building platform.
Registered developers can create apps and get their own subdomain (e.g. username.wixstudio.com) on which their sites are hosted.
Organization Website: https://www.wix.com/
Reason for PSL Inclusion
We'd like to properly isolate each subdomain to prevent global cookie setting on wixstudio.com and highlight that each subdomain hosts sites of a different user, unrelated to the others.
Number of users this request is being made to serve:
DNS Verification via dig
Results of Syntax Checker (
make test
)