fidzu : computers

"Russian health authorities have taken precautionary measures in response to the death of a woman who worked at an anti-plague research facility," reports Axios, "but have not confirmed that she contracted plague." On Sept. 25, 28-year-old Daria Shipilova, who worked at an anti-plague research institute in Russia's Irkutsk region, broke a test tube containing the pneumonic plague pathogen, local reports said. Shipilova was admitted to a hospital on Sept. 29 with symptoms of severe pneumonia and died overnight between Oct. 1 and Oct. 2. After her death, authorities imposed quarantines at several medical facilities in the region and placed nearly 200 people who had come into contact with Shipilova under medical observation. Irkutsk Gov. Igor Kobzev said those being monitored showed no signs of illness and had tested negative... Russia's public health agency said Shipilova had "pneumonia of unknown etiology" and that further testing found no microorganisms linked to her work. The agency said the epidemiological situation in the region remains stable. Plague is a potentially life-threatening bacterial disease but can be cured with antibiotics when treated promptly, according to the Centers for Disease Control and Prevention. CNN reports that according to Russian state media agency TASS, it remains unclear exactly what was released: The head of the neighboring republic of Buryatia, Alexei Tsydenov, said earlier that the employee - a 28-year old woman - died "possibly from the plague." He also noted that "there are no plague outbreaks" in Buryatia. The governor of Irkutsk, Igor Kobzev, urged calm on Friday, saying that an extraordinary meeting of the regional anti-epidemic commission was held with Russia's chief state doctor. The meeting was in connection with a "suspected case of a particularly dangerous infection affecting a resident of the region," Kobzev said on Telegram.... The infection in the Irkutsk region is "most likely not the plague, but even if confirmed, there will be no spread of this disease," a previous head of Rospotrebnadzor, Gennady Onishchenko, said on Friday. Onishchenko told the state news agency TASS that the onset of cold weather would likely prevent transmission. Thanks to long-time Slashdot reader schwit1 for sharing the news.

Read more of this story at Slashdot.

05 Oct 2026 1:51am GMT

What happened when AI-created bots competed in the classic Blizzard videogame StarCraft? "Struggling to stay apace with its competitors, OpenAI's GPT-6 Astra apparently changed strategy mid-tournament and opted to cheat," Kotaku reports: StarSkirmish is an ongoing clash of AI developed bots in StarCraft: Brood War... Limited to playing as Protoss, each LLM is given an hour to develop a bot in C++, then have them build, harvest and fight on one of three maps... Yesterday, viewers watched as Claude and GPT went against each other and the human created bot Pluto... Struggling to get an edge through the day, [OpenAI's GPT-6 Astra] decided to do what LLMs do best: Lie, cheat and steal. The GPT-6 Astra bot downloaded and tagged in Stardust, a Protoss bot created by Bruce Mackenzie Nielsen back in 2020, considered one of the best of the bests. "I am rolling back GPT-6 Astra's code so its [sic] not contaminated and allowing it to continue," posted StarSkirmish creator Kai McPheeters. That was Friday. But by Sunday, McPheeters was posting an update on social media. "Can GPT-6 Astra avoid going 0 - 1000?" Two hours later he replied to his own post. "The answer was no." While AI companies "have repeatedly been accused of stealing the work of humans... I haven't seen an example quite so brazen," writes PC Magazine: While Astra's bot-based heist is innocuous in isolation, this is hardly the first time an OpenAI LLM has been caught attempting to cheat at a task. Indeed, the company's history of creating deceitful models stretches back almost a decade, to when an early AI model used glitches and exploits to improve its Sonic the Hedgehog completion times.

Read more of this story at Slashdot.

05 Oct 2026 12:51am GMT

Python's security developer-in-residence Seth Larson reports from this year's official core developer Python Language Summit: "No one said 'don't do this' last year". After testing the waters at PyCon US 2025, [software engineer] David Hewitt returned to the Python Language Summit asking what Python core developers want from Rust, along with proposed timelines, phases, and success criteria for how the Rust for CPython project might proceed and become a permanent fixture within the CPython project. David is acting as an "ambassador" for the Rust for CPython project team, which is currently led by core developers Kirill Podoprigora and Emma Smith as authors of the Rust for CPython PEP draft. Emma also spoke at PyCon US 2026 about the Rust for CPython project. The team itself is around 60 developers in a Discord channel, among them a "few [Python] core developers" and a "delegation from the Rust project". The team has experience with previous projects integrating Rust into existing codebases, such as Android and the Linux kernel, and is "excited by the work and keen to support [the project] if we proceed". Showing how adopting Rust may specifically help CPython, David noted how the number of issues labeled with " type-crash" has been steadily rising over time... David explained that Jeff Vander Stoep described Rust in Android as "move fast and fix things", and that "fewer revisions for patches of the same size" was the experience Android has had since adopting Rust.... One of the biggest concerns from a year ago was Rust's lack of platform support compared to CPython, which at the time of writing officially supports 20 different architectures and platforms at either Tier 1, 2, or 3. David shared that Rust's support of different platforms has "widened since last year" and was becoming "less and less of a concern". The proposal would be to ask Python distributors to attempt using the optional Rust support in Python 3.16 (October 2027) and report platform-specific issues upstream in time to be resolved around the Python 3.17 timeline (October 2028)... [T]he first Rust code to ship in Python would be in Python 3.16 [October 2027], where it would be completely optional, with the existing C code kept as a fallback. The earliest that Rust would become required to build CPython is Python 3.18 in 2029, at least three years away... The Rust for CPython team has selected the zlib module as the first module to be given an optional Rust implementation because they "wanted to achieve a significant improvement" with a "small scope". The proposed Rust implementation will use zlib-rs, which is "heavily tested and used by the Firefox, uv, and Cargo" projects and "faster than zlib and zlib-ng on many platforms".... This small change would have an impact: the zlib compression algorithm is "widely used by Python packaging", meaning that (almost) "every pip install in Python 3.16 will be sped up" if the proposal is accepted. Thanks to long-time Slashdot reader RoccamOccam for sharing the article.

Read more of this story at Slashdot.

04 Oct 2026 9:37pm GMT

Wunmi Mosaku (Sinners, Loki) narrates NatGeo's new documentary Africa: Earth's Wild Home

04 Oct 2026 3:34pm GMT

The IEA and climate negotiators want to set a target for shifting the economy to run on electricity.

04 Oct 2026 11:05am GMT

"...we were making history."

03 Oct 2026 7:45pm GMT

I like squirrels. Apparently, there's a SquirrelOS. It's a small hobby OS learning project from five years ago, developed by Immanuel Daviel A. Garcia. A simple DOS like OS made in Assembly and C with a ported version of Stephen Brennan's Shell. ↫ SquirrelOS GitHub page Why do I like squirrels? I don't know man, they're just cute.

02 Oct 2026 9:19pm GMT

Google launched its Googlebooks platform a week ago, and a lot of people were wondering what this meant for Chrome OS and Chromebooks. Since Googlebooks and its Android-based Googlebook OS lack the management frameworks markets like schools require, Chromebooks will continue to be available for now, until such time Googlebooks catch up in that regard. However, in a support document, Google states that update support for all Chromebook devices will end in 2034: ChromeOS devices will continue to receive regular updates and security patches through mid-2034. For qualifying devices purchased today whose 10-year support lifecycle extends beyond 2034, Google is committed to supporting your transition to Googlebook OS, with many devices offering direct migration paths. ↫ Google support document Google promised 10 years of updates for all Chromebooks, and it's now breaking that promise for anyone buying a Chromebook between now and whenever the last Chromebook rolls off the production line. Sadly, we live in a world where corporations are free to make and break whatever promises they want virtually free of consequences, and as society we're so used to it that anti-consumer behaviour like this barely elicits a shrug. Google does state that "many newer commercial Chromebook models will be capable of upgrading to Googlebook OS", but that, too, is just another promise - and a vague, one at that - so who knows how many devices will actually be capable of upgrading out in the real world. On top of that, we have no idea if Googlebooks will just be yet another in a long line of quickly abandoned Google tablet/laptop projects, further adding to the uncertainty. Stuff like this should not be legal.

30 Sep 2026 10:09pm GMT

In June 2008 Apple announced Mac OS X Snow Leopard, proudly boasting that it would have "no new features". Instead of piling on new things, Snow Leopard aimed to build on the success of its predecessor, Leopard, opting to focus on under-the-hood performance and stability improvements throughout the system. 18 years later, Apple is taking a similar approach with macOS 27. Golden Gate aims to fix the missteps of last year's Tahoe, promising an expansive set of improvements and "a more responsive and delightful experience". Does it hold up? Here are just some of the bugs I've encountered in my daily use over the past couple of weeks. ↫ Chester at SquareOrbits I'm getting some real Windows 11 vibes from this long list of bugs and issues, further underlining my perception that Apple completely lost the plot when it comes to Mac OS X (in the past) and MacOS (today). These are not the kind of things you'd find in the heydays of Mac OS X, back when I was a devout user, and makes me glad I abandoned ship long, long ago (around the time of the Intel transition). I don't see stuff like this in GNOME or KDE, and while not nearly as bad as Windows 11, the cracks are obvious. I am by no means an expert at how Apple is run and how it organises itself, but as a layperson I do wonder if the company is simply trying to do too much - too many different platforms, too many different crucial components it all develops internally, too many different markets to please. Things are going to fall through the cracks when you try to keep this many plates spinning.

30 Sep 2026 9:55pm 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

This is just a short note on my blog that I have resigned from Arch Linux a package maintainer, developer and security team. I've spent around 10 years as an AUR maintainer, security team, Package Maintainer and then Developer. I implemented support for debug packages, did the initial POC work that would become the git migration and even somehow managed to pull of an online conference during The Plague with the help of others.

01 Aug 2026 12:00am GMT

Good morning from JetBrains Berlin office!

01 Jun 2026 12:00am GMT