Add discourse.diy

[xfalcox]

Public Suffix List (PSL) Submission

Checklist of required steps

• Description of Organization

• Robust Reason for PSL Inclusion

• DNS verification via dig

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

• Cloudflare
• Let's Encrypt
• MAKE SURE UPDATE THE FOLLOWING LIST WITH YOUR LIMITATIONS! REMOVE ENTRIES WHICH DO NOT APPLY AS WELL AS REMOVING 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, 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.

• A role-based email address has been used and this inbox is actively monitored with a response time of no more than 30 days.

Abuse Contact:

• Abuse contact information (email or web form) is available and easily accessible.

  URL where abuse contact or abuse reporting form can be found: https://www.discourse.org/contact

---

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 and cause other issues, and the rollback timing is acceptable. Proceed anyways.

---

Description of Organization

Civilized Discourse Construction Kit, Inc. : https://www.discourse.org/

CDCK is the company behind Discourse, the open-source forum software.

I'm Falco, a software engineer at CDCK.

Organization Website:
https://www.discourse.org/

Reason for PSL Inclusion

We are offering free hostnames for people who want to run Discourse on their own servers, but can't, for any reason, obtain their own domain.

Each hostname will be a complete and separate instance of Discourse, without any cookie sharing or connection.

See #949 or #768 for similar requests from us.

Number of users this request is being made to serve:
1000+
There are thousands of self-hosted installs of Discourse, and we estimate hundreds of instances will use this domain, which each one having their own set of members, so we estimate thousands of users across the instances.

DNS Verification

dig _psl.discourse.diy TXT +short
"https://github.com/publicsuffix/list/pull/2748"

[simon-friedberger]

Since you are doing the hosting and controlling the software there is no need to be on the PSL, right?

[pencilnav]

BLOCKING: discourse.diy expires on 2027-01-15T21:26:54Z (~11 months) Fails minimum 2 year requirement - domain must be renewed.
Checked via registrar RDAP: https://rdap.namecheap.com/domain/discourse.diy
You'll need to renew your domain before this can get merged. @xfalcox

[xfalcox]

BLOCKING: discourse.diy expires on 2027-01-15T21:26:54Z (~11 months) Fails minimum 2 year requirement - domain must be renewed. Checked via registrar RDAP: https://rdap.namecheap.com/domain/discourse.diy You'll need to renew your domain before this can get merged. @xfalcox

We have renewed it for 3 years now @pencilnav

> whois discourse.diy | grep Expiry
Registry Expiry Date: 2029-01-15T21:26:54.623Z

Since you are doing the hosting and controlling the software there is no need to be on the PSL, right?

We are not hosting this, this domain subdomain will be given for people running Discourse on their own servers @simon-friedberger.

Also, on the software, since we are fully open-source software, people are free to customize install, which go from subtle changes up to rewriting it entirely.

[dnsguru]

@rishabhnambiar @Supermathie any comments?

[Supermathie]

👍🏻 from me

Since you are doing the hosting and controlling the software there is no need to be on the PSL, right?

In this case we are not hosting, but even if we were (see discourse.group) the PSL inclusion is necessary as it then becomes a security boundary for e.g. SAML, oAuth apps, cookies

EDIT: also, we are not controlling the software, the users (the individual site admins) are.

[rishabhnambiar]

👍 all good from me, for the reasons given above.

[pencilnav]

@xfalcox https://discourse.diy should implement redirect to https://www.discourse.org/contact for easier abuse reporting. See #2680 (comment)

[Supermathie]

redirect

this is now in place 👍