My first reaction as soon as I saw that .unwrap() in the code snippet. Like hmmmm surely you don't want your whole program crashing just because you exceeded some arbitrary size limit while filling up a list?? Wut. Feels like slapping .unwrap() everywhere is way easier than it should be.

Why isn't it just embedded in the page is my real question 🧐

‪Hmm so it turns out shim_lock is not part of fw but part of the magical UEFI shim that Linux uses as signing workaround, but apparently my firmware does not like it and won't boot it?? This is truly magical... and by magical I mean I want to set my desk on fire.‬

Absolutely love the design of the frontend, great work! Also table-based chall display FTW.

"I got volunteered" sounds like when your boss approaches you with "you really like X right? Nice, we got a bunch of work on X you'll take care of it right?" 😂

Commits:
- 6.15 open_tree_attr: git.kernel.org/pub/scm/linu...
- 6.15 RIP x86 32-bit BIGSMP (+NUMA): git.kernel.org/pub/scm/linu...
- 6.16 RIP uselib: git.kernel.org/pub/scm/linu...
- 6.17 file_{set,get}attr: git.kernel.org/pub/scm/linu...

Noticed this too. They are as big as my thumb on a 27in display, WTF. I feel like one random piece of UI gets bigger every day on YT.

program.why2025.org/why2025/talk...
github.com/ThijsRay/l1t...