Lmao. Delusional regime.

Finally moved my mini-pc servers to the "under the basement stairs data center". I still have two kubernetes nodes left in my office upstairs, but they're silent (mini pcs as well), so eventually they'll move downstairs as well. But right now it's so quiet here without the drone of the enterprise grade HDDs gnawing my brain

Imagine looking at the Grey zone as a reliable news source lmao

For the first time since 2014 there are no Israeli hostages, alive or dead, being held in Gaza. Those yellow ribbons can come off now 🎗️

@Viss Yeah, I don't go on mastodon as often as I used to. I actually made some pulled chuck roast with bulgogi sauce today, slow cooked, delish stuff, kimchi and all.

Morphine was such a brilliant band. Man, I can't stop listening to them, especially in this weather.

@Viss Oof. I missed that kind of content.

The concept of ClawdBot is cool, but people buy entire Mac minis just for that and I find it completely insane.

@infoseclogger I'm a tokyo night kinda guy

@zcutlip yikes

I friggin love my framework laptop

@dannotdaniel unfortunately battlefield won't run on linux

On the rare occasion I boot up my Windows machine, I’m instantly reminded why it’s such a rare occasion

Now we wait

Trump saying that the iron dome is solely based on American technology is an insane lie

@zcutlip they actually fixed it pretty quickly but they're refusing to acknowledge a low severity vulnerability and pushing back on everything. This is taking to much of too many people's time.

Some people are willing to die on the dumbest hill for a low impact vulnerability instead of just admitting it. The amount of time and energy this ridiculous back-and-forth with a certain open source project about a truly, stupid, input validation vulnerability (THAT THEY HAD ALREADY FIXED!) is really too much. This isn't the first time with those folks. It's incredibly frustrating. I am sure that they are frustrated with me as well. This honestly is not worth my time.

Re yesterday vulnerability drama: we've got a cve id today. We're working out on getting the advisory out and get it published

Yesterday my team member and I disclosed our first vulnerability for 2026. It's in a VERY well known kubernetes infrastructure, an open source project. In an unsurprising turn of events (they did the exact thing to us a year ago) they immediately rejected the issue being a security vulnerability and categorized it as a bug, they've already pushed a PR with a fix. I explained that this was a security vulnerability and not just a bug, since you can bypass their entire solution in a stealthy way by injecting malicious, unsanitized user controlled strings. In their book this isn't a vulnerability, which it obviously is. I've reached out to mitre this morning to get a CVE id

@bp https://www.merriam-webster.com/dictionary/sarcasm