Just dropped 🔥
Live report.
"The United Kingdom, Australia and Canada have formally recognised the state of Palestine as part of a an effort to revive momentum for a two-state solution, according to a joint statement."
Das hessische #Kultusministerium hat halt einfach einen an der Waffel.
RE: https://mastodon.social/users/RitaWerner/statuses/115236135895723526
Some new developments. Only took me about 9 months to finally figure out 😅
https://0xcats.net/reverse%20engineering/hardware%20hacking/cracking-hp-smartmemory/
I was sharing some pictures with @aral this morning of the places we live in. He shared some from Ireland, and I shared some from Gaza🗝️
It broke my heart to go through my old album of photos of my house before it became rubble bulldozed by the Zionist machinery.
But I have to remind myself of the truth—that it's been leveled to the ground, I have no home, and the criminal perpetrators are still doing this to the remaining homes in the Strip.
One day we'll be free
#IsraelTerroristState
I'm again running my free Rust training course for FOSS developers. It's split into two sessions of two hours. First session is on Wednesday, October 1 at 13-15 UTC. Second sessions is two days later, on Friday, October 3 at 13-15. See https://liw.fi/training/rust-foss-dev/ for more information.
Boosts welcome. Share widely amongst your friends who might be interested.
cancel disney plus, get your kids into firmware reverse engineering
Mesa is working to update our contributor guide. Can you guess why?
Did you guess AI?
Because if you did, you'd be right. I don't want to put anyone on blast here so please don't go digging to find the motivating MR and harass the contributor or anything like that.
But the situation was exactly what you might think. Someone ran ChatGPT on the code and asked it for suggestions on making it more performant. They applied a bunch of the changes against their local branch, tested it, and found that it gave maybe a 0.5-1.0% perf boost in some titles.
That's totally fine. I don't care what tools you use to find a bottleneck. I'll happily take more FPS, no matter who found the issue or how. If some AI assistant helps you find things no one else has found and lets us make drivers faster, great!
But that's not what happened.
What happened next is that they then tried to make it the Mesa project maintainers' job to sort through the shit ChatGPT spit out and decide what's useful and what's not and why the changes helped and whether or not they were correct. The contributor had no no idea and, more importantly, they had no desire to actually learn about the Mesa code-base or the hardware in question. They just wanted to run ChatGPT and send its suggestions towards upstream.
This is not useful. This is not contributing. It's just burning maintainer time sorting through AI hallucinations. We have enough mediocre code to review that comes from actual humans who are actually trying to learn about Mesa and help out. We don't need to add AI shit to the merge request pile. If you don't understand the patch well enough to be able to describe what it does and why it makes things faster, don't submit it.
So now we're making it really clear: If you submit the merge request, you're responsible for the code change as if you typed it yourself. You don't get to claim ignorance and "because the AI said so". It's your responsibility to do due diligence to make sure it's correct and to accurately describe the change in the commit message.
Some things shouldn't have to be explicitly written down but here we are... 😩
OH MY FUCKING GOD
PSA for anyone who interacts with US Woodworking Online Content while Living Outside The USA: “600 grit” is not “P600”, but, like, “P1200”.
THERE’S A SEPARATE IMPERIAL (sorry, US Standard) UNIT FOR SANDPAPER GRIT
i’m so fuckin steamed right now
