I hope that I'm not stealing the Let's Encrypt staff's thunder, but it has finally happened...
![]()
We asked...
They delivered!
Note: This is not yet in production and thus not yet in force.
I hope that I'm not stealing the Let's Encrypt staff's thunder, but it has finally happened...
![]()
We asked...
They delivered!
Note: This is not yet in production and thus not yet in force.
Yay! Thanks @aarongable and colleagues. 
(Of course this implementation is different from having the new rate limit applied in production, but I'm so happy to see this making progress!)
I noticed that the wording of the current duplicate certificate rate limit has now changed in production.
Still 7 days though.
Which change are you referring to @griffin? The rate limit docs still use phrasing from 2 years ago.
This is the new wording I was meaning:
Aah, I see, the PR mentioned above is active in production
Just that the newly developed rate limit hasn't been enabled yet. I get it now 
Griffin,
You have been truly helpful.
Much appreciated.
Thanks.
Kal Osman
You are quite welcome! 