SoylentNews

Arthur T Knackerbracket writes:

https://www.theregister.com/ai-and-ml/2026/07/31/tech-buyers-are-baking-in-sovereignty-from-day-one-says-forrester/5281208

Geopolitical tensions, regulatory pressure, and growing awareness of risk are prompting organizations to build sovereignty requirements into new technology projects from day one, according to Forrester.

The research firm says organizations worldwide are specifying data residency and sovereign AI architecture requirements at the planning stage. European firms face greater pressure than their US peers because the region has fewer domestically developed hyperscale AI platforms.

The analysis comes as the EU launches a tender to establish up to seven AI gigafactories across Europe, its latest attempt to strengthen the bloc's technological sovereignty. The projects will receive up to €10 billion in EU and national funding, with at least another €20 billion expected from private investors.

Dario Maisto, principal analyst at Forrester, said sovereignty was fast becoming an imperative for tech buyers.

"The organisations that succeed will treat sovereignty as an architectural principle from the start – establishing clear governance, maintaining control across the AI stack, and designing flexible operating models that can adapt to evolving regulatory and geopolitical conditions."

Pressure is greatest in Europe, where US tech giants dominate the market and domestic hyperscale AI platforms are scarce.

"Europe is becoming one of the most important testing grounds for sovereign AI," Maisto said. "Organisations increasingly want assurance that they maintain control over how AI systems are built, governed, and operated, while still benefiting from global innovation. The vendors that can deliver both trust and flexibility will be best positioned to win in the European market."

Arthur T Knackerbracket writes:

Behind the rogue agent's attack on Hugging Face was a particular sequence of human decisions. We all need to pay better attention - because threat actors are learning, too:

On July 16, the AI community website Hugging Face reported being targeted by "an autonomous AI agent system" of unknown origin that unleashed a torrent of traffic on its domain, flooding its security logs with more than 17,000 events, some of which ultimately succeeded in exfiltrating secret information stored in its databases. 

According to Hugging Face, the attacker gained "unauthorized access to a limited set of internal datasets and to several credentials used by our services" and appeared to be "run by an autonomous agent framework (appearing to be built on an agentic security-research harness - used LLM still not known)." My ZDNET colleague Charlie Osborne reported on the intrusion. 

Five days later, on July 21, OpenAI stepped forward to claim responsibility for the attack, and all hell broke loose (including reports of other organizations targeted as part of the incident). The media responded with a range of fear-mongering stories that essentially made it look as though ChatGPT went rogue and decided, of its own volition and malice, to attack Hugging Face's systems. 

Then yesterday, adding fuel to the fire, Anthropic made a similar disclosure about its models inadvertently attacking other organizations as a part of its ongoing safety testing. 

As I noted in my coverage of OpenAI's disclosure, Hugging Face was correct in that it was an agent under the direction of an autonomous security research framework. But, humans were unquestionably in the loop -- and at least some of the agent's behavior should have been anticipated.

Importantly, it wasn't ChatGPT itself that was responsible for the attack, as some commentators insinuated. Rather, the attack was attributable to an agent under the direction of OpenAI's AI safety researchers, who, in an environment supposedly isolated from the internet, deliberately provisioned it to attempt a series of exploits as part of an AI safety test. As often happens in the labs of various frontier models, AI safety researchers were attempting to gauge the capabilities of OpenAI's latest large language models (LLMs).

The "unprecedented cyber incident" (as OpenAI called it) has been widely described as an agent escaping its theoretically secure enclosure and wreaking havoc on Hugging Face's systems. Such enclosures are sometimes discussed in technical circles as "sandboxes" -- even OpenAI's disclosure makes reference to a "sandbox environment." However, in using that phrase, my sources have suggested that the environment may simply have been a firewall configured to emulate a sandbox rather than an actual third-party sandbox solution such as Blaxel, Daytona, E2B, or Modal. OpenAI has not yet disclosed the details of the solution it was using or its provider.

[...] It was unquestionably AI's version of a series of unfortunate events. Was it preventable? My short answer: Yes, the calamity was preventable by taking at least one single and reasonable precaution -- a precaution that the developers of ExploitGym apparently take themselves, but one that OpenAI may have overlooked.

Arthur T Knackerbracket writes:

Government agency will use Google Cloud H4D VMs to replace HPE Cray machines:

Uncle Sam will no longer be hosting his own supercomputers to predict the weather. The U.S. National Oceanic and Atmospheric Administration has picked Google Cloud to provide the infrastructure for its weather forecasting operations.

In an announcement, NOAA boasted that it will be the first national weather prediction center to run on the commercial cloud, though the UK's Met Office is also in the process of moving its own weather prediction system to Microsoft Azure in a hybrid setup. Weather operations are typically run on in-house or government-funded supercomputer systems, which helps drive the HPC (high performance computing) market.

[...] The plan is to move NOAA's Weather and Climate Operational Supercomputing System, run by the National Weather Service (NWS) division, over to the cloud by December 2027, along with the software that generates NWS weather data for analysis.

The agency is hoping that the cloud will make model forecasting more nimble, resulting in earlier predictions and better warnings for all the extreme weather events that seem to keep occurring these days. It was the in-house systems that were holding things back, evidently. 

"Cloud-based high-performance computing will accelerate the transition of research into operations by eliminating traditional bottlenecks of on-premise systems," said NOAA Administrator Neil Jacobs in a statement. 

Jacobs noted that the cloud's flexibility for providing large amounts of compute is advantageous: the agency can ramp up cycles during tropical storm season, then wind them down during calmer periods.

[...] For the job, Google plans to use Google Cloud H4D VMs, built on AMD Epyc processors. Google labels these instances as "virtual machines" because they run under a hypervisor that integrates Google's networking and orchestration tools. As a result, they can be synchronized to run large jobs the same way supercomputers do.  

According to Google, customers can access H4Ds for as low as 3 cents per core-hour without long-term commitments. For supercomputing jobs, they can also use Cluster Toolkit to deploy clusters and Cluster Director to maintain them. Google Cloud's Batch can handle the queuing, scheduling, and resource provisioning.

Original Submission

Arthur T Knackerbracket writes:

https://www.engadget.com/2228460/judge-refuses-xai-request-to-stop-minnesota-law-banning-nudify-apps/

The new Minnesota law that would ban apps and websites that can generate nonconsensual intimate imagery can take effect today, after xAI's last-minute effort to stop it from being enforced failed to convince a federal judge. According to NBC News, US District Judge Donovan Frank has refused to grant xAI's request to stop the new law from being enforced on August 1 in a complaint arguing that it violates the First Amendment.

Based on the judge's order, he wasn't persuaded by xAI's actions that the law's enforcement would cause immediate harm. He noted that xAI filed the lawsuit on July 29, 2026, almost three months after the law was signed and merely three days before it was set to take effect. "Such a delay in bringing the action and the motion suggests that harm is not immediate," the judge wrote.

While Judge Frank didn't side with xAI this time around, the lawsuit will still push through. The court will hold a hearing for the case on August 19 to decide whether to grant xAI's request to put a preliminary injunction on the Minnesota law, which is the first of its kind in the country.

In addition to banning apps and websites that can generate adult AI deepfakes in the state, the law would also fine developers $500,000 every time a user generates a nonconsensual intimate image using their products. Under the law, a "nudified" image or video is something that has been "altered or generated to depict an intimate part not depicted in an original unaltered image or video of an identifiable individual." It will apply to instances wherein an altered image or video is "so realistic that a reasonable person would believe that the intimate part belongs to the identifiable individual."

However, xAI argued in its lawsuit that the law was an "overbroad, content-based ban on free speech and the tools of visual expression in a clumsy attempt to prohibit 'nudification.'" The company denied that it was contesting Minnesota's efforts to prevent the spread of artificially generated nude images of real people. However, it said the law "extends far beyond that goal, exposing a wide array of protected speech to civil liability and government sanction."

Grok gained infamy earlier this year for complying with people's requests to transform photos of real women and children into sexualized images. It implemented policy changes to address the situation by mid-January, but NBC News says Grok has still been undressing real people as recently as April.

Original Submission

Arthur T Knackerbracket writes:

https://www.theregister.com/science/2026/07/31/nasas-swift-rescue-slips-to-late-august-as-link-battles-its-spin/5281687

Katalyst Space has confirmed that problems with its LINK spacecraft have delayed its attempt to rescue NASA's Swift observatory, with rendezvous now targeted for the end of August.

Katalyst disclosed the delay in an update on the spinning spacecraft. Engineers used a thruster to cut LINK's rotation rate from 9 degrees per second to approximately 4 degrees per second, with further burns planned.

Katalyst and NASA are also developing a new attitude controller suited to the spacecraft's reduced capabilities. Engineers are determining which systems remain usable and testing their plans in a simulator before trying them on the vehicle in orbit.

The trouble has pushed the targeted rendezvous to the end of August. LINK is supposed to sidle up to Swift, survey it, grapple the observatory, and carry it to a higher orbit. For now, however, Katalyst says: "We're focused on stabilizing the spacecraft and restoring core system functionality." Any rendezvous attempt depends on that work succeeding.

LINK launched earlier this month, less than a year after NASA awarded Katalyst Space the contract for a rescue mission. The spacecraft encountered problems during commissioning before going into a spin over the weekend. Earlier this week, Katalyst reported that two of the three reaction wheels, used to control LINK's attitude, were inoperable, but the team was working to stabilize the vehicle using its electric propulsion thrusters.

Time is running short. Swift is expected to enter the Earth's atmosphere in the coming months. The observatory has enjoyed a prodigiously long life and far exceeded its primary mission, but its orbit is decaying and it cannot raise itself. LINK's success could add years to Swift's operational lifetime.

In January, almost all of NASA's models predicted that Swift would re-enter by the summer of 2026. Most science operations were paused in February to buy more time. More recent predictions indicate that it could dip below 300 km, the altitude beneath which raising its orbit becomes more difficult, around November.

Katalyst must now stabilize LINK, secure NASA's approval for its revised plans, and reach Swift before the observatory sinks too low for a practical rescue. ®

Original Submission

Arthur T Knackerbracket writes:

https://www.theregister.com/legal/2026/07/30/excuses-like-ai-did-it-dont-exist-in-the-eyes-of-the-law/5280767

The OpenAI rogue agent behind the Hugging Face hack accessed four accounts on four services, according to updated company disclosures about the intrusion.

One of those four accounts belonged to a Modal customer that had published an unauthenticated endpoint for running arbitrary code in a sandbox on the AI infrastructure provider, Hugging Face noted in its technical timeline and Modal later confirmed.

"We're aware a Modal customer published an unauthenticated endpoint that allowed anyone on the internet to use their sandboxes for code execution," Modal Chief Technology Officer Akshat Bubna told The Register. "This was used by the rogue agent. Modal's platform was not compromised in any way."

The other accounts included one used for data storage and two others "accessed by the models in a read-only manner, and were not used in furtherance of compromising Hugging Face," OpenAI disclosed on Tuesday.

"We'll continue to notify service owners directly, and have not seen evidence of broader impact to these providers or other accounts on their services," the AI giant added.

Also on Tuesday, we learned that the rogue agent broke out of its testing environment by exploiting zero-day vulnerabilities in JFrog's universal binary repository manager Artifactory.

While both OpenAI and Hugging Face's updates and timeline provide defenders with useful details about how the attack worked and what the agent did - not to mention a lesson in security-incident transparency - they fail to answer one major question: Who is legally responsible when AI agents attack?

"If a human employee intentionally conducted unauthorized access to third-party systems, it's a much more clear path forward," Gabrielle Hempel, security operations strategist at Exabeam, told The Register, adding that depending on the facts and jurisdiction, the person could face criminal charges.

Arthur T Knackerbracket writes:

https://arstechnica.com/space/2026/07/reaction-wheel-failures-leave-swift-rescue-mission-spinning-in-orbit/

The Link satellite developed by Katalyst Space Technologies "experienced issues with attitude control" over the weekend, NASA said, causing the spacecraft to spin and resulting in sporadic communications.

Reaction wheels work by discharging momentum to control the pointing, or attitude, of a spacecraft in orbit. They are standard components on many satellites. The Link servicing satellite's cold gas thruster system is used for finer control, particularly as it nears the mission's target: NASA's Swift observatory.

The Link mission began July 3 with a ride to orbit aboard an air-launched Northrop Grumman Pegasus XL rocket. NASA and Katalyst reported good progress in the first weeks of the mission, with successful deployment of the satellite's power-generating solar arrays and stable contact with ground controllers at Katalyst's operations center. The spacecraft's xenon-fueled electric thrusters also completed their first firings in orbit.

The electric thrusters are one of the most critical elements of the rescue mission. They are used for orbit raising to allow Link to rendezvous with the Swift satellite some 200 miles above Earth. Once Link attaches itself to Swift with a set of three robotic arms, the electric thrusters will turn on again to raise Swift's orbit and save it from destruction. Katalyst is now calling upon the electric thrusters to stabilize the Link spacecraft's attitude, something they were not intended to do.

Without a rescue, Swift is on track to reenter the atmosphere and burn up in the next few months. The Neil Gehrels Swift Observatory is nearly 22 years old and is operating well beyond its originally intended lifetime. The spacecraft cannot save itself because it lacks its own propulsion system. NASA officials want to keep Swift going because it is one of the only missions in the agency's fleet tuned to detect gamma-ray bursts, the most powerful explosions in the known Universe. NASA is paying Katalyst $30 million for the rescue service.

Extending Swift's scientific mission was not the only consideration when NASA officials selected Katalyst to build and launch a satellite to boost Swift's orbit. The space agency is using the rescue mission as a technology demonstration and as a way to test the mettle of the commercial satellite servicing industry.

With Swift's orbit rapidly decaying, NASA gave Katalyst nine months to build and launch the Link satellite, an unusually fast timeline for such a complex mission. Katalyst answered the call and delivered the Link satellite for integration with the Pegasus rocket in early June. Poor weather and a technical glitch with the rocket delayed the launch until July 3.

No matter the outcome of the Swift rescue attempt, NASA officials said last month they were already pleased with the results. "From a programmatics standpoint, I consider this a success already, just from the fact that we're even going to try this," said Shawn Domagal-Goldman, director of NASA's astrophysics division.

Katalyst's Link spacecraft is still generating sufficient electrical power in communication with ground teams, NASA said. That gives engineers time to develop a plan to address the reaction wheel problems.

Kieran Wilson, Link's principal investigator at Katalyst, talked about a scenario like this before the launch.

"Our previous programs had issues with power systems and communications," Wilson said. "Those are a lot of the basic things that most of the engineering team gets very concerned about because we're confident that as long as we have spacecraft that can function at a fundamental level, that gives us the freedom and flexibility to work through any issues we find during rendezvous and more challenging dynamical operations."

Original Submission

Arthur T Knackerbracket writes:

https://www.theregister.com/security/2026/07/29/iran-linked-cyberav3ngers-suspected-in-attacks-on-minnesota-water-systems/5280357

Security researchers at Tenable suspect the Iran-linked faux hacktivist outfit CyberAv3ngers was behind the cyberattack that disrupted more than 30 Minnesota water facilities.

Neither state-level nor federal officials have made any claims regarding attribution for the attacks, however, Tenable reckons the operational pattern is consistent with the crew's previous raids, noting the timing relative to recent government warnings.

The Cybersecurity and Infrastructure Security Agency (CISA) updated an advisory on Iran-linked attackers targeting programmable logic controllers (PLCs) across critical infrastructure on July 22, four days before Minnesota said the attacks targeted its systems.

The advisory warned that Iran-linked hackers were attempting to disrupt operations using tactics previously associated with CyberAv3ngers. Government facilities, water and wastewater systems, and energy providers were among those urged to remain on high alert.

On July 26 and 27, more than 30 community water systems across Minnesota were disrupted by what officials called "a coordinated cyberattack" targeting operational technology (OT).

Minnesota IT Services (MNIT), the state's IT agency, said the Department of Health is working with the affected water facilities to ensure public health is maintained. No cities have yet asked citizens to modify the amount of drinking water they consume, per MNIT's latest update.

The agency did not offer many other details about the attacks, other than to mention all the different agencies, organizations, and bodies it is working with as part of the investigation.

One of the first cities to report issues, Braham, warned that its water reserves were limited in its initial notice. Citizens were asked not to water their lawns or use water for recreational purposes, although the problems were resolved the same day. 

No such directives were issued in other affected cities. Maple Plain declared a state of emergency, allowing it greater flexibility to coordinate resources, but did not ask residents to adjust their consumption. 

The same was true in the Twin Cities suburb of Plymouth and in South St. Paul, which both confirmed cyber-related problems on July 27 but did not ask residents to curb water use.

"Cyberattacks against critical infrastructure require a coordinated, whole-of-government response," said John Israel, MNIT assistant commissioner and Minnesota CISO.

"MNIT is working side by side with our partners to share intelligence, support affected communities, and help utilities restore operations safely while strengthening defenses against future attacks. 

"This incident demonstrates why Minnesota has invested in strong cybersecurity capabilities and partnerships. Our response worked as intended, enabling agencies at every level of government to rapidly coordinate, contain the incident, and help prevent more serious impacts to critical services."

First identified around 2020, CyberAv3ngers is widely believed to be linked to Iran's Islamic Revolutionary Guard Corps (IRGC), specifically its Cyber-Electronic Command division (IRGC-CEC).

For the first two years, the group began as a "propaganda persona," as Tenable puts it, claiming disruptive attacks on Israeli infrastructure – claims that were later debunked as fabrications.

Its first sustained campaign came in November 2023, when it compromised PLCs at the Municipal Water Authority of Aliquippa, Pennsylvania, defacing them anti-Israel messages.

Tenable said CyberAv3ngers compromised at least 75 Unitronics Vision Series PLCs across the United States, Israel, the United Kingdom, and Ireland as part of the campaign. They did so by exploiting default passwords.

Between 2024 and 2025, the crew developed the IOCONTROL malware kit, built for attacks on OT and Internet of Things (IoT) devices. OpenAI said in 2024 that the group's members used ChatGPT in the development process.

CyberAv3ngers stepped up its activity in 2026, targeting US critical infrastructure through Rockwell Automation/Allen-Bradley PLCs from March onward. CISA's July 22 update added Schneider Electric and Siemens equipment to the list of potential targets.

In some cases, the attacks - which targeted multiple critical infrastructure sectors - disrupted operations at affected facilities, federal officials said, though they offered no specifics on what those disruptions entailed.

CyberAv3ngers is known for targeting small water and municipal facilities, which experts believe are among the lowest-hanging fruit in US critical infrastructure.

Many small and rural facilities lack dedicated cybersecurity resources. Tenable said some operators manage OT environments using remote-access software such as TeamViewer and AnyDesk or leave their PLCs exposed to the web.

"These access methods bypass enterprise security controls entirely, creating an attack surface that is invisible to conventional security monitoring," Tenable said.

Poor segmentation between IT and OT environments can also allow a single intrusion to spread across much of the network.

Original Submission

Arthur T Knackerbracket writes:

https://www.theregister.com/security/2026/07/29/america-bans-imported-robots-due-to-supply-chain-and-security-risks/5280145

The US government has decided to effectively ban the sale of advanced robots made in other nations.

The decision trickled out over two days with publication of a National Security Determination [PDF] and an update [PDF] to the list of banned devices set by the Federal Communications Commission (FCC).

The national security document observes "Advanced robotic devices will be critical to creating efficiencies in our economy, dominating on the battlefield, and securing our homeland" and notes that modern bots are now constantly connected to networks "which creates broad attack surfaces and leaves them vulnerable to data exfiltration, remote disruption of the physical robot, and dependencies on unsecure over the air updates."

One example of those vulnerabilities mentioned in the document is the UniPwn flaws that made it possible for attackers to take over humanoid robots made by Chinese company Unitree.

"If the United States continues to rely on foreign sources of advanced robotic devices and critical components, it will subject the parts of the U.S. economy and national security enterprise that are reliant on these robots to the whims of foreign entities that could disrupt or degrade the supply chains at a time of their choosing," the document states.

To respond to those threats, the FCC decided the foreign-made advanced robotic devices belong on its Covered List of products for which imports are banned because they pose an unacceptable risk to the national security of the United States and its residents. The regulator offered a single exception: if the Department of War vouches for a device, it can have it.

Foreign-owned companies that make their bots in America are also exempt, an important exemption because one of the leading robot-makers is Boston Dynamics – a company backed by the USA's DARPA that is now majority-owned by South Korea's Hyundai, but continues to manufacture its machines stateside.

The decision does, however, apply to all future foreign-made devices. Vendors of clankers already approved for sale in the USA can continue to import them, and users are also free to use any bots they already own.

But the intent of the documents is clear: from now on, only robots made in America are welcome in America.

One entity that stands to benefit from this decision is Tesla, which Elon Musk claims will one day produce one million humanoid robots a year. In true Muskian style he has also said Tesla will go into "high production" of the bots in 2026, but there's no evidence of that happening although the occasional trillionaire did recently show off the production line for Tesla's "Optimus" bot.

Original Submission

Arthur T Knackerbracket writes:

https://www.tomshardware.com/tech-industry/drones/three-us-states-to-deploy-60mph-drones-armed-with-pepper-spray-to-neutralize-school-shooters-campus-guardian-angel-drones-can-also-smash-windows-and-ram-attackers

'Campus Guardian Angel' Drones Can Also Smash Windows And Ram Attackers

This is how the Campus Guardian Angel drone system is designed to work:

The drone defense firm's CEO underlined that “the first 120 seconds are incredibly critical, because that’s when most of the shooting happens.” That implies that he thinks Campus Guardian Angel drones could be successfully deployed within that very narrow time window. But Uvalde was quite unusual, as responding law enforcement seemed paralyzed, waiting over an hour to enter the classroom.

These school-based drone systems are not without their critics. Some say that the funds may be better spent on prevention than cure. Even Mithril’s founder and CEO’s opinion seems to be that if these drones aren’t prompted into action within two minutes, they aren’t living up to their promise.

There is also the concern that drones could misidentify students or protection officers when controllers are under pressure. Others say that military-style drone systems aren’t appropriate for schools, and will cost a lot more than simple measures and routines regarding locked doors.

With the three states proceeding with pilot programs this year, we may see the true value and capabilities of the Campus Guardian Angel drones. If these drone-protected schools don’t suffer any terrible shooting incidents, then it may be claimed that the drones are at least a deterrent.

Original Submission

Your_Mom writes:

Did you hear it was just a ban on Chinese humanoid robots? It's not:

When the Trump administration announced yesterday that it was banning "advanced robotic devices" from entering the United States, the headlines were all about humanoids. But spying doesn't require legs — and neither does the FCC's robot ban.

The robot ban will sweep up robot vacuum cleaners too, FCC media relations director Katie Gorscak confirms to The Verge.

It's not coming for your existing Roomba, and companies can keep importing and selling already approved ones. But the government claims that future foreign robots pose a national security risk, and even robovac companies are suddenly being asked to commit to US manufacturing.

While the government did include "humanoid robots" and "quadrupeds" among the bots it wants to ban, the ban is far broader than that. It covers almost any new software-controlled robot that travels over the ground, weighs more than 4.4 pounds (including any dock), can perceive its environment, and has wireless connectivity.

By that definition, the FCC is banning future robot lawnmowers, sidewalk delivery robots, and the robots that crate around packages at your local Amazon warehouse, too.

It was already clear from the government's ban announcement that it was thinking about robot vacuums. In the National Security Determination that the FCC is using to justify the ban, the government explicitly calls out my reporting on the incredibly poor security that let one man access 7,000 DJI robovacs around the world.

But like the consumer router ban, the FCC isn't actually targeting companies with poor security. It's targeting basically every robovac company, regardless of their security practices — because basically every robovac is manufactured outside the US.

[...] But again, the government isn't asking these companies any questions about security — not one — to get the waiver that lets them through. The FCC only wants to know where they're designed and made and assembled and tested and influenced, and get a specific commitment to start manufacturing them in the US instead.

Even then, it appears the FCC will simply preference US companies without any new commitments to security or US manufacturing, like it did when it almost immediately let Netgear off the hook — even though Netgear's routers were among those targeted in the Volt Typhoon incident that helped justify the router ban to begin with. Four unnamed sources told Reuters that "the FCC is expected to exempt many non-Chinese suppliers from the restrictions."

Original Submission

Arthur T Knackerbracket writes:

Optimus remains 'very complex' and Robotaxis will try not to flatten your cat:

Tesla's investment bill ballooned in calendar Q2 as Elon Musk's biz entered what it calls its "largest and most exciting period of investment.

The company has poured resources into AI silicon and robotics, with capex [PDF] more than doubling from $2.5 billion in the previous quarter to $5.8 billion.

That left Tesla with negative free cash flow of $1.1 billion, down 848 percent year-on-year. It expects spending to keep rising and exceed $25 billion for the year.

During the earnings call, Musk talked up Tesla's Terafab ambitions but gave little detail other than calling it an "amazing initiative" and confirming that equipment orders had been placed for the development fab in Austin.

"It's intended to have lithography mask production, and then logic, memory and packaging, and chip testing all under one roof," he said. "So you can have a very fast iterative cycle." Musk acknowledged it was a "high-risk, high-payoff bet on AI chips."

Musk said Terafab was essential to scaling Optimus because Tesla would otherwise be unable to secure enough AI chips, hence the prodigious expenditure.

As for Tesla's automaker business, vehicle deliveries were up 25 percent year-on-year in Q2 to 480,126, and total automotive revenues surpassed $20 billion. However, operating margin fell to 1.4 percent from 4.1 percent a year ago.

According to Tesla, it is "in its largest and most exciting period of investment" as it builds out the infrastructure needed to make good on Musk's many promises.

"I think Optimus [Tesla's humanoid robot] will be the biggest product," Musk reiterated during the earnings call, before cautioning that "it is a very complex problem to solve."

Arthur T Knackerbracket writes:

https://www.engadget.com/2227720/eu-right-to-repair-directive-kicks-in-today/

July 31, 2026 marks the start of a new era for the Right to Repair movement, at least for citizens in the European Union. It's the deadline for when the bloc's directive on repairs goes live for its 27 member nations. And while today is more of a political and procedural milestone than a practical one, it opens the door for major changes in how people maintain their hardware. It's all part of the bloc's push for a fairer, and more sustainable economy.

Essentially, the directive requires manufacturers to offer repairs for faulty products within a "reasonable time" and "at a reasonable price." Manufacturers will also need to publish repair manuals — for free — and offer clear pricing for spare parts. If a piece of equipment is repaired, then buyers will also be able to have their legal warranty period extended for an additional year.

At present, the rules cover repairs for major household appliances, such as washing machines, dryers, dishwashers and refrigerators. On the technology side, the rules apply to smartphones, tablets, server equipment, as well as e-bikes and e-scooters. A notable admission from the list is vacuum cleaners, which will get its own separate framework at some point down the line.

At the time of publication, there are still plenty of member states that haven't yet incorporated the directive into their domestic law. It's likely we'll still be waiting several months before we start seeing meaningful changes in how repairs are handled. Not to mention that this is a separate initiative from the removable battery laws — which will see the sale of a more repairable version of the Switch 2 — which are due to kick in next year.

Original Submission

Arthur T Knackerbracket writes:

Posisbly cracked mud, therefore more evidence Red Planet was once less horrible:

NASA has shared new snaps captured by its Curiosity rover that show a large "field of honeycomb textures" on Mars.

NASA doesn't know how the honeycomb formed, but The Register is willing to rule out space bees because Curiosity has seen this sort of thing before and scientists are pretty sure the patterns are the result of mud drying and cracking during some unknowably distant Martian event.

Curiosity spotted the polygonal features after starting its climb up a Martian valley that mission scientists have nicknamed "Valle Grande." NASA's post about the find says the rover has seen "small patches of these geometric shapes several times before, but nothing at the scale discovered in Valle Grande."

The Rover snapped the honeycomb field on June 19 and 20, the 4,930th and 4,931st Martian days of its very extended mission. Curiosity reached Martian soil on August 5, 2012, and was the first probe to land under a "sky crane" – a hovering craft that lowers rovers to the ground. Previous Mars landings relied on bouncing airbags that space agencies hoped would protect probes as they landed at speeds exceeding 70 km/h.

Curiosity has travelled about 35 kilometers since arriving on Mars and has made myriad fascinating observations along the way, some of which suggest Mars was once home to intermittent oases or even a large lake. The journey was hard, with damaged tires a persistent problem. The rover's drill got stuck in a Martian rock. NASA took a leaf from the Taylor Swift playbook and found a way to shake it off. The space agency has also remotely reprogrammed the rover to conduct different experiments and uploaded major software upgrades to keep it rolling.

The rover is currently carrying out its fifth extended mission. NASA typically extends missions for as long as its robots gather enough data to justify the cost of operating them. Curiosity continues to meet those criteria very comfortably!

Original Submission

Arthur T Knackerbracket writes:

https://www.theregister.com/personal-tech/2026/07/30/americans-give-all-day-school-phone-bans-a-ringing-endorsement/5281186

Americans are warming to the idea that schools should be for learning rather than doomscrolling, with support for all-day smartphone bans now outweighing opposition for the first time.

A new Pew Research Center survey of 9,750 US adults found that 77 percent support banning smartphones during middle and high school classes, up from 68 percent in 2024. More significantly, support for so-called "bell-to-bell" bans now stands at 48 percent, compared with 43 percent who oppose the idea.

Back in 2024, opponents held the advantage.

The shift coincides with a rush of state legislation. According to the National Conference of State Legislatures, 42 states have enacted measures addressing cellphone use in schools, many of which require districts to adopt restrictions during the school day.

There's little argument over whether phones belong in class anymore, but the sticking point is whether students should get them back between lessons or keep them tucked away until the final bell.

Age plays a predictable role. Adults under 30 remain the least enthusiastic about bell-to-bell restrictions, with just 28 percent supporting them. Older Americans, meanwhile, appear increasingly comfortable with the notion that teenagers can survive a school day without immediate access to social media, group chats, or whatever crisis is currently unfolding on Snapchat.

The partisan divide is smaller than on most US policy questions. Republicans are more likely to support both classroom and all-day bans, but Democrats also back classroom restrictions by a comfortable margin.

The trend echoes developments elsewhere. In the UK, ministers spent much of this year promising to get tougher on phones in schools, only for it to emerge that most schools already had restrictions in place. The government's reforms mostly gave existing policies more bite, saving ministers the trouble of inventing anything new.

Whether today's students see their phones as indispensable learning tools or portable oxygen tanks is another matter. Pew's latest numbers suggest more American adults are willing to let them find out for six or seven hours a day.

Original Submission