@cas

> if you reply to this telling me to not use vscode i will probably block you, yes that includes suggesting codium or whatever

I'm pretty sure vscodium is basically the same as if you got vscode straight from your distro repos (unless your distro just ships the precompiled binaries straight from microsoft, which is a bad idea™)

Not that I looked much into vscodium these past few years.

@cas that's why I stick to b4 0.14 for dear life. 0.14 was the last version to not have huge vibecoded junk

sooo i tried using the new b4 review TUI for my last U-Boot PR and it was a bit of a disaster. I understand the process being a bit clunky to begin with but the whole process of actually setting up a branch was really involved. It failed to update a bunch of series on pathwork, and the b4 ty emails it generated had completely wrong commit SHAs

I get that the intention is primarily patch review but even for that it feels less like a tool i can utilise to automate the process and more like an imposed workflow that offers little flexibility

the thing that really pissed me off in the end though was realising that b4 review was VIBE CODED, kinda explains everything... This tool had so much potential but i struggle to see now how it will deliver when AI is involved in building it

#kernel #maintainer #b4 #mainline #patchwork #foss

@aelin @cas @craftyguy @oausi maybe regular booting of pmOS every few hours would've

@aelin @craftyguy @oausi @cas yeah not sure faster builders and integrated testing of our packages before getting published would have done much to prevent this from happening.

It was an Alpine package upgrade, not an initramfs upgrade that broke booting.

@craftyguy @oausi @postmarketOS yep you should run edge only if you know that you may get a broken system at any point in time. edge is by definition unstable.

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

AI is going great

🟪 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.

chinchillas

@danirabbit and then you ended up building a whole ubuntu-based distro anyway

Yes, anything is possible as long as you are motivated to do it ^^

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/

#postmarketos #linuxmobile

Read root-owned files as an unprivileged user:

https://github.com/0xdeadbeefnetwork/ssh-keysign-pwn/blob/main/README.md

@chimera Is this using gnome-session 50 too?

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 🎉

https://github.com/OpenRC/openrc/pull/1007

#postmarketos

@zyx @craftyguy Thanks go to @navi for helping me figure this out!