Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description of Organization
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.
Description of Organization
Boutir (https://www.boutir.com) helps individual merchants to build and host their online webstore. Merchant can use their own custom domain, or use *.boutir.com (e.g. https://ingoodhandsof.boutir.com), therefore we would like to have boutir.com in the public suffix list and have it as eTLD
I'm founder of Boutir, and built Boutir with other engineers in the team.
Boutir is a SAAS business, merchants can subscribe our monthly / yearly plan to setup, maintain and operate their online webstore using our mobile app. There is also a free plan for merchants and they can setup their store (e.g. xxx.boutir.com) in 10 mins.
Organization Website: https://www.boutir.com
Reason for PSL Inclusion
With iOS14.5 launch, in accordance with their AppTrackingTransparency framework, Facebook will start processing pixel conversion events from iOS 14 devices using Aggregated Event Measurement to preserve user privacy and help running effective campaigns. Specifically, Facebook would associate events triggered from a website to be associated with a Domain, the corresponding merchant's owned Facebook Ad Account, and the corresponding Pixel.
Merchant needs to verify their website's domain with Facebook and this would be done at eTLD+1 level. In our case, it would be boutir.com
However, as with our model, each merchant operates separately and independently. aaa.boutir.com products, data, events are totally separated from those from bbb.boutir.com. But now we cannot do it, as Facebook only verify eTLD+1 (i.e. boutir.com) and would not verify and associate events with aaa.boutir.com separately with bbb.boutir.com. Merchants from aaa.boutir.com and bbb.boutir.com cannot pass through the verification step, and cannot effectively associate events triggered from their website to their domain.
If boutir.com can be listed in the PSL, Facebook can separately verify aaa.boutir.com and bbb.boutir.com, and different merchants can associate events and track separately with different domain aaa.boutir.com and bbb.boutir.com
boutir.com registration for is up to 19/10/2023, longer than 2 years from now.
We have a past issue #1202. The issue has been closed as I have not provided response on time while we are still discussing with Facebook to see if we have to make the domain boutir.com listed on PSL. After confirming with Facebook side, the issue has been closed and thus I re-create a new issue for this.
DNS Verification via dig
dig +short TXT _psl.boutir.com
"#1225"
make test