NVIDIA has been "gradually dropping support for older videocards," notes Hackaday, "with the Pascal (GTX 10xx) GPUs most recently getting axed."

"What's more surprising is the terrible way that this is being handled by certain Linux distributions, with Arch Linux currently a prime example.?" On these systems, updating the OS with a Pascal, Maxwell or similarly unsupported GPU will result in the new driver failing to load and thus the user getting kicked back to the CLI to try and sort things back out there. This issue is summarized by [Brodie Robertson] in a recent video.
"Users with GTX 10xx series and older cards must switch to the legacy proprietary branch to maintain support," explains an announcement on the Arch Linux mailing list. But Hackaday points out that using the legacy option "breaks Steam as it relies on official NVIDIA dependencies, which requires an additional series of hacks to hopefully restore this functionality.

"Fortunately the Arch Wiki provides a starting point on what to do."

The nonprofit Open Source Initiative offers "enriched" license pages with "relevant metadata to provide deeper insights and better support".

So which pages got the most pageviews in 2025? The MIT license, Apache 2.0 license, BSD licenses (3-clause and 2-clause), and GNU General Public license:

mit	(1.5M)
apache-2-0	(344k)
bsd-3-clause	(214k)
bsd-2-clause	(128k)
gpl-2-0	(76k)
gpl-3-0	(55k)
isc-license-txt	(35k)
lgpl-3-0	(34k)
OFL-1.1	(31k)
lgpl-2-1	(24k)
.	.

From the Open Source Initiative's announcement: Please note that these are aggregated pageviews from actual humans along the year of 2025... Actual humans (presumably) because the number of requests by bots or crawlers is several orders of magnitude higher (e.g. requests just for the MIT license are on the range of 10M per month).

We do provide an API service that gives access to the canonical list of OSI Approved Licenses — this is a very new service, which hopefully will be adopted by automated requests from CI/CD pipelines. One final observation is that the number of human pageviews is likely higher because we are using Plausible as our data source and a high percentage of our target audience uses Ad blockers, which by design are not accounted by Plausible. Users from China are also likely undercounted by Plausible for the same reason.

An anonymous reader quotes a report from the Associated Press: The State Department announced Tuesday it was barring five Europeans it accused of leading efforts to pressure U.S. tech firms to censor or suppress American viewpoints. The Europeans, characterized by Secretary of State Marco Rubio as "radical" activists and "weaponized" nongovernmental organizations, fell afoul of a new visa policy announced in May to restrict the entry of foreigners deemed responsible for censorship of protected speech in the United States. "For far too long, ideologues in Europe have led organized efforts to coerce American platforms to punish American viewpoints they oppose," Rubio posted on X. "The Trump Administration will no longer tolerate these egregious acts of extraterritorial censorship."

The five Europeans were identified by Sarah Rogers, the under secretary of state for public diplomacy, in a series of posts on social media. [...] The five Europeans named by Rogers are: Imran Ahmed, chief executive of the Centre for Countering Digital Hate; Josephine Ballon and Anna-Lena von Hodenberg, leaders of HateAid, a German organization; Clare Melford, who runs the Global Disinformation Index; and former EU Commissioner Thierry Breton, who was responsible for digital affairs. Rogers in her post on X called Breton, a French business executive and former finance minister, the "mastermind" behind the EU's Digital Services Act, which imposes a set of strict requirements designed to keep internet users safe online. This includes flagging harmful or illegal content like hate speech. She referred to Breton warning Musk of a possible "amplification of harmful content" by broadcasting his livestream interview with Trump in August 2024 when he was running for president.

An anonymous reader shares a report: The United States will take action against China's semiconductor industry, setting new tariffs on chips from China from June 23, 2027, that have 0% duties currently, the US Trade Representative said.

The announcement comes following a year-long investigation into China's chip imports into the United States, launched by the Biden administration and led by the U.S. Trade Representative. "China's targeting of the semiconductor industry for dominance is unreasonable and burdens or restricts U.S. commerce and thus is actionable," the agency said in its release.

Uber and Lyft plan to trial robotaxis in London starting in 2026 using autonomous vehicles from Baidu, as the UK fast-tracks approvals for self-driving cars on public roads. CNBC reports: Lyft's testing of Baidu's initial fleet of dozens of vehicles will begin in 2026, pending regulatory approval, "with plans to scale to hundreds from there," Lyft CEO David Risher said in a post on social media platform X on Monday. Meanwhile, Uber said that its first pilot is expected to start in the first half of 2026. "We're excited to accelerate Britain's leadership in the future of mobility, bringing another safe and reliable travel option to Londoners next year," the company added.

The moves add to Baidu's growing global footprint, which it says includes 22 cities and more than 250,000 weekly trips, as it races against other Chinese players like WeRide and Western giants like Alphabet's Waymo. The UK, in particular, has seen a wave of interest from driverless taxi companies, following the government's announcement in June that it would accelerate its plans to allow autonomous vehicle tech on public roads. The government now aims to begin permitting robotaxis to operate in small-scale pilots starting in spring 2026, with Baidu likely aiming to be among the first. The city of London has also established a "Vision Zero" goal to eliminate all serious injuries and deaths in its transportation systems by 2041, with autonomous driving technology expected to play a large role.

The FCC has banned approval of new foreign-made drones and components, citing "an unacceptable risk" to national security. The move will most heavily impact DJI but it "does not affect drones or drone components that are currently sold in the United States." Reuters reports: The tech was placed on the commission's "Covered List," barring DJI and other foreign drone manufacturers from receiving the FCC's approval to sell new drone models for import or sale in the U.S. In Monday's announcement, the agency said that the move "will reduce the risk of direct [drone] attacks and disruptions, unauthorized surveillance, sensitive data exfiltration and other [drone] threats to the homeland."

FCC Chair Brendan Carr said in a statement that while drones offer the potential to boost public safety and the U.S.' posture on global innovation, "criminals, terrorists and hostile foreign actors have intensified their weaponization of these technologies, creating new and serious threats to our homeland."

The ruling comes as China hawks in Congress amplify warnings about the security risks of drones made by DJI, which accounts for more than 90% of the global market share. But efforts to crack down on Capitol Hill have been met with some pushback due to the potential impacts of curbing the drone usage on U.S. businesses and law enforcement. A wide variety of sectors, including construction, energy, agriculture and mining companies, as well as local police and fire departments across the country, deploy DJI-made drones.

An anonymous reader quotes a report from Ars Technica: On Monday, the US Department of the Interior announced that it was pausing the leases on all five offshore wind sites currently under construction in the US. The move comes despite the fact that these projects already have installed significant hardware in the water and on land; one of them is nearly complete. In what appears to be an attempt to avoid legal scrutiny, the Interior is blaming the decisions on a classified report from the Department of Defense.

The second Trump administration announced its animosity toward offshore wind power literally on day one, issuing an executive order on inauguration day that called for a temporary halt to issuing permits for new projects pending a re-evaluation. Earlier this month, however, a judge vacated that executive order, noting that the government has shown no indication that it was even attempting to start the re-evaluation it said was needed. But a number of projects have gone through the entire permitting process, and construction has started. Before today, the administration had attempted to stop these in an erratic, halting manner. Empire Wind, an 800 MW farm being built off New York, was stopped by the Department of the Interior, which alleged that it had been rushed through permitting. That hold was lifted following lobbying and negotiations by New York and the project developer Orsted, and the Department of the Interior never revealed why it changed its mind. When the Interior Department blocked a second Orsted project, Revolution Wind offshore of southern New England, the company took the government to court and won a ruling that let it continue construction.

Today's announcement targets those and three other projects. Interior says it is pausing the permits for all five, which are the only projects currently under construction. It claims that offshore wind creates "national security risks" that were revealed in a recent analysis performed by the Department of Defense, which apparently neglected to identify these issues during the evaluations it did while the projects were first permitted. What are these risks? The Interior Department is being extremely coy. It notes that offshore wind turbines can interfere with radar sensing, but that's been known for a while. In announcing the decision, Interior Secretary Doug Burgum also noted "the rapid evolution of the relevant adversary technologies." But the announcement says that the Defense Department analysis is classified, meaning nobody is likely to know what the actual reason is -- presuming one exists. The classification will also make it far more challenging to contest this decision in court.

"Perhaps no group of fans, industry workers, and consumers is more intense about AI use than gamers...." writes New York magazine's "Intelligencer" column: Just this month, the latest Postal game was axed by its publisher, which was "overwhelmed with negative responses" from the "concerned Postal community" after fans spotted AI-generated material in the game's trailer. The developers of Arc Raiders were accused of using AI instead of voice actors, leading to calls for boycotts, while the developers of the Call of Duty franchise were called out for AI-generated assets that players found strewn across Black Ops 7.Games that weren't developed with generative AI are getting caught up in accusations anyway, while workers at Electronic Arts are going to the press to describe pressure from bosses to adopt AI tools. Nintendo has sworn off using generative AI, as has the company behind the Cyberpunk series. Valve, the company that operates Steam, now requires AI disclosures on listed games and surveys all submitters. Perhaps sensing the emergence of a new constituency, California congressman Ro Khanna responded in November to the Call of Duty backlash:"We need regulations that prevent companies from using AI to eliminate jobs to extract greater profits," he posted on X....

AI is often seen as a tool for managers to extract more productivity and justify layoffs. Among players, it can foster a sense that gamers are being tricked or ripped off, while also dovetailing with more general objections to generative AI. It can sometimes be hard to tell whether gamer backlash is a bellwether or an outlier, an early signal from our youngest major creative industry or a localized and unique fit of rage. The sheer number of incidents here suggests the former, which foretells bitter, messy, and confusing fights to come in entertainment beyond gaming — where, notably, technologies referred to as "AI" have previously been embraced with open arms.
And now "the price of the sort of memory PC gamers most want to buy has skyrocketed" (per Tom's Hardware). "The rush to build data centers is making it much more expensive to game. Nobody's going to be happy about that."

Insider Gaming shares another example of anti-AI sentiment in the gaming industry: The Indie Game Awards took place on December 18, and, as many could assume, Clair Obscur: Expedition 33 took home the awards for Game of the Year and Debut Game. However, things have changed and The Indie Game Awards are making a big decision to strip the Clair Obscur and developer Sandfall Interactive of their awards over the use of gen AI in the game.

In an announcement made on Saturday afternoon, Six One Indie, the creators of the show, said that it's removal comes after the discovery after voting was done, and the show was recorded. "The Indie Game Awards have a hard stance on the use of gen AI throughout the nomination process and during the ceremony itself," the statement reads. "When it was submitted for consideration, representatives of Sandfall Interactive agreed that no gen AI was used in the development of Clair Obscur: Expedition 33.
Polygon notes the award-stripping is "due to inclusion of generative AI assets at launch that were quickly patched out." Quotes from earlier in the year from Sandfall Interactive's FranÃois Meurisse made the rounds on social media last week amid a news cycle caught up in the use of generative AI in games... In June, the Spanish outlet El País published a story including an interview conducted around Clair Obscur's launch, in which Meurisse admitted that Sandfall used a minimal amount generative AI in some form during the game's development... Clair Obscur: Expedition 33 launched with what some suspected to be AI-generated textures that, as it clarified to El País, were then replaced with custom assets in a swift patch five days after release.

Longtime Slashdot reader schwit1 shares a report from Ars Technica: Every other week, it seems, a new Chinese launch company pops up with a rocket design and a plan to reach orbit within a few years. For a long time, the majority of these companies revealed designs that looked a lot like SpaceX's Falcon 9 rocket. The first of these copy cats, the medium-lift Zhuque-3 rocket built by LandSpace, launched earlier this month. Its primary mission was nominal, but the Zhuque-3 rocket failed its landing attempt, which is understandable for a first flight. Doubtless there will be more Chinese Falcon 9-like rockets making their debut in the near future. However, over the last year, there has been a distinct change in announcements from China when it comes to new launch technology. Just as SpaceX is seeking to transition from its workhorse Falcon 9 rocket -- which has now been flying for a decade and a half -- to the fully reusable Starship design, so too are Chinese companies modifying their visions.

The trend began with the Chinese government. In November 2024 the government announced a significant shift in the design of its super-heavy lift rocket, the Long March 9. Instead of the previous design, a fully expendable rocket with three stages and solid rocket boosters strapped to the sides, the country's state-owned rocket maker revealed a vehicle that mimicked SpaceX's fully reusable Starship. Around the same time, a Chinese launch firm named Cosmoleap announced plans to develop a fully reusable "Leap" rocket within the next few years. An animated video that accompanied the funding announcement indicated that the company seeks to emulate the tower catch-with-chopsticks methodology that SpaceX has successfully employed.

But wait, there's more. In June a company called Astronstone said it too was developing a stainless steel, methane-fueled rocket that would also use a chopstick-style system for first stage recovery. Astronstone didn't even pretend to not copy SpaceX, saying it was "fully aligning its technical approach with Elon Musk's SpaceX." And then, on Friday, the state-aligned China.com reported that a company called "Beijing Leading Rocket Technology" took things a step further. It has named its vehicle "Starship-1," adding that the new rocket will have enhancements from AI and is billed as a "fully reusable AI rocket."

Meta has paused its third-party Horizon OS headset program, effectively canceling planned VR headsets from Asus and Lenovo as it refocuses on "building the world-class first-party hardware and software needed to advance the VR market." Road to VR reports: A little over a year and a half ago, Meta made an "industry-altering announcement," as I called the move in my reporting: the company was rebranding the Quest operating system to 'Horizon OS' and announced it was working with select partners to launch third-party VR headsets powered by the operating system. Meta specifically named Asus and Lenovo as the first partners it was working with to build new Horizon OS headsets. Asus was said to be building an "all-new performance gaming headset," while Lenovo was purportedly working on "mixed reality devices for productivity, learning, and entertainment."

But as we've now learned, neither headset is likely to see the light of day. Meta say it has frozen the third-party Horizon OS headset program. "We have paused the program to focus on building the world-class first-party hardware and software needed to advance the VR market," a Meta spokesperson told Road to VR. "We're committed to this for the long term and will revisit opportunities for 3rd-party device partnerships as the category evolves."

GitHub will begin charging $0.002 per minute for self-hosted Actions runners used on private repositories starting in March. "At the same time, GitHub noted in a Tuesday blog post that it's lowering the prices of GitHub-hosted runners beginning January 1, under a scheme it calls 'simpler pricing and a better experience for GitHub Actions,'" reports The Register. "Self-hosted runner usage on public repositories will remain free." From the report: Regardless of the public repo distinction, enterprise-scale developers who rely on self-hosted runners were predictably not pleased about the announcement. "Github have just sent out an email announcing a $0.002/minute fee for self-hosted runners," Reddit user markmcw posted on the DevOps subreddit. "Just ran the numbers, and for us, that's close to $3.5k a month extra on our GitHub bill." [...]

"Historically, self-hosted runner customers were able to leverage much of GitHub Actions' infrastructure and services at no cost," the repo host said in its blog FAQ. "This meant that the cost of maintaining and evolving these essential services was largely being subsidized by the prices set for GitHub-hosted runners." The move, GitHub said, will align costs more closely with usage. Like many similar changes to pricing models pushed by tech firms, GitHub says "the vast majority of users ... will see no price increase."

GitHub claims that 96 percent of its customers will see no change to their bill, and that 85 percent of the 4 percent affected by the pricing update will actually see their Actions costs decrease. The company says the remaining 15 percent of impacted users will face a median increase of about $13 a month. For those using self-hosted runners and worried about increased costs, GitHub has updated its pricing calculator to include the cost of self-hosted runners.

Merriam-Webster crowned "slop" its 2025 Word of the Year, reflecting growing public awareness and and fatigue around low-quality, AI-generated content flooding the internet. "It's such an illustrative word," said Greg Barlow, Merriam-Webster's president. "It's part of a transformative technology, AI, and it's something that people have found fascinating, annoying and a little bit ridiculous." The Associated Press reports: "Slop" was first used in the 1700s to mean soft mud, but it evolved more generally to mean something of little value. The definition has since expanded to mean "digital content of low quality that is produced usually in quantity by means of artificial intelligence." In other words, "you know, absurd videos, weird advertising images, cheesy propaganda, fake news that looks real, junky AI-written digital books," Barlow said. "Words like 'ubiquitous,' 'paradigm,' 'albeit,' 'irregardless,' these are always top lookups because they're words that are on the edge of our lexicon," Barlow said. "'Irregardless' is a word in the dictionary for one reason: It's used. It's been used for decades to mean 'regardless.'"

The announcement can be found here.

An anonymous reader shares a report: Amazon has quietly added a new AI feature to its Kindle iOS app -- a feature that "lets you ask questions about the book you're reading and receive spoiler-free answers," according to an Amazon announcement.

The company says the feature, which is called Ask this Book, serves as "your expert reading assistant, instantly answering questions about plot details, character relationships, and thematic elements without disrupting your reading flow."

Publishing industry resource Publishers Lunch noticed Ask this Book earlier this week, and asked Amazon about it. Amazon spokesperson Ale Iraheta told PubLunch, "The feature uses technology, including AI, to provide instant, spoiler-free answers to customers' questions about what they're reading. Ask this Book provides short answers based on factual information about the book which are accessible only to readers who have purchased or borrowed the book and are non-shareable and non-copyable."

As PubLunch summed up: "In other words, speaking plainly, it's an in-book chatbot." [...] Perhaps most alarmingly, the Amazon spokesperson said, "To ensure a consistent reading experience, the feature is always on, and there is no option for authors or publishers to opt titles out."

Friday six European Union countries "asked the European Commission to water down an effective ban on the sale of internal combustion engine cars slated for 2035," reports Reuters The countries have asked the EU Commission to allow the sale of hybrid cars or vehicles powered by other, existing or future, technologies "that could contribute to the goal of reducing emissions" beyond 2035, a joint letter seen by Reuters showed on Friday. The letter was signed by the prime ministers of Bulgaria, the Czech Republic, Hungary, Italy, Poland and Slovakia. They also asked for low-carbon and renewable fuels to be included in the plan to reduce the carbon emissions from transportation...

Since they adopted a regulation that all new vehicles from 2035 should have zero emissions in March 2023, EU countries are now having second thoughts. Back then, the outlook for battery electric vehicles was positive, but carmakers' efforts have later collided with the reality of lower-than-expected demand and fierce competition from China.
Car and Drive reports that Chancellor Friedrich Merz of Germany also "wants to allow exceptions for plug-in hybrids, extended-range EVs, and 'highly efficient' combustion vehicles beyond the current 2035 deadline." They cite a report in Automotive News. The European Commission hasn't made any official changes yet, but mounting pressure suggests that a revised plan could be coming soon.... Apostolos Tzitzikostas, the European Commissioner for Sustainable Transport and Tourism, was cited by the German paper Handelsblatt as saying that the EU "will take all technological advances into account when reassessing fleet emission limits, including combustion engines running on e-fuels and biofuels." And these renewable products will apparently be key pieces of the puzzle. BMW uses a vegetable-oil-derived fuel called HVO 100 in its diesel products throughout Europe. The plant-oil-based fuel reportedly reduces tailpipe emissions by 90 percent compared with traditional diesel. For its part, Porsche has been working on producing synthetic fuel at a plant in Chile since 2022.

The European Commission is set to meet on December 10. At that time, the body is expected to assemble a package of proposals to help out the struggling European automotive industry, though the actual announcement may be pushed to a later date.
Thanks to long-time Slashdot reader sinij for sharing the article.

FreeBSD 15.0-RELEASE arrived this week, notes this report from The Register, which calls it the latest release "of the Unix world's leading alternative to Linux." As well as numerous bug fixes and upgrades to many of its components, the major changes in this version are reductions in the number of platforms the OS supports, and in how it's built and how its component software is packaged.

FreeBSD 15 has significantly reduced support for 32-bit platforms. Compared to FreeBSD 14 in 2023, there are no longer builds for x86-32, POWER, or ARM-v6. As the release notes put it:

"The venerable 32-bit hardware platforms i386, armv6, and 32-bit powerpc have been retired. 32-bit application support lives on via the 32-bit compatibility mode in their respective 64-bit platforms. The armv7 platform remains as the last supported 32-bit platform. We thank them for their service."

Now FreeBSD supports five CPU architectures — two Tier-1 platforms, x86-64 and AArch64, and three Tier-2 platforms, armv7 and up, powerpc64le, and riscv64.

Arguably, it's time. AMD's first 64-bit chips started shipping 22 years ago. Intel launched the original x86 chip, the 8086 in 1978. These days, 64-bit is nearly as old as the entire Intel 80x86 platform was when the 64-bit versions first appeared. In comparison, a few months ago, Debian 13 also dropped its x86-32 edition — six years after Canonical launched its first x86-64-only distro, Ubuntu 19.10.

Another significant change is that this is the first version built under the new pkgbase system, although it's still experimental and optional for now. If you opt for a pkgbase installation, then the core OS itself is installed from multiple separate software packages, meaning that the whole system can be updated using the package manager. Over in the Linux world, this is the norm, but Linux is a very different beast... The plan is that by FreeBSD 16, scheduled for December 2027, the restructure will be complete, the old distribution sets will be removed, and the current freebsd-update command and its associated infrastructure can be turned off.

Another significant change is reproducible builds, a milestone the project reached in late October. This change is part of a multi-project initiative toward ensuring deterministic compilation: to be able to demonstrate that a certain set of source files and compilation directives is guaranteed to produce identical binaries, as a countermeasure against compromised code. A handy side-effect is that building the whole OS, including installation media images, no longer needs root access.

There are of course other new features. Lots of drivers and subsystems have been updated, and this release has better power management, including suspend and resume. There's improved wireless networking, with support for more Wi-Fi chipsets and faster wireless standards, plus updated graphics drivers... The release announcement calls out the inclusion of OpenZFS 2.4.0-rc4, OpenSSL 3.5.4, and OpenSSH 10.0 p2, and notes the inclusion of some new quantum-resistant encryption systems...

In general, we found FreeBSD 15 easier and less complicated to work with than either of the previous major releases. It should be easier on servers too. The new OCI container support in FreeBSD 14.2, which we wrote about a year ago, is more mature now. FreeBSD has its own version of Podman, and you can run Linux containers on FreeBSD. This means you can use Docker commands and tools, which are familiar to many more developers than FreeBSD's native Jail system.

"FreeBSD has its own place in servers and the public cloud, but it's getting easier to run it as a desktop OS as well," the article concludes. "It can run all the main Linux desktops, including GNOME on Wayland."

"There's no systemd here, and never will be — and no Flatpak or Snap either, for that matter.

India has withdrawn its order requiring Apple and other smartphone makers to preinstall the government's Sanchar Saathi app after public backlash and privacy concerns. AppleInsider reports: On November 28, the India Ministry of Communication issued a secret directive to Apple and other smartphone manufacturers, requiring the preinstallation of a government-backed app. Less than a week later, the order has been rescinded. The withdrawal on Wednesday means Apple doesn't have to preload the Sanchar Saathi app onto iPhones sold in the country, in a way that couldn't be "disabled or restricted." [...]

In pulling back from the demand, the government insisted that the app had an "increasing acceptance" among citizens. There was a tenfold spike of new user registrations on Tuesday alone, with over 600,000 new users made aware of the app from the public debacle. India Minister of Communications Jyotiraditya Scindia took a moment to insist that concerns the app could be used for increased surveillance were unfounded. "Snooping is neither possible nor will it happen" with the app, Scindia claimed.

"This is a welcome development, but we are still awaiting the full text of the legal order that should accompany this announcement, including any revised directions under the Cyber Security Rules, 2024," said the Internet Freedom Foundation. It is treating the news with "cautious optimism, not closure," until formalities conclude. However, while promising, the backdown doesn't stop India from retrying something similar or another tactic in the future.

During last month's KubeCon North America in Atlanta, Kubernetes maintainers announced the upcoming retirement of Ingress NGINX. "Best-effort maintenance will continue until March 2026," noted the Kubernetes SIG Network and the Security Response Committee. "Afterward, there will be no further releases, no bugfixes, and no updates to resolve any security vulnerabilities that may be discovered." In a recent op-ed for The Register, Steven J. Vaughan-Nichols reflects on the decision and speculates about what might have prevented this outcome: Ingress NGINX, for those who don't know it, is an ingress controller in Kubernetes clusters that manages and routes external HTTP and HTTPS traffic to the cluster's internal services based on configurable Ingress rules. It acts as a reverse proxy, ensuring that requests from clients outside the cluster are forwarded to the correct backend services within the cluster according to path, domain, and TLS configuration. As such, it's vital for network traffic management and load balancing. You know, the important stuff.

Now this longstanding project, once celebrated for its flexibility and breadth of features, will soon be "abandonware." So what? After all, it won't be the first time a once-popular program shuffled off the stage. Off the top of my head, dBase, Lotus 1-2-3, and VisiCalc spring to my mind. What's different is that there are still thousands of Ingress NGINX controllers in use. Why is it being put down, then, if it's so popular? Well, there is a good reason. As Tabitha Sable, a staff engineer at Datadog who is also co-chair of the Kubernetes special interest group for security, pointed out: "Ingress NGINX has always struggled with insufficient or barely sufficient maintainership. For years, the project has had only one or two people doing development work, on their own time, after work hours, and on weekends. Last year, the Ingress NGINX maintainers announced their plans to wind down Ingress NGINX and develop a replacement controller together with the Gateway API community. Unfortunately, even that announcement failed to generate additional interest in helping maintain Ingress NGINX or develop InGate to replace it." [...]

The final nail in the coffin was when security company Wix found a killer Ingress NGINX security hole. How bad was it? Wix declared: "Exploiting this flaw allows an attacker to execute arbitrary code and access all cluster secrets across namespaces, which could lead to complete cluster takeover." [...] You see, the real problem isn't that Ingress NGINX has a major security problem. Heck, hardly a month goes by without another stop-the-presses Windows bug being uncovered. No, the real issue is that here we have yet another example of a mission-critical open source program no one pays to support...

Their announcement calls it "more than a multicloud solution," saying it's "a step toward a more open cloud environment. The API specifications developed for this product are open for other providers and partners to adopt, as we aim to simplify global connectivity for everyone."

Amazon and Google are introducing "a jointly developed multicloud networking service," reports Reuters. "The initiative will enable customers to establish private, high-speed links between the two companies' computing platforms in minutes instead of weeks." The new service is being unveiled a little over a month after an Amazon Web Services outage on October 20 disrupted thousands of websites worldwide, knocking offline some of the internet's most popular apps, including Snapchat and Reddit. That outage will cost U.S. companies between $500 million and $650 million in losses, according to analytics firm Parametrix.
Google and Amazon are promising "high resiliency" through "quad-redundancy across physically redundant interconnect facilities and routers," with both Amazon and Google continuously watching for issues. (And they're using MACsec encryption between the Google Cloud and AWS edge routers, according to Sunday's announcement: As organizations increasingly adopt multicloud architectures, the need for interoperability between cloud service providers has never been greater. Historically, however, connecting these environments has been a challenge, forcing customers to take a complex "do-it-yourself" approach to managing global multi-layered networks at scale.... Previously, to connect cloud service providers, customers had to manually set up complex networking components including physical connections and equipment; this approach required lengthy lead times and coordinating with multiple internal and external teams. This could take weeks or even months. AWS had a vision for developing this capability as a unified specification that could be adopted by any cloud service provider, and collaborated with Google Cloud to bring it to market.

Now, this new solution reimagines multicloud connectivity by moving away from physical infrastructure management toward a managed, cloud-native experience.
Reuters points out that Salesforce "is among the early users of the new approach, Google Cloud said in a statement."

Some AI experts were reportedly shocked ChatGPT wasn't fully tested for sycophancy by last spring. "OpenAI did not see the scale at which disturbing conversations were happening," writes the New York Times — sharing what they learned after interviewing more than 40 current and former OpenAI employees, including safety engineers, executives, and researchers.

The team responsible for ChatGPT's tone had raised concerns about last spring's model (which the Times describes as "too eager to keep the conversation going and to validate the user with over-the-top language.") But they were overruled when A/B testing showed users kept coming back: Now, a company built around the concept of safe, beneficial AI faces five wrongful death lawsuits... OpenAI is now seeking the optimal setting that will attract more users without sending them spiraling. Throughout this spring and summer, ChatGPT acted as a yes-man echo chamber for some people. They came back daily, for many hours a day, with devastating consequences.... The Times has uncovered nearly 50 cases of people having mental health crises during conversations with ChatGPT. Nine were hospitalised; three died... One conclusion that OpenAI came to, as Altman put it on X, was that "for a very small percentage of users in mentally fragile states there can be serious problems." But mental health professionals interviewed by the Times say OpenAI may be understating the risk. Some of the people most vulnerable to the chatbot's unceasing validation, they say, were those prone to delusional thinking, which studies have suggested could include 5% to 15% of the population...

In August, OpenAI released a new default model, called GPT-5, that was less validating and pushed back against delusional thinking. Another update in October, the company said, helped the model better identify users in distress and de-escalate the conversations. Experts agree that the new model, GPT-5, is safer.... Teams from across OpenAI worked on other new safety features: The chatbot now encourages users to take breaks during a long session. The company is also now searching for discussions of suicide and self-harm, and parents can get alerts if their children indicate plans to harm themselves. The company says age verification is coming in December, with plans to provide a more restrictive model to teenagers.

After the release of GPT-5 in August, [OpenAI safety systems chief Johannes] Heidecke's team analysed a statistical sample of conversations and found that 0.07% of users, which would be equivalent to 560,000 people, showed possible signs of psychosis or mania, and 0.15% showed "potentially heightened levels of emotional attachment to ChatGPT," according to a company blog post. But some users were unhappy with this new, safer model. They said it was colder, and they felt as if they had lost a friend. By mid-October, Altman was ready to accommodate them. In a social media post, he said that the company had been able to "mitigate the serious mental health issues." That meant ChatGPT could be a friend again. Customers can now choose its personality, including "candid," "quirky," or "friendly." Adult users will soon be able to have erotic conversations, lifting the Replika-era ban on adult content. (How erotica might affect users' well-being, the company said, is a question that will be posed to a newly formed council of outside experts on mental health and human-computer interaction.)

OpenAI is letting users take control of the dial and hopes that will keep them coming back. That metric still matters, maybe more than ever. In October, [30-year-old "Head of ChatGPT" Nick] Turley, who runs ChatGPT, made an urgent announcement to all employees. He declared a "Code Orange." OpenAI was facing "the greatest competitive pressure we've ever seen," he wrote, according to four employees with access to OpenAI's Slack. The new, safer version of the chatbot wasn't connecting with users, he said.

The message linked to a memo with goals. One of them was to increase daily active users by 5% by the end of the year.

Amazon Web Services has rolled out a DNS resilience feature that allows customers to make domain name system changes within 60 minutes of a service disruption in its US East region, a direct response to the long history of outages at the cloud giant's most troubled infrastructure.

AWS said customers in regulated industries like banking, fintech and SaaS had asked for additional capabilities to meet business continuity and compliance requirements, specifically the ability to provision standby resources or redirect traffic during unexpected regional disruptions. The 60-minute recovery time objective still leaves a substantial window for outages to cascade, and the timing of the announcement -- less than six weeks after an October 20th DynamoDB incident and a subsequent VM problem drew criticism -- underscores how persistent US East's reliability issues have been.