Gabriele Svelto

It looks like we've already reached the "no means yes" stage of "artificial intelligence"

https://gist.github.com/bretonium/291f4388e2de89a43b25c135b44e41f0

I'm trying to do some very high resolution scans of the Bubblegum Crisis OST covers and booklets, but it's hard because my scanner sucks and I have to stitch various bits together. This is the result scaled down from a 12k image. I need to find a way that takes less manual work.

#BubblegumCrisis #RetroAnime #DigitalPreservation

Look at these defeatist headlines by those woke radical leftists at *checks notes* Yahoo! Finance

Pedro Sánchez' refusal to bow to Trump's demands is proof that European politicians don't have to be spineless cowards, most of them simply chose to be

In case you where wondering what most bit-flips look like this was sent by a colleague some time ago.

A few years ago I designed a way to detect bit-flips in Firefox crash reports and last year we deployed an actual memory tester that runs on user machines after the browser crashes. Today I was looking at the data that comes out of these tests and now I'm 100% positive that the heuristic is sound and a lot of the crashes we see are from users with bad memory or similarly flaky hardware. Here's a few numbers to give you an idea of how large the problem is. 🧵 1/5

When talking about the energy consumed by LLMs don't be fooled by arguments focusing solely on the direct power consumption of these models, because they are externalizing a lot of it. Browsers are now doing proof-of-work calculations to access many websites, because websites need to protect themselves from AI scrapers. That takes power! Let that sink in: every computer, tablet or phone on earth is now consuming more power *every time it accesses a webpage* because of "AI".

Don't anthropomorphize LLMs, language is important. Say "the bot generated some text" not "the AI replied". Use "this document contains machine-generated text" not "this work is AI-assisted". See how people squirm when you call out their slop this way.

Toots don't go viral, they escape containment

In the early days of personal computing CPU bugs were so rare as to be newsworthy. The infamous Pentium FDIV bug is remembered by many, and even earlier CPUs had their own issues (the 6502 comes to mind). Nowadays they've become so common that I encounter them routinely while triaging crash reports sent from Firefox users. Given the nature of CPUs you might wonder how these bugs arise, how they manifest and what can and can't be done about them. 🧵 1/31

If you have an Intel Raptor Lake system and you're in the northern hemisphere, chances are that your machine is crashing more often because of the summer heat. I know because I can literally see which EU countries have been affected by heat waves by looking at the locales of Firefox crash reports coming from Raptor Lake systems.