Australian Government Probes OpenAI for Alleged Illegal Access to Patient Health Records

The Australian government has launched a formal investigation into whether OpenAI broke the law by allegedly hacking into a sensitive government health website. The probe, announced by the Department of Health and Aged Care, centers on claims that researchers working with the artificial intelligence company used unauthorized methods to access restricted patient data systems during testing of new model capabilities.

According to reports from TechCrunch, the incident occurred when OpenAI employees or contractors attempted to extract structured medical records from a portal designed for authorized healthcare providers only. The site in question handles millions of records related to Medicare claims, pharmaceutical prescriptions, and vaccination histories. Australian authorities believe the access went beyond standard web scraping and involved techniques that bypassed authentication controls.

Privacy advocates have expressed alarm at the potential scale of the breach. The health portal contains highly sensitive personal information protected under strict federal laws including the Privacy Act 1988 and the My Health Records Act. If proven, the actions could result in significant fines or even criminal charges against individuals involved. OpenAI has maintained that its team operated within ethical boundaries during what it described as legitimate security research, though the company has not released detailed statements on the exact methods employed.

The investigation gained momentum after internal logs from the health department flagged unusual traffic patterns originating from IP addresses linked to OpenAI data centers. Security analysts examining the logs noticed repeated attempts to query database endpoints using crafted prompts that appeared designed to trick the system’s input validation. This approach mirrors techniques sometimes used in prompt injection attacks against large language models, but applied in reverse against traditional web applications.

Federal officials moved quickly to contain any possible data exposure. They temporarily restricted API access to the portal and began notifying affected parties whose records may have been viewed. The Department of Health confirmed that no evidence suggests bulk data was downloaded, yet even limited access to individual records raises serious questions about consent and oversight. Medical privacy experts argue that such incidents erode public confidence in digital health infrastructure that took years to build.

OpenAI’s rapid expansion into government and enterprise contracts has placed increased scrutiny on its operational practices. The company has positioned itself as a leader in safe artificial intelligence development, yet episodes like this one highlight gaps between stated principles and real-world testing procedures. Sources familiar with the matter told TechCrunch that the research team sought to improve the model’s ability to summarize complex medical documents but encountered rate limiting and access controls that prompted them to experiment with alternative entry points.

Critics within the cybersecurity community view the situation as symptomatic of a broader pattern. Technology firms increasingly test their systems against real-world data sources without always securing proper permissions first. In Australia, the situation is compounded by the country’s relatively small population and highly centralized health data architecture. A single portal serves as the gateway for most national health interactions, making it both an attractive target for research and a high-risk asset if compromised.

The Australian Signals Directorate, the nation’s cyber intelligence agency, has been brought into the investigation to assess technical aspects of the access method. Their preliminary findings suggest the team used automated scripts combined with manually refined queries to map the site’s structure. While not traditional hacking in the sense of exploiting software vulnerabilities, the systematic probing of protected endpoints may still violate computer misuse provisions under the Criminal Code Act.

Legal scholars following the case point out that intent will play a major role in determining outcomes. If OpenAI can demonstrate that its researchers believed they were operating on publicly accessible information or with implied consent, penalties might be limited to administrative warnings. However, evidence that the team knowingly circumvented login requirements could trigger civil penalties reaching into the millions of dollars as well as possible referrals to police for prosecution.

This episode arrives at a tense time for relationships between artificial intelligence developers and national governments. Many countries, including Australia, have begun drafting legislation that would require transparency around training data sources and testing methodologies. The European Union has already implemented strict rules through its AI Act, while the United States continues to rely on a patchwork of sector-specific regulations. Australia’s response could set important precedents for how smaller nations handle powerful foreign technology companies.

Health Minister Mark Butler addressed the situation during a press conference, emphasizing that patient trust remains the top priority. He stated that any organization, regardless of its global influence or technological sophistication, must respect Australian laws designed to protect citizens’ medical information. The minister announced additional funding for cybersecurity audits across all federal health databases to prevent similar incidents in the future.

OpenAI has cooperated with investigators by providing server logs and internal documentation, according to government sources. The company also paused related research projects pending the outcome of the review. In a brief statement, OpenAI reiterated its commitment to responsible development practices and expressed willingness to work with Australian authorities to strengthen safeguards around sensitive data.

The case has sparked renewed debate about the ethics of scraping public sector websites for artificial intelligence training. Proponents argue that such data contains valuable patterns that can improve diagnostic tools and administrative efficiency in healthcare. Opponents counter that the potential harms from unauthorized access outweigh any benefits, particularly when dealing with protected health information that individuals never consented to share with private corporations.

Academic researchers in the field of medical artificial intelligence have watched the situation closely. Many rely on de-identified datasets provided through official channels, yet they acknowledge that real-world performance often requires exposure to messier, more varied examples. The controversy may lead to the creation of new ethical review boards specifically for artificial intelligence projects involving government data.

As the investigation proceeds, authorities are examining similar incidents involving other major technology companies. Preliminary reports suggest that several organizations have tested boundaries with Australian government websites in recent years, though none have triggered the level of response seen with OpenAI. This broader review could result in updated guidelines for technology firms seeking to conduct research on public infrastructure.

The outcome of the Australian probe may influence how other nations approach similar situations. Countries with valuable public datasets, from tax records to educational statistics, are increasingly wary of foreign artificial intelligence companies treating their digital assets as free resources. International cooperation on digital standards has become more urgent as these conflicts multiply.

Privacy organizations have called for greater transparency from OpenAI regarding its data acquisition practices. They recommend that the company publish detailed reports on how it sources information for model training and testing, especially when that information comes from government systems. Such disclosures could help rebuild confidence among regulators and the general public.

Technical teams within the Australian health department have begun implementing additional layers of protection, including behavioral analysis tools that can detect unusual query patterns in real time. These measures aim to balance open access for legitimate medical professionals with stronger barriers against automated systems. The upgrades reflect a growing recognition that traditional username and password controls are insufficient against sophisticated artificial intelligence agents.

The incident also raises questions about the responsibility of cloud service providers that host both the artificial intelligence companies and government systems. Many of these providers serve both sides of the equation, creating potential conflicts of interest when disputes arise. Greater contractual clarity may be needed to define acceptable use policies across different customer categories.

Medical professionals have mixed reactions to the news. Some welcome the possibility that advanced artificial intelligence could reduce administrative burdens and improve patient outcomes through better data analysis. Others worry that repeated security incidents could make patients hesitant to engage with digital health services altogether. The balance between innovation and protection will require careful calibration by policymakers.

As details continue to emerge, the Australian government has pledged to keep the public informed about significant developments. The investigation is expected to take several months, involving forensic analysis of network traffic, interviews with OpenAI personnel, and consultation with independent cybersecurity experts. The findings could lead to new legislation specifically addressing artificial intelligence interactions with critical national infrastructure.

The situation serves as a reminder that technological capability must always be matched with appropriate governance structures. Organizations developing powerful artificial intelligence tools bear a special responsibility to ensure their pursuit of knowledge does not come at the expense of individual privacy rights or national security interests. How Australia resolves this particular case may shape the rules of engagement between governments and technology companies for years to come.

from WebProNews https://ift.tt/Pk7RVy8

Gmail’s Blue Overhaul: Why a Simple Color Swap Has Inbox Veterans Seeing Red

Google just painted over one of Gmail’s most recognizable visual cues. The yellow stars and importance chevrons that once popped against the white inbox background now appear in a saturated blue. The shift rolled out this week to many users on the web version. And the reaction came fast.

Accessibility drove the decision. Yellow struggles to meet modern contrast standards against white. Blue clears those bars with room to spare. The company laid it out plainly. In a post on X, the Gmail team stated, “We updated our default star and “Important” label colors from yellow to blue to meet modern accessibility standards. This change ensures inboxes are clearer, easier to read, and more inclusive for everyone.” (Android Authority, Sep 24, 2026).

Simple enough on paper. But long-time users disagree. They argue the new hue blends into Gmail’s existing blue accents. The result flattens years of learned visual hierarchy. Stars no longer stand apart from importance markers. Both now compete for attention in the same color family. Scanning an inbox full of messages suddenly takes more effort.

One user in Google’s support forums captured the frustration early. “The change of the Chevron to bright blue from the muted yellow has resulted in substantial screen noise,” they wrote. The post noted that the old muted yellow sat quietly beside the stars. The new blue version screams for attention. (Gmail Community, mid-September 2026).

The distinction between the two markers matters. Stars represent manual flags. Users click to add them. They act as personal bookmarks. Importance markers come from Gmail’s algorithm. The system weighs who you email often, which messages you open and reply to, keywords in emails you read, and actions like archiving or deleting. Hover over an importance marker and Gmail sometimes explains its reasoning. Click it to correct a mistaken call. That feedback trains the model. (Google Support).

Those differences once showed clearly. Yellow for both, yet context made them distinct. The star carried personal intent. The chevron signaled algorithmic priority. Now the identical blue shades erase that instant recognition. Everything looks urgent. Or nothing does.

Android Police captured the broader sentiment. Users took to Reddit and Google Support Forums to vent. The new markers make email scanning harder and add visual clutter, many said. Some received the change weeks ago. Others saw it only in the past few days. The rollout appears gradual, typical for Google. (Android Police, Sep 24, 2026).

But here’s the rub. Google offers partial fixes. For stars, head to Settings, then See all settings, General tab, and scroll to Stars. Select the yellow preset. Re-star any previously marked messages because the color change doesn’t apply retroactively. Importance markers lack a color option. Users can hide them entirely under Settings, Inbox tab, by choosing “No markers.” That removes the chevrons but also loses the algorithmic signals.

Developers already stepped in. One independent coder released a free Chrome extension called Gold Markers for Gmail. It simply swaps the new blue importance markers back to gold. No data collection. No extra permissions. The extension works only on accounts that have received the update. (Antonio Cosentino’s blog, Sep 18, 2026).

This isn’t Gmail’s first visual tweak. The service has added practical features lately. Direct copying of 2FA codes from emails. AI-powered search overviews that answer natural language questions about your inbox. Yet those additions feel like improvements. The color change strikes many as a downgrade to a core scanning tool.

Contrast requirements explain part of the choice. Web Content Accessibility Guidelines set strict ratios for text and icons. Yellow often falls short on white backgrounds, especially for users with low vision or certain color deficiencies. A vivid blue hits the numbers reliably. Still, critics point out that blue already dominates Gmail’s interface. Buttons, links, accents. Adding more blue reduces differentiation rather than enhancing it.

Power users built workflows around the old markers. Some rely on stars as a portable to-do list that syncs across clients via IMAP. Others use the importance view as a first filter before diving deeper. Multiple star colors have been available for years. Red for urgent. Green for completed. Blue for reference. The default change affects even those custom setups for some users, according to complaints on X.

One reply to Gmail’s announcement read, “You’ve completely ruined YEARS of email labelling in my inbox.” Another user asked for a color picker instead of a forced default. The volume of feedback suggests Google is watching. The product team said it tracks responses and monitors the rollout. Direct in-product feedback remains the best channel for individual cases.

The episode highlights a familiar tension. Companies optimize for standards and broad accessibility. Dedicated users optimize for speed and muscle memory. What improves readability for one group can disrupt efficiency for another. Inboxes process hundreds of messages daily for many professionals. Every extra millisecond of cognitive load adds up.

So far no reversal appears likely. Google rarely undoes accessibility-driven changes. The workarounds exist for now. Yellow stars return with a few clicks and some manual effort. Hiding markers removes noise at the cost of information. Third-party extensions fill the gap for those comfortable with them.

Yet the backlash serves as a reminder. Interface elements that seem minor often carry years of habit. The yellow markers had become invisible in the best way. They worked without drawing attention to themselves. The new blue version demands notice. Whether that trade-off proves worthwhile will show in the weeks ahead as more accounts receive the update.

Users who depend on quick visual parsing face a choice. Adapt to the blue markers. Restore what they can through settings. Or wait to see if feedback prompts further adjustments. For an email service that handles so much of daily work, even small changes carry weight. This one clearly does.

from WebProNews https://ift.tt/08E4Q5K

How Brian Chesky Built an AI Brain at Airbnb to Halve Meetings and Double Output

Brian Chesky faced a problem common among CEOs of fast-growing companies. He no longer knew everything happening inside Airbnb. The solution? An artificial intelligence system trained on thousands of his own presentations and documents. The result has been dramatic.

“My whole job was, ‘how can I not need meetings to know what’s going on inside the company?'” Chesky told Business Insider. He built what he calls an “intelligence corpus” or “brain.” It draws from 18,000 Keynote slides, 50,000 Google documents and extensive additional company data. Dashboards feed him real-time insights. Meetings? Cut in half. “This intelligence layer means I now have total information,” he said.

The changes run far deeper. Airbnb now ships over 600 features this year. That’s almost twice the previous pace. Nearly half of customer service requests get handled by AI without human involvement. Support costs per booking dropped 16% year-over-year. Revenue hit $3.6 billion in the second quarter, up 17%. The company grows faster than its rivals. All while keeping headcount roughly flat.

Chesky’s Personal AI Shift

It started at the top. Chesky fed hundreds of gigabytes of his files into Claude. He uses the model as a personal agent. Executive team members received AI tutors. The practice spread companywide after he hired Ahmad Al-Dahle, former head of Meta’s generative AI efforts including the Llama models, as chief technology officer in January 2026.

“I have so underestimated the impact of AI,” Chesky said in an August earnings discussion covered by New York Post. The expense of AI tokens runs higher than forecast. Yet the return dwarfs those costs. Productivity gains appear across search, sign-up, checkout, payments and host tools. Time from concept to launch fell by as much as 60%. AI now writes about 60% of new code.

But Chesky draws a sharp line. Airbnb won’t build frontier models. “We are not going to be a company that develops AI, but we’re going to be a company that applies AI,” he noted in recent remarks tracked on X. His goal remains clear. Turn Airbnb into an AI-native organization from the ground up. One founded today with this technology baked in.

The approach yields visible wins for users and hosts. An AI assistant launched in North America in 2025 now operates in more than 50 languages. Plans call for voice integration soon. Review summaries, listing highlights and personalized recommendations roll out steadily. Testing has begun on an AI-powered search function. Natural language queries produce conversational yet visual results. Titles and highlights generate in real time, tailored to each traveler.

Customer service delivers the clearest early victory. Forty-five percent of issues that begin with the AI agent resolve completely without escalation. That figure rose from about one-third earlier in the year. The business becomes simpler to run. Complex travel questions meet contextual understanding that generic chatbots lack.

And the ambition stretches further. Chesky committed at the Skift Global Forum to launching a full AI agent in 2027. Skift reported his exact words: “I’ve said this, and now you can hold me to a statement: Next year we will launch our agent.” The interface will prove “much richer than a chatbot.” Travelers might one day describe a broad trip goal — a family vacation to Europe, say — and watch the platform assemble options across stays, activities, transport and more.

This fits a larger vision. Airbnb expands beyond home rentals. The app now lists boutique hotels in major cities, offers car rentals, grocery delivery, airport transfers and luggage storage. Credits and price-match guarantees sweeten hotel bookings. Chesky envisions an “everything app for traveling and living.” Services could eventually generate $1 billion or more in annual revenue.

His push extends outside the core business too. Chesky backs a new AI lab focused on user interaction and design. He won’t serve as its CEO. The effort, first reported in June, reflects skepticism that general-purpose tools from OpenAI or others suffice for travel and commerce. Rich visual interfaces matter more than text conversations. Airbnb has declined partnerships with certain AI providers, preferring to shape the technology to its needs.

Wall Street notices. Shares climbed sharply after recent earnings. Analysts point to measurable gains: more demand, more supply, lower costs. Chesky compares AI to electricity. The long-term economic value accrues to those who apply it effectively, not merely those who build the underlying models. “I think applying AI is where most of the economic value will eventually be,” he said.

Challenges remain. Travel decisions involve emotion, taste and countless variables that resist simple automation. Chatbot-style interfaces often fail here. Chesky has said no one has fully cracked AI for travel or e-commerce yet. The richer agent he promises must overcome those limits. Execution risk exists. So does competition from Booking Holdings, Expedia and emerging AI travel startups.

Still, the internal transformation appears real. Engineers produce more with the same headcount. Hosts receive better tools for onboarding, pricing and management. Guests get faster resolutions and smarter recommendations. The CEO regains visibility into operations without endless meetings. Total information, he calls it.

So what does this mean for other leaders? Chesky argues many CEOs don’t fully grasp activities across their organizations. AI can close that gap. It demands hands-on engagement from the top. Founder mode, a concept he helped popularize, gains new relevance in the AI era. Details matter. Product intuition matters. General tools rarely deliver domain-specific breakthroughs.

Airbnb’s story shows one path forward. Ingest your own company’s knowledge. Build dashboards and agents tailored to real workflows. Measure obsessively — features shipped, resolution rates, cost per booking, speed to market. Spend more on inference when returns justify it. Stay focused on application over raw model development.

The numbers back Chesky’s bet so far. Revenue growth outpaces peers. Profitability improves. Innovation velocity rises. And he insists this represents only the beginning. An agent arrives next year. New services multiply. The AI brain that halved his meetings may soon reshape how millions plan their travels. The experiment continues. Results already impress.

from WebProNews https://ift.tt/iHw0eNW

Banks Sound Alarm on AI Shopping Agents: Fraud Risks Outpace Safeguards

Big banks are growing uneasy. A coalition of global lenders warned Tuesday that AI agents making purchases for consumers could drive higher rates of scams, fraud and data-privacy problems. The technology, they say, is advancing faster than rules or systems can handle.

The report, titled Building Trust in Agentic Commerce, comes from six institutions: Bank of America, Capital One, ING, NatWest, Commonwealth Bank of Australia and New Zealand’s ASB Bank. It paints a picture of consumer excitement colliding with practical dangers. Customers like the idea of AI handling shopping tasks. Yet many worry the agents won’t act in their best interests.

“Consumers are unclear if AI will act in their interests,” the banks stated in the paper. “They are concerned that AI agents may buy the wrong thing or spend too much – or even worse, lose their money to scams and fraud. They are not sure whether they will be protected or who they will need to go to if things go wrong.”

Those words capture the tension. People want convenience. Banks see liability headaches ahead. And the pace of change feels relentless. British retailer John Lewis reported AI-driven search traffic jumped to 2.5% from 0.3% a year earlier, according to a report in The Independent.

The concerns run specific. AI agents might ask users for card details then enter them directly on merchant sites. They could steer shoppers toward payment methods with weaker consumer protections. Bad actors could compromise the agents themselves or impersonate merchants. New forms of social engineering become possible. Disputes and chargebacks could surge for reasons outside merchants’ control.

PYMNTS Intelligence research shows the hesitation in practice. About 50% of Americans have used AI for some retail purchase. Only 22% start product research with the tools. When it comes to letting an agent actually shop and pay, that drops to 24%. “The change stops as the agent gets closer to the money,” the firm noted in its September report “Will the 2026 Shopping Season Go Agentic?”.

Banks Push for Transparency and Audit Trails

Issuers and acquirers often lack real-time visibility into an agent’s identity, the true merchant of record or the customer’s exact intent. Routine payment authorization doesn’t answer whether the agent bought what the person actually wanted. The banks propose solutions. They want clear disclosure whenever an AI agent participates in a transaction. Greater transparency into how agents reach decisions. Stronger safeguards around customer data. And full audit trails from initial customer instruction through authentication, intent, transaction steps, warnings, interventions and final outcome.

These records would help investigate problems, recover funds and settle disputes. Liability, the banks argue, should reflect where error or risk entered the chain. The principles remain voluntary for now. The group plans to take its proposals to policymakers and follow up with a second paper on implementation. The original Gizmodo coverage first highlighted the banks’ discomfort with autonomous shopping, available at gizmodo.com.

But the worries extend beyond retail. Recent Reuters coverage on the same day detailed how the banks see agentic commerce introducing new safety risks with potential for higher scam and fraud rates. The story is at reuters.com. PYMNTS followed with deeper analysis on the need for audit trails from instruction to payment outcome, linked here: pymnts.com.

Payment giants have started to lean in. Mastercard joined Visa in enabling AI bots to handle purchases with virtual cards carrying spending limits. That WSJ article from last week shows the industry bracing for this shift, at wsj.com. Yet the same story notes executives rethinking fraud models and what happens with rogue agents.

Consumer comfort varies by task. Experian’s recent study found 54% of consumers open to AI agents applying for credit on their behalf. Far more trust the tools to compare loans or hunt for better rates. Still, handing over actual payment authority crosses a line for many. The gap between research and execution reveals deep caution.

So the banks aren’t alone. Regulators watch closely. Bank of England officials have discussed kill switches for autonomous AI in markets. European Central Bank President Christine Lagarde has called AI a major risk to financial stability. Singapore’s central bank now ranks AI-assisted cyber and operational threats at the top of its concerns.

The report also flags risks to merchants. Higher dispute volumes could follow even when they deliver exactly what the agent ordered. Chargebacks might rise because the human never reviewed the final choice. And liability questions remain unresolved. Does authorizing an agent equal authorizing every purchase it makes? Courts haven’t tested that scenario yet.

Technology firms push forward. OpenAI, Anthropic, Google and Meta promote chatbots as shopping assistants. Early pilots have moved to live tests and limited scaling. The banks acknowledge customer demand. They just want guardrails before problems multiply.

One proposal stands out. Every participant in the transaction should know when an AI agent is involved and who it represents. Simple in theory. Complex in practice when agents act across multiple steps and services. The banks call for interoperability standards too. Without them, fragmented systems could create more blind spots.

Adoption data suggests acceleration. What was experimental a year ago now shows measurable traffic on major retail sites. That momentum won’t slow. Banks, for their part, aim to shape development rather than resist it. Their paper offers a framework. Whether policymakers and tech companies adopt the ideas will determine how safely this technology scales.

Fraud protections built for human shoppers don’t map neatly onto autonomous agents. Intent becomes harder to prove. Authentication layers multiply. Data flows grow more intricate. The coalition’s call for preserved evidence from start to finish addresses exactly these gaps. Without such records, sorting responsibility after a bad transaction turns messy fast.

And messy disputes hurt everyone. Customers lose trust. Merchants face costs. Banks handle the chargebacks and fraud claims. The principles paper tries to head off that cycle. It won’t solve every problem. But it marks a serious first step from the institutions that ultimately bear much of the financial risk.

The conversation has begun. Today’s warnings from major lenders could shape tomorrow’s rules. Consumers stand to gain powerful tools. They also face new vulnerabilities. Getting the balance right matters. The banks have laid out their view. Now the rest of the industry must respond.

from WebProNews https://ift.tt/WGeIDab

South Korea’s Central Bank Weighs Next Moves as AI Boom Fuels Growth and Price Pressures

SEOUL — The Bank of Korea raised its benchmark interest rate twice in quick succession this summer. It now sits at 3%. Yet the debate over further tightening has only grown sharper.

Inflation refuses to settle near the 2% target. Growth has surprised to the upside, powered by semiconductor exports tied to the global surge in artificial intelligence. Household debt climbs. Housing prices in the Seoul area accelerate. Policymakers tread carefully.

On Tuesday, board member Chang Yong-sung laid out the framework. The central bank will set the timing and pace of additional rate hikes by watching inflation, economic growth and financial stability conditions. “Going forward, factors such as accumulating financial imbalances, sector-specific income improvements, global market trends and geopolitical risks will likely shape financial stability,” he said in remarks released with the Reuters report.

Chang stressed coordination. Monetary policy and macroprudential tools must work together. Fiscal and financial authorities need to address difficulties for vulnerable groups. The message was clear. No predetermined path exists. Data will decide.

BOK Shifts Stance After Years of Accommodation

The shift began in July. The Monetary Policy Board lifted the base rate 25 basis points to 2.75%. All seven members backed the move. It marked the first hike in three and a half years. Inflation had climbed above 3%. Semiconductor exports roared ahead. Domestic demand showed signs of recovery.

August brought another 25 basis point increase. The rate reached 3%. Six members voted yes. One dissented. The central bank revised its 2026 growth forecast sharply higher to 3.3% from 2.6%. The 2027 projection rose to 2.9%. Inflation forecasts held at 2.7% this year and 2.3% next. Core inflation, however, was marked up. It is now seen at 2.5% for both years.

Governor Shin Hyun Song explained the back-to-back action. Preemptive steps help anchor expectations. They limit the eventual cost of reining in prices. Yet he also signaled caution. The board would assess the effects of the two hikes before deciding on more.

By September, the tone remained measured. The BOK’s own Monetary Policy Report stated it would decide additional hikes while closely monitoring inflation, economic developments and financial stability. Inflation is projected to stay above target for a prolonged period. Growth should remain solid, supported by exports, investment and recovering consumption. Housing prices and household loans are both picking up speed. (Bank of Korea)

Short sentences. Clear risks. Persistent price pressures. Stronger domestic demand. These forces collide.

Analysts have taken notice. JPMorgan Chase stands out for its hawkish view. The bank sees upside to its already bold call for the policy rate to reach 3.75%. It expects hikes in November, February and May of next year. Semiconductor-driven expansion could stoke even stronger inflation, provided credit and financial markets hold steady. That terminal rate exceeds the 3.5% median in Bloomberg surveys. (Bloomberg, published Sept. 21, 2026)

But not everyone agrees on the pace. Minutes from the August meeting, released in mid-September, revealed divisions. Dissenter Hwang Kun-il argued for holding rates. He pointed to rising delinquencies and the need to support growth. A stronger won had given room to evaluate prior moves. Such splits suggest future decisions may come more slowly. (Reuters)

And markets have priced in more. Some forecasts see the 1-year forward 3-month rate near 4.2%. That implies roughly four hikes from current levels. Economists at Goldman Sachs see only one additional 25 basis point move, taking the rate to 3.25%. The gap between market pricing and bank projections creates trading opportunities in rates markets.

Geopolitics adds uncertainty. Tensions in the Middle East have kept oil prices elevated. That feeds imported inflation in an energy-dependent economy. The won’s path matters too. A weaker currency amplifies cost pressures. Recent strength helped, yet volatility persists.

Financial stability concerns loom large. Household debt in South Korea ranks among the highest relative to income in major economies. Apartment prices in the capital region have accelerated. Consumer loans grow. The central bank has warned repeatedly about these imbalances. Chang’s comments Tuesday reinforced the need for complementary policies to prevent them from deepening.

So the board watches incoming numbers. August and September inflation readings. Business sentiment. Nominal GDP. Spillovers from the semiconductor sector into wages and consumption. Each data point shapes the next vote.

The October meeting will test the mood. Many expect no change then. But the door stays open for November. One more hike this year would bring the rate to 3.25%. Further moves in 2027 remain possible if growth stays hot and prices fail to moderate.

Korea’s economy shows a clear split. Export powerhouses in chips thrive on AI demand. Domestic sectors lag. This bifurcation complicates policy. Strong headline growth gives room to tighten. Yet uneven gains risk leaving parts of the economy behind.

Shin has emphasized flexibility. Each decision stays live. No mechanical path forward. That approach fits the moment. Global central banks navigate similar crosscurrents. The Federal Reserve recently hiked. Other major banks adjust. Korea cannot ignore external forces.

Yet its choices remain homegrown. Assess the data. Balance growth against prices. Guard financial stability. Chang’s remarks Tuesday captured the essence. The central bank holds the tools. It will use them as conditions warrant. No more. No less.

Investors, businesses and households wait for the next signal. The semiconductor cycle could extend. Oil prices could spike again. Domestic demand could accelerate faster than expected. Any of these would tilt the board toward tighter policy.

For now, the stance is restrictive. Rates at 3% after two quick moves. Inflation forecasts above target. Growth upgraded. The BOK has moved from accommodation to restraint. How far it goes depends on the balance of those three factors — inflation, growth, stability. The coming months will reveal whether more hikes lie ahead or if the current level suffices to cool pressures.

from WebProNews https://ift.tt/iq1uKY8

Linux 7.3-rc4 Released with Fixes for x86, ARM64, Btrfs, EXT4 and More

The Linux kernel development cycle continues its steady pace with the release of version 7.3-rc4. Linus Torvalds announced the fourth release candidate on the kernel mailing list, noting that the update arrives with a typical mix of fixes across various subsystems while maintaining overall stability for what has become a routine part of the merge window process.

This latest candidate brings together contributions from hundreds of developers, addressing issues that surfaced after the initial code merges for the 7.3 series. According to the Phoronix report, the patch volume sits at a moderate level compared to previous candidates, suggesting that the kernel team has already resolved many of the larger structural changes and now focuses on polishing specific areas that showed problems during testing.

Several architecture-specific updates appear in this release. The x86 maintainers included corrections for memory management and virtualization components, particularly around Intel and AMD hardware support. These changes help ensure consistent behavior across different processor generations, especially when dealing with newer instruction set extensions and power management features. ARM64 developers contributed fixes related to interrupt handling and memory barrier semantics that could have caused rare but problematic race conditions on multi-core systems.

Storage and file system improvements form another significant portion of the changes. The Btrfs file system received multiple patches that address edge cases in its RAID implementation and snapshot handling. Users who rely on Btrfs for complex storage setups will benefit from these refinements, which reduce the chance of metadata corruption during heavy write workloads. EXT4 also saw attention, with updates that improve handling of inline data and directory indexing under high contention.

The block layer and SCSI subsystem picked up several important corrections. These address potential deadlocks and error handling paths that became apparent during stress testing with modern solid-state drives and high-performance storage arrays. The device mapper component, which underpins technologies like LVM and software RAID, received fixes that enhance reliability when resizing logical volumes or handling transient device failures.

Networking remains a constant area of activity in kernel development, and 7.3-rc4 continues that tradition. The TCP stack saw improvements to congestion control algorithms and packet scheduling, helping to reduce latency in certain network conditions. WiFi drivers for popular chipsets from Intel, MediaTek, and Realtek gained bug fixes that resolve connectivity drops and power management issues reported by users on laptops and embedded devices. The Bluetooth subsystem also received attention, particularly around Low Energy device pairing and audio streaming stability.

Graphics and display support continue to evolve with this candidate. The AMD graphics drivers incorporated corrections for power management transitions and display output handling on newer GPU generations. Intel’s i915 driver team addressed several race conditions that could lead to screen corruption or system instability when switching between different display configurations. The Nouveau driver for NVIDIA hardware picked up minor fixes that improve compatibility with recent Mesa userspace components.

One area that has seen consistent attention throughout the 7.3 cycle involves Rust integration within the kernel. While still considered experimental, the infrastructure for writing kernel modules in Rust has received refinements that make the binding layer more reliable. These changes primarily affect how Rust code interacts with core kernel APIs for memory allocation and synchronization primitives. The Phoronix coverage highlights that these updates represent incremental progress rather than major new capabilities, which aligns with the cautious approach the kernel community has taken toward introducing new programming languages.

Hardware support continues to expand in expected ways. The sound subsystem gained better compatibility with newer audio codecs found in recent laptops and mobile devices. USB updates address enumeration problems with certain high-speed peripherals, while the PCI subsystem received patches that improve resource allocation on systems with complex bridge configurations.

Performance monitoring and debugging tools also benefited from this release candidate. The perf subsystem incorporated fixes that restore accurate event counting on certain CPU models, which should please developers who rely on precise measurements for optimization work. The tracing infrastructure saw improvements to probe handling that reduce overhead when using kprobes on hot code paths.

Security-related changes appear throughout the candidate, though many take the form of hardening rather than fixes for newly discovered vulnerabilities. The memory management code received additional checks that help prevent certain classes of use-after-free errors. The SELinux and AppArmor security modules both saw refinements to their policy handling that eliminate potential inconsistencies when dealing with complex namespace setups.

Testing and quality assurance efforts have clearly influenced the content of this release candidate. The kernel test robot and various automated validation systems flagged issues that developers then addressed before this snapshot. This process helps catch problems that might otherwise only surface after wider deployment. The moderate size of the diffstat for rc4 suggests that the development cycle has moved past the period of major feature integration and into a phase where stability takes priority.

For those following the kernel release schedule, this candidate arrives roughly on the expected timeline. The merge window for 7.3 closed several weeks ago, and the community has since focused on integrating bug reports from early testers and continuous integration systems. If the pattern from previous cycles holds, we can expect one or two more release candidates before the final 7.3 version arrives, assuming no major regressions appear in the coming days.

The involvement of major technology companies remains evident in the contributor list. Engineers from Intel, AMD, Google, Red Hat, SUSE, and various hardware vendors have all submitted patches that made their way into this candidate. This broad participation reflects the diverse requirements that the Linux kernel must satisfy, from enterprise servers and cloud infrastructure to consumer laptops and mobile devices.

Users who track kernel development through git trees can pull this candidate immediately for testing. The tag linux-7.3-rc4 is available in the main kernel repository, and distribution maintainers will likely begin incorporating it into their development branches soon. Those running earlier candidates or the 7.2 stable series may want to consider upgrading if they have encountered any of the specific issues addressed in this update.

The ongoing development process demonstrates how the kernel community balances the introduction of new features with the need for reliability. Each release candidate serves as both a snapshot of current progress and an opportunity for wider testing before finalization. The 7.3 series appears to be following this established pattern, with rc4 providing another step toward what should be a solid release when it eventually arrives.

Looking at the broader context of kernel development, the 7.3 cycle has incorporated several notable changes beyond the bug fixes highlighted in this candidate. Earlier merge windows brought updates to scheduling algorithms, memory management improvements, and expanded support for newer hardware platforms. The Rust integration work, while still in its early stages, continues to expand the options available to developers who want to write safer kernel code without sacrificing performance.

The file system updates deserve particular attention because they affect data integrity across countless deployments. The improvements to Btrfs and EXT4 in this candidate build upon years of refinement that have made these file systems suitable for demanding production environments. Similar attention to the networking stack ensures that Linux remains competitive in high-throughput data center applications while maintaining the responsiveness needed for desktop and mobile use cases.

Driver updates for modern hardware continue to arrive at a steady pace. As new processors, graphics cards, and peripheral devices reach the market, kernel developers work to ensure compatibility and optimal performance. This rc4 release includes work that helps prepare the kernel for hardware that vendors have only recently announced, demonstrating the proactive nature of much kernel development work.

The security enhancements, though sometimes less visible to end users, play a vital role in maintaining trust in the platform. By continuously improving memory safety, access controls, and cryptographic primitives, the kernel team helps protect systems against both known and emerging threats. These changes often result from collaboration between academic researchers, industry security teams, and independent developers who identify potential weaknesses before they can be exploited.

Performance work in this candidate focuses on reducing latency and improving efficiency rather than introducing dramatic new optimizations. The accumulated effect of many small improvements across subsystems often leads to measurable gains when running real-world workloads. Users who test this candidate on their specific hardware configurations may notice smoother operation in areas that previously showed occasional hiccups.

The documentation updates included in rc4, while not always the most exciting changes, help ensure that both new and experienced kernel developers can understand the current state of the code. Updated comments, improved explanations in the documentation directory, and clearer error messages all contribute to a more maintainable codebase over time.

As the kernel approaches what may be its final release candidates, the focus will increasingly shift toward identifying and resolving any remaining issues that could affect stability. The community relies on users who run these pre-release versions to report problems promptly so developers can address them before the version number increments to the final release.

This steady progression through the release cycle reflects years of experience in managing a project of this scale and complexity. The Linux kernel has grown to support an enormous range of hardware and use cases, yet the development process remains structured around these regular merge windows and release candidates. Each step brings the project closer to delivering another version that will serve as the foundation for operating systems and embedded devices worldwide for months or even years to come.

The contributions that make up 7.3-rc4 represent countless hours of development, testing, and review by individuals and teams spread across different time zones and organizations. Their collective effort ensures that Linux continues to meet the diverse needs of its users while preparing for the technological demands of the future. As testing of this candidate expands, feedback from the broader community will help shape the final form of the 7.3 release and influence the direction of subsequent development cycles.

from WebProNews https://ift.tt/IcX7RBH

Microsoft: AI Licenses Alone Fail—Workflow Redesign Drives 20% Sales Boost and 75% Faster Supply Chains

Microsoft has spent the last several years treating its own workforce as a living laboratory for artificial intelligence adoption. The results, shared in a September 17 blog post by Chief People Officer Kathleen Hogan, show that simply handing out licenses produces limited returns. Real performance gains arrive only after teams redesign the underlying processes that define how work actually happens.

Hogan’s account stands out because it comes from inside the company that sells Copilot to the world. Rather than promotional language, the post offers a candid assessment of what happened when Microsoft turned the same tools on itself. The numbers cited are concrete: sales teams that rebuilt their deal workflows around AI recorded 20 percent higher close rates, supply chain groups shortened cycle times by as much as 75 percent, and one nine-person product team delivered a major release in just 35 days. These outcomes did not appear on adoption dashboards that tracked login counts or prompt volume. They surfaced only after leaders stopped measuring usage and started measuring changed business results.

The distinction between adoption and transformation sits at the center of the lessons Microsoft learned. Early in the rollout, the company distributed licenses to more than 100,000 employees. Usage climbed, yet many managers reported that daily rhythms felt unchanged. Meetings still ran long, decision loops remained slow, and output quality showed only marginal improvement. The pattern repeated across departments. Engineers used Copilot to accelerate code completion, but the broader development lifecycle stayed anchored to the same handoffs and approval gates that existed before the tools arrived. Sales representatives generated better first drafts of proposals, yet the end-to-end sales motion continued to follow legacy stages that no longer matched the speed of the new material.

That realization prompted a shift in focus. Instead of asking “how many people are using the tools,” Microsoft began asking “which workflows produce measurably better outcomes when AI is embedded inside them.” The question forced teams to map every step of their current process, identify which steps consumed the most time or introduced the most error, and then redesign those steps around AI capabilities. The resulting changes looked different in every function, but they shared a common trait: AI stopped being an optional assistant and became part of the standard operating procedure.

Nowhere was this redesign more visible than inside the sales organization. Traditional deal reviews involved lengthy slide decks, multiple alignment meetings, and manual updates to customer relationship management records. After the transformation, teams built prompts that automatically pulled customer history, competitor data, and pricing guardrails into a single living document. The document updated in real time as new information arrived, eliminating the need for separate status reports. Sales managers could query the document directly instead of scheduling yet another sync call. The compressed cycle allowed representatives to spend more time with customers and less time on internal coordination. The 20 percent lift in close rates emerged from that time reallocation, not from any single prompt trick.

Supply chain teams followed a similar path. Legacy processes relied on batch reporting that arrived days or weeks after events occurred. When disruptions hit, teams spent hours reconciling data from separate systems before they could even begin to model alternatives. The redesigned workflow connected Copilot directly to live telemetry streams from factories, ports, and logistics partners. Planners could ask natural-language questions about inventory buffers, lead-time variances, or alternative sourcing options and receive answers grounded in current data. The system flagged anomalies before they became crises. Cycle times that once stretched into multiple weeks shrank dramatically. In one documented case, a procurement team reduced the end-to-end sourcing process from 28 days to seven. The 75 percent reduction cited by Hogan reflects the aggregate impact across dozens of such improvements.

Product development offered perhaps the clearest illustration of speed gains. A small team tasked with modernizing an internal administrative portal decided to treat the entire build as an AI-augmented effort. Rather than writing detailed specifications and handing them to developers, the group maintained a living requirements document that Copilot referenced continuously. Developers described features in plain language, received working code snippets, and iterated inside the same chat thread. Quality assurance, normally a separate phase, ran in parallel because the model could generate test cases and edge-condition scenarios on demand. The result was a production-ready service delivered in 35 days by nine people, a timeline that would have been unthinkable under the previous staged approach.

These examples share more than impressive metrics. Each required leaders to relinquish the comfort of measuring activity and instead embrace accountability for outcomes. Adoption dashboards still exist inside Microsoft, but they now serve as diagnostic tools rather than success indicators. When usage in a particular team remains high yet business metrics stay flat, the diagnosis almost always points to an unchanged workflow. The remedy is not more training on prompt engineering. It is a structured redesign exercise that brings together the people who do the work, the leaders who own the results, and the AI specialists who understand the models’ current limits.

Hogan emphasizes that this redesign work is harder than distributing software. It demands psychological safety so employees will admit which parts of their current process are inefficient. It requires time from senior leaders who must participate in mapping sessions rather than simply endorsing them. And it forces uncomfortable trade-offs when legacy controls, designed to reduce risk, now slow down the very outcomes leaders claim to want. Many teams discovered that their most deeply held assumptions about necessary approvals or mandatory documentation crumbled under scrutiny once real-time AI verification became available.

The cultural dimension of this shift receives equal attention in the blog post. Microsoft had to retrain managers to evaluate performance based on delivered value rather than hours logged or documents produced. Some employees initially worried that visible AI assistance would make their contributions look smaller. Leaders countered by celebrating outcomes publicly and by sharing specific examples of how human judgment, not machine output, remained the decisive factor. A sales representative might use AI to generate a compelling proposal, but only the representative’s relationship insight could close the deal. A supply chain analyst might receive instant scenario models, but only the analyst’s experience with supplier behavior could select the right path. Making those distinctions explicit helped reduce anxiety and increased willingness to experiment.

Another lesson involved the pace of capability improvement. Microsoft’s own models advanced rapidly during the period covered by the blog post. Features that required custom development in the first quarter became native capabilities by the third. Teams that had invested weeks building bespoke connectors found those connectors suddenly unnecessary. The realization pushed the company toward lighter, more adaptable integration patterns. Rather than locking workflows into rigid custom code, architects now favor composable prompts and reusable prompt libraries that can be updated as models evolve. This approach reduces technical debt and keeps the focus on business process rather than infrastructure maintenance.

Data governance also surfaced as a critical workstream. Early experiments sometimes pulled information from sources whose freshness or permission levels had not been fully validated. The resulting hallucinations, though infrequent, damaged trust. Microsoft responded by building clear data lineage into every AI-assisted workflow. Users now see source citations alongside generated content, and sensitive fields are automatically masked or restricted. The governance layer did not slow adoption once teams understood it protected rather than hindered their work. On the contrary, confidence in the outputs increased, which encouraged even broader use.

The blog post also addresses the scaling challenge. What works for a nine-person product team does not automatically translate to a division of 3,000. Microsoft created a central transformation office that maintains a library of proven workflow patterns. Teams can browse patterns for sales forecasting, code review, contract analysis, or incident response and then adapt the closest match to their context. This approach prevents every group from starting from scratch while still allowing local ownership of the final design. The central team also tracks which patterns deliver the highest return on effort so that future investment can concentrate on the most promising areas.

Perhaps the most sobering lesson concerns the limits of AI on its own. Hogan repeatedly returns to the idea that technology alone does not change behavior. Without deliberate process engineering, the tools become faster ways to do the same old things. The 100,000 licenses distributed early in the program provided a useful on-ramp, yet they did not constitute transformation. Only when leaders accepted the harder work of redesign did measurable business value appear. That distinction, she argues, separates organizations that will capture AI’s full potential from those that will simply automate yesterday’s inefficiencies.

Microsoft continues to refine its approach. New experiments explore multi-agent systems that hand work between specialized models without human intervention at every step. Other teams are testing how AI can participate in strategic planning sessions by synthesizing market signals in real time. Each experiment follows the same discipline: begin with the business outcome, redesign the workflow that produces it, then embed AI where it adds the most leverage. The company has made the methodology available to customers through its advisory services, suggesting that the lessons learned internally now inform external guidance.

For organizations still early in their own AI efforts, the Microsoft experience offers a practical sequence. First, resist the temptation to declare victory based on license counts or monthly active users. Second, identify a handful of high-impact workflows where delay or error carries measurable cost. Third, assemble cross-functional teams to map those workflows in detail, highlighting every handoff, approval, and data translation step. Fourth, prototype new designs that place AI at the center rather than the periphery. Fifth, measure the revised process against the original baseline using the same key performance indicators that mattered before the tools arrived. Where the gap is large and sustained, scale. Where it is not, revisit the design.

The blog post ends on a note of cautious optimism. Microsoft has seen tangible improvements in speed, quality, and employee experience, yet leaders acknowledge that the work has only begun. New model capabilities will continue to arrive, and each wave will require fresh examination of existing processes. The organizations that embed continuous redesign into their operating rhythm, rather than treating it as a one-time project, stand the best chance of staying ahead.

By sharing both the successes and the stumbles, Microsoft has provided a reference point more valuable than any marketing campaign. The message is straightforward: licenses are easy, transformation is not. The difference between the two explains why some companies see only modest productivity gains while others, like the teams inside Microsoft that fully embraced workflow redesign, achieve step-change improvements in the metrics that matter most to their business.

from WebProNews https://ift.tt/qlMk7EW