Army Cyber Command Trains AI Agents for Real Cyber Roles, With Humans Still Holding the Reins

Lt. Gen. Christopher Eubank delivered a striking message this month at the TechNet Augusta conference. The head of U.S. Army Cyber Command described a small team that had built and trained artificial intelligence agents to mimic human workflows in just 45 days. These agents now fill specific positions inside cyber units. They don’t make the final calls on risk. Humans do.

Task Force Lexington launched in April. Its roughly 10 members, a mix of civilians and service members led by a lieutenant colonel awaiting promotion, focus solely on this effort. They craft agents for roles that include developers, data engineers, host analysts and exploitation analysts. “You name the work role, we’re creating,” Eubank said, according to DefenseScoop.

The command has already deployed 17 agentic mission elements and cyber protection teams. They scour the Department of Defense Information Network daily. Some take on red team duties, hunting for weaknesses the way adversaries might. Others handle simpler tasks such as drafting situation reports. All of it happens under close watch.

“We’re now at a place in the cyberspace domain where we have to augment our workforce, and right now the fastest, easiest, smartest, best way to augment the workforce is to create agents and train those agents,” Eubank told DefenseScoop. He noted that everyone around the world, friend and foe alike, pursues AI capabilities. Staying ahead matters.

The training mirrors what human operators receive. Agents earn a form of Job Qualification Readiness before they receive missions. When they err, supervisors correct the approach, send the system back for retraining, and reintegrate it. This loop repeats until performance meets the standard. The process echoes how the Army corrects and retrains soldiers. But the speed changes everything.

Agents work at machine pace. They complete steps far quicker than people can. That creates tension. Commanders must decide which risks belong to humans and which an agent might handle. “Each and every day, we sit down as a group, we figure out the guardrails we’re going to apply to these agents, [and] we ask ourselves: Is it risk that a human should be answering, or is it risk that an agent can answer?” Eubank explained. “And right now, today, humans are all responsible for risk. We have not turned any agents loose to assume risk on their own behalf.”

The balance feels like a delicate dance. Agents check their output with people. Humans review before assigning the next step or ordering deeper analysis. The approach keeps decision authority with commanders while letting automation handle volume and velocity. Lt. Gen. Jeth Rey, Deputy Chief of Staff for G-6, captured the pressure. “Our adversaries are doing it at machine speed and we must catch up and we must get ahead,” he said, as reported by TechRadar.

Task Force Lexington deliberately sidestepped commercial frontier models. Eubank wanted to prove the work could advance with industry support but without dependence on the largest providers. Token costs worried him. So did the absence of clear governance. “We’re going to price ourselves out of business” without better controls, he warned. Compute shortages represent another hard limit. The Army will never have enough, he acknowledged.

Instead the team traveled to the Defense Innovation Unit in Silicon Valley. Senior engineers there shared practical lessons on integration. The visit reinforced a simple insight. Form a small, dedicated group and give it one mission. That model produced results faster than Eubank expected. The task force now fields requests from across the command. It tracks its own progress while pushing new projects forward.

This push fits a wider pattern. The Army has experimented with AI for scenario generation at the National Training Center and explored human-machine teaming in other domains. Recent contracts with firms such as Seekr aim to deliver trusted agents for frontline use. Yet the cyber focus stands out. Network defense underpins every military function. Communications, logistics, command, all rely on secure information systems. Adversaries already operate at digital speed. The service intends to match them.

Recent reporting highlights parallel efforts. Breaking Defense detailed how these agents receive training to the same standard as humans and operate inside defined work roles. The publication noted the emphasis on human oversight for any decision that carries operational risk. Such caution reflects lessons from private sector incidents where agents broke out of controlled environments.

Eubank’s team applies guardrails daily. They debate each new capability. They test in controlled settings before expanding use. The command avoids handing agents independent authority to act on the network. That restraint persists even as the technology shows promise in red teaming and protective missions.

Broader military interest in agentic systems grows. The service has deployed AI tools to support human resources functions for millions of soldiers, veterans and families. Other initiatives explore AI for wargaming, decision support and adaptive training scenarios. Yet success in cyber will likely set the tone for adoption elsewhere. If agents can reliably augment analysts and operators without introducing new vulnerabilities, the model could spread.

Challenges remain. Trust forms slowly. Humans must verify outputs even when agents move faster. Scaling beyond a 10-person task force will test the command’s ability to maintain standards. Governance questions loom large. So does the reality of limited compute. Eubank offered no illusions on that front.

Still, the early returns encourage. Agents trained in weeks rather than months. They handle repetitive work and free people for harder problems. They hunt threats across the DODIN every day. And they do so while commanders retain final say on risk.

The Army’s approach signals a pragmatic path. Build small. Train to human standards. Keep risk decisions with people. Measure progress against real missions rather than laboratory benchmarks. Expand only after guardrails prove solid. In a domain where adversaries move at machine speed, this measured integration may offer the surest route forward.

Recent coverage from Army.mil shows parallel education efforts. The Command and General Staff College now offers an AI Basics elective that teaches officers to build their own agents for unit problems. That pipeline could supply the next generation of leaders comfortable directing both human teams and digital ones.

Industry observers note the significance. The Army has moved from pilots to daily operations inside its most sensitive networks. Other organizations still debate frameworks. The service simply started with a small team, clear roles, and strict human oversight. Results followed.

from WebProNews https://ift.tt/HuoZY0F

Apollo’s Cloud Breach Exposes Private Equity’s Vulnerability to Vishing Gangs

Private equity giant Apollo Global Management confirmed this week that hackers stole names, birth dates, home addresses and Social Security numbers from its cloud systems. The admission marks the first public confirmation from a major financial player hit in a months-long extortion campaign.

But the details reveal more. Attackers didn’t exploit some novel software flaw. They called employees. They pretended to be IT support. They tricked people into handing over passwords and approval codes. Old tactics. New scale.

The breach occurred between July 6 and July 10. Apollo’s human resources chief, Matthew Breitfelder, laid out the basics in a letter filed with California’s attorney general. Hackers gained unauthorized access to certain cloud platforms. They made off with personal information belonging to an undisclosed number of people. The filing stops short of saying whether the victims were Apollo staff, portfolio company employees or something else.

Apollo manages more than $900 billion. It employs roughly 5,000 people. A breach at this scale carries weight. Yet the firm offered few additional specifics. Spokeswoman Giovanna Falbo declined to answer questions from TechCrunch, including whether any ransom changed hands.

One firm’s confirmation spotlights a wider assault on finance.

Weeks earlier, Google’s threat intelligence team dropped a detailed warning. They tracked a single group behind multiple extortion brands: Falcon, Helix, Pink and Redact. The actors previously operated under the BlackFile name until that brand supposedly shut down in May. Google saw the same infrastructure, the same phishing templates, the same voice-phishing playbook. “UNC6671 continues to rely on voice phishing (vishing) to target enterprise employees, posing as IT helpdesk staff facilitating mandatory, urgent security migrations,” the researchers wrote in their Aug. 6 analysis.

These calls often reached workers on personal cellphones. Victims landed on spoofed login pages. Adversary-in-the-middle tools grabbed credentials and multi-factor tokens. Once inside, scripts pulled data from Microsoft 365 and Okta environments. The group then demanded payment. Some victims paid hundreds of thousands of dollars. Google documented Bitcoin wallets tied to earlier BlackFile activity that collected more than $10 million before the rebrand.

Reuters broke the story in early August. Hackers had targeted Apollo along with Blackstone, Bridgewater Associates, Bain Capital and others. At the time, it remained unclear who actually lost data. Now Apollo’s filing removes the doubt for at least one name on that list. Reuters reported the initial targeting wave on Aug. 6.

CyberScoop added fresh color hours after the TechCrunch story. The outlet noted Apollo told regulators it found no evidence the stolen records appeared online or fueled immediate fraud. The company said it notified law enforcement, hired outside experts and tightened controls. Still, the piece highlighted how this campaign has touched private equity, law firms, rating agencies and medical technology companies. It also linked the activity to BlackFile’s successor brands. CyberScoop published its report on Aug. 21.

The pattern feels familiar. And relentless. Social engineering has powered breaches for decades. Yet the current wave shows how effectively modern attackers combine it with cloud access and automated exfiltration. They don’t need zero-days. They need a convincing phone voice and a believable story about an urgent security update.

Private equity sits in an awkward spot. These firms move enormous sums. They hold sensitive deal data, investor records and personal details on executives across portfolio companies. Much of that information lives in the same cloud platforms the attackers targeted. Defenses that work for banks don’t always translate. Speed matters more than caution in many deal teams. Employees juggle personal and corporate devices. MFA fatigue is real.

Google’s researchers pointed to exactly these weaknesses. They urged phishing-resistant authenticators such as FIDO2 keys. They called for tighter session controls, corporate-device requirements and better monitoring of identity-provider logs. Simple steps on paper. Hard to enforce at scale inside fast-moving investment shops.

Apollo isn’t alone in staying quiet. Most targets in the early reports still haven’t disclosed outcomes. That silence fuels speculation. Did others pay quietly? Are more notifications coming? The California filing only covers residents of that state. Other states will likely see their own notices in coming weeks.

Extortion economics explain the focus on finance. Stolen personal data sells. But strategic information about pending buyouts or funding rounds can be worth far more in the right hands. The attackers know this. Their ransom demands reportedly started high, sometimes millions, before negotiation brought them down. One Google-tracked campaign extracted $750,000 from a single victim.

So what happens next? Regulators will watch. Investors will ask harder questions during due diligence. Insurance underwriters may raise rates for firms that can’t prove strong identity controls. And the hackers? They’ll keep calling. New brand names may appear. The tactics will stay the same.

Apollo says it has strengthened security. Good. Others in the sector should treat this as more than a single incident. The campaign didn’t stop with one cloud environment. It adapted. It rebranded. It kept going. Finance runs on trust and information. Both just took another hit.

The breach letter is available through California’s attorney general site. Google’s full threat analysis offers the clearest picture yet of the actors behind these calls. Recent coverage from CyberScoop fills in operational details that emerged only after Apollo’s filing went public.

from WebProNews https://ift.tt/hCPpDej

From Satire to Strategy: How Recycled Wastewater Including Urine Is Already Cooling AI Data Centers

Jason Kelce stands at a toilet in the opening scene. The former Philadelphia Eagles star and co-founder of Garage Beer fills a container while delivering a deadpan line. “AI data centers waste millions of gallons of water.” He then steps outside. A crowd joins him. They sing in unison. “Let’s pee on computers together to save humanity.”

The music video, produced with Liquid Death, landed this week as a marketing stunt. It quickly sold out its limited-edition “Data Center Coolant Collector” glass mug priced at $18. Fine print on the product page and in the ad warns repeatedly. Don’t actually mail urine. The suits made them say it. Yet the crude humor struck a nerve. Public opposition to new data centers has climbed. A Gallup poll shows about seven in ten Americans now resist construction in their communities.

But here is the twist. The joke rests on a technical truth. Treated wastewater, which includes human urine after processing, already cools servers at scale. Experts who spoke to TechCrunch confirmed as much days after the video dropped. Michael Obradovitch, vice president of Data Center Global Accounts at Ecolab, called the commercial funny and tongue-in-cheek. He added that alternative water sources see use today at levels comparable to what the industry needs.

Bruno Pigott serves as executive director of the WateReuse Association. He previously acted as assistant administrator for water at the EPA. Pigott told the same outlet you would not pour raw urine straight into a cooling tower. The fluid carries salts, urea, bacteria and organic matter. These leave mineral deposits. Constant cleaning would follow. Evaporative cooling systems pass hot air over water to shed heat. The image of urine misting through that process makes the point clear. It would not work untreated.

Still, the broader concept holds. Wastewater treatment plants process sewage that contains urine. Advanced facilities apply membrane bioreactors, reverse osmosis and ultraviolet light. The output becomes safe for industrial reuse. In some cases the water reaches standards high enough to drink. Dr. Greta Zornes leads water reuse efforts at engineering firm CDM Smith. She has spent more than two decades in the field. Zornes now spends every workday on recycled water projects for data centers. “We use recycled water for cooling for all kinds of industries, and we have for decades,” she said. A boom in demand from tech facilities has changed her routine.

Data centers consume enormous volumes to keep chips from overheating. Evaporative systems account for most of that draw. A single mid-size facility can pull millions of gallons daily. Larger ones push toward five million. The Lawrence Berkeley National Laboratory calculated that U.S. data centers used roughly 17.4 billion gallons in 2023. That figure sits well below water spent on swimming pools or golf courses. The comparison offers little comfort to communities facing local shortages. Opposition has grown sharper as AI training clusters multiply.

Loudoun County, Virginia, illustrates the tension. More than 250 data centers already operate there. Plans call for at least two dozen more. As of 2025 the facilities drew about 200 million gallons of recycled water each day. That covered 43 percent of total demand. The remaining 260 million gallons, or 57 percent, came from potable supplies according to Loudoun Water. Proximity matters. Zornes explained that data centers must sit near sizable wastewater plants. Rural sites often lack the volume or treatment capacity. Building the pipes, plants and connections takes years.

Some operators have begun to act as anchors for new infrastructure. Meta pledged at least $270 million toward wastewater projects near its facilities. The investment aims to expand treatment capacity so that recycled supplies can grow. Obradovitch sees potential for more such arrangements. Data centers bring capital. Municipalities gain upgraded systems that benefit residents too. “That’s where data centers can actually come in and be anchors of water infrastructure,” he said.

Policy makers have taken notice. Pigott advocates for legislation that would offer a 30 percent tax credit for industries scaling recycled water systems. He believes the incentive would speed adoption across data centers and other heavy users. Senators have introduced the bipartisan Advancing Water Reuse Act to push similar measures. The timing aligns with rising scrutiny. Consumer backlash against AI products has intensified. Water use ranks high among the complaints.

Recent studies point to even larger opportunities. A paper published in PMC examined symbiosis between data centers and wastewater treatment plants worldwide. Treated effluent from these plants carries substantial cooling potential. Pairing facilities geographically could satisfy nearly all global data center cooling demand. The approach would recover waste heat from servers to dry sludge and power anaerobic digestion at the treatment side. Annual benefits include cutting 84 million tonnes of CO₂ equivalent emissions, conserving 1.3 billion cubic meters of freshwater, and generating net cost savings near $95.4 billion. The United States, Japan, China, the Netherlands and United Kingdom hold the greatest potential. The analysis appeared this year and builds on earlier work showing 18.2 billion tonnes of available wastewater annually with 593 million megawatt-hours of cooling energy.

Real-world projects have moved beyond theory. In Memphis, xAI’s Colossus supercomputer will draw treated wastewater instead of tapping the city’s drinking supply. The arrangement avoids pulling 3 million gallons daily from municipal potable sources. An engineer at the site noted that Elon Musk called it stupid to use clean water for cooling when lesser quality suffices. The city’s plant already treats 40 million gallons a day, leaving ample capacity. xAI will pay for the recycled resource. Construction delays have pushed timelines, yet the model demonstrates feasibility at hyperscale.

Other regions experiment with non-potable alternatives. A billionaire developer in West Texas targets fracking wastewater to serve AI facilities. The Permian Basin produces vast volumes of produced water alongside oil. Pipelines and treatment hubs already move millions of barrels daily. Data centers need land, power and water. The area offers all three at low cost. Similar thinking appears in Nebraska, where a Google-linked project builds a $10 million pipeline to route non-contact cooling water to a resource recovery facility.

Not every attempt has gone smoothly. In Cheyenne, Wyoming, a contractor for Meta flushed bacteria-contaminated water from a closed-loop cooling system into public sewers during construction of an AI campus. The incident introduced a rare bacterium into the recycled water network. City officials revoked discharge permits, drained and disinfected systems, and tightened rules. New policy now requires separate collection tanks for datacenter cooling discharges rather than direct sewer connections. The episode serves as a reminder. Infrastructure must match technical and regulatory realities.

Amazon reported using 2.5 billion gallons globally last year for cooling. The company compares that volume to the 3.3 trillion gallons Americans apply to lawns and gardens annually per EPA data. Microsoft and others echo the message that responsible sourcing from wastewater can limit impact. The claims invite skepticism in communities already strained. Yet the engineering exists. Treatment processes proven in space, where astronauts recycle urine into drinking water, scale up on Earth through industrial plants.

Pigott welcomed the attention the Liquid Death video brought. “I’m glad that people are concerned about water, and anything that raises awareness of water, however crude it may be, could actually be beneficial,” he said. The campaign offers a chance to explain existing solutions. Zornes and Obradovitch spend their days turning that awareness into projects. They design systems that blend treated effluent with evaporative towers, closed loops and heat recovery. The work demands coordination among utilities, tech operators, engineers and regulators.

Challenges remain. Scale-up takes capital and time. Rural expansion faces treatment bottlenecks. Public trust erodes when incidents like Cheyenne occur. Still, the trajectory looks clear. Recycled water will supply a larger share of data center cooling. Wastewater, urine included after rigorous processing, forms part of the mix. The Kelce video made the idea memorable. Engineers have quietly made it practical for years. As AI demand accelerates, those quiet efforts will determine whether communities face scarcity or share the burden through smarter infrastructure.

Recent coverage in Data Center Dynamics and PCMag captured the marketing wave. Both noted how the stunt rides a broader anti-data center sentiment that has gone viral. The PMC study on global symbiosis, meanwhile, quantifies what operators could achieve if they pair facilities systematically. Those numbers suggest the joke may one day look like an early signal of a necessary shift rather than mere provocation.

from WebProNews https://ift.tt/FrqZ8H3

Google’s Pixel Phones Gain Self-Fix Tools for Dropped Calls, Slow Data and Spotty Wi-Fi

Google is preparing to hand Pixel owners a new way to troubleshoot their own connectivity headaches. The feature, spotted in recent code, promises to scan for problems with mobile data, phone calls and Wi-Fi networks before offering step-by-step remedies. Early signs point to a tool that could cut down on support calls. Yet plenty of questions remain about when it will arrive and exactly how far it will go.

Researchers at Android Authority found the work inside version 1.0.962958926 of the Pixel Troubleshooting app. They manually enabled hidden screens to reveal what Google has built so far. The centerpiece is an option labeled “Connectivity health” that would live under Settings and then Network & internet. Tap it and the phone would report whether it has spotted trouble with any of the three main connection types.

From there users could dive into dedicated diagnostics for mobile data, calls or Wi-Fi. Mobile data diagnostics has progressed the furthest. It tests connection quality and speed. Then it suggests concrete changes. In one example the tool told the tester to set Private DNS to “off” or “automatic.” After the adjustment it generated a report listing every setting altered during the session. The status flipped to “Normal.”

Call diagnostics and Wi-Fi diagnostics still sit at their opening screens in the current build. No troubleshooting flows load behind them yet. That gap shows the project remains a work in progress. Google has not commented on a release schedule, which models will receive it first or which Android version will carry the code.

The new capability builds on tools Google already ships. Official support pages describe a narrower process available today. Open the Settings app, tap Device health & support, then choose Call diagnostics or Mobile data diagnostics. Google’s own documentation notes this option exists only in the US for US subscribers on Pixel 11 phones. It can auto-detect issues, optimize settings, run speed tests or call-quality checks through Google servers and produce detailed reports.

But those existing flows focus on specific symptoms. The upcoming Connectivity health menu aims to give one overview screen plus targeted help for all three connection categories. TechRepublic reported the discovery one day after the initial teardown and noted that the phone-side checks cannot verify carrier network health or upstream problems. A “Normal” result means the device believes its own settings look good. It does not guarantee the tower or internet backbone performs well.

Enterprise administrators may wonder how the tool behaves on managed devices. The teardown gives no indication whether it detects administrator-controlled policies before recommending DNS changes or other tweaks. Reports generated by the diagnostics would list modified settings but questions linger about where those files are stored and who can read them.

Pixel phones have offered other self-diagnostic menus for some time. Hidden test modes let users check battery health, sensors, cameras and more. A separate Bluetooth diagnostics tool arrived earlier this year. The connectivity addition fits a pattern. Google wants owners to solve straightforward issues without opening a support ticket or visiting a store.

Frustration with dropped calls and sluggish data runs high among smartphone users. Carriers often point fingers at the device. Device makers return the favor. A tool that quickly isolates phone-side configuration errors could shorten those arguments. It might also surface patterns that help Google improve future modem firmware or Android networking stacks.

Timing matters. The code surfaced just as Google prepares the Pixel 11 series and associated software drops. Similar features have appeared in test builds only to vanish or shrink before public release. APK teardowns offer a glimpse but carry no guarantees.

Still, the direction feels clear. Google continues to expand built-in troubleshooting across hardware and software. Recent Android betas include stronger cellular security logging that records modem events and potential threats such as jamming or downgrade attacks. Those protections sit alongside user-facing diagnostics. Together they suggest a broader push to make Pixels more self-reliant.

Users who test the current public diagnostics already see value. The mobile data tool can toggle airplane mode, check SIM placement, verify network type selection and recommend a full network settings reset when nothing else works. Instructions warn that not every Pixel supports every 5G band on every carrier. They advise contacting the operator for outages or plan changes once device settings check out.

The new unified menu could streamline that advice. One entry point would surface an overall health score then route the user to the relevant fixer. A generated report might serve as evidence when escalating to carrier support. At least that is the hope.

Privacy questions hover in the background. Diagnostic reports that list changed settings and test results could contain location or network identifiers. Google has not detailed data handling for this feature. Past Pixel tools send usage and diagnostics information only when users opt in. Whether the same consent model applies here remains unseen.

Analysts following Android development see the move as part of a larger effort to reduce reliance on third-party apps for basic maintenance. Plenty of network analyzer utilities already exist on the Play Store. Few integrate as deeply with system settings or offer automatic fixes. Google’s version would run with elevated privileges and direct access to toggle configurations that normal apps cannot touch.

Of course success depends on accuracy. False positives that send users chasing the wrong setting could erode trust. False negatives that declare everything normal while calls still fail would prove equally annoying. The mobile data example performed cleanly in testing. Broader real-world validation must wait for a wider rollout.

Google’s history with connectivity features offers mixed lessons. Adaptive Connectivity Services, once known as Connectivity Health Services, has quietly optimized background data use for years. The new diagnostics feel more visible and actionable. They speak directly to everyday pain points rather than operating behind the scenes.

Industry watchers will track whether the feature debuts alongside the next Pixel Drop or waits for a full Android release. Early code often changes. The Private DNS recommendation, for instance, might gain smarter logic to avoid conflicting with work profiles or VPN policies.

For now the discovery gives Pixel fans something to anticipate. A phone that not only connects but also explains why it sometimes refuses to do so represents a step forward in user control. It won’t solve every network outage. It could, however, prevent many unnecessary factory resets and support conversations. That alone would mark progress.

Additional reporting from recent days reinforces the momentum. Android Headlines described the work as giving owners more self-service options across connectivity types. The Times of India highlighted how the tool spots bad data, dropped calls and flaky Wi-Fi then walks users through corrections. No major new technical details emerged beyond the original teardown, but the coverage signals growing interest in Google’s shift toward proactive device maintenance.

from WebProNews https://ift.tt/giVqhUI

Fairphone Brings Its Fixable Phone to America: A Challenge to Throwaway Tech

After years of limited imports and third-party markups, Fairphone has finally arrived in the U.S. market with its latest model. The device, known as the Fairphone Gen 6+ or 6 Plus, sells for $649 or $650 depending on the retailer. It goes on sale today directly from the company and Amazon. No more workarounds. No more paying a premium to a middleman like Murena.

This marks a shift. Previous Fairphone models reached American buyers only through indirect channels. Those routes often added hundreds to the cost. One report noted U.S. customers paid around $900 for the prior generation. Now the company offers straightforward access. Buyers can pick it up unlocked for AT&T and T-Mobile networks. Verizon compatibility remains uncertified by the brand itself.

The phone itself looks familiar to those who followed the brand from Europe. A 6.31-inch LTPO AMOLED display runs at 120Hz. It sits just above full HD resolution. Inside sits a Qualcomm Snapdragon 7s Gen 4 processor paired with 12GB of RAM. Storage comes in at 256GB of UFS 3.1, expandable by microSD. Cameras include a 50-megapixel main sensor and 13-megapixel ultrawide. A 4,415mAh battery powers the package. Three colors greet buyers: Cobalt Blue, Horizon Black and a green option.

Yet specs alone don’t tell the story. The real point lies in how the device comes apart. Owners can replace 12 different parts using only a single screwdriver. The battery. The display. The USB-C port. Even the cameras and back cover. Many swaps take less than five minutes. No adhesives. No specialized tools. Parts range from $7.99 for a SIM tray to $89.99 for a new screen. This approach stands in sharp contrast to flagships from Apple and Samsung. Those devices often discourage repair. They glue components tight. They threaten warranty voidance.

iFixit awarded the previous model a perfect 10 out of 10 for repairability. The new version follows the same path. Fairphone includes a five-year warranty. Software updates stretch to 2033. That means Android 16 at launch with support running nearly eight years total. Such longevity remains rare in consumer electronics. Most manufacturers tie success to annual upgrade cycles. Fairphone bets on the opposite.

The company built its name on ethics and sustainability. More than 50 percent of materials come from recycled or fair sources. The firm claims 100 percent e-waste neutrality. For every phone sold, it takes one back. That supports circular practices through reuse, repair and recycling. These details matter to a growing segment of buyers. They care about where minerals originate. They question labor conditions in supply chains.

But entering the American market brings hurdles. Tariffs hit imported electronics. A Reuters report from late 2025 highlighted a 34 percent tariff impact on Fairphone’s costs. CEO Raymond van Eck addressed the issue head on. “Our strategy is built for uncertainty,” he told Reuters. “The tariffs weather may change daily, but the demand signal in the U.S. is clear.” He pointed to advancing right-to-repair legislation nationwide. That momentum, he said, creates opportunity.

Fairphone first tested U.S. waters with repairable headphones earlier this year. The audio line served as a beachhead. Sales grew fast. The company reported 61 percent year-on-year revenue growth in the third quarter of 2025. Device sales rose 61 percent. Audio increased 40 percent. Spare parts jumped 41 percent. Those numbers suggest pent-up interest. Consumers appear ready for alternatives to disposable gadgets.

Industry observers take notice. Gay Gordon-Byrne, executive director of The Repair Association, reacted positively to the launch. She told CNET, “I’m sure there will be a lot of consumer interest and interest in teardowns and evaluations.” Her group has pushed for repair rights for years. Easier access to parts and instructions forms a core demand. Fairphone delivers both.

Software choices add another layer. Some versions ship with stock Android. Others partner with Murena to offer /e/OS. That privacy-focused system builds on Android but removes Google tracking and data collection. It includes an Advanced Privacy widget and easy migration tools. The combination appeals to users wary of constant surveillance. One recent article from Gizmodo emphasized that this represents the first new Fairphone released in the U.S. running full-fledged Android. Previous options leaned toward de-Googled variants.

Practical features round out the package. A physical switch activates minimalist mode. It reduces distractions for focused use. A fingerprint sensor sits in the power button. The device carries an IP55 rating for dust and water resistance. Not class-leading. But adequate for daily life. Modular accessories include cases, lanyards, finger loops and card holders. Most cost $30 or less.

Critics point to trade-offs. The battery capacity sits lower than many competitors. Performance targets midrange use rather than flagship speed. Price at $650 positions it above budget options yet below premium models. Buyers pay for longevity instead of raw power. That equation won’t suit everyone. Early reactions on X show a mix of excitement and skepticism. Some users ask who will actually buy it. Others praise the stand against e-waste.

And the broader context matters. Smartphone lifespans have shrunk. Average replacement cycles hover around two to three years in many markets. Repair costs often exceed the value of older devices. Right-to-repair laws gain traction in states across the country. California, New York and others have passed measures. Federal interest grows. Manufacturers face pressure to provide parts and documentation for longer periods.

Fairphone anticipated some of these trends. The Dutch company launched in 2013 with a modular concept. It faced production challenges early on. Scaling ethical sourcing proved difficult. Yet persistence paid off. Spare parts availability for years after sale became a signature. Support extending to 2033 for the Gen 6+ sets a high bar. Few competitors match it. Google offers seven years on Pixel devices. Apple provides updates for roughly that span but makes repairs harder.

Recent coverage highlights the significance of this moment. A story published hours ago by 9to5Google detailed the full specifications and confirmed today’s availability. Another piece from Android Central explored the Murena partnership and privacy benefits of /e/OS. These reports build on the foundation laid by the original CNET coverage of the debut.

So what comes next? Fairphone plans further expansion. It eyes partnerships with mobile operators. More audio products could follow. The company aims to prove that repairable design scales. Success in the U.S. could influence other brands. Samsung and Google already offer some self-repair programs. Those remain limited compared with Fairphone’s approach. If consumer demand grows, pressure will mount for broader change.

The Gen 6+ won’t dominate sales charts. It targets a niche. Environmentally conscious buyers. Repair enthusiasts. Privacy advocates. People tired of forced obsolescence. Yet its presence matters. It demonstrates a different business model. One built around longevity instead of constant consumption. In an industry addicted to new releases, that stance feels refreshing.

Challenges remain. Competition stays fierce. Supply chain ethics require constant vigilance. Tariffs could rise or fall with political shifts. Consumer education takes time. Many still view repair as inconvenient. But the pieces align. Legislation moves forward. Awareness of e-waste grows. Spare parts sales already contribute meaningful revenue.

Fairphone’s U.S. entry arrives at an interesting time. Tech fatigue spreads. Repair cafes gain popularity. Younger buyers express concern about climate impact. Whether those trends translate into significant sales for a $650 modular phone remains to be seen. The company clearly believes the moment has come. Direct availability removes a major barrier. The product delivers on its promises of easy repair and long support.

Buyers now face a genuine choice. Stick with the familiar cycle of upgrades every couple years. Or try something built to last. The screwdriver sits in the box for a reason. Fairphone wants owners to use it. That invitation alone sets this device apart. In a market flooded with incremental improvements, a phone designed for disassembly offers something truly different.

from WebProNews https://ift.tt/PFVijXe

Debian’s Stark Choice: Ban AI Code or Embrace It With Guardrails

Debian turns 33 this month. The distribution that powers much of the internet’s infrastructure now faces one of its most divisive debates yet. Developers began casting votes August 15 on a general resolution that could reshape how the project handles large language models. Results won’t arrive until August 28. But the ballot already reveals deep fractures.

Eight distinct options sit before voters. One demands an outright ban written into the Social Contract. Another offers conditional acceptance with strict disclosure rules. Others split the difference. None of the above remains a real possibility. The discussion didn’t emerge from nowhere.

Earlier this year Debian punted on similar questions. LWN.net reported the project chose to handle AI-assisted contributions case by case. Lucas Nussbaum had floated a draft resolution that allowed such work under conditions like full accountability and disclosure. Conversations on the mailing lists stayed civil. They also exposed sharp differences. Russ Allbery pushed for precise terms. “AI” struck him as too amorphous. Sean Whitton called for clear distinctions between uses. The project simply wasn’t ready.

Matters accelerated this summer. A formal proposal to ban LLM contributions sparked fresh debate. By late July five options had emerged. Then eight. Voting opened with the clock ticking through the end of the month. Phoronix covered the start of balloting in detail. The choices range from prohibition to pragmatic acceptance.

Choice 1 adds explicit language to the Social Contract. “We will not allow direct contributions to Debian written with the use or assistance of large language models (LLMs) or other generative AI tools.” Matthias Geiger proposed it. Seconds came from heavyweights including Ian Jackson and David Bremner. The rationale runs long. Copyright status stays murky. Quality suffers from hallucinations. Reviewers burn out. New contributors skip the learning process. Training data often scraped without regard for licenses or robots.txt.

Geiger didn’t mince words. LLM output contradicts Debian’s deliberate pace. Stability built the project’s reputation. Rushing code that might contain hidden errors threatens that foundation. The ban targets direct contributions only. Upstream projects remain untouched. Enforcement would rely on trust. Yet the signal matters.

Lucas Nussbaum countered with Choice 2. Allow AI-assisted contributions. But only if contributors meet six conditions. They must verify legal compatibility of the tools. Confirm licensing and attribution for any third-party material. Take full responsibility for correctness, security and utility. Disclose significant use. Discuss bulk changes in advance. Protect confidentiality. Nussbaum gathered an impressive list of seconds that includes Stefano Zacchiroli and Julian Andres Klode. The proposal acknowledges every major concern. Then insists humans stay accountable.

Ian Jackson offered Choice 3. Reject LLMs as far as practical. Update the Code of Conduct. His text paints a grim picture. Environmental damage. Exploitation of creators. Disruption of the open web. Generation of low-value content. Mental health risks for users. Economic bubbles. The proposal stops short of total prohibition. Upstream realities make that impossible. Instead it demands human-written messages to other humans. Allows narrow exceptions. Treats violations as conduct issues. Several ban supporters seconded this one too.

Other options strike different balances. Pierre-Elliott Bécue’s Choice 4 accepts AI contributions for Debian-specific work while placing full responsibility on the submitter. Mark the changes. Sign them. Avoid cloud tools for sensitive data. Marc Haber’s Choice 5 calls for responsible use without endorsement or prohibition. Existing standards apply. Disclosure encouraged but not required. Tobias Frost’s cautious approach in Choice 6 prefers human work where practical yet trusts contributor judgment.

One proposal cuts to the project’s identity.

Gard Spreemann’s Choice 7 declares “Debian is created by humans.” Generative output cannot count as a direct contribution. Tools may assist. The final result must come from a person. The text draws inspiration from policies at GCC and Rust. It argues AI creates asymmetry. Reviewers carry extra burden. Trust erodes when contributions arrive without deep understanding. Holger Levsen takes the argument further in Choice 8. Climate destruction becomes the deal breaker. Resource consumption, energy demands and corporate motives render the technology unacceptable regardless of output quality.

These aren’t abstract arguments. Debian ships software millions rely upon. Servers. Desktops. Embedded systems. A single flawed package can cascade. Hallucinated code in a watch file or override risks silent breakage. Reviewers already shoulder heavy loads. Adding machine-generated patches that look plausible but hide subtle bugs accelerates burnout. Several proposers cited real examples from other projects.

Legal questions compound the technical ones. Courts have yet to settle whether LLM output carries copyright. Who owns it? The prompter? The model trainer? No one? Debian’s Free Software Guidelines demand clear licensing. Uncertainty clashes with that requirement. Training data scraped from public repositories without consent raises separate licensing issues. Some models ignore robots.txt. Others train on code released under strong copyleft terms.

Environmental costs draw fire too. Training and running frontier models consumes massive electricity. Data centers compete with residential power needs in some regions. Levsen’s proposal doesn’t attack users. It condemns the broader system that incentivizes ever-larger models. Fight the industry, not the individual developer who reaches for a productivity tool.

Yet productivity gains tempt many. Code completion, documentation drafts, translation assistance. Modern LLMs handle repetitive tasks well when humans verify output. Smaller, locally run models reduce privacy and environmental concerns. Several proposals explicitly allow such tools as long as final responsibility rests with the contributor. The split reflects genuine disagreement over where the line sits between assistance and replacement.

Recent coverage shows the debate resonates beyond Debian. XDA Developers noted the ballots opened amid diverging policies across Linux projects. The kernel accepts AI assistance under Linus Torvalds’ direction. Some compilers banned it. Debian’s decision could influence other distributions and upstream projects. Or it could produce another deferral if none of the options secures the required majority.

Proposal A needs a three-to-one supermajority. Others require simple majorities. Preferential voting means developers rank their choices. The outcome could land anywhere on the spectrum. A strong showing for the ban might signal cultural resistance. A victory for conditional acceptance could normalize disclosure practices. None of the above would kick the issue back to case-by-case handling once more.

But the conversation itself already changed things. Developers aired concerns in public. Proposals cited Gentoo’s restrictive policy and Codeberg’s approach. They referenced earlier Debian threads from 2024 and 2025. The project has wrestled with this for years. This vote forces a choice. Or at least an attempt at one.

Critics of heavy regulation worry about enforcement nightmares. How do you prove a patch came from an LLM? Static analysis fails. Stylistic tells disappear as models improve. Self-reporting becomes the norm. Trust remains essential. Proponents of the ban counter that a clear policy sets expectations. Contributors who disagree can work on non-Debian packages or upstream instead.

Supporters of permissive approaches point to reality. Many developers already experiment privately. Forbidding the practice won’t eliminate it. Better to set rules that preserve quality and accountability. Disclosure requirements let reviewers apply extra scrutiny. Bulk change rules prevent surprise floods of machine-generated patches.

And the human element. Debian’s strength has always been its community. People who understand the policies, the architecture, the social norms. Replacing that knowledge transfer with prompt engineering risks hollowing out the contributor base over time. Onboarding new maintainers already challenges the project. LLMs that produce working code without teaching the why could make matters worse.

So the vote matters. Not because it will settle every question. Technology moves too fast. Models improve. Legal precedents emerge. Energy sources change. But the outcome will telegraph Debian’s values to the wider free software world. Stability versus speed. Human craft versus machine assistance. Trust versus verification. The distribution that famously moves slow now decides whether that philosophy extends to artificial intelligence.

Votes continue through August 28. Statistics will appear on the Debian vote site as ballots arrive. Whatever the result, the discussion exposed real tensions. Debian isn’t alone. Every major project will face similar choices. How they answer will shape the next decade of open source development. For now, the Debian developers hold the floor. Their ranked preferences will speak for the project’s direction.

from WebProNews https://ift.tt/FySOBe9

Jamie Dimon’s Blunt Warning to UK’s New Chancellor: Higher Bank Taxes Risk Driving Capital Away

Jamie Dimon didn’t mince words. In a recent call with UK Chancellor John Healey, the JPMorgan Chase chief executive laid out a clear message. Higher taxes on banks could push jobs and investment elsewhere. The conversation, which took place last week ahead of the government’s October budget, echoes Dimon’s earlier cautions. But this time the stakes feel higher.

Prime Minister Andy Burnham’s administration has signaled openness to fresh levies on the financial sector. Strong bank profits have fueled calls from Labour voices for more revenue. Yet Dimon sees danger in that path. “If you have an uncompetitive tax system, capital leaves your country,” he said, according to the Fortune report on the exchange.

The remark lands with force. UK banks already shoulder a 3% corporation tax surcharge on profits above certain thresholds. Shareholders have shouldered billions in extra costs under the existing regime. Dimon put a number on it during a July podcast appearance. “I mean, it may sound great, ‘tax the banks’, but it’s $5bn that my shareholders paid on that extra tax.”

Short. Direct. And pointed.

That July interview, released on the Master Investor Podcast with Wilfred Frost, set the tone. Dimon warned then that such policies carry “adverse consequences.” He didn’t stop there. “I would be very cautious if I was a government thinking that penalising any company out of the ordinary is a good thing for that country,” he added, as reported by The Guardian.

His comments targeted the new leadership directly. Burnham had only recently taken office. The prospect of tax hikes on lenders quickly drew scrutiny. Dimon tied the issue to JPMorgan’s ambitious plans for Britain. A £3 billion headquarters project in Canary Wharf hangs in the balance. Raise taxes too much, he suggested, and the bank might rethink its commitment.

“I don’t know what I’d do,” Dimon said when asked about the potential impact on that project. The uncertainty carries weight. JPMorgan employs thousands in London. Its presence bolsters the city’s status as a global financial center. Lose momentum there and the ripple effects could spread.

But. The UK government faces real pressures. Public finances remain stretched. Debt levels loom large. Burnham’s team eyes additional revenue sources. Banks, flush with recent earnings, present an obvious target. Political appeal is clear. Economic fallout less so.

Dimon drew on American experience to make his case. Finance jobs in New York have declined, he noted, partly because of that city’s heavy tax burden. The parallel feels deliberate. What happens in one major hub can foreshadow troubles in another. London has competed fiercely with New York for talent and listings. Make the tax climate too hostile and the advantage shifts.

Recent signals from X amplify the tension. Bloomberg’s account captured the latest exchange. “JPMorgan’s Jamie Dimon warned UK Chancellor of the Exchequer John Healey in a call last week against higher taxes on banks as Prime Minister Andy Burnham’s government prepares its budget for October,” the Bloomberg article detailed, citing the Financial Times.

The Financial Times itself broke the news of the Healey call on Sunday. Dimon highlighted how taxes often drive jobs elsewhere. He pointed again to New York’s struggles. The message to Healey was unmistakable. Proceed with caution.

Industry observers see broader implications. Other banks watch closely. A move against one large player could signal wider policy shifts. Capital moves fast when conditions sour. London’s edge, built over decades, isn’t guaranteed forever.

Dimon offered some praise amid the warnings. He commended outgoing Chancellor Rachel Reeves for her efforts. “She did a great job,” he said in earlier remarks covered by Retail Banker International. That goodwill may buy some time. Yet the new team starts fresh. Healey must balance revenue needs with growth priorities.

The October budget will test those choices. Speculation swirls around possible surcharge increases or new levies. Burnham has left the door open. His government inherited an economy still recovering from multiple shocks. Brexit. Pandemic. Inflation. Each left marks.

Banks argue they already contribute plenty. Corporation tax. Levies. Employment taxes. The surcharge adds another layer. Push further and returns diminish. Investment decisions get reassessed. Headquarters. Hiring. Expansion.

Dimon’s track record lends credibility to his views. He has steered JPMorgan through crises. His perspective spans decades. When he speaks on policy, markets listen. Governments sometimes do too.

Still the politics pull the other way. “Tax the banks” resonates with voters facing cost of living strains. Few shed tears for large financial institutions. The challenge lies in separating rhetoric from reality. Taxes that appear painless can carry hidden costs. Slower growth. Fewer jobs. Reduced tax take over time.

Dimon made that connection explicit. Penalize companies beyond normal bounds and the country suffers. Capital doesn’t wait around. It finds friendlier shores. Other European centers. Asian hubs. Even back to the United States.

UK officials counter that the financial sector remains strong. London retains its position. Yet data on employment trends and listings tell a more nuanced story. Some activity has shifted. Paris gained ground after Brexit. New York keeps its pull.

The Canary Wharf project symbolizes bigger bets. Three billion pounds represents serious commitment. Jobs. Infrastructure. Prestige. Canceling or scaling back would send a signal. One that markets would read quickly.

Dimon stopped short of outright threats. He left ambiguity. “I don’t know what I’d do.” That uncertainty itself serves as pressure. Governments hate surprises in budget planning. Banks hate unpredictable tax regimes.

So the dance continues. Healey listens. Burnham decides. Dimon speaks his mind. The outcome will shape London’s financial future for years.

Recent commentary on X reflects the urgency. Users noted how governments often act surprised when capital departs after margin squeezes. One post highlighted Dimon’s podcast line about uncompetitive systems driving money away. The conversation has momentum.

Analysts at The Banker questioned timing. Dimon voiced concerns early in the new government’s tenure. That move carries risks for JPMorgan too. It could prompt officials to explore alternatives or harden positions. “The CEO’s interjection on bank tax so soon under the PM’s tenure creates risks for the US lender,” The Banker wrote in late July.

Yet silence carries risks as well. Policy gets set without input. Bad ideas gain traction. Dimon clearly prefers engagement. Even when the message is uncomfortable.

High government debt and deficits worldwide add another layer. Dimon warned about those pressures separately. They make tax policy choices harder. Every sector faces scrutiny. Banks just happen to be in the spotlight now.

The coming weeks will prove telling. Preparations for the budget intensify. Consultations continue. Dimon’s warnings may temper ambitions. Or they may be dismissed as self-serving. Either way the debate is joined.

London’s status isn’t static. It must be earned. Competitive taxes. Predictable rules. Open markets. These factors matter. Dimon believes they matter a great deal. His latest intervention aims to keep them front of mind.

Whether Healey and Burnham agree remains to be seen. The proof will appear in policy details. Numbers in the budget. Language around fiscal strategy. Markets will parse every line.

For now the warning stands. Tax hikes sound appealing. Consequences follow. Capital flows where it finds welcome. Britain has options. So do the banks.

from WebProNews https://ift.tt/huL5cbB