fidzu : geek

The number of game pages being created per-day on Itch has doubled, the indie games site announced Saturday on Bluesky. When asked why, they responded: "take a guess." As the gaming news site Aftermath puts it, "the surge has been almost entirely down to AI-created garbage racing onto the platform as the popularity of vibe-coded theft, copycats and machine-built slop explodes." Back in 2024, when the spectre of AI-'created' video games was still in its infancy, indie platform itch.io decided that the best it could do to combat this growing threat was, like Valve has done with Steam, institute a voluntary 'AI' filter when adding new projects to the site. By November 2026, as itch buckles under the weight of new AI-generated 'games' pouring onto the site, that filter is proving about as robust as a wet paper bag.... Shopfronts are being deluged by this shit, and it's making it a terrible user experience for customers. And while in Valve's case there's a compelling case for stronger human moderation of the store, I'm not sure that's a viable option for a relatively tiny, community-run platform like itch... [A]t time of writing I visited the latest releases section and there was still a huge number of clearly AI-generated titles (or titles making extensive use of AI in their visual assets) which made no use of itch's voluntary tag system. The issue here isn't that these games are making money--itch themselves say in a reply that while the number of projects listed has doubled, "the number of downloads and purchases has not"--it's that an inability to combat this surge makes the site worse for every single person using it. It gets harder to find real games, for example, and it also makes the shopfront look like a clearance rack.

Read more of this story at Slashdot.

02 Nov 2026 12:34pm GMT

This DIY e-paper display works in two official ecosystems or on your own server.

02 Nov 2026 12:00pm GMT

"Police continue to blindly trust Flock cameras above and beyond the evidence in front of their own eyes," reports Jalopnik.com. "After incorrectly connecting Rosalyn Crump's car to a shooting that had occurred the previous day, police had her car towed and impounded as evidence, reports Moneywise..." According to WWBT 12 On Your Side, Richmond, Virginia, police didn't have a license plate number for the suspect's car, making it impossible to search Flock's records for that plate. Flock cameras collect more than just license plate information, so police searched for a make, model, color, and approximate model year. Based on this extremely vague description, police zeroed in on Crump's 2012 Hyundai Elantra. Around 2 a.m. they started looking through the windows with flashlights to see what was in plain sight, which isn't technically a "search" - at least, not one that would require a warrant... [Crump was asleep, but left her home to speak to the police officers to tell them they had the wrong car. But they didn't believe her.] Other body cam footage shows an officer expressing doubt that Crump's car is the right one, since child seats and other items inside seem inconsistent with a shooting. Another officer replies, "Don't be surprised if they would have set that up like that." Instead of believing the evidence, or Crump, or interviewing witnesses who could have corroborated her story, police called Seibert's Towing to impound the car... [Later] Police identified a similar-looking car that seemed to be actually connected to the shooting, and released Crump's Elantra. Nobody actually told Crump this until four days later. Seibert's told Moneywise that police didn't actually release the car until then. Either way, they didn't tell her that Seibert's had ripped the front bumper off during the towing process - leaving the car undrivable - until she arrived to pick it up. Seibert's took responsibility for causing the cosmetic damage, and was willing to cover the $2,212.30 bill to paint and replace the bumper cover, fog lights, and wheel liners. Then Crump asked for a full mechanical inspection, which revealed damaged tie rods and ball joints, jacking the bill beyond $6,000. Seibert's says it didn't cause this damage. Regardless of how it occurred, Seibert's insurer and Crump agree that her Hyundai is now a total loss due to the cost of the repairs it needs. It had been drivable, if mechanically worn, before police ordered it towed, damaging it for nothing more than a case of mistaken identity. The president of Seibert's towing told Moneywise that while they'd originally offered $2,200 to repair the bumper damage, Crump must now negotiate with their insurance company. Crump has now resorted to a GoFundMe campaign to attempt to raise $17,100 for rental car expenses, a new car, and the expenses of moving to a different neighborhood. 130 donors have already contributed $7,431. Reached for comment, the Richmond Police Department told local newscasters they "understand that Ms. Crump did not ask to become part of this investigation," and that they recognize the "frustration of having a vehicle towed and subsequently damaged." But they also said they were following a "credible" lead, which is their responsibility. The department "appreciates Ms. Crump's cooperation" (and "sincerely hopes the remaining concerns about her vehicle can be resolved.") The city of Richmond has "already started backing away from Flock before Crump's story aired," reports Moneywise. "Mayor Danny Avula has decided not to renew Richmond's license plate reader deal with Flock, which ends June 30, 2027. As of September, the city had 99 Flock readers on its streets." They note that the Institute for Justice, a public interest law firm in Arlington, Virginia, "has tallied at least 27 cases since 2018" of similar police errors. "In each case, a license plate reader mistake led police to stop, jail or point guns at drivers who'd done nothing wrong. More than half came in 2023 or later."

Read more of this story at Slashdot.

02 Nov 2026 8:34am GMT

From the blog It's FOSS Gregory Kurtzer is no stranger to the Linux world. He created CentOS, and when Red Hat messed it up, he started Rocky Linux as the community replacement. He also co-founded CIQ, the company offering enterprise support around Rocky. His latest project has nothing to do with rebuilding another Linux distro, though. He has built an entirely new operating system kernel, and he didn't write most of the code himself. An AI agent did. Meet Ginux, Linux userspace without Linux underneath... It's an independent, Rust-first x86-64 kernel. Which simply means it is NOT a fork of the Linux kernel. It has its own memory management, scheduler, process model, filesystems, networking, and device support, all written from scratch. The most interesting part is that even though it is not Linux, it is Linux-compatible. Ginux implements the Linux ABI (the binary interface compiled programs use to talk to the kernel), so existing Linux binaries can run on it unmodified. In the project's own terms, Linux is a "personality" that Ginux exposes, not the kernel running underneath... Right now, Ginux runs only in a QEMU virtual machine, with no physical hardware profile, no GPU or NVMe support, and no independent security audit.

Read more of this story at Slashdot.

02 Nov 2026 5:04am GMT

A long flight home from feeding grounds messes with birds' internal clocks.

31 Oct 2026 11:15am GMT

The regulator says Tavneos was approved on the basis of manipulated study data. Should patients still have access to it?

31 Oct 2026 11:02am GMT

Sculpt OS 26.10 brings quite a few new features, like scalable cursors, support for UK keyboards, better webcam support, and more, but the real meat of this release is much tastier. First, Sculpt 26.10 is the first version based on Genode's custom microkernel instead of relying on a 3rd-party kernel. This kernel - designed from the ground up for the needs of Genode and Sculpt OS in particular - is not only more "micro" than any other of the microkernels supported by Genode, it also solves long-standing deficiencies concerning CPU scheduling and kernel-memory management. Sculpt OS finally stands on Genode's own footing! Finally, Sculpt OS 26.10 pays tribute to this year's overall theme of "building bridges" by featuring our software development kit (Goa SDK) running directly on Sculpt OS without virtualization. This entails a wealth of tooling including GCC, Binutils, Git, Sequoia, Expect, Curl, man, Make, and CMake having landed on Genode. Although still young and not time-tested yet, it shows what's possible today and allows us developers to gradually shift more and more development routine into this self-hosted environment, stressing the general-purpose qualities of Genode and motivating further optimizations. ↫ Sculpt OS release 26.10 announcement This new release also completes the transition from XML to Genode's own HID language for configuration, moves from VirtualBox 6 to 7, and upgrades a whole slew of its Linux-based drivers

31 Oct 2026 8:02am GMT

Raymond Chen published another story from the Windows development trenches, this time about what happens when you hold down the power button. If you hold a PC's power button for 12 seconds, it will turn off at the hardware level without notifying the operating system. This is a safety feature so that you can turn of the computer even if the operating system's "Shut down" command isn't working. After eight seconds of the power button being held down, the Windows kernel realizes that the user is trying to do a force-power-off of the system, and it quickly takes a kernel dump that can be uploaded to the Windows Error Reporting service the next time you turn the system on. ↫ Raymond Chen I'm a bit confused by these numbers, because I have never seen a PC take this long to power off when holding down the power button; usually it takes only a few seconds to do so, meaning Windows would never generate said kernel dump. I tried reading through the various ATX specification documents to find more information on this, but then I remembered I'm not an electrical engineer so I have no idea what I'm looking at. The baseline is that ATX always provides standby power to the motherboard, and pressing the power button shorts the power button pin to ground, telling the PSU to power on fully. Pressing the power button if the computer is running tells the operating system to initiate a shutdown (although you can change this behaviour), but if you hold the button down for a certain number of seconds, it forces a power-off. So far, so good; basic information. It seems that the length of time you need to hold down the power button to force a power-off is dependent on the motherboard in question, handled by a microcontroller or some other IC. Virtually every source I can find says this timing is set to about 4-5 seconds, which is quite a bit shorter than the number of seconds given by Chen. Perhaps motherboard manufacturers consider the 12 seconds to be too long, and just do their own thing, regardless what the ATX specification suggests? What further complicates matters is that Chen details how the kernel dumps created after pressing the power button for 8 seconds do, in fact, get sent to Microsoft once the computer turns on again. In fact, he is one of the people who gets to see these dumps and respond to them, so obviously they are indeed rolling in. Does this mean there's a huge number of computers out there that require you to hold down the power button for 12 seconds to force a shutdown that nobody's ever seen? These emergency kernel dumps are internally classified as "long power button hold" (LPBH) failures. One of the pieces of information recorded in these emergency kernel dumps is whether the screen consists entirely of black pixels. Those failures are sub-classified as "black screen LPBH", and they go to a special virtual team for analysis. (I happen to be a member of this black screen LPBH team.) ↫ Raymond Chen What's going on here? Obviously, I'm not going to doubt Chen, so there must be something here I don't quite understand or that I'm missing. The ATX specification might suggest 12 seconds, but could Windows perhaps adapt its kernel dump behaviour - dumping much sooner than 8 seconds - based on the motherboard it's running on, maybe through information provided by the chipset drivers? I would love it if someone more knowledgeable than me can help us unravel this small mystery.

31 Oct 2026 7:54am GMT

From curl 8.12 through 8.16, config files could slice variable values and include other config files without an explicit depth cap. Together, these features let curl simulate any two-counter Minsky program. Under the usual idealization of unbounded strings and resources, this construction was Turing-complete. Curl 8.17.0 added a five-level include cap that breaks this reduction. ↫ Nicolas Seriot Neat.

31 Oct 2026 7:10am GMT

This is a story of how we got from something like this: Failed to deserialize BUILDINFO file: Parser failed with the following error: unknown ^ invalid makepkg build environment option expected `buildflags`, `ccache`, `check`, `color`, `distcc`, `sign`, `makeflags` To this: When the ALPM project started, the goal was fairly simple: Better tooling to interact with the low-level plumbing of Arch Linux Package Management (ALPM). This meant binaries to read/write individual file types, better error messages, extensive specifications and of course exports to common dataformats like JSON. The thing is, although some of us already had experience with low-level dataframe parsing, …

08 Oct 2026 12:00am GMT

Over the last few weeks, we have been doing research on the integration of our official distribution packages when installed on a target system. In this context we have been looking at the current uses of alpm-install-scriptlet(5) files and alpm-hooks(5) in around 120 package source repositories (alpm-source-repo(7)) to better understand the underlying functionality and use-cases these two integrations offer and target. In this article we are going to look at how these two systems work, how Arch Linux is currently using them and attempt to provide suggestions for when to use which. Learning about alpm-hooks(5) and alpm-install-scriptlet(5) files …

09 Aug 2026 12:00am GMT

Good morning from JetBrains Berlin office!

01 Jun 2026 12:00am GMT