@jschauma A better long-term solution is to actually pay for search so that it doesn't enshittify. Kagi embraced AI and quickly scaled it back when its paid users complained.

@glyph A related problem is that Python packaging has two distinct modes (libraries and scripts) that often use the same "packaging tools" but with very different intended outcomes.

@jerry ...yet

@bagder I still wish that getdns (https://getdnsapi.net/) had taken off well enough to replace c-ares.

@bagder Well, we certainly had a good time with your talk at ICANN! Lots of unexpected DNS topics for us to mull over...

@miek Please please please write these numbers up when you get to the point of real benchmarks. They could help those of us who want to see people be less afraid of DNS over TCP.

@bourgwick @pitchfork Excellent mix of history and tribute.

@jerry Was it as loud in real life as it seems here?

@jerry Please write at least a few paragraphs with the video.

@bagder One possible addition for the future: if you can’t code but can write, consider adding to the docs.

@bagder Proposal: for your followup requests, you say "you can use AI to start your followup, but what you send must not have the standard AI pros and cons, nor silly bullet points; otherwise, it will be ignored". That is, let them use the tool they know, but force them to also do some editing.