Hi @algernon, I made a plugin yesterday to integrate Iocaine into Traefik as middleware. You can find it at https://git.mstar.dev/mstar/traefik-iocaine-middleware
Idk if it’s good, but at least it works with Iocaine’s tcp mode. No idea about Unix socket though. It might.

Happy birthday to trailblazing American computer scientist Frances Elizabeth Allen (1932 – 2020) who made foundational contributions to optimizing compilers, optimizing programs and parallel computing. She was the first woman to become an IBM Fellow, where she worked from 1957 to 2002 and as an emeritus fellow afterwards. She was the first woman to win the Turing Prize.

IBM Research was recruiting teachers 🧵1/n

#printmaking #womenInSTEM #histSci #mathematician #sciart #compsci #mastoArt

“One of my chefs mentioned that if they could cook the steak on the grill they could get it right the first time. This is not an acceptable attitude in the microwave era. Also they’re worried I’m planning on firing all of them. That’s true, but not relevant here.” https://www.colincornaby.me/2025/08/in-the-future-all-food-will-be-cooked-in-a-microwave-and-if-you-cant-deal-with-that-then-you-need-to-get-out-of-the-kitchen/

Join Kagi!

We are looking for a talented and detail-oriented developer to join our marketing team's efforts in creating and maintaining our website, product landing pages, newsletter templates & more. Fully remote.

For details & to apply: https://kagi.peopleforce.io/careers/v/137940-software-developer-web-marketing-systems

#Kagi #FediHire #Remote #Jobs

A Gentle Introduction to Fortran

https://hackaday.com/2025/08/04/a-gentle-introduction-to-fortran/

27 Behind the Scenes Polaroid Snapshots From the Making of the 1995 Cult Classic “Hackers”
https://www.vintag.es/2025/07/hackers-polaroids.html

vibe physics

https://www.youtube.com/watch?v=TMoz3gSXBcY

"you are specifically and intentionally refusing to learn anything, which just seems like a problem." <- This!

Vibecoding can never reach the level of coolness Borland Delphi had

https://oldbytes.space/@gloriouscow/114962468342656021

I love this kind of #bugs, especially when they are features 🤣

#arm64: Linear mapping is mapped at the same static virtual address

https://project-zero.issues.chromium.org/issues/434208461

Does anyone have experience with driving a stepper motor found in simple electronic clocks in both directions?

(img source: https://www.explainthatstuff.com/quartzclockwatch.html )

#electronics

Pwnie Awards 2025 nominations:

https://docs.google.com/document/d/1fynP2jWwrFP9wOQLFQIyFjmq0PDUaJW3e-x5I7yN7ZI/edit

🌪️ TyphoonCon 2026 is set for May 25-29 in Seoul!

Our Call for Papers and Call for Training are now open. Interested in joining our 2026 lineup? Get all the details here:
Call for training: https://typhooncon.com/call-for-training-2026/
Call for papers: https://typhooncon.com/call-for-papers-2026

My mom basically told me the she would like to be a senior UAT tester - as in telling clueless kids how old people can't figure out their UI.

We should definitely have that role!

A fool with a tool is a more dangerous fool.

— u

The Google Project Zero post from a while ago that showed memory safety bugs were more common in new code continues to annoy me because it’s such a clear example of computer scientists doing social science without understanding how to do it.

The root problem is that they are no counting the number of bugs. There is no ground truth that they are able to use. They are counting the number of bugs found. And how are bugs found? When you have some existing technique (static analysis, fuzzing, code review, whatever) that finds that kind of bug.

So their conclusion is ‘bugs that existing techniques are able to find are less likely to appear in code that has already been subject to those techniques’. To which the correct response is ‘well, duh’.

The original Coverity paper, which introduced a large range of brand new static analysis techniques, found a load of bugs in old code. When we started running existing C and C++ code on CHERI, we saw very little correlation between the bugs that we found and the age of the codebase (we found quite a few bugs that were 20+ years old).

If you remove the sample bias, the results are far less clear cut and there are a load of confounding factors. If a memory-safety bug causes random crashing in one in a million runs of a userspace program based on some non-deterministic factor, it’s unlikely that anyone will debug it. If a sequence of actions reliably crashes a kernel, it will probably be fixed. If an attacker finds it and is actively exploiting it, it will almost certainly be fixed. The symptoms and reproducibility of the bug have a huge impact on whether it will be fixed.

Coolest AI project I've seen so far:

https://www.youtube.com/watch?v=IAuapNwJ2vQ

Praise be the Omnissiah!

#wh40k

Hashcat v7.0.0 released https://hashcat.net/forum/thread-13330-post-63567.html#pid63567

Proton’s Lumo AI chatbot: not end-to-end encrypted, not open source

https://pivot-to-ai.com/2025/08/02/protons-lumo-ai-chatbot-not-end-to-end-encrypted-not-open-source/ - text
https://pivottoai.libsyn.com/20250802-protons-lumo-ai-chatbot-not-end-to-end-not-open-source - podcast
https://www.youtube.com/watch?v=HDPZbUPUFyk&list=UU9rJrMVgcXTfa8xuMnbhAEA - video