Markey’s Data Center Bill Takes Aim at AI’s Growing Pollution and Power Toll

Senator Edward J. Markey released a discussion draft last week that could reshape how America builds the massive facilities powering artificial intelligence. The proposal, part of his broader AI Accountability Agenda, targets the surge in data centers that consume vast electricity, strain local grids and spew emissions. Communities near these projects have complained for years. Now federal rules may force operators to prove they won’t make things worse.

The Massachusetts Democrat has long pushed back against lax oversight. His new measure, the Protecting Communities from Data Center Impacts Act, demands a federal certificate before any permitting or construction. Operators must show the project won’t harm public interest. Minimum standards cover energy use, pollution and economic fallout. Short. Direct. And overdue, according to critics of the current pace.

Data centers already rival nations in their appetite for power. Last year they used 448 trillion watt-hours globally. That topped electricity consumption in all but 10 countries. The facilities produced 208 million tons of carbon dioxide, matching Argentina’s annual output. They also consumed 1.2 trillion gallons of water. AP News reported these figures from a United Nations University study. Projections look starker. By 2030 consumption could hit 935 trillion watt-hours. That equals nearly 3 percent of worldwide electricity. Emissions would double to about 440 million tons.

But the numbers tell only part of the story. AI now drives roughly 20 percent of data center energy demand. That share may reach 40 percent in four years. Servers run hotter. Cooling systems gulp more water. And many projects turn to fossil fuels for quick supply. A fresh report examined 74 planned gas-fired plants meant to serve data centers directly. Their combined capacity? 143 gigawatts. Annual greenhouse gas emissions could total 662 million tons. That matches the yearly output of Australia or France. Nearly half the plants would sit in Texas. Others cluster in Ohio, Pennsylvania and West Virginia. Reuters covered the Environmental Integrity Project analysis, published July 1.

Jen Duggan, the group’s executive director, put it plainly. “An industry of the future should not be chained to dirty fuels of the past and the air pollution from fossil fuels that cause real harm to communities.” Pollutants like nitrous oxide and benzene threaten nearby residents. Developers counter that off-grid plants dodge some standard rules. They move faster. Yet the health costs linger.

Markey’s draft doesn’t leave these burdens to chance. Facilities would pay for grid upgrades themselves. They must sign agreements to cut demand during peak stress. No more shifting extra costs onto households. Data centers would also fund renewable generation and storage to match their needs. On-site diesel backups? Off limits under the plan. Construction must meet high labor standards too. Grants would help communities hire experts to track air quality, water use, noise and health effects. Technical aid would build local capacity to push back or mitigate damage.

From Local Complaints to National Policy

Residents have organized in Virginia, Georgia, Oregon and beyond. They cite higher bills, diesel fumes, constant hum and strained water supplies. Markey hosted a roundtable in July 2025 titled “The Data Center Next Door.” It spotlighted hidden costs of AI and cryptomining. He released a storybook that same day. Families described living beside these complexes. The tales weren’t abstract. They detailed disrupted nights, respiratory issues and unexpected rate hikes.

The senator has kept pressure on regulators. In June he urged EPA Administrator Lee Zeldin to scrap a proposed rule that eases Clean Air Act permitting for data centers and related fossil infrastructure. Last September he opposed rollback of the New Source Review program. November 2025 brought a letter to the Federal Energy Regulatory Commission. Markey warned against unjust rate increases for families. March 2026 saw him call on state utility regulators to shield ratepayers. He reintroduced the AI Environmental Impacts Act in June. That bill requires operators to disclose full environmental footprints or face fines. Markey’s Senate office detailed the agenda and history July 10.

States haven’t waited. More than 300 bills appeared across 30 legislatures early this year. New York weighs a three-year halt on new builds while agencies craft rate protections. Massachusetts considers a commission to study load growth from AI facilities. Pennsylvania lawmakers debate local moratoria. These efforts vary. Yet they share frustration with unchecked expansion. Markey’s draft draws lessons from them. It aims to knit patchwork rules into one national standard. But, some industry voices worry added requirements could slow AI progress. Others see efficiency gains. Operators who optimize code and hardware may face lighter compliance loads.

The Guardian spoke with Markey around the release. He stressed immediate harms over distant promises. “We need to make sure these datacenters don’t turn into pollution bombs.” The paper highlighted personal stories driving his agenda. One involved a teen’s suicide linked to an AI chatbot. Another described rural water shortages near proposed sites. A discrimination lawsuit tied to biased algorithms. A nurse veteran distressed by workplace AI. These anecdotes ground the policy in lived experience. They also signal Markey’s decade-long fight to curb Big Tech power. His agenda spans worker surveillance, child safety, civil rights, healthcare judgment and wealth sharing. Data centers form one pillar. Yet they anchor the physical reality behind digital hype.

Recent coverage shows momentum. Google’s 2026 environmental report revealed its electricity use jumped more than 250 percent since 2019. The company hit 43 terawatt-hours in 2025, up 37 percent in a single year. AI and cloud services drive the spike. Other hyperscalers report similar trends. Meanwhile a Carnegie Mellon economist calculated U.S. data centers imposed $25 billion in pollution and health damages last year. That figure could rise 85 percent soon. U.S. News & World Report examined the analysis in May. Without grid decarbonization, emissions may exceed prior forecasts by 57 percent. Allianz Trade projected 286 million tons of CO2 from centers in 2025 alone.

Markey’s certificate requirement stands as the draft’s sharpest tool. It flips the script. Instead of reacting after construction, agencies review impacts first. Air and water quality. Noise levels. Energy draw on the local grid. Effects on jobs and taxes. Ecosystem strain. Failure to meet standards blocks the project. The approach echoes environmental justice principles. Communities gain resources to monitor and respond. They no longer absorb costs alone.

Critics of the Trump administration’s AI Action Plan see the draft as direct rebuttal. That plan favored speed over safeguards. Markey called it a “race to the bottom.” His legislation insists on accountability now. AI’s benefits exist. Faster drug discovery. Improved weather models. Enhanced accessibility tools. Yet infrastructure supporting those gains carries trade-offs. Water diverted from farms. Power plants built near homes. Bills that rise for everyone else. The senator’s plan forces those trade-offs into daylight before concrete pours.

Passage faces hurdles. Industry lobbyists argue strict rules could push projects overseas. Some Republicans favor streamlined permitting to maintain U.S. leadership in AI. Bipartisan interest in child online safety and bias protections may open doors. COPPA 2.0 cleared the Senate unanimously earlier this year. Markey hopes similar common ground emerges here. Still, the data center bill touches energy policy, environmental law and economic development. Compromise won’t come easy. And time matters. New facilities break ground monthly. Emissions climb. Grids strain.

So the discussion draft invites input. Markey pledged to consult communities, workers and state leaders. He wants to refine the text before formal introduction. That process could incorporate ideas from New York’s moratorium debate or Virginia’s ratepayer complaints. It may tighten labor language or expand grant programs. Whatever the final shape, the proposal marks a shift. Federal government would no longer treat data centers as invisible infrastructure. They become regulated actors with duties to neighbors and the climate.

Projections grow more urgent each quarter. One study warned data center land footprint could exceed 14,500 square kilometers by decade’s end. Water consumption for cooling and power might equal basic domestic needs of 1.3 billion people. These scales demand coordinated response. Markey’s bill offers one model. It pairs transparency with enforcement, local aid with operator accountability. Success depends on execution. Yet the direction feels clear. The AI boom cannot ignore its physical costs. Communities have waited long enough.

from WebProNews https://ift.tt/DUJdnYr

Christopher Nolan’s Flip Phone Era: Why the Director Still Rejects Smartphones Amid ‘The Odyssey’

Christopher Nolan has never owned a smartphone. He has never used email. These facts, once quirks of a prominent filmmaker, now stand out sharply in an industry and culture tethered to constant digital connection.

The director behind Oppenheimer, Inception and the upcoming The Odyssey carries a flip phone when he travels. At home and on set, he relies on others. Assistants print emails for him. Colleagues hand him phones when needed. “I do not,” he told Complex in May, recounting his 60 Minutes exchange. “I never have.”

Nolan’s Practical Resistance

His stance isn’t born from outright rejection of technology. Nolan embraces tools that serve his stories. Practical effects, large-format film, intricate VFX — these define his work. Yet personal devices that demand attention? Those he avoids. “I worry the world is eventually going to wear me down,” he said in a recent Telegraph interview. “Partly because I know I’d become horribly addicted to them if I had one.”

Short. Direct. The admission lands with force. Addiction lurks there, he believes. Not in some abstract moral panic. In the quiet moments that fuel his scripts.

Waiting for a train. Sitting between takes. Those pockets of time once sparked ideas. Now, many fill them scrolling. Nolan opts out. “I actually really like not having one because it gives me time to think,” he explained to The Hollywood Reporter years ago. “You know, when you have a smartphone and you have 10 minutes to spare, you go on it and you start looking at stuff.” Longer analytical sentences follow that thought. The distraction compounds. Ideas that might have formed stay buried under notifications and feeds.

But it’s getting harder. QR codes returned after COVID. Menus, tickets, check-ins — all demand a smartphone now. “The return of the QR code has been quite… quite tricky,” Nolan said on 60 Minutes, as reported by Complex. “QR code had sort of gone away, but COVID brought it back and now it’s kind of everywhere. And if you don’t have a smartphone, you can’t do much with a QR code.” He carries the flip phone for travel. Otherwise, he lives as many once did. “I feel very fortunate to not be wearing the digital shackles, but such is life.”

And his team adapts. Printed emails pile up. “People are like, ‘You’ve got to take a look at this.’ Alright,” he noted. “But no, I’ve just never been particularly interested in that as a form of communication.” Face-to-face still matters. So does privacy. He hands off scripts in person. No leaks from careless forwards. No digital trail that could expose an unfinished idea.

His children notice. “My kids would probably say I’m a complete Luddite,” Nolan told The Hollywood Reporter in 2023. He pushes back on the label. “I would actually resist that description. I think technology and what it can provide is amazing. My personal choice is about how involved I get. It’s about the level of distraction. If I’m generating my material and writing my own scripts, being on a smartphone all day wouldn’t be very useful for me.”

That computer he writes on? No internet connection. Security and focus both win. Rumors swirl anyway. A Blue Thunder remake? Nolan heard it secondhand. No urge to log on and correct the record. “I have absolutely no idea where it came from. And besides, I was always more of an Airwolf fan,” he quipped recently, per posts referencing the Telegraph.

His approach influences sets too. Strict no-phone policies during shoots preserve concentration. Matt Damon highlighted this in a recent appearance, noting Nolan’s habit preserves deep thinking time. Actors and crew focus without the pull of devices. “Phones have become a huge distraction, and people work much better without them,” Nolan once shared with Esquire, as cited across coverage.

Yet he doesn’t ban phones from theaters out of puritanism. He praises venues like Quentin Tarantino’s that enforce the rule. The big screen demands attention. Distractions diminish the experience. His films reward that focus — intricate plots, practical spectacle, sound design that envelops.

Recent coverage shows the conversation evolving. As AI tools generate content at scale, Nolan’s children spot the difference immediately. They’ve grown up online enough to recognize low-effort output. “Slop,” they call it. Their father steers clear, using technology where it elevates narrative, not replaces craft. In The Odyssey, engineering challenges for IMAX filming demanded ingenuity from actors and crew alike. No digital shortcuts there.

Industry insiders watch closely. Nolan’s output remains prolific. Blockbusters built on original stories. No endless franchises. His method — analog where it counts, selective with the rest — yields results that stand apart. Others chase virality and algorithmic favor. He thinks. He writes offline. He shoots on film when possible.

Critics once called it eccentricity. Now some see wisdom. Phone addiction studies mount. Attention spans shrink. Executives admit their own devices colonize time. Damon, in conversation with Conan O’Brien, pointed to Hong Kong streets where screens dominate all ages. “I see it with myself, how quickly I’ll allow my attention to kind of get colonized by these devices,” he said. Nolan offers the counterexample. Preserve the quiet. Let ideas form.

Of course, not everyone can opt out. Nolan’s success affords assistants and buffers. A working parent juggling schedules might struggle without apps. He acknowledges the shift. Life pushes forward. QR codes multiply. Services assume connectivity. “It’s getting harder and harder,” he concedes.

Still, he persists. No digital shackles. Flip phone in pocket. Ideas in head. The approach feels increasingly radical. And surprisingly practical. In a profession fueled by imagination, protecting the space for it matters. Nolan doesn’t preach. He simply lives it. Others debate the trade-offs. His films keep arriving. Grand in scale. Human in detail.

The Digital Trends piece captured it well last week. His take resists the binary — neither Luddite nor enthusiast. Practical. Thoughtful. A reminder that technology serves us best when we dictate the terms.

from WebProNews https://ift.tt/XIY69te

Linux 7.3 Unlocks Extra Graphics Pipe on AMD APUs, Sharpening Performance Edge

AMD engineers have quietly pushed forward a change that stands to tighten graphics scheduling on the company’s latest integrated processors. With patches queued for the Linux 7.3 kernel, the AMDGPU driver now activates a second graphics pipe on GFX11-based APUs. The move targets modern chips built on RDNA 3 and RDNA 3.5 architectures. It promises more work queues and smoother hardware-level priority handling.

The update comes from Alex Deucher, a longtime AMD Linux engineer. In the patch submitted to the amd-gfx mailing list, he laid out the constraints in clear terms. “Enable gfx pipe1 hardware support,” Deucher wrote. “This is only available on gfx11 chips using the F32 microcontroller. Chips using the RS64 microcontroller are not able to use the second gfx pipe. In practice this means the second pipe is only available on APUs. This explains the stability issues Pierre-Eric saw previously with this on Navi33.”

That earlier instability on discrete Navi 33 parts had held back broader adoption. Now the code limits the feature to APUs where it belongs. The kernel sets GFX11_NUM_GFX_RINGS to two by default but drops back to one when RS64 is detected. Early initialization routines adjust the number of rings and load the right microcode accordingly. Simple. Targeted. And apparently overdue.

Why does any of this matter? A single graphics pipe per MicroEngine has long forced the driver to juggle competing workloads in tighter quarters. Adding the second pipe spreads tasks across more hardware queues. The result should appear in better task prioritization at the hardware level. Stability improves. Spurious stalls decrease. For users of Ryzen AI 300 series laptops or hand-held gaming devices running Linux, the difference could feel tangible once distributions pick up the kernel.

Phoronix first highlighted the patch series on July 10, 2026, noting its place among other AMDGPU and AMDKFD updates headed to DRM-Next. Those updates also refresh PSP 15.0.9 and SMU 15.0.9 IP blocks, fix assorted bugs, and advance the project’s effort to remove BUG() calls from the driver. The full pull request sits in the amd-gfx archives for review.

But the pipe change draws particular attention. It builds on years of incremental GFX11 enablement that began when RDNA 3 first reached market. Earlier kernels brought basic support. Later ones refined power management and compute features. This step refines the graphics front end itself. And it does so without touching discrete GPUs that rely on the RS64 microcontroller, avoiding the very crashes that once blocked progress.

Industry observers on X reacted quickly. Chris Mizo noted that the change “will help better graphics scheduling, more work queues, stability, and overall driver behavior on supported AMD APUs.” His summary, posted hours after the Phoronix article, reached Linux enthusiasts following SteamOS and Bazzite development for handheld PCs. Similar chatter appeared in Spanish-language tech accounts, underscoring how quickly driver news travels across communities that rely on AMD silicon.

The timing aligns with growing adoption of AMD-powered mini PCs, thin laptops, and gaming handhelds. Devices based on Strix Point and its successors already ship with strong open-source driver support. Yet small inefficiencies in command submission or queue management can still surface under heavy mixed workloads — think simultaneous gaming, video encoding, and background AI tasks. A second pipe gives the scheduler more breathing room.

Deucher’s explanation also clarifies why the feature stayed dormant so long on certain parts. Navi 33, a discrete RDNA 3 GPU, apparently triggered the same code paths during early testing. Stability suffered. Once the microcontroller distinction was identified, the path forward became straightforward: gate the extra pipe behind the F32 check and expose it only where hardware guarantees success. The patch does exactly that.

Kernel developers have grown accustomed to AMD’s steady drumbeat of improvements. Each merge window brings another batch of fixes and feature work. This one feels different because it touches a fundamental piece of the graphics engine that users can indirectly feel through frame timing and responsiveness. No flashy new hardware. Just better use of what already exists in millions of shipped APUs.

That pragmatic focus defines much of the AMD Linux effort. Rather than chase headline features alone, the team closes long-standing gaps. Earlier this year similar patches expanded support for newer IP blocks in Strix Halo and prepared for future RDNA variants. The pipe1 work fits the same pattern: identify a hardware capability, confirm its limitations, expose it safely.

Distributions will need time to integrate Linux 7.3 once it stabilizes. Early testers can already pull the DRM-Next tree and experiment. For most users the change will arrive quietly with their next major update. Yet its presence signals continued investment in squeezing more from integrated graphics at a time when hybrid computing workloads grow more demanding.

Hardware priority scheduling now gains a real second lane on these APUs. More queues mean less contention. Stability issues that once haunted early experiments have an explanation and a fix. The result is a driver that aligns more closely with the silicon’s actual design. And that alignment tends to pay dividends over years of kernel releases to come.

Other recent coverage adds context to AMD’s Linux momentum. A June 2026 report from Wccftech detailed expanded kernel support for upcoming RDNA 4 elements, including compute driver readiness that ensures launch-day compatibility. While distinct from the pipe1 work, it shows the same methodical preparation across GPU generations.

Meanwhile, discussions around Strix Halo Linux stability have intensified in 2026. A video update from early in the year highlighted maturing ROCm support on those high-end APUs, though it predates this week’s kernel patches. The new pipe enablement could complement such efforts by smoothing graphics command flow in mixed CPU-GPU-AI scenarios.

Deucher and his colleagues rarely seek spotlight. Their patches speak through merged code and eventual real-world gains. This one speaks clearly. Two pipes instead of one. Better scheduling. Fewer surprises. For Linux users on modern AMD APUs, that’s meaningful progress arriving in the next kernel cycle.

from WebProNews https://ift.tt/BzrDkdR

EU Tells Meta to Dismantle Instagram and Facebook Features That Keep Users Hooked

Brussels delivered a stark message to Meta on Friday. The European Commission issued preliminary findings that the company’s Instagram and Facebook apps breach the bloc’s landmark Digital Services Act through what regulators call their addictive design. Features long central to the platforms’ ability to hold attention now stand accused of harming users’ physical and mental health, especially children and teenagers.

Infinite scroll. Autoplay videos. Push notifications. Highly personalized recommendation systems. These elements, the Commission said, fuel compulsive use. They shift the brain into autopilot mode. Users keep scrolling. They lose track of time. And Meta, investigators concluded, never properly weighed the consequences.

The European Commission made its position clear. “Protecting the physical and mental health of Europeans must be a priority for social media platforms. The Digital Services Act provides a clear framework to hold platforms accountable for the addictive design and effects of their services. We are fully committed to enforcing our legislation in Europe,” said Henna Virkkunen, the EU executive vice-president for digital policy, according to multiple reports including The New York Times.

Meta pushed back immediately. “We disagree with these preliminary findings, which don’t accurately take into account the significant steps we’ve taken to protect teens,” a company spokesperson told CNBC. The firm pointed to recent introductions of Teen Accounts that automatically limit nighttime access and cap daily screen time at 15 minutes. It promised to keep working with regulators.

Yet the Commission found those efforts insufficient. Time management tools can be dismissed with a tap. Parental controls demand technical skill and constant attention from guardians. Awareness messages buried in a separate safety center page fail to address the core problem. The apps’ very architecture, optimized for reels, stories and endless feeds, encourages excessive use at all hours, including late into the night for minors. Regulators reviewed Meta’s own internal documents, risk assessments, user data and a wide body of scientific research on behavioral addiction. They interviewed experts. The evidence, they said, pointed to systemic failure.

This confrontation has been building. The Commission opened formal proceedings against Meta in May 2024. It has already issued preliminary findings on the company’s weak age verification that allowed children under 13 to create accounts. A separate probe into so-called rabbit hole effects, where recommendation algorithms pull vulnerable young users deeper into harmful content, continues. Friday’s action fits a pattern. The EU hit TikTok with similar accusations of addictive design earlier this year. Now Meta faces concrete demands that could force basic changes to how its apps function.

Regulators want autoplay and infinite scroll turned off by default. They call for effective screen time breaks that actually interrupt sessions. Recommendation algorithms should prioritize something other than raw engagement. These are not minor tweaks. They strike at the heart of a business model built on keeping people online as long as possible. Meta’s ad revenue depends on time spent and attention captured. Alter the defaults, and user behavior could shift dramatically.

The stakes are high. A final decision against the company could bring fines reaching 6 percent of its global annual turnover. For a firm that generated more than $200 billion in revenue last year, that ceiling exceeds $12 billion. The Commission will weigh the infringement’s nature, gravity, recurrence and duration. Meta now has time to examine the full case file, submit a written defense and face questions from the European Board for Digital Services. The process could take months. Yet the preliminary nature of the findings already signals a regulatory shift with implications far beyond Europe.

Other outlets quickly highlighted the breadth of the move. BBC News reported that features such as personalized recommendations could encourage compulsive use particularly among children and teens. Politico noted the demand to make the recommendation algorithm less driven by engagement metrics. CNN emphasized that the two-year investigation concluded Meta failed to warn users adequately about risks to their wellbeing.

Industry observers have long debated these design choices. Critics argue that infinite scroll removes natural stopping points, much like a slot machine that never runs out of coins. Autoplay videos eliminate the friction of deciding whether to watch the next clip. Personalized feeds, trained on vast troves of user data, serve content calibrated to maximize dwell time. The result feels effortless. For some users it becomes compulsive. Studies cited in the Commission’s review link prolonged nighttime use to sleep disruption, anxiety and other harms, especially in developing adolescent brains.

Meta has introduced tools over the years. Usage reminders. Quiet mode. Parental supervision features. The company touts them as evidence of good faith. Regulators counter that these measures sit on top of a foundation built for addiction. They are too easy to ignore. They do not change the underlying incentives. And they place too much burden on individual users and families rather than on the platform itself.

The timing adds pressure. European officials have grown impatient with Big Tech’s pace on child safety. France has floated ideas for minimum ages on social media. The Commission itself is preparing a Digital Fairness Act that could impose even stricter rules on harmful design practices. Friday’s action against Meta serves as both enforcement and warning. Comply, or face escalating penalties and possible product redesigns across the region.

Yet compliance carries risks for Meta. Disabling autoplay and infinite scroll by default might reduce engagement in Europe, a market of more than 450 million people. Advertisers could see lower reach. Creators might post less if algorithms favor different signals. And any successful changes could inspire regulators elsewhere. Lawmakers in the United States have watched Europe’s moves closely. Multiple lawsuits there already target the same design practices, alleging they contribute to youth mental health crises.

So far Meta shows no sign of immediate capitulation. Its statement to reporters stressed disagreement with the findings while expressing shared goals around teen safety. The company will likely argue that its existing protections, recent updates and ongoing research demonstrate adequate risk mitigation. It may offer further concessions or data to blunt the case. But the Commission’s language leaves little room for half measures. Design changes are not suggestions. They read like requirements.

This episode marks another chapter in the uneasy relationship between Silicon Valley and Brussels. The EU has fined tech giants before. It has forced product alterations on privacy, content moderation and competition grounds. Now it takes direct aim at the psychological hooks that make social media so profitable and, for many, so difficult to put down. The outcome will test whether regulation can reshape not just rules but the fundamental user experience of the world’s largest social platforms.

Meta has until it submits its formal response to decide how aggressively to fight. The Commission has until it issues a final decision to prove that its framework can deliver meaningful change. Users, particularly younger ones, sit in the middle. Their feeds may soon look different. Their habits might follow. The question is whether those shifts come voluntarily from the company or under sustained regulatory force.

from WebProNews https://ift.tt/fN4z6ic

Helium Computer: Verifiable Computation via Zero-Knowledge Proofs and Hardware Attestation

The helium computer project stands out as a noteworthy effort to bring verifiable computation into practical use across distributed networks. By focusing on transparency as a core principle, the initiative addresses longstanding concerns about whether complex calculations performed on remote machines can be trusted without direct oversight. The approach outlined on the helium.computer blog explains how cryptographic proofs and open verification methods allow anyone to confirm that specific tasks were executed exactly as claimed.

At its foundation, the system relies on zero-knowledge proofs combined with specialized hardware attestations. These tools generate compact certificates that demonstrate a program ran correctly on authorized equipment while keeping the underlying data private when necessary. The blog post highlights that such certificates can be independently checked by any participant in the network, removing the need to trust a central operator or a single cloud provider. This model shifts the balance from blind faith toward mathematical certainty, a change that carries implications for fields ranging from artificial intelligence training to financial modeling.

The motivation for this work stems from repeated incidents in which users discovered discrepancies between promised and actual computation. Reports of altered training runs, hidden backdoors in inference engines, and opaque pricing models have eroded confidence in outsourced processing. Helium Computer responds by requiring every node to produce a verifiable record of its activity. When a machine completes a workload, it attaches a proof that links the input, the program logic, and the output in an unforgeable chain. Verifiers can sample these records at random and confirm their accuracy without rerunning the entire job, which keeps costs manageable even at large scale.

One practical application involves large language model inference. Organizations that depend on external services for generating text or analyzing documents often worry about data leakage or model tampering. With Helium’s framework, a service provider can prove that a specific model version processed a given prompt and produced a particular response. The proof reveals nothing about the model weights themselves, preserving proprietary information while still allowing the customer to audit the integrity of the operation. The blog entry notes that this capability opens doors for regulated industries where audit trails are mandatory.

Another area of focus is decentralized training of machine learning models. Instead of concentrating compute power in a handful of data centers, the network can recruit GPUs and TPUs from many independent operators. Each contributor submits a proof alongside gradient updates or checkpoint files. Aggregators then verify that the submitted work matches the expected training protocol before incorporating the results. This arrangement reduces single points of failure and spreads economic incentives across a wider group of hardware owners. The transparency layer ensures that no participant can inject malicious updates without detection.

Hardware plays a central role in making these guarantees practical. The system incorporates devices that support remote attestation, a feature built into modern secure processors. When a node boots, it generates a cryptographic signature that identifies both the hardware model and the exact software image loaded into memory. This signature becomes part of the larger proof chain, linking the physical machine to the logical execution. The helium.computer blog explains that without this hardware root of trust, software-only proofs would remain vulnerable to kernel-level manipulation.

Beyond the technical architecture, the project places emphasis on open specifications. All proof formats, verification algorithms, and attestation protocols are published under permissive licenses. Independent researchers can implement their own checkers and run parallel validations, creating a marketplace of auditors rather than a monopoly. This openness contrasts with proprietary systems that keep their validation methods secret, often citing security through obscurity. Helium Computer argues that true security emerges only when multiple parties can examine and improve the same verification code.

Economic design also receives careful attention. Nodes earn rewards for completing verifiable tasks, with payouts tied directly to the quality and timeliness of their proofs. If a node fails to produce a valid certificate or if its hardware attestation does not match the registered profile, the network can slash its stake or withhold payment. This mechanism discourages cheating and encourages operators to maintain clean, up-to-date equipment. The blog post points out that such incentives align individual profit motives with collective trust requirements, a balance often missing from volunteer-based distributed computing projects.

Scalability remains an active research topic. Generating succinct proofs for very large computations can require substantial overhead, both in time and memory. The team has explored recursive proof composition, where smaller proofs are combined into a single master certificate that still validates the entire workload. Early benchmarks suggest that verification time stays nearly constant even as the original job grows to millions of GPU hours. Continued improvements in proof systems, such as newer folding schemes and hardware-accelerated polynomial commitments, are expected to drive these costs down further.

Privacy considerations receive equal weight. Many workloads involve sensitive information that cannot be revealed during verification. Zero-knowledge techniques allow proofs to attest to correct execution without exposing the data that was processed. For example, a medical research group could confirm that a statistical model was trained on patient records without ever disclosing those records to the compute provider or to the public verifiers. The same holds for proprietary algorithms in financial risk systems or recommendation engines. The blog entry underscores that privacy and transparency are not mutually exclusive when the right cryptographic primitives are applied.

Adoption pathways include integration with existing cloud orchestration tools. Developers can submit jobs through familiar interfaces while the backend automatically wraps them in proof-generating runtimes. This compatibility lowers the barrier for teams already invested in containerized workflows. Over time, the project anticipates that proof generation will become a standard checkbox option in major cloud platforms, much like encryption at rest or audit logging. As more organizations demand verifiable computation, providers that cannot supply proofs may find themselves at a competitive disadvantage.

Challenges persist. Not every algorithm lends itself easily to efficient proof generation. Certain floating-point operations common in scientific computing still require careful reformulation to fit within the constraints of current proof systems. Similarly, interactive machine learning pipelines that depend on human feedback loops introduce timing and nondeterminism issues that must be handled explicitly. The helium computer team acknowledges these limitations and publishes regular updates on which workloads are fully supported and which require additional engineering.

Community governance adds another layer of transparency. Decisions about protocol upgrades, supported hardware profiles, and dispute resolution mechanisms are made through on-chain voting weighted by staked tokens. This structure prevents any single company from unilaterally changing the rules. Detailed meeting notes and code repositories are available for public inspection, allowing outside contributors to follow along and submit improvements. The blog post presents this openness as essential for long-term credibility, especially when the network’s value rests on collective confidence.

Looking forward, the project aims to expand beyond pure computation into data availability and storage proofs. Combining verifiable execution with guaranteed data persistence would create end-to-end assurances for complete data pipelines. A researcher could prove that a dataset was stored reliably, preprocessed according to documented steps, and then used to train a model whose outputs satisfy predefined statistical tests. Each link in that chain would carry its own cryptographic evidence, forming a tamper-proof audit log spanning multiple operators and time periods.

Educational resources also form part of the initiative. The blog regularly publishes tutorials on how to generate and verify proofs using open-source libraries. Sample code demonstrates integration with popular deep learning frameworks, showing developers how little extra work is required to add transparency to their existing pipelines. By lowering the technical barrier, the project hopes to encourage broader experimentation and feedback from real-world users.

In practice, several pilot programs have already tested the system at modest scale. A financial analytics firm used the network to run Monte Carlo simulations for portfolio stress testing. Each simulation run produced a proof that the random seeds, model parameters, and numerical methods followed the approved specification. Auditors could later confirm that no shortcuts were taken and that the reported risk metrics were derived from the stated inputs. The firm reported that this verifiable approach satisfied both internal compliance teams and external regulators more effectively than traditional signed reports.

Another pilot involved training a computer vision model on crowdsourced imagery. Contributors uploaded photos along with metadata proofs that established the images had not been altered after capture. Training nodes then produced a certificate showing that the model had been updated only with verified data and according to the agreed learning schedule. The resulting model could be distributed with a guarantee of provenance, giving downstream users confidence that the training set met quality and ethical standards.

These examples illustrate how verifiable computation moves from theoretical possibility to daily utility. As hardware becomes more efficient at generating proofs and as software libraries mature, the overhead continues to shrink. The helium.computer blog maintains that the ultimate goal is to make transparency the default setting for any outsourced workload, so that trust becomes an automatic property rather than an expensive add-on.

The broader impact could extend to scientific research, where reproducibility has become a pressing concern. Journals increasingly require authors to share not only data and code but also the exact compute environment used to produce published results. A verifiable compute layer would allow researchers to attach a compact proof to their papers, letting peers confirm that the claimed experiments were executed faithfully. This practice would reduce the frequency of retracted studies and accelerate collective progress by making verification faster and cheaper.

Regulatory bodies may also find value in the approach. Agencies responsible for overseeing algorithmic trading, credit scoring, or medical device software could require proof-based attestations instead of self-reported compliance. Because the proofs are machine-checkable, enforcement becomes partly automated, freeing human auditors to focus on higher-level policy questions. The cryptographic receipts would serve as digital equivalents of sealed laboratory notebooks, providing immutable evidence of proper procedure.

Helium Computer’s emphasis on transparency therefore addresses both technical and societal needs. By combining hardware roots of trust, succinct cryptographic proofs, open specifications, and aligned economic incentives, the project constructs a foundation on which more reliable distributed systems can be built. The ongoing work documented on the project’s blog demonstrates steady progress toward making verifiable computation accessible, affordable, and routine across a growing range of applications. As these tools become standard practice, the distinction between trusted and untrusted compute environments may gradually disappear, replaced by environments where correctness can be confirmed by anyone at any time.

from WebProNews https://ift.tt/sx9OvUE

Meta’s Muse Image Lets Strangers Generate Your Face From Instagram Photos — And It’s On By Default

Meta rolled out Muse Image on July 7. The new model from Meta Superintelligence Labs generates and edits pictures with striking accuracy. It handles complex prompts. It pulls from multiple references. And it turns public Instagram profiles into raw material for anyone who types an @-mention.

But here’s the part that lands like a quiet bombshell. If your Instagram account sits on public settings, others can create images of you. No permission asked. No alert sent. You’re opted in from the start.

The Mechanics Behind the Likeness Grab

The process looks simple on the surface. A user opens Meta AI in Instagram, WhatsApp or the dedicated app. They type a prompt. They add @yourusername as a reference. Muse Image scans available public photos. It blends your features into whatever scene the prompter describes. The output carries an invisible Content Seal watermark. Yet that mark only identifies the image as AI-made. It does nothing to stop creation or notify the subject.

Meta’s own policy states the rule without apology. Instagram Help Center explains: “You will not be notified about content created using AI features at Meta.” The same page notes that public accounts on default settings allow “people may be able to create content with your Instagram content using AI features at Meta.” No push notification announced the change. No explicit consent screen appeared for millions of users.

And. This isn’t some distant beta test. Reports surfaced within hours of launch. TechCrunch detailed how the feature fits a pattern Meta has repeated before. TechCrunch pointed to the company’s 2021 decision to shut down facial recognition after lawsuits and regulatory heat. Now the same data practices return under a creative banner. Users retain some control through settings. But the default favors broad access.

Wired tested the rollout and found the updated language hadn’t reached every account by Tuesday afternoon. Wired described the fastest fix: switch the account to private via browser. The mobile app path requires more steps. Profile. Hamburger menu. Sharing and reuse. Toggle off both Posts and Reels under the section labeled “Allow people to use your content on Instagram and with AI features on Meta.” Even then, previously generated images stay in circulation. The opt-out blocks only future use.

Gizmodo captured the frustration in real time. Gizmodo noted the burden falls entirely on individuals to discover and disable the capability. Privacy advocates have flagged this approach for years. Meta collects vast stores of faces and contexts. Then it opens selective doors unless users actively close them.

The Digital Trends piece that first highlighted the default-on status pulled no punches. Digital Trends observed that a watermark alone fails to address deeper questions of likeness rights. Creators, influencers and ordinary users now compete with synthetic versions of themselves. Some versions will flatter. Others will distort. A few could damage reputations. None require the original person’s approval.

Yet Meta frames the release as pure advancement. In its announcement, the company called Muse Image its most advanced image generation model yet. It follows instructions faithfully. It edits with precision. It composes from multiple references. Early tests shared on X showed the system combining web search, text rendering and multi-stage editing. One post from AI researcher Alexandr Wang linked to research samples that demonstrated these strengths. But the same capabilities that impress engineers also amplify the privacy stakes.

Public reaction on X mixed excitement with alarm. Multiple users posted warnings within the first 24 hours. One account shared the WION News article that called the feature a pathway to deepfakes. WION emphasized that strangers can now @-mention any public profile and pull facial data without consent or notification. The story stressed the absence of proactive outreach from Meta. No mass email. No in-app banner. Just a revised help page that most users will never read.

This pattern echoes earlier Meta moves on AI training data. The company faced backlash in 2024 when it updated policies to scrape public posts for model improvement. European regulators pushed back. Some users formed opt-out campaigns. Now the focus shifts from training to direct generation. The data stays inside Meta’s systems. The outputs spread across chats, stories and external platforms.

So what happens when a brand, a troll or a marketer generates dozens of images featuring your face in fabricated scenarios? Current tools offer limited recourse. Reporting mechanisms exist for harassment or impersonation. But proving harm from a single AI image remains difficult. Watermarks help detect fakes after the fact. They don’t prevent the initial creation.

Meta insists users hold the reins. Settings exist. Private accounts limit exposure. The company shut down its old facial recognition system amid criticism. Yet the new feature revives similar data practices under the banner of creativity. Regulators in the EU and elsewhere have already signaled interest in biometric data and consent defaults. Lawsuits over likeness rights have multiplied as generative tools proliferate.

Industry watchers expect further scrutiny. The speed of deployment outpaced communication. The default setting maximized adoption at the expense of awareness. And the technology itself continues to improve. Muse Video sits in preview. Future updates could extend the same reference system to moving images. The stakes rise accordingly.

Users who want to act now face a clear but imperfect path. Make the account private. Disable the content reuse toggle. Monitor for unauthorized images in the wild. These steps reduce risk. They don’t eliminate it. Existing generations persist. And determined prompters can still reference cached or shared versions of public photos.

The launch reveals a deeper tension. Tech giants race to ship powerful media tools. They build on years of accumulated user data. They prioritize engagement and capability over exhaustive consent flows. The result feels both inevitable and unsettling. Powerful AI arrives. Your face helps power it. Whether you like it or not.

Meta has updated its help documentation. It has provided opt-out instructions. It has added technical safeguards like invisible watermarks. But the core choice remains: broad access by default, individual action required to withdraw. That choice will define the conversation in the weeks ahead. As more users discover the feature through articles or personal experience, pressure will build for clearer notifications, retroactive controls or stricter defaults.

One thing is certain. The images are already being made. Some will delight their subjects. Others will provoke outrage. A few may spark legal tests. All of them trace back to the same pool of public Instagram photos. And to a policy that assumed most people wouldn’t mind until they did.

from WebProNews https://ift.tt/qZDveE2

Robot Labor Takes Shape: AI Pushes Autonomy From Warehouses to Uncertain Horizons

Robots have long handled the dirty, dull and dangerous jobs. Yet something shifted in recent years. Advances in artificial intelligence now point toward machines that tackle sequences of unpredictable tasks without constant human guidance. The change arrives not from one breakthrough but from the steady stacking of data, models and hardware improvements.

From Narrow Tasks to Broader Capabilities

Industrial robots once followed rigid scripts inside safety cages. Today many operate with greater independence. Boston Dynamics deploys its four-legged Spot for inspections in hazardous spots. The machine navigates slippery surfaces thanks to reinforcement learning that lets it recover balance after slips. Its wheeled cousin Stretch grabs totes in warehouses run by DHL and others. These systems show autonomy works best in controlled settings. But real-world messiness changes everything.

Ars Technica examined this shift in a feature published Tuesday. Experts there describe autonomy as a moving target. ISO standards define it as a machine performing tasks based on its current state and sensed data without outside help. Matt Malchano, vice president of software at Boston Dynamics, captured the evolution. “When I started maybe about 15 years ago… the goal was to just get a robot to navigate from point A to point B,” he said. “And now, when we think of autonomy, we think of this huge space of tasks.” (Ars Technica)

Sergey Levine, professor at UC Berkeley and cofounder of Physical Intelligence, stressed the data requirement. “The key to making modern machine learning systems work is to get enough of a critical mass of data so that we see generalization,” Levine explained. “You can either have something that is kind of OK but not amazing at everything or something that’s extremely good at one thing… We really want something that’s extremely good at all things.” The company he helps lead trains a single foundation model that recombines skills across commands and robot types. Success hinges on scale. Without enough varied examples, robots falter when conditions drift even slightly.

Jonathan Hurst, cofounder of Agility Robotics, put the difficulty in perspective. “It’s dramatically harder to have an embodied AI; it’s 10 times harder to have an embodied AI,” he told the publication. Agility’s Digit humanoid currently moves totes in warehouses for GXO, Toyota, Schaeffler and Mercado Libre. Amazon tests it too. Yet deployments keep robots inside work cells separated from people. Safety remains paramount. Hurst noted that true autonomy will eventually mean deciding how to respond when handed a baby. That day sits far off.

Recent industry reports reinforce the pattern. The International Federation of Robotics highlighted agentic AI as a top trend for 2026. This hybrid combines analytical AI for decisions with generative AI for adaptability. The result aims at machines that handle complex environments on their own. (IFR)

Epoch AI assessed current robot performance in February. Navigation succeeds commercially in food delivery and warehouse transport. Manipulation works in structured warehouse picking but stalls in homes or multi-step jobs. Transfer to new objects or settings stays rare. Most systems require task-specific fine-tuning. That bottleneck limits scale. (Epoch AI)

Progress shows in simulation and hardware too. NVIDIA supports benchmarks such as RoboLab for testing generalist policies. University of Maryland researchers, backed by NVIDIA grants, build AI humanoids for household chores. Their systems blend generative AI with sequential decision-making. FieldAI supplies embodied software that works across robot types and recently partnered with Boston Dynamics for dynamic sites. These moves suggest the software layer may prove as decisive as the hardware.

Tesla pursues its Optimus humanoid to manage unsafe or repetitive work. The company applies vision and planning techniques refined in its vehicle fleet. Figure AI targets warehouses and factories with foundation models paired to physical manipulation. Physical Intelligence, Skild AI and others chase a single brain that transfers across bodies and tasks. Venture money flows. Analysts watch for the moment when one model delivers consistent results outside the lab.

Yet gaps persist. Training demands enormous data. Teleoperation by humans costs money and time. Simulations omit real physics quirks. World models that predict outcomes burn compute. Reinforcement learning can suffer catastrophic forgetting when new skills overwrite old ones. And safety incidents linger in memory. A 1979 case in which a Ford robot killed worker Robert Williams still informs standards. Surgical systems from Intuitive delegate most decisions to doctors. Bhushan Patel, principal technical program manager there, said the issue centers on how much control passes to the machine. “The question is not whether the robot is autonomous or not,” he observed. “The question is how much decision-making and action execution we are delegating to machine versus human.” Only a few FDA-cleared systems approach level three autonomy.

Dipam Patel, a Purdue PhD student working with the US Army, offered a blunt standard. “The robot should be able to do everything on its own without any external dependencies. Only then can we push towards general-purpose robots.” His view echoes the long road ahead. Agility aims to ship Digit v5, its first cooperatively safe AI-enabled humanoid, within the next 12 months. Hyundai trains Atlas humanoids at a metaplant for possible 2028 deployment in electric-vehicle production. Timelines stretch. Full home deployment that handles children or fragile objects could take decades.

Economics will decide adoption speed. One human supervising ten robots slashes costs below human labor. Recent reinforcement learning work shared on X improved recovery from mid-task errors. Success rates on 16-step missions rose from 38 percent to 71 percent. The gain matters because real deployments meet surprises. Robots that self-correct reduce supervision needs. That shifts the math. Companies such as BMW and Tesla see compound returns. A purchased robot holds value years later. Wages rise.

Investment and research accelerate. The AI boom draws robotics PhDs at record rates. Conferences like AUTONOMOUS 2026 in San Francisco gather founders focused on foundation models, sim-to-real gaps and compute stacks. BCG analysts describe physical AI as systems that maintain causal world models, predict results and reason under uncertainty. Level five reasoning, where robots pursue complex goals over time, still sits in the aspirational column. (BCG)

National security analysts note parallel advances. Google DeepMind’s Robotic Transformer 2 handles novel scenarios. NVIDIA’s Isaac GR00T foundation model targets generalized humanoid skills with fast and slow thinking modes. China aims to lead in humanoids by 2027. Market forecasts reach tens of billions within a decade. The UK launched a £52 million robotics adoption program earlier this year.

Form factors vary. Humanoids suit many roles but not all. Some jobs need small arms for tight apartments. Others require giant machines for farms. The best shape matches the work. That flexibility could widen deployment faster than pure bipedal designs.

Challenges remain formidable. Unstructured homes differ sharply from factory floors. Error recovery, long-horizon planning and safe interaction with people demand further gains. Regulatory standards evolve. Public acceptance hinges on proven reliability. Unions at Hyundai raised concerns during earlier Atlas tests.

Still the momentum builds. What once looked like science fiction now appears as incremental engineering problems. Robots already inspect bridges, move packages and scout crops. Next they may stock retail shelves, deliver inside buildings or assist in hospitals. Each successful niche funds the next capability jump.

Researchers and executives agree on one point. General-purpose autonomy will arrive gradually. No single demo will mark the transition. Instead a thousand small improvements compound until the machines simply work. When that happens the definition of labor changes. And the factories, warehouses and eventually homes that welcome these new workers will look different. The only certainty is that the machines are learning faster than before.

from WebProNews https://ift.tt/zGnL2aN