alternative_right shares a report from Phys.org: Astronomers have an answer for a long-running mystery in astrophysics: why is the growth of supermassive black holes so much lower today than in the past? A study using NASA's Chandra X-ray Observatory and other X-ray telescopes found that supermassive black holes are unable to consume material as rapidly as they did in the distant past. The results appeared in the December 2025 issue of The Astrophysical Journal.

[...] The team ran tests of the three main possible scenarios currently being considered for the slowdown of black hole growth. These options were: could the decline in black hole growth be caused by less efficient rates of consumption, or by smaller typical black hole masses, or by fewer actively growing black holes? Their analysis of the data, extending over billions of years of cosmic history, led them to the conclusion that black holes are indeed consuming material less rapidly the later they are found after the Big Bang. The researchers expect this trend of slower-growing black holes to continue into the future.

An anonymous reader quotes a report from TechCrunch: Anthropic co-founder and CEO Dario Amodei is not happy -- perhaps predictably so -- with OpenAI chief Sam Altman. In a memo to staff, reported by The Information, Amodei referred to OpenAI's dealings with the Department of Defense as "safety theater." "The main reason [OpenAI] accepted [the DoD's deal] and we did not is that they cared about placating employees, and we actually cared about preventing abuses," Amodei wrote.

Last week, Anthropic and the U.S. Department of Defense (DoD) failed to come to an agreement over the military's request for unrestricted access to the AI company's technology. Anthropic, which already had a $200 million contract with the military, insisted the DoD affirm that it would not use the company's AI to enable domestic mass surveillance or autonomous weaponry. Instead, the DoD -- known under the Trump administration as the Department of War -- struck a deal with OpenAI. Altman stated that his company's new defense contract would include protections against the same red lines that Anthropic had asserted.

In a letter to staff, Amodei refers to OpenAI's messaging as "straight up lies," stating that Altman is falsely "presenting himself as a peacemaker and dealmaker." Amodei might not be speaking solely from a position of bitterness, here. Anthropic specifically took issue with the DoD's insistence on the company's AI being available for "any lawful use." [...] "I think this attempted spin/gaslighting is not working very well on the general public or the media, where people mostly see OpenAI's deal with the DoW as sketchy or suspicious, and see us as the heroes (we're #2 in the App Store now!)," Amodei wrote to his staff. "It is working on some Twitter morons, which doesn't matter, but my main worry is how to make sure it doesn't work on OpenAI employees."

Early Friday "there were nearly 113 incidents of people reporting issues with Microsoft 365 as of 1:05 a.m. ET," reports Reuters. But that's down "from over 15,890 reports at its peak a day earlier, according to Downdetector." Reuters points out the outage affected antivirus software Microsoft Defender and data governance software Microsoft Purview, while CRN notes it also impacted "a number of Microsoft 365 services" including Outlook and Exchange online: During the outage, Outlook users received a "451 4.3.2 temporary server issue" error message when attempting to send or receive email. Users did not have the ability to send and receive email through Exchange Online, including notification emails from Microsoft Viva Engage, according to the vendor. Other issues that cropped up include an inability to send and receive subscription email through [analytics platform] Microsoft Fabric, collect message traces, search within SharePoint online and Microsoft OneDrive and create chats, meetings, teams, channels or add members in Microsoft Teams...

As with past cloud outages with other vendors, even after Microsoft fixed the issues, recovery efforts by its users to return to a normal state took additional time... Microsoft confirmed in a post on X [Thursday] at 4:14 p.m. ET that it "restored the affected infrastructure to a (healthy) state" but "further load balancing is required to mitigate impact...." The company reported "residual imbalances across the environment" at 7:02 p.m., "restored access to the affected services" and stable mail flow at 12:33 a.m. Jan. 23. At that time, Microsoft still saw a "small number of remaining affected services" without full service stability. The company declared impact from the event "resolved" at 1:29 p.m. Eastern. Microsoft sent out another X post at 8:20 a.m. asking users experiencing residual issues to try "clearing local DNS caches or temporarily lowering DNS TTL values may help ensure a quicker remediation...."

Microsoft said in an admin center update that [Thursday's] outage was "caused by elevated service load resulting from reduced capacity during maintenance for a subset of North America hosted infrastructure." Furthermore, Microsoft noted that during "ongoing efforts to rebalance traffic" it introduced a "targeted load balancing configuration change intended to expedite the recovery process, which incidentally introduced additional traffic imbalances associated with persistent impact for a portion of the affected infrastructure." US itek's David Stinner said it appears that Microsoft did not have enough capacity on its backup system while doing maintenance on its main system. "It looks like the backup system was overloaded, and it brought the system down while they were still doing maintenance on the main system," he said. "That is why it took so many hours to get back up and running. If your primary system is down for maintenance and your backup system fails due to capacity issues, then it is going to take a while to get your primary system back up and running."
"This was not Microsoft's first outage of 2026," the article notes, "with the vendor handling access issues with Teams, Outlook and other M365 services on Wednesday, a Copilot issue on Jan. 15 plus an Azure outage earlier in the month..."

The price of water and sewer services for American households has more than doubled since the early 1980s after adjusting for inflation, even though per-capita water use has actually decreased over that period. Households in large cities now spend about $1,300 a year on water and sewer charges, approaching the roughly $1,600 they spend on electricity. The main driver is federal regulation.

Since the Clean Water Act of 1972 and the Safe Drinking Water Act of 1974, the U.S. has spent approximately $5 trillion in contemporary dollars fighting water pollution -- about 0.8% of annual GDP across that period. The EPA itself admits that surface water regulations are the one category of environmental rules where estimated costs exceed estimated benefits.

New York City was required to build a filtration plant to address two minor parasites in water from its Croton aqueduct. The project took a decade longer than expected and cost $3.2 billion, more than double the original estimate. After the plant opened in 2015, the city's Commissioner of Environmental Protection noted that the water would basically be "the same" to the public. Jefferson County, Alabama, meanwhile, descended into what was then the largest municipal bankruptcy in U.S. history in 2011 after EPA-mandated sewer upgrades pushed its debt from $300 million to over $3 billion.

Is there a trend? This week four different articles appeared on various tech-news sites with an author bragging about switching to Linux.

"Greetings from the year of Linux on my desktop," quipped the Verge's senior reviews editor, who finally "got fed up and said screw it, I'm installing Linux."

They switched to CachyOS — just like this writer for the videogame magazine Escapist: I've had a fantastic time gaming on Linux. Valve's Windows-to-Linux translation layer, Proton, and even CachyOS' bundled fork have been working just fine. Of course, it's not perfect, and there's been a couple of instances where I've had to problem-solve something, but most of the time, any issues gaming on Linux have been fixed by swapping to another version of Proton. If you're deep in online games like Fortnite, Call of Duty, Destiny 2, GTAV or Battlefield 6, it might not be the best option to switch. These games feature anti-cheats that look for versions of Windows or even the heart of the OS, the kernel, to verify the system isn't going to mess up someone's game....

CachyOS is thankfully pre-packed with Nvidia drivers, meaning I didn't have to dance around trying to find them.... Certain titles will perform worse than their counterparts, simply due to how the bods at Nvidia are handling the drivers for Linux. This said, I'm still not complaining when I'm pushing nearly 144fps or more in newer games. The performance hit is there, but it's nowhere near enough to stave off even an attempt to mess about with Linux.

Do you know how bizarre it is to say it's "nice to have a taskbar again"? I use macOS daily for a lot of my work, which uses a design baked back in the 1990s through NeXT. Seeing just a normal taskbar that doesn't try to advertise to me or crash because an update killed it for some reason is fantastic. That's how bad it is out there right now for Windows.
"I run Artix, by the way," joked a senior tech writer at Notebookcheck (adding "There. That's out of the way...") I dual-booted a Linux partition for a few weeks. After a Windows update (that I didn't choose to do) wiped that partition and, consequently, the Linux installation, I decided to go whole-hog: I deleted Windows 11 and used the entire drive for Linux...

Artix differs from Arch in that it does not use SystemD as its init system. I won't go down the rabbit hole of init systems here, but suffice it to say that Artix boots lightning quick (less than 10 seconds from a cold power on) and is pretty light on system resources. However, it didn't come "fully assembled..." The biggest problem I ran into after installing Artix on the [MacBook] Air was the lack of wireless drivers, which meant that WiFi did not work out of the box. The resolution was simple: I needed to download the appropriate WiFi drivers (Broadcom drivers, to be exact) from Artix's main repository. This is a straightforward process handled by a single command in the Terminal, but it requires an internet connection... which my laptop did not have. Ultimately, I connected a USB-to-Ethernet adapter, plugged the laptop directly into my router, and installed the WiFi drivers that way. The whole process took about 10 minutes, but it was annoying nonetheless.

For the record, my desktop (an AMD Ryzen 7 6800H-based system) worked flawlessly out-of-the-box, even with my second monitor's uncommon resolution (1680x1050, vertical orientation). I did run into issues with installing some packages on both machines. Trying to install the KDE desktop environment (essentially a different GUI for the main OS) resulted in strange artifacts that put white text on white backgrounds in the menus, and every resolution I tried failed to correct this bug. After reverting to XFCE4 (the default desktop environment for my Artix install), the WiFi signal indicator in the taskbar disappeared. This led to me having to uninstall a network manager installed by KDE and re-linking the default network manager to the runit services startup folder. If that sentence sounds confusing, the process was much more so. It has been resolved, and I have a WiFi indicator that lets me select wireless networks again, but only after about 45 minutes of reading manuals and forum posts.

Other issues are inherent to Linux. Not all games on Steam that are deemed Linux compatible actually are. Civilization III Complete is a good example: launching the game results in the map turning completely black. (Running the game through an application called Lutris resolved this issue.) Not all the software I used on Windows is available in Linux, such as Greenshot for screenshots or uMark for watermarking photos in bulk. There are alternatives to these, but they don't have the same features or require me to relearn workflows... Linux is not a "one and done" silver bullet to solve all your computer issues. It is like any other operating system in that it will require users to learn its methods and quirks. Admittedly, it does require a little bit more technical knowledge to dive into the nitty-gritty of the OS and fully unlock its potential, but many distributions (such as Mint) are ready to go out of the box and may never require someone to open a command line...

[T]he issues I ran into on Linux were, for the most part, my fault. On Windows or macOS, most problems I run into are caused by a restriction or bug in the OS. Linux gives me the freedom to break my machine and fix it again, teaching me along the way. With Microsoft's refusal (either from pride or ignorance) to improve (or at least not crapify) Windows 11 despite loud user outrage, switching to Linux is becoming a popular option. It's one you should consider doing, and if you've been thinking about it for any length of time, it's time to dive in.
And tinkerer Kevin Wammer switched from MacOS to Linux, saying "Linux has come a long way" after more than 30 years — but "Windows still sucks..."

After a successful November 27th launch to the International Space Station, Russia discovered an accident had occurred on their launch site's mobile maintenance cabin — when a drone spotted it lying upside down in a flame trench. "The main issue with the structure collapse is that it puts Site 31/6 — the only Russian launch site capable of launching crew and cargo to the International Space Station (ISS) — out of service until the structure is fixed," reports the space-news site NASA Spaceflight There are other Soyuz 2 rocket launch pads, but they are either located at an unsuitable latitude, like Plesetsk, or not certified for crewed flights, like Vostochny, or decommissioned and transferred to a museum, like Gagarin's Start at Baikonur. As a result, Russia is temporarily unable to launch Soyuz crewed spacecraft and Progress cargo ships to the ISS, whose nearest launch (Progress MS-33) was scheduled for December 21....

When the rocket launched, a pressure difference was created between the space under the rocket, where gases from running engines are discharged, and the nook where the [144-ton] maintenance cabin was located. The resulting pressure difference pulled the service cabin out of the nook and threw it into the flame trench, where it fell upside down from a height of 20 m. Photos of the accident showed significant damage to the maintenance cabin, which, according to experts, is too extensive to allow for repairs. The only way to resume launches from Site 31/6 is to install a spare maintenance cabin or construct a new one.

Despite the fact that the fallen structure was manufactured in the 1960s, two similar service cabins were manufactured recently at the Tyazhmash heavy-engineering plant in Syzran for other Soyuz launch complexes at the Guiana Space Center and Vostochny Cosmodrome. The production of each cabin took around two years to complete, however, it was not for an emergency situation.
"Various experts gave different possible estimates of the recovery time of the Site 31 launch complex: from several months to three years."

A critical security flaw in Chromium's Blink rendering engine can crash billions of browsers within seconds. Security researcher Jose Pino discovered the vulnerability and created a proof-of-concept exploit called Brash to demonstrate the bug affecting Chrome, Edge, OpenAI's ChatGPT Atlas, Brave, Vivaldi, Arc, Dia, Opera and Perplexity Comet.

The flaw, reports The Register, exploits the absence of rate limiting on document.title API updates in Chromium versions 143.0.7483.0 and later. The attack injects millions of DOM mutations per second and saturates the main thread. When The Register tested the code on Edge, the browser crashed and the Windows machine locked up after about 30 seconds while consuming 18GB of RAM in one tab. Pino disclosed the bug to the Chromium security team on August 28 and followed up on August 30 but received no response. Google said it is looking into the issue.

On Cloudflare's blog, a senior research engineer shares a plan for "improving the trustworthiness of JavaScript on the web."

"It is as true today as it was in 2011 that Javascript cryptography is Considered Harmful." The main problem is code distribution. Consider an end-to-end-encrypted messaging web application. The application generates cryptographic keys in the client's browser that lets users view and send end-to-end encrypted messages to each other. If the application is compromised, what would stop the malicious actor from simply modifying their Javascript to exfiltrate messages? It is interesting to note that smartphone apps don't have this issue. This is because app stores do a lot of heavy lifting to provide security for the app ecosystem. Specifically, they provide integrity, ensuring that apps being delivered are not tampered with, consistency, ensuring all users get the same app, and transparency, ensuring that the record of versions of an app is truthful and publicly visible.

It would be nice if we could get these properties for our end-to-end encrypted web application, and the web as a whole, without requiring a single central authority like an app store. Further, such a system would benefit all in-browser uses of cryptography, not just end-to-end-encrypted apps. For example, many web-based confidential LLMs, cryptocurrency wallets, and voting systems use in-browser Javascript cryptography for the last step of their verification chains. In this post, we will provide an early look at such a system, called Web Application Integrity, Consistency, and Transparency (WAICT) that we have helped author. WAICT is a W3C-backed effort among browser vendors, cloud providers, and encrypted communication developers to bring stronger security guarantees to the entire web... We hope to build even wider consensus on the solution design in the near future....

We would like to have a way of enforcing integrity on an entire site, i.e., every asset under a domain. For this, WAICT defines an integrity manifest, a configuration file that websites can provide to clients. One important item in the manifest is the asset hashes dictionary, mapping a hash belonging to an asset that the browser might load from that domain, to the path of that asset.
The blog post points out that the WEBCAT protocol (created by the Freedom of Press Foundation) "allows site owners to announce the identities of the developers that have signed the site's integrity manifest, i.e., have signed all the code and other assets that the site is serving to the user... We've made WAICT extensible enough to fit WEBCAT inside and benefit from the transparency components." The proposal also envisions a service storing metadata for transparency-enabled sites on the web (along with "witnesses" who verify the prefix tree holding the hashes for domain manifests).

"We are still very early in the standardization process," with hopes to soon "begin standardizing the integrity manifest format. And then after that we can start standardizing all the other features. We intend to work on this specification hand-in-hand with browsers and the IETF, and we hope to have some exciting betas soon. In the meantime, you can follow along with our transparency specification draft,/A>, check out the open problems, and share your ideas."

Software vendors keen to monetize AI should tread cautiously, since they risk inflating costs for their customers without delivering any promised benefits such as reducing employee head count. From a report: The latest report from McKinsey & Company mulls what software-as-a-service (SaaS) vendors need to do to navigate the minefield of hype that surrounds AI and successfully fold such capabilities into their offerings. According to the consultancy, there are three main challenges it identifies as holding back broader growth in AI software monetization in the report.

One of these is simply the inability to show any savings that can be expected. Many software firms trumpet potential use cases for AI, but only 30 percent have published quantifiable return on investment from real customer deployments. Meanwhile, many customers see AI hiking IT costs without being able to offset these by slashing labor costs. The billions poured into developing AI models mean they don't come cheap, and AI-enabling the entire customer service stack of a typical business could lead to a 60 to 80 percent price increase, McKinsey says, while quoting an HR executive at a Fortune 100 company griping: "All of these copilots are supposed to make work more efficient with fewer people, but my business leaders are also saying they can't reduce head count yet."

Another challenge is scaling up adoption after introduction, which the report blames on underinvestment in change management. It says that for every $1 spent on model development, firms should expect to have to spend $3 on change management, which means user training and performance monitoring. The third issue is a lack of predictable pricing, which means that customers find it hard to forecast how their AI costs will scale with usage because the pricing models are often complex and opaque.

An anonymous reader quotes a report from Ars Technica: On Wednesday afternoon, Anthropic experienced a brief but complete service outage that took down its AI infrastructure, leaving developers unable to access Claude.ai, the API, Claude Code, or the management console for around half an hour. The outage affected all three of Anthropic's main services simultaneously, with the company posting at 12:28 pm Eastern that "APIs, Console, and Claude.ai are down. Services will be restored as soon as possible." As of press time, the services appear to be restored. The disruption, though lasting only about 30 minutes, quickly took the top spot on tech link-sharing site Hacker News for a short time and inspired immediate reactions from developers who have become increasingly reliant on AI coding tools for their daily work. "Everyone will just have to learn how to do it like we did in the old days, and blindly copy and paste from Stack Overflow," joked one Hacker News commenter. Another user recalled a joke from a previous AI outage: "Nooooo I'm going to have to use my brain again and write 100% of my code like a caveman from December 2024."

The most recent outage came at an inopportune time, affecting developers across the US who have integrated Claude into their workflows. One Hacker News user observed: "It's like every other day, the moment US working hours start, AI (in my case I mostly use Anthropic, others may be better) starts dying or at least getting intermittent errors. In EU working hours there's rarely any outages." Another user also noted this pattern, saying that "early morning here in the UK everything is fine, as soon as most of the US is up and at it, then it slowly turns to treacle." While some users criticized Anthropic for reliability issues in recent months, the company's status page acknowledged the issue within 39 minutes of the initial reports, and by 12:55 pm Eastern announced that a fix had been implemented and that the company's teams were monitoring the results.

Slashdot reader Charlotte Web shared this report from the Register: Among the software developers who use Microsoft's GitHub, the most popular community discussion in the past 12 months has been a request for a way to block Copilot, the company's AI service, from generating issues and pull requests in code repositories. The second most popular discussion — where popularity is measured in upvotes — is a bug report that seeks a fix for the inability of users to disable Copilot code reviews. Both of these questions, the first opened in May and the second opened a month ago, remain unanswered, despite an abundance of comments critical of generative AI and Copilot...

The author of the first, developer Andi McClure, published a similar request to Microsoft's Visual Studio Code repository in January, objecting to the reappearance of a Copilot icon in VS Code after she had uninstalled the Copilot extension... "I've been for a while now filing issues in the GitHub Community feedback area when Copilot intrudes on my GitHub usage," McClure told The Register in an email. "I deeply resent that on top of Copilot seemingly training itself on my GitHub-posted code in violation of my licenses, GitHub wants me to look at (effectively) ads for this project I will never touch. If something's bothering me, I don't see a reason to stay quiet about it. I think part of how we get pushed into things we collectively don't want is because we stay quiet about it."

It's not just the burden of responding to AI slop, an ongoing issue for Curl maintainer Daniel Stenberg. It's the permissionless copying and regurgitation of speculation as fact, mitigated only by small print disclaimers that generative AI may produce inaccurate results. It's also GitHub's disavowal of liability if Copilot code suggestions happen to have reproduced source code that requires attribution. It's what the Servo project characterizes in its ban on AI code contributions as the lack of code correctness guarantees, copyright issues, and ethical concerns. Similar objections have been used to justify AI code bans in GNOME's Loupe project, FreeBSD, Gentoo, NetBSD, and QEMU... Calls to shun Microsoft and GitHub go back a long way in the open source community, but moved beyond simmering dissatisfaction in 2022 when the Software Freedom Conservancy (SFC) urged free software supporters to give up GitHub, a position SFC policy fellow Bradley M. Kuhn recently reiterated.
McClure says In the last six months their posts have drawn more community support — and tells the Register there's been a second change in how people see GitHub within the last month. After GitHub moved from a distinct subsidiary to part of Microsoft's CoreAI group, "it seems to have galvanized the open source community from just complaining about Copilot to now actively moving away from GitHub."

"I have not pulled this, I'm annoyed by having to even look at this, and if you actually expect me to pull this I want a real explanation and not a useless link," Linus Torvalds posted Friday on the Linux kernel mailing list.

Phoronix explains: It's become a common occurrence seeing "Link: " tags within Git commits for the Linux kernel that point to the latest Linux kernel mailing list patches of the same patch... Linus Torvalds has had enough and will be more strict against accepting pull requests that have link tags of no value. He commented yesterday on a block pull request that he pulled and then backed out of:

"And dammit, this commit has that promising 'Link:' argument that I hoped would explain why this pointless commit exists, but AS ALWAYS that link only wasted my time by pointing to the same damn information that was already there. I was hoping that it would point to some oops report or something that would explain why my initial reaction was wrong.

"Stop this garbage already. Stop adding pointless Link arguments that waste people's time. Add the link if it has *ADDITIONAL* information....

"Yes, I'm grumpy. I feel like my main job — really my only job — is to try to make sense of pull requests, and that's why I absolutely detest these things that are automatically added and only make my job harder."
A longer discussion ensued...

• Torvalds: [A] "perfect" model might be to actually have some kind of automation of "unless there was actual discussion about it". But I feel such a model might be much too complicated, unless somebody *wants* to explore using AI because their job description says "Look for actual useful AI uses". In today's tech world, I assume such job descriptions do exist. Sigh...

• Torvalds: I do think it makes sense for patch series that (a) are more than a small handful of patches and (b) have some real "story" to them (ie a cover letter that actually explains some higher-level issues)...

Torvalds also had two responses to a poster who'd said "IMHO it's better to have a Link and it _potentially_ being useful than not to have it and then need to search around for it."

• Torvalds: No. Really. The issue is "potentially — but very likely not — useful" vs "I HIT THIS TEN+ TIMES EVERY SINGLE F%^& RELEASE".
  
  There is just no comparison. I have literally *never* found the original submission email to be useful, and I'm tired of the "potentially useful" argument that has nothing to back it up with. It's literally magical thinking of "in some alternate universe, pigs can fly, and that link might be useful"

• Torvalds: And just to clarify: the hurt is real. It's not just the disappointment. It's the wasted effort of following a link and having to then realize that there's nothing useful there. Those links *literally* double the effort for me when I try to be careful about patches...
  
  The cost is real. The cost is something I've complained about before... Yes, it's literally free to you to add this cost. No, *YOU* don't see the cost, and you think it is helpful. It's not. It's the opposite of helpful. So I want commit messages to be relevant and explain what is going on, and I want them to NOT WASTE MY TIME.
  
  And I also don't want to ignore links that are actually *useful* and give background information. Is that really too much to ask for?

Torvalds points out he's brought this up four times before — once in 2022.

• Torvalds: I'm a bit frustrated, exactly because this _has_ been going on for years. It's not a new peeve.
  
  And I don't think we have a good central place for that kind of "don't do this". Yes, there's the maintainer summit, but that's a pretty limited set of people. I guess I could mention it in my release notes, but I don't know who actually reads those either.. So I end up just complaining when I see it.

In 2016 comedian Dave Chappelle made headlines by requiring concert attendees to lock their cellphones in a pouch to prevent recording.

Nine years later those pouches (made by tech startup Yondr) are required for at least 2.5 million students in America, reports CBS News, "and the company said the number could triple after the 2025 numbers are tallied in about three months... Students in 35 states, including New York, Florida, Texas, California, Massachusetts and Georgia, now contend with laws or rules limiting phones and other electronic devices in school."

For example, The Yonkers School District purchased about 11,000 pouches, according to the article, "to comply with the statewide mandate that bans phones in classrooms." The pouch, which students carry with them, is locked and unlocked using magnets affixed to the entrance of the school and outside the main office... ["Some students have reported long lines and disruption at their schools," the article notes later, "as they wait to open their pouches." But on the first day of school at Yonkers, one student said the lines actually went pretty smoothly, and they ended up having a live conversation with a friend during lunch and "felt human"...] Other students were not so enthralled by the pouch; some reported seeing classmates bypass the Yondr pouch by using their Apple watches, buying "burner" phones and putting them in the pouch, breaking the pouch and other tricks to get to their phones.

[Yondr CEO Graham] Dugoni acknowledged that there will always be some students who can figure out how to get around the restrictions. The purpose of the pouches, he said, was to create a culture change in a school and create an environment conducive to their learning and development. More than 70% of high school teachers in the U.S. say cellphones are a major classroom distraction, according to the Pew Research Center Center.
Yondr CEO Graham Dugoni uses a flip phone, the article points out, and says "Our whole perspective is that it's not taking something away from students, it's giving them something back."

He says his larger mission is to create chances for people "to experience life outside of a fully digital realm" — and that Yondr now has school partners in all 50 U.S. states, and in 45 different countries: The cost of buying the pouches — roughly $25-30 per student — has set off debates around how schools should be spending their limited budgets. It's a particular issue for districts struggling with crumbling infrastructure, limited textbooks and access to other technology needed to learn...Districts in various states have reported spending from $26,000 to over $370,000, with Cincinnati Schools saying they spent $500,000 to provide pouches for students in grades 7-12.

"Some joyless ne'er-do-well has loosed a botnet on the community-driven Arch Linux distro," reports the Register, with a distributed denial of service (DDoS) attack that apparently started a week ago.

Arch maintainer Cristian Heusel announced Thursday on the project's web site that the attack "primarily impacts our main webpage, the Arch User Repository (AUR), and the Forums." We are aware of the problems that this creates for our end users and will continue to actively work with our hosting provider to mitigate the attack. We are also evaluating DDoS protection providers while carefully considering factors including cost, security, and ethical standards... As a volunteer-driven project, we appreciate the community's patience as our DevOps team works to resolve these issues.
A status update Friday acknowledged "we are suffering from partial outages." The Register reports: The attack comes as the project has been enjoying a boost in mainstream success. The distro was picked by Valve to underpin the SteamOS software running on its Steam Deck handheld gaming gadget, with the company providing the project with funding for further development. Late last year, a new version of the archinstall tool was released, with a view to making the system more friendly to newcomers...

For now, the Arch team is working to mitigate the attack's impact, which highlights a bootstrapping issue. Tools designed to shift traffic to mirrors in the event the main infrastructure is unavailable rely on a mirror list obtained from that same main infrastructure, with Heusel advising that users should "default to the mirrors listed in the pacman-mirrorlist package" if tools like reflector fail. Installation media can be downloaded from a range of mirrors, too, but should be checked against the project's official signing key before being trusted.

A new video shows flames emanating from one side of a Boeing 767 moments after takeoff, reports LiveMint.com. "Delta flight 446 was forced to make an emergency landing in Los Angeles," they report, adding "No one was injured. The fire was extinguished upon landing." According to a report by Aviation A2Z, the plane (24-year-old Boeing 767-400 with registration N836MH) had just departed from Los Angeles International Airport when its left engine ignited. The pilots promptly declared an emergency and requested to return to the airport.
Delta faced a similar issue less than three months ago. The article notes the engine of an Airbus also caught on fire in April when pushing back from the gate for departure. CBS News describes that incident: Delta said crew members evacuated the cabin when flames were seen in the tailpipe of one of the plane's two main engines and fire crews quickly responded. According to Delta, the plane, an Airbus 330, had 282 passengers, 10 flight attendants and two pilots on board...

The engine fire marks the latest aviation scare involving the airline in recent months. In February, 21 people were injured after a Delta plane flipped upside down while landing amid wintry conditions at Toronto Pearson International Airport. All of the injured passengers were later released from the hospital. In January, several people were injured after a Delta flight aborted its takeoff at Hartsfield-Jackson Atlanta International Airport, forcing about 200 passengers to evacuate the plane through emergency slides. ["A passenger says the engine on the Boeing 757 caught fire," according to CBS's video report in January.]

In Tokyo Mitsubishi is deploying "an innovative new battery swap network for electric cars" in a multi-year test program reports the EV news site Electrek.

But it's not just for electric cars. Along with the 14 modular battery swapping stations, Mitsubishi is also deploying "more than 150 battery-swappable commercial electric vehicles" from truck maker Fuso: A truck like the Mitsubishi eCanter typically requires a full night of AC charging to top off its batteries, and at least an hour or two on DC charging in Japan, according to Fuso. This joint pilot by Mitsubishi, Mitsubishi Fuso Trucks, and [EV battery swap specialist] Ample aims to circumvent this issue of forced downtime with its swappable batteries, supporting vehicle uptime by delivering a full charge within minutes.

The move is meant to encourage the transport industry's EV shift while creating a depository of stored energy that can be deployed to the grid in the event of a natural disaster — something Mitsubishi in Japan has been working on for years.
The article's author also adds their own opinion about battery-swapping technology. "When you see how simple it is to add hundreds of miles of driving in just 100 seconds — quicker, in many cases, than pumping a tank of liquid fuel into an ICE-powered car — you might come around, yourself."

A volunteer group called WikiPortraits is working to address Wikipedia's issue of featuring outdated and unflattering portraits by providing high-quality, openly licensed images. Since 2024, they have covered global festivals, taken thousands of images, and improved representation of underrepresented individuals, though challenges with funding and media credentials remain. 404 Media reports: This portrait problem stems from Wikipedia's mission to provide free reliable information. All media on the site must be openly licensed, so that anyone can use it free of charge. That, in turn, means that most photos of notable people on the site are of notably poor quality. "No professional photographers ever have their photos on Wikipedia, because they want to make money from the photos," said Jay Dixit, a writing professor and amateur Wikipedia photographer. "It's actually the norm that most celebrities have poor photos on Wikipedia, if they have photos at all. It's just some civilian at an airport being like, 'Oh my god, it's Pete Davidson,' click with an iPhone."

Dixit is part of a team of volunteer photographers, called WikiPortraits, that's trying to fix that problem. "It's been in the back of our minds for quite a while now," said Kevin Payravi, one of WikiPortraits' cofounders. "Last year, finally, we decided to make this a reality, and we got a couple of credentials for Sundance 2024 [a major film festival]. We sent a couple photographers there, we set up a portrait studio, and that was our first organized effort here in the U.S. to take good quality photos of people for Wikipedia."

Since last January, WikiPortraits photographers have covered around 10 global festivals and award ceremonies, and taken nearly 5,000 freely-licensed photos of celebrity attendees. And the celebrity attendees are often quite excited about it. [...] WikiPortraits photos are currently used on Wikipedia articles in over 120 languages, and they're viewed up to 80 million times per month from those pages alone. In January, for example, Payravi said that over 1,500 WikiPortraits photos were used on articles that collectively received 140 million views. Many WikiPortraits photos have also been used by a variety of news outlets around the world, including CNN Brasil, Times of Israel, and multiple non-English-language smaller news organizations. "[N]ot being an official news or photo agency means WikiPortraits sometimes faces problems getting media credentials to cover events," notes 404 Media. "Funding poses another main challenge."

"Photographers must already own a professional-quality camera, and usually have to cover the cost of getting to events and at least part of their lodging. Although WikiPortraits sometimes receives rapid grants from the Wikimedia Foundation and private donors to cover costs, Payravi said he still likes to run a 'tight ship.'"

"Thousands of buildings across the United States are staying cool with the help of cutting-edge batteries made from one of the world's simplest materials," reports the Washington Post — ice. When electricity is cheap, the batteries freeze water. When energy costs go up, building managers turn off their pricey chillers and use the ice to keep things cool. A typical building uses about a fifth of its electricity for cooling, according to the International Energy Agency. By shifting their energy use to cheaper times of day, the biggest buildings can save hundreds of thousands of dollars a year on their power bills. They can also avoid using electricity from the dirtiest fossil fuel plants. In places where the weather is hot and energy prices swing widely throughout the day — for instance, Texas, Southern California and most of the American Southwest — buildings could cut their power bills and carbon emissions by as much as a third, experts say...

When every building is blasting its air conditioner at the same moment on a hot day, power companies often fire up backup generators, known as peaker plants, which are generally extra pricey and polluting. If utilities avoid using peaker plants, they'll pollute less and save money. Last year, the Energy Department struck a tentative $306 million loan deal with the ice-battery-maker Nostromo Energy to install its systems in 193 California buildings to make energy cheaper and cleaner while lowering the state's blackout risk.
"The batteries themselves are huge..." the article acknowledges, citing one in New York City that uses 100 parking spot-sized tanks "which collectively make 3 million margaritas' worth of ice each night... But that's starting to change." (And they believe new smaller designs "could bring the batteries into smaller buildings and even houses.") Wherever they can squeeze into the market, ice batteries could be a cheaper and longer-lasting option than the lithium-ion batteries that power phones, cars and some buildings because their main ingredient is water, experts say. The pricey chemicals in a lithium-ion cell might degrade after 10 years, but water never wears out.
And according to the article, one company has already installed ice batteries in over 4,000 buildings...

An anonymous reader quotes a report from Ars Technica: What exactly is wrong with the batteries in some of Google's Pixel 4a phones still out there? Google has not really said. Now that many Pixel 4a owners are experiencing drastically reduced battery life after an uncommon update for an end-of-life phone, they are facing a strange array of options with no path back to the phone they had.

Google's "Pixel 4a Battery Performance Program," announced in early January, told owners that an automatic update would, for some "Impacted Devices," reduce their battery's runtime and charging performance. "Impacted" customers could choose, within one year's time, between three "appeasement" options: sending in the phone for a battery replacement, getting $50 or the equivalent in their location, or receiving $100 in credit in the Google Store toward a new Pixel phone. No safety or hazard issue was mentioned in the support document.

Google did not explain why only certain devices were affected, but Hector Martin -- of Asahi Linux on Apple silicon, open source Kinect drivers, and other fame -- took apart the update's binary kernel and has some guesses. Martin points out that the updated Pixel 4a kernel has these interesting characteristics:

- It seems to have been built by a Google engineer "on their personal machine, not the proper buildsystem."
-- There is no source provided, as would normally be required of a Linux kernel build, though it may only need to be provided on request under the GNU General Public License.
- The maximum charge voltage of certain battery profiles changes from 4.44 volts to 3.95, which would mean batteries cannot charge to anywhere near their former potential.
- There are two main battery profiles, with distinct "ATL" and "LSN" markers; Martin suggests they relate to Amperex Technology Limited and Lishen, manufacturers of battery cells.
- LSN-tagged batteries assigned the "debug" profile can see capacity reduced from 3,080 milliamp hours (mAh) to 1,539 mAh. The big question is why Google pushed an automatic update to a phone from 2020. "No news or community reports have surfaced yet of Pixel 4a devices causing fires, or even simply failing to function, after four years," writes Ars' Kevin Purdy. "It's an automatic update with a strong fix, but for what?"

Google's support page only states that the update will "improve the stability of their battery's performance."

An anonymous reader shared this report from TechCrunch: The developer behind Pixelfed, Loops, and Sup, open source alternatives to Instagram, TikTok, and WhatsApp, respectively, is now raising funds on Kickstarter to fuel the apps' further development. The trio is part of the growing open social web, also known as the fediverse, powered by the same ActivityPub protocol used by X alternative Mastodon... [and] challenge Meta's social media empire... "Help us put control back into the hands of the people!" [Daniel Supernault, the Canadian-based developer behind the federated apps] said in a post on Mastodon where he announced the Kickstarter's Thursday launch.

As of the time of writing, the campaign has raised $58,383 so far. While the goal on the Kickstarter site has been surpassed, Supernault said that he hopes to raise $1 million or more so he can hire a small team... A fourth project, PubKit, is also a part of these efforts, offering a toolset to support developers building in the fediverse... The stretch goal of the Kickstarter campaign is to register the Pixelfed Foundation as a not-for-profit and grow its team beyond volunteers. This could help address the issue with Supernault being a single point of failure for the project... Mastodon CEO Eugen Rochko made a similar decision earlier this month to transition to a nonprofit structure. If successful, the campaign would also fund a blogging app as an alternative to Tumblr or LiveJournal at some point in the future.

The funds will also help the apps manage the influx of new users. On Pixelfed.social, the main Pixelfed instance, (like Mastodon, anyone can run a Pixelfed server), there are now more than 200,000 users, thanks in part to the mobile app's launch, according to the campaign details shared with TechCrunch. The server is also now the second-largest in the fediverse, behind only Mastodon.social, according to network statistics from FediDB. New funds will help expand the storage, CDNs, and compute power needed for the growing user base and accelerate development. In addition, they'll help Supernault dedicate more of his time to the apps and the fediverse as a whole while also expanding the moderation, security, privacy, and safety programs that social apps need.

As a part of its efforts, Supernault also wants to introduce E2E encryption to the fediverse.
The Kickstarter campaign promises "authentic sharing reimagined," calling the apps "Beautiful sharing platforms that puts you first. No ads, no algorithms, no tracking — just pure photography and authentic connections... More Privacy, More Safety. More Variety. " Pixelfed/Loops/Sup/Pubkit isn't a ambitious dream or vaporware — they're here today — and we need your support to continue our mission and shoot for the moon to be the best social communication platform in the world.... We're following the both the Digital Platform Charter of Rights & Ethical Web Principles of the W3C for all of our projects as guidelines to building platforms that help people and provide a positive social benefit.
The campaign's page says they're building "a future where social networking respects your privacy, values your freedom, and prioritizes your safety."