"what operating system do you use?" "u-boot"

Once they port irssi to u-boot I won't have any reason to boot to linux ever again

Did you know you could play 2048 inside U-Boot?

Video: https://ircb.dersco.re/uploads/funderscore/08b8678f945b925e

Thanks I guess to whoever implemented this \o/

@cas @fizzo yay!

special delivery from @fizzo :D

@samueldr big yes.

@samueldr :( this is not fun

/me hugs

@elly @pj @BrodieOnLinux While it does take time for me to set everything up with sway I always end up with something I actually want to use and that works just fine for all my intents and purposes.

It could be said I like to do stuff manually :)

i think big endian isn't enough there should be a bigger endian

A pretty cool thing about the Fediverse:

It will still be around in a decade. Even two decades.

Usenet still exists. IRC still exists. Email still exists. When you build platforms on open protocols and standards, it doesn't actually matter what corporations try and do to enshittify it. So long as there are people who are still willing to run instances, and users who still want to talk to one another without going through some corporation's platform, it'll still be here.

IMPORTANT UPDATE:

Denmark has scheduled a vote on Chat Control the 14th of October. Despite not wanting to break end-to-end encryption, 🇩🇪 Germany remains both UNDECIDED and critical to defeating the proposal.

If you are German, please take action and contact your Bundestag members today via https://fightchatcontrol.de !

Microsoft attempting to force people to switch from Windows 10 to Windows 11 has somehow resulted in a 10% increase in the market share of Windows 7 https://www.windowscentral.com/microsoft/windows-11/windows-7-usage-skyrockets-as-users-refuse-to-upgrade-to-windows-11-in-wake-of-windows-10-end-of-support

EDIT: Before replying to this post, please see this reply about how apparently the entire increase in Win7 market share is due to like one person in Singapore installing it a zillion times https://chitter.xyz/@Vordus/115301165497461902

💣💣💣

#XDC2025: Full day recordings for Day 1 & 2 are now available on the TU Wien platform, and Day 3 will follow shortly. Individual talk recordings will be available on YouTube in the coming weeks. https://video.tuwien.ac.at/events/xdc

hi, security team, I keep getting fishing emails.

security team: you mean phishing?

no. fishing. I'm pretty certain.

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

@gfxstrand LLMs really do supercharge specific kinds of idiocy and blind faith.

Before, across all my projects, I would get maybe 0.5 dudes a year who just ran a tool, applied the suggestions blindly and tried to have them merged because "${tool} suggested it".

This year I've already seen "IDK why this is here, ${LLM} did it" bunch of times, and it makes me mad as hell.

YOU opened the PR, YOU are responsible.

@ariadne Same thing with issue reports, some people seem to generate them with LLMs now.

If you don't want to spend time writing your issue report, then why should I spend time on fixing your issue? AND waste time reading your bogus report in the process?

@ariadne My small amount of free time has value, I just ask that you respect that.