-
From what I’ve heard, which could be wrong since it’s just second-hand anecdotes —- internal Google promotions favor people who start and launch new projects rather than maintain old ones.
If that’s true, Google’s products aren’t subject to cancelation in the way that any given web service is.
https://killedbygoogle.com/
-
CodeRabbit
CodeRabbit: AI Code Reviews for Developers. Revolutionize your code reviews with AI. CodeRabbit offers PR summaries, code walkthroughs, 1-click suggestions, and AST-based analysis. Boost productivity and code quality across all major languages with each PR.
-
The Let's Encrypt community also made some fun references to the Roadrunner cartoons in the early days.
(1) The reference implementation of the ACME server was originally going to be called Anvil, but was renamed to Boulder. (A later lightweight testing implementation is called Pebble.)
(2) A later ACME client was called "dehydrated", after, well, take a look: https://github.com/dehydrated-io/dehydrated
(3) I'm pretty sure I'm forgetting another roadrunner joke here somewhere
-
It's the DNS1 challenge[1]. This reduces the challenge to using some DNS provider with an API supported by a client[2] / [3], as well as the server needing to be able to reach the LE-API. We use this with the CNAME delegation into an irrelevant zone everywhere to get wildcard certificates for our LBs ( meaning: the _acme_challenge.example.com record is just a CNAME for _acme_challenge.dont.ever.use.this.example.com, and the servers just have credentials to modify records in the zone )
1: https://letsencrypt.org/docs/challenge-types/#dns-01-challen...
2: https://eff-certbot.readthedocs.io/en/stable/using.html#dns-...
3: https://github.com/acmesh-official/acme.sh/wiki/dnsapi
