uv is a pretty useful band-aid

@WPalant "makes perfect sense when you are in the business of breaking stuff so people have to pay you for fixing it" - https://dzone.com/articles/why-you-should-avoid-jsf

Is there actually a name for the development model where you don’t have a single codebase for all your clients/device model/whatever but rather fork the codebase whenever a new client/device model/whatever comes along? You then continue your development in the new codebase and occasionally cherry pick some of the improvements for the older variants of your codebase (of which you eventually accumulate dozens if not hundreds).

Games That Weren't: How can you possibly squeeze a 32-bit PlayStation CD ROM game into a small Game Boy Color Cartridge? Well, HotGen would attempt to do just that with a conversion of Resident Evil in mid-1999 and to make it as close as possible with similar 3D perspectives using scaled sprites.

https://www.gamesthatwerent.com/2025/12/resident-evil/

#ResidentEvil #GameBoy #GameBoyColor

@wirepair Thanks I'll take a look. Language is less important, I'm more interested in the API design rn.

@algernon You mean the HTML parts? I had a similar problem but IME if the CSS is good HTML is very basic, e.g. this is what I have around sugar.css:

https://github.com/v-p-b/sugardocy/blob/main/sugar-template.html

@algernon @liebach Have you tried sugar.css? It's pretty minimal but customizable.

https://sugar-css.com/

Is there a #logging library that provides nice interfaces (not N config variables) for both:

- "Reliable" logging, when you want to e.g. flush every message immediately because you are debugging
- "Performant" logging, when you don't want to waste time on I/O?

(what's the proper terminology here?)

There must be of course middle-ground, e.g. I imagine errors should always be recorded reliably in many situations, but I imagine that e.g. auto-tweaking performance on debug log level would be reasonable.

[RSS] Windows Exploitation Techniques: Winning Race Conditions with Path Lookups

https://projectzero.google/2025/12/windows-exploitation-techniques.html

[RSS] Thinking Outside The Box [dusted off draft from 2017]

https://projectzero.google/2025/12/thinking-outside-the-box.html

#VirtualBox

@wolf480pl @bagder do you have a link about this? :)

New Project Zero issue:

Adobe DNG SDK: areaSpec overlap miscalculation lead to integer overflow, leading to OOB read/write

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

CVE-2025-64783

🚨 noyb has filed complaints against #TikTok and #Grindr. As it turns out, TikTok even tracks you while you're using other apps. For example, TikTok was able to track a person’s Grindr usage - which allows it to draw conclusions about his sexual orientation and sex life

👉 https://noyb.eu/en/tiktok-unlawfully-tracks-your-shopping-habits-and-your-use-dating-apps

Mitre has just published their top 25 most dangerous software vulnerabilities of 2025

How does #CHERIoT stack up against this list?

5, 7, 8, 11, 14, and 16 are deterministically mitigated with just a recompile.

13 will trap, but is recoverable on a per-compartment basis.

15 is trivial to mitigate with compartmentalisation. Phil Day wrote about this 18 months ago.

6 is mitigated by good capability-based filesystem APIs.

25 is mitigated by our software capability model in the RTOS.

1, 2, 3, 9, 10, 12, 22, and 23 and are not normally applicable on embedded platforms.

That leaves you with a lot more spare brainpower to think about avoiding the remaining seven (4, 17, 18, 19, 20, 21, and 24). The impact of many of these is limited in an environment where there is a programmer model that makes implementing the principles of least privilege and intentional use trivial.

Attempting Cross Translation Unit Taint Analysis for Firefox

https://attackanddefense.dev/2025/12/16/attempting-cross-translation-unit-static-analysis.html

I've never felt one with any other movie character like this. RIP, legend!

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

@joxean Don't give them ideas please!

Public preview of synced passkeys brings the security benefits of MFA with simpler usability, while avoiding the security risks of weaker MFA options like SMS. However, even the simplest MFA can fail when credentials are lost, making account recovery a critical part of the user experience. To improve usability in such cases, we are introducing public preview for account recovery with AI-powered biometric match against government issued IDs across 192 countries.

https://techcommunity.microsoft.com/blog/microsoft-entra-blog/synced-passkeys-and-high-assurance-account-recovery/3627343

@mumblegrepper I wouldn't be surprised if this was the actual strategy...

[RSS] Don't judge an audiobook by its cover: taking over your Amazon account with a Kindle

https://blog.thalium.re/posts/dont-judge-an-audiobook-by-its-cover-taking-over-your-amazon-account-with-a-kindle/