hot take: if you think that you have to fear that contributors will abandon your software project because you ban llm contributions, there might be a bigger problem around
๐ช okay, whoever the fuck is emailing the Rust Foundation, threatening various Rust team members, and threatening to literally stalk people at a public event next week
fuck you
this discussion was supposed to be over and we were supposed to spend the rest of the day distracted, not trying to do even more damage control because you fuckers don't know how to actually do activism
you are an active harm to the causes you support and you're making a lot of work for people who are on the same fucking side as you
responsible disclosure in the future: not dropping the vuln on a Friday afternoon or the weekend.
I dunno who needs to hear this but I got a D in Linux operating systems in college. If youโre passionate about something donโt let some institutional structure tell you that youโre not good at it
New monthly blog post is up!
"postmarketOS in 2026-04: new boot splash"
https://postmarketos.org/blog/2026/05/10/pmOS-update-2026-04/
Read root-owned files as an unprivileged user:
https://github.com/0xdeadbeefnetwork/ssh-keysign-pwn/blob/main/README.md
If a "security researcher" files a GHSA advisory that's obvious slop (e.g. quoting function signatures that don't exist) is it right to somehow make the report public (as way of punishment) or just close it by clicking really hard and getting on with your life?
If the former, is that even possible in GitHub?
Really nice job @fun tracking down **and** fixing a 20 year old bug in #openrc ๐
why would you write if (x) ; else y; instead of if (!x) y;?
(ignore the horrible indentation, itโs 4 spaces then 1 tab then 4 spaces again)