Stories
Slash Boxes
Comments

SoylentNews is people

SoylentNews is powered by your submissions, so send in your scoop. Only 12 submissions in the queue.

Log In

Log In

Create Account  |  Retrieve Password


Site News

Join our Folding@Home team:
Main F@H site
Our team page


Funding Goal
For 6-month period:
2022-07-01 to 2022-12-31
(All amounts are estimated)
Base Goal:
$3500.00

Currently:
$438.92

12.5%

Covers transactions:
2022-07-02 10:17:28 ..
2022-10-05 12:33:58 UTC
(SPIDs: [1838..1866])
Last Update:
2022-10-05 14:04:11 UTC --fnord666

Support us: Subscribe Here
and buy SoylentNews Swag


We always have a place for talented people, visit the Get Involved section on the wiki to see how you can make SoylentNews better.

When was the last time you compiled an operating system kernel?

  • This morning---I live on the unstable nightly build!
  • Every time a major release comes out
  • Whenever my distro does it for me
  • Last century
  • That one time when I was in college and I was experimenting
  • Never
  • What's a kernel?
  • Other (describe in the comments)

[ Results | Polls ]
Comments:55 | Votes:145

posted by mrcoolbp on Monday August 17, @07:49PM   Printer-friendly

If the Markets Reject OpenAI and Anthropic, the US Should Nationalize Them:

This essay was written with Nathan E. Sanders, and originally appeared in The Guardian .

If the Markets Reject OpenAI and Anthropic, the US Should Nationalize Them

OpenAI, and then Anthropic , were each formed by AI developers who feared unrestrained corporate AI development—specifically, that companies like Google and Meta would steer the technology towards deleterious, maybe even catastrophically unsafe, outcomes for society. Their founders proclaimed that their new labs, uniquely, could be trusted to develop the technology in humanity's best interest. But each, in turn, were themselves co-opted by the same market incentives, themselves becoming corporate behemoths zealously guarding future investor value rather than the public interest.

It was only a few weeks ago, in June, when OpenAI and Anthropic each filed for their IPOs and were met with buzz about trillion-dollar valuations. The hype around their valuations is so extreme that many worry about their potential for concentrating wealth on a global scale. In an effort to leave something for the rest of us, some observers have proposed that the federal government seize a share of these companies' stock to create a US sovereign wealth fund , or redistribute their revenues to produce a dividend for taxpayers.

Now the headlines are about public backlash to AI datacenters and the AI chip giant Nvidia's slumping stock. The tech and AI giant SpaceX's newly minted stock price tanked just weeks after its IPO. There are even questions about whether the leading AI labs will ever be sustainably profitable . All of a sudden, the makers of ChatGPT and Claude face strong headwinds as they seek to generate the massive equity assets that once felt all but assured.

In fact, evidence suggests the market itself could reassess that these companies offer nothing of financial value. In that case, perhaps we can return them both to their original purposes. If these AI companies should fail in the financial markets, the US should nationalize them and convert them into national labs operated under democratic control that preserve their benefit to the public interest.

The economics of the big AI labs hardly guarantee a booming return on investment. Frontier AI models are both expensive to train and depreciate within months, when a newer model appears. This means that the payback window to extract profit from them is very narrow. Meanwhile, enterprise clients are getting smart about minimizing AI token usage. Even worse, the models are basically commodities; the best ones largely perform and behave similarly, which depresses prices. Perhaps most importantly, open-source and Chinese competitors— lagging only a few months behind the leading labs in capability—give away for free the kinds of models Anthropic and OpenAI sell.

Even setting aside the model training costs, it's not clear whether the unit economics of AI as it's currently conceived will ever be sustainably profitable. Many of these free and open-source models can be run locally: the large ones on private clouds and high-end servers, the smaller ones on anyone's laptop or even cellphone, putting to question the companies' exorbitant capital investment in datacenters.

It's not that OpenAI and Anthropic are not valuable as organizations. They have remarkably talented AI scientists and engineers that are continuously producing innovations driving a global mania for their offerings. These leading labs might not ever be profitable, but their products are doing a lot of good in the world. You may or may not be a user of or believer in their technology, but their staggering, ongoing usage growth suggests that an awful lot of people would be disappointed if the companies simply disappeared.

The problem isn't the people or the products, it's the system. As constituted, OpenAI and Anthropic may not be valuable as market equities. If the market assesses they are not capable of producing a growing financial return on investment for shareholders, the companies will collapse.

Maybe private, for-profit is just not the right economic model under which to develop AI. Perhaps OpenAI should be returned to its private non-profit roots, the legacy they fought so hard to change and which Anthropic's founders spurned . Or possibly both could be reorganized as research centers at universities, returning to academia the scores of high-profile research faculty they have poached .

But a better outcome for society would be to establish public ownership and operation of their product-oriented capabilities. Turn OpenAI and Anthropic into US government agencies producing AI as a public good.

Transitioning the big AI labs into public agencies would require some restructuring. We can separate these companies into two pieces: product innovation and compute operations. The innovation function can be publicly managed, akin to national labs. Congress could provide more rigorous oversight than the kind of unfettered venture capital these labs have recently had access to. The US has a long, successful history of these kinds of institutions, which have produced world-shaping innovations in spaceflight, telecommunications, nuclear power and more. Congress currently manages a $200bn R&D portfolio , within which frontier AI development is, arguably, a glaring gap.

AI operations could be managed as a commodity resource, like public electrical or water utilities: local or regional ownership, nationwide distribution and strict regulation on how they balance fee extraction from ratepayers with raising capital for infrastructure investment. Although AI datacenters are not the same as power or water treatment plants, the US also has a long history of managing national, regional and state supercomputing centers.

Other countries, including Switzerland , Spain and Singapore , are already operating public AI labs. They also have national supercomputing centers already providing public access for running AI models for general use, as do Germany and Australia.

The benefits to the public are clear. Through democratic oversight, the most important AI models could become open, transparent and responsive to the demands of the public rather than private shareholders. They could be aligned to democratic values rather than corporate profits, never taking advertiser money to promote certain brands and training on only appropriately licensed data. And they could be set to focus on the realistic and pro-social goal of maximizing the usefulness of AI to society rather than the fanciful and anti-social goal of supplanting humans with artificial general intelligence.

By emphasizing scientific cooperation rather than corporate competition, we could also reduce the overall resource and environmental cost associated with AI. Instead of perpetually dueling training runs of each companies' models at ever large scales targeted to fuel investor hype, we could limit AI training resources based on cost and benefit to the public.

What's in it for the companies themselves and their employees, who sacrifice hypothetical billions in equity by ceding to public ownership? A return to their roots and to their core mission of developing AI safely in the public interest, if they are serious about it. Both companies are theoretically bound through their governance structures to prioritize mission over profit anyway (not that anyone really thinks that's how they currently operate).

To be clear, we're not advocating for a golden parachute for the executives or investors, or for continuing the outlandish pay rates of the most highly remunerated AI researchers. If the public is footing the bill, these compensation packages should be aligned to the civil service and those employees not satisfied with that can go elsewhere—if the business models of any remaining private labs still support much higher pay.

While we believe that these companies are unsustainable as private firms, the timeline remains unclear. Their primary investor story is that AI is a race to "artificial general intelligence"—the kind of AI you're used to from science fiction. The bet seems to be that the two companies can convince enough people that this outcome will turn them a profit, go public, and then make their investors and employees rich before the bubble bursts.

But suppose that the bubble bursts. If the US is smart, it will catch the companies as they fall. Regardless of what the markets think, to the public, they're too valuable to let die.


Original Submission

posted by jelizondo on Monday August 17, @03:12PM   Printer-friendly

https://www.zdnet.com/article/linux-desktop-use-surged-on-one-workday-cloudflare-data-shows/

Web traffic analysis site StatCounter recently showed that desktop Linux had reached an all-time high of 10.65% in the North American desktop market. Many people, even many Linux fans, dismissed this proportion as fake news. However, the last time I looked at the numbers in 2025, Statcounter only showed a high of just over 5%. As I mentioned in my recent report, Linux doubling its market share in just over a year should get everyone's attention.

I dug deeper and found that data from popular content delivery network Cloudflare also showed that the Linux desktop has been gaining popularity. By its count, desktop Linux has now reached 6.4%. That proportion is not as high as StatCounter's, but it represents significant growth given that Linux accounted for 4.1% of North American operating systems for the same period last year.

Cloudflare's dataset is much larger than StatCounter's. StatCounter monitors about a million websites, while Cloudflare keeps an eye on over 24 million websites. Cloudflare itself claims to cover about 20% of the web

A deeper look also reveals that desktop Linux use tends to peak during the work week. For example, believe it or not, on Monday, 6 July, when people were back after the 4 July holiday, Linux usage jumped to a high of 22%. 

The users of these systems are not AI agents or bots, but real people. I set Cloudflare to count humans rather than bots. If you include people and bots, Linux has a 9.7% market share. That proportion is similar to StatCounter's score. By Cloudflare's count, bots alone come to 19%.

These numbers tell us that workers are leading the way to the Linux desktop. That result is not surprising. Historically, they're people who prefer control over their PCs, like open systems, or have a specific workload, such as programming or system administration, where Linux works well. 

Microsoft has long known this requirement. Windows Subsystem for Linux (WSL), for example, is designed for Windows developers who also need Linux's power and tools. It's been years since Microsoft released WSL user numbers, but in 2020, there were 3.5 million WSL users

However, past performance doesn't explain present trends. So, why are we now seeing such a bump in Linux desktop growth?  Experts believe this trend is largely AI developers and Linux users running AI Agents. 

For example, as David Linthicum, former managing director and chief cloud strategy officer at Deloitte Consulting and AI and cloud influencer, recently observed, while "Windows 11 can technically run local AI workloads, but as you begin using multiple tools, managing different projects, and installing various dependencies, the friction starts to build," it's a different story for Linux users.

Linthicum continued: "Linux delivered what I can only describe as a true 'AI desktop' experience. Setup was straightforward, mainstream AI instructions matched what you'd actually see in your environment, and GPU-accelerated apps simply worked -- consistently. I spent far less time troubleshooting and far more time actually executing on projects."

As for agents, Linux Foundation CEO Jim Zemlin summed up their role succinctly: "Linux is the OS of choice for AI agents.

There are other reasons why desktop Linux is finally picking up popularity, including:

  • Dislike for Windows 11: Even Windows fans like ZDNET's Ed Bott are finding lots to dislike about Windows 11. Adding salt to the wound, Windows 10 is out of support.
  • Many Windows 10 PCs can't be "upgraded" to Windows 11: There are ways to move some Windows 10 PCs to Windows 11, but that still leaves millions of computers that can't make the shift. For these machines, Linux is the way to keep them useful.
  • Linux is easy to use: Enough of the "Linux is so hard!" nonsense. You don't need to be a shell command expert. Many Linux distros are easy for Windows users to pick up. These include my own favorite, Linux Mint; my fellow ZDNET Linux fan Jack Wallen's fave, Zorin OS; and the looks-like Windows VailuxOS distro.
  • Linux gaming has come of age: Gaming has never been Linux's best point, but thanks to Steam, Linux is now a more significant gaming platform. While Linux remains a niche player in the broader PC gaming market, its share is higher than ever and growing slowly.
  • Installing Linux desktop software is easy: Can you install an app on your Android phone or iPhone? Yes? Congrats, you can install programs on Linux. App stores are now the default way to install software on desktop Linux. You may not need to, though, as Bott pointed out in his Linux experiment for ZDNET: "All of my basic productivity apps -- 1Password, Obsidian, and even Microsoft Edge -- were easy enough to install, and I had no trouble using my cloud-based Office files in Edge on Linux."

Original Submission

posted by jelizondo on Monday August 17, @05:49AM   Printer-friendly

When it comes to recording, tracking, and storing data, the concept of "permanence" can be a lot trickier than you'd expect:

More and more, our data—private photos, work documents, confidential information, and so on—are migrating to digital clouds and platforms. In a more recent and perhaps controversial turn of events, some gaming firms are pushing for digital downloads in lieu of physical CDs.

One recurring argument against digital options has been that it's not as "permanent" as their physical counterparts. After all, aren't physical storage systems safer from the whims of a tech firm wiping your cloud storage—or, even worse, forcing you to choose a subscription plan?

But CDs break. Books burn. USBs go defunct. Personally, I—a stickler for physical media—have a very bad track record of breaking my game chips and scratching my movie discs. There are real challenges in dealing with physical storage systems, too, and big players like Microsoft are investing significant resources to overcome the inevitable decay caused by, well, the passage of time.

[...] The following responses may have been lightly edited for length and clarity.

Mohiuddin Ahmed, Computer scientist, Adelaide University, Australia.

Data storage is a contextual matter. Given the transient nature of everything around us, permanent data storage is some sort of a myth at this stage. That said, multiple copies of data and moving them to a new storage every couple of years can be thought of as a practical solution toward permanent data storage.

Francesca Musiani, Research director, Center for Internet and Society at the National Center for Scientific Research, France.

I find the idea of "permanent" data storage quite elusive, not only in our digital "era." Every medium we have ever invented eventually fails, from stone inscriptions that erode to paper burning, CDs' "disc rot" and solid-state drives that gradually lose stored charge. Further, even if a storage medium could survive for centuries, the devices and software needed to read it may not; a perfectly preserved floppy disk is of little use if no one can build or maintain a compatible drive. In this sense, data loss is a techno-historical problem, I would say: preserving information requires preserving the means of interpreting it.

[...]

Jack Cushman, Director, Library Innovation Lab at Harvard Law School; creator of the Public Data Project.

I know of one data storage form that can be permanent: a library. Or rather, a world full of libraries. Libraries aren't perfect storage devices (nothing is), but they are fiercely committed to self-repair. A good library is a collection of people, technologies, and practices that pass an obligation—to remember the things we must remember—from the last generation to the next.

Libraries, rather than better hard drives, are what solve correlated failure, cataloged in the LOCKSS (Lots Of Copies Keep Stuff Safe) threat model. A correlated failure is when you make really great, durable copies of the data you care about, and then they all get hit by an asteroid. Shouldn't have had them all in one physical location. Or a hacker marks them all for deletion (they were all behind one sysadmin), or a government orders them all destroyed (all in one regulatory regime), or they all rot at the same time (all from one flawed batch), or the money to store them dries up (all on one funding source).

On a long enough timeline any copy will break. You need multiple copies with different vulnerabilities so they don't all break at the same time. Then you need to repair the broken ones. A worldwide network of libraries does the repair work, whether the objects are 30 medieval Magna Carta manuscripts or 300,000 government datasets.

[...]

Kevin Curran, Computer scientist and cybersecurity researcher, Ulster University, U.K.

No form of digital storage media is truly reliable for passive, long-term archival use. Entropy eventually wins, failures occur faster than expected, and the only practical solution is active management—periodic verification, rewriting data, and maintaining multiple redundant copies on fresh media. The most common form of storage which is hard drives—should not be viewed as archival media. Hard drives should be treated as consumables.

A recent Iron Mountain report highlighted that one-fifth of 1990s era hard drives sent to them were entirely unreadable, even under ideal storage conditions. Quite simply, standard hard drives were not designed for long-term archival use. You can never decouple the magnetic disks from the reading hardware inside so if either fails, then the whole drive dies. Hard drives magnetic charge fades over time, bearings seize, and there is often no partial recovery option. There are methods to try to combat this such as periodic full rewrites to refresh the magnetic domains but how many would ever do this?

[...]

Adnene Guabtni, Principal research scientist, Commonwealth Scientific and Industrial Research Organisation, Australia.

Data loss, whether from hardware failure, natural disaster, cyberattack, human error, or simply a discontinued cloud service, has plagued computing since its inception. Solving it requires a multi-faceted approach combining data replication and distribution, decentralization, and data sovereignty. First, data replication and distribution across multiple cloud storage services reduces the risk of data loss from a single point of failure. This approach costs more, since the user must subscribe to multiple providers. Yet, it doesn't protect against a global outage or a coordinated cyberattack affecting several providers at once.

[...]

Melanie Hubbard, Head of Digital Scholarship & Data Services, Boston College Libraries

When we talk about data these days, we typically mean data that is born-digital or digitized. It is the digital aspect that adds to its instability, though it is also what makes it more discoverable, accessible, usable, and manageable. From the moment something is made digital, it becomes harder to grasp, like sand sifting through fingers, as the risks of degradation, context loss, format obsolescence, container vulnerability, and shifting technology loom. For instance, I can't plug in a FireWire drive or load a CD directly on my laptop anymore. I can plug in my USB drive, but the data is corrupted.

The closest we come to data permanence is when it is in a pure analog format, such as books, punchcards, and stone tablets, but these are not practical for data storage and access at scale, and analog offers no guarantees. After all, ancient libraries stand in ruins today, if they stand at all. And even when technological limitations don't cause data loss, there are always the risks posed by politics, corporate greed, the laws of thermodynamics, or natural disaster.


Original Submission

posted by jelizondo on Monday August 17, @12:59AM   Printer-friendly

https://ludens.cl/photo/spectra/spectra.html

The biggest lie in color photography is that you can accurately represent the colors of objects by simply recording the amount of red, green and blue in them. This technique - the only one in current mainstream use - gives good results only when the spectral sensitivity curves of the camera precisely match those of the human eye, and when the spectrum of the light used to make the photo is perfectly smooth, and no different kind of light will ever be used!

It's clear that the first of these requirements is hard enough to meet, and that the second one is, simply and plainly, never true.

And that's why photographers are always battling to get the right colors - and never do get them!

Not only in photography is this matter an important one. In daily life it is, too. Lots of electronic technicians hate that stupid problem of not being able to correctly read resistors. It happens that old-style resistors, and some other parts too, are labelled with color bands or dots, instead of numbers. Under some lighting conditions it can be hard to tell a red from an orange, or a green from a blue. This leads to the wrong resistors being installed in equipment, and thus more troubleshooting work.


Original Submission

posted by mrcoolbp on Sunday August 16, @08:11PM   Printer-friendly

Firefox says it will keep supporting uBlock Origin even as Microsoft Edge and other Chromium browsers phase it out under Manifest V3:

Firefox recently announced via Bluesky post: "Our support for uBlock Origin isn't going anywhere." The moment comes in response to news that Microsoft Edge is soon going to lock out uBlock Origin and other ad-blocking extensions that run on Manifest V2 architecture.

Once Microsoft Edge moves to Manifest V3, ad-blocking extensions won't have access to the functions needed to properly identify and block ads that occur while browsing websites and watching videos.

Microsoft's move isn't surprising, as Edge is based on Chromium, the open-source browser engine that powers most web browsers today, including Opera, Brave, Vivaldi, and Samsung Browser. Google initiated the migration from Manifest V2 to V3 in Chrome/Chromium, and Microsoft Edge is now following Google's lead.

But Firefox is one of the few web browsers remaining that isn't based on Chromium, and it's now the only major browser to still support uBlock Origin. Neither Safari nor DuckDuckGo—the two other major non-Chromium browsers out there—support uBlock Origin.

For die-hard uBlock Origin fans, Firefox appears to be the only browser left without compromises. With any other browser, you'll need to settle for uBlock Origin Lite (with fewer features and less ad-blocking success) or whatever built-in ad-blocking feature comes with the browser.


Original Submission

posted by hubie on Sunday August 16, @03:27PM   Printer-friendly
from the free-as-in-you-need-to-have-a-Cloudflare-subscription dept.

Cloudflare built an AI agent workspace for its employees. Now it's open source:

Cloudflare has open-sourced its Cloudflare OS platform, which it first developed as an internal workspace for employees to build apps using AI agents—including people who are not software developers or engineers. The company also touts a security framework designed to reduce the risk of employee vibe-coding sessions creating serious security flaws or leading to data breaches.

The tech company spent several months building and internally testing Cloudflare OS, which allows employees to describe workflows in natural language so that an AI agent can code them into applications. In an August 5 blog post announcing the open source version's availability on GitHub, the company claims thousands of Cloudflare employees use the platform on a daily basis to "create documents and slides, automate repeatable tasks, and build small apps to visualize data and help them do their work."

"This is a full-on personal app vibe coding platform, in which the sandbox is so secure that you can pretty much go wild—the AI cannot introduce a significant security bug," said Kenton Varda, principal engineer at Cloudflare, in a post on the social media platform X. "We believe a company's security team can feel comfortable giving non-technical users permission to vibe code and then sleep soundly at night."

The security model relies on creating fine-grained app instances so that a document editor app would run each document as a separate instance in a separate sandbox, Varda explained. The Cloudflare OS platform manages who has permission to access each instance, and each individual runs their own copy of the code that they can freely modify.

[...] Cloudflare OS can work with just about any AI model and allows organizations to select the most suitable model for the job at hand. "Not every user needs access to the max thinking mode of the latest frontier lab model," said Sam Rhea, chief information officer at Cloudflare, in a separate blog post. "And we do not need team members spending $20 to summarize their email inbox every hour."

[...] Cloudflare shared some hard lessons learned along the way as it tried to ensure the efficient use of AI tools through Cloudflare OS. One early mistake involved simply giving everyone outside the engineering team "the same tools with slightly friendlier user interfaces" because the AI coding harnesses that engineers typically use are less suitable for knowledge work involving "one-off outputs and work on projects that involve dozens of systems of record," Rhea explained.

"If you give everyone a harness workspace that is great at writing code, you'll wind up with way more code than you need," Rhea wrote in his blog post. "The result became a flood of vibe coded apps looking for a problem to solve."

The growing use of AI agents within the organization also meant "anyone at Cloudflare could now write bad code, faster, thanks to AI," Rhea said. So the organization created the Cloudflare Engineering Codex, an "authoritative guide" to help both human engineers and AI agents review code and catch potential issues.

[...] Now that the company is open-sourcing Cloudflare OS for others to use, developers can try to run the entire stack on their own machines. A notable caveat is that the Cloudflare OS backend can only be deployed by Cloudflare users who have subscribed to the Workers Paid plan.

The paid subscription requirement was not initially made clear up front. A GitHub user raised the issue and shared a screenshot showing that their Workers Free plan had been stopped from deploying the Cloudflare OS backend partway through the process.

"You have a right to charge but requirements should be completed before starting the deployment process," wrote the GitHub user mac2net. "I wasted 20 minutes I will never get back."


Original Submission

posted by hubie on Sunday August 16, @10:40AM   Printer-friendly
from the pet-peeved dept.

Owners of Petlibro pet feeders have "service issue" that prevents feeding of the pets. If you can't even bother to feed your own pet? Why do you have them? Also if we can't even depend on the machines to feed pets how are we depending on them to do other more important things. But why do you need cloud access to set a schedule to feed a pet? Or that is to say to open a tray so the pet in question can access the food. As it was when it was not opening it was mocking or taunting the pet with food it could not access.

Pets should now be on their normal feeding schedule again ... Perhaps the service issue was just there to put some of the furries on a diet.

Petlibro says it's working to resolve a 'service issue' that's causing its smart feeders not to dispense food on schedule.

Smart pet-feeder company Petlibro suffered an outage on Tuesday, giving users a harsh reminder of the risks of relying on smart devices.

https://www.theverge.com/tech/979295/petlibro-outage-smart-pet-feeders
https://arstechnica.com/gadgets/2026/08/pet-owners-say-smart-pet-feeder-outage-led-to-furry-ones-going-unfed/


Original Submission

posted by hubie on Sunday August 16, @05:57AM   Printer-friendly
from the Yes,-but,-Meta? dept.

Meta's recent open-weight release of Muse Glimmer 30B has re-ignited the debate over whether locally hosted models can replace subscription-based cloud APIs like Claude 3.5 Sonnet, GPT-4o, and Gemini 2.0 Pro. But what does it actually take in terms of silicon, power draw, and real-world performance to run Meta's latest agentic model at best capacity?

To run Muse Glimmer 30B at "best capacity"—meaning unquantized (FP16) or high-precision 8-bit (FP8/Q8_0) with its full 131,072-token context window loaded into VRAM alongside the DFlash speculative decoder—hardware requirements land between 48 GB and 64 GB of VRAM. A dual NVIDIA RTX 5090 workstation (~64 GB VRAM) requires an initial hardware investment of roughly $4,500–$6,000, while an Apple Mac Studio (128 GB Unified Memory) costs around $3,800–$4,800.

The operational energy divergence between PC rigs and Apple Silicon is substantial:

  • Dual-NVIDIA Workstation (750W Peak): Under heavy 8-hour daily agent workloads, power costs average ~$35/month ($420/year). Continuous 24/7 background operation increases power costs to ~$86/month ($1,036/year).
  • Apple Silicon Mac Studio (130W Peak): Under the same 8-hour daily workload, power costs average ~$5.90/month ($71/year), or ~$15/month for continuous 24/7 agent loops—yielding an 80%+ energy reduction over PC GPU setups.

In terms of capability, Muse Glimmer 30B holds its ground surprisingly well against mega-parameter cloud models:

                        Benchmark / Workload
                        Muse Glimmer 30B (Local)
                        Claude 3.5 Sonnet (Cloud)
                        GPT-4o / o3-mini (Cloud)

                        SWE-bench Verified (Coding)
                        76.0
                        49.0
                        70.5 (o3-mini)

                        MCP Atlas (Tool Use)
                        75.5
                        81.2
                        80.0

                        DeepSearch QA (Research)
                        74.6
                        82.0
                        84.1

                        AIME 2026 (Math/Logic)
                        94.7
                        78.3
                        91.0

The Verdict: While frontier cloud models like Claude 3.5 Sonnet and Gemini 2.0 Pro maintain a clear lead in complex architectural design and massive context capacity (up to 2M tokens), Muse Glimmer 30B dominates in privacy, zero token costs, and low-latency local agent execution. For software developers and privacy-conscious users running 24/7 personal assistants, local hardware offers a compelling alternative to continuous cloud API fees.

Model weights and GGUF quantizations are currently available via Hugging Face under the Apache 2.0 license.

------

I'd call 3.5 Sonnet a bit of a strawman, over a year old, but still an impressive target to match locally, privately, at those prices.


Original Submission

posted by hubie on Sunday August 16, @01:12AM   Printer-friendly

AI-assisted research only used 20 prompts to find an exploit to hack hundreds of millions of people:

Critical 'Zoomsday' Flaw Enables Total Device Takeover During Zoom Calls — AI-Assisted Research Only Used 20 Prompts To Find An Exploit To Hack Hundreds Of Millions Of People.

The team claims it cooked the exploit with merely 20 prompts to an AI agent. The exploitable area is substantial, as recent estimates pin Zoom's monthly active users at around 220 million and an estimated 56% of the global conferencing market share.

With the exploit, the attacker was able to get full remote code execution, meaning they could effectively control the user's computer and their data — invisibly, to boot. Zoom isn't an application that runs with administrator privileges, so kernel-level rootkits are off the menu, but once you have the user's data, it's not like you need much else. Plus, it's easy to gain exploit persistence any number of other ways.

A.Security says a small team developed this exploit with a mere 20 prompts to an AI agent — pointing out how easy it was to come up with a nation-state-class vulnerability with meager resources. While the majority of AI-assisted vulnerability research focuses on open-source software or applications with published communications protocols or file formats, Zoom is fully proprietary, and it was still easily cracked open.

The firm further noted that "the model requiring elite teams, months of effort, and weapons-grade budgets has collapsed," and that "the barrier that kept these weapons scarce has collapsed, and it will not come back" — basically repeating what every security researcher has been yelling from the top of their lungs for the past year or so.

The vulnerability itself is, rather unsurprisingly, a buffer overrun: the program fails to check that an input is the right size, so you can push more data than it expects and overwrite part of the following memory with code that will be executed.

First, the scientists decompiled the Android package and asked an AI agent to rank the potential attack surfaces to relatively little success. They then turned their attention to the communications protocol. They found that the code library handling annotations received each object (rectangles, text, etc.) in serialized form, with count fields telling the recipient how much data to read next.

Crucially, they found that the code handling these reads didn't have a boundary check for maximum size, meaning one could simply lie about it and send a chunk of data that's too large and padded with exploit code at the end, as Norman Stansfield would say, bin-go!


Original Submission

posted by hubie on Saturday August 15, @08:25PM   Printer-friendly

https://science.nasa.gov/missions/chandra/nasa-telescopes-create-colorful-craft-from-nearby-nebula/:

Like a collage made of layered sheets of colored cellophane, a vibrant new image layers observations of a famous star-forming nebula from NASA space telescopes. The resulting cosmic "craft" reveals new details about the star formation region known as 30 Doradus, or the Tarantula Nebula.

Located in the Large Magellanic Cloud, a small neighbor galaxy to the Milky Way about 160,000 light-years from Earth, the Tarantula has thousands of young stars embedded in a vibrant honeycomb-like structure of gas and dust.

NASA Tarantula image

The new composite image contains X-rays from NASA's Chandra X-ray Observatory, which has repeatedly observed the Tarantula Nebula over the course of its mission, in the layer that appears in blue. The X-ray data reveals gas blown away by winds from the surfaces of young, massive stars and heated to millions of degrees by shock waves, like sonic booms from supersonic jets.

The red represents infrared data from NASA's James Webb Space Telescope showing thousands of young stars, plus swaths of cool dust that will provide the ingredients to form new stars and planets. Optical data in the green layer from NASA's Hubble Space Telescope uncovers hydrogen gas that is warmer than seen with Webb, as well as some individual stars through the nebula.

The composite image shows the full Hubble and Webb images of this region, as well as a large section of the Chandra image, all recently published in a research paper in the Astrophysical Journal. In some regions the blue Chandra layer stands alone, and in others it combines with either the red Webb data or the green Hubble data. In the middle region all three images overlap to provide a holistic view in red, orange, yellow, green, and blue.

Previously, astronomers had studied the amount and the impact of energy produced by winds from young, massive stars in the Tarantula Nebula. Scientists expect that much of this energy should heat gas so that it produces X-rays. However, the research paper shows that there is much less X-ray-emitting gas in the nebula than expected. This led researchers to ask: Where has this energy gone and what tamed the Tarantula Nebula?

By studying the data from Chandra, Hubble, and Webb, combined with data from NASA's retired Spitzer Space Telescope, the team concluded the Tarantula may be losing energy from several sources.

First, up to half of the hot gas is leaking through the shell walls of the gas and dust structures and escaping the nebula. Next, there is stirring and mixing between the cold gas near the shell walls and some of the hot gas, lowering the overall temperature of the gas. Finally, comparisons with computer simulations suggest the Tarantula may be losing energy through conduction. This involves direct physical contact between hot and cooler material, like with a frying pan on a burner, causing the hot and cooler material to equalize in temperature. In the case of the Tarantula Nebula, the hot gas would be conducting heat by being in direct contact with the cooler gas in the shells, especially in the densest regions. This scenario does not necessarily involve mixing the hot and cooler gas.

The combination of these three channels for losing large amounts of energy leads to this colorful and complex display revealed by NASA's telescopes working together.

Second NASA Tarantula image

Journal Reference: Jennifer A. Rodriguez et al 2026 ApJ 998 318 DOI 10.3847/1538-4357/ae3c7a


Original Submission

posted by hubie on Saturday August 15, @03:44PM   Printer-friendly
from the Blue-Pill-Forever dept.

Arizona State University is introducing a degree in Content Creation. This is not an April fool's joke or a hoax.

The degree will teach the craft of influencing and online content creation which will include lessons on creating powerful content across video, podcasts, analytics, and social media strategy.

Online comments in response to this announceent have included "F**k. This. Timeline." and "Just imagine explaining to someone that your homework is 'go viral'".

Classes start this October.


Original Submission

posted by hubie on Saturday August 15, @10:56AM   Printer-friendly
from the yeah-well-I'm-gonna-build-my-own-chips-with-blackjack-and-hookers dept.

Anthropic and OpenAI are racing to scale up while reducing dependence on Nvidia:

Anthropic is hiring a "custom silicon team" to design chips on which to run its models, the company has revealed.

Yesterday, Business Insider noticed a job listing for a senior engineer with experience shipping semiconductor designs. (You can see listings for a silicon engineer and a technical program manager, silicon on Anthropic's job board right now.) A spokesperson for Anthropic then confirmed the plans to both Business Insider and TechCrunch.

The spokesperson clarified that Anthropic will still take a "multi-chip approach," with plans to use hardware from other companies alongside its own designs as it continues to scale up.

This is confirmation of a rumor that has been circulating for a little bit; The Information previously reported that Anthropic was considering working with Samsung as a hardware manufacturing partner.

Anthropic is not alone in walking this path. Its competitor, OpenAI, recently announced a new custom chip called Jalapeño designed for large language model inference in data centers. OpenAI partnered with Broadcom to develop the chip. Google has been running its models on its own hardware for a while; Meta has also designed and deployed its own chips, and Mistral is reportedly looking into doing the same.

There are a few reasons AI providers are doing this. First, much of the industry is heavily reliant on Nvidia for the hardware the companies' models run on, and Nvidia's continued leverage there is a potential strategic vulnerability, especially as AI companies operate in an environment where compute infrastructure is highly competitive as demand continues to outstrip current capacity.

Second, designing chips for specific models and vice versa could lead to better performance. So, for example, if OpenAI can reap the rewards of that vertical integration, you can bet Anthropic and other frontier model providers will want that advantage as well.

To that point, Anthropic says its teams will co-design new hardware and models side by side. It has co-designed certain hardware with partners before, but the plan is now to bring more silicon expertise inside Anthropic itself.

Anthropic may also hope this could help its frontier models get some extra competitive edge as software developers and other users begin exploring running cheaper, smaller, or open-weight models on their own hardware or on edge devices.

However, since Anthropic is still in the process of hiring key team members, it will be some time before either the company or its users see any benefits.


Original Submission

posted by mrcoolbp on Saturday August 15, @06:08AM   Printer-friendly

https://www.engadget.com/2236104/cbp-officers-are-misusing-surveillance-tech/

US Customs and Border Protection (CBP) agents have reportedly misused electronic databases to spy on family members, try to get dates and even provide intelligence to suspected drug traffickers, according to freedom of information (FOIA) files seen by Wired. Officers allegedly abused databases that can draw from sources like license plate readers, facial recognition and smartphone searches to violate the privacy of numerous individuals.

The FOIA files, ranging from 2009 to 20222, show a number of troubling incidents. A CBP officer is alleged to have used a government database to contact a flight attendant, and another was accused of using data from trusted-traveler applications to ask people out. One employee provided border-crossing data to someone involved in a divorce, and another abused internal policies by tracking coworkers cellphones with ad-tech-derived location data.

Of 300 incidents tracked by Wired, 138 were referred to CBP management and 78 assigned to criminal investigators, while 43 others weren't investigated. Many of the claims were handled internally or put under the category of minor misconduct, but 21 were withheld due to potential law-enforcement proceedings that suggest criminal misconduct were involved.

The report is noteworthy because the DHS has more access to private citizens' data than ever before and has built one of the largest surveillance systems in the world, Wired noted. Its sources include records on immigration arrests, border screening records, naturalization applications and the SENTRI trusted-traveler program. The agency also has access to Palantir's ICM and FALCON systems, along with the DHS Mobile Fortify facial-recognition app deployed on agents phones.

CBP told Wired that it takes misconduct allegations seriously and works to "uphold the rule of law and hold ourselves accountable... [and takes] appropriate investigatory, corrective, and disciplinary action."


Original Submission

posted by mrcoolbp on Saturday August 15, @01:22AM   Printer-friendly

https://arstechnica.com/tech-policy/2026/08/claudes-new-scarlet-letter-watermark-is-invisible-for-now/

Anthropic has revealed that it will soon watermark content that is processed (not just generated!) by any of its models. In a support article, Anthropic explained that it was rolling out machine-readable watermarks to comply with the European Union's AI Act, which requires all AI system providers to watermark AI-generated or manipulated audio, image, text, and video outputs. The law applies to any AI model released after August 2 and provides a grace period until December 2026 for providers to update previously released models.

Anthropic confirmed that moving forward, all new models offered globally—not just in the EU—will mark AI-generated content "from day one." Text outputs will "carry embedded watermarks," invisible to the user, and other "generated files will include digitally signed provenance metadata where supported," Anthropic said.

Notably, Anthropic is deploying a "nuke it from orbit" approach, applying the watermarks to all processed content where supported, even though the EU does not require it for cases where an AI system performs "an assistive function for standard editing" (the guidance's own example is grammar correction), or where it doesn't "substantially alter" the user's text or its meaning.

A watermark applied at the model level can't tell wholesale generation from a comma fix, so Claude may end up stamping exactly the content the law was written to leave alone. How thoroughly it truly watermarks will not be known until Anthropic releases a detection tool that can be tested. The company said that it plans to eventually share details about how to detect marks in order to offer technical support that the EU's law requires.

Anthropic also noted that the watermarks won't work on "some platforms or features" that don't support them. For non-text content, Anthropic will use the C2PA metadata approach to record provenance.

The approach described by the EU and implemented by Anthropic is unfortunately trivially easy for bad actors to bypass, while potentially punishing users who trust the system to accurately label their outputs. Text watermarks work by biasing the model's word choices in a pattern spread across the entire document, only detectable in aggregate by the right tool. The catch is that "invisible" can also mean the model occasionally trades the best word for a slightly worse one, just to keep the signal intact.

Anthropic noted that those marks "will travel with the text when it's copied and pasted elsewhere, and may persist through some editing." But if watermarked text is pasted into another chatbot system that edits the text, the watermark could be destroyed. With image and video content, screenshotting/recording or using any decent metadata editing tool will suffice to remove this information, too. And once Anthropic tells the world how to identify these watermarks, building a system to remove them would be trivial.

Further, the potential for misinterpretation seems high; the watermark is not particularly informative. Anthropic explained that a "detected mark provides a signal that content was processed by Claude, but is not fully conclusive." The only real message the mark sends is that "the content may have been processed by Claude," Anthropic said, and the mark may even appear on content that was not generated by Claude.

On top of this, you have the general public, who may not grasp the difference between processed text and wholly generated text. If the system watermarks human-authored text simply because it was edited in a workflow that touches Claude, suddenly it carries the same denotation as wholly generated text does. And all of this in a system where the "lack of a detected mark doesn't mean the content wasn't AI-generated or processed," Anthropic said.

To its credit, Anthropic acknowledges that it may be marking some content that the AI Act does not require to be labeled: "People often use Claude to proofread, translate, summarize, or convert files. The output can carry a Claude mark even if the underlying ideas, text, or data originated from another source." So, despite being explicitly exempted by the law, Claude will mark any editing work done on original writing.

If the watermarks become a catch-all for any Claude use, from spellchecks to complete rewrites, Anthropic's solution will likely frustrate users by going further than necessary to label content in ways that could inadvertently muddle provenance. A teacher or professor, for instance, should not interpret this watermark signal as anything beyond "AI touched this," but it is easy to imagine they will. After all, what is the point of a watermark that cannot differentiate between light editing and wholly generated text?

The matter becomes even murkier when we turn to another section of the EU AI Act, 50(4), which addresses how those publishing such text must explicitly label content. Under their labeling regime, wholly generated AI text does not require a label in most instances. AI-written novel? No label. Marketing copy generated by AI? Nope. But if the text is meant to "inform the public on matters of public interest," you have to label it unless a human reviews it editorially (meaning, the editor is known and accountable). So, we have a strange situation where, on the model level, it's "watermark all the things," but on the public disclosure front, it's "you don't need to label this AI text if Joe looked at it."

Ars reached out to Anthropic to see if there's a timeline for details on detection to be released or results from any testing the company can share assessing the likelihood for false negatives or positives. We also asked if Anthropic could address how its watermarks may conflict with standard editing and other exemptions from the AI Act, but Anthropic sent a statement that did not address Ars' questions.

"We're adding marking to Claude's output to comply with the EU AI Act, and other labs are taking similar steps," Anthropic said. "It's hard to identify AI-generated text, and this gives people better tools for identification. Text from supported Claude models, including output from Claude Code, will carry an invisible watermark, and it doesn't change the meaning, quality, or readability of Claude's responses. We also plan to ship a text detection API so users can do more of this themselves."

In the EU, transparency requirements are meant to ensure AI tools like Claude don't upset "the integrity and trust in the information ecosystem, raising new risks of misinformation and manipulation at scale, fraud, impersonation, and consumer deception." One EU support article forecasted that the obligations would be the "primary compliance challenge" for many AI firms.

"People should know when they are interacting with AI or exposed to AI-generated content," the European Commission's guidelines said. "This will help them make informed decisions, calibrate their trust and reliance on AI, and avoid misinformation or deception." Still, it's hard to square this with the fact that a wholly generated article on a matter of public interest gets a watermark, but not a reader-facing label, if an editor properly reviews it.

AI firms like Anthropic are best positioned to develop watermarking solutions, the EU expects, since AI moves fast and there will be an ongoing "need for new methods and techniques to trace origin of information."

But that largely leaves the societal value of such marks up to tech firms to decide, with the EU only stipulating that "techniques and methods should be sufficiently reliable, interoperable, effective and robust as far as this is technically feasible."

In its post, Anthropic said it plans to continue working on its watermarks and detection methods that meet the EU's demands. If Claude's labels fail, the AI Act carries steep penalties for violations, including fines up to 15 million euros, or 3 percent of a company's worldwide annual revenue.


Original Submission

posted by mrcoolbp on Friday August 14, @08:39PM   Printer-friendly

https://www.techdirt.com/2026/08/12/ninth-circuit-rewrites-section-230-to-remove-the-part-that-actually-mattered/

For all the talk of "reforming" or "repealing" Section 230 in Congress, the fact is that the courts over the past three or four years have effectively chipped away so steadily at the law that it's lost a significant chunk of its usefulness. The latest comes from the Ninth Circuit, which ruled earlier this week that Section 230 is not, in fact, an immunity from lawsuit, but merely a defense against liability. This may sound like a procedural technicality — and, indeed, the coverage of this case from the likes of Reuters covers it as a boring procedural story — but it's a huge deal.

To get there, the panel had to rewrite the history of Section 230 and wave off a whole stack of its own prior rulings as either sloppy word choice or mere dicta.

To understand why this ruling is such a big deal, you first have to understand Section 230's true benefit: it would get bogus cases tossed at the earliest moment. This is the entire key to why Section 230 is important. The point of Section 230 is to put the liability on the party actually violating the law — which would be the creator of the content, and not the intermediary tool they use to host/distribute that content. But the mechanism used to protect speech is that it gets the cases against intermediaries dismissed very early (aggrieved parties can still sue the actual speakers).


Original Submission