@schorsch3000 the PSL is not here to serve just you and Let’s Encrypt. The PSL project has been alive for at least 9 years, and funny enough it seems the entire world just discovered it these months because they are being rate-limited by Let’s Encrypt. Providers had years to request the submission to the PSL but they didn’t, so I hope you don’t mind if we are taking a little bit of extra time to make sure we continue to deliver an affordable service for the entire community.
As one of the contributor to the PSL, I’m thrilled that Let’s Encrypt decided to use the list. This is a sign that they value the project and recognize the quality of the list. And we strive to continue to maintain such level of quality. Quality requires time, and there’s a lot of other things we’re working on about the PSL that will increase the stability of the list and have higher priorities for us.
I understand your needs and believe me, we feel the pressure, but we also want to make sure we don’t make stupid errors in the process. As you probably know, pressure and urgency are bad advisors.
The implications of being in the list should not be underestimated. The list is used by the majority of browser vendors, therefore there may be side effects on how the domain is interpreted that a lot of newly submitters may not be fully aware of. We need to make sure that before they get on the list, they are fully aware of them. We had proof that some people were not, as they were only attracted by the need of bypassing rate-limiting to get a free Let’s Encrypt certificate.
Since your interest seems to be specific about Let’s Encrypt, you may also want to take a look at the comment I posted here. I think the comment equally applies to any PSL request that is LE-centric https://github.com/publicsuffix/list/pull/107#issuecomment-184602303
I appreciate your understanding.