[09:26:16] @cosmicalpha I actually would've liked the approach of querying WHOIS just two days ago, but I learned that WHOIS is on it's way out [09:30:31] RDAP is a replacement for WHOIS, in fact as of 2025 operators of gTLD will no longer be required to offer a WHOIS server, only an RDAP one: https://www.icann.org/resources/pages/global-amendment-2023-en [09:31:06] This I just discovered yesterday btw [09:31:27] for us RDAP is even better than WHOIS because it is machine-readable JSON over HTTPS [09:34:16] here's miraheze.org's info over RDAP if interested on what it looks like: https://rdap.publicinterestregistry.org/rdap/domain/miraheze.org?jscard=1 [09:39:57] only problem with RDAP is that not many ccTLDs have implemented it (https://deployment.rdap.org/) but I think the writing is very much on the board here [09:52:49] @pixldev deploy tool saying non-zero exit code in prep isn't always bad. It just means you should pay attention to the output and confirm it's expected before rolling out. [09:53:05] I've noticed them often recently [09:53:12] @agentisai what's it been moaning about [09:53:44] if it is what MacFan said, root owning RequestSSL's folder instead of www-data [09:54:07] the one on test151 was because of merge conflict, according to MacFan as well [09:54:24] Root owning folders will do that [09:54:33] Because it runs as www-data [18:25:34] Fair, though I now added another PoC using RDAP [18:27:35] That's cool [18:27:39] And new [18:27:55] Right?? [18:28:02] If only I had discovered it sooner [18:28:37] Heh [23:04:34] @cosmicalpha not a bad implementation, since we only care about the nameservers [23:04:47] we can roll with that until there's some proper library for this [23:08:21] So, I'll finish the CNAME and rDNS one, then move to make some class for your implementation, and we can _finally_ close T11699