A proposal within the Fedora Linux community suggests improving the kernel's DRM Panic screen to a more user-friendly, BSOD-style experience. Phoronix reports: Open-source developer Jose Exposito proposed today a nicer experience for DRM Panic integration on Fedora. Rather than using DRM Panic with just the kernel log contents being encoded in the QR code displayed when a kernel panic occurs, the proposal is to have a customized Fedora web-page with the encoded QR contents to be shown on that web page. Besides having a more pleasant UI/UX, from this web page the intent would also be to make it easier to report this error to the Fedora BugZilla. Being able to easily pass the kernel log to the Fedora bug tracker could help in making upstream aware of the problem(s) and seeing if other users are also encountering similar panics.

Right now this idea was just raised earlier today as a "request for comments" on the Fedora mailing list. While a prototype at this point, Exposito already developed a basic web interface for demoing the solution.

Friday 72-year-old Richard Stallman made a two-hour-and-20-minutes appearance at the Georgia Institute of Technology, talking about everything from AI and connected cars to smartphones, age verfication laws, and his favorite Linux distro. But early on, Stallman also told the audience how "I despise DRM...I don't want any copy of anything with DRM. Whatever it is, I never want it so badly that I would bow down to DRM." (So he doesn't use Spotify or Netflix...)

This led to an interesting moment when someone asked him later if we have an ethical obligation to avoid piracy.. First Stallman swapped in his preferred phrase, "forbidden sharing"...

"I won't use the word piracy to refer to sharing. Sharing is good and it should be lawful. Those laws are wrong. Copyright as it is now is an injustice."

Stallman said "I don't hesitate to share copies of anything," but added that "I don't have copies of non-free software, because I'm disgusted by it." After a pause, he added this. "Just because there is a law to to give some people unjust power, that doesn't mean breaking that law becomes wrong....

"Dividing people by forbidding them to help each other is nasty."

And later Stallman was asked how he watches movies, if he's opposed to DRM-heavy sites like Netflix, and the DRM in Blu-ray discs? "The only way I can see a movie is if I get a file — you know, like an MP4 file or MKV file. And I would get that, I suppose, by copying from somebody else."

"Sharing is good. Stopping people from sharing is evil."

Richard Stallman spoke Friday at Atlanta's Georgia Institute of Technology, continuing his activism for free software while also addressing today's new technologies.

Speaking about AI, Stallman warned that "nowadays, people often use the term artificial intelligence for things that aren't intelligent at all..." He makes a point of calling large language models "generators" because "They generate text and they don't understand really what that text means." (And they also make mistakes "without batting a virtual eyelash. So you can't trust anything that they generate.") Stallman says "Every time you call them AI, you are endorsing the claim that they are intelligent and they're not. So let's let's refuse to do that."

"So I've come up with the term Pretend Intelligence. We could call it PI. And if we start saying this more often, we might help overcome this marketing hype campaign that wants people to trust those systems, and trust their lives and all their activities to the control of those systems and the big companies that develop and control them."

"By the way, as far as I can tell, none of them is free software."

When it comes to today's cars, Stallman says they contain "malicious functionalities... Cars should not be connected. They should not upload anything." (He adds that "I am hoping to find a skilled mechanic to work with me in a project to make disconnected cars.")

And later Stallman calls the smartphone "an Orwellian tracking and surveillance device," saying he refuses to own one. (An advantage of free software is that it allows the removal of malicious functionalities.)

Stallman spoke for about 53 minutes — but then answered questions for nearly 90 minutes longer. Here's some of the highlights...

Anna's Archive lost control of its primary .org domain after it was placed on registry-level serverHold -- "an action that's typically taken by the domain name registry," reports TorrentFreak. Despite mounting legal pressure and speculation tied to its Spotify backup, the site remains accessible via multiple alternative domains, underscoring the resilience of shadow libraries. From the report: A few hours ago, the site's original domain name suddenly became unreachable globally. The annas-archive.org domain status was changed to "serverHold," which is typically done by the domain registry. This status effectively means that the domain is suspended and under investigation. Similar action has previously been taken against other pirate sites.

It is rare to see a .org domain involved in domain name suspensions. The American non-profit Public Interest Registry (PIR), which oversees the .org domains, previously refused to suspend domain names voluntarily, including thepiratebay.org. The registry's cautionary stance suggests that the actions against annas-archive.org are backed by a court order.

PIR's marketing director, Kendal Rowe, informs TorrentFreak that "unfortunately, PIR is unable to comment on the situation at this time." It is possible that, in response to the 'DRM-circumventing' Spotify backup, rightsholders requested an injunction targeting the domain name. However, we have seen no evidence of that. In the WorldCat lawsuit, OCLC requested an injunction to force action from intermediaries, including domain registries, but as far as we know, that hasn't been granted yet.

Here it is — Betty Boop's first appearance, which became public domain on Thursday. It's a 60-second song halfway through a longer cartoon about a restaurant titled Dizzy Dishes. (The first scene makes it clear this is a restaurant of anthropomorphized animals — which explains why the as-yet-unnamed character has floppy dog ears...)

So Fleischer Studios has now warned that claiming Betty Boop is public domain "is actually not true." Very often, different versions of a character that have been developed later can independently enjoy copyright protection. Also, names and depictions of a character very frequently will remain separately protected by trademark and other laws, regardless of whether the copyright has expired.
But is that really true? Fleischer Studios went out of business in 1946, notes Los Angeles Times columnist Michael Hiltzik: By then it had sold the rights to its cartoons and the Betty Boop character. A new Fleischer Studios was formed in the 1970s by Fleischer descendants, including Max's grandson Mark Fleischer, and set about repurchasing the rights that had been sold. Whether it reacquired the rights to Betty Boop is up for discussion... According to a federal appeals court ruling in 2011, the answer is no. Having navigated its way through the three or four copyright transfers that followed the original rights sale, the appeals court concluded that the original Fleischer studios sold the rights to Betty Boop and the related cartoons to Paramount in 1941 but couldn't verify that the rights to the character had been sold in an unbroken chain placing them with the new studio. The "chain of title" was broken, the appellate judges found — but they didn't say who ended up with Betty Boop.
And last month Cory Doctorow pointed out that "while the Fleischer studio (where Betty Boop was created) renewed the copyright on Dizzy Dishes, there were many other shorts that entered the public domain years ago." That means that all the aspects of Betty Boop that were developed for Dizzy Dishes are about to enter the public domain. But also, all the aspects of Betty Boop from those non-renewed shorts are already in the public domain. But some of the remaining aspects of Betty Boop's character design — those developed in subsequent shorts that were also renewed — are also in the public domain, because they aren't copyrightable in the first place, because they're "generic," or "trivial," constitute "minuscule variations," or be so standard or indispensable as to be a "scène à faire...." But we're not done yet! Just because some later aspects of the Betty Boop character design are still in copyright, it doesn't follow that you aren't allowed to use them! U.S. Copyright law has a broad set "limitations and exceptions," including fair use.
So while Fleischer Studios insists Betty Boop "will continue to enjoy copyright and trademark protection for years to come," Doctorow has some thoughts on that trademark: Even the Supreme Court has (repeatedly) upheld the principle that trademark can't be used as a backdoor to extend copyright.

That's important, because the current Betty Boop license-holders have been sending out baseless legal threats claiming that their trademarks over Betty Boop mean that she's not going into the public domain. They're not the only ones, either! This is a routine, petty scam perpetrated by marketing companies that have scooped up the (usually confused and difficult-to-verify) title to cultural icons and then gone into business extracting rent from people and businesses who want to make new works with them.
"Trademarks only prevent you from using character names and depictions in a way that misleads consumers into thinking your work is produced or sponsored by the rightsholder," Duke University clarified in their January 1st explanation of Public Domain Day 2026 — "for example, by putting them on unlicensed merchandise. They do not prevent you from using them in a new creative work clearly unaffiliated with the rights owners..."

"Regardless of who owns the later versions of the character, the original Betty Boop character from 1930 is in the public domain." This is another reason why copyright expiration is so important: It brings clarity... Under US copyright law, anyone is free to use characters as they appeared in public domain works. If those characters recur in later works that are still under copyright, the rights only extend to the newly added material in those works, not the underlying material from the public domain works — that content remains freely available. Second, with newer versions of characters, copyright only extends to those new features that qualify for such protection...

Dozens of post-1930 Betty Boop cartoons, including Ker-Choo (1932) and Poor Cinderella (1934), did not have renewals. The newly added material in these animations is also in the public domain... To sum up the copyright story so far: in 2026, the underlying Betty Boop character goes into the public domain. She is joined there by the attributes, plot lines, and dialogue that were first introduced in those later cartoons without renewed copyrights, as well as the uncopyrightable attributes of her later instantiations...

Certainly, there would be a risk of consumer confusion if you use Betty Boop as a brand identifier on the kind of merchandise Fleischer sells — jewelry, back packs, water bottles, dolls. Trademark law does protect Fleischer against that risk. Contrast these uses with simply putting the Boop character in a new artistic work. This is exactly what copyright expiration is intended to allow. Were trademark law to prevent this, then trademark rights would be leveraged to obtain the effective equivalent of a perpetual copyright — precisely what the Supreme Court said we cannot do...

If courts have delineated the line between copyright and trademark, why is there so little clarity in this area? Sadly, companies sometimes claim to have more expansive rights than they actually do, capitalizing on fear, uncertainty, and doubt to collect royalties and licensing fees to which they are not legally entitled.

Michal Kicinski, who co-founded both CD Projekt and the DRM-free digital games store GOG back in 2008, has acquired 100% ownership of GOG from CD Projekt, bringing the platform full circle to one of its original creators.

GOG was already operating as part of CD Projekt through its Sp.z.o.o. subsidiary, but Kicinski now takes complete control of the company. The platform will continue operating independently and maintain its commitment to DRM-free gaming. "The mission stays the same: Make Games Live Forever," GOG said in its announcement.

CD Projekt's joint CEO Michal Nowakowski said the parent company's focus on its development roadmap and franchise expansion made this the right time for the move. GOG has signed a distribution agreement ensuring all upcoming CD Projekt Red titles will release on the platform. Kicinski, describing himself as a "mature gamer" who plays classics, said he's personally involved in developing several retro-spirited games slated for GOG in 2026.

A group of activists has scraped Spotify's entire library, accessing 256 million rows of track metadata and 86 million audio files totaling roughly 300TB of data. The metadata has been released via Anna's Archive, a search engine for "shadow libraries" that previously focused on books.

Spotify described the activists as "anti-copyright extremists who've previously pirated content from YouTube and other platforms" and confirmed it is actively investigating the incident. The activists claim this represents "the world's first 'preservation archive' for music which is fully open" and covers "around 99.6% of listens."

They appear to have used Spotify's public web API to scrape the metadata and circumvented DRM to access audio files. Spotify insists that this is not a security breach affecting user data. Though the more pressing concern for the music industry may be AI training rather than pirate streaming services -- similar YouTube datasets have reportedly been used by unlicensed generative AI music services.

"In the lead up to its Switch 2 console release, Nintendo updated its user agreement," writes the Free Software Foundation, warning that Nintendo now claims "broad authority to make consoles owned by its customers permanently unusable."

"Under Nintendo's most aggressive digital restrictions management (DRM) update to date, game console owners are now required to give Nintendo the unilateral right to revoke access to games, security updates, and the Internet, at its sole discretion." The new agreement states: "You acknowledge that if you fail to comply with [Nintendo's restrictions], Nintendo may render the Nintendo Account Services and/or the applicable Nintendo device permanently unusable in whole or in part...."

There are probably other reasons that Nintendo has and will justify bricking game consoles, but here are some that we have seen reported:

— "Tampering" with hardware or software in pretty much any way;
— Attempting to play a back-up game;
— Playing a "used" game; or
— Use of a third-party game or accessory...


Nintendo's promise to block a user from using their game console isn't just an empty threat: it has already been wielded against many users. For example, within a month of the Switch 2's release, one user unknowingly purchased an open-box return that had been bricked, and despite functional hardware, it was unusable for many games. In another case, a user installing updates for game cartridges purchased via a digital marketplace had their console disabled. Though it's unclear exactly why they were banned, it's possible that the cartridge's previous owner made a copy and an online DRM check determined that the current and previous owner's use were both "fraudulent." The user only had their console released through appealing to Nintendo directly and providing evidence of their purchase, a laborious process.

Nintendo's new console banning spree is just one instance of the threat that nonfree software and DRM pose to users. DRM is but one injustice posed by nonfree software, and the target of the FSF's Defective by Design campaign. Like with all software, users ought to be able to freely copy, study, and modify the programs running on their devices. Proprietary software developers actively oppose and antagonize their users. In the case of Nintendo, this means punishing legitimate users and burdening them with proving that their use is "acceptable." Console users shouldn't have to tread so carefully with a console that they own, and should they misstep, beg Nintendo to allow them to use their consoles again.

Amazon says it will allow authors to offer their DRM-free ebooks in the EPUB and PDF formats through its self-publishing platform, Kindle Direct Publishing. Starting on January 20, 2026, authors who set their titles as DRM-free will see their books made available in these more open formats. From a report: The decision to use Digital Rights Management (DRM), a copyright protection mechanism, is set by the authors when they publish their ebooks on Amazon's platform. The company notes these changes won't impact previously published titles. If authors want to change the status of older titles, they'll have to log into the Kindle Direct Publishing (KDP) author portal and change an option in the settings. (Instructions on how to make that change are on Amazon's KDP support site here.) This move may actually incentivize authors to apply DRM to their ebooks.

Android's security team published a blog post this week about their experience using Rust. Its title? "Move fast and fix things." Last year, we wrote about why a memory safety strategy that focuses on vulnerability prevention in new code quickly yields durable and compounding gains. This year we look at how this approach isn't just fixing things, but helping us move faster.

The 2025 data continues to validate the approach, with memory safety vulnerabilities falling below 20% of total vulnerabilities for the first time. We adopted Rust for its security and are seeing a 1000x reduction in memory safety vulnerability density compared to Android's C and C++ code. But the biggest surprise was Rust's impact on software delivery. With Rust changes having a 4x lower rollback rate and spending 25% less time in code review, the safer path is now also the faster one... Data shows that Rust code requires fewer revisions. This trend has been consistent since 2023. Rust changes of a similar size need about 20% fewer revisions than their C++ counterparts... In a self-reported survey from 2022, Google software engineers reported that Rust is both easier to review and more likely to be correct. The hard data on rollback rates and review times validates those impressions.

Historically, security improvements often came at a cost. More security meant more process, slower performance, or delayed features, forcing trade-offs between security and other product goals. The shift to Rust is different: we are significantly improving security and key development efficiency and product stability metrics.

With Rust support now mature for building Android system services and libraries, we are focused on bringing its security and productivity advantages elsewhere. Android's 6.12 Linux kernel is our first kernel with Rust support enabled and our first production Rust driver. More exciting projects are underway, such as our ongoing collaboration with Arm and Collabora on a Rust-based kernel-mode GPU driver. [They've also been deploying Rust in firmware for years, and Rust "is ensuring memory safety from the ground up in several security-critical Google applications," including Chromium's parsers for PNG, JSON, and web fonts.]
2025 was the first year more lines of Rust code were added to Android than lines of C++ code...

OpenBSD 7.8 has been released, adding Raspberry Pi 5 support, enhanced AMD Secure Encrypted Virtualization (SEV-ES) capabilities, and expanded hardware compatibility including new Qualcomm, Rockchip, and Apple ARM drivers. Phoronix reports: OpenBSD 7.8 also brings multiple improvements around enabling AMD Secure Encrypted Virtualization (AMD SEV) support with support for the PSP ioctl for encrypting and measuring state for SEV-ES, a new VMD option to run guests in SEV-ES mode, and other enablement work pertaining to that AMD SEV work in SEV-ES form at this point as a precursor to SEV-SNP. AMD SEV-ES should be working to start confidential virtual machines (VMs) when using the VMM/VMD hypervisor and the OpenBSD guests with KVM/QEMU.

OpenBSD 7.8 also improves compatibility of the FUSE file-system support with the Linux implementation, suspend/hibernate improvements, SMP improvements, updating to the Linux 6.12.50 DRM graphics drivers, several new Rockchip drivers, Raspberry Pi RP1 drivers, H.264 video support for the uvideo driver, and many network driver improvements. The changelog and download page can be found via OpenBSD.org.

"It's not just you. The internet is getting worse, fast," writes Cory Doctorow. Sunday he shared an excerpt from his upcoming book Enshittification: Why Everything Suddenly Got Worse and What to Do About It.

He succinctly explains "this moment we're living through, this Great Enshittening" using Amazon as an example. Platforms amass users, but then abuse them to make things better for their business customers. And then they abuse those business customers too, abusing everybody while claiming all the value for themselves. "And become a giant pile of shit."

So first Amazon subsidized prices and shipping, then locked in customers with Prime shipping subscriptions (while adding the chains of DRM to its ebooks and audiobooks)... These tactics — Prime, DRM and predatory pricing — make it very hard not to shop at Amazon. With users locked in, to proceed with the enshittification playbook, Amazon needed to get its business customers locked in, too... [M]erchants' dependence on those customers allows Amazon to extract higher discounts from those merchants, and that brings in more users, which makes the platform even more indispensable for merchants, allowing the company to require even deeper discounts...

[Amazon] uses its overview of merchants' sales, as well as its ability to observe the return addresses on direct shipments from merchants' contracting factories, to cream off its merchants' bestselling items and clone them, relegating the original seller to page umpty-million of its search results. Amazon also crushes its merchants under a mountain of junk fees pitched as optional but effectively mandatory. Take Prime: a merchant has to give up a huge share of each sale to be included in Prime, and merchants that don't use Prime are pushed so far down in the search results, they might as well cease to exist. Same with Fulfilment by Amazon, a "service" in which a merchant sends its items to an Amazon warehouse to be packed and delivered with Amazon's own inventory. This is far more expensive than comparable (or superior) shipping services from rival logistics companies, and a merchant that ships through one of those rivals is, again, relegated even farther down the search rankings.

All told, Amazon makes so much money charging merchants to deliver the wares they sell through the platform that its own shipping is fully subsidised. In other words, Amazon gouges its merchants so much that it pays nothing to ship its own goods, which compete directly with those merchants' goods.... Add all the junk fees together and an Amazon seller is being screwed out of 45-51 cents on every dollar it earns there. Even if it wanted to absorb the "Amazon tax" on your behalf, it couldn't. Merchants just don't make 51% margins. So merchants must jack up prices, which they do. A lot... [W]hen merchants raise their prices on Amazon, they are required to raise their prices everywhere else, even on their own direct-sales stores. This arrangement is called most-favoured-nation status, and it's key to the U.S. Federal Trade Commission's antitrust lawsuit against Amazon...

If Amazon is taxing merchants 45-51 cents on every dollar they make, and if merchants are hiking their prices everywhere their goods are sold, then it follows you're paying the Amazon tax no matter where you shop — even the corner mom-and-pop hardware store. It gets worse. On average, the first result in an Amazon search is 29% more expensive than the best match for your search. Click any of the top four links on the top of your screen and you'll pay an average of 25% more than you would for your best match — which, on average, is located 17 places down in an Amazon search result.
Doctorow knows what we need to do:

• Ban predatory pricing — "selling goods below cost to keep competitors out of the market (and then jacking them up again)."

• Impose structural separation, "so it can either be a platform, or compete with the sellers that rely on it as a platform."

• Curb junk fees, "which suck 45-51 cents on every dollar merchants take in."

• End its most favoured nation deal, which forces merchants "to raise their prices everywhere else, too.

• Unionise drivers and warehouse workers.

• Treat rigged search results as the fraud they are.

These are policy solutions. (Because "You can't shop your way out of a monopoly," Doctorow warns.) And otherwise, as Doctorow says earlier, "Once a company is too big to fail, it becomes too big to jail, and then too big to care."

In the mean time, Doctorow also makes up a new word — "the enshitternet" — calling it "a source of pain, precarity and immiseration for the people we love.

"The indignities of harassment, scams, disinformation, surveillance, wage theft, extraction and rent-seeking have always been with us, but they were a minor sideshow on the old, good internet and they are the everything and all of the enshitternet."

Thanks to long-time Slashdot readers mspohr and fjo3 for sharing the article.

Independent UK bookshops will now be able to sell ebooks via a new platform (Bookshop.org's expansion), keeping 100% of profits and offering a non-Amazon way to reach digital readers. "Bookshops now have an additional tool in their fight against Amazon," said Nicole Vanderbilt, managing director of Bookshop.org UK. "Digital readers don't depend on Amazon's monopoly any more, now that they can find ebooks at the same price on Bookshop.org." The Guardian reports: Bookshop.org launched in the UK in November 2020 as a platform for independent bookshops to sell physical books. Bookshops receive 30% of the cover price from each sale they generate; so far, the UK site has generated 4.5 million pounds for independent bookshops. Customers will also now be able to buy ebooks through a bookshop of their choice. Profits from orders without a specified bookshop will be added to a shared pool, which will be distributed among all participating bookshops on the platform. [...]

The platform will launch with a catalogue of more than a million ebooks from all major publishers. It will be available online via a web browser and through the Bookshop.org apps on Apple and Android. "Due to Amazon's proprietary digital rights management [DRM] software and publishers' DRM requirements, it's not currently possible to buy DRM-protected ebooks from Bookshop.org or local bookshops and read them on your Kindle," said Bookshop.org. However, the site is working with the e-reader company Kobo to support Kobo devices "later this year," and longer term would "love to offer our own eInk device."

An anonymous reader quotes a report from Ars Technica: Last year, we reported on the efforts of classic iPod fans to preserve playable copies of the downloadable clickwheel games that Apple sold for a brief period in the late '00s. The community was working to get around Apple's onerous FairPlay DRM by having people who still owned original copies of those (now unavailable) games sync their accounts to a single iTunes installation via a coordinated Virtual Machine. That "master library" would then be able to provide playable copies of those games to any number of iPods in perpetuity.

At the time, the community was still searching for iPod owners with syncable copies of the last few titles needed for their library. With today's addition of Real Soccer 2009 to the project, though, all 54 official iPod clickwheel games are now available together in an easily accessible format for what is likely the first time.

[...] Now that the consolidated clickwheel game collection is complete, though, owners of any iPod 5G+ or iPod Nano 3G+ should be able to sync the complete library to their personal device completely offline, without worrying about any server checks from Apple. They can do that by setting up a Virtual Machine using these GitHub instructions or by downloading this torrented Internet Archive collection and creating their own Virtual Machine from the files contained therein. The effort was made possible by GitHub user Olsro, with help from other iPod enthusiasts. To Olsro, completing the project "means this whole part from the early 2000s will remain with us forever."

He also expressed hope that "this Virtual Machine can also be useful towards any security [or] archeologist researcher who want to understand how the DRM worked."

ZDNet's Steven Vaughan-Nichols shares his list of "what's new and improved" in the latest Linux 6.16 kernel. An anonymous reader shares an excerpt from the report: First, the Rust language is continuing to become more well-integrated into the kernel. At the top of my list is that the kernel now boasts Rust bindings for the driver core and PCI device subsystem. This approach will make it easier to add new Rust-based hardware drivers to Linux. Additionally, new Rust abstractions have been integrated into the Direct Rendering Manager (DRM), particularly for ioctl handling, file/GEM memory management, and driver/device infrastructure for major GPU vendors, such as AMD, Nvidia, and Intel. These changes should reduce vulnerabilities and optimize graphics performance. This will make gamers and AI/ML developers happier.

Linux 6.16 also brings general improvements to Rust crate support. Crate is Rust's packaging format. This will make it easier to build, maintain, and integrate Rust kernel modules into the kernel. For those of you who still love C, don't worry. The vast majority of kernel code remains in C, and Rust is unlikely to replace C soon. In a decade, we may be telling another story. Beyond Rust, this latest release also comes with several major file system improvements. For starters, the XFS filesystem now supports large atomic writes. This capability means that large multi-block write operations are 'atomic,' meaning all blocks are updated or none. This enhances data integrity and prevents data write errors. This move is significant for companies that use XFS for databases and large-scale storage.

Perhaps the most popular Linux file system, Ext4, is also getting many improvements. These boosts include faster commit paths, large folio support, and atomic multi-fsblock writes for bigalloc filesystems. What these improvements mean, if you're not a file-system nerd, is that we should see speedups of up to 37% for sequential I/O workloads. If your Linux laptop doubles as a music player, another nice new feature is that you can now stream your audio over USB even while the rest of your system is asleep. That capability's been available in Android for a while, but now it's part of mainline Linux.

If security is a top priority for you, the 6.16 kernel now supports Intel Trusted Execution Technology (TXT) and Intel Trusted Domain Extensions (TDX). This addition, along with Linux's improved support for AMD Secure Encrypted Virtualization and Secure Memory Encryption (SEV-SNP), enables you to encrypt your software's memory in what's known as confidential computing. This feature improves cloud security by encrypting a user's virtual machine memory, meaning someone who cracks a cloud can't access your data. Linux 6.16 also delivers several chip-related upgrades. It introduces support for Intel's Advanced Performance Extensions (APX), doubling x86 general-purpose registers from 16 to 32 and boosting performance on next-gen CPUs like Lunar Lake and Granite Rapids Xeon. Additionally, the new CONFIG_X86_NATIVE_CPU option allows users to build processor-optimized kernels for greater efficiency.

Support for Nvidia's AI-focused Blackwell GPUs has also been improved, and updates to TCP/IP with DMABUF help offload networking tasks to GPUs and accelerators. While these changes may go unnoticed by everyday users, high-performance systems will see gains and OpenVPN users may finally experience speeds that challenge WireGuard.

"A Nintendo Switch 2 user reportedly got his brand-new console banned by Nintendo after buying used Switch 1 games and patching them on his console," reports Tom's Hardware: According to Reddit user dmanthey, they purchased four used titles off the Facebook marketplace, inserted them into the Switch 2, and had them all updated. When they turned on their handhelds the following day, they received a message saying that they were restricted from Nintendo's online services and that they couldn't even download the games they had already bought...

[T]hey were able to prove their innocence by pulling up the Facebook Marketplace listing for their games and sending the photos of their purchased cartridges. According to the Redditor, the process was painless and fast, and it was "so much easier than getting support from Microsoft or Sony...." Other users warned, though, that this isn't always a guaranteed resolution.

Nintendo is known for being protective of its intellectual property and delivers harsh penalties to anyone caught violating it. We've already had several reports of users getting banned for using Mig Flash, even on their own ROMs. And while it's not true that getting banned turns your Switch 2 into a brick, it will still prevent you from accessing the company's online services, which severely restricts its features and usability.
"Nintendo attaches unique codes to its Switch game cartridges to prevent piracy," notes Engadget. "However, bad actors can copy games onto a third-party device, like the MIG Flash, and then resell the physical game card. Once Nintendo detects two instances of its unique code being online at the same time, it will ban any accounts using it..." This anti-piracy policy isn't new — Nintendo has long had a reputation for fiercely combating any type of piracy — but it has become relevant again thanks to the recently released Switch 2, which offers backwards compatibility with original Switch titles. The company even recently amended its user agreement to allow itself the power to brick a Nintendo Switch that's caught running pirated games or mods.

An anonymous reader quotes a report from the BBC: A lack of action by big tech firms is enabling the "industrial scale theft" of premium video services, especially live sport, a new report says. The research by Enders Analysis accuses Amazon, Google, Meta and Microsoft of "ambivalence and inertia" over a problem it says costs broadcasters revenue and puts users at an increased risk of cyber-crime. Gareth Sutcliffe and Ollie Meir, who authored the research, described the Amazon Fire Stick -- which they argue is the device many people use to access illegal streams -- as "a piracy enabler." [...] The device plugs into TVs and gives the viewer thousands of options to watch programs from legitimate services including the BBC iPlayer and Netflix. They are also being used to access illegal streams, particularly of live sport.

In November last year, a Liverpool man who sold Fire Stick devices he reconfigured to allow people to illegally stream Premier League football matches was jailed. After uploading the unauthorized services on the Amazon product, he advertised them on Facebook. Another man from Liverpool was given a two-year suspended sentence last year after modifying fire sticks and selling them on Facebook and WhatsApp. According to data for the first quarter of this year, provided to Enders by Sky, 59% of people in UK who said they had watched pirated material in the last year while using a physical device said they had used a Amazon fire product. The Enders report says the fire stick enables "billions of dollars in piracy" overall. [...]

The researchers also pointed to the role played by the "continued depreciation" of Digital Rights Management (DRM) systems, particularly those from Google and Microsoft. This technology enables high quality streaming of premium content to devices. Two of the big players are Microsoft's PlayReady and Google's Widevine. The authors argue the architecture of the DRM is largely unchanged, and due to a lack of maintenance by the big tech companies, PlayReady and Widevine "are now compromised across various security levels." Mr Sutcliffe and Mr Meir said this has had "a seismic impact across the industry, and ultimately given piracy the upper hand by enabling theft of the highest quality content." They added: "Over twenty years since launch, the DRM solutions provided by Google and Microsoft are in steep decline. A complete overhaul of the technology architecture, licensing, and support model is needed. Lack of engagement with content owners indicates this a low priority."

BrianFagioli writes: Signal has officially had enough, folks. You see, the privacy-first messaging app is going on the offensive, declaring war on Microsoft's invasive Recall feature by enabling a new "Screen security" setting by default on Windows 11. This move is designed to block Microsoft's AI-powered screenshot tool from capturing your private chats.

If you aren't aware, Recall was first unveiled a year ago as part of Microsoft's Copilot+ PC push. The feature quietly took screenshots of everything happening on your computer, every few seconds, storing them in a searchable timeline. Microsoft claimed it would help users "remember" what they've done. Critics called it creepy. Security experts called it dangerous. The backlash was so fierce that Microsoft pulled the feature before launch.

But now, in a move nobody asked for, Recall is sadly back. And thankfully, Signal isn't waiting around this time. The team has activated a Windows 11-specific DRM flag that completely blacks out Signal's chat window when a screenshot is attempted. If you've ever tried to screen grab a streaming movie, you'll know the result: nothing but black.

Synology's upcoming Plus Series NAS systems will restrict full functionality to users who install the company's self-branded hard drives, Tom's Hardware is reporting, marking a significant shift in the consumer NAS market. While third-party drives will still work for basic storage, critical features including drive health monitoring, volume-wide deduplication, lifespan analysis, and automatic firmware updates will be disabled, the publication said.

The restriction doesn't apply to Synology's 2024 and older models, only affecting new Plus Series devices targeted at SMBs and advanced home users. Synology itself doesn't manufacture drives but rebrands HDDs from major manufacturers like Seagate, Western Digital, and Toshiba, often with custom firmware that functions as DRM. According to Synology, the change follows successful implementation in their enterprise solutions and will deliver "higher performance, increased reliability, and more efficient support." A workaround exists: users can initialize a non-Synology drive in an older Synology NAS and then migrate it to a new Plus model without restrictions.

"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."