Two scientific journals that experimented with paying peer reviewers found the practice sped up the review process without compromising quality, according to findings published this month.

Critical Care Medicine offered $250 to half of 715 invited reviewers, with 53% accepting compared to 48% of unpaid reviewers. Paid reviews were completed one day faster on average. In a more dramatic result, Biology Open saw reviews completed in 4.6 business days when paying reviewers $284 per review, versus 38 days for unpaid reviews. "For the editors it has been extremely helpful because, prior to this, in some areas it was very difficult to secure reviewers," said Alejandra Clark, managing editor of Biology Open.

The Certification Authority/Browser Forum "is a cross-industry group that works together to develop minimum requirements for TLS certificates," writes Google's Security blog. And earlier this month two proposals from Google's forward-looking roadmap "became required practices in the CA/Browser Forum Baseline Requirements," improving the security and agility of TLS connections... Multi-Perspective Issuance Corroboration
Before issuing a certificate to a website, a Certification Authority (CA) must verify the requestor legitimately controls the domain whose name will be represented in the certificate. This process is referred to as "domain control validation" and there are several well-defined methods that can be used. For example, a CA can specify a random value to be placed on a website, and then perform a check to verify the value's presence has been published by the certificate requestor.

Despite the existing domain control validation requirements defined by the CA/Browser Forum, peer-reviewed research authored by the Center for Information Technology Policy of Princeton University and others highlighted the risk of Border Gateway Protocol (BGP) attacks and prefix-hijacking resulting in fraudulently issued certificates. This risk was not merely theoretical, as it was demonstrated that attackers successfully exploited this vulnerability on numerous occasions, with just one of these attacks resulting in approximately $2 million dollars of direct losses.

The Chrome Root Program led a work team of ecosystem participants, which culminated in a CA/Browser Forum Ballot to require adoption of MPIC via Ballot SC-067. The ballot received unanimous support from organizations who participated in voting. Beginning March 15, 2025, CAs issuing publicly-trusted certificates must now rely on MPIC as part of their certificate issuance process. Some of these CAs are relying on the Open MPIC Project to ensure their implementations are robust and consistent with ecosystem expectations...

Linting
Linting refers to the automated process of analyzing X.509 certificates to detect and prevent errors, inconsistencies, and non-compliance with requirements and industry standards. Linting ensures certificates are well-formatted and include the necessary data for their intended use, such as website authentication. Linting can expose the use of weak or obsolete cryptographic algorithms and other known insecure practices, improving overall security... The ballot received unanimous support from organizations who participated in voting. Beginning March 15, 2025, CAs issuing publicly-trusted certificates must now rely on linting as part of their certificate issuance process.
Linting also improves interoperability, according to the blog post, and helps reduce the risk of non-compliance with standards that can result in certificates being "mis-issued".

And coming up, weak domain control validation methods (currently permitted by the CA/Browser Forum TLS Baseline Requirements) will be prohibited beginning July 15, 2025.

"Looking forward, we're excited to explore a reimagined Web PKI and Chrome Root Program with even stronger security assurances for the web as we navigate the transition to post-quantum cryptography."

"The big set of open-source graphics driver updates for Linux 6.15 have been merged," writes Phoronix, "but Linux creator Linus Torvalds isn't particularly happy with the pull request." The new "hdrtest" code is for the Intel Xe kernel driver and is around trying to help ensure the Direct Rendering Manager header files are self-contained and pass kernel-doc tests — basic maintenance checks on the included DRM header files to ensure they are all in good shape.
But Torvalds accused the code of not only slowing down the full-kernel builds, but also leaving behind "random" files for dependencies "that then make the source tree nasty," reports Tom's Hardware: While Torvalds was disturbed by the code that was impacting the latest Linux kernel, beginning his post with a "Grr," he remained precise in his objections to it. "I did the pull, resolved the (trivial) conflicts, but I notice that this ended up containing the disgusting 'hdrtest' crap that (a) slows down the build because it's done for a regular allmodconfig build rather than be some simple thing that you guys can run as needed (b) also leaves random 'hdrtest' turds around in the include directories," he wrote.

Torvalds went on to state that he had previously complained about this issue, and inquired why the hdr testing is being done as a regular part of the build. Moreover, he highlighted that the resulting 'turds' were breaking filename completion. Torvalds underlined this point — and his disgust — by stating, "this thing needs to *die*." In a shot of advice to fellow Linux developers, Torvalds said, "If you want to do that hdrtest thing, do it as part of your *own* checks. Don't make everybody else see that disgusting thing...."

He then noted that he had decided to mark hdrtest as broken for now, to prevent its inclusion in regular builds.
As of Saturday, all of the DRM-Next code had made it into Linux 6.15 Git, notes Phoronix. "But Linus Torvalds is expecting all this 'hdrtest' mess to be cleaned up."

As Rust approaches its 10th anniversary, "there is an important piece of documentation missing that many other languages provide," notes the Rust Foundation.

While there's documentation and tutorials — there's no official language specification: In December 2022, an RFC was submitted to encourage the Rust Project to begin working on a specification. After much discussion, the RFC was approved in July 2023, and work began.

Initially, the Rust Project specification team (t-spec) were interested in creating the document from scratch using the Rust Reference as a guiding marker. However, the team knew there was already an external Rust specification that was being used successfully for compiler qualification purposes — the FLS.
Thank Berlin-based Ferrous Systems, a Rust-based consultancy who assembled that description "some years ago," according to a post on the Rust blog: They've since been faithfully maintaining and updating this document for new versions of Rust, and they've successfully used it to qualify toolchains based on Rust for use in safety-critical industries. [The Rust Foundation notes it part of the consultancy's "Ferrocene" Rust compiler/toolchain.] Seeing this success, others have also begun to rely on the FLS for their own qualification efforts when building with Rust.
The Rust Foundation explains: The FLS provides a structured and detailed reference for Rust's syntax, semantics, and behavior, serving as a foundation for verification, compliance, and standardization efforts. Since Rust did not have an official language specification back then, nor a plan to write one, the FLS represented a major step toward describing Rust in a way that aligns with industry requirements, particularly in high-assurance domains.
And the Rust Project is "passionate about shipping high quality tools that enable people to build reliable software at scale," adds the Rust blog. So... It's in that light that we're pleased to announce that we'll be adopting the FLS into the Rust Project as part of our ongoing specification efforts. This adoption is being made possible by the gracious donation of the FLS by Ferrous Systems. We're grateful to them for the work they've done in assembling the FLS, in making it fit for qualification purposes, in promoting its use and the use of Rust generally in safety-critical industries, and now, for working with us to take the next step and to bring the FLS into the Project.

With this adoption, we look forward to better integrating the FLS with the processes of the Project and to providing ongoing and increased assurances to all those who use Rust in safety-critical industries and, in particular, to those who use the FLS as part of their qualification efforts.
More from the Rust Foundation: The t-spec team wanted to avoid potential confusion from having two highly visible Rust specifications in the industry and so decided it would be worthwhile to try to integrate the FLS with the Rust Reference to create the official Rust Project specification. They approached Ferrous Systems, which agreed to contribute its FLS to the Rust Project and allow the Rust Project to take over its development and management... This generous donation will provide a clearer path to delivering an official Rust specification. It will also empower the Rust Project to oversee its ongoing evolution, providing confidence to companies and individuals already relying on the FLS, and marking a major milestone for the Rust ecosystem.

"I really appreciate Ferrous taking this step to provide their specification to the Rust Project," said Joel Marcey, Director of Technology at the Rust Foundation and member of the t-spec team. "They have already done a massive amount of legwork...." This effort will provide others who require a Rust specification with an official, authoritative reference for their work with the Rust programming language... This is an exciting outcome. A heartfelt thank you to the Ferrous Systems team for their invaluable contribution!
Marcey said the move allows the team "to supercharge our progress in the delivery of an official Rust specification."

And the co-founder of Ferrous Systems, Felix Gilcher, also sounded excited. "We originally created the Ferrocene Language Specification to provide a structured and reliable description of Rust for the certification of the Ferrocene compiler. As an open source-first company, contributing the FLS to the Rust Project is a logical step toward fostering the development of a unified, community-driven specification that benefits all Rust users."

Cloud providers like the security of running things in virtual machines "at scale" — even though VMs "are not known for having fast cold starts or a small footprint..." noted Microsoft's Open Source blog last November. So Microsoft's Azure Core Upstream team built an open source Rust library called Hyperlight "to execute functions as fast as possible while isolating those functions within a VM."

But that was just the beginning... Then, we showed how to run Rust functions really, really fast, followed by using C to [securely] run Javascript. In February 2025, the Cloud Native Computing Foundation (CNCF) voted to onboard Hyperlight into their Sandbox program [for early-stage projects].

[This week] we're announcing the release of Hyperlight Wasm: a Hyperlight virtual machine "micro-guest" that can run wasm component workloads written in many programming languages...

Traditional virtual machines do a lot of work to be able to run programs. Not only do they have to load an entire operating system, they also boot up the virtual devices that the operating system depends on. Hyperlight is fast because it doesn't do that work; all it exposes to its VM guests is a linear slice of memory and a CPU. No virtual devices. No operating system. But this speed comes at the cost of compatibility. Chances are that your current production application expects a Linux operating system running on the x86-64 architecture (hardware), not a bare linear slice of memory...

[B]uilding Hyperlight with a WebAssembly runtime — wasmtime — enables any programming language to execute in a protected Hyperlight micro-VM without any prior knowledge of Hyperlight at all. As far as program authors are concerned, they're just compiling for the wasm32-wasip2 target... Executing workloads in the Hyperlight Wasm guest isn't just possible for compiled languages like C, Go, and Rust, but also for interpreted languages like Python, JavaScript, and C#. The trick here, much like with containers, is to also include a language runtime as part of the image... Programming languages, runtimes, application platforms, and cloud providers are all starting to offer rich experiences for WebAssembly out of the box. If we do things right, you will never need to think about whether your application is running inside of a Hyperlight Micro-VM in Azure. You may never know your workload is executing in a Hyperlight Micro VM. And that's a good thing.
While a traditional virtual-device-based VM takes about 125 milliseconds to load, "When the Hyperlight VMM creates a new VM, all it needs do to is create a new slice of memory and load the VM guest, which in turn loads the wasm workload. This takes about 1-2 milliseconds today, and work is happening to bring that number to be less than 1 millisecond in the future."

And there's also double security due to Wasmtime's software-defined runtime sandbox within Hyperlight's larger VM...

Samsung teased its "AI Vision Inside" refrigerators at January's CES tradeshow. (Its internal sensors can now detect 37 different fresh ingredients and 50 processed foods, generating lists for your cellphone or a screen on your refrigerator's door.)

But the refrigerators are part of a larger "AI Home" lineup of screen-enabled appliances with advanced AI features, and Engadget got to see them all together this weekend at Samsung's Bespoke AI conference in Seoul, Korea: The centerpiece of the Bespoke line remains Samsung's 4-door French-Door refrigerator, which is now available with two different-sized screens. There's a model with a smaller 9-inch screen that starts at $3,999 or one with a massive 32-inch panel called the Family Hub+ for $4,699. The former is ostensibly designed for people who want something a bit more discreet but still want access to Samsung's smart features, which includes widgets for your calendar, music, weather, various cooking apps and more. Meanwhile, the larger model is for families who aren't afraid of having a small TV in their face every time they open their fridge. You can even play videos from TikTok on it, if that's what you're into....

For cooking, Samsung's matte glass induction cooktops are mostly the same, but its Bespoke 30-inch single ($3,759) and double ($4,649) wall ovens have...you guessed it, more AI. In addition to a 7-inch display, there are also cameras and sensors inside the oven that can recognize up to 80 different recipes to provide optimal cooking times. But if you prefer to go off-script and create something original, Samsung says the oven will give you the option to save the recipe and temperature settings after cooking the same dish five times. And for a more fun application of its tech, the oven's cameras can record videos and create time-lapses of your baked goods for sharing on social media.

When it's time to clean up, Samsung's $1,399 Bespoke Auto Open Door Dishwasher has a few tricks of its own. In this case, the washer uses AI (yet again) and sensors to more accurately detect food residue and optimize cleaning cycles...
There's also an "AI Jet Ultra Cordless Stick" vacuum cleaner, which "uses AI to better detect what surface its on to more effectively hoover up dirt and debris."

Interestingly, in January Samsung's refrigerators also got a mention in iFixit's "Worst of CES" video.

"I've been dreaming of this moment for 20 years," says Aptera co-CEO Steve Fambro. Aptera's solar-powered electric car just drove 300 miles on a single charge.

"We're one step closer to a future where every journey is powered by the sun," Aptera says in their announcement.

"This go around, Aptera took to the highway for the first time ever..." writes the EV blog Electrek. "At one point, Aptera's video noted that its solar EV was pulling over 545 watts of solar input, even though it was overcast."

"Less time searching for chargers," Aptera says in their announcement, adding that their "production-intent" car proved "that a solar EV isn't just a concept for the future, but a real-world solution ready for the present" — while turning Route 66 into "a test bed for a vehicle built to thrive independently..." "The panoramic windshield gives you this incredible view of the landscape," Steve said [in a video accompanying the announcement], describing the drive. "It's like a big picture window into the future."

The final stretch took the team back into California, where they reflected on the journey, the data, and the excited reactions from drivers who caught a glimpse of the vehicle on the road. "Almost everyone we passed had their phones out filming us," Steve laughed. "It's clear that Aptera's design stops traffic — without needing to stop for a charge."
"I was struck by how normal this trip seemed, except for all the gawking from fellow travelers," writes long-time Slashdot reader AirHog. "Best of luck to Aptera to reach their funding and production goals this year for this remarkable vehicle."

They drove on highways to Lake Havasu, and then to California's Imperial Valley — starting in Flagstaff, Arizona on symbolic Route 66. It was 100 years ago that Route 66 was proposed to link Chicago and Los Angeles, which Fambro credits to a visionary who believed in "something bigger than the road itself — believing in what it could unlock for the world." "And they did it. Route 66 became one of the most iconic highways in America, proving that what once seemed improbable could become inevitable.

"I think about that alot with Aptera. We're building something people say can't be done. History shows us the boldest ideas, the ones that challenge that status quo are the ones that truly change the world.
They take their futuristic, tear-dropped shaped "Jetsons" car to a drive-through wildlife refuge named Bearizona. They stop at a general store for some beef jerky. "We're just having a fun time seeing all the sights."

"I've been dreaming of this moment for 20 years," says Aptera co-CEO Steve Fambro. "Driving in the most efficient vehicle on the road. Watching the sights go by. I got emotional just taking it all in." "This company. This idea. It's real. It's visceral. And I'm just so proud of each and every person who helped make this dream a reality.

"We have the chance to make a real change in how the world moves. The road hasn't been easy. It's been painful, difficult. And it's brought me to my breaking point sometimes. But being in this moment right now? I can say it's all been worth it...

"I feel we're at the forefront of something truly revolutionary. We're not fighting an uphill battle any more. We're standing at the edge of something incredible. Ready to break through.

"To all of you who supported us, my commitment is this. We're not stopping. We're moving forward with more energy and more passion than ever. The road ahead is an open highway. And the future is ours to shape."
To celebrate Aptera is holding a giveaway for a camping kit, a $100 gift card to their online store, and a free Aptera pre-order to a winner chosen at random from those who subscribe/watch/comment on their new video...

In 1999 Slashdot reader Jeremie announced "a new project I recently started to create a complete open-source platform for Instant Messaging with transparent communication to other IM systems (ICQ, AIM, etc)." It was the first release of the eXtensible Messaging and Presence Protocol, and by 2008 Slashdot was asking if XMPP was "the next big thing." Facebook even supported it for third-party chat clients until 2015.

And here in 2025, the chair of the nonprofit XMPP Standards Foundation is long-time Slashdot reader ralphm, who is now issuing this call to action at XMPP.org: The European Digital Markets Act (DMA) is designed to break down walled gardens and enforce messaging interoperability. As a designated gatekeeper, Meta—controlling WhatsApp and Messenger—must comply. However, its current proposal falls short, risking further entrenchment of its dominance rather than fostering genuine competition. [..]

A Call to Action

The XMPP Standards Foundation urges Meta to adopt XMPP for messaging interoperability. It is ready to collaborate, continue to evolve the protocol to meet modern needs, and ensure true compliance with the DMA. Let's build an open, competitive messaging ecosystem—one that benefits both users and service providers.

It's time for real interoperability. Let's make it happen.

The Washington Post reports that after months of polar darkness, the extent of sea ice blanketing the Arctic this winter "fell to the lowest level on record, researchers announced this week... the smallest maximum extent in the 47-year satellite record, according to the National Snow and Ice Data Center.

"Since then, the ice has already begun to melt again." "Sea ice is acting like the old canary in the coal mine," Dartmouth University geophysicist Don Perovich said. "It's saying loud and clear that warming is occurring...."

In the summer, when the sun's radiation shines down on the Arctic for 24 hours a day, the ice acts as a shield, reflecting more than half of the light that hits it back into space.... With so little sea ice in the Arctic this year, more sunlight will be able to reach the open ocean, which absorbs more than 90 percent of the radiation that hits it. This will further warm the region, accelerating ice melt and exposing even more water to the light. This feedback loop helps explain the rapid warming of the Arctic, and it is expected to lead to a complete lack of summer sea ice in the region within decades, [said explained Melinda Webster, a sea ice scientist at the University of Washington]. The consequences would be dire for seals, polar bears and other wildlife, which depend on a stable sea ice platform to birth their young and hunt for food. It would also expose miles of coastline to pounding ocean waves, accelerating the erosion that threatens to tip some communities into the sea.

But the effects will also be felt in places far from the poles, Perovich said. Studies suggest that a complete loss of Arctic sea ice would raise global temperatures as much as adding a trillion tons of carbon dioxide to the atmosphere. Changes in the Arctic could also affect the jet stream, the river of winds that flows through the upper atmosphere, contributing to more extreme weather around the globe.

"What happens in the Arctic doesn't stay in the Arctic," Perovich said.
Earlier this year sea ice also fell 30% below the amount typical in the Antarctic prior to 2010, the researchers report. The total amount of sea ice on earth has now reached an all-time low, declining by more than a million square miles (2.5 million square kilometers) below the pre-2010 average.

"Altogether, Earth is missing an area of sea ice large enough to cover the entire continental United States east of the Mississippi."

The Register: Following our report last week on IBM's ongoing layoffs, current and former employees got in touch to confirm what many suspected: The US cuts run deeper than reported, and the jobs are heading to India. IBM's own careers site numbers back that up. On January 7, 2024, Big Blue listed just 173 open positions in India. On November 23, 2024, there were 2,946 jobs available in the nation. At the time of writing, the IT titan listed 3,866 roles in India.

American jobs listed for these three periods are 192, 376, and 333, respectively, though at least among those being laid off, there's doubt those roles will be filled with job seekers in the States. A current IBMer who won't be there much longer said that after being told to teach recently hired workers in India "everything I know," the reward was a resource action, or RA -- Big Blue's euphemism for a layoff. After receiving an RA notification, employees typically have a set period of time to apply for open roles elsewhere in the mega-corporation. But just because there are open positions listed in the US doesn't mean IBM is making much of an effort to fill them, we are told.

Microsoft CEO Satya Nadella has told employees that DeepSeek's R1 AI model has set "the new bar" for his company's AI ambitions, citing the startup's ability to reach the top of app store rankings. "What's most impressive about DeepSeek is that it's a great reminder of what 200 people can do when they come together with one thought and one play," The Verge cited Nadella as saying.

"Most importantly, not just leaving it there as a research project or an open source project, but to turn it into a product that was number one in the App Store. That's the new bar to me," he added. Microsoft quickly deployed DeepSeek's R1 on its Azure platform in January. The AI model gained recognition for its optimization below Nvidia's CUDA layer, enabling greater efficiency.

China's ambitious AI infrastructure push has resulted in hundreds of idle data centers with local media reporting up to 80% of newly built computing resources remaining unused. The country announced over 500 data center projects during 2023-2024, with at least 150 completed facilities now struggling to secure customers in a rapidly changing market.

The rise of DeepSeek's open-source reasoning model R1, which matches ChatGPT o1's performance at a fraction of the cost, has fundamentally altered hardware demand. Computing needs now prioritize low-latency infrastructure for real-time reasoning rather than facilities optimized for large-scale training workloads.

Technical misalignment compounds the problem, as many centers were constructed by companies with little AI expertise, MIT Technology Review reports. The facilities, often built in remote regions to capitalize on cheaper electricity and land, now face obsolescence as AI companies require proximity to tech hubs to minimize transmission delays. GPU rental prices have collapsed, with eight-GPU Nvidia H100 server clusters now leasing for 75,000 yuan ($10,333) monthly, down from peaks of 180,000 yuan, making operations financially unsustainable for many data center operators.

An anonymous reader quotes a report from Tom's Hardware: Qualcomm has reportedly filed secret complaints against Arm with the European Commission, the U.S. Federal Trade Commission (FTC), and the Korea Fair Trade Commission. Qualcomm argues that Arm's open licensing approach helped build a robust hardware and software ecosystem. However, this ecosystem is under threat now as Arm moves to restrict that access to benefit its chip design business, namely compute subsystems (CSS) reference designs for client and datacenter processors and custom silicon based on CSS for large-scale clients.

Qualcomm has presented its case to the EC, U.S. FTC, and Korea FTC behind closed doors and through formal filings, so it does not comment on the matter now. Arm rejected the accusations, stating that it is committed to innovation, competition, and upholding contract terms. The company called Qualcomm's move an attempt to shift attention from a wider commercial dispute between the two companies and use regulatory pressure for its benefit.

Indeed, the antitrust complaints align with Qualcomm's arguments in a recent legal clash with Arm in Delaware. Qualcomm won that trial, as the court ruled that the company did not break the terms of its architecture license agreement (ALA) and technology license agreement (TLA) by acquiring Nuvia and using its IP in its Snapdragon X processors for client PCs. Arm said it would seek a retrial. However, Qualcomm seems to want to ensure that it will have access to Arm's instruction set architecture and technologies by filing complaints with antitrust regulators.

sciencehabit quotes a report from Science.org: Whales sing, orcas squeal, and sea turtles croak. But sharks are more the strong, silent type. Now, researchers report the first evidence that sharks make sounds, too, described today in Royal Society Open Science. The animals may be making the sounds -- a series of clicking noises -- by snapping their flat rows of teeth, which are blunt for crushing prey. The sharks can hear mostly low-frequency noise, and the clicks they emit are higher pitched, which suggests they are not for communicating with other rigs. It's possible they are a defensive tactic. Marine mammals that eat rigs, such as leopard seals, can hear in the frequency range of the rig clicks, but the researchers question whether a few clicks would deter an attack. The sounds might be part of their response to being startled, the team says.

An anonymous reader quotes a report from ZDNet, written by Steven Vaughan-Nichols: Despite the minor delay, Linux 6.14 arrives packed with cutting-edge features and improvements to power upcoming Linux distributions, such as the forthcoming Ubuntu 25.04 and Fedora 42. The big news for desktop users is the improved NTSYNC driver, especially those who like to play Windows games or run Windows programs on Linux. This driver is designed to emulate Windows NT synchronization primitives. What that feature means for you and me is that it will significantly improve the performance of Windows programs running on Wine and Steam Play. [...] Gamers always want the best possible graphics performance, so they'll also be happy to see that Linux now supports recently launched AMD RDNA 4 graphics cards. This approach includes support for the AMD Radeon RX 9070 XT and RX 9070 graphics cards. Combine this support with the recently improved open-source RADV driver and AMD gamers should see the best speed yet on their gaming rigs.

Of course, the release is not just for gamers. Linux 6.14 also includes several AMD and Intel processor enhancements. These boosts focus on power management, thermal control, and compute performance optimizations. These updates are expected to improve overall system efficiency and performance. This release also comes with the AMDXDNA driver, which provides official support for AMD's neural processing units based on the XDNA architecture. This integration enables efficient execution of AI workloads, such as convolutional neural networks and large language models, directly on supported AMD hardware. While Rust has faced some difficulties in recent months in Linux, more Rust programming language abstractions have been integrated into the kernel, laying the groundwork for future drivers written in Rust. [...] Besides drivers, Miguel Ojeda, Rust for Linux's lead developer, said recently that the introduction of the macro for smart pointers with Rust 1.84: derive(CoercePointee) is an "important milestone on the way to building a kernel that only uses stable Rust functions." This approach will also make integrating C and Rust code easier. We're getting much closer to Rust being grafted into Linux's tree.

In addition, Linux 6.14 supports Qualcomm's latest Snapdragon 8 Elite mobile processor, enhancing performance and stability for devices powered by this chipset. That support means you can expect to see much faster Android-based smartphones later this year. This release includes a patch for the so-called GhostWrite vulnerability, which can be used to root some RISC-V processors. This fix will block such attacks. Additionally, Linux 6.14 includes improvements for the copy-on-write Btrfs file system/logical volume manager. These primarily read-balancing methods offer flexibility for different RAID hardware configurations and workloads. Additionally, support for uncached buffered I/O optimizes memory usage on systems with fast storage devices. Linux 6.14 is available for download here.

An anonymous reader quotes a report from Android Authority: No matter the manufacturer, every Android phone has one thing in common: its software base. Manufacturers can heavily customize the look and feel of the Android OS they ship on their Android devices, but under the hood, the core system functionality is derived from the same open-source foundation: the Android Open Source Project. After over 16 years, Google is making big changes to how it develops the open source version of Android in an effort to streamline its development. [...] Beginning next week, all Android development will occur within Google's internal branches, and the source code for changes will only be released when Google publishes a new branch containing those changes. As this is already the practice for most Android component changes, Google is simply consolidating its development efforts into a single branch.

This change will have minimal impact on regular users. While it streamlines Android OS development for Google, potentially affecting the speed of new version development and bug reduction, the overall effect will likely be imperceptible. Therefore, don't expect this change to accelerate OS updates for your phone. This change will also have minimal impact on most developers. App developers are unaffected, as it pertains only to platform development. Platform developers, including those who build custom ROMs, will largely also see little change, since they typically base their work on specific tags or release branches, not the main AOSP branch. Similarly, companies that release forked AOSP products rarely use the main AOSP branch due to its inherent instability.

External developers who enjoy reading or contributing to AOSP will likely be dismayed by this news, as it reduces their insight into Google's development efforts. Without a GMS license, contributing to Android OS development becomes more challenging, as the available code will consistently lag behind by weeks or months. This news will also make it more challenging for some developers to keep up with new Android platform changes, as they'll no longer be able to track changes in AOSP. For reporters, this change means less access to potentially revealing information, as AOSP patches often provide insights into Google's development plans. [...] Google will share more details about this change when it announces it later this week. If you're interested in learning more, be sure to keep an eye out for the announcement and new documentation on source.android.com. Android Authority's Mishaal Rahman says Google is "committed to publishing Android's source code, so this change doesn't mean that Android is becoming closed-source."

"What will change is the frequency of public source code releases for specific Android components," says Rahman. "Some components like the build system, update engine, Bluetooth stack, Virtualization framework, and SELinux configuration are currently AOSP-first, meaning they're developed fully in public. Most Android components like the core OS framework are primarily developed internally, although some features, such as the unlocked-only storage area API, are still developed within AOSP."

An anonymous reader quotes a report from Ars Technica: Software developer Xe Iaso reached a breaking point earlier this year when aggressive AI crawler traffic from Amazon overwhelmed their Git repository service, repeatedly causing instability and downtime. Despite configuring standard defensive measures -- adjusting robots.txt, blocking known crawler user-agents, and filtering suspicious traffic -- Iaso found that AI crawlers continued evading all attempts to stop them, spoofing user-agents and cycling through residential IP addresses as proxies. Desperate for a solution, Iaso eventually resorted to moving their server behind a VPN and creating "Anubis," a custom-built proof-of-work challenge system that forces web browsers to solve computational puzzles before accessing the site. "It's futile to block AI crawler bots because they lie, change their user agent, use residential IP addresses as proxies, and more," Iaso wrote in a blog post titled "a desperate cry for help." "I don't want to have to close off my Gitea server to the public, but I will if I have to."

Iaso's story highlights a broader crisis rapidly spreading across the open source community, as what appear to be aggressive AI crawlers increasingly overload community-maintained infrastructure, causing what amounts to persistent distributed denial-of-service (DDoS) attacks on vital public resources. According to a comprehensive recent report from LibreNews, some open source projects now see as much as 97 percent of their traffic originating from AI companies' bots, dramatically increasing bandwidth costs, service instability, and burdening already stretched-thin maintainers.

Kevin Fenzi, a member of the Fedora Pagure project's sysadmin team, reported on his blog that the project had to block all traffic from Brazil after repeated attempts to mitigate bot traffic failed. GNOME GitLab implemented Iaso's "Anubis" system, requiring browsers to solve computational puzzles before accessing content. GNOME sysadmin Bart Piotrowski shared on Mastodon that only about 3.2 percent of requests (2,690 out of 84,056) passed their challenge system, suggesting the vast majority of traffic was automated. KDE's GitLab infrastructure was temporarily knocked offline by crawler traffic originating from Alibaba IP ranges, according to LibreNews, citing a KDE Development chat. While Anubis has proven effective at filtering out bot traffic, it comes with drawbacks for legitimate users. When many people access the same link simultaneously -- such as when a GitLab link is shared in a chat room -- site visitors can face significant delays. Some mobile users have reported waiting up to two minutes for the proof-of-work challenge to complete, according to the news outlet.

An anonymous reader quotes a report from VentureBeat: Chinese AI startup DeepSeek has quietly released a new large language model that's already sending ripples through the artificial intelligence industry -- not just for its capabilities, but for how it's being deployed. The 641-gigabyte model, dubbed DeepSeek-V3-0324, appeared on AI repository Hugging Face today with virtually no announcement (just an empty README file), continuing the company's pattern of low-key but impactful releases. What makes this launch particularly notable is the model's MIT license -- making it freely available for commercial use -- and early reports that it can run directly on consumer-grade hardware, specifically Apple's Mac Studio with M3 Ultra chip.

"The new DeepSeek-V3-0324 in 4-bit runs at > 20 tokens/second on a 512GB M3 Ultra with mlx-lm!" wrote AI researcher Awni Hannun on social media. While the $9,499 Mac Studio might stretch the definition of "consumer hardware," the ability to run such a massive model locally is a major departure from the data center requirements typically associated with state-of-the-art AI. [...] Simon Willison, a developer tools creator, noted in a blog post that a 4-bit quantized version reduces the storage footprint to 352GB, making it feasible to run on high-end consumer hardware like the Mac Studio with M3 Ultra chip. This represents a potentially significant shift in AI deployment. While traditional AI infrastructure typically relies on multiple Nvidia GPUs consuming several kilowatts of power, the Mac Studio draws less than 200 watts during inference. This efficiency gap suggests the AI industry may need to rethink assumptions about infrastructure requirements for top-tier model performance. "The implications of an advanced open-source reasoning model cannot be overstated," reports VentureBeat. "Current reasoning models like OpenAI's o1 and DeepSeek's R1 represent the cutting edge of AI capabilities, demonstrating unprecedented problem-solving abilities in domains from mathematics to coding. Making this technology freely available would democratize access to AI systems currently limited to those with substantial budgets."

"If DeepSeek-R2 follows the trajectory set by R1, it could present a direct challenge to GPT-5, OpenAI's next flagship model rumored for release in coming months. The contrast between OpenAI's closed, heavily-funded approach and DeepSeek's open, resource-efficient strategy represents two competing visions for AI's future."

The president of Signal defended the messaging app's security on Wednesday after top Trump administration officials mistakenly included a journalist in an encrypted chatroom they used to discuss looming U.S. military action against Yemen's Houthis. For a report: Signal's Meredith Whittaker did not directly address the blunder, which Democratic lawmakers have said was a breach of U.S. national security. But she described the app as the "gold standard in private comms" in a post on X, which outlined Signal's security advantages over Meta's WhatsApp messaging app. "We're open source, nonprofit, and we develop and apply (end-to-end encryption) and privacy-preserving tech across our system to protect metadata and message contents," she said.

A software engineer successfully ran Meta's Llama 2 generative AI model on a 20-year-old PowerBook G4, demonstrating how well-optimized code can push the limits of legacy hardware. MacRumors' Joe Rossignol reports: While hardware requirements for large language models (LLMs) are typically high, this particular PowerBook G4 model from 2005 is equipped with a mere 1.5GHz PowerPC G4 processor and 1GB of RAM. Despite this 20-year-old hardware, my brother was able to achieve inference with Meta's LLM model Llama 2 on the laptop. The experiment involved porting the open-source llama2.c project, and then accelerating performance with a PowerPC vector extension called AltiVec. His full blog post offers more technical details about the project.