computers

28 Jul 2026

Slashdot

Judge Blocks First State Law That Would Have Banned Prediction Markets

An anonymous reader quotes a report from Ars Technica: Minnesota, the first US state to prohibit prediction markets, was prevented from enforcing the law by a federal court ruling just days before the ban was scheduled to take effect. But while Minnesota was stopped from enforcing a total ban, the state may ultimately be allowed to prohibit some types of prediction-market wagers. The Trump administration and the two largest prediction markets -- Kalshi and Polymarket -- sued Minnesota after the state enacted the law in May. The cases were consolidated, and a ruling (PDF) issued yesterday imposed a preliminary injunction blocking the law that was scheduled to take effect on August 1. Minnesota lawmakers saw prediction markets as indistinguishable from gambling, but the US Commodity Futures Trading Commission (CFTC) argues it has exclusive authority to regulate the platforms under federal law. One of the primary legal questions is whether event contracts are "swaps," which are regulated by the CFTC. Swaps are defined broadly in US law to include contracts in which payment "is dependent on the occurrence, nonoccurrence, or the extent of the occurrence of an event or contingency associated with a potential financial, economic, or commercial consequence." US District Judge Katherine Menendez in the District of Minnesota, a Biden appointee, said Minnesota's total ban on prediction markets is likely to violate US law because many trades on Kalshi and Polymarket are swaps. Menendez wrote: "Specifically, it appears that whether the Minnesota statute is expressly preempted turns on whether the state law attempts to regulate trades in event contracts that qualify as "swaps" within the meaning of the CEA [Commodity Exchange Act]. And there are several examples of event contracts hosted by Kalshi and Polymarket US that fit that definition because they concern the occurrence of events with clear potential economic, financial, or commercial consequences that are neither remote or unattenuated. Kalshi and Polymarket US are designated contract markets, so the CFTC has exclusive jurisdiction to regulate transactions involving those 'swaps.'" Menendez said the CFTC, Kalshi, and Polymarket met their burden of showing they are likely to succeed on the merits, so she issued "a preliminary injunction barring enforcement of Minnesota's prediction market statute until a final decision on the merits is reached." But she said Minnesota may be able to prohibit some types of event contracts offered on Kalshi and Polymarket because not all of them appear to meet the definition of swaps. For example, Menendez doesn't think prediction-market bets on the outcome of Love Island USA meet the legal definition of swaps. Minnesota could continue litigating the case in district court or ask a federal appeals court to overturn the preliminary injunction.

DEF CON Bans Meta-Style 'Pervert Glasses'

DEF CON has banned "Meta-style glasses with recording capabilities," with no exceptions being made even for those with prescription versions. "Be sure to pack non-violating eyewear if you need them," DEF CON said. The Register reports: [The conference's official photo policy] has not been updated since 2023, predating the recent growth of camera-equipped eyewear developed by Meta with EssilorLuxottica under its Ray-Ban and Oakley brands. It states that public photography is permitted but with several caveats that essentially prohibit capturing the image of anyone, except on-stage speakers, unless the photographer obtains consent from the subject(s). "Love to see a 'no pervert glasses' policy at DEF CON," said EFF director of cybersecurity Eva Galperin.

GrapheneOS Defends Data-Wiping Function That Blocked US Border Search

GrapheneOS is defending its duress-password feature after an environmental activist used it to wipe his Pixel phone during a U.S. Customs search and was later indicted for allegedly destroying property under government control. The nonprofit says the operating system is "completely legal," cannot recover the erased data, and should not be weakened with encryption backdoors. Meanwhile, the activist faces up to five years in prison if found guilty. PCMag reports: In a post on Saturday, the Canadian nonprofit behind the operating system, the GrapheneOS Foundation, explained that the software offers a range of features to prevent data extraction. For example, one safeguard is the "auto-reboot timer" that'll reboot a locked device after a set period of time to put the data at rest, leaving all files inside encrypted. The group's post subtly suggests that GrapheneOS phones can withstand law enforcement searches without requiring users to resort to a duress password. "People should carefully consider how to use it in an actual duress situation where there can be physical or legal consequences for wiping the device," the nonprofit wrote. "GrapheneOS doesn't require it to protect data from being extracted from the device, but it takes recovering it completely off the table even with the PIN/password for each profile on the device." On X, the nonprofit has also said it can do nothing to help US law enforcement recover data from Tunick's phone. "Data cannot be recovered after the key derivation material is reliably wiped. It's not possible and there's nothing we can do to assist with it," the group wrote. "Similarly, it's not possible to assist with bypassing encryption because the hardware and software has been designed to prevent it."

27 Jul 2026

OSnews

Windows NT got its name from one of Intel’s failed x86 replacements

Dave Farquhar published an article today about Windows NT 3.1's place in the market when it was originally released, and while the article is interesting and a fun read, it does mention this: Microsoft took its nascent code that it intended to form the base of OS/2 3.0, renamed it Windows New Technology, and eventually released it as Windows NT 3.1. ↫ Dave Farquhar While Microsoft did, in fact, use the "New Technology" branding as a marketing trick, this is not what "NT" originally stood for. Two developers from the original Windows NT development team, Mark Lucovsky and David Thompson, explained all the way back in 2003 that "NT" came from the codename for Intel's then-new RISC platform, the Intel i860 (Raymond Chen confirmed the veracity of their story). The i860 was the first target platform for Windows NT, and it was codenamed "N-10" - NT. Finally, it was time to start writing some code. "We checked the first code pieces in around mid-December 1988," Lucovsky said, "and had a very basic system kind of booting on a simulator of the Intel i860 (which was codenamed "N-Ten") by January." In fact, this is where NT actually got its name, Lucovsky revealed, adding that the "new technology" moniker was added after the fact in a rare spurt of product marketing by the original NT team members. "Originally, we were targeting NT to the Intel i860, a RISC processor that was horribly behind schedule. Because we didn't have any i860 machines in-house to test on, we used an i860 simulator. That's why we called it NT, because it worked on the 'N-Ten.'" ↫ Paul Thurrott The i860 was one of Intel's many attempts over the years to replace x86 with something more modern, but - as would become tradition with Intel and attempting to replace its x86 architecture - it suffered from endless delays, missed targets, and lacklustre performance. It saw only sporadic use in the market, and ended up on the chopping block after only a few years. Intel tried to replace x86 again soon after with Itanium, which suffered an identical fate. Still, the engineers working on the i860 platform in the late '80s and early '90s at Intel can at least take some pride in that to this day, the most popular desktop operating system in the world got its name from the product they developed. Intel's i860 might barely even be worthy of a footnote today, but billions of PC users log into their Windows "N-10" machines every day, unwittingly carrying a torch for the failed x86 replacement.

27 Jul 2026 11:37pm GMT

Ars Technica

Microsoft unveils AI security tools it says outperform competing platforms

Microsoft says tools cost less than competing ones and outperform them, too.

27 Jul 2026 9:56pm GMT

Trump admin exempts SpaceX's Starlink from FCC ban on foreign-made routers

Starlink has a Texas factory but also makes routers in Vietnam.

27 Jul 2026 9:40pm GMT

Epic diarrhea outbreak has 40% of Americans avoiding fruits and veggies

Kennedy has focused on nutrition but has neglected food safety, critics say.

27 Jul 2026 8:42pm GMT

OSnews

The Fedora 45 sausage factory

This is a walkthrough of how Fedora turns source code and packages into the artifacts you download and install. It follows the a package from a packager's git push to a composed release: ISOs, cloud images, container images, and OSTree deployments. ↫ Simon de Vlieger Linux distributions - good ones like Fedora, at least - are really complex operations, with a ton of checks and balances to ensure no git push eventually ends up causing problems on individual users' machines way down the line. The fact so many people involved in this complex web of processes also happen to be volunteers doing all of this out of the goodness of their hearts is amazing. Of course, this doesn't just apply to Fedora, but also the countless other distributions out there, especially those not owned by some giant corporation like IBM. If you're just a casual Fedora user, there's really no reason you have to know or be aware of any of this, but it's still fun and interesting to understand the inner workings of your distribution of choice.

27 Jul 2026 7:33pm GMT

Comanche: Maximum Overkill from 1992 does weird things on Intel processors

Let's do another article about weird code in video games. The original 1992 Comanche release is extremely picky about memory managers. The game refuses to work with EMM emulators and crashes when EMM386 is active. The game may also hang or reboot the system when HIMEM.SYS is not loaded (the problem seems to be system configuration dependent). These issues are clearly noted in the Comanche documentations, but at the same time they're also all signs of a substandard DOS extender. On top of that, the game authors accomplished a remarkable feat: By only loosely following Intel's instructions on how to enter protected mode, NovaLogic managed to write a game which worked on the then-existing 386 and 486 processors, but under some circumstances failed to run on Pentium and later processors. ↫ Michal Necasek at OS/2 Museum As usual, a great read from Michal Nacesek.

27 Jul 2026 7:23pm GMT