Agreguesi i feed

Version:next-20260824 (linux-next) Released:2026-08-24

Gluons are the quantum 'Gorilla Glue' involved in binding quarks together, ScienceAlert reminds us. But for nearly 50 years, physicists have hunted for "glueballs", exotic particles predicted by this theory of the strong interaction — the only type of particle in nature composed entirely of force mediators: Now, a collaboration working at a collider in Beijing says it has the clearest evidence yet that a known particle called X(2370) is dominated by one of these elusive states... Physicists sifted through the wreckage of high-energy particle collisions to find strong evidence of this glueball, made predominantly of gluons — massless force carriers of the strong interaction between quarks... The new evidence for this exotic, unstable glueball's ephemeral existence comes from a recent preprint on arXiv, presented at the International Conference on High Energy Physics in Brazil... This collaboration uses the Beijing Electron Positron Collider II, a particle accelerator and collider that smashes electrons into their antimatter counterparts, called positrons, to probe perplexing particle physics. The resultant glueball is an "unprecedented form of matter," says Jin Shan, a particle physicist at Nanjing University and one of the research team's leaders. "It not only enables the theory describing strong interactions to pass its most rigorous test, but also vastly expands the boundaries of our understanding of the physical world," he told Fan Chen at South China Morning Post... Previously, in a study published in the journal Physical Review Letters in 2024, the researchers analyzed 10 billion meson decay events. They measured the X(2370) particle's mass and spin parity — a property that dictates its interactions and almost-instantaneous decay — for the first time, finding complete agreement between their experimental values and predictions. Now, they've identified its additional decay modes and determined its flavor-singlet nature, "the most important characteristic of a glueball...." The authors describe their work as the clearest experimental result to emerge from nearly 50 years of glueball searches, supporting the long-standing theoretical prediction that gluons can bind together into a new form of matter. The discovery ""highlights advances in technology and analytical techniques that have recently revealed another decades-in-the-making physics mystery," the article points out. "More experiments are needed to further confirm and constrain the prototypes of the highly esoteric glueball; in other words, more particle smashing."

Read more of this story at Slashdot.

The long legal battle over ownership of Linux "is closer than ever to ending," reports the Register, "after a panel of three judges ruled a claim against IBM and Red Hat isn't valid, and that time has expired for further action." In 2021, an heir to SCO settled with IBM for $14.25 million — a sum that reflects the fact SCO had for years failed to produce strong evidence to back its claims. Another of SCO's legal successors, Xinuos, filed a new claim that IBM should be on the hook because Big Blue knew it did not own the code it contributed to Linux but instead had a non-exclusive license to use it. Xinuos argued that when IBM contributed Project Monterey code to Linux [25 years ago], it breached that license. Xinuos eventually took that argument to the US District Court for the Southern District of New York — and failed to convince it that IBM and Red Hat had a case to answer. Xinuos appealed, and on August 10th the United States Court of Appeals for the Second Circuit decided [PDF] not to revisit the District Court's decision, agreeing that the original legalese governing Project Monterey means it's too late to re-litigate the matter. The Appeals Court also agreed that Xinuos tried to frame the case as a licensing issue but failed, instead arguing that the issue was really about ownership. That ain't all, folks, because Xinuos intends to file a petition to have the case re-heard by the full bench of the Court of Appeals. That hardly ever happens, unless the court finds significant errors or major legal issues that make a rehearing worthwhile. Law firm Kaplan says the Second Circuit has allowed reviews of less than 0.03 percent of the cases it has handled. So perhaps this matter is now close to a final resolution. Back in 2000 Slashdot interviewed one of the presidents of SCO.

Read more of this story at Slashdot.

A Pew Research senior data scientist analyzed 500,000 English-language webpages from the past five years with an AI detection tool to estimate how many were likely written or edited by AI: Of all the pages in this sample, 10% show significant signs of AI authorship... If we filter old webpages out of our samples and look at only the pages published after the release of ChatGPT, the trend is even more pronounced. In the July 2026 snapshot, signs of AI authorship can be found in over one-third of pages published after ChatGPT was released. This is in line with other studies that have shown that large shares of recently published pages on the internet were likely written or substantially edited by AI. AI-authored text is not evenly spread across the web. When ChatGPT was first released, the kinds of linguistic patterns that can signal AI authorship appeared at similar rates across the main top-level web domains (.com, .org, .edu and .gov). But in samples from 2026, around one-in-ten pages with a .com domain show signs of AI authorship — about double the share on .org domains (4.6%), and 10 times the rate on .edu or .gov domains (both around 1%). They even identified specific ways online text has changed, "comparing the internet of today to a snapshot from 2023." Em dashes appear twice as often Oxford commas increased 63%. Words used more frequently by AI (like "delve," "interplay" or "testament") have more than doubled in usage. "Negative parallelism" comparisons ("it's not just X, it's Y") have nearly tripled.

Read more of this story at Slashdot.

3,346 backers pledged $1,198,844 on Kickstarter to build the (modular) handheld Linux computer, the Mecha Comet. It's slightly bigger and heavier than your smartphone, with a 4-inch AMOLED display and loaded up with things like microphones, speakers, a SIM tray, two USB ports and a mini HDMI port. There's three separate kill switches for wifi, microphone and camera — plus a "boot mode" switch for the SD card, and even three pins for instant access to its debug console. It's now expected to ship in October or November (and is still available for preorder). Snap-in extensions include a keyboard (with programmable colors for its backlit keys), a gamepad, and a special IO Breakout that exposes the 40 pogo pins for modules, sensors, and MCUs. They're all open hardware, and founder Shoaib Merchant says "I'm looking forward to more community designs over the upcoming months." He shows the screen in action in a video on Kickstarter, demonstrating native apps like Music, Notes, Settings, and Files — as well as a Terminal app running on its color screen. A Linux correspondent at How-To Geek notes its ships "with a custom, hardware-optimized Linux distro out of the box," so "it's like having a dedicated Linux terminal in your pocket." And they argue the new device "could be the future of Linux smartphones." I should also mention that you don't necessarily have to use the battery; it can power on over USB PD without one. Overall, you're getting the same I/O you'd expect from a computer in a smartphone-like form factor, complete with modular input devices — and it's running Linux under the hood. For me, that's the most innovative gadget I've seen in the Linux hardware space in a long time... It's powerful enough to run most Linux terminal apps, which opens up a lot of possibilities. You're also getting an NPU built right into the SoC, which opens up the possibility for on-device AI workflows — something not possible in budget smartphones. Now, I personally plan to use it for SSHing into my main computer and home lab and operating them remotely. That's also why I'll be putting the LTE modem in the M.2 slot rather than an SSD — mobile data means I can reach my machines even when there's no Wi-Fi around. I also showed it to my partner, and she sees this as the ideal minimalist phone for digital detoxing. There's a built-in media player, a basic notes app, and you can even run Spotify from the terminal if you want.

Read more of this story at Slashdot.

Week 30

This week's icon is for Titouan Real's project:
Era: "Manage your time"

Check out all weekly app icons created so far in the gallery and follow my icon creation adventures as they happen (including sketches) on the Fediverse.

Need icons?

I love designing icons and am happy to contribute them free of charge when your project is Free and Open Source. Join as a community sponsor to maintain a steady supply of app icons to the Linux ecosystem (every little helps!).

It's "radically different from other quantum computers" reports Phys.org. The Helios system uses trapped ions — charged atoms suspended in free space using electromagnetic fields. But it operates with 98 qubits — making it the largest trapped-ion quantum computer built so far. Quantinuum, the company behind the device, is based in Cambridge, U.K., and Broomfield, Colorado. It demonstrated earlier machines operating on 32 qubits in 2023 and 56 qubits in 2025... It relies on two major advances — one in hardware and one in software. First, the four-way X junction lets the system handle several tasks at once rather than one at a time, which is much faster. That was impossible in earlier QCCD [quantum charge-coupled device] machines, which could only move data back and forth in a single line or loop. Second, judicious use of the freedom offered by the two dimensions of the X junction relies on new classical control software called Helios runtime, which plans the smartest, fastest route for moving and processing the data. Together, these represent a substantial advance in the engineering of quantum computers. An important consequence is that Helios can perform computations that cannot be performed even on the largest supercomputers using known methods within reasonable amounts of time and power consumption. This demonstrates the ability of this device and its successors to surpass the computational prowess of classical computers — although their algorithms and hardware are rapidly advancing, too. Having said that, Helios' computations have just been random benchmark tests, so the practical importance of this leap forward is still limited. To perform quantum computations of practical importance in science and commerce, even the most optimistic estimates suggest that quantum computers must be enormously bigger and better — of the order of a million qubits.

Read more of this story at Slashdot.

A class action filed this week accused Amazon's Twitch gaming service of using video streams to fuel its AI products without licensing or obtaining permission, reports Engadget: Earlier this month, Twitch Support posted on X that it added an option to opt out of "having your channel content used to train generative AI content models across Amazon." Shortly after, Twitch hosted an episode of its recurring Patch Notes stream where Mike Minton, the company's chief product officer, said "if it was opt-in, nobody would opt in," when asked by a viewer why the Twitch settings for AI training aren't opt-in but instead enabled by default, requiring users to opt out if they don't want to participate. Now, the latest class action lawsuit claims that Twitch and Amazon committed a breach of contract when the companies decided to use its streamers as "free training stock for separate commercial AI products."

Read more of this story at Slashdot.

This week OpenAI launched a version of ChatGPT exclusively designed for teenagers between the ages of 13 and 17, reports CTV, "saying this version came with stronger protections around content related to mentions of suicide, self-harm and romantic or sexual chats." [Tech analyst Carmi Levy says] "What it's doing is it's using cues, it's sort of watching how you're using the tool, and it's trying to guess your age." Levy said if ChatGPT thinks a person has lied about their age when they first signed up, it will automatically put them into the Teens mode for protection. "It includes those sort of two things: prevent you from having experiences that are age inappropriate, and also add features that are aligned with academics, so that makes it easier to study, makes it less likely for you to cheat on an assignment, provide resources that that that allow you to learn more effectively," he said. Levy reminded users that this is still an application and a web service, which means it's constantly collecting personal information about the users' activities on the device and using the data to estimate their age... In the event a user is talking about self-harm, this new version will block the conversation and suggest additional help or call emergency or mental health services, Levy explained. It would do the same with violent content, eating disorders, engaging in dangerous activities, as well as explicit, sexual or graphic content. "It's using AI again to sort of parse out that conversation: 'are we headed in a in a significant direction? If so, throw up that guardrail, stop it from happening, redirect.'" However, the tech analyst said a number of people who have attempted to bypass the guiderails for research have succeeded in doing so "with a little bit of prompting.... I wouldn't call it 100% safe. That's kind of the catch-22 of the entire AI industry." This will lead parents to think that their children are safer and reduce the oversight on their online activities, which Levy described as a "perverse impact" that is "problematic." "Parents should not assume that OpenAI has their kids' best interests at heart. They should also not assume that these technologies are perfect. They will miss certain things, and they will also engage in what we call false positives," he said. "An adult who's legitimately is in the platform might be tagged as a child because the AI simply got it wrong." OpenAI's blog post says the new mode was designed for "preserving the ability to learn, create, and explore." But CNN notes the move "comes as OpenAI faces a string of lawsuits alleging that inappropriate conversations with ChatGPT contributed to the harm or deaths of young people." [New tools] include nudges for teen users to take a break if they've been active for 90 minutes within a three-hour window. OpenAI is also adding options for teens or parents to set "Quiet Hours" when ChatGPT is unavailable or "Study Hours" where ChatGPT's study mode for learning will be on by default. The company also said it has improved protections to prevent ChatGPT from expressing personal feelings toward a user. And it's adding reminders that caution teens to think twice if they try to upload a private or sensitive image to the chatbot... Nearly a third of American teens use AI chatbots daily, a Pew Research Center study published in December found. ChatGPT was by far the most popular AI chatbot in the survey, with more than half of those teens reporting having used it. Engadget shared this observation from Josh Golin, the executive director of Fairplay, a non-profit advocating for policies to make the internet safer for children. "Most parents, overwhelmingly, do not avail themselves of [parental oversight] tools, in part because they are deliberately made hard to find and use." Golin's group wanted to see testing of the tools first to see whether they led to better outcomes for teenagers. "The way this was just announced feels more like a response aimed at public relations than actual deep thinking about what kind of support [teens] need." And Mashable got a similar quote from Robbie Torney, head of AI/digital assessments for Common Sense Media's Youth AI Safety Institute. OpenAI's teen experience makes important safety commitments, but "What we really need now is evidence that they work, and we need this evidence, including our testing and the testing of others, before anyone, including parents, puts real trust in ChatGPT for Teens." Importantly, Torney said parents shouldn't assume their child is using ChatGPT for Teens. While OpenAI uses age estimation to place users in the age-appropriate version of ChatGPT, it can still mistake a user as older. Parents can be sure their child is using the teen version by linking their ChatGPT account to their child's and implementing OpenAI's parental control features. If a teen has previously lied about their age — and plenty do — they may continue to access the adult version of ChatGPT... Torney said caregivers must enact parental controls to receive notifications from OpenAI should their teen discuss suicide, self-harm, or acts of violence in immediate or dangerous ways... An OpenAI spokesperson said every notification is reviewed by a trained human before it's sent. The company strives to review notifications in under one hour.

Read more of this story at Slashdot.

In recent weeks, I’ve been working on adding key rotation support to flatpak, so that repositories which sign their commits and summary files with a key with an expiry date have a way to push updates to that key to all the clients which use them. Currently that’s not possible without each client manually having its config updated to use the new key data (even if the change in key data is just to bump the expiry date).

In the process I’ve learned a few more things about GPG keys, subkeys, signatures, UIDs, etc., which I thought I might dump here in case it’s useful for someone else (or me, in the future). I don’t claim to be an expert, so I may still be misunderstanding some bits. GPG is complex. One thing which has helped ground things is finding the documentation in RFC 4880 (and related) which defines the GPG packet format.

One thing which keeps flatpak’s use of GPG simple is that it doesn’t use any of the web-of-trust features or trust-on-first-use (TOFU). Its use of GPG is limited to the keyring format (essentially pubring.gpg), for storing and publishing public and private keys, subkeys, signatures, revocations, UIDs; and using them to sign and verify OSTree commits and various repository files (summary, summary.idx, etc.).

Quick primer on the parts of GPG

GPG has keyrings: collections of primary keys. A primary key has public and private/secret parts. The way flatpak uses it, the secret part of a key always stays on the server, and is used to generate signatures. The public part is published by the server and configured in every client using that repository, used to verify the commit signatures. Each client has one keyring per remote it has configured. Typically this contains one primary key, but it could contain several, any of which can be used to verify signatures from that remote.

A key is identified using a fingerprint, a 40-character hex string. It can also be identified using a key ID, which is a substring of the fingerprint. There’s also keygrips, but let’s ignore those.

You can see fingerprints for keys using gpg --list-keys --fingerprint.

A primary key has one or more subkeys (at least in flatpak’s usage). All of these keys have public and private/secret parts as above. Each key has a usage which indicates what GPG will let you use it for, such as certifying, signing, authenticating, encrypting. The primary key is typically used to certify its subkeys by creating cross-certification signatures which bind them to the primary key, forming a short chain of trust — anyone who trusts the primary key should trust a subkey which it cross-certifies.

You can see subkeys as the sub lines using gpg --list-keys --with-subkey-fingerprint. The [SCE], [S], [E] (etc.) fields show the usage flags for a key.

The other usage we care about is signing (flatpak doesn’t use authentication or encryption usages). GPG separates keys by usage to prevent attacks where a key is used for a purpose it’s not intended for, and because keys used for different purposes often need to be treated with different levels of care.

In particular, separating by usage means the private/secret part of the primary key can be kept completely offline, and only brought out in a special key signing ceremony when a new subkey needs to be generated and cross-certified. This reduces the risk of the very valuable primary key, which is the root of every client’s trust in the repository, being leaked.

So, we use a signing subkey for day-to-day signing of OSTree commits. For a big flatpak repository, the private/secret part of this subkey might be kept in a hardware security module, so it can’t be exfiltrated from the server if the server were compromised. But there’s still the risk of a compromised server being used to sign things it shouldn’t (such as malicious apps).

That’s a matter for server security, but we can somewhat mitigate against the possibility of the signing subkey being leaked by setting an expiration date on it. Clients might choose not to trust signatures made by it after that date; and gpg certainly wouldn’t allow it to be used to create new signatures.

The expiry date of a key is shown as an expires field in the gpg --list-keys --with-subkey-fingerprint output.

What happens when the subkey expires? By that point, the administrators should have generated another subkey, cross-certified by the primary key in a key signing ceremony (I assume the ceremony involves cake). The private/secret part of the new subkey needs to stay secret, as before; but the public part needs to be distributed to every client’s keyring, along with the new cross-certification signature from the primary key, so the clients know they can trust signatures made by that subkey.

That’s the bit which flatpak is currently lacking.

So in summary: GPG has keyrings. Keyrings have primary keys. Primary keys have one or more subkeys and cross-certification signatures from the primary key on those subkeys. Each subkey has a usage, but flatpak only uses certify (for the primary key) and sign (for the subkeys). Keys can have expiration dates.

And if you want to see the full contents of a keyring, run gpg --list-keys --with-colons. It’ll output everything (no filtering) in a machine readable format described here (best reference I’ve been able to find), which is sometimes easier to use than remembering which --with-blah option to pass to GPG to get it to show the information you want.

What else does GPG have?

Quite a few things. We’ll ignore the big things which are not relevant to flatpak.

Each primary key also has one or more UIDs. These are like subkeys in that they are cross-certified by the primary key. Each UID is a user identity — typically a name and email address. If you were using GPG in a web of trust, the binding between the primary key and a UID is what you sign that you trust when you sign someone’s key in a key signing party.

The UIDs are listed below each primary key in gpg --list-keys.

Flatpak doesn’t need UIDs, but they are an unavoidable part of GPG — each primary key must have at least one. A flatpak repository will typically put a server contact email address in the UID and then everyone will ignore it.

UIDs can be revoked; for example if someone loses control of the email address in it and wants their friends to no longer trust emails from it. Flatpak currently doesn’t use this.

What else can be revoked? The cross-certification signatures! You may have heard of a GPG revocation certificate. This is a way of revoking an entire primary key. But there’s also a way of revoking a particular cross-certification signature, meaning that the primary key is still valid/trusted, but the owner of the primary key has lost control of one of the subkeys, and that subkey should no longer be trusted. This is different from key expiration, as it’s a statement that something has explicitly gone wrong.

Because of how GPG is built up as a series of packets of different types, a signature revocation is actually a revocation packet appended to the primary key. This means you can re-cross-certify a subkey after revoking it, by appending another cross-certification packet. And even revoke it again after that. Not sure if there’s a use case for this or if it’s just a consequence of the packet format, but this behaviour does play havoc with working out whether to trust a subkey.

Cross-certification signatures can also have an expiration date built into them, separate from the expiration date of the subkey. I’m not sure of the use case for this either, but there must be one.

Some notes on running GPG on the command line

GPG is historically famously hard to use. I feel this has got better in recent years, particularly for scripting it. In particular it’s added a whole load of --quick-blah commands to generate keys, set expiries, etc. from scripts.

One thing which repeatedly tripped me up before I stopped trying to fight it was its concept of a ’homedir’. GPG needs to look for its keyring (and trust database, and various other files) somewhere, and will not run without them, so you always need to pass it a ‘homedir’ to look for them in. By default, this will be ~/.gnupg, so it’s very easy to accidentally end up operating on your personal GPG keyring when you’re trying to do something in a project.

If using GPG as a tool or in a script, I think you should always create a temporary homedir, pass it as gpg --homedir=/path/to/temp and explicitly import whatever keys or context you need into this homedir before doing whatever operation you need.

This is necessary even if ‘all’ you want to do is view a downloaded .gpg keyring, because what GPG displays may be affected by the trust database in its homedir. So to view a downloaded keyring you should still do something like mkdir temp; gpg --homedir=./temp ./path/to/download.gpg.

If you are trying to sign something, you will typically pass the fingerprint or key ID of a primary key to GPG; for example as gpg --local-user 0xfingerprint --sign ./path/to/file. GPG will helpfully use the usage flags of the subkey of that primary key to choose which subkey to sign with. If you want to sign with a specific subkey, you need to suffix the fingerprint with an exclamation mark (!) otherwise GPG will still choose what it thinks is the most appropriate subkey, which might not align with the subkey you carefully chose. This ! suffix format is common throughout the GPG command line interface for when you want to specify a specific subkey.

Sorry

That was more of a braindump than I imagined when I set out to write this. I hope some of it is useful; feedback welcome if I’ve got anything wrong. If any GPG experts fancy reviewing key rotation support in flatpak, the draft implementation is here.

"Iran shut down a British power plant for four days in an unprecedented cyber attack," reports the Telegraph. More details from the BBC: The government said that at no point was there a risk to the UK's energy system, but the Department for Energy Security and Net Zero (DESNZ) has contacted power companies to advise them about the risk of cyber attacks... DESNZ said the incident had affected a small-scale generator and at no point had there been a risk to the wider energy system. The UK's power network has a number of smaller gas generators which provide short-term power when needed. Thanks to Alain Williams (Slashdot reader #2,972) for sharing the news.

Read more of this story at Slashdot.

Slovakia acquired speed cameras to modernize its traffic control-- but there was a surprise. Tom's Hardware cites this story from the Risky Bulletin Newsletter: Unfortunately, the country's national security service, the NBU, has discovered that the cameras have multiple security issues. Firstly, they have SMS-activated Russian backdoors. Secondly, live camera feeds can be accessed by anyone with the device IP, no password necessary... [The cameras] are thought to be rebranded Russian CORDON PRO.M traffic cameras, produced by a St. Petersburg-based firm called Semicon... reportedly bought via a Cyprus-based shell company with fake certifications. Reports also suggest that pressure from the opposition political party in Slovakia led to the NBU investigations... Probably most seriously, in terms of national security, these cameras contain a hardcoded list of Russian phone numbers, which can be used to open a backdoor. An SMS from one of these numbers can open shell and network access... [T]he SecureBoot feature is ineffective, and the web management portal can be accessed, exposing live streams, by anyone with the camera IP. Cameras that have been installed and set up have since been deactivated by the Slovak Ministry of the Interior. Meanwhile, for due diligence, an independent auditor will be called in to confirm the NBU's findings. It is thought that Croatia, and some other countries in Eastern Europe, may have undiscovered issues with traffic control cameras of similar origin.

Read more of this story at Slashdot.

"There is still no sign of economy-wide job destruction," says economist Erik Brynjolfsson. Working with researchers at the Stanford Digital Economy Lab, Brynjolfsson has determined an AI "job apocalypse" is unlikely, reports the Washington Post, "even though it will likely impact entry-level jobs." And Brynjolfsson "predicts that demand for experienced workers such as senior coders will still be high even if AI takes on more routine knowledge and coding work in the future." Earlier this month, Brynjolfsson and his colleagues at the Stanford Digital Economy Lab updated their widely publicized report, "Canaries in the Coal Mine? Six Facts about the Recent Employment Effects of Artificial Intelligence," to reflect that they do not see widespread, economy-wide job displacement associated with AI... Brynjolfsson: What has moved on the upside is productivity. Nonfarm business productivity growth is running over 2 percent, the best sustained stretch since the late-1990s boom... The gains show up years after the investment, and they're starting to show up... By 2030, we will have enormously more capable AI, meaningfully faster productivity growth and an unemployment rate that looks unremarkable — somewhere in its historical range. That surprises people, but it's what the mechanism implies... [T]he technology is becoming much more powerful, and it's going to be even more powerful. Secondly, there are huge implications for business and the economy, including some increases in living standards, but also, potentially, job disruption. And then, thirdly, we must act now to address this gap. We can't just sit back and wait for the tsunami to hit us. And one of the things we can do is put in place institutions, policies and research to make the technology more complementary — using AI to complement people so it creates more jobs. A common misconception among business managers is AI, in order to be effective, has to reduce jobs. That's just not true. You can use AI to increase employment and productivity at the same time. It's kind of a win-win... Right now, tax policy is very skewed toward favoring capital versus labor — and, as a consequence, a lot of entrepreneurs and managers, they're basically being guided by the federal government to replace workers with machines. And I don't think that's necessarily what we'd like to have happen. From an economist's perspective, what you want to be doing is not mimicking and replacing things. You want to be extending and complementing — have humans do new things they never could have done before. He acknowledges "real, persistent and widening" effects on entry-level jobs, with a labor market "closing the on-ramp for people starting their careers... If companies don't hire people at the base of the pyramid, then they're not going to have those people later when they need them." One he points out that one company is instead using AI to speed up its training of young employees.

Read more of this story at Slashdot.

"It began life just a year after SimCity 4's 2003 launch," writes the blog PCGamesN. "Now, over 20 years later, it's still going strong with the arrival of Network Addon Mod update 50." The SimCity 4 Network Addon Mod, or simply 'NAM' among the community, has long been a de facto recommendation to anyone looking to pick up the classic city builder. It's a comprehensive overhaul to the game's transportation and infrastructure networks that combines key fixes with a vast set of additional build pieces such as overpasses, intersections, on-ramps, roundabouts, and so on.... [Y]ou'll be able to place down elements adjacent to one another that might previously have needed a one-tile gap between them. Streets can be dragged diagonally, slope tolerances have been improved, and you can build tunnels with the street network. The new version also includes a fix for the 'Eternal Commuter Loop' bug, which might sound fairly innocuous if you're not deep in the weeds. In actuality, it's a 23-year-long frustration that has plagued modders ever since launch. Essentially, it's a problem with the regional pathfinding across city boundaries in certain layouts, causing your Sims to bounce from location to location in search of work without actually taking up a job in any of them. Your zone demand is ruined, traffic builds to unsustainable levels, and the economy falls to pieces before your very eyes. Until now, the only real solution was to simply avoid building layouts that gave your commuters the chance to loop between locations. Now, by blocking specific neighbor-to-neighbor routes while allowing the rest to run as normal, the problem has been resolved... Equally impressively, the mandatory implementation of the DLL has reduced the size of the NAM codebase "by almost 90% and by more than ten million lines, making it easier to maintain and reducing the chance of bugs." Thanks to long-time Slashdot reader Striek for sharing the news.

Read more of this story at Slashdot.

An anonymous reader shared this report from the blog It's FOSS: Canonical has committed funding to a three-year PhD project focused on building a system that can automatically translate large C codebases into Rust. And they are not alone; UK Research and Innovation is matching their funding for the project, which is set to run through the University of Bristol's Programming Languages Research Group. The PhD is aiming to build an all-encompassing platform that can take a C repository running into hundreds of thousands of lines and translate it into Rust that's "safe, behaviourally correct and maintainable Rust." The work will be carried out by a student, Alex Wood, who will be supported by Professor Meng Wang leading the work, with Dr. Cristina David and Canonical's Jon Seager serving as co-supervisors.

Read more of this story at Slashdot.

Version:7.1.10 (stable) Released:2026-08-23 Source:linux-7.1.10.tar.xz PGP Signature:linux-7.1.10.tar.sign Patch:full (incremental) ChangeLog:ChangeLog-7.1.10

Version:6.18.46 (longterm) Released:2026-08-23 Source:linux-6.18.46.tar.xz PGP Signature:linux-6.18.46.tar.sign Patch:full (incremental) ChangeLog:ChangeLog-6.18.46

Version:6.12.105 (longterm) Released:2026-08-23 Source:linux-6.12.105.tar.xz PGP Signature:linux-6.12.105.tar.sign Patch:full (incremental) ChangeLog:ChangeLog-6.12.105

Version:6.6.153 (longterm) Released:2026-08-23 Source:linux-6.6.153.tar.xz PGP Signature:linux-6.6.153.tar.sign Patch:full (incremental) ChangeLog:ChangeLog-6.6.153

Version:6.1.184 (longterm) Released:2026-08-23 Source:linux-6.1.184.tar.xz PGP Signature:linux-6.1.184.tar.sign Patch:full (incremental) ChangeLog:ChangeLog-6.1.184