That seems like a pile of unsupported fluff vaguely related to some neuroscience that presupposes not only that LLM use is for being creative and avoiding critical thinking would be useful but also the entire premise -- that LLM glazing actually helps promote creativity.
Sounds like "we don't want you to have a portable abstraction between our platform and your automation". Also, their documentation directing users to reference github actions `@master` is classic fly...
I've crashed an RC helicopter because of a similar software issue. Rotorflight is an OSS flight controller, and it has an internal mode for tracking if the vehicle is on the ground or not that isn't always quite accurate at the margins. If you're touching the ground and it's not in ground-handling mode, the I-term in the PID loop winds up really quickly (because the input isn't producing the expected rotation rate) and flips your model on its side.
Betaflight (flight controller for drones, which rotorflight is based on) has a similar function called "air mode" which is common to either disable or set to a switch for aerobatic drones so that they'll still have full rotation rates at zero throttle.
The 787 had three such bugs, in 2015 it was found out if the plane wasn't restarted once every 248 days (2^31 100ths of a second), the AC generation system would shut off, even mid-flight[0].
In 2016 it was found that if the plane wasn't restarted once every 22 days the 3 flight computers could reboot simultaneously, also in mid-flight[1].
In 2020 it was found that if it wasn't restarted at least every 51 days that the stale data monitoring system, and the stall and overspeed horns all stop operating[2].
Some A350s also had an uptime-dependent fault found in 2019[3].
Thanks for writing this. It reminds me of Steve Job's commencement speech at Stanford.
> Again, you can’t connect the dots looking forward; you can only connect them looking backward. So you have to trust that the dots will somehow connect in your future. You have to trust in something — your gut, destiny, life, karma, whatever. This approach has never let me down, and it has made all the difference in my life.
He had an inoperable cancer and wanted to spend his remaining time doing what he wanted rather than sitting in a hospital getting ultimately fruitless treatments. Pancreatic cancer doesn't fuck around. It's not like he died of pneumonia because he loved sleeping outdoors in the rain.
What? That's not at all the case. The type of cancer that Jobs has could be surgically removed. He spent time receiving alternative treatments and delayed his surgery.
> Jobs had a rare form of the cancer, known as neuroendocrine cancer, which grows more slowly and is easier to treat
> GEP-NETs are slow growing tumors that have the potential to be cured surgically if the tumor is removed prior to metastasis.
> Many journalists mentioned and even focused on Jobs’ initial decision to forego conventional treatments and instead use complementary and alternative medical (CAM) therapies, including acupuncture, botanicals, and dietary changes.
Agreed, but it’s remarkable how well this approach worked for him till then. No approach can solve every problem. I wonder if this one, on balance, was the right one for him, or for others.
I enjoyed his recent conversation with Lex, but I lost quite a bit of respect for his opinion on politics when he called the Cambridge Analytica scandal nonsense.
Not sure if you tried prosody[0], but I found it rather powerful and simple to configure, including multiuser chat(muc) and peering. It's written in lua and has a module system so it's easy to extend. In particular I used the dovecot auth module[1] so users could login with their email credentials and I could manage a single user repo.
Yep, Prosody was one of my failed attempts :P I am running everything on a kubernetes cluster, so a maintained helm chart is the first thing I check when running something. I didn't have much luck with XMPP servers with this.
That IMAP auth trick is really awesome thinking BTW, kudos!
Ah interesting, I haven't tried running it on k8s yet. Migrating my mail stack over to k8s has been on my todo list for a little while; should probably get around to it since dovecot and postfix have supported inet sockets for user/domain db and auth for ~12 years now.
Dovecot is really great, and a ton of stuff supports using it as a sasl auth backend (postfix being an important one). I made a simple facade service that feeds it and postfix from couchdb via its dict backend[0] and postfix's tcp_tables[1], then point everything at dovecot for auth. Couch document IDs map really well to email/user, domain, and sieve script lookups; helluva lot simpler than setting up and managing LDAP.
I've been running XMPP/ejabberd for a decade, it's a single service embarking everything you need, including what it takes to do A/V calls (NAT traversal & al.). Nonetheless, it's also the quietest and lowest-profile piece of server software I've ever used. I don't need a container for that, but if you want, there's an official docker image for it. Without going to host millions of concurrent users and needing to distribute the service across multiple physical servers via clustering, I don't see what good an "helm chart" does for you, but then you do you.
Apparently, some DNS query implementations use an "0x20 bit encoding" to add additional random bits to the query ID for poisoning attack resistance.
I've been trying to track down a DNS latency issue in my network and noticed a device doing this and initially thought it was malware, but there is an RFC[0](though expired), and Google announced that they had implemented this for queries from their public DNS servers in 2023[1].
