fidzu : computers

An anonymous reader quotes a report from NPR: Billions of dollars are traded every week on the lightly regulated prediction market sites, where users bet on everything from movie reviews to elections to conflicts in the Middle East. Clinical trials are just the latest area where the industry's rapid growth is raising ethical questions. Kalshi claims such bets will provide a new source of information about which drugs will get approved, and what clinical trials will show promising results, which the company says can help investors decide what new drugs to fund. "If you want to ban profiting from the failure of clinical trials, you would start with the stock market, where the financial incentive for this type of profit is orders of magnitude larger," said Kalshi spokesman Jack Such, pointing to stock market short sellers who have profited from clinical trial failures. "While Kalshi and the stock market are the same in this regard, they do differ in one important way: the stock market doesn't give any valuable information to researchers," Such said. Drug trial researchers, though, are far from convinced. David Tsai, who runs clinical trials at a biotech company in the San Francisco Bay Area, started an online petition pushing for such betting to be banned, making the case that betting on drug trials "threatens the very foundation of trust and integrity in biotechnology." Tsai is concerned that the prospect of betting provides those involved with a clinical trial a reason to tamper with the results for a prediction market payout. "If we were running a trial for an oncology drug that requires an infusion, a pharmacist who had placed a bet saying that it's gonna work well, or doesn't work well, could obviously adjust the infusion rate, could adjust the source temperature of the drug," he said. "They could change any number of variables that could obviously have a direct impact [on] how the trial and the data and the patient safety would come out." Another skeptic is Nicholas Zaorsky, a professor of radiation oncology at the Mayo Clinic in Jacksonville, Fla., who has helped run clinical trials and agrees that prediction markets can interfere with the advancement of life-saving drugs. "Prediction markets can be valuable in some settings because they aggregate information, but clinical trials are fundamentally different: investigators, coordinators, and sometimes even participants can directly influence aspects of the outcomes being wagered on," Zaorsky said. "That creates financial incentives that risk undermining trial integrity." Bettors should not be rooting for an experimental medicine to fail just to earn a buck, says Joshua Pederson, the father of a 12-year-old cancer patient enrolled in a clinical trial. "It's a dark idea," he said. "It's quite ghastly." Kalshi, for its part, argues that its prediction markets could help patients track promising medical breakthroughs and clinical trials, enlisting experts including 23andMe founder Anne Wojcicki to make the case. "Most patients don't know about the choices available in clinical trials or which programs are most promising. The opportunity to have an open, transparent dataset about trial probabilities is extremely promising and empowering for people," a white paper sponsored by Kalshi stated.

Read more of this story at Slashdot.

07 Aug 2026 9:00pm GMT

Former U.S. National Cyber Director Chris Inglis says the biggest AI risk isn't sentience but autonomy. "What I'm worried about is that they get to choose what and where they do something, and under what rules they do it," he said, citing recent cases of AI agents from OpenAI, Anthropic, and Meta escaping security sandboxes. He argues developers need stronger safeguards, monitoring, and human accountability, invoking Asimov's idea that protecting humans should come before simply obeying them. The Register reports: "Asimov was right," he said, referring to science fiction author Isaac Asimov and his three laws that were to be followed by robots -- more specifically, AIs, in this case. "The first rule, and we call it the superior role, must be that it's designed not to hurt humans," Inglis said. "Second rule: To obey humans, such that it doesn't achieve agency and aspiration on its own. And the third: To do what humans tell it - and in that order. Instead we've designed them in the exact opposite way." What this means, he explained, is that AI developers created models to "do what humans tell you, obey the humans until it's inconvenient, and then the third one is maybe implied - protect humans - but if that's not built into the DNA, hardwired into it, then we have no right to expect it." Inglis admits it's not possible to hardwire rules into models and still keep their non-deterministic nature. "I would offer that you can tease those out in a highly controlled environment, a true sandbox, where you say, 'Let's put this thing through its paces, and let's back away to see what happens,'" he said. "Maybe you get the equivalent of a mini nuclear explosion in that room, and now you know this thing is capable of that." Inglis thinks another problem with AI is that it's become a commodity. "It's not like you can control it like you can nuclear material," he said. "You can't even specify its properties the way you can for an airplane or for an automobile, as diverse as they might be. Its manifestations are so numerous, so diverse, that as a general matter, you can't actually win by simply saying, "I will design those properties in,'" he added. "You need to do that to some degree, and then make sure that you understand how to watch it, monitor it, make sure you know what it does." [...] Ultimately, humans remain accountable for AI models' actions, according to Inglis. "They remain the source of agency and aspiration. It's possible for them to give broad authority to an AI model and have it run around for 30 hours without further consultation, but they need to know what they've asked it to do, and they need to know what they expect it will deliver in terms of performance on the back end. If they don't, then they're going to get what they deserve, which is the very frequent unpleasant surprise."

Read more of this story at Slashdot.

07 Aug 2026 8:00pm GMT

Fitted with telescopes, the plane did our longest imaging of the Sun's corona.

07 Aug 2026 7:00pm GMT

"Framework has been sending out email notifications to customers alerting of a limited data breach in which customer information was accessed through a Metabase BI service zero-day exploit," writes Slashdot reader DuoDreamer. Data includes customer names, email addresses, phone numbers, and physical addresses. "Framework is investigating whether or not this included Framework for Business customers as well." TechCrunch reports: Framework's spokesperson Eric Schumacher told TechCrunch that the breach affected "all customers," but declined to specify a specific number. Framework computers are relatively niche products, but some estimates say the company sold hundreds of thousands of devices. Metabase disclosed its own breach in a blog post on its official website, where it said that it was hacked by someone using an unknown security flaw, a so-called zero-day. The company said the hackers exploited the bug to give them the ability to access customers' databases stored on Metabase's cloud servers. In its email to customers, Framework also included the email Metabase sent to the company, which says hackers accessed Framework's cloud instance. The computer maker said it investigated the incident and found that hackers had stolen its customers' personal data, but did not include their payment information.

Read more of this story at Slashdot.

07 Aug 2026 7:00pm GMT

19 new maps continue the story from MachineGames' other campaign additions.

07 Aug 2026 6:00pm GMT

DOGE's inflated "Wall of Receipts": 96% of grant savings unverifiable, GAO says.

07 Aug 2026 5:51pm GMT

There's been a small flurry of articles from a variety of sources, all talking about more or less the same thing: Microsoft is trying to explain why Windows 11 is as difficult to develop as it is, in turn justifying why it's become such a mess over the years. I'm picking this one from Windows Central, which is an interview with Microsoft's CVP of Design and Research for Windows and Devices, Marcus Ash. Taking the long, still ongoing transition from the Control Panel to the Settings application as an example, Ash explains why this is such a long and difficult process. Unsurprisingly, Ash says that the reason this has taken so long is that Microsoft prides itself on compatibility with legacy tooling and workflows, so it can't just rush in and modernize everything without first ensuring the modern replacements maintain functionality with what came before. ↫ Zac Bowden at Windows Central This isn't really news to anyone. One of Windows' prized strong points is its often excellent backwards compatibility. This doesn't just apply to individual applications, but also to things like software makers adding settings panels to Control Panel, or complex business applications expecting certain entry points into the Control Panel to exist - and much, much more, all over the operating system. I'm exaggerating, but you can't so much as move a single pixel in the taskbar without breaking some component of some obscure corporate middleware suite from 1999 that somehow still functions as the beating heart of like 187 Fortune 500 companies. Sometimes I wonder if Microsoft is going about this the wrong way entirely. Of course, I have no idea what I'm talking about, but I feel like Microsoft has so man tools at its disposal to deal with this issue that it's not really using to their fullest potential. Specifically, Windows itself has a number of incredibly capable tools in its toolbox to make sure any application ever written for Windows and even DOS, regardless of how many bits it requires, can run. Windows has advanced and highly capable tools for virtualisation and containerisation, and on top of that, Windows NT has a very capable personalities system that feels underutilised, too. Couldn't these tools be harnessed to effectively isolate the entire backwards compatibility problem from the actual Windows operating system people use, and turn them into optional components installed and activated when required by an older application? Isolating backwards compatibility this way would then leave the Windows team much less shackled and more free to improve Windows at every level without having to worry so much about maintaining backwards compatibility. If the components an older application needs are virtualised, containerised, or part of a Windows NT personality and thus frozen in time, the Windows team would be free to work on the "current" version of said component without breaking the application in question. I feel like Microsoft has tried to use these technologies to address backwards compatibility in the past, but in true Microsoft fashion, it always seems to do so halfheartedly, without any real coherent vision behind it. Again, I wish to reiterate I'm by no means qualified enough to make any definitive statements about this, but it sure does feel like Microsoft is underutilising a lot of the tools it already has at its disposal.

06 Aug 2026 10:20pm GMT

Once upon a time in the mysterious lands of Mexico, starting in Fall 1996 and through Spring 1997, I coded a windowed operating system in 32-bit machine code, fit it into a floppy, and jumped in excitement as it boot up. Of course, I knew it was a great thing because you couldn't boot Windows 3.1 or GEM from a floppy disk, but I was very far from knowing how so cool it was. Unfortunately, not a thing I could give away for everyone to see, as it was written for a homebrew computer based on the Am29000 processor. Let's go back to my memories, some notes, and the ride of discovering again what I forgotten. ↫ Óscar Toledo Gutiérrez Trying to summarise this absolute gem of an article and all of the amazing effort and skill involved would be a huge disservice to Óscar Toledo Gutiérrez. I enjoyed this so much. Be sure to try out his custom emulator of a custom computer to run his custom operating system.

06 Aug 2026 9:28pm GMT

Two years ago, I was Porting my JavaScript Game Engine to C for No Reason. I have since found a reason: making a new N64 game! The result is Xibalba 64 - a Wolfenstein 3D-like FPS. Modretro agreed to publish the game as a physical launch title for their M64 (a modern N64 clone), complete with cartridge, packaging and manual! ↫ Dominic Szablewski The article details the development process, from setting up the correct tooling to actually getting the game to play on a real Nintendo 64, and everything in between - including optimising the game to get it to run at a steady 60fps. The biggest issue is that the Nintendo 64 is quite a complex and quirky console, and in order to develop for it, you needed access to Nintendo's officially sanctioned platform library, libultra. These days, though, there's an open source alternative, libdragon, enabling homebrew development. It's awesome that, thanks to the hard work of volunteers, people can still develop top-notch games for something like the Nintendo 64. If we had left it up to Nintendo, we'd be seeing nothing of the sort today.

06 Aug 2026 9:06pm 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

Just trying to answer one simple question: What if the terminal was 3D?

11 May 2026 12:00am GMT