Re:Chrome 56 Beta: “Not Secure” Warning, Web Bluetooth, and ...
by kuschku on Friday December 09, 2016 @11:43AM
(#13139778)
That's so oddly specific, it's basically every hosted solution you could invent, ever.
If I want to build my own little Github sites, I'd already run into the problem.
And, in fact, I've run into the limits several times before, and had to use startssl certs for far longer than planned because of that.
We're talking about edge-cases within edge-cases at this point: a service that (1) offers HTTPS subdomains (2) hasn't been able to get a rate-limit increase from Let's Encrypt (3) is unwilling to buy a wildcard cert (4) either is growing by hundreds of subdomains a day, or has a significant amount of clients who can't wait a few hours for a cert but won't buy their own. That's so oddly specific, I'm not surprised people aren't going out of their way to cater to it.