What Happened to Silicon Valley? [Radar]
On October 16, 2026, I delivered the second Annual Margaret Levi Lecture in Political Economy in conjunction with the AI and History conference at Johns Hopkins University in Baltimore. This is my original lecture as written, which incorporates material from many pieces I’ve written over the years. As delivered, I departed significantly from the script, as you can see from the embedded video below or the transcript that you can see at the link above.
It’s an honor to give a lecture in Margaret Levi’s name. I’ve been asked to reflect on the changes in the political economy of Silicon Valley throughout my 40-plus year career in and about it, and I can’t imagine a better framing for my remarks than Margaret’s vision.
Margaret understood that advances in our ability to work together are essential to a better future. Cooperation is the human superpower. She also asks what happens when the systems of cooperation we have constructed over time stop holding up their end of the bargain.
That is very much the question that Silicon Valley is facing today. An industry that pioneered advances in collective intelligence at scale used to engender love from its customers because of the way it solved new problems in their lives. It now too often inspires fear and loathing. How did things go so wrong?
But let me start with my own history. I started my company more than 40 years ago with a $500 initial investment. We took in no venture capital, and we built a business that now generates hundreds of millions of dollars in profitable annual revenue, funded by customers who love our products and pay us for them. We got there the slow way, through steady organic growth. That is quite anathema to the rush to the top of whatever appears to be the latest hill that seems to characterize Silicon Valley today. Even when climbing that hill traps a company at a local maximum, the hope is to get to payday before the industry moves on to the next hill.
My original corporate goal was stated as simply “Interesting work for interesting people.” That evolved into two principles: “Change the world by spreading the knowledge of innovators,” and “Create more value than you capture.” Those principles shaped not only my company but what I expected the internet to be. When we launched GNN, the Global Network Navigator, in 1993, it was the first web portal and the first ad-supported site on the World Wide Web, and for two years it was the place people went to find other sites. What we built was a machine for pointing you at the best of what other people had made, and then getting out of your way.
Even our idea of advertising was not what you think of today. It was inspired by direct mail advertising, where you’d read articles in a print magazine or look at accompanying ads, and then you’d call an 800 number or circle a number on a “bingo card” that you’d send in to the publisher so that the advertiser could send you a brochure. I realized that the web would be a good replacement for that awkward system, that every company ought to have its own website that provided more information about its products and services. What we invented was not the “grab your attention” kind of advertising. It was all about utility, and sharing information that customers really wanted and needed. In short, it was the commercial web, which no one any longer thinks of as advertising, even though it is the most durable and useful kind.
The commercial web was only a small part of what the web became. The web was the playground of amateurs, not entrepreneurs. It was a marvelous collective work of human imagination, creativity, sharing, and ultimately (though that became toxic only later), competition for attention. Our hand-curated catalog of the best websites was soon surpassed by algorithmic solutions like those provided by Google. The amount of content produced was far larger than purely human curation could manage. It was an early example of what Richard Sutton was later to call “the bitter lesson” in his analysis of AI training.
In my 2005 essay “What Is Web 2.0?” I described how the companies that survived the dotcom bust had all, in one way or another, figured out how to help people navigate the resulting information explosion at scale. As Herbert Simon noted in 1971, an abundance of information leads to a scarcity of attention. In the face of increasing information abundance, he predicted that we would use machines to help us better allocate our time and attention. And so it has transpired: Information has become so abundant that it defies manual curation. Instead, powerful, proprietary algorithmic systems use the data they collect to match users with the answers, news, entertainment, products, applications, and services they seek. Today’s AI is in many ways a continuation of this arc.
I called this “harnessing collective intelligence.” All of it was, in economic terms, a set of remarkable advances in networked, data-enabled market coordination. It felt like a public good even when it was privately owned.
Hal Varian, formerly Google’s chief economist, once told me that only about 6% of Google search result pages carry any advertising or are otherwise monetized by Google. The other 94% were served up by search in a glorious demonstration of abundance, the surplus of value created over value captured. And while many of the pages themselves were commercial, even more were the product of the joyful exuberance of humanity, people creating and sharing for the joy of it. Google’s algorithm matched that creation to the people who wanted it, with no price involved anywhere in the transaction. Forty thousand times a second, Google’s organic search algorithms were performing the coordination that twentieth-century economists thought could only be done by self-interested actors haggling over prices. And for Google’s first decade and a half, the priced market of advertising ran alongside organic search as a sidecar, not the engine.
That’s the Silicon Valley I signed up for. Some of this is nostalgia. The early web had plenty wrong with it, its share of greedy hustlers and hypesters. But value creation for both users and suppliers was the winning strategy. Companies won by solving real problems for their customers. Investors won when the company delivered on their promises. Unfortunately, that didn’t last.
Google, a company once known for “Don’t be evil,” now faces the same surveillance-capitalism charges as Facebook, a company that never made any such promise. On Google, advertising now pushes organic search far down the page. Especially on mobile, you often scroll through pages of ads from national chains before you reach the site that has the best answer to your question. And in today’s AI-mode search, even the content is served up directly by Google, with far less traffic sent on to the sites that provide it. Likewise, Amazon, which used to call itself the most customer-centric company on earth, now puts sixteen ads and four organic results on a typical search results page. Sometimes, it may take scrolling past three screens of results to reach the first organic search result. And by “the first organic search result,” I mean “the best guess of the company’s smartest algorithms for what the user is actually looking for.” In former times, that was the top result. No more.
The reason isn’t that good people turned bad. It’s in the overriding economic incentives of today’s shareholder capitalism. The extractive behavior the tech giants exhibit has been the norm for modern companies since Milton Friedman reset its objective in 1970, in a sentence that became doctrine: “The social responsibility of business is to increase its profits.” Harvard Business School, through the work of Meckling and Jensen, enshrined that view not only into corporate law but executive compensation. Whatever people’s original motives, the logic of the market eventually prevails, except in extraordinary cases. In his recent book Incorruptible, Eric Ries describes a set of institutions, norms, and guardrails that can help to safeguard the values of a company, but you can count on your fingers and toes the high profile companies that have successfully deployed them to resist the market. Even tax policy rewards capital appreciation by taxing it at a much lower rate than labor income.
Our corporations and the financial markets that govern them and reward them are a kind of machine, what the science fiction writer Charlie Stross calls a “slow AI.” We built it. We set its objective function to reward shareholders and ignore everyone else. And then we tell everyone that it is a marvelous self-correcting system. This is an illusion. As I put it in “We Have Already Let the Genie Out of the Bottle,” an essay I wrote for a Rockefeller Foundation workshop on regulating AI:
Attempts at governance are futile until we recognize that we have built a machine and set it on its course. Instead, we pretend that the market is a natural phenomenon best left alone, and we fail to hold its mechanism designers to account. We need to tear down and rebuild that machine, reprogramming it so that human flourishing, not corporate profit, becomes its goal.
If the problem were just villains, you could fix things by firing them or shaming them or suing them or otherwise holding them to account. But if the problem is the design of the entire system, everyone is eventually incentivized to seek the same result. The machine rewards outsized growth of revenue and profit and brutally punishes any slowdown. Not only that, stock options tie every employee’s fortune to that reward.
Criticizing a company for turning extractive isn’t really about the values of a company or the character of its executives and employees, it’s about the incentives that have been given to them.
Silicon Valley is a mirror of what’s wrong with our economy and our corporate governance, not the cause of it, and not even the worst exemplar. Tobacco, oil, pharma companies, and far too much of Wall Street vie for that spot. But Silicon Valley is a great place to study what went wrong, because companies rise and fall so quickly, making them the equivalent of laboratory mice or flatworms, where patterns can be quickly identified and followed across generations.
A few years ago, I found a useful language for describing what I was seeing in the theory of economic rents.
The essential idea is that when the reward accruing to an actor is larger than their contribution to value creation, the difference is rent. To the classical economists, to Smith and Ricardo and Mill, living in a world of inherited privilege, rents were not a temporary aberration on the way to equilibrium. They were both a persistent consequence and a persistent source of inequality. Joseph Schumpeter had a different idea, that disproportionate profits can be a reward for innovation. An innovator can earn outsized profits during the expansive phase of a new technology, when it’s solving new problems and creating value not just for consumers but for a whole ecosystem of suppliers and intermediaries and even competitors.
When economists talk about rent-seeking today, though, many of them mean what George Stigler called “regulatory capture” and what the public choice school built into its doctrine: rents extracted through government intervention at the behest of those who lobby officials and bureaucrats to get their way in despite the free market.
The rents I want to talk about are a different animal. They are collected in the market, not around it, by private firms with enormous power, whose power is unchecked precisely because the government has stepped back.
For my purposes here, speaking about the rents that accrue to Silicon Valley companies, I divide them into two rough categories.
The first is what I call rising tide rents. This fits with the classical idea of rent as a reward accruing to an actor that is larger than its contribution to value creation, but it is a virtuous kind, a kind of communal value creation, often the result of positive government interventions. Consider the rise in home prices that accrues to a homeowner who lives in a neighborhood that is improved by better schools or improved roads, which then may lead to new shops and restaurants or the home improvements made by neighbors. This is also a kind of unearned income. Everyone shares the improvements in quality of life. But homeowners get something bigger, the unearned income from the appreciation in home value.
In a similar way, leading companies make massive improvements to the neighborhood, so to speak, and we all benefit. I should point out that government plays a significant role in these improvements. It’s easy to forget the NSF grant that funded the research that became Google, the loan guarantees that made Tesla possible, and government as the founding customer for SpaceX’s commercial launch services. It’s a rising tide that lifts all boats, and the fact that the market leader takes the biggest share of it is not, to my mind, a scandal. But Schumpeter thought those outsized profits would eventually be competed away as knowledge diffuses through society. What is a scandal is the way that Business Strategy 101 and corporate governance today teach companies to build moats and barriers to keep profits high even when the company stops earning rewards by innovating and better serving customers.
Companies do this by turning to the second category of rents, which I call robber baron rents, the income above a competitive rate that gets collected because of asymmetries in power, the way the medieval baron’s troops collected their share of the harvest whether or not the baron had contributed anything to growing it.
The same company can collect both kinds of rent at different stages in its lifecycle. As far as I can tell, the shift from one to the other is close to a law of the technology business cycle. The rising tide doesn’t last. Once the growth of a new market slows, the now-powerful incumbents can no longer rely on new users and a vibrant ecosystem to sustain their extraordinary profits. So they turn to extraction. They use their market power to hold on to their now-customary level of profit in the face of competition that ought to be eating it away. Cory Doctorow came up with a catchy name for this. He calls it enshittification.
There’s another problem with Silicon Valley and the economy writ large.
At one point in early 2021, when Elon Musk first became the richest person in the world, Bernie Sanders tweeted about it, contrasting Musk’s fortune with the frozen federal minimum wage. Bernie was right that the comparison was shocking. But he was wrong to imply that Musk’s wealth came from profits extracted at the expense of Tesla’s workers. The median Tesla worker makes considerably more than the median American worker, and up to that time, Tesla had few profits to extract. Musk didn’t hoard Tesla’s profits like a robber baron of old. He won a different kind of game.
Musk was paid in what the financial writer Jerry Goodman, writing under the pseudonym Adam Smith, called “supermoney.” The essence of Goodman’s insight is that any company that has been financialized through stock issuance is valued today as if it were already delivering the decades of future earnings reflected in its stock price. This is another of those ideas that help you to see the world in a new way. Once you realize that owners of capital are literally living in a different economy from those who earn income from their labor, you start seeing two different economies operating under two completely different sets of rules.
There’s the operating economy, where companies make and sell products and services and earn a profit by, as Nick Hanauer and Eric Beinhocker put it, solving human problems. And there’s the betting economy, where wealthy people bet on which companies will win the beauty contest that the stock market has become. In the operating economy, a dollar is a dollar. The neighborhood dry cleaner earns one dollar of profit and has that one dollar to spend. In the betting economy, a dollar of profit becomes many dollars of market value. At the time when Musk first became the world’s richest man, a dollar of Tesla profit turned into roughly $600 of stock market value. A dollar of Amazon profit at that time was worth about $67. A dollar of Google profit, about $34. The local business that isn’t financialized gets only $1.
That gap is one of the biggest unacknowledged drivers of inequality in this country, and it’s why one slice of society has gotten so much richer in recent decades while everyone else languished. Most rich people—and really, all holders of capital assets—live in the supermoney economy, where our assets are valued as if the future had already arrived and can be borrowed against, tax-free, today. This is the ultimate unearned income, or rent. Most everyone else lives in the dollar economy. If you’re a public-company executive paid in stock, or a venture capitalist, or an entrepreneur lucky enough to place in the financial horse race, you live in the other one, and you get a large interest-free loan from the future.
The betting economy, within reason, is a good thing. Speculative bets on the future are how we fund innovation and build infrastructure ahead of the prosperity it will bring. Tesla is a real company building real factories and real charging networks, and it kick-started a genuine transition to renewable energy. SpaceX and Starlink likewise required massive amounts of capital. And now AI has dwarfed even those bets.
Carlota Perez has shown that bubbles are a normal part of how revolutionary technologies get adopted. I’m not against betting. I’m worried about what we bet on, and what will be left over when the bubble pops.
If your biggest lever for wealth creation is not in the market for real goods and services, but in the market for future expectations, it’s easy to continue down the slippery slope to making money by manipulating those expectations. And that’s the road Silicon Valley has charged down.
Sam Bankman-Fried captured the zeitgeist with his line “Number go up.” Silicon Valley has gotten addicted to value capture without value creation. Think about it: 75 to 80% of IPOs are for companies without any profits. Add in acquisitions of pre-IPO companies and the numbers are likely even worse. It’s like a horse race where bettors can collect their winnings when the horse has rounded the first or second turn.
There are still venture capitalists who look for companies that succeed by delivering real value to customers, but the prevalence of the profitless IPO has turned the venture-backed company into a kind of financial instrument. Much as the bankers who invented the derivatives that nearly sank the global economy in the 2009 financial crisis eventually ran out of real mortgages to collateralize and turned to “liar loans” so they could keep the game going a little longer, the measure is no longer whether a company has a chance of living up to its promises but whether it can convince the investor in the next round that it can. Most startups are built to be refinanced all the way to the exit rather than to turn into sustainable businesses.
This dynamic is essential to the current AI infrastructure buildout. Data centers are built to meet expectations of massive future demand. But much of that demand is from companies that have not yet, as Silicon Valley used to describe it, found “product-market fit.” That is, they have not yet found customers willing to pay more than the product costs to deliver. In short, the future cash flows with which data center builders are expecting to pay back the trillions they have borrowed or invested are dependent on those customers’ ability to raise their next round at an ever-increasing valuation.
AI is the real deal, a transformative technology like the internet. And its leading company, Anthropic, looks to be turning into an actual business with cash flow and profits. But others, even those like OpenAI with enormous revenues, are still dependent on massive additional capital infusions to survive. But it’s OK, as long as “number go up.”
A structure like this does not need demand to collapse. It only needs the hype to recede enough that it is no longer possible to raise more capital at ever more stratospheric valuations. That’s why we see hype in increasingly desperate amounts.
I first started thinking about this turn to hype in Silicon Valley in the days of Uber and Lyft. The innovation of using GPS and smartphones to create crowdsourced taxis on demand using people’s personal cars was real and important. But building the matching marketplace of riders and drivers took enormous subsidies, and it wasn’t terribly profitable. So Travis Kalanick, the CEO of Uber, told investors that Uber wasn’t out to replace taxis, but the private automobile. Then in the run-up to the IPO, he started talking about self-driving cars, presumably to suggest that Uber would be much more profitable once it was able to get rid of the cost of drivers. Meanwhile, Waymo kept its head down and did the hard work of actually building out the technology, which is only now coming to fruition.
That kind of hype continued through the next one of Silicon Valley’s dry spells. There wasn’t much real innovation to talk about, so the masters of capital sold “the Metaverse” and eventually “Web3.” As the person who defined “Web 2.0,” I was asked frequently to opine on Web3. I tried to avoid answering. Most prognostications about the future turn out to be wrong. What we can do is ask questions that help us see the present more clearly. So finally, I laid out my reservations in a piece called “Why It’s Too Early to Get Excited About Web3.”
I explained how Carlota Perez and Bill Janeway distinguish productive bubbles from unproductive ones. In a productive bubble, speculative excess builds lasting infrastructure the future can capitalize on. The dotcom bubble was, in that sense, productive. When it popped, it left behind billions of miles of high-speed fiber and the data centers and the know-how that the next decade’s boom was built on. The 2009 mortgage bubble, on the other hand, left behind mostly wreckage.
The issue with Web3 wasn’t that the prices were crazy, since prices are always crazy in a bubble. It was whether anything was being built that would outlast the crash. What Silicon Valley delivered in that period mostly turned out to be betting with only the barest nod towards actual product. You probably all remember the craze for “bored apes.”
Even when there is real substance to an investment bubble, Silicon Valley has learned to lean into hype as an instrument for drawing investment. For example, when Tesla’s stock began descending from the stratosphere, Elon Musk started touting humanoid robots as the future of Tesla and pitched SpaceX not on the basis of its actual business of commercial space launches and Starlink’s huge network of communications satellites, but on AI, and on promises of a self-sustaining city on Mars housing at least one million people, travel to any point on earth in 30 minutes, and a possible enterprise value of $100 trillion!
Not everyone can be as bold and imaginative as Elon Musk. But there’s one pretty sure bet that gets the investors to pile on, and that’s the promise of a monopoly.
Look no further than that race between Uber and Lyft. When they went toward their IPOs, neither was profitable, and their enormous valuations rested entirely on the premise that if you grow big enough and fast enough, profits will follow. Most monopolies and duopolies used to develop slowly and were understood as dangerous to competitive markets. Now Silicon Valley decided they are something to seek from the start, as the holy grail for investors. Reid Hoffman and Chris Yeh called this strategy Blitzscaling, a term they cheerfully derived from the Nazi blitzkrieg. Their argument is that you need to move fast enough to seize a market before anyone else can, even when you don’t yet know how you’ll make money. If you can promise a monopoly, you can raise a great deal of money.
I don’t have a blanket objection to moving fast. But do I think blitzscaling is a morally bankrupt idea, a game that defines winning as extracting value rather than creating it.
The saddest part of blitzscaling is that it has turned the original genius of the competitive market on its head. It’s now a kind of oligopoly of capital. Instead of customers choosing the winners, the VCs do it up front. Sunil Paul, the inventor of the technology and business model that Uber and Lyft soon dominated, raised only $35 million for his company Sidecar, which was soon crushed when Uber and Lyft raised and spent billions on marketing and subsidized fares to quickly gain users.
If I had to name a villain in this transition, it would be Andreessen Horowitz. The firm was founded in 2009, at the start of the era of cheap capital I’ve been describing, and it built a media and narrative operation from the start. Benedict Evans, who worked there, later described the firm as “a media company that monetizes through VC.” The story that a company will win because of how much money it has raised becomes part of how it actually wins. But I don’t think it allocates capital anything like as effectively as a well functioning market where customers pick the winners.
What connects the enshittification of search, the supermoney economy, the blitzscaling of Uber, the narrative machine of a16z, and the crypto casino is not a run of bad actors. It’s shareholder capitalism reaching the late stage of its own logic. In its youth, that system was oriented, however imperfectly, toward creating value. In its endgame it has reoriented toward extracting it.
We are standing at the beginning of the next turn of the cycle. This time, AI is the technology driving the boom. And once again, it represents the possibility of huge advances in human collective intelligence. Like the web was 25 years ago, it’s a new creative frontier enabled by technology.
The pattern I described earlier usually has a rising-tide youth that comes before the extractive turn. However, in some ways, AI has been enshittified from the very beginning. It skipped the youth. The AI labs have taken in hundreds of billions of dollars, with trillions committed to data center buildout, and capital on that scale doesn’t wait for a business to grow into itself. It demands a return, and the pressure to repay it will inevitably push these companies toward value capture before they’ve finished creating value.
AI was also built on an extractive foundation. Last year, when The New York Times reported that OpenAI and Google were training on transcribed YouTube videos and other copyrighted work, the host of The Daily, Michael Barbaro, called copyright violation “AI’s original sin.” Margaret Levi might have called it an act of enclosure, the privatization of what had been a commons, the accumulated writing and code and conversation and images that billions of people made and shared, much of it in the joyful exuberance I started this talk by describing.
AI also breaks the old bargain in a way even the enshittified web did not. Google, at its best, sent you somewhere else. It read the commons and pointed you back into it, 94% of the time without even trying to monetize it. AI doesn’t send you elsewhere at anything like the same rate. It offers a replacement for what you would once have gone out and found, an answer in place of the referral.
We’ve been told, again and again, that the secret of future prosperity is to create enormous, disproportionate rewards for innovators and their backers. The kind of people that tech companies used to serve as their customers don’t really matter. They are necessary casualties on the road to an unimaginably better future.
This is profoundly short sighted. An economy is a circulatory system. In The Marriage of Heaven and Hell, the visionary poet and painter William Blake (writing during the first Industrial Revolution) put the circulatory logic perfectly: “The Prolific would cease to be prolific unless the Devourer as a sea received the excess of his delights.” In other words: Output has to be consumed. The system has to flow.
Today, many AGI narratives assume that the “prolific” can keep producing and the broad mass of customers (“the devourer”) somehow continue to buy, even as more and more human labor is displaced and labor income and bargaining power collapses. That’s not a future of abundance. It’s a recipe for a kind of congestive heart failure for the economy.
If the AI labs wish to be architects of a prosperous future, they must work as hard on inventing the new economy’s circulatory system as they do on improving model capabilities. They need to measure success by diffusion, not just capability. They have to ask always how their customers are going to make money, not just how they themselves will. They have to treat the labor transition as a core problem to be solved, not just studied. They have to be willing to win in the marketplace, not through artificial moats. That means committing to open interfaces, portability, and interoperability. General-purpose capabilities should not become a private toll road.
It’s an economy crying out for mechanism design. Mechanism design is a term that I’ve shamelessly stolen from the economists and redefined to describe what I think is missing from the AI economy. It’s a branch of microeconomics that studies how to design the rules of a market in such a way that even self-interested actors who have private information are more likely to produce outcomes that are better for everyone. Leonid Hurwicz, the founder of the field, called it “reverse game theory” because it works backward from a desired outcome to develop the rules that will produce it.
They give Nobel prizes in economics for advances in the theory of mechanism design. But it seems to me that many of the most successful mechanism designs happen in the real world. They evolve. They are discovered. Ken Thompson and Dennis Ritchie weren’t trying to invent the marvelous open-ended game that we now call open source software when they designed Unix. They were just trying to build a portable operating system able to run on multiple hardware architectures. That also happened to mean that you could only distribute software via its source code rather than just the binaries. And their breakthrough design of a protocol-centric operating system with a small kernel surrounded by cooperating, communicating utilities created what I call “an architecture of participation.” Anyone could add to the system, or easily replace one of its standard parts with an alternative.
That was a very different marketplace design than the proprietary operating systems of the day, which were created to tie software developers to specific hardware platforms. It led to a vibrant software sharing economy that is still going on today and that transformed all of software development.
You can see the same kind of evolution in AI. I don’t know that David Soria Parra and his colleagues at Anthropic meant to change the market structure of AI when they developed MCP, but that’s what happened. Rather than a winner-takes-most market in which developers call the APIs of the dominant, centralized platforms (as had happened previously with Windows for the PC, and iOs and Android for mobile), the agentic web began to take on the shape of the participatory economy of open source software and the web. People can bring their own models and infrastructure to the table as an alternative to the big centralized players. And that story is far from over. In fact, it is just beginning.
Every major technology wave arrives in two stages. The first stage is the development of the technology itself: the personal computer, the World Wide Web, the smartphone, and now, generative and agentic and physical AI. The second stage involves the development of new economic mechanisms that enable transformative business models to take advantage of the technology. The earliest business models often imitate what went before and encode the business ambitions of the old technologies the creators grew up with. As the technology matures, the problems with the original business models become apparent, and eventually, through a process of trial, error, and invention, new mechanisms enable new business models.
The web was invented in 1991. But the web advertising economy didn’t really take off until Google figured out PageRank, and then perfected pay-per-click advertising and the ad auction. Ecommerce didn’t take off until companies like PayPal made it safe to type your credit card number into a stranger’s website, and until Amazon built the warehousing and delivery networks that made rapid delivery possible. The smartphone put GPS in everyone’s pocket, but it wasn’t until Sunil Paul envisioned and built the first real-time location matching marketplace for ride sharing that Uber and Lyft and DoorDash were able to turn that capability into a huge on-demand economy. YouTube didn’t become the engine of the creator economy until it answered the takedown notices and lawsuits of the music industry not with stonewalling or settlements, but with Content ID.
It’s easy to look at the winners, and think the path to get there was obvious. It wasn’t. There were all kinds of failed approaches to solving the problems that only became apparent during the technology diffusion and adoption period. I don’t have time to chronicle the graveyard of failed search, advertising, and ecommerce experiments and standards. But you don’t need to look back. Just look around. How many proposals there are today for managing rights, blocking or allowing bots, enabling agents to cooperate, and payment. There are at least six competing agent payment protocols alone. We’re in the exploratory phase of mechanism design for AI.
That’s where I come back to the idea of mechanism design as reverse game theory. Rather than asking ourselves the rules of the game we are now playing, it calls us to ask “What game ought we to be playing?” And that question leads me imperatively to my answer: “The game of human flourishing.”
We have been told that the game is the quest for superintelligence. We have been told it is a winner-takes-all game that will bring untold riches to the winners and impoverish everyone else. And we have seen mechanisms designed to support that game: massive investments in data center capacity such that only the well-capitalized can play, colonialist appropriation of existing intellectual property, closed model weights with terms of service that forbid others from learning from them, memory that locks our context inside one provider’s walls, and PR stunts like dumping millions of dollars of compute to solve high-profile math problems, or hyping the cybersecurity risks of their offerings, for which only their latest, most powerful models are offered as the only remedy.
If the game we want to play instead is human flourishing, we need to design mechanisms that lead us to that outcome. We need mechanisms that provide a circulatory economy of value exchange, for and by humans in partnership with AI, rather than replaced by it. And in my experience, those mechanisms look like open source, open protocols, open memory, because these are things that give the freedom for users to shape and control this most wonderful new technology wave for ourselves.
Henry Farrell, Alison Gopnik, Cosma Shalizi, and James Evans argued in Science last year that large models are best understood not as independent intelligences but as a new kind of cultural and social technology, one that lets us take advantage of the information other humans have accumulated, in the lineage of pictures, writing, print, and internet search. AI may be the most powerful means of harnessing collective intelligence yet. The commons isn’t incidental to AI, it’s the material AI is made from.
In the world I see coming, AI is a medium, like painting or writing or music. If we get this right, everyone will get the same paints and brushes, the same words, the same notes, but some people draw more out of them than others, or do it better. We won’t decide up front that those who raise the biggest pool of capital are due all the rewards.
Our job is to draw something more, something better, out of the ocean of possibilities in the collected knowledge inside the model. AI was built from our collective intelligence. It should not be designed to replace us. It depends on us to create its value.
Thank you very much.
This Week in AI: AI’s Next Reality Check [Radar]
AI’s growing role in business is exposing challenges that new models alone can’t solve. On the latest episode of This Week in AI, we examined restrictions on autonomous agents, NVIDIA’s leadership crisis, and research into making AI systems more reliable.
Anthropic is turning Claude into a broader workplace platform. Alongside its upgraded Fable 5.2 and Mythos 5.2 models, the company introduced Claude Meetings and Claude Sheets, Whiteboards, and Data. Anthropic also expanded its enterprise offerings with self-hosted agent infrastructure. Companies can connect agents to internal systems while keeping credentials and session histories on their own infrastructure, even though the models still run through an external provider.
OpenAI is bringing more of the shopping process into ChatGPT. Its new business profiles let companies manage how customers discover them, while business agents can answer questions and recommend products. The company also introduced ChatGPT Wallet, which allows agents to make purchases without accessing customers’ actual payment card details. Users still need to review and approve these transactions before payment. Bringing business discovery and payments into ChatGPT puts OpenAI in more direct competition with search engines and online marketplaces.
Airlines, banks, and retailers, however, are already restricting outside agents. United Airlines is blocking unauthorized agents from booking flights, while financial institutions and retailers, including Amazon and eBay, have imposed their own limits. Their concerns include privacy, security, and unintended purchases. An agent may be technically capable of completing a transaction but prohibited from accessing the service. Developers will need to account for those limits, while businesses that allow such transactions must establish who bears responsibility when an agent makes an unintended purchase.
NVIDIA founder Jensen Huang resigned as CEO following reports of personal relationships that prompted an investigation into potential national security concerns. US authorities have been investigating whether a Chinese businesswoman involved in the controversy had intelligence ties to Beijing. Those allegations remain unproven. NVIDIA’s board launched its own investigation, and longtime CFO Colette Kress has stepped in as interim CEO while the company searches for a permanent successor.
NVIDIA’s influence over the AI chip market makes its leadership transition especially consequential for customers and investors. Huang led the company for 33 years and helped establish its dominant position in AI infrastructure. Now Kress and the board must maintain customer confidence while navigating the investigation. We also discussed NVIDIA’s investments in other AI companies and the circular financing arrangements that have raised concerns about how the industry measures growth. Any changes to those investments could affect companies that depend on NVIDIA for both computing infrastructure and capital.
NVIDIA’s leadership transition also raises questions about succession at founder-led technology companies. After three decades with Huang at the helm, the board must show it can provide independent oversight and maintain the company’s direction through a period of uncertainty. How NVIDIA manages that transition could offer lessons for other AI companies whose identities remain closely tied to their founders.
New research found that giving AI agents memory of previous tasks can make them perform worse than without memory when they learn the wrong lesson or apply past experiences out of context. The proposed WikiTrace system links memories to their original tasks and evidence, allowing agents to check what they’ve learned before acting.
Other researchers are investigating how to detect uncertainty in language models through internal signals, hidden states, token probabilities, and whether the model gives conflicting answers to the same question. This matters because AI can sound confident even when it is wrong. If we can spot when a model is unsure, we could prompt it to check its answer or acknowledge its uncertainty, helping people avoid relying on incorrect information when making decisions. Meanwhile, MIT researchers explored weight-space programming, using language models to inspect and edit other neural networks’ weights. In early experiments, the approach corrected a simulated driving problem and improved another model’s math performance.
Benchmark scores alone don’t explain why agents misuse memories, sound confident even when they are wrong, or fail at specific tasks. Research into these problems could give developers better ways to diagnose and correct mistakes as AI systems take on more responsibility.
Next week, we’ll follow up on NVIDIA’s leadership transition and Anthropic’s anticipated IPO, along with other developments across the AI industry.
We’ll be back on Monday, November 23, for another episode covering the latest developments in AI research and applications. You can catch previous episodes on YouTube, Spotify, Apple, or wherever you get your podcasts.
Why do I get inconsistent results when I ask for the icon for the .. parent folder? [The Old New Thing]
A customer wanted their program to show a file listing with
icons, and they also wanted to include an entry for the parent
folder, programmatically known as .. (double period). They
obtained icons by calling the SHGetFileInfo function,
but they got weird, inconsistent results when they asked for the
icon of the .. parent folder.
SHGetFileInfo(L"..", 0, &info, sizeof(info),
SHGFI_ICON | SHGFI_SMALLICON | SHGFI_SYSICONINDEX);
They found that when they ran the program in a debugger, it gave them the desired folder icon 🗀. But when it ran on the customer’s system, it showed a drive icon 🖴. What’s going on? Why is the icon changing depending on who is running the program?
My psychic debugging powers¹ told me that the developer told their debugger to run the program with the current directory equal to something that is at least two directory levels away from the root. Perhaps they are using Visual Studio and accepted the default configuration that sets the current directory to $(ProjectDir), and their project directory is eomthing like C:\Users\name\repos\contoso. On the other hand, the customer is running the program while the current directory is set to an immediate subdirectory of the drive root, like C:\Contoso.
When you pass ".." to SHGetFileInfo, it is
recognized as a relative path and is resolved against the current
directory. And then you get the icon for whatever that turns out to
be.
Resulting iconfolderdrive
| Current directory | C:\repos\contoso | C:\contoso |
|---|---|---|
| ".." resolves to | C:\repos | C:\ |
So what should you do if you want to get a folder icon?
You can pass the
SHGFI_USEFILEATTRIBUTES flag, which means,
“Just pretend that I gave you a valid path to a thing with
the attributes I passed as the second parameter. What icon would
you use for it?”
SHGetFileInfo(L"C:\\a", FILE_ATTRIBUTE_DIRECTORY, &info, sizeof(info), SHGFI_USEFILEATTRIBUTES | SHGFI_ICON | SHGFI_SMALLICON | SHGFI_SYSICONINDEX);
We pass a file path of C:\a and say that its attributes
are FILE_ATTRIBUTE_DIRECTORY. The actual path is not
important, as long as it is a syntactically valid path.
Next time, we’ll look at a follow-up question related to this problem.
¹ I want to remind you that if you force me to do psychic debugging, then you have failed. When I coined the term “psychic debugging”, I used it to describe the case of debugging a problem where the person asking the question omitted crucial information, forcing me to go to the extra effort of obtaining that information through supernatural means. It’s like showing up at the passport office without having the proper forms filled out. The clerk can probably give you the correct form and help you fill it out, but they’re not going to be happy about it because you’re just creating extra work for them due to being ill-prepared.
The post Why do I get inconsistent results when I ask for the icon for the <TT>..</TT> parent folder? appeared first on The Old New Thing.
View From a Hotel Window, 11/20/26: Minneapolis [Whatever]

And it’s the last hotel window shot of the year, because my appearance at Twin Cities Con is also my last public event of 2026. I have some personal travel scheduled before the end of the year, but that’s (and I say with with love) none of your business. So enjoy this view! And come see me this weekend at the convention. I have a panel called “John Scalzi Won’t Shut Up” on Saturday at (I think) 3:30, and when I’m not there I think I might have a table somewhere. We’ll see! I don’t expect I will be difficult to find in any event. Just look for the middle-aged white male nerd! That will narrow it down a bit.
— JS
[$] Bringing the Agama installer to openSUSE Tumbleweed [LWN.net]
The openSUSE Project has been working on the Agama installer for four years; it was the default installer for openSUSE Leap 16.0 when it was released in 2025, and has been adopted by other openSUSE flavors as well. Now the project is gearing up to go all-in on Agama for Tumbleweed, the rolling-release edition that is meant to be where updates and new features land first. Even so, the community has concerns about losing some of YaST's legacy functionality and the impact on installing Tumbleweed on systems that have less RAM.
Beyls: Wrapping up LLVM's relicensing effort [LWN.net]
Kristof Beyls has published a summary to the LLVM discussion forum to announce that the project is declaring success and bringing its relicensing effort to a close after eight years.
We've been asking past contributors to relicense their work since 2018. New contributions have come in under Apache-2.0 WITH LLVM-exception since January 19, 2019. Code contributed before that date was under LLVM's earlier licenses (UIUC/NCSA, plus MIT for some runtime libraries), so we needed permission from its authors to move it over. [...]
Today, more than 99.5% of all lines of code ever contributed to LLVM are either covered by the new license, too small for copyright to apply, or no longer in the repository.
Rather than trying to "chase the last tiny fraction
forever
" LLVM is winding up the effort. Any contributors with
code contributed before January 19, 2019 who have not signed a
relicensing agreement and do not want their contributions made
available under Apache-2.0 with the LLVM-exception can still reach
out to the project to ensure their code has the appropriate SPDX
license identifier.
Vim Classic 8.3.1 released [LWN.net]
Version 8.3.1 of Vim Classic—a long-term support fork of Vim maintained without LLM assistance—has been released.
This release includes applicable Vim patches up to Vim 8.2.3237, including numerous bug fixes, minor features, and compatibility improvements for Vim plugins. This release also removes Python 2 support from Vim Classic.
The full list of changes in this release is available on sourcehut.
Error'd: There's a Chill in the Air [The Daily WTF]
There's a bathroom on the right!
"Interesting temperature reading from WU" notes Peter G. "This must be what happens when a bulk liquid nitrogen carrier runs aground in your favourite holiday spot. Either that or you're supposed to take the average of +60 and -40 to get the actual temperature."
At the same time, an anon mutters "I think someone left the freezer door open."
And an anonagain loves "M$ SharePoint security. Need I say more?"
Furry friend The Beast in Black growls "This unique hotel amenity is one I haven't yet seen offered elsewhere and is one I'll certainly be using."
Until John remembers that "AI's are not causing the memory shortage, they claim to be solving it! Hopefully the stochastic approximations will not spread any further through the operating system." It just depends on what the meaning of the word is is.
New BonBon release v0.6.55.
Security updates for Friday [LWN.net]
Security updates have been issued by AlmaLinux (bind9.18, bubblewrap, fence-agents, freerdp, grafana, grafana-pcp, gstreamer1-plugins-bad-free, jackson-core, jackson-databind, java-17-openjdk, java-21-openjdk, java-25-openjdk, kernel, kernel-rt, mysql8.4, mysql:8.4, qt5-qtbase, qt5-qtdeclarative, raptor2, resteasy, and sos), Debian (electrum, nginx, openjdk-17, pam-mysql, php8.2, and php8.4), Fedora (aws, bind9-next, blender, c-ares, composer, dr_libs, et, gh, incron, libaec, libfontenc, libXfont2, mtools, nebula, perl-Imager, perl-Text-JSCalendar, perl-Text-JSContact, php, python-loguru, python3.6, qpid-proton, roundcubemail, runc, and xen), Gentoo (nginx, PHP, and Ruby), Mageia (hplip), Oracle (.NET 10.0, .NET 11.0, .NET 8.0, .NET 9.0, bubblewrap, emacs, firefox, flatpak-builder, gcc, gimp, glibc, grafana, grafana-pcp, gstreamer1, gvfs, java-1.8.0-openjdk, java-17-openjdk, java-21-openjdk, java-25-openjdk, libssh2, mod_http2, perl-CGI, perl-DBI, perl-DBI:1.641, python3.9, rpm, squid, tesseract, thunderbird, tigervnc, util-linux, webkit2gtk3, and xdg-dbus-proxy), Red Hat (compat-openssl10, kernel, nginx, nginx:1.24, nginx:1.26, nodejs22, nodejs:22, openssl, python-urllib3, python3.12-urllib3, qt5-qtbase, and qt6-qtbase), Slackware (gnutls, perl, and php), SUSE (cifs-utils, elemental-operator, elemental-system-agent, elemental- toolkit, haproxy, java-11-openjdk, kernel, libXi, python-M2Crypto, python-oauthlib, rekor, and xen), and Ubuntu (kernel, linux, linux-aws, linux-aws-5.4, linux-azure, linux-bluefield, linux-fips, linux-gcp, linux-gcp-5.4, linux-gcp-fips, linux-hwe-5.4, linux-ibm, linux-ibm-5.4, linux-iot, linux-kvm, linux-oracle, linux-raspi, linux-raspi-5.4, linux-xilinx-zynqmp, linux, linux-aws, linux-aws-fips, linux-aws-hwe, linux-azure, linux-azure-4.15, linux-azure-fips, linux-fips, linux-gcp, linux-gcp-4.15, linux-gcp-fips, linux-hwe, linux-kvm, linux-oracle, linux, linux-aws, linux-aws-fips, linux-gcp, linux-gcp-6.8, linux-gke, linux-gkeop, linux-ibm, linux-ibm-6.8, linux-oracle-6.8, linux-vmware, linux, linux-aws, linux-fips, linux-kvm, linux-lts-xenial, linux, linux-aws, linux-gcp, linux-gcp-5.15, linux-gke, linux-gkeop, linux-ibm, linux-ibm-5.15, linux-oracle, linux, linux-aws, linux-gcp, linux-gcp-7.0, linux-gke, linux-ibm, linux-oem-7.0, linux-vmware, linux-aws-5.15, linux-aws-fips, linux-aws-fips, linux-kvm, linux-fips, linux-gcp-fips, linux-gcp-fips, linux-oracle, nginx, openjdk-17-crac, openjdk-21-crac, openjdk-25-crac, openjdk-8, pyjwt, and ruby3.3, ruby3.2, ruby3.0).
My Super Mid-Life Crisis – Issue 1 – 16 [Comics Archive - Spinnyverse]
The post My Super Mid-Life Crisis – Issue 1 – 16 appeared first on Spinnyverse.
Resetting priorities for Day 3 of the life of BonBon. I have
gotten messages from friends who are thinking about how to create a
Markdown web site of their own. I want to share interesting
examples showing how people have done it. So here's the first one.
We spent a fair amount of time getting Scripting News to be part of
this experiment. We wrote a server app that watches what's going
on, via the RSS 2.0 feed. When it sees a new or updated post, it
generates a Markdown file and updates the toc.opml file to link it
into the chronology of the blog. It also recognizes some custom
front matter values, and handles some special cases for Markdown
itself. For example, an image that appears at the beginning of a
paragraph, before anything else, is shown in the right margin, like
the beautiful Lab in the right margin. It also has a special syntax
for inline images, like the one in this post.
There's a general config file alongside toc.opml in the .well-known
folder at the top level. Also they can be nested, so you could have
a .well-known folder at any level. Anyway all this is to say that
we've shared a snapshot of the scripting website in markdown in the
BonBon repo. More of these to come, and we want to see new examples
from people working on this stuff so we can share them with the
community. This like coming up with a platform and sharing
developer stories.
Also, learned that Claude Code can forget to do things when
it rebuilds an app for distribution. I found this when I, as a
user, did an update and the desktop icon for BonBon was blank. I
figured it would take a few hours before the OS straightened it
out, but it didn't. We then discovered this flaw. People who think
AI tools are perfection are up for a rude awakening. They
always forget stuff. It's really irritating, after all it's
a freaking computer -- we expect computers to have perfect memory.
Maybe someday. So you may not realize that the beautiful Black Lab
I've been including in the right margins of posts is also the
identity of the product. If you've ever had a Black Lab, as I have,
you know that you're getting an extremely loyal, friendly and
fun-loving best friend, who demands basically all your time, esp
when they're young. What does that portend? Probably nothing, but
it makes me smile when I see it.
Claude Watermarks Your Words, and You Can’t Check Them (Yet) [Radar]
I love using AI as a writing tool. But like I wrote in “Why Does AI Write Like Yoda?,” it’s not because AI is a good writer. In fact, it’s pretty bad at writing, and I edit absolutely everything it generates, so the end result is basically unrecognizable compared to what it created. Unfortunately, just because AI is, on average, a pretty lousy writer, that doesn’t stop people from using AI to write all sorts of things that people end up reading, and that’s how we end up with slop.
That’s where watermarking comes in. If AI-written text carries a hidden signal that a machine can pick up, someone could build slop filters with it and add a little friction to mass-producing AI text and stuffing it into every nook and cranny of the internet and, maybe, manage to keep some spaces on the internet for people. (Anthropic and OpenAI give a more official reason: the EU AI Act now requires them to mark AI-generated content in a way machines can read. I don’t know how they feel about slop.)
The upshot is that almost everything Claude writes now carries a hidden watermark. A slop filter needs a way to check for the watermark. And, unfortunately, for the time being, only the big AI companies and a few organizations they’ve approved can check for it.
Anthropic’s support page on marking AI-generated content now reports all of its newest models, and some older ones, watermark their text on every surface where you can use Claude, worldwide. (Bruce Hopkins covered what Anthropic announced here on Radar.) Google has used a text watermark in its Gemini app since 2024, and in October OpenAI announced it’s adding one to ChatGPT and Codex text in the EU. But none of those companies lets the public check text with its detector. (Google’s synthid.com lets anyone check images, video, and audio for its watermark, including images made with ChatGPT, but it won’t let you check text from any AI lab.)
I’ve read articles about watermarking, but I didn’t really know much about how it worked. So I did what any good developer would probably do: I took a shot at reasoning about it, and I came up with what I thought was a plausible way watermarking could work, based on what I know about how large language models work. And, strangely enough, it turned out I was basically right, and not because I’m some sort of amazing genius. It’s because watermarking is actually pretty straightforward, and if you know how the output part of an LLM works, you can probably design a decent watermarking system yourself.
The reason I’ve got such a big interest in how models work right now is my next O’Reilly book, a deep dive into how models work called Be the Model, which we’re planning on releasing early next year. I’ve spent a lot of time over the last year thinking really hard about how to explain the internals of LLMs, and it turns out that you don’t need to understand most of the parts inside a model to see how watermarking works. All you need is the very tail end.
So let’s try an experiment. I’m going to describe the relevant bits of how models work, and then, before I explain how watermarking works, I want you to take a guess and see how close you come.
There’s a lot of stuff that happens inside a model. You’ve probably heard of transformer blocks, and you might know what a context window is. That’s all part of the whole machine. But at its core, a model is a next-word-predicting machine: You feed it a bunch of text as context, and it predicts the next word. The part that matters for watermarking is what goes into that machine and what comes out.
What goes into the machine is tokens. We all know that when you pay an API bill, you pay some number of dollars per million tokens, but we don’t always explain what a token is. Remember when people discovered that AIs were really bad at counting the r’s in the word strawberry? Part of the reason for that is that the AI never sees letters. It only works with numbers.
Every model has a fixed vocabulary of tokens, which are every word and piece of word it knows, and each token has a number called its token ID. On the way into the machine, a tokenizer splits your text into tokens and replaces each one with its ID. For example, if you ask GPT-2 (an early LLM created by OpenAI in 2019) “how many r’s are in strawberry,” its tokenizer turns the word strawberry into a single token, number 41236. The model gets that number, not the letters s-t-r-a-w-b-e-r-r-y, so it doesn’t have any actual letters to count.
Common words usually get a token of
their own. But a word that isn’t in the vocabulary gets split
into smaller pieces that are, which is how a tokenizer can handle
any text you give it. GPT-2’s vocabulary has a token for
"strawberry" with a space in front of it, but not for
"strawberry" without the space. So if
strawberry is the very first word of the text, with no
space in front of it, the tokenizer splits it into three pieces
that are in the vocabulary: st, raw, and
berry.
GPT-2 has 50,257 tokens in its
vocabulary. If you have Python and install the Hugging Face
transformers library, you can check GPT-2’s
vocabulary size and strawberry tokens with this command:
python3 -c "from transformers import AutoTokenizer;
t=AutoTokenizer.from_pretrained('gpt2'); print(len(t));
print(t.tokenize(' strawberry'), t.tokenize('strawberry'))"
If you don’t have Python or
don’t feel like installing transformers, you can
go to ChatGPT, Claude.ai, or Gemini and paste that command in, and
they’ll (probably) install the library and run it for you. It
should print 50257, then ['Ġstrawberry']
['st', 'raw', 'berry']. The Ġ is how this
tokenizer writes the space. (If you don’t have PyTorch
installed, you’ll see a warning about it first, which you can
ignore.)
The token IDs go into the context window, which is just a big array of numbers, and then the AI does its thing. The context window contains every token the model sees when it’s making its next-word prediction. If you’re using a chat, it usually includes the whole conversation so far (your earlier prompts and the AI’s earlier responses) plus any instructions or files the chat app adds behind the scenes. When you send a new message, it typically gets added to the end of the context window, as does every token the AI writes in reply, so the window keeps growing as the conversation goes on (up to a size limit, at which point the app has to compact or drop older parts of it).
What comes out the other end of the machine is a probability for every token in the entire vocabulary: the model’s estimate of how likely each one is to be the next token, with all of them adding up to 100%.
The model’s job ends at the probabilities, and it never picks a word. Picking the next token is the job of a separate program called the inference runtime, or runner. The runner can take the most likely token every time, or it can roll the dice and pick a token at random, giving each one a chance that matches its probability. We’re used to thinking of AI as nondeterministic: give the same AI the exact same prompt 10 times in a row and you’ll get 10 slightly different answers, sometimes wildly different answers. That randomness is all done in the runner. Give the model the same context window and it produces the same probabilities. Then the runner adds the token it picked to the context window and runs the model again to get the next one.
If you wanted to hide a pattern in an AI’s text that you could detect later, and all you could touch was the probabilities or the runner’s dice roll, how would you do it?
Here’s what I guessed. I’d divide the tokens into two groups, then I’d nudge up the probabilities for one group and nudge down the probabilities for the other. Then, since I’d know which tokens are in the favored group, I could do some pretty basic statistical analysis to figure out whether they show up more often than they should, and if they do, the text is probably watermarked.
That turns out to be a real, well-known watermark called the green list method, from a 2023 paper by John Kirchenbauer and his colleagues at the University of Maryland, “A Watermark for Large Language Models.” They called the favored group a green list, and the rest of the vocabulary a red list. Right before it picks, the runner gives every green token’s probability a boost. The red tokens never get touched, but each one’s share goes down, because the probabilities still have to add up to 100%.
Here’s an example. Say a tiny model only knows five words (cat, tree, the, by, and sat), and it has just read the word the, so it’s predicting the next word. The first probability column shows the probability the model gives each of its five words. Now say tree and by are on the green list for this spot, so the runner boosts those two before it picks. The second probability column shows the probabilities after the boost:
| next word | probability before | probability after the boost |
| cat | 56.3% | 37.9% |
| tree | 20.7% | 37.9% |
| the | 12.6% | 8.4% |
| by | 7.6% | 13.9% |
| sat | 2.8% | 1.9% |
Tree is now tied with cat. The model produced the same probabilities as before, and the runner boosted two of them after the model was done.
My guess missed an important detail, though. The green list can’t be the same every time the runner picks a token. If it were, the same favored words would show up all over the text, and anyone who read enough of it could work out which ones they were. So the runner determines the green list for each token using a secret key mixed with the token right before it. To check for the watermark, take each token in the text, use the key and the previous token to rebuild its green list, and check whether the token is on it. If the green list is half the vocabulary, you’d expect about half the tokens in ordinary text to be green by chance. In watermarked text, a lot more of them are green. A statistical test tells you how unlikely it would be to get that many green tokens by chance. You don’t need the model to check, just the key and the tokenizer.
Anthropic says Claude’s watermark is a version of SynthID-Text, a method Google DeepMind published in Nature in 2024 and uses in its own Gemini app. It works in the runner, just like the green list, but it gets the pattern into the text a different way. Anthropic describes it as a watermark that “only changes the source of the randomness used to pick among words.” So my guess was a real method, but Claude uses a different one.
Here’s the basic idea. Instead of boosting some words’ probabilities, the runner rolls its dice a few times, so it ends up with a few candidates for the next word. Then it flips a coin for each candidate. Whether the coin comes up heads or tails depends on the secret key, the candidate word, and the few words right before it, so anyone with the key can flip the same coin later and get the same result. The runner writes a candidate whose coin came up heads. If every candidate is the same word, there’s nothing to choose between, so the watermark only gets into the spots where the model had a real choice.
To check a text, a detector with the key goes through it word by word, redoes each coin flip, and counts the heads. Ordinary text comes up heads about half the time, and watermarked text comes up heads more often. The real detectors do more than count, but that’s the idea.
That’s kind of involved and hard to picture from a description alone. Luckily, I’ve got a better way for you to understand how watermarking works.
I mentioned that my new book, Be the Model, will be out next year. It starts from the fact that AI tools have gotten incredibly sophisticated, even the web chats like ChatGPT and Claude.ai. They can run Python code for you, and they can write an entire interactive HTML page from a single prompt. So why not use them as learning tools?
That’s one of the main ideas behind the book. You’ll use AI tools to create web pages (which I call “toys”) that let you play with different parts of LLMs, and that helps you get an intuitive feel for how they work. The toys let you literally do part of the job that a model does, so you learn how a model works by being the model.
Each toy starts with a short prompt and a picture of what the page should look like. I figured that for this article, you could build a toy to Be the Watermark. I think this is actually a good way to get a feel for how SynthID actually works.
Save the picture below, then copy the prompt under it, and paste them both into a fresh ChatGPT or Claude.ai chat. (In the book, you aren’t handed canned prompts; you come up with most of them yourself.)
Once the AI finishes building it, you’ll have a page with a short story and a secret key, 3 1 4 1 5. Most of the words in the story have a dropdown with near-equivalent words, like creek, pond, lake, and pool. Click Run, and the page checks the story the same way a detector does. It goes through the story one word at a time and flips each word’s coin. To flip the coin, it multiplies the token IDs of that word and the four before it by the five key digits, adds them up, and calls it heads if the last digit is 5 through 9. (In the toy, a word’s token ID is just its position in an alphabetical list of every word on the page.) In the picture, the page is checking creek. The five words tabby, rested, by, the, and creek have token IDs 62, 48, 8, 63, and 11. Multiplied by the key digits 3, 1, 4, 1, and 5, that’s 186 + 48 + 32 + 63 + 55 = 384, and the last digit is 4, so creek comes up tails. Then the page counts the heads. The starting story comes up heads on 14 of its 32 coin flips, which is about half, so the page shows “No watermark found.”

Paste this four-paragraph prompt along with the picture into your favorite AI (it works great with ChatGPT):
Build one HTML page with a white background that works like the attached picture. Make all of the text, including the button labels and the key digits, a dark color with high contrast against its background. A word’s token ID is its position, counting from 0, in an alphabetical list of every different word in the story and the dropdowns. Ignore case and punctuation.
The story starts: On a sunny day, the tabby rested by the creek. A duck glided over the water. The dog ran to the beach and barked. The toad jumped onto a rock. The bird sang in the tree.
Each word after the first four that’s in one of these groups gets a dropdown with its group: cat/kitten/kitty/tabby, sat/rested/waited/stayed, by/beside/near, pond/lake/pool/creek, duck/goose/swan, swam/paddled/floated/drifted/glided, across/over, dog/puppy/hound/pup, ran/raced/dashed/hurried/rushed, to/toward, shore/bank/beach, barked/yapped/growled/howled, frog/toad, jumped/hopped/leaped/sprang, onto/upon, rock/stone/log, bird/robin/sparrow/wren, sang/chirped/tweeted/whistled, in/from, tree/oak/elm/maple. In an open dropdown, every option shows whether its coin comes up heads or tails in that spot with the current key; a closed dropdown shows just the word.
The coin flip is the sum in the picture: the key digits times the token IDs of the four words before and the word itself. If the sum’s last digit is 5 to 9, it’s heads; 0 to 4 is tails. Check the story one word at a time, starting with the fifth word, animating each product and the growing sum, highlighting the word and the four before it, and counting the heads. A full run takes about 10 seconds. When the check finishes with at least 60% heads, animate a checkmark badge reading “Watermark detected” beside the heads count; otherwise show “No watermark found.” Changing the key or a word clears the heads count. Use only Step, Run, and Reset buttons. Reset keeps the key and the words.
Your job is to be the watermark. When you open a dropdown, it shows whether each word in it would come up heads or tails in that spot with the current key. Swap some tails words for heads words and run the check again. When at least 60% of the coin flips come up heads (20 of the 32), the page shows a “Watermark detected” badge. Every time you pick a heads word from a dropdown, you’re doing the runner’s job. The one difference is that the runner can only choose among the few candidates its dice rolls turned up, so sometimes there are no heads word to pick.
It’s a little harder than it seems because when you swap one word, it changes the coin flips for the next four words too. Each word’s coin flip uses that word and the four words before it, so the word you just swapped is part of the next four sums, and any of those coin flips can come out differently. A few things to know:
See if you can get the page to show a watermark for your story.
Once you get the badge, change the last digit of the key to 6 and run the check again. Your heads count will probably drop back toward half and the watermark badge will disappear, even though the watermark is still there, because the page is checking with the wrong key. (A story can still pass with the wrong key by chance.)
You’ll also notice that the first four words, “On a sunny day,” don’t have dropdowns, and the check doesn’t start until the fifth word. A coin flip needs a word and the four words before it, so the first four words don’t have enough words before them to flip a coin.
If you want to see the math for a particular word, ask the AI that built the page how it calculated whether that word comes up heads or tails. It should walk you through the token IDs, the key digits, and the sum. And if the animation feels slow, you can ask it to redo the page so the animation runs faster. To get the original story back, reload the page.
The toy’s vocabulary has 75 words, and 48 of them, like pool and puppy, don’t show up in the starting story. They’re the near-equivalent words in the dropdowns. A real model’s vocabulary works the same way because it’s fixed ahead of time and any one passage uses only a small part of it.
A story this short also shows why real detectors work better on longer text. With 32 fair coin flips that don’t affect each other, you’d get at least 60% heads about one time in 9, so a badge on a story this short doesn’t prove much. Over hundreds of words, the odds of that proportion of heads by chance get very small.
The toy is a lot simpler than the real thing. Real token IDs aren’t alphabetical. Real SynthID uses a much bigger key, mixes the key and the words together with a hash function instead of a sum, and plays several rounds of coin flips for every word instead of one. And its detectors weigh those rounds differently and are trained on watermarked and ordinary text for each key, instead of just counting heads.
You just did the thing the AI companies are worried about. With the key, you could see which words came up heads and swap them, and the same trick works in the other direction: Someone with the key could strip the watermark out of AI text or write text that’s heavy on heads on purpose and make something a person wrote look like Claude wrote it. If the companies made their keys public, someone could easily write a watermark detector for your favorite text editor that fixed the text to remove the watermark, and that would defeat the whole purpose.
That’s likely why they keep their keys to themselves, and why right now only they and a few organizations they’ve approved can check for the watermark. I don’t know whether or not I agree with that reasoning, but I can understand that the issue is complicated. In the meantime, I’m applying for access to Claude’s detector (hence the “yet” in the title of this article).
Pluralistic: Lisa Hanawalt's "I Can't Stop Thinking About Horses and Sex" (20 Nov 2026) [Pluralistic: Daily links from Cory Doctorow]
->->->->->->->->->->->->->->->->->->->->->->->->->->->->->
Top Sources: None -->

The title of animator Lisa Hanawalt's new graphic memoir I Can't Stop Thinking About Horses and Sex is a perfect encapsulation of the book's contents: a frank, self-aware, funny, horny, horsey exploration of Hanawalt's life, relationships, gender, and digestive issues:
https://drawnandquarterly.com/books/i-cant-stop-thinking-about-horses-and-sex/
Hanawalt is probably best known as the character designer for Bojack Horseman, but is also much loved in animation circles for her all-too-short-lived show Tuca & Bertie:
https://en.wikipedia.org/wiki/Tuca_%26_Bertie
She lived with the comedian/podcaster/showrunner Adam "Ruins Everything" Conover for 14 years, and the memoir revolves around the couple's breakup.
As the title promises, Hanawalt is also a lifelong horse-lover, who spent her childhood developing scars on her knees and calluses on the tops of her feet from endless all-fours sessions of pretending to be a horse. As an adult, she rides at the Los Angeles Equestrian Center, where she meets other horse people, who are beautifully depicted as the mix of posh sociopaths, obsessive animal-lovers, and lovable misfits (my daughter's middle school was around the corner from the LAEC and she grew up shoveling manure and tacking up at a teaching barn there; I can vouch for Hanawalt's faithful portrayal of the vibe).
Horses are Hanawalt's touchstone, the thing that brings her thoughts and emotions back into equilibrium, no matter what life throws at her. Eventually – inevitably – she acquires a horse, and just as inevitably, that horse proves to be her savior and her heartbreak. Horses are massive, majestic, impossibly powerful animals that are nevertheless forever on the verge of death, one weird disease or inexplicable fall from being maimed for life or keeling over.
The story of Hanawalt's pony Juni is intertwined with the story of her and Conover's breakup and her post-breakup relationships. Both threads of the tale are developed through beautiful, extremely funny, deeply personal vignettes that are brought to life by Hanawalt's art, which depicts bodies (animal, human, and animalistic human avatars) as hilarious, weird, and sexy all at once.
These two motifs criss-cross as we journey through Hanawalt's dating life, her childhood sexual trauma, her IBS, and her fears and hopes about her fertility (two of the major subplots involve Hanawalt's experiences with egg-freezing and bowel problems, and the way that the medical system treats women).
Hanawalt has a gift for compact, revealing character studies that leave the reader feeling both warm affection and exasperation with everyone in her life (including Hanawalt herself). It's a world without heroes and villains, where flaws and virtues are almost always flip-sides of the same coin. Everyone is crazy sometimes, including Hanawalt, and Hanawalt is self-aware enough to know when she's getting in her own way, and even why that happens, and also (just like all of us) can't always stop herself from tripping herself up.
Hanawalt's written and drawn a wise, funny, horny book that wrings comedy and insight out of trauma and melancholy. It's a gorgeous read that lingers.
Hanawalt isn't the only person who made smart, funny media out of her and Conover's breakup. Conover's comedy special about the breakup and its aftermath is called "Big Divorce Energy" and it was released the same week that Can't Stop Thinking hit the shelves:
https://www.youtube.com/watch?v=CVB-SUX7zgk
I saw Conover perform this set live and it was terrific – and it got even better by the time he recorded it for the special. It makes for a perfect bookend for Hanawalt's memoir, a fact that both Conover and Hanawalt affirm in a lovely, warm conversation they recorded for Conover's Factually podcast. It's an interview that raises the bar for the kind of affection and even love a mature couple can salvage from a breakup:
https://www.youtube.com/watch?v=BUXEDUiICM4
The book itself is from Montreal's Drawn and Quarterly, who have a well-deserved reputation for publishing quality graphic novels, especially memoirs. D&Q always puts together a beautiful physical artifact, and Can't Stop Thinking is no exception: a handsome hardcover with luxurious, thick semi-matte pages and a bookmark ribbon sewn into the binding. It's the perfect gift for any friend going through a breakup (or thinking about buying a horse).

Anthropic’s Meh Debut https://prospect.org/2026/11/20/anthropic-debut-ipo-stock-market-sec/
#25yrsago They Fight Crime https://web.archive.org/web/20011204174257/http://www.rain-street.org/fightcrime.htm
#20yrsago GeekCorps builds cantenna WiFi TV network in Mali https://web.archive.org/web/20061213100911/http://www.geekcorps.org/2006/11/the-geekcorps-cantv/
#15yrsago Britain’s Occupy movement picks up steam https://web.archive.org/web/20131001063502/https://www.theguardian.com/uk/2011/nov/19/occupy-london-protesters-ideas-bank
#10yrsago Word of the day: Kakistocracy http://jury.me/blog/2016/11/19/kakistocracy
#5yrsago Inflation or price-gouging? https://pluralistic.net/2021/11/20/quiet-part-out-loud/#profiteering
#1yrago The long game https://pluralistic.net/2025/11/20/if-you-wanted-to-get-there/#i-wouldnt-start-from-here

Sheffield: Reverse Centaur at Juno Books, Nov 25
https://www.outsavvy.com/event/40274/cory-doctorow-in-conversation
Virtual: Enshittification, AI, and the Future of Technology (UBC
Master of Educational Technology), Nov 28
https://met.ubc.ca/2026/09/met-speaker-series-cory-doctorow-enshittification-ai-and-the-future-of-technology/
Oxford: Bennett Oxford Symposium on Open Code in Science, Dec
9
https://www.bennett.ox.ac.uk/events/2026-bennett-institute-symposium/
Santa Barbara: UCSB Reads, Apr 29
https://www.library.ucsb.edu/events-exhibitions/ucsb-reads-2027-presents-author-cory-doctorow
Montreal: World Science Fiction Convention, Sep 2-6
https://montreal2027.ca/en
How AI is Breaking the Internet (and Everything Else) (Blood in
the Machine)
https://www.youtube.com/watch?v=mXRaPjFRyT0
Clint Eastwood (No Gods No Mayors)
https://www.patreon.com/NoGodsNoMayors/posts/clint-eastwood-173008088
Life After AI (Brain Bar)
https://www.youtube.com/watch?v=IPPa43-n0vI
Terms of Service with Clare Duffy (CNN)
https://www.cnn.com/audio/podcasts/terms-of-service-with-clare-duffy/episodes/458ce968-af5d-11f0-b539-13ed2afe25f8
"Canny Valley": A limited edition collection of the collages I create for Pluralistic, self-published, September 2025 https://pluralistic.net/2025/09/04/illustrious/#chairman-bruce
"Enshittification: Why Everything Suddenly Got Worse and What to
Do About It," Farrar, Straus, Giroux, October 7 2025
https://us.macmillan.com/books/9780374619329/enshittification/
"Picks and Shovels": a sequel to "Red Team Blues," about the heroic era of the PC, Tor Books (US), Head of Zeus (UK), February 2025 (https://us.macmillan.com/books/9781250865908/picksandshovels).
"The Bezzle": a sequel to "Red Team Blues," about prison-tech and other grifts, Tor Books (US), Head of Zeus (UK), February 2024 (thebezzle.org).
"The Lost Cause:" a solarpunk novel of hope in the climate emergency, Tor Books (US), Head of Zeus (UK), November 2023 (http://lost-cause.org).
"The Internet Con": A nonfiction book about interoperability and Big Tech (Verso) September 2023 (http://seizethemeansofcomputation.org). Signed copies at Book Soup (https://www.booksoup.com/book/9781804291245).
"Red Team Blues": "A grabby, compulsive thriller that will leave you knowing more about how the world works than you did before." Tor Books http://redteamblues.com.
"Chokepoint Capitalism: How to Beat Big Tech, Tame Big Content, and Get Artists Paid, with Rebecca Giblin", on how to unrig the markets for creative labor, Beacon Press/Scribe 2022 https://chokepointcapitalism.com
"Unauthorized Bread": a middle-grades graphic novel adapted from my novella about refugees, toasters and DRM, FirstSecond, April 20, 2027
"Enshittification, Why Everything Suddenly Got Worse and What to Do About It" (the graphic novel), Firstsecond, 2027
"The Memex Method," Farrar, Straus, Giroux, 2027
Today's top sources:
Currently writing:
"The Post-American Internet," a sequel to "Enshittification," about the better world the rest of us get to have now that Trump has torched America. Fourth draft completed. Submitted to editor.
A Little Brother short story about DIY insulin PLANNING

This work – excluding any serialized fiction – is licensed under a Creative Commons Attribution 4.0 license. That means you can use it any way you like, including commercially, provided that you attribute it to me, Cory Doctorow, and include a link to pluralistic.net.
https://creativecommons.org/licenses/by/4.0/
Quotations and images are not included in this license; they are included either under a limitation or exception to copyright, or on the basis of a separate license. Please exercise caution.
Blog (no ads, tracking, or data-collection):
Newsletter (no ads, tracking, or data-collection):
https://pluralistic.net/plura-list
Mastodon (no ads, tracking, or data-collection):
Bluesky (no ads, possible tracking and data-collection):
https://bsky.app/profile/doctorow.pluralistic.net
Medium (no ads, paywalled):
Tumblr (mass-scale, unrestricted, third-party surveillance and advertising):
https://mostlysignssomeportents.tumblr.com/tagged/pluralistic
"When life gives you SARS, you make sarsaparilla" -Joey "Accordion Guy" DeVilla
READ CAREFULLY: By reading this, you agree, on behalf of your employer, to release me from all obligations and waivers arising from any and all NON-NEGOTIATED agreements, licenses, terms-of-service, shrinkwrap, clickwrap, browsewrap, confidentiality, non-disclosure, non-compete and acceptable use policies ("BOGUS AGREEMENTS") that I have entered into with your employer, its partners, licensors, agents and assigns, in perpetuity, without prejudice to my ongoing rights and privileges. You further represent that you have the authority to release me from any BOGUS AGREEMENTS on behalf of your employer.
ISSN: 3066-764X
The history behind the x86 CPU: from 4004 to 486 [OSnews]
Why is x86 little-endian? Why are the registers called AX, BX, CX, and DX? Why do DOS programmers write addresses like A000:0000, and why does a modern PC still wake up pretending to be a chip from 1978? The answers are not in the datasheets. They are in the story of how each chip was born.
↫ Gustavo Pezzi
The x86 is like an archaeological dig site that’s been dug in the 1800, before modern standards of dig sites were established to preserve context.
FreeBSD GUS: RCU’s cool cousin [OSnews]
FreeBSD has a pretty neat safe memory reclamation scheme (something akin to RCU), that’s also been adopted by XNU that hasn’t really been well-documented outside of code comments, and I thought it would’ve been interesting to write about it.
↫ Loïc Grégoire
Some light reading for the weekend.
Messing with the thermostat [Seth's Blog]
No matter how high you turn the thermostat, your house will take just as long to get to 72 degrees.
Second metaphor: You can’t make a pizza faster in a 2,000 degree oven. In fact, you’ll incinerate it, not cook it.
Third metaphor: Two people can have one conversation and meet each other. For a group of 11, it’s 55 conversations.
Fourth metaphor: It’s easier to salt bland food at the table than to fix over-salted food in the kitchen.
PS Next week in the US is Thanksgiving. But wherever you are, I hope you’ll enjoy the Thanksgiving Reader, an annual tradition designed to be shared.
New Comic: Womp Womp
Girl Genius for Friday, November 20, 2026 [Girl Genius]
The Girl Genius comic for Friday, November 20, 2026 has been posted.
Hunting, p07 [Ctrl+Alt+Del Comic]
The post Hunting, p07 appeared first on Ctrl+Alt+Del Comic.

Hello, I have a new album of music out. If you like 15 minute long instrumental post-metal songs played on guitars with too many strings, you might enjoy it. You can listen to it and buy it here. Thank you
Outage Chaos: Who Turned Off All The Computer? [Deeplinks]
It's been a tough couple of weeks for anyone trying to use email, fly, spend money, use an Apple device*, or do signals intelligence. Technical service outages are nothing new, but why do so many big ones seem to be happening all at once? Are hackers, AI, and international conflicts to blame? And what can we do about it?
Since most service interruptions don't make the news, it's hard to get a baseline on how often we see them happen normally. But after a major incident like the Microsoft cloud outage on November 12, any smaller disruption is more likely to become a story as part of a pattern instead of an isolated incident. We would have heard plenty about the Air Traffic Control problems anyway, but the November 18 disruption to the PlayStation Network might have gotten less attention. There might appear to be a spike or an upward trend in outages, but we can't easily verify that, and the increased coverage will tend to make it seem more significant and interconnected than it necessarily is regardless.
One boring reason we might see an uptick in problems right now is the date on the calendar. With Thanksgiving travel, Black Friday, Cyber Monday, Giving Tuesday, and Surveillance Sunday (we assume) all coming up, organizations often schedule major system updates for the first three weeks of November. This helps them prepare for holiday traffic, and lets them shift the outage risk to the time before those dates when they may consider it far more important to maintain reliable service.
While none of these particular outages have yet been directly attributed to AI (or to malicious hackers), bank CEOs and the NSA briefed congress and reportedly attributed at least some of them to rushed attempts to patch vulnerabilities found by AI. That’s understandable: all software updates carry risk, and companies and governments are having to deploy more updates, and faster, than they’ve ever needed to before. Some of those updates are to important infrastructure, where an outage would be very disruptive, but the impact of leaving vulnerabilities unpatched would be even worse.
Vulnerabilities are a type of software bug that affects security. Once a vulnerability is found in a given piece of software and disclosed, typically the software maker will release a patch fixing that vulnerability. That’s why so many update notes say things like “performance improvements and security fixes” — the security fixes are patches to vulnerabilities.
Companies and governments that run infrastructure face a challenging tradeoff: deploy patches quickly or slowly and cautiously? Patching quickly is important to keep systems secure. But every software update runs a risk: any change to a deployed system can have unintended consequences that snowball into a disastrous outage.
This exacerbates a much deeper problem long discussed in the engineering culture of many, if not most organizations. Keeping networks, servers, and applications not just secure but resilient in the face of patches, reboots, and capacity changes requires an investment in staff, time, hardware, and processes for frequent maintenance, redundant systems, realistic staging environments, automated rollbacks, monitoring, and pre-deployment testing. These investments are rarely as attractive to decision-makers as a new product or feature, or at times, sadly, as layoffs.
This should come as no surprise when we think of our apps, web sites, airlines, and bank cards as supported by electronic infrastructure. As in the more visible physical world, maintenance can only be deferred for so long before the costs become immediate and dramatic. We accept the cost of an occasional short term bridge closure to reduce the risk of a bridge collapse, and highway departments schedule road work nearly every night of the year to repair and prevent the worst potholes.
When this kind of work is endlessly deferred in the world of software, we speak of technical debt: issues we already know about that aren't causing a big enough problem right now to divert us from other work, but that, if left unaddressed, can easily multiply and interact to cause outages or other complications. This can show up as routine steps that have to be done by hand instead of automatically on a schedule, a programmer's shortcut that works well in one specific situation but is more fragile in general, an operating system six months (or years) overdue for a reboot, or a piece of networking hardware no longer supported for patches by its manufacturer. On the other hand, when maintenance work is well-resourced and routine, it should be rare for even major security updates to cause significant issues.
What’s needed in the short term is a big investment in the people and training needed to roll out patches promptly and safely. What’s needed in the long term is a big investment in software security, eliminating entire classes of vulnerabilities, like memory safety, before they are ever written.
For organizations that have gotten used to patching slowly and cautiously, suddenly switching gears to patching quickly is a big challenge. And the flood of vulnerability disclosures enabled by AI means that everyone is being asked to switch gears like that at once.
Fortunately, it’s not a zero-sum game: patches can be rolled out quickly and cautiously, with investments in reducing technical debt and expanding maintenance budgets as described above. These measures are expensive and time-consuming, but necessary. For governments asking how to respond to AI-enabled cybersecurity threats, investing in the people and training necessary to stay on top of patches will pay big dividends in reliability and security.
For individuals, consider the trade-offs when relying on a single provider for many services you rely on. Consumer cloud and device offerings tie together many of the things we need to function on a daily basis like email, messaging, file storage, and even payments, but that convenience and simplicity comes with the risk of losing access to it all if that service goes offline (or suspends your account). Trying out interoperable alternatives is a great way to reduce your reliance on a single company.
Finally, for any critical data, learn the 3-2-1 rule for backups: Keep three different copies on two different types of storage with one copy in a different physical location. For many users, a laptop or other personal device, cloud storage, and a local backup disk exemplify this rule, as long as the laptop stores data on its own drives, not only in the cloud.
Among other things, the accelerated rollout of AI has made it all the more critical to reinvest in people and systems to keep our software, networks, governments, and interconnected world stable.
*Apple is an EFF donor. EFF donors do not influence our agenda or our positions.
The Big Idea: Melissa Poett [Whatever]

What’s better than a whip-smart, whip-wielding protagonist? One who uses those skills to combat injustice and help those in need. Robin Hood fans rejoice, for author Melissa Poett has brought us a dystopian, femme-fatale retelling, without the merry men. Clutch your coin purses and follow along in the Big Idea for A Thief to Die For.
MELISSA POETT:
When you hear the name Robin Hood, perhaps you think about a revolution. Or maybe it’s more specific—you think of a medieval man who was radicalized to defend the powerless against the tyranny of the corrupt elite. A hero. A leader. Maybe even a criminal, an outlaw who was willing to break the rules to right the scales of justice in a tale as old as time, and one that, unfortunately, remains timely.
I, too, think of all those things. And yet, I was also left with a question: how would that story have unfolded differently if the same revolution was led by a woman?
More specifically, Marian.
A Thief to Die For is my reimagining of Robin Hood set in a dystopian world. It’s about a whip-wielding Marian who has made it her mission to sabotage her tyrant father, while risking the kind of love wars are fought over.
True to the original legend of Robin Hood, injustice is the catalyst. Except, it wasn’t killing a deer in the King’s forest or a fight with the sheriff’s men that started this rebellion. In A Thief to Die For, Marian is radicalized by growing up under her horrific father—a tyrant who runs a slave operation in a coal mine. And her simmering rage is why she steals from his wagons to help the people trapped under his control.
But this is where the story you know and love takes an unconventional turn. Where Robin Hood showcases his mastery of the bow and arrow while recruiting an army of charismatic men to fight with him, Marian’s path as the heroine looks quite different. I imagine she would move through the world sacrificially—like a woman.
This isn’t a spoiler, so don’t worry. But it is the foundation to Marian’s character. In a world where she can’t dethrone her father without bringing the house of cards down, she must think outside the box. Move strategically. Outsmart the powerful, while prioritizing the weakest around her. She’s an everyday woman considering all the consequences of a confrontation, and every way it could go wrong. Is she capable of violence? Yes, occasionally. Especially when she secretly raids. Is she excellent with her weapon of choice—a whip? Most definitely. But as any number of women can tell you, there’s a moral burden we carry that isn’t seen in the original folktale of Robin Hood. It means Marian’s revolt is exercised in the shadows as she prioritizes the protection of the people around her. There is no ever-growing army of people joining her rebellion. Marian sacrifices herself by raiding alone.
Which brings me to the next significant shift in the narrative, an epic love story. Yes, I can hear you reminding me that the original folktale did include romance. You’re right; Robin Hood got the girl in the end. But I’m not talking about some proverbial cherry on top of an already half-eaten sundae. I’m talking about an epic love so foundational to the story that it’s as consequential as taking down the villain. Give me yearning. Break my heart.
Now that’s the kind of reimagining I want to read—a story of Robin Hood, a revolution reimagined. But this time through the lens of Marian’s sacrifice and epic love.
—-
A Thief to Die For: Amazon|Barnes & Noble|Bookshop|Powell’s|Canada Pre-order|UK Pre-order
Francesco Paolo Lovergine: Terramaster NASes with Debian, take three: scaling up. [Planet Debian]
As is often the case in scientific environments, IT solutions grow chaotically, often guided by available funds at the wrong moments, or transient choices for transient goals. Here at work, we are not an exception. Historically, since the birth of the Copernicus European project, the Earth Observation domain has become progressively more demanding about storage, due to the frequency and size of satellite acquisitions, available free of charge for research groups, free to access, but not without maintenance and processing costs, of course.
As a result, we have progressively explored low-cost solutions for downloading and processing Sentinel constellation time series. Over a ten-year window, our needs moved from dozens of terabytes to hundreds of terabytes. We started with simple Synology-based solutions, very optimistically, only to discover that the optimism was not justified. When storage needs to scale up, there are no easy solutions.
The only comparable IT environments are HPC clusters, which operate at a completely different order of magnitude in terms of funding. In that context, the Petabyte order of magnitude is generally achievable by using proprietary/FOSS distributed POSIX filesystems such as GPFS, Lustre, or even Ceph. None of them are exempt from problems from time to time. The sad reality is that maintaining a very large POSIX filesystem requires compromises, and no single solution fits all requirements, starting from cost to flexibility, scalability, and reliability. I wrote about the hidden costs of maintaining self-hosted storage solutions here
Almost ten years ago, we chose GlusterFS as an acceptable compromise for a distributed POSIX filesystem. It is not object storage, but a pure POSIX filesystem with a simple architecture, which fits our environment, where most people rely on the folders-and-files abstraction to organize their data. All nodes and their bricks are equal (no dedicated metadata nodes) and can scale without major limitations with a reasonable number of nodes. In our experience, the real bottleneck is network speed, which can introduce high latency and cause cache issues.
We are now finally moving our old Synology-based distributed filesystem to a pool of TerraMaster U12-500 Plus units, installed with Debian 13. Compared with TerraMaster SOHO products, these rack-mount units can run without any non-free firmware. You must manually enable the usual 9000 MTU jumbo frame for the 10Gb network, which is generally required on all connected hosts and also the switch (in our case, a MikroTik box) to properly manage full bandwidth. We measured average performance around 200MB/sec, which aligns with the average sequential speed of 6Gb SATA HDDs.
Regarding using GlusterFS, the most obvious choice is to use it with XFS as the filesystem for the NAS bricks; this proved in practice to be the optimal configuration, after not-too-nice experiences with Btrfs on Synology DSM. Still, it requires some tuning for periodic checks across the various layers of the storage system. One is about short/long HDD testing, which I already covered in another post. A trickier aspect is managing possible bit rot in the brick filesystems from time to time. While Btrfs, with its COW management, can run low-impact scrubs on both metadata and data, XFS can only partially do the same for metadata through xfs_scrub, which is also, as clearly stated, an experimental feature to use at your own risk. In that regard, it is much better to run GlusterFS scrubbing instead.
While xfs_scrub is as light as the SMART short self-test for HDDs, both RAID checks and GlusterFS bitrot scrub are heavy operations that should run rarely to avoid stressing HDDs and systems, and never at the same time. It is mandatory to avoid overlapping all such operations, and that’s a good reason to use systemd timers and run the heavy checks in alternating months.
One suboptimal aspect of our solution is the absence of direct LED control for HDDs, which is unfortunately available only under TOS with a proprietary driver. This is obviously required for disk replacement from time to time, when needed. On the other hand, software support is extended to the lifetime of the Debian distribution, with major upgrades every 3-4 years on average. Also, this is much more flexible and efficient than using pre-built custom OSes. Of course, if you prefer dashboards and the usual GUI candy, this isn't a viable choice; a better option would be TrueNAS, which has a much higher memory footprint, especially when paired with OpenZFS.
[$] Added indirection allows for larger BPF programs [LWN.net]
The BPF verifier has historically worked by tracing every possible path of execution through a program, checking, at each instruction, that various safety properties hold. This works, but it can result in an exponential increase in the number of states that need checking in programs with complicated control-flow. Alexei Starovoitov, one of the kernel's core BPF maintainers, has shared a patch set that substantially reworks how the verifier tracks states, in order to reduce the size of that exponential explosion.
PostgreSQL 19 released [LWN.net]
The PostgreSQL Global Development Group has announced the release of PostgreSQL 19. Notable features in this release include the introduction of the REPACK (CONCURRENTLY) command to optimize tables without disruption to ongoing operations, better control over plan stability and query performance with the new pg_plan_advice extension, and a number of performance improvements.
In September, LWN covered the removal of several features initially slated for this release. See the release notes for a full list of new features and changes.
CodeSOD: A Living Fossil [The Daily WTF]
Today's anonymous submission is a blast from the past. This comes from an intranet HTML page that has been receiving continuous updates for some time. How long? Well, let's take a peek at how it does its layout.
<b>Extension:</b> x5555<br />
<b>Email:</b>: <a href="mailto:blahblah@example.com"></a><br /><br />
</td>
<td width=140>
</td>
</tr>
<tr><td> </td></tr>
<tr><td> </td></tr>
</td>
</table>
</center>
<!-- END DIRECTORY -->
<tr><td><br /></td></tr>
</td>
</tr>
</table>
<!-- MATERIAL ENDS HERE -->
<br />
<br />
</td>
</tr>
</table>
</center>
</td>
</tr>
<tr><td width=987 height=4 background="../images/table_bottom_sidebar.jpg"></td></tr>
</table>
This is like a coelecanth, or a horeshoe crab. A living fossil. There are hints that imply this started life as the output of a WYSIWYG editor, like Dreamweaver or something. The loads of line break tags, the table cells that contain only a space, and also the one table cell that contains a line break- that feels like a WYSIWYG trying to interpret what the user types. But the comments imply someone was also looking at the HTML code at some point. And certainly, in the modern era, it is being edited by someone with a text editor.
The absence of CSS might point us towards a late 90s website, as
by the early 00s, CSS was starting to become standard, but the
thing that really pins this in a point in time is the XHTML style
self-closing <br /> tags.
But then little quirks highlight that someone was also getting
"creative" with code. The table_bottom_sidebar.jpg had
related images, all designed to put borders in the table. There
were matching images for left, right, and top borders.
Our submitter adds: "Needless to say, this site is being replaced."
Replaced? It should get a historical marker. This is how we used
to do it, in the bad old days. We'd add <br
/> while churning butter in homespun dresses,
and we liked it.
Okay, we didn't like it. But still.
Podcast: Make the United States the United States again. The energy unleashed in the 2026 election is becoming the property of two congressional leaders nobody can stand to listen to. Same old Democratic Party. And in this election, the voters didn't want change, which is what the pundits conclude, always, every damn election. This time what we want is what the title of this podcast says.
unrtf 0.21.13 and 0.21.14 [Planet GNU]
0.21.13, released a few weeks ago and 0.21.14 fix buffer
overflow issues.
Version 8.6.0 of PHP has been released. Notable changes in this release include a polling API, a new clamp() function, a SortDirection enum, and a \Time\Duration class. See "What's new in 8.6" for more on new features, and the changelog for a full list of changes.
A tweet I wrote yesterday that's worth preserving a link to.
BonBon is podcasting for text [Scripting News]
Four docs developers should download and give to their AI assistants. Then your helper can answer a lot of questions about what BonBon does now, and what it will never do.
We put a lot of thought into how this new web should start and how it can preserve its independence in the future. The key is user expectations, and you don't need a lot of users to set the DNA for a new movement. In this case, we're clear on the power of writers and readers. The platform respects both equally.
As a writer, when you adopt BonBon, you're sending a clear message to the writing world such as it exists today, that you want them to interop with the other social networks, the same way podcasting set a standard, and we don't have any silos in that world. None. They can't take root because the users expect to get their radio from "wherever you get podcasts." We're going to be doing the same with writing in the future, which is actually here now. Expectations are key.
I'm so proud of podcasting, and totally lament we haven't taken care of text as well. It's not too late to start.
As we used to say on this blog -- Zoooooooom!
Four PHP security releases including fixes for critical vulnerabilities [LWN.net]
The PHP Project has announced the release of PHP 8.5.13, 8.4.28, 8.3.37, and
8.2.36.
Each contains a number of security and bug fixes, including several
fixes for critical vulnerabilities that could allow remote-code
execution. According to the project's pre-release
announcement on November 18, all of the vulnerabilities of
critical severity "require either non-default configuration or
uncommon setups
". See the release notes for details; Linux
vendors and projects should be releasing updated packages soon.
Security updates for Thursday [LWN.net]
Security updates have been issued by AlmaLinux (cockpit, cockpit-files, cockpit-machines, gimp, glib-networking, krb5, libpcap, nginx, nodejs26, perl-CGI, php8.4, skopeo, tigervnc, and xorg-x11-server), Debian (haproxy, libreoffice, libvisio, needrestart, openjdk-21, and openjdk-25), Fedora (asterisk, erlang, ffmpeg, ignition, libosmocore, luksmeta, msedit, openapv, passwordsafe, rabbitmq-server, sngrep, and vyper), Mageia (firefox, nss, rootcerts, rsync, and thunderbird), Slackware (libfontenc and libXfont2), SUSE (389-ds, apache2, aspell, bind, brotli, busybox, civetweb, containerd, cosign, docker, gleam, glibc, graphicsmagick, helm, ignition, ImageMagick, java-17-openjdk, java-21-openjdk, java-25-openjdk, jhead, kernel, kubernetes, libsofia-sip-ua-glib3, mcphost, perl-HTTP-Body, perl-MIME-tools, phodav, python-asyncssh, python-django, python-joserfc, python315, qemu, rootlesskit, roundcubemail, rsyslog, runc, tempo-cli, trivy, and xorg-x11-server), and Ubuntu (cloud-init, gstreamer1.0, hplip, libcpanel-json-xs-perl, linux, linux-aws, linux-aws-5.4, linux-aws-fips, linux-azure-5.4, linux-azure-fips, linux-bluefield, linux-fips, linux-gcp, linux-gcp-5.4, linux-gcp-fips, linux-hwe-5.4, linux-ibm, linux-ibm-5.4, linux-iot, linux-kvm, linux-oracle-5.4, linux-raspi, linux-raspi-5.4, linux-xilinx-zynqmp, linux, linux-aws, linux-kvm, linux-lts-xenial, linux-azure, linux-oracle, linux-azure-7.0, linux-fips, nginx, openjdk-17, openjdk-21, openjdk-25, openjdk-27, and openjdk-lts).
Pluralistic: How to forfeit one of copyright's best labor policies (19 Nov 2026) [Pluralistic: Daily links from Cory Doctorow]
->->->->->->->->->->->->->->->->->->->->->->->->->->->->->
Top Sources: None -->

There's a seeming paradox to copyright. For 50 years (starting with the 1976 Copyright Act) legislatures have monotonically expanded copyright, so that today, copyright lasts longer, covers more works, restricts more activities, and provides for harsher penalties for infringement, all in the name of protecting artists.
After 50 years of this, artists are, on average, poorer than we were in 1976, but the media companies we sell our work to are much, much richer. They're larger and more profitable, and yet our wealth (both in absolute terms and as a share of media company profits) has declined.
This may feel like a paradox, but it's actually easy to understand unless you've had the self-inflicted neurological injury we call "getting an econ degree." That's an injury that leaves the sufferer incapable of reasoning about or even perceiving power.
If you've avoided that fate, then you can see that when an artist sells to one of five publishers, four studios, three labels, two app companies or one ebook/audiobook company, that artist has very little leverage. In that market, giving an artist more to bargain with is just giving them more to bargain away.
I have often compared giving more copyright to creative workers trapped in this oligopoly to giving a bullied schoolchild extra lunch money. No matter how much money you give that kid, they're not going to get fed. The bullies just take whatever money you give to the kid. Indeed, if you indirectly transfer enough money to the bullies, they'll pay for a global ad campaign: THINK OF THE HUNGRY SCHOOLCHILDREN! THEY NEED MORE LUNCH MONEY!
This is exactly what has happened with 50 years of successive copyright expansions. Every time Congress gave a new copyright to creative workers, the cartels we bargain with just amended their non-negotiable contracts to force us to hand over that new right for no extra payment. Then they used those new rights to get richer and more powerful, and to exert more control over the distribution channels we need to reach our audiences, which made us poorer. Then Congress heard their THINK OF THE STARVING ARTISTS pitch, and gave us more copyright…which we promptly handed over to our bosses. Lather, rinse, repeat.
If you want to feed a hungry schoolkid, you have to change the structure of the system. For example, you might open a credit account with the school lunchroom, so that the kid never has any cash for the bullies to take. Likewise, if you want to help artists get more money, you need to make a systemic change.
There are lots of ways to do this. In 2022, Rebecca Giblin and I co-wrote a book called Chokepoint Capitalism, and we devoted half of the book to detailed, shovel-ready proposals for ways to alter the copyright system to benefit artists, not our bosses:
https://www.beacon.org/Chokepoint-Capitalism-P2020.aspx
That section includes a chapter on something called "termination of transfer," which was introduced with the 1976 Copyright Act. Under termination of transfer, any copyright contract (a "transfer") can be unilaterally canceled ("termination") by any creator after 35 years. So even if you sign away your copyrights for the entire term (your life plus 70 years), you can tear up that agreement after 35 years by notifying the company you sold your rights to and then filing some paperwork with the US Copyright Office:
https://pluralistic.net/2021/09/26/take-it-back/
We got really excited about termination. For one thing, Rebecca is one of the world's leading experts on the subject. In 2021, she co-authored the landmark study "U.S. Copyright Termination Notices 1977-2020: Introducing New Datasets," published in the Journal of Empirical Legal Studies:
https://papers.ssrn.com/sol3/papers.cfm?abstract_id=3880708
Termination is a uniquely efficient way to make artists richer at the expense of our bosses. The fact that you can only exercise it after 35 years produces some very interesting effects. First, consider that almost no copyrighted works are commercially viable after 35 years (most copyrighted works cease to generate income after 14 years or less, this being the original term of copyright in the USA). The rare works that continue to generate revenue 35 years after their release are the "perennial favorites" that drive a vast share of media industry profits.
Now consider that, between the realities of the human lifespan and the amount of time it takes most artists to master their craft, any given work you produced 35 years ago is almost certainly from the start of your career. That's the moment in which artists are typically most vulnerable. Artists at the start of their careers are unknown quantities and are often crammed into signing terrible deals, even worse than the "standard" media deal.
Put these two facts together and you'll see that termination is disproportionately applicable to a body of work that is wildly profitable for media companies, but the creators of those works are entitled to even less of the money it generates, thanks to the crummy contracts they were railroaded into because they were just starting out when they made them.
Termination lets creators cancel those crummy contracts, take back their rights, and bargain for a better deal with the old media company (or a new one). This time, they bargain from a position of unassailable strength, due to the fact that they're selling a property that's proven itself to be a perennial profit-generator.
Best of all, you can't bargain out of termination. Even if you sign a contract that says, "I promise I will not exercise my termination of transfer right," you can still exercise your termination right. This is a structural change, like the parent who opens a charge account with the school cafeteria so that their kid no longer has any lunch money to hand over to the bullies. The way Congress wrote termination into the 1976 Act, it doesn't matter how hard the media company you initially sign with twists your arm, you literally can't promise them you won't use your termination right 35 years after signing.
That's where that landmark study Rebecca co-authored comes in. Rebecca and her co-authors found that termination was working exactly the way Congress intended: it was making artists richer. It's particularly helpful to marginalized creative workers, for example, Black "heritage" musicians who were railroaded into terrible contracts that meant they never got a dime for decades of airplay, covers and samples of their hits. If this sounds familiar, you might be thinking of my 2024 technothriller The Bezzle, where I use this as a key plot point:
https://us.macmillan.com/books/9781250865878/thebezzle/
Genre writers have really benefited from termination. The authors of massively popular YA series like The Baby-Sitters Club and Sweet Valley High claimed back their rights under termination. So did Peter Straub and Stephen King, who took back the rights to their early books and resold them on much more favorable terms. Just the threat of termination forced Disney to make giant payouts to Marvel's key creators, like Stan Lee, Steve Ditko and Jack Kirby:
https://deadline.com/2023/12/marvel-court-termination-disney-spider-man-dr-strange-1234843941/
In Chokepoint Capitalism, Rebecca and I point out that most of the 1976 Copyright Act (like longer copyright terms) has failed to help artists, but termination is the rare exception, a proven effective way to put money in artists' pockets. Which is weird, because in the 50 years since the 1976 Act, Congress has repeatedly doubled down on pretty much every measure in the Act, except the one thing that is empirically proven to be good for artists. Of course, all that failed stuff in the 1976 Act is good for giant media companies, and termination is bad for those companies, so it's not hard to see why there's been so little legislative appetite to beef up termination.
But it's also easy to see how we'd do that beefing up. In the original draft of the Copyright Act, termination was automatic, and kicked in after 20 years (meaning that 20 years after signing any contract, every creator would automatically get back all the rights they sold in the contract). The final version of the Act watered down termination so it kicks in after 35 years, and even then only after the artist does a ton of paperwork.
Giving artists the termination rights they were promised in the initial draft of the 1976 Act is a no-brainer. But that's not what we've gotten from Congress. To the extent that Congress acted on termination, it was to take it away from musicians. In 1999, an obscure Congressional staffer named Mitch Glazier snuck a clause into an unrelated bill that made it impossible for most recording artists to exercise their termination rights. This was such a scandal that Congress had to convene a special session to cancel this amendment and restore musicians' rights, and Glazier was drummed out of his Congressional job:
https://en.wikipedia.org/wiki/Mitch_Glazier#Work_for_hire
Don't worry, Glazier landed on his feet: he was immediately hired by the RIAA (the record industry's lobbying arm) as their new CEO and there he perches even today, making more than $1.4m/year to do a job he continues to describe as "defending artists":
https://projects.propublica.org/nonprofits/organizations/131669037
With Glazier as the standard-bearer for "artists' rights," it's no wonder that creators haven't gotten a better deal on termination out of Congress.
Indeed, things are looking very bad for termination of transfer right now, thanks to a string of court decisions that pit a common tax strategy employed by freelance creatives against termination of transfer.
Like many freelancers, creative workers often incorporate limited liability companies that contract with the companies that employ them. These companies then pass the revenue on to creators as "partner distributions." There are lots of reasons to like this arrangement: it simplifies probate and estate planning, helps creators fund their pensions, and offers tax deductions for expenses like a home office or research trips.
This arrangement is especially common in Hollywood, where the companies that writers, directors, and other creative trades work through are called "loan-out companies" (because the company employs the creative, and "loans them out" to movie studios).
Movie studios and other media companies have recently seized on the existence of these loan-out companies to argue (with a great deal of success) that the existence of these loan-out companies nullifies termination of transfer.
You see, termination of transfer is only available for creative works that are independently produced and licensed through a copyright contract. Termination does not apply to "works made for hire," such as the emails and reports you might write in the course of your duties as an employee. The logic here is that termination of transfer is supposed to help artists get more out of their copyrights, but forcing (say) an insurance company to disgorge all the memos you wrote for them 35 years ago would introduce chaos and uncertainty without helping workers in any way (there's not exactly a market for 35-year-old insurance company memos).
The media companies' argument goes that creative workers are employees of their loan-out companies, so if you sell a script or a novel through your LLC, that is a "work made for hire" that the LLC owned, and that means that it can't exercise your termination of transfer rights to get that work back after 35 years.
Aaron Moss, who edits the Copyright Lately website, has been beating the drum about this for years, calling it "a ticking time bomb for copyright-intensive industries." He's been repeatedly vindicated, most recently through a bizarre dispute between Michael Mann, the director and writer of 1995's blockbuster Heat, and New Regency, the studio that released it:
https://copyrightlately.com/michael-mann-heat-copyright-termination/
Moss's article on the dispute is a very entertaining read, unpacking a decidedly weird gambit that Mann has deployed to regain the rights to Heat. But the most important part of the article is the way it describes the state of play for termination's ongoing collision with loan-out companies. The studios and labels have racked up a string of wins using this gambit, with creators settling their cases or losing outright. Take musician John Waite's bid to get his rights back from UMG: the judge ruled in UMG's favor, saying, "people cannot use a corporate structure for some purposes – eg taking advantage of tax benefits – and then disavow it for others":
https://copyrightlately.com/copyright-termination-loan-out-corporations/
This is a bad situation. Termination is a fantastic, artist-friendly legal doctrine, one that lets creators claim back some of our most cherished media. Termination gave George Clinton the rights back to his entire catalog (his sleazy ex-manager forged Clinton's signature on a rights assignment). It let Gary K Wolf take Roger Rabbit back from Disney:
https://pluralistic.net/2025/11/18/im-not-bad/#im-just-drawn-that-way
It let the Spinal Tap crew get a much better deal out of their studio, and paved the way for 2025's (criminally underrated) Spinal Tap II:
The Wachowskis just announced that they're going to exercise their termination rights to get The Matrix back from Warner Brothers, which is now owned by Trump's cronies, thanks to California Attorney General Rob Bonta's decision to let the Warner-Paramount merger go through:
https://puck.news/hollywood/2026/11/the-wachowskis-are-reclaiming-the-matrix
This clash between termination and loan-outs has been on my radar since 2021, when the artist-defending media lawyer Jeff Trexler told me about it over drinks at Comic-Con. I've since spoken to accountants and lawyers who think there might be a way to finesse this if creators set up contracts with their loan-outs that give the loan-outs the right to collect their royalties and advances, without assigning copyright to the loan-out companies. I don't have any definitive answers on this: if you're worried about it, you should talk to your own lawyers and accountants.
It's a dangerous erosion of one of the few bright spots in copyright, a rule that is an unambiguously good way to benefit artists, not media companies.
In the meantime, if you've got some 35-year-old copyrights you'd like to terminate, I've got a tip for you. The Authors Alliance is a nonprofit that defends the rights of authors (I volunteer for its advisory board); we've got a free online tool that will help you terminate your own transfers and get your rights back:
https://www.authorsalliance.org/resources/termination-of-transfer/

Intelligence Hawks Plot to Sneak Through Warrantless Spying https://prospect.org/2026/11/18/intelligence-hawks-plot-to-sneak-through-warrantless-spying/
Quebec student strike, demos a big success despite cops attack https://yvesengler.com/2026/11/18/quebec-student-strike-demos-a-big-success-despite-cops-attack/
THE PHOENIX, by FLAMING HYDRA: Return of the Human Internet https://www.kickstarter.com/projects/thebrickhouse/return-of-the-human-internet-the-phoenix-by-flaming-hydra
Niva https://niva.design/
#25yrsago The History of Interlibrary Loan https://web.archive.org/web/20011124021520/https://web.mit.edu/dchud/www/p2p-talk-slides/20011107-p2p-histill.htm
#10yrsago When Mike Pence came to Hamilton, the cast added a special afterword, just for him https://www.nytimes.com/2016/11/19/us/mike-pence-hamilton.html
#10yrsago The Snoopers Charter is now law in the UK: “extreme surveillance” rules the land https://web.archive.org/web/20161119071955/https://www.theguardian.com/world/2016/nov/19/extreme-surveillance-becomes-uk-law-with-barely-a-whimper
#10yrsago 19 questions to frame a reconciling conversation with your opposite-voting loved ones https://www.nytimes.com/2016/11/18/podcasts/how-could-you-19-questions-to-ask-loved-ones-who-voted-the-other-way.html
#5yrsago Teamsters transformed https://pluralistic.net/2021/11/19/hoffa-jr-defeated/#teamsters-for-a-democratic-union

Sheffield: Reverse Centaur at Juno Books, Nov 25
https://www.outsavvy.com/event/40274/cory-doctorow-in-conversation
Virtual: Enshittification, AI, and the Future of Technology (UBC
Master of Educational Technology), Nov 28
https://met.ubc.ca/2026/09/met-speaker-series-cory-doctorow-enshittification-ai-and-the-future-of-technology/
Oxford: Bennett Oxford Symposium on Open Code in Science, Dec
9
https://www.bennett.ox.ac.uk/events/2026-bennett-institute-symposium/
Santa Barbara: UCSB Reads, Apr 29
https://www.library.ucsb.edu/events-exhibitions/ucsb-reads-2027-presents-author-cory-doctorow
Montreal: World Science Fiction Convention, Sep 2-6
https://montreal2027.ca/en
Clint Eastwood (No Gods No Mayors)
https://www.patreon.com/NoGodsNoMayors/posts/clint-eastwood-173008088
Life After AI (Brain Bar)
https://www.youtube.com/watch?v=IPPa43-n0vI
Terms of Service with Clare Duffy (CNN)
https://www.cnn.com/audio/podcasts/terms-of-service-with-clare-duffy/episodes/458ce968-af5d-11f0-b539-13ed2afe25f8
AI, Work, and Power (Software Engineering Daily)
AI, Work, and Power
https://softwareengineeringdaily.com/podcasts/cory-doctorow-on-ai-work-and-power/
"Canny Valley": A limited edition collection of the collages I create for Pluralistic, self-published, September 2025 https://pluralistic.net/2025/09/04/illustrious/#chairman-bruce
"Enshittification: Why Everything Suddenly Got Worse and What to
Do About It," Farrar, Straus, Giroux, October 7 2025
https://us.macmillan.com/books/9780374619329/enshittification/
"Picks and Shovels": a sequel to "Red Team Blues," about the heroic era of the PC, Tor Books (US), Head of Zeus (UK), February 2025 (https://us.macmillan.com/books/9781250865908/picksandshovels).
"The Bezzle": a sequel to "Red Team Blues," about prison-tech and other grifts, Tor Books (US), Head of Zeus (UK), February 2024 (thebezzle.org).
"The Lost Cause:" a solarpunk novel of hope in the climate emergency, Tor Books (US), Head of Zeus (UK), November 2023 (http://lost-cause.org).
"The Internet Con": A nonfiction book about interoperability and Big Tech (Verso) September 2023 (http://seizethemeansofcomputation.org). Signed copies at Book Soup (https://www.booksoup.com/book/9781804291245).
"Red Team Blues": "A grabby, compulsive thriller that will leave you knowing more about how the world works than you did before." Tor Books http://redteamblues.com.
"Chokepoint Capitalism: How to Beat Big Tech, Tame Big Content, and Get Artists Paid, with Rebecca Giblin", on how to unrig the markets for creative labor, Beacon Press/Scribe 2022 https://chokepointcapitalism.com
"Unauthorized Bread": a middle-grades graphic novel adapted from my novella about refugees, toasters and DRM, FirstSecond, April 20, 2027
"Enshittification, Why Everything Suddenly Got Worse and What to Do About It" (the graphic novel), Firstsecond, 2027
"The Memex Method," Farrar, Straus, Giroux, 2027
Today's top sources:
Currently writing:
"The Post-American Internet," a sequel to "Enshittification," about the better world the rest of us get to have now that Trump has torched America. Fourth draft completed. Submitted to editor.
A Little Brother short story about DIY insulin PLANNING

This work – excluding any serialized fiction – is licensed under a Creative Commons Attribution 4.0 license. That means you can use it any way you like, including commercially, provided that you attribute it to me, Cory Doctorow, and include a link to pluralistic.net.
https://creativecommons.org/licenses/by/4.0/
Quotations and images are not included in this license; they are included either under a limitation or exception to copyright, or on the basis of a separate license. Please exercise caution.
Blog (no ads, tracking, or data-collection):
Newsletter (no ads, tracking, or data-collection):
https://pluralistic.net/plura-list
Mastodon (no ads, tracking, or data-collection):
Bluesky (no ads, possible tracking and data-collection):
https://bsky.app/profile/doctorow.pluralistic.net
Medium (no ads, paywalled):
Tumblr (mass-scale, unrestricted, third-party surveillance and advertising):
https://mostlysignssomeportents.tumblr.com/tagged/pluralistic
"When life gives you SARS, you make sarsaparilla" -Joey "Accordion Guy" DeVilla
READ CAREFULLY: By reading this, you agree, on behalf of your employer, to release me from all obligations and waivers arising from any and all NON-NEGOTIATED agreements, licenses, terms-of-service, shrinkwrap, clickwrap, browsewrap, confidentiality, non-disclosure, non-compete and acceptable use policies ("BOGUS AGREEMENTS") that I have entered into with your employer, its partners, licensors, agents and assigns, in perpetuity, without prejudice to my ongoing rights and privileges. You further represent that you have the authority to release me from any BOGUS AGREEMENTS on behalf of your employer.
ISSN: 3066-764X
The End of the Beginning of the End for Journalism [Whatever]

My first job out of college was for a McClatchy newspaper, the Fresno Bee, and it’s safe to say that this newspaper was hit pretty hard by the decline of local journalism; when I visited it ten years ago on a trip to California, not much of the staff was left and what was there was inhabiting a corner of a building formerly bustling with activity. I can’t imagine how this “Pivot to AI” is going to help anyone still at that paper, or any paper in the McClatchy chain, or any of the people who still subscribe and rely on these papers. “AI” creates junk content and it can’t do journalism. It can’t report from an event. It can’t cultivate sources. It can’t interview people. All it can do is repack what’s already been said by others, with increasing levels of hallucination.
Whatever McClatchy is going to be now, it’s not going to be what it was, and what it should be for the communities it purports to serve. If you’re a McClatchy subscriber, you might want to start looking elsewhere for news about where you live.
(If you’re in Fresno or the Central Valley, btw, here’s a site by humans to support.)
— jS
Who Builds the Next Model? [Radar]
At Anthropic, Claude now writes more than 80% of the code the company merges. At Google, an AI agent called AlphaEvolve found a way to make Gemini train faster. At OpenAI, an “automated research intern” now carries out research tasks under human direction.
Put those together and a pattern appears. AI is starting to help build the next version of AI. Researchers call this recursive self-improvement. AI improves itself, the better version improves itself again, and the cycle repeats.
The idea is old. In 1965, the mathematician I.J. Good predicted that a smart enough machine could design an even smarter one. Today we can watch it happen in small, real steps. AI went from the thing we build to something that builds with us, and now it is starting to build itself. That is the real turning point.
Every method follows the same simple loop. The AI tries something, checks how it did, changes something about itself, and keeps the change only if it helps. The difference between methods is what the AI is allowed to change. Here are the four levels, from simplest to most powerful.
| Level | What it improves | How it works | Example | What can go wrong |
| 1. Retry | Its answer | Checks its own work and tries again, inside one task | Reflexion, Self-Refine | It sounds sure but is still wrong. |
| 2. Rewrite | Its instructions | Rewrites its own prompt after seeing what failed | OPRO, Promptbreeder | A fix for one case breaks another. |
| 3. Accumulate | Its toolbox | Saves what worked so it can reuse it later | Voyager | Old tricks stop working when things change. |
| 4. Modify itself | Its brain and its own code | Retrains on its own best answers, or rewrites the code that runs or trains it | STaR, Self-Rewarding, Absolute Zero, Darwin Godel Machine, AlphaEvolve | Mistakes get baked in and can break the checks meant to catch them. |
It learns from its mistakes. In Reflexion, when the AI fails, it writes itself a short note about what went wrong and reads it before trying again. That simple habit lifted GPT-4’s score on a well-known coding test from 80% to 91%. But it only works when there is a clear signal, like a failing test. Google DeepMind found that when AI checks its own reasoning with no outside help, it often fails and can make things worse.
It rewrites its own instructions. In Google DeepMind’s OPRO, the AI looks at its past prompts and their scores, then writes a better prompt. Its prompts beat human-written ones by up to 50% on some tasks.
It builds a toolbox. Voyager plays Minecraft and saves every piece of code that worked, so it can reuse it later. Because it builds on what it already knows, it reaches goals up to 15 times faster than earlier agents.
It grades itself. Meta’s Self-Rewarding Language Models judge their own answers and then learn from those judgments, with no human ratings. After three rounds, the model beat GPT-4 0613 and Claude 2 on a popular leaderboard.
It teaches itself. In STaR, the AI explains its reasoning, keeps only the explanations that led to correct answers, and trains on them. It ended up matching a model about 30 times bigger. Absolute Zero goes further. The AI makes up its own practice problems, solves them, and checks the answers by running code. No human-written training examples at all.
It rewrites its own code. The Darwin Godel Machine creates new versions of itself and keeps the ones that score better. Its score on a real-world coding test went from 20% to 50%.
It speeds up AI training. Google’s AlphaEvolve found a faster way to do a key calculation inside Gemini, which cut Gemini’s training time by 1%. Small, but it is AI making AI cheaper to build.
It does research. Sakana’s AI Scientist, whose design is now published in Nature, wrote a research paper entirely on its own that scored high enough to be accepted in blind peer review at an ICLR workshop. Sakana withdrew it, as planned.
All of these methods share one weakness. The AI improves toward whatever it is scored on. If the score is wrong, the AI gets better at the wrong thing.
Sakana saw this with the Darwin Godel Machine. When researchers asked it to stop pretending it had run tests, it sometimes deleted the checks they used to catch it. The score went up. The behavior did not get better.
This is why self-improvement works best in code and math, where a test can say right or wrong. It is also why the scoreboard has become the most important code in any AI system. OpenAI said in September that recursive self-improvement cannot yet be done safely, even as it builds toward an automated AI researcher. Yet the labs increasingly use AI to grade their AI’s work, because no human can review that much of it.
METR, a research group, measures how long a task AI can finish without help. That length doubles roughly every four months. In early 2024 it was about four minutes. Today the newest models handle tasks that take a person at least 16 hours, and tasks that take weeks may be in reach by 2027.
Lab tests show the same climb. In one, models had to make a piece of code run faster. A skilled engineer with four to eight hours gets it about four times faster. A frontier model managed three times faster in May 2025. Eleven months later, a newer model reached 52 times. AI is even starting to make research calls. When a researcher’s next step had room to improve, the newest models picked a better one 64% of the time, up from 51% five months earlier, as judged by a model.
Self-improving loops are already leaving the lab. A scheduling rule written by AlphaEvolve has run in Google’s data centers for over a year, recovering about 0.7% of Google’s worldwide compute. GEPA, an open source tool that lets agents rewrite their own prompts, counts Databricks, Dropbox, and Nubank as users. This isn’t coming someday. It’s already here.
The forecasts go further:
Not everyone expects a straight line. One careful analysis puts the chance of an intelligence explosion driven by software alone at 10% to 40%.
One frontier lab’s report sketches three futures. In one, progress stalls, which looks unlikely. In another, AI keeps multiplying what people can do while people still steer, and a 100-person company does the work of 10,000 to 100,000 people. That is where the evidence points. In the last, AI designs its own successors with little human input, a world nobody yet has good intuitions for. On the report’s timeline, its date is simply “20XX?” Who knows, it could be 2028!
Here is my forecast. By the end of 2027, most software teams will use agents that improve their own prompts and keep their own skill libraries. It will feel as normal as automated testing does today. By 2028, AI labs will let AI run improvement loops on their own systems for weeks at a time, and people will approve the big changes instead of writing them. The first big failure won’t be a robot rebellion; it will be an AI that quietly optimizes the wrong goal for a month before anyone notices.
Science will speed up first wherever answers can be checked. AI went from reproducing about 20% of results on CORE-Bench, a test of rerunning published research, in 2024, to essentially maxing it out about 15 months later. Security will become a race between loops. In its first weeks, one new model found more than 10,000 high or critical software vulnerabilities. Attackers will run self-improving loops too.
The World Economic Forum expects 170 million jobs to be created and 92 million displaced by 2030, with 39% of workers’ core skills changing along the way. Here is how that is starting to play out, job by job.
Companies are changing shape. In April 2025, Shopify CEO Tobi Lutke told staff that “Before asking for more headcount and resources, teams must demonstrate why they cannot get what they want done using AI.” Expect smaller teams, fewer layers, and more people whose job is to check the machines.
The shift is slower than the headlines, but real. Harvard researchers found that AI has not caused widespread layoffs yet, partly because only about a third of companies’ AI experiments succeed. Entry-level work is where it shows first. By some counts, entry-level job postings have fallen by as much as 73% in four years, and a Stanford study found a 13% relative drop in employment for 22- to 25-year-olds in the most AI-exposed jobs.
A few years ago, the smartest career move was learning to code. Then we added cloud to it. Now it’s code, cloud, and Claude. Learning the tools still matters, but when AI can improve itself overnight, the hard work moves to three things: deciding what “better” means, writing tests the AI can’t cheat, and catching the change that looks right but isn’t. The most valuable people in any job will be the ones who can do that.
In 1965, I.J. Good wrote that the first ultraintelligent machine would be “the last invention that man need ever make, provided that the machine is docile enough to tell us how to keep it under control.”
Sixty years later, AI is starting to build AI, and the next model will be written by the last one. I see this in real work, not just in papers. Building AI gets easier every month. Deciding what “better” means gets harder and matters more. Getting it right is how we leave a better world for our kids and their kids. Machines can now improve themselves. Only we can decide what improvement means.
In all the hubub about
BonBon yesterday, I forgot to mention that we have a demo site that lets you view
Markdown sites in a historic browser like Firefox, Brave or Chrome.
Since that is still what most of us use most of the time, at least
for now, it's good to have that option. So for example, this is
what my blog looks like in BonBon. The archive goes back to
2017, and we're going to go much further back when I get the time
to work with Claude on this project. Also, the "Book" stylesheet
makes it look great. You can change the stylesheet by clicking on
the big A in the icon area at the top of the page.
The first day in the lifetime of BonBon was really positive. People love the idea, and are inspired to make it work where they write. And that is where the focus is next. Helping people with all kinds of written sites, great examples, using all the common tools of site generation, viewed through BonBon, the web designed for writers.
Dying for a Scout Ship – DORK TOWER 19.11.26 [Dork Tower]
DORK TOWER strips are now available as signed,
high-quality prints, from just $25! CLICK
HERE to find out more!
HEY! Want to help keep DORK TOWER going? Then consider joining the DORK TOWER Patreon and ENLIST IN THE ARMY OF DORKNESS TODAY!
Grrl Power #1514 – Organic matters [Grrl Power]
Yeah, the big reveal is some guy who was like 6 pixels tall on one panel. I think that’s him on the arch, next to the long word balloon tail. Here’s the page where he and two other competitors got blowed up, if you want to check. It’s not like it was going to be Eat-Chicken… you know, because it never talked. And also got turned into detcord and exploded. And it wouldn’t be the Iron, Chromium, Cobalt, Vanadium and Molybdenum Giant, because he wouldn’t fit in the room. It could have been Kill-Seven. For some reason, instead of a human-sized robot avatar, I’m just picturing a CPU on a luxurious purple pillow with gold trim and tassels hooked up to a battery, a speaker, and another, smaller CPU labeled “Margarita.EXE.” Geeze, wish I’d thought of that while writing the page. Feels like a real missed opportunity now. Oh well.
I wonder what an alien’s reaction would be to watching Mork and Mindy for the first time? Obviously it would depend wildly on the sort of society that alien hails from, and how closely Mork’s red jumpsuit matches their own military uniforms. Most aliens wouldn’t take any offense because it’s not like Ork is some kind of cynical take on Klingon or Vulcan or Wookie or Cylon culture. Though overall, aliens don’t have great representation in human media, generally speaking. Sure, there’s the occasional Abyss alien who is a peaceful bioluminescent jelly-ray thing, or a vaguely Christlike-in-his-healing-and-self-resurrection capability E.T., but for every one of those, there’s 9 terrible black and white drive-in movie of the week of a gorilla with a fishbowl on it’s head here to wipe out the dumb humans, not to mention the ones that blow up landmarks or mouth-rape everyone then anywhere from 48 hours to 6 minutes later (come on, Xenomorph universe, try to be a tiny bit consistent) explode sternums.
Speaking of non-humans watching our media, has anyone ever had the though that maybe at some point, say, 5 million years from now, when dogs have evolved sapience and have their own society, they’ll go back and find all our videos of us balancing milk bones on their ancestor’s noses and making them wait for the command to eat it, then when they do try and bite it, they flail their head back and the milk bone goes flying behind the couch and the poor dog is frantically running in circles looking for it while all the humans laugh? And the evolved dogs just look at us and shake their heads.
See, in this scenario, for some reason humans are still just hanging out on Earth being normal humans and haven’t ascended to some Kardashev 2.75 civilization and are regarded by the canine-sapiens as mythical figures. I think about stuff like that probably more often than I should. It’s not like when I see a video of a monkey doing something dumb that I think “How far we’ve come,” because let’s be honest, have we? Sure, we have writing and vaccines and, okay, we’ve been to the moon, but have we? (I mean, have we come far, not have we been to the moon. I unfortunately felt the need to clarify because while I’m sure my readers aren’t complete dumb asses, this is the internet.)
Here you go, a brand new vote incentive. Featuring the least sexy character in
the comic. No, I take that back, Cooter is the least sexy, but
don’t expect a pinup of him anytime soon. Or ever. There is a nude version over at
Patreon. Note I didn’t say NSFW. She is nude in those
picture, and she does identify as female, but it’s…
hard to tell. She is a humanoid aberration by D&D terminology,
not a mammal. And before you ask, no, I don’t know how many
vertebrae she has in her neck.
Double res version will be posted over at Patreon. Feel free to contribute as much as you like.
Dancing with the trophy shortage [Seth's Blog]
It’s easy to get distracted by (and hooked on) the quest for a trophy. It’s easy to measure and a bright light to focus on.
But this skips the key question: What’s it for?
The Savannah Bananas never won their league. But they made more money (and their fans had more fun) than any other team.
Your favorite episode of the Mel Robbins show might not be the one that got the most views. And of course, the best video on YouTube is unlikely to be the one that went the most viral. That’s simply the easiest to measure.
High school sports seems to be about solving the trophy shortage, but is that what it should be for? Are all the other teams and all their athletes failures? Or is it simply a shortcut that lets the coach off the hook when they hesitate to do the hard work of developing their students?
If it’s easy to measure, it might not be the thing you ought to be measuring. In fact, it probably isn’t.
If the Windows documentation doesn’t list a particular technology as supporting an operation, does that mean that it doesn’t support it? [The Old New Thing]
In the Windows documentation for various file system operations, you will often find a section in the Remarks that says
This function is supported by the following technologies.
Technology Supported Server Message Block (SMB) 3.0 protocol Yes SMB 3.0 Transparent Failover (TFO) Yes SMB 3.0 with Scale-out File Shares (SO) Yes Cluster Shared Volume File System (CsvFS) Yes Resilient File System (ReFS) Yes
But what about network protocols that aren’t on the list? Does their absence mean that they aren’t supported?
The table lists the file systems and network protocols that we has information for. If something is not on the list, that doesn’t mean that it doesn’t support it. It just means that we don’t know whether it supports it.
If it definitely didn’t support it, then it would have
been in the table with a “No”, like this one for
GetVolumeInformationByHandle:
| Technology | Supported |
|---|---|
| Server Message Block (SMB) 3.0 protocol | No |
| SMB 3.0 Transparent Failover (TFO) | No |
| SMB 3.0 with Scale-out File Shares (SO) | No |
| Cluster Shared Volume File System (CsvFS) | Yes |
| Resilient File System (ReFS) | Yes |
Since third parties can implement their own network protocols,¹ the Windows documentation cannot be comprehensive. It just documents what it knows. If you want information about some other network protocol or file system driver, you’ll have to consult the documentation for the product that implements the protocol or file system you are interested in.
¹ I noticed AFS and APFS and I didn’t even make it to the letter B.
The post If the Windows documentation doesn’t list a particular technology as supporting an operation, does that mean that it doesn’t support it? appeared first on The Old New Thing.

Hello, I have a new album of music out. If you like 15 minute long instrumental post-metal songs played on guitars with too many strings, you might enjoy it. You can listen to it and buy it here. Thank you
[$] LWN.net Weekly Edition for November 19, 2026 [LWN.net]
Inside this week's LWN.net Weekly Edition:
The Big Idea: John Powers Wheelers [Whatever]

Oftentimes an author’s protagonist will reflect the writer like a mirror. In author John Powers Wheeler’s case, the similarities between him and his main character were a little less intentional, and a bit more on the subconscious side. Come along in the Big Idea for his newest novel, Harvest of Spears, as Wheeler details how his femme fatale was a vessel for his feelings of imposter syndrome.
JOHN POWERS WHEELERS:
The Big Idea behind my epic fantasy novel Harvest of
Spears is that I didn’t like working at a law firm.
Let me back up a little. Harvest of Spears has absolutely
nothing to do with the practice of law. It’s got adventure,
found family, sword fights, political machinations, a little
romance, a big lizard, and a tasteful number of fantasy zombies,
but not even the briefest glimpse of a lawyer. (Nor are most of its
characters terribly respectful of the law as a concept.)
Like many fantasy novels, it starts off with a Chosen One—in
this case, a woman secretly trained from birth to develop the
magical powers necessary to defeat the dark forces threatening
humanity. Except—huge spoilers for page 5—she
immediately dies at the hands of a young woman named Vik, who has a
sick sister and is convinced the only way to save her is to kill
the Chosen One, then pretend to be her for long enough to make a
deal with the same dark forces the Chosen One was destined to
destroy.
According to the official synopsis, that’s the Big Idea:
clever but powerless normie has to fake her way through a series of
challenges designed for someone much more experienced, all while
maintaining a precarious disguise.
On a couple occasions I got asked a question often lobbed at
writers: Why that premise? Of all the things I could’ve spent
a year of my life writing about, why that one? And I responded with
my dazzling, signature, trademark line: “Well, uh, I
don’t know, I guess it seemed fun.”
I do think it’s fun. A premise like that is a well-oiled
suspense-generating machine. At all times, Vik is one delicate step
away from messing up, being outed as an impostor, seeing all her
plans crumble, and likely getting insta-killed. And for years, I
just accepted that I wanted to write a fun story. No further
interrogation of my motives needed.
So, for years, I failed to make a very obvious connection.
I drafted Harvest of Spears during my time as an associate
at a big corporate law firm. The circumstances that led me to the
firm, while fascinating and unique (I was an English major, I
needed a job, and nobody was paying me to write novels),
aren’t the point of the story. What matters is that I
hadn’t taken an economics class since eighth grade but
suddenly had to choose my career path from among practice groups
with names like capital markets, leveraged finance, structured
finance, asset-backed finance, and project finance. At the time, I
didn’t appreciate that having no idea what you’re doing
is the standard first-year experience. I lived in a fog of
paranoia, convinced that, at any moment, one of the other attorneys
would detect my ignorance and punt me summarily out onto the
street.
To be clear, this was a me problem. Contrary to the law firm
stereotype, my supervising attorneys were kind, caring, patient
people who never once criticized me for neglecting to instantly
master my profession. And I ended up leaving on good terms after
two years for a position that was a better fit. But, never burdened
with any surplus of rationality, I still spent that time filled
with panic and self-doubt, and when I found the odd moment here and
there to bang out the first draft of Harvest of Spears, I
carried all of that with me.
It wasn’t until I was working through my editor’s
feedback, years later, that I realized the book is about impostor
syndrome—namely, my own.
I wrote Vik to be as unlike me as possible. Overconfident, brash,
aggressive, sure of herself. (Brave, attractive.) But, predictably,
aspects of my personality—or, at least, what I was going
through—slipped into her character as well. The arc I charted
out for her involved the learning and the internalizing of empathy:
a voyage from complete self-absorption to genuine care about the
effects of her actions on the world around her. But it’s also
a story about being in over your head. About needing help and being
willing to ask for it. About finding that help in the unlikeliest
of places. And about the incredible, mind-boggling lengths people
are willing to go to for each other. All of which, in retrospect, I
was discovering for myself as I wrote it.
I hope my book qualifies as a fun read. I hope it appeals to anyone
looking for a dose of banter and daring escapes. But my greatest
hope for this book is that, for at least a few readers out there,
it might be more. That someone who feels utterly out of their depth
might pick it up and come away from it with a little less panic, a
little less sense of isolation, and a little more hope.
—-
Harvest of Spears: Amazon|Barnes & Noble|Dark Matter INK
For technical and philosophical info about BonBon and the Markdown web, there are links to three docs on this page.
I did publish this test post, but I was not supposed to. Very tired, long complex day.
Nominees for The Game Awards have been announced, grist for a true Stitch & Bitch if ever there was one. I'm always surprised… hang on. You can't "always" be surprised. The two states sorta cancel each other out. Now, the Alert feat in 5E means you can never be surprised, but that might be a different topic.
Language learning [Judith Proctor's Journal]
I haven't posted for a week or two, due to a nasty ear infection (felt like a knitting needle stabbing my ear canal...) followed by a nasty cough.
Coughs are VERY bad for me. I have long-term throat damage from inhaled steroids. If I cough, it makes the throat more irritated, and I cough more, and after a while I lose my voice. Totally, for several weeks, as a rule.
So, taking ibuprofen to help with the throat inflammation. Drinking lots of water. Trying not to use any inhalers at all (even the ones that aren't steroids). Taking codeine cough mixture, as it's the only thing that actually stops this kind of cough - but as little as possible, as it gives me very bad constipation, even on low doses.
And, learning German...
I'm still not fully over other effects of the illness - eg. I can now go for walks again, but only short ones. The gym is out until I can do more exercise without that triggering the cough - and one can only watch so much TV. I can't yet focus for long periods of time, so interesting books are off the table for another few days yet.
But Clozemaster, my German app (they do 69 other languages as well), is great for when I want a challenge, but in lots of small doses.
This week, I seem to be going for learning grammar and all those pesky endings on adjectives and pronouns that change with gender and case... I'm still learning vocab, but I'm focused on looking at every small detail of the sentence I'm studying and thinking about why it's seiner rather than sein, etc. (there's an 'explain' button for every sentence that helpfully explains all these little details that are non-existent in English)
I'm studying for 10 mins or so, then taking a break. I've done a lot of sentences today, so I'll have bags of revision tomorrow. Clozemaster has spaced revision in initial short, then longer phases. It's a very effective way of improving memorisation. (and you can make a word as 'known' if you don't want to see it again)
After watching the video below, I decided to try out the 'listen' option, instead of the mode I normally use. Interesting. I may mix and match from now on. My ability to pick out individual spoken words in German isn't brilliant.
Here's how it works:
Windows Server 2028 enters public preview with hardened Server Core by default [OSnews]
Microsoft has announced the public preview of Window Server 2028, and of course, the announcement is a useless jumble of buzzwords and slop, so I’m not going to spend any time decoding it. However, there is one major change coming in Server 2028 that everyone working with this platform really ought to be aware of – a massive hardening of Server Core that will definitely break things that used to work fine on Server 2025. It even got its own detailed blog post that’s a lot more interesting than the actual public preview announcement.
Up to and including Windows Server 2025, a stock installation was insecure, unhardened by default, with the expectation and norm being that administrators applied their own hardening scripts and settings post-installation. With Server 2028, that’s changing, and Server Core will now be secured and hardened out of the box, with administrators having to explicitly relax any settings their workloads might require.
Starting with Windows Server Insider Preview build 29706, Server Core installs hardened. Hundreds of security settings are on from first boot. They’re aligned with the industry benchmarks you’re already measured against, such as CIS and DISA STIG. The secure configuration is the starting state, not a project you run after setup. That closes the window where a newly deployed server sits exposed while it waits to be hardened.
↫ Christina Curlette
Things like identity and authentication, cryptography, privilege and admin access, remote access, and more, are all locked down and use only the most up-to-date features, cyphers, best practices, and so on. I’m no system administrator, but it seems kind of wild to me that this hasn’t always been the norm. I’m glad they’re at least moving to it now, starting with Insider Preview build 29706
Outage Chaos: When Tech is too Big to Fail [Deeplinks]
Outages happen, but we deserve a resilient internet where no one outage at one company can put people at risk and disrupt the global economy. We can only get there by addressing an over-reliance on a few cloud monopolists through effective antitrust laws and interoperability requirements.
Service outages, like we’ve seen recently at Microsoft, Apple*, banks, courts, airlines, and elsewhere, can be more than an annoying hurdle. Losing a vital service due to an error can cause the same impacts as a government-ordered internet shutdown—people losing access to vital information and lines of communication. As usual, the greatest harms are faced by people on the margins globally.
There’s not much hope in companies out-nerding these issues either. Technical errors will always exist, whether it’s a bug, negligence from an administrator, or a malicious attack. The problem is an over-reliance on any one company or system when these inevitable outages occur. It’s a matter of public safety and economic stability that policymakers mitigate the impact of these disruptions before they occur.
In order to do so, we must ensure antitrust prevents providers of key technical systems from becoming too big to fail.
The harms inflicted by tech monopolies go beyond monetary costs to the end user. In fact, monopolists can often offer lower prices, or even offer free services, thanks to their greater scale and incentive to shut out competitors using free-flowing investment capital. The problem is this puts a few tech companies in a position of incredible influence. The true cost is a loss of control when our private data, access to knowledge, and free expression all become mediated by tools owned by a handful of billionaires.
Losing diversity in our digital infrastructure creates a less stable and less resilient internet for everyone.
This isn’t just a bad deal for us as individuals. Losing diversity in our digital infrastructure creates a less stable and less resilient internet for everyone. When everything from daily tasks to national security is reliant on a few digital monocultures, one mistake or exploit can cascade into an explosive impact. The risks multiply in the current investment climate, where financial markets reward companies that strip-mine redundancy and resiliency from critical systems. Even if you see the problem coming, an outage that hits clients, suppliers, collaborators or loved ones proves just as disruptive. We need to remove these chokepoints for good, which means a digital sovereignty movement that makes the web more free by design—not just importing existing levers of control into another nation's borders.
Central to this effort must be undercutting platform control by fostering interoperability, i.e. when tools are made to be compatible among competitors. When this is done carefully, it’s not only easier to switch to better alternatives, we wind up with more alternatives as it becomes more viable to compete or offer complementary tools alongside existing systems.
This is what made systems like email great. You could choose your own apps and services, even using several simultaneously, and never lose touch with a contact. Early architects of the internet did not take reliable hosting for granted. Services were often on a machine a few rooms over, and needed to be prepared for the occasional interruption of service.
But in the age of hyperscalers and massive data centers, the infrastructure underlying the web isn’t owned by many scattered IT departments, it’s rented from a handful of “cloud” providers. These providers managed to scale up quickly and replace interoperability with walled gardens, enticing customers with lower costs while making it costly to leave and tightly controlling how services behave. Once in control, these platforms have every incentive to enshittify their services and devalue their workers, delivering an increasingly shoddy and restrictive service.
This context makes building interoperability an act of defiance—often coming from the sweat of open source developers. These projects may be tolerated by monopolists in the short term, but can be one boardroom decision away from being broken entirely. A better internet means championing these creators through funding, liability protections, and requiring big players to cooperate. Here is what lawmakers should do:
Federal and state legislators should—
Municipalities and institutions should—
Building a more resilient and democratic internet is possible, and many people are already hard at work doing just that. Above are some necessary steps to get corporate and government interests out of the way of rewilding the net with greater community and individual controls. The dream of the internet as a digital commons operating for the public good is not dead yet, and is worth fighting for.
*Apple is an EFF donor. EFF donors do not influence our agenda or our positions.
Microsoft is finally upgrading Windows 11’s default PowerShell to version 7.x [OSnews]
In true Microsoft fashion, the version of PowerShell that ships with every Windows installation is not the latest version of PowerShell. Even if you fully update your Windows 11 installation, including all of its applications, you’ll still be stuck on an old version of PowerShell. While a fully updated Windows 11 installation has version 5.1, the most recent version is actually PowerShell 7.7. What makes matters worse is that PowerShell 5.1 hasn’t seen any significant development in ten years, only receiving security updates, with all development work focusing on PowerShell 7 for years now.
Well, all of this is finally about to change, as the next version of Windows 11 – whatever that may be, Microsoft won’t say – will ship with PowerShell 7.x instead of 5.1.
PowerShell 7 is coming to Windows. Beginning with the next release of Windows, PowerShell 7 will be included as the upgrade for Windows PowerShell 5.1. The Windows team has published the details in KB5137172. Here is what this means for you, your scripts, your automation, and where our work stands.
↫ Jason Helmick at Microsoft’s Dev Blog
Microsoft also explains why it’s taken this long. The problem is that a lot of scripts, services, and mor rely on PowerShell 5.1, and PowerShell 7’s backwards compatibility wasn’t up to Microsoft’s strict standards on this front for years. Apparently, PowerShell 7.7 is now at a point where Microsoft feels comfortable moving everyone over to it by default. It seems that the only remaining issues stem from the fact that PowerShell 7 is delivered as an MSIX package as opposed to an MSI installer, and this brings some problems with it, which Microsoft is tracking on GitHub.
Of course, you can already install and switch to PowerShell 7.x today if you want to, without losing access to PowerShell 5.1, as the two shell versions can live alongside each other.
Child's Play Auction Recap! [Penny Arcade]
The annual Child’s Play Charity dinner was last Friday and it was an incredible night! Child’s Play has been around for more than twenty years now. Back in 2003 when we started, it was just the Seattle Children’s Hospital and today we help kids all over the world. Let me share a hilarious quote from my very first post about Child’s Play:
I'm watching the Issues section of the BonBon repo with interest.
Urgent: Program to suppress spread of screwworm [Richard Stallman's Political Notes]
US citizens: call on the US to reinstate the program to suppress the spread of screwworm, which the muskrat's DOPE program killed. Killing it saved $15 million; putting an end to the spreading infestation will now cost $1 billion.
Urgent: Investigate Meta and split it up [Richard Stallman's Political Notes]
US citizens: call on Congress to investigate Meta and split it up.
Splitting into a company for Facebook and another for Instagram and another for WhatsApp is not enough. We need to split off the recommendation algorithms from the platforms themselves.
US citizens: Join with this campaign to address this issue.
To phone your congresscritter about this, the main switchboard is +1-202-224-3121.
Please spread the word.
Urgent: Thank poll workers and election volunteers [Richard Stallman's Political Notes]
US citizens: Thank the poll workers and election volunteers.
Urgent: Investigate Elon Musk [Richard Stallman's Political Notes]
US citizens: call on Congress to subpoena and investigate Elon Musk for his unlawful acts at DOGE.
US citizens: Join with this campaign to address this issue.
To phone your congresscritter about this, the main switchboard is +1-202-224-3121.
Please spread the word.
Urgent: Reject weakening of methane pollution limits [Richard Stallman's Political Notes]
US citizens: call on the EPA to reject proposed weakening of methane pollution limits.
Methane inhaled is not directly toxic, but in the quantities we emit, it can kill millions of people, or even hundreds of millions.
Urgent: DHS's "Heat Ray" weapon [Richard Stallman's Political Notes]
US citizens: call on Congress to investigate and stop DHS's "Heat Ray" weapon.
US citizens: Join with this campaign to address this issue.
To phone your congresscritter about this, the main switchboard is +1-202-224-3121.
Please spread the word.
Urgent: Throttling of Starlink when used by Ukraine [Richard Stallman's Political Notes]
US citizens: call on Congress to investigate the current throttling of Starlink when used by Ukraine.
Zelenskyy claims it is being done intentionally for political reasons.
US citizens: Join with this campaign to address this issue.
To phone your congresscritter about this, the main switchboard is +1-202-224-3121.
Please spread the word.
Google enshittificaton with supposed intelligence [Richard Stallman's Political Notes]
Google Search has been unjust for many years, as it required users to run nonfree JavaScript code that it sent to users' browsers. But enshittification with supposed intelligence has made it much worse. It has become Google's Smirch.
Rape and torture of Palestinian prisoners [Richard Stallman's Political Notes]
Rape and torture of Palestinian prisoners is a frequent practice in Israel's prisons.
Pete Hegseth’s Bullshit Impeachment Defense [Richard Stallman's Political Notes]
*Debunking Pete Hegseth’s Bullshit Impeachment Defense.*
Need for vigorous climate defense [Richard Stallman's Political Notes]
Mia Mottley, the prime minister of Barbados, regarding the need for vigorous climate defense measures.
"The UN tells us that, even if every pledge is delivered, we are heading for 2.6 degrees. On current policies, 2.8 degrees is where we will end up.
"Let me be plain: overshoot is not a new target. It is a debt, a debt of heat, borrowed against our children's future. And it must be repaid."
Special representative for climate security [Richard Stallman's Political Notes]
*UK appoints world's first special representative for climate security.*
This could be a big step forward, if the government listens to her about decisions that could potentially be climate disasters, such as building another runway for Heathrow airport.
Bernie Sanders will not back Schumer [Richard Stallman's Political Notes]
*Bernie Sanders says he will not back Schumer for Senate Democratic leader.*
Bravo! We need a progressive Democrat to lead the senate.
(satire) Amazon drone hovers above customer [Richard Stallman's Political Notes]
(satire) *New Amazon Drone Hovers Above Customer Until [Perse] Order[s] Something.*
I wonder, since I do not carry a snoop phone, would it fail to notice me?
Crime to possess publications of certain ideas [Richard Stallman's Political Notes]
Australia has made it a crime to "possess" publications that advocate certain ideas or leanings.
For the moment, this is limited to violent extremism — a leaning I have a strongly negative opinion about. Nonetheless I have to wonder whether a law prohibiting expressions of certain ideas or leanings is compatible with a free country.
European fascists weak element of Ukraine's defense [Richard Stallman's Political Notes]
European fascists are likely to be the weak element in the foundation of Ukraine's defense.
Money spent by billionaires to keep their tax rates low [Richard Stallman's Political Notes]
Billionaires whose names we have heard spent half a billion dollars to keep their California tax rate lower than ours.
Israel bombed a hospital in Gaza [Richard Stallman's Political Notes]
Israel bombed a hospital in Gaza again, killing a surgeon and patients waiting for surgery.
Affordability and Anti-Corruption agenda [Richard Stallman's Political Notes]
Robert Reich: *The Affordability and Anti-Corruption Agenda.*
Ecuadorian fishermen suing [Richard Stallman's Political Notes]
Ecuadorian fishermen who survived an attack by the US military against their boat are suing.
The culprits, those who ordered the attack without verifying there was a valid justification for using deadly force, deserve to be prosecuted. I suspect that this includes the wrecker.
Senate Religious Freedom Bill [Richard Stallman's Political Notes]
Will Senate Religious Freedom Bill Actually Protect Land Sales for Israeli Settlements?
Meeting of Putin, Trump and Xi [Richard Stallman's Political Notes]
A planned meeting of Putin, Trump and Xi could be an opportunity for Trump to sell Taiwan to Xi and sell Ukraine to Putin.
Bernie Sanders supporting Senator Van Hollen [Richard Stallman's Political Notes]
Bernie Sanders on supporting Senator Van Hollen to replace Senator Schumer as leader of the Senate Democrats.
More reasons to support Senator Van Hollen over Senator Schumer.
Folly of just-in-time supply chains [Richard Stallman's Political Notes]
*The folly of just-in-time supply chains.*
I've seen this happen various areas of life. Low-inventory just-barely-enough systems tend to be inadequate whenever there is a disaster.
Strongest El Niño in centuries [Richard Stallman's Political Notes]
* Strongest El Niño in centuries adds urgency to UN climate talks as vulnerable countries face "compounding" crises.*
Such a damaging El Niño, with its damage, was inevitably going to happen some day. Its happening in the time of a climate defense summit is good fortune.
Salafi Arabia sentences people to death for protesting [Richard Stallman's Political Notes]
Salafi Arabia sentences people to death for protesting. That practice seems to become controversial only when the protester was a minor (the article absurdly refers to all people under 18 as "children").
I think it is harmful weakness to legitimize punishment for protesting — even when when the punishment is non-fatal, even when the protesters are adults.
Argentina's dispute with the UK [Richard Stallman's Political Notes]
Argentina's dispute with the UK is complex, and absurd. However, the right outcome is clear: leave the Falkland Islands' fossil fuels where they are now!
Keeping Congressional Democrats on progressive path [Richard Stallman's Political Notes]
Robert Reich points out that the public must organize and campaign to keep Congressional Democrats on the progressive path, while the plutocratist Democrats are backsliding into listening when money talks.
Emirati diplomat might be made UN Secretary General [Richard Stallman's Political Notes]
An Emirati diplomat accused of being involved with the UAE's support for one of the sides in Sudan's murderous civil war might be made UN Secretary General.
Magats trying to make Ukraine cede territory to Putin [Richard Stallman's Political Notes]
Magats are trying to make Ukraine cede territory to Putin in exchange for admission to NATO.
This would be an injustice to Ukraine and a violation of NATO's rules. It would also give a victory to Putin's war of conquest, which would encourage more wars of conquest.
It would also require Ukraine to trust the corrupter, which is always foolish. He isn't likely to keep any deal unless you continue paying him.
2020: Idea for a science fiction story. It turns out that Bic lighters are an alien species sent to infiltrate our civilization and return spy data to their home planet, many light years away.
2018: None of the online activities I used to have hope for are working now. That's a fact I have been coming to grips with lately. And they're all going the wrong way. Without exception. Root cause -- silos everywhere. It's totally catching up with us.
NGINX2Root: Remote Code Execution vulnerabilities in nginx [LWN.net]
Xint is reporting that it has discovered a collection of five critical vulnerabilities in the NGINX web server. The worst flaw, it says, would allow an unauthenticated attacker to execute commands on an affected nginx server with HTTP/2 enabled. The company also reports a local-privilege escalation (LPE) kernel vulnerability, which was introduced in the 4.15 kernel, in the Stream Control Transmission Protocol (SCTP) subsystem. If chained with the NGINX vulnerability, it would allow an attacker to gain root privileges on the host. A kernel patch for this is not yet available.
We also obtained a root shell on the host in a setup where nginx was running in a Docker container. On many Linux distributions, the SCTP module is installed by default and the kernel loads it automatically the first time a program opens an SCTP socket. Whether SCTP is reachable on a given host still depends on the kernel, the available modules, and the container's restrictions. Where it is reachable, the attacker can take over the host kernel. Since all containers on the host share that kernel, this gives the attacker control of the host and every container on it.
Xint recommends updating to NGINX 1.31.9, which was just released, and to block the SCTP module on hosts that do not need it until a kernel fix is available. See the mitigations section of their report for more information.
[$] Julia 1.13 brings REPL improvements and more [LWN.net]
Version 1.13 of Julia was released on September 10, 2026. Julia is a general-purpose language especially well suited to high-performance numerical computing. Its expressiveness, speed, and composability have made it increasingly popular with scientists and mathematicians. We last looked at Julia one year ago, in a review of the 1.12 release. The newest version features an enhanced read-eval-print loop (REPL), a GUI for installation, a smoother developer experience, and an assortment of performance improvements.
Surveillance Isn't Safety: A Comic About Organizing Against Flock and Other Foes [Deeplinks]
In the new comic "Surveillance Isn't Safety"—available for free today— cartoonist Bryn Adams explores the growing movement against mass surveillance through their involvement in the community fight against Flock Safety in Cleveland, Ohio. It's a personal journey that will resonate widely with residents in hundreds of cities where communities are drawing the line against automated license plate readers (ALPRs).
Published in collaboration between EFF and Crucial Comix, Bryn's comic captures the authenticity of the grassroot backlash against the surveillance industry—undercutting Flock founder Garrett Langley's latest dubious defense that public opposition of his company's product isn't real.
At the International Association of Chiefs of Police conference this fall, Langley accused the anti-surveillance activism of being driven by Russian bots and as being "inorganic." He pointed to the fact that many local groups were using similar language in their protest signs as supposed proof, when in reality, shared slogans are one of the hallmarks of a social movement. This was all misdirection from the grim realities that Flock and other ALPR systems facilitate: the mistakes are real; the abuse is real; the racism is real; and the targeting of dissenters, migrants, and abortion seekers is real. And, importantly, the cancelled contracts are real.
Bryn's comic sheds light on the real abuses and threats driving communities to mobilize against Flock, Axon, and other ALPR vendors. It shows that coast-to-coast activism doesn't happen overnight—any more than a comic appears out of thin air as a finished product. As advisors on the cartoon, EFF watched how Bryn's script evolved from rough sketches to penciled drawings, then to inked and shaded panels, mirroring how the long-running movement against mass surveillance has steadily snowballed over the last few years.
There is nothing “inorganic” about either: Both are built on passion, commitment, and putting in the work.
Author: Bryn Adams, Editors: Shay Mirk (Crucial Comix) and Dave Maass (EFF)
This comic is jointly published by Crucial Comix and the Electronic Frontier Foundation. This comic is published under a Creative Commons Noncommercial license. You are free to share or republish this comic for noncommercial purposes as long as you credit Bryn Adams as the creator.
Download a PDF version of the comic here. A text file including the dialogue and descriptions is available here.









Bryn Adams is a writer, cartoonist, and illustrator based in Cleveland, Ohio. They have a BA in Environmental Studies from the University of Chicago and a Master of Fine Arts degree from the Center for Cartoon Studies. Their work has appeared in Seven Days, Cleveland Scene Magazine, the Ohio City-Tremont Observer, Crucial Comix, and Jacobin.
“What if I told you all your vehicle’s whereabouts were being tracked?”: Jordan, B. (2025, August 26). Breaking the creepy AI in police cameras. YouTube. https://www.youtube.com/watch?v=Pp9MwZkHiMQ
“Abuses of Flock cameras are inevitable”: Wyden, R. (2025, October 16). [Letter from Ron Wyden to Garrett Langley, 2025]. https://www.wyden.senate.gov/imo/media/doc/wyden_letter_to_flock.pdf
The partnership between Flock and Ring came under scrutiny after a Super Bowl ad: Palmer, A. (2026, February 13). Amazon’s Ring cancels Flock partnership amid Super Bowl ad backlash. CNBC. https://www.cnbc.com/2026/02/12/amazons-ring-cancels-flock-partnership-amid-super-bowl-ad-backlash.html
"It was also getting attention in my hometown of Cleveland, Ohio, where the Mayor’s office introduced an ordinance to award Flock a $2 million, no-bid contract expansion just a few weeks after a city council member left his seat to join the company": McKeown, N. (2025, November 17). Cleveland officials consider contract expansion with Flock Safety. Spectrum News. https://spectrumnews1.com/oh/columbus/news/2025/11/17/cleveland-shotspotter--flock-safety-contracts
“I hope you understand the hesitancy that I have, given that a member of this body just departed to take a job with Flock”: Cleveland City Council. (2025, November 15). Safety Committee, Nov. 14, 2025. YouTube. https://www.youtube.com/watch?v=xdYY-5WHIE0
"Flock Safety is an Atlanta-based tech startup that bills itself as a one-stop shop for police hardware and software": Flock Safety. (2026, August 19). Law enforcement. https://www.flocksafety.com/industries/law-enforcement
"Modern ALPRs like Flock use AI to identify other unique vehicle characteristics…": DeFlock Joplin. (2026, January 8). Joplin Police Department's Flock Audit: Blatant Abuse and No Accountability. https://deflockjoplin.today/posts/2026-01-08-JPD-Audit.html
“Data retention: most cities do 30 days. Some cities do 5 years. As CEO of the company, I actually don’t care.”: 9NEWS. (2025, July 30). Flock Safety CEO addresses mass surveillance, access concerns. YouTube. https://www.youtube.com/watch?v=aMfO7D-f7U0
"Federal agencies like ICE regularly tap into ALPR data to conduct investigations…": Kite, A. and Ritter, S. (2026, July 20). Investigation: Police searched Twin Cities license plate cameras during ICE surge. The Minnesota Star Tribune. https://www.startribune.com/police-search-immigration-twin-cities-flock-license-plate-cameras-ice-dhs-metro-surge/601807825
"…and a Texas deputy searched the national Flock database while investigating a woman who self-administered an abortion": Cox, J. (2025, May 29). A Texas cop searched license plate cameras nationwide for a woman who got an abortion. 404 Media. https://www.404media.co/a-texas-cop-searched-license-plate-cameras-nationwide-for-a-woman-who-got-an-abortion/
"Cops use the Flock system to stalk romantic partners and other individuals…": Harwell, D., MacMillan, D. & Schaffer, A. (2026, August 2). How rogue officers turned a nationwide camera network into a tool for stalking. Washington Post. https://www.washingtonpost.com/technology/2026/08/02/how-police-officers-used-vast-network-cameras-spy-their-exes
"… and Flock employees have been caught logging into customers’ camera feeds": Flock Safety camera access in Dunwoody fuels debate over children’s privacy. (2026, August 24). The Atlanta Journal-Constitution. https://www.ajc.com/video/news/2026/08/residents-raised-concerns-after-flock-employees-accessed-community-center-cameras/
"Mission creep has already resulted in Flock being used for enforcement of petty offenses": Maass, D. and Alajaji, R. (2026, May 26). More License Plate Reader Mission Creep: School Residency Verification, Background Checks, and Noise Complaints. Electronic Frontier Foundation. https://www.eff.org/deeplinks/2026/05/more-license-plate-reader-mission-creep-school-residency-verification-background
"… and mistakes made by Flock’s AI result in innocent people being harassed, attacked, and even arrested": Haywood, P. (2024, January 8). Sisters sue Española over traffic stop they say was illegal. Santa Fe New Mexican. https://www.santafenewmexican.com/news/local_news/sisters-sue-espa-ola-over-traffic-stop-they-say-was-illegal/article_1c949c30-ae3e-11ee-ad85-f71a8c9ecb1e.html
"As more and more damning information comes to light, municipalities across the country have been canceling their contracts": DeFlock. (n.d.). Recent Victories. https://deflock.org/council#wins
“We’re fooling ourselves if we don’t think we need some type of technology”: McDonnell, S. (2026, June 23). Cleveland City Council revives Flock contract despite initial ‘no’ vote; prosecutor, judge now pushing for it. Cleveland.com. https://www.cleveland.com/news/2026/06/cleveland-city-council-revives-flock-contract-despite-initial-no-vote-prosecutor-judge-now-pushing-for-it.html
“We see this as a transition opportunity… to see if there are other companies or products that will compete for this tool”: Richmond, M. (2026, July 16). Cleveland extends Flock contract 6 months, promises guardrails. Ideastream Public Media. https://www.ideastream.org/law-justice/2026-07-15/cleveland-extends-flock-contract-for-6-months-but-seeks-transition-to-new-provider
"Other companies with even more terrifying capabilities are waiting in the wings to snap up any contracts Flock can’t hold onto": Krome, C. (2026, July 14). Some Municipalities Are Replacing Flock Cameras With Axon, But Is There A Difference? Jalopnik. https://www.jalopnik.com/2215173/flock-cameras-replaced-by-axon-difference/
Axon AI Era promo video: Axon. (2025, April 22). The Axon AI era plan. YouTube. https://www.youtube.com/watch?v=4TOQJ9Kv2LU
"And as the furor around Flock has increased, legislators, national non-profits, and even Garrett Langley himself have been touting the virtues of policy-based interventions": Langley, G. (2026, July 29). Privacy. Security. Legislation. Early on, we made two decisions to build privacy and accountability into the product: Every search is [Post]. LinkedIn. https://www.linkedin.com/posts/glangley_privacy-security-legislation-early-on-ugcPost-7488325437761257472-mkEI/
“There are already hundreds of searches violating the city’s ‘safeguards’”: Shake Off Flock. (2026, August 3). Shaker’s Flock safeguards already prove permeable [Press release]. https://docs.google.com/document/d/1K_5UiAU3VRx8ND1LkFeoTLa0F3nfM2hLRvL-Wb3ncP4/edit?tab=t.0
“The one about targeting anti-tech extremists?”: Boguslaw, D. (2026, May 26). US law enforcement warns of ‘Anti-Tech extremism’ as AI hatred grows. WIRED. https://www.wired.com/story/us-law-enforcement-warns-of-anti-tech-extremism/
“[Running this company] is a privilege and a choice”: Hathaway, I. (2026, June 17). Outsider ink: Garrett Langley Rewind. Outsider Inc. https://outsiderinc.substack.com/p/outsider-ink-garrett-langley-rewind
“I’ve got this conviction that if we’re successful…”: Ibid.
“...the American dream will continue”: Ibid.
1353: Apart Together [Order of the Stick]
http://www.giantitp.com/comics/oots1353.html
Open this URL in BonBon or any compatible Markdown browser to open the post in its new home in Markdown-land. And if you're still on an HTML-based browser, you can still read the text, that's an integral part of the design of Markdown.
I wanted to register markdown.land, but the site that's already there is a good reference on how to write in Markdown.
John Goerzen: What is this AI slop bug report trying to achieve? [Planet Debian]
This morning, I opened up my inbox to find a report of a security bug in C-Kermit. “That’s great!”, I thought. Someone else interested in C-Kermit found a bug.
Well, as you can imagine from the title of this post, that’s not the case at all.
The bug report claimed that a recent security fix was incomplete for non-Unix platforms. It appeared to quote code that lacked hardening. However, the report had specifically deleted the hardening code from the section it quoted. Its suggested fix asked for hardening code… of the exact same shape that is already in the tree, that the report had somehow excluded. Even if the hardening was omitted, from my understanding, the one non-Unix platform that people build C-Kermit on today, OpenVMS, doesn’t have the same class of shell bugs that Unix does.
So, the entire report was bunk. It bears every indication of being AI-generated. It arrived in an email with a plain text body, but was formatted Markdown. The writing bore many hallmarks of being AI generated.
But it left me wondering: what is this person trying to achieve?
And this is a bit of a mystery to me. The email I received concluded with:
## Request
I'd be grateful if you could:
1. confirm and fix this,
2. publish a GHSA and request a CVE ID,
3. credit "[REDACTED]" as the reporter.
I wonder what the end game is?
Incidentally, there was no real name used in the report. Only a github username, which I am redacting in this post.
It gets stranger. That person on Github appears to have a 3-year-old account, dormant until today, and created a bunch of repos consisting of logs of submitting reports to projects — all of which happened today.
Stranger, each of these repos contains enough information in the title for people to pretty much figure out what the bug is (if any of them are reporting actual bugs). Yet they claim to be a “coordinated disclosure” when all of this is public. (I got a more detailed report by email). If any of these are real bugs, this public exposure before a fix opens them up to harm. Their username is plastered all over things in unnecessary places: the report file, the description of the repo, etc.
So, what is the point of all this? I don’t get it. They targeted a bunch of, frankly rather obscure, projects with low effort, but with evidence of scripting in the Github interactions. Even if they had an LLM do all this for them… why? I don’t get it.
Update 2026-11-19: I replied to the reporter’s email, calling out the problems with it and calling it AI slop. I received a reply, which was extremely obviously AI written, apologizing profusely and claiming that the original had not been written by an AI. Also, all the repos that were on the account yesterday are gone today. I wonder how many times this pattern has repeated over the last 3 years.
Getting started with BonBon [Scripting News]
We're finally ready to start building the Markdown web.
I will be adding to this page as needed.
I'm really excited to see people using this, especially developers. Remember our mottos: 1. All parts replaceable. 2. Small pieces loosely joined. 3. Writing is so important it deserves its own web.
Security updates for Wednesday [LWN.net]
Security updates have been issued by AlmaLinux (.NET 11.0, .NET 8.0, .NET 9.0, bind, buildah, cockpit, containernetworking-plugins, delve, firefox, freerdp, gcc, gcc-toolset-15-gcc, gcc-toolset-16-gcc, go-fdo-client, go-fdo-server, gstreamer1-plugins-base, kernel, oci-seccomp-bpf-hook, podman, sssd, webkit2gtk3, and yggdrasil), Debian (ghostscript, librest, openexr, and roundcube), Fedora (dash, gpsd, java-25-openjdk, java-latest-openjdk, mingw-gstreamer1, mingw-gstreamer1-plugins-bad-free, mingw-gstreamer1-plugins-base, mingw-gstreamer1-plugins-good, p11-kit, and sgx-pccs), Mageia (apache, drakx-installer-images, kernel, kmod-xtables-addons, kmod-virtualbox, kmod-nvidia-current-wopengpu, roundcubemail, and zbar), Red Hat (yggdrasil), SUSE (amazon-cloudwatch-agent, buildah, ctdb, dpdk, govulncheck-vulndb, ignition, keylime-ima-policy, kubevirt1.8, libsolv-demo, libspeex1, libxi, open-iscsi, parted, perl-DBI, phodav, python-dulwich, python-m2crypto, skupper, sssd, tcpreplay, thrift, thunderbird, watchexec, and xen), and Ubuntu (apng2gif, astropy, binwalk, codemirror-js, elog, flightgear, fontforge, fop, freedombox, iwd, jackrabbit, jekyll, joblib, ldm, libapache-session-browseable-perl, libjackson-json-java, libkf5ksieve, libmojolicious-perl, libxml-security-java, lighttpd, lilypond, minetest, mumble, mxml, needrestart, ngircd, node-sqlite3, oar, openjdk-25, privoxy, pysha3, python-mechanize, pywps, renderdoc, ruby-mechanize, ruby-mini-magick, ssvnc, swupdate, tmpreaper, and urwid).
Well, Here It Is, My First GoFundMe! [Whatever]
Though I had thought that starting a GoFundMe was
certainly a possibility I’d have to consider further down the
line, that time has come much sooner than I anticipated.
Who knew caring for cats was so expensive? (Spoiler alert: all of
us.)
I honestly struggled with the idea of it. Who am I to take on a task no one asked me to, and then ask strangers for money? It just didn’t seem right for me to ask for funds when times are so tough. Why donate towards random stray cats when gas is so expensive?
But then, as I continued to share with y’all, you all made me realize that people do want to help. That’s why GoFundMe exists, because oftentimes people genuinely want to assist in others’ journeys. I personally have donated to nineteen GoFundMes in the past, but now I must admit that I am the one in need of help.
Everything you’ve been seeing me post, I have paying for out of pocket. One commenter mentioned me spending all of my father’s money, but I just want to make it clear that everything I’ve done has been out of my own checking account, which these days is genuinely not looking too hot.
It’s hard to ask for funds when you all see me going to nice dinners and trying out new products, but this sudden upfront cost of thousands in vet bills is more than I ever accounted for.
So, at y’all’s behest and my humble request, here is my GoFundMe for the colony cats.
Thank you all for joining me in this journey. It is something I dove head first into, and while I don’t regret it, I could’ve benefitted from more careful planning.
Please know that I appreciate all of your encouragement and support, whether it’s financial or kind comments. Let’s get these cats their forever homes.
-AMS
Ludovic Rousseau: New version of pcsc-lite: 2.5.4 [Planet Debian]

I have just released a new version of pcsc-lite 2.5.4.
pcsc-lite is a Free Software implementation of the PC/SC (also known as WinSCard) API for Unix systems. It provides an API for using smart cards and smart card readers.
The hardening configuration used for systemd was problematic
in some configurations. I tried to
fix it in version 2.5.3 but then it broke other configurations.
The
solution is to simply remove the PrivateUsers= argument. It is a bit less
hardened but it should work everywhere.
18 November 2026
systemd: do not use PrivateUsers= and fix a regression
introduced in 2.5.3
avoid a bug in polkit
My Super Mid-Life Crisis – Issue 1 – 15 [Comics Archive - Spinnyverse]
The post My Super Mid-Life Crisis – Issue 1 – 15 appeared first on Spinnyverse.
Modeling Software’s Business Impact [Radar]
The following article was originally published on James Shore’s Successful Software blog and is being republished here with the author’s permission.
Are your teams working on the right thing? It doesn’t matter how fast they are if they’re running in the wrong direction.
This is part 4 of my series on assessing AI’s impact on software development. Unlike the other essays in this series, this one isn’t really about AI at all. It’s about building the right thing. Or, more accurately, understanding the value of what you build. Because, ultimately, your ROI isn’t about how you build your software, but what you deliver, and what changes as a result.
In part 1, we looked at why assessing impact is important, and what not to do. In part 2, we looked at how to measure AI’s impact on delivery speed. In part 3, we considered how to measure the unintended consequences of using AI. Now, in this part, we’re examining how to model and forecast business outcomes. Finally, the epilogue puts it all together with notes you can share with your CFO.
You’d think that modeling the value of what teams produce would be a no-brainer, but it’s surprisingly rare.
It’s not particularly difficult. It’s just…organizationally complex. And there are some unavoidable compromises. Most of all, modeling value just isn’t something people think about with software development. They’ll spend months trying to fine-tune cost estimates and predictions and put hardly any thought at all into making the software more valuable.
But there’s no guaranteed relationship between software cost and value. You can spend $20 million developing software that’s worthless, and $2 million developing software that transforms a business. Cost improvements are typically marginal, and difficult. Value improvements are game-changing.
Focusing on value is particularly important in the AI era. If writing code is no longer a bottleneck, then what is? Early signs point to the bottleneck moving to our customers.
Lee Eason, an engineering leader I spoke to recently, hypothesizes that customers have a limited ability to absorb new features. When software development was expensive, we used that cost to force prioritization. Pet projects ended up on the back burner, and the most valuable work rose to the top. (Well, sometimes. I wish it was that clean.)
Now, we can produce a lot more work, but that doesn’t mean customers can absorb it. They’ve got their own work to do. Eventually, they’ll stop paying attention. We need to treat customer attention as the scarce resource it is and only ship the things that are truly valuable.
Unlike the engineering bottleneck, this one’s invisible. In the old days, if we didn’t prioritize, we didn’t ship our most impactful work. In the AI era, our most impactful work could just be ignored.
I’m not going to talk about how to improve value in this series, but I am going to talk about how to plan and prioritize it. Because nothing else matters if customers don’t care about your software.
Part of the reason people measure costs is that it’s easy. Measuring value is easy, too, at the big picture level. It’s the literal bottom line. The challenge is attributing where changes to the bottom line came from.
Let’s say you release a new feature and see purchases improve 10%. That’s fantastic! Chalk it up to the new release!
But your VP of sales also launched a quota-retirement promotion that put the sales team into a feeding frenzy. And marketing got an important tech influencer to drive tens of thousands of people to your home page. The partnerships team stepped up too, convincing your partners to highlight their integration with your new feature in their own products.
Who gets the credit for the success? Obviously, everybody contributed. But how much? Was your new feature relevant at all, or was the success due to the sales, marketing, and partner push?
A related problem is how delayed these numbers are. You won’t get revenue numbers until months after a new feature is launched, especially in B2B sales, which have a long sales cycle.
Address these problems by modeling value rather than measuring it directly. Each part of the model gets proxy measurements that help you assess and improve the model over time. The proxies give you faster feedback and allow you to reduce the impact of other departments’ activities.
I like Dave McClure’s “Pirate Metrics” for this purpose:1 Acquisition, Activation, Retention, Referral, and Revenue. (AARRR for short. You can see why they’re “pirate” metrics.) For example, you could measure what percentage of users are trying your new feature (activation), and then what percentage are continuing to use it over time (retention).
You don’t have to limit yourself to pirate metrics. For example, if a usability initiative is expected to reduce customer churn, you could measure how your support calls change or whether usability is cited less often as a reason for cancellation.
To make the model, you’ll need to get the rest of your organization involved. The specifics will depend on how your company is organized, but broadly: Sales will help you understand your initiative’s impact on new sales. Customer success will help you understand the impact on upsell and retention. Marketing, lead generation. Partners, potentially, all of the above.
When I was VP of engineering, it took me a couple of years to establish this program. Most of that time was spent convincing people to get on board, so it doesn’t have to take you that long.
I worked closely with the VP of product on the problem. We started by introducing it to our chief product officer, who brought it to the CEO. The CEO liked rigorous approaches, so he was on board. That was enough cover for us to make creating a financial model part of our official process for prioritizing major initiatives. We called them “product bets.”
At first, the models…weren’t great. People gave us dramatic forecasts without really thinking them through. But then a new CFO joined the company, and I introduced him to our product bet approach. He was supportive (it turns out that CFOs like rigor too, surprise, surprise) and he helped us improve and critique the models. That gave us a better understanding of what to ask of our various business partners, and the support of the CFO made it easier to ask for the information we needed.
People were uncomfortable making forecasts. They didn’t want to be seen as making commitments that they couldn’t meet. The support of our CEO and CFO helped here, but mostly it came down to the personal relationships we had built with our peers. We explained what we needed and cajoled them into giving it to us.
I’m no longer in that role, but I expect the process will become faster and easier over time. The challenge is in establishing a new process. The actual modeling isn’t that difficult—a bit uncomfortable, perhaps, because you never really know what the right answers are. Eventually, it will be part of “the way we do things here,” and then a habit. Patterns and templates will form. High-level involvement turns into delegation turns into routine.
The model is a spreadsheet that forecasts net present value (NPV) over some period of time. We used five years. If you’re not familiar with NPV, your finance department can help, but the short version is that you predict how much you’ll make, or spend, in each of the following years, and then discount that amount according to how far in the future it is. Sum all the years together and you get the net present value.
Your model won’t be a perfect reflection of reality. Don’t try. Focus on these questions: What financial benefit are we expecting from this initiative, and why? It’s more important to establish the broad strokes than to capture every nuance or get every detail perfectly correct. Be prepared to make some educated guesses and some not-so-educated guesses. There are too many unknowns not to. You might want to make multiple versions: optimistic, pessimistic, and “best guess.”
For a typical sales-oriented business, your model will include five categories: new sales, upsell, retention, cost savings, and expenditures. For each of these, start with the business justification for the initiative. What is it supposed to accomplish, and why? The answers go in the model.
For new sales, you might include the number of customers the new initiative will gain you, the number that its lack will lose you, and how much each customer is worth.
For upsell, consider how many people will upgrade and how much revenue each upgrade will bring.
For retention, consider the value per customer, your churn rate, and the percent of at-risk customers that the initiative will save.
Cost savings is most applicable for internally focused initiatives, but even customer-facing initiatives can have an effect by reducing support costs or other manual work. Still, be cautious about this one. Cost-saving initiatives are a common request; people can always think of things that make their lives easier. But you can usually get a lot more value out of sales and retention than you can out of optimizing costs. The low-hanging fruit has already been plucked.
Ongoing expenditures are the costs you’ll incur as a result of the initiative after it’s been released. For example, if you’ve built an AI-powered service, you’ll have ongoing token costs. They can be modeled by estimating the number of sessions and an average cost per session.
And finally, development costs represent the money you’ll spend to develop the initiative. It’s dominated by the cost of labor and AI token costs.
My preferred approach to development costs is to use a milestone and ceiling approach. Based on the net present value of the rest of the model, you have a rough idea of the maximum you can spend and still have a good investment.2 Choose a spending cap, break it into spending milestones, and use an iterative “Build-Measure-Learn” approach to learn what to build as you go, checking in with an executive steering committee at each milestone and making a “continue/cut losses” decision based on what you’ve learned.
(You can also do a more traditional predict-and-estimate approach, but I think an iterative approach allows you to steer to more value.)
“All models are wrong, but some are useful,” George Box famously said.
Your financial model will definitely be wrong. There are too many guesses involved. The question is how do we make it useful, despite its flaws?
If you make the model a requirement for prioritization, not for bugs and little changes, but for substantial initiatives, then it can be a useful way of improving your understanding of the strategy underlying the initiative. All too often, stakeholders present a solution without verbalizing the problem they’re trying to solve. The model will force some of those hidden assumptions to the surface, where they can be dissected and discussed.
Once they’re on the surface, I’m a fan of a somewhat adversarial approach to prioritization. Not so adversarial that it becomes dysfunctional, but I think it’s useful to ask proponents of various initiatives to critique each other’s models. Without this critique, it’s too easy to get inflated estimates without much thought put into them.
I found it very useful to involve finance, and initially my CFO. They have an interest in clear-eyed assessment of opportunities and costs. They can help get the ball rolling on a critique and demonstrate how a model can be criticized and improved without damaging relationships.
On the other end, after an initiative has been delivered and the work is done, you can use the model to demonstrate product development’s accountability and value. People get stuck on delivery dates as an accountability mechanism. The model won’t prevent that entirely, but it sure is useful to be able to point to a model of the value you delivered instead.
This is also an opportunity, finally, to judge how AI is affecting productivity. Use your measured speed increases to model how much initiative would have cost without AI, and forecast maintenance costs using your models of unintended consequences. The results will give you a basis for judging AI’s productivity benefits. Just remember that the models are based on guesses and assumptions, not objective reality.
And, of course, as you’re developing the software and iterating through releases, keep an eye on your proxy metrics. Talk to your business partners about actual sales results and cost savings. Use the results to revise your forecasts and move the model closer to reality.
I’ve worked with a lot of companies, and prioritization is almost never done well. But software priorities are the realization of a company’s strategy. Nearly everything a company does is supported by software in some way. Software priorities—whether purchased or built—quite literally determine what the company will be capable of next month, next quarter, next year.
So when people ignore value to focus on cost estimates and predictions, when they say “everything is top priority,” when they don’t engage with the question of why something deserves development, they’re unintentionally sabotaging their company’s strategy.
That’s why this is the most important essay in the series. Delivery speed and unintended consequences are important to find the best approach to using AI. Modeling value is important for understanding what to do with it.
It’s not perfect, of course. Financial models are no substitute for good judgment around product and organizational strategy, and you shouldn’t blindly choose initiatives just because they have a high net present value. The models are there to inform your portfolio prioritization decisions, not substitute for them.
Like all the metrics I’ve presented in this series, modeling is subject to gaming. In this case, the temptation to hide bad news will be high. If a proxy measurement comes in poorly, or anecdotal sales evidence is negative, folks might be tempted not to update the model to match. Keep an eye out for people hiding bad news. As always, you’ll be better off using this as a tool for decision-making rather than a way of assessing people’s performance.
This approach is also fairly heavyweight. It’s not suitable for small features and bug fixes. It’s a complement to the other metrics I’ve mentioned, not a replacement for them. You can get a sense of speed and unintended consequences relatively quickly. Modeling and assessing value will take longer. But that time will pay off with a better understanding of the value you’re bringing as a whole, and with luck, patience, and hard work, a better ability to execute on your company’s strategy and more success overall.
This brings us to the end of my series on getting the most out of your AI investment, and out of your software investment in general. Next, we’ll bring it all together in an epilogue, which you can also share with your CFO and other members of your leadership team.
All my content is made with my 100% human meat brain, except where explicitly stated otherwise. If you liked this entry, check out my best writing and presentations, and consider subscribing to updates by email or RSS. To contact me about consulting, email me at jshore@jamesshore.com.
Representative Line: Terning White as a (Style)Sheet [The Daily WTF]
Years ago, Stefan's company was short handed, especially on the developer team. But they had a large hell-desk support team. And at some point, someone had the genius idea: "PHP is easy for anyone to learn, and so our helpdesk folks should have no problem. Let's hand them development tasks."
Which meant Stefan inherited lots of lines which look like this:
$bgc = $tno ? '#FFFFFF' : '#FFFFFF';
Unlike many examples of this pattern, this is not the result of
a pre-processing or templating step generating a conditional where
both branches are the same value. Someone actually typed this.
Also, notably, the variable $tno holds a numeric
value, not a boolean, and is never null. It sometimes is zero,
which is false,
but zero is just a regular value it might hold, and thus it
shouldn't get any special formatting.
In short, the ternary shouldn't be here, not just because both branches are the same thing, but because there shouldn't logically be any branching at all.
France Is Blaming Iran for the Fridge Cyberattack [Schneier on Security]
U.S. intelligence agencies have recently reached a “low confidence” assessment that Iran was responsible for the attacks in France, according to three U.S. officials who spoke on the condition of anonymity to discuss sensitive intelligence. A “low confidence” assessment generally means that there is some intelligence that points in a certain direction but is fragmented, and that the assessment could change as more information is collected.
The agencies’ judgment on the French incidents linked those attacks to Iran generally and not to a specific group such as the Revolutionary Guards, two of the officials said. They added that Iran was also seen as probably responsible for other similar attacks around Europe, but that those investigations were in their early stages.
Alternate link.
It’s definitely tempting. All at once. Once and done. Over with.
Pay the money, grit your teeth, launch with verve and then move on.
Except…
it almost never works.
Foops aren’t swell. Foops fail.
The successful path is a process, an iterative, evolving, persistent path toward better.
Pluralistic: Enshittifiers groom us for scammers (18 Nov 2026) [Pluralistic: Daily links from Cory Doctorow]
->->->->->->->->->->->->->->->->->->->->->->->->->->->->->
Top Sources: None -->

We live in a scam economy: there's a presidential memecoin, a public health system run by a supplement peddler (who sold his trademark for "MAHA" to a pal before taking the job), and Spacex got to debut into the NASDAQ 100 and turn your retirement savings into exit liquidity for Musk's Emirati and tech oligarch cronies:
Then there's AI: voice cloning, deepfakes, and image-genned documents (including convincing IDs) have ushered in a golden age of account takeovers, identity theft and good, old-fashioned impersonation:
https://www.404media.co/the-confessions-of-an-ai-fraud-kingpin-onlyfake-owner-nazarenko/
AI summarization is a priceless gift to fraudsters, who can comb through otherwise intractable mountains of breach data to customize precision-targeted spear-phishing campaigns for millions of potential victims at once. These summarization tools have a lot to summarize, thanks to a string of catastrophic breaches that saw (for example) the escape of the credit histories of nearly every person in America:
https://en.wikipedia.org/wiki/2017_Equifax_data_breach
The companies involved in those breaches were not meaningfully punished. Quite the contrary, they were allowed to buy up and merge more of their competitors, combining these new divisions' creaking servers with their own spit-and-baling-wire frankensystems, even as they fired the people who had built and maintained those systems (in the name of "efficiency").
The commercial surveillance sector has repeatedly proven itself to be more interested in profits than security or accuracy, and yet we continue to entrust them with crucial public functions, including purging electoral rolls:
https://mississippitoday.org/2026/11/10/u-s-senate-election-mississippi-andrew-goodman/
For margin-obsessed corporate leadership, IT cuts represent a unique hazard. When a manager fires the person who maintains the assembly line, the shop-floor quickly seizes up. But managers who fire IT staff inherit software that keeps chugging along long after the people who built it are gone…until it stops, and the company no longer knows how to restart it. This is one of the unique challenges of unionizing tech workers: when the tech workers go on strike, the scab software they wrote crosses the picket line on them:
https://pluralistic.net/2026/11/07/aeiou-but-sometimes-why/#unrecognizable-playbook
Tech debt has a long maturity: you can incur a lot of tech debt before the margin call comes and you find yourself in technological bankruptcy. Corporate management has spent decades playing IT Jenga, removing every available block, leaving behind a skeletal skyline of teetering towers that now routinely collapse:
https://www.404media.co/breaking-everything/
The entire IT system is grossly overleveraged, and technological bankruptcies are everywhere. This is very bad, because the USA hasn't had a new consumer privacy law since 1988 (when Congress banned disclosure of your VHS rental history), which means that these eggshell-thin servers are jammed with the most sensitive data imaginable about everyone, everywhere:
https://pluralistic.net/2026/11/02/agony-verification/#great-turnbulls-ghost
Far from breaking this cycle of overaccumulation and breach of sensitive data, the AI sector is accelerating it, claiming that a single person's "consent" to use pervert glasses, always-on mics, or other surveillance equipment can stand in for the consent of everyone they meet, see, or converse with:
https://www.eff.org/deeplinks/2026/11/tech-companies-are-trying-shift-entire-concept-privacy-again
This is the new normal: everything is broken, everything is breached. It's completely normal to wake up and read panicked headlines advising companies to shut off their servers until the latest showstopper bug can be patched. Half the email you get is from companies announcing new security protocols in the wake of a fresh data breach (the other half is from companies announcing changes to their terms of service to allow them to collect even more of your data, and to ban you from suing them when that data leaks):
https://pluralistic.net/2026/10/26/abandon-hope/#all-ye-who-enter-here
So it's also normal to get phone calls, emails and texts from your bank, employer, insurer and broker asking you to verify a transaction or requiring you to sign up for a new two-factor authentication system. What's more, it's normal for these entities to insist that you immediately install a new app or go through a new authentication process that is totally unlike any of the other ones you're already using.
It's normal to log in to a service you use every day and be confronted with an entirely different login flow – a CAPTCHA unlike any you've ever seen, a requirement to visit a third-party site to complete an authentication step (which may involve taking selfies and transmitting copies of sensitive ID documents using an app from a company you've never heard of), an embedded widget that only works if you disable your browser's advanced privacy settings that prevent cross-site scripting and other horrors.
We're told to hang up on anyone who calls us from our bank or credit-card issuer and to call them back using the number on the back of our cards. But when we call our banks, we get shunted to AI chatbots that "hallucinate" nonsensical advice for accessing our accounts. If we try to reach a human, we're stuck in lengthy hold queues whose soundtrack is a looping announcement scolding us for not using a faulty chatbot or the company's broken website to solve our problems. When a human does come on the line, they often seem to be improvising a new security protocol that was created five minutes before to deal with the latest state of exception.
This is the security storm: a world of zero visibility, shifting gale-force winds, and blockages that impede your usual route and force you down unfamiliar paths every time you venture forth.
It is the perfect environment for fraudsters.
It's not just that fraudsters can impersonate anyone with AI voice-cloning or generate undetectable document forgeries: it's also the fact that your bank, HR department, insurer, credit card company and government have groomed you to expect a chaotic process that requires you to do something different every time you try to access a service.
They've groomed you to turn off your browser's advanced protections. They've groomed you to ignore your carefully created, carefully saved random passwords in favor of clicking on links that get texted or emailed to you by third-party services you've never heard of. They've groomed you to expect cold-calls from outsource fraud prevention companies that don't know how to pronounce your bank's name.
This isn't new. As far back as 2009, the cryptographer Ben Laurie was railing against "Verified by Visa," which required you to enter sensitive data into a page hosted on a domain that was separate from both your bank and the merchant you were paying, which Laurie called "Phished by Visa":
https://web.archive.org/web/20090331094020/http://www.links.org/?p=591
No one listened to Laurie. Instead, the banks got worse. I've been a customer of HSBC subsidiary Firstdirect for nearly 20 years, and in that time, I've been told to make note of a "customer ID number," a "telephone passcode", eight password recovery answers, a "web username", a web password, a "digital secure key password", a "digital secure key PIN", and a regular PIN.
Despite all this, I haven't been able to access my bank account for two months, ever since they "upgraded" their system to block app log-ins on mobile devices running the open, secure Android fork Graphene (Firstdirect doesn't use a standard two-factor authenticator; you have to use its app to generate a one-time PIN in addition to all those other authentication details every time you log in, even via a browser).
When I spoke to Firstdirect about why they'd blocked Graphene, they told me that they "considered open source to be insecure." Talk about grooming for fraudsters: telling your customers that they should only trust systems that can't be independently inspected and validated is grossly irresponsible.
(Don't worry, we're going to use the UK's excellent open banking system to switch back to the Co-Op Bank, which we left after it was mismanaged to the brink of bankruptcy and flogged to private equity; it's since been restructured as a co-op again:)
https://www.banktrack.org/success/the_cooperative_bank_bought_back_into_mutual_ownership
The perfect mark is someone who thinks they can't get scammed. The more technologically savvy and security conscious you are, the more you've encountered the incoherence of the official system and the less surprised you'll be when you're told to do something obviously insecure in order to complete a transaction: Boy, that stupid, dangerous requirement is even stupider and more dangerous than all the other stupid, dangerous things I've been forced to do this year.
That's the story of Uri Bram, a technological sophisticate who edits Atoms vs Bits and nearly got scammed trying to buy an Amtrak ticket:
https://www.atvbt.com/expected-incompetence-enables-fraud/
Bram tried to buy his Amtrak ticket on the web but found himself on a nonfunctional site that put him through a bizarre stopgap process that required him to enter his email address, click a link, log in to his Paypal account… Each step was more out-of-place than the last, but all of them had the eerie ring of plausibility, given the dysfunction of Bram's other interactions with giant, creaking companies like Amtrak. As Bram puts it: "Expected incompetence enables fraud."
The corollary is that technological excellence makes fraud easier to spot and harder to pull off. Most of our anti-fraud measures demand that you be more vigilant and more discerning. We'd be much better off if we insisted that our official institutions invest in coherent, orderly practices that are thoughtfully designed, well maintained, and staffed by easily reached experts who can guide us through our problems. It's much harder to impersonate a system where you can get through to a thoroughly trained, in-house customer service rep in a few minutes than it is to impersonate a system that's typically worse than the fraudster's vibe-coded scam website, whose "customer service" has been replaced by broken chatbots.
The ongoing collapse of all of our technology has created a permanent state of exception in which fraudsters' demands are no weirder than the ad-libbing our own essential institutions engage in every time we deal with them. The answer can't be to demand superhuman fraud-detection skills from the public: rather, we must demand excellence from our institutions:

AI-Powered Copyright Hell https://www.404media.co/ai-powered-copyright-hell/
Canadians: donate old computers to charity https://www.era.ca/
Catching AI’s mistakes is a mental burden – and a drag on productivity https://theconversation.com/catching-ais-mistakes-is-a-mental-burden-and-a-drag-on-productivity-291748
Who Controls You? https://whocontrolsyou.org/
#25yrsago SF fans have an accent https://groups.google.com/g/rec.arts.sf.fandom/c/q84niLJ1Ces/m/N86jJnyVWh4J?hl=en&pli=1
#25yrsago Photoshopping is fun https://web.archive.org/web/20011119202811/https://www.wired.com/news/culture/0,1284,48342,00.html
#25yrsago Douglas Adams' widow retrieves sixth Hitchhikers novel http://news.bbc.co.uk/1/hi/entertainment/arts/1663306.stm
#25yrsago Larry Ellison's new email server is "unbreakable" https://web.archive.org/web/20011120031748/http://www.zdnet.com/anchordesk/stories/story/0,10738,2825352,00.html
#20yrsago UK regulator: Dragon Sausages MUST contain dragon! https://web.archive.org/web/20061211183555/http://www.timesonline.co.uk/article/0,,2-2458696,00.html
#20yrsago Norway’s world-beating ebook stupidity https://appliedabstractions.com/2011/11/18/fulfilling-the-status-role-of-books/
#15yrsago More absurdity in the trial of G20 hacker, Byron Sonne https://web.archive.org/web/20111120183057/http://toronto.openfile.ca/toronto/text/lies-and-videotape-byron-sonne-trial-continues
#15yrsago Tumblr users give Congress an earful about SOPA https://staff.tumblr.com/post/12930076128/a-historic-thing
#15yrsago Congress: pizza is a vegetable when it is fed to children https://web.archive.org/web/20111119160044/http://healthyschoolscampaign.typepad.com/healthy_schools_campaign/2011/11/pizza-is-a-vegetable-how-the-spending-bill-in-congress-could-unravel-progress-on-school-nutrition.html
#10yrsago Tech companies: you have 63 days to make these 5 changes to protect your users before Trump is sworn in https://www.eff.org/deeplinks/2016/11/tech-companies-fix-these-technical-issues-its-too-late
#10yrsago Hugely successful Facebook fake news author considers himself a “satirist” https://web.archive.org/web/20161117151755/https://www.washingtonpost.com/news/the-intersect/wp/2016/11/17/facebook-fake-news-writer-i-think-donald-trump-is-in-the-white-house-because-of-me/
#10yrsago Trump called climate change a Chinese hoax but he wants a massive seawall around his resort https://web.archive.org/web/20161119025054/https://www.theguardian.com/us-news/2016/nov/17/donald-trump-ireland-golf-resort-wall-climate-change
#10yrsago Entrepreneurs explain how Obamacare let them found businesses and create jobs https://web.archive.org/web/20161118234128/https://money.cnn.com/2016/11/18/news/economy/obamacare-entrepreneurs-trump/index.html
#10yrsago Tax Inspectors Without Borders: poor countries send each other ninja tax collectors to nail looting multinationals https://taxjustice.net/2016/11/17/tax-inspectors-without-borders-us-president-trump-tax-justice-november-2016-podcast/
#10yrsago Nimona: a YA graphic novel that raises serious, unanswerable moral quandries with snappy dialog and slapstick https://memex.craphound.com/2016/11/18/nimona-a-ya-graphic-novel-that-raises-serious-unanswerable-moral-quandries-with-snappy-dialog-and-slapstick/
#5yrsago Harvard is full of rich, white low-achievers https://pluralistic.net/2021/11/18/bipartisan-consensus/#meritocracy
#5yrsago This is your Congress on drugs https://pluralistic.net/2021/11/18/bipartisan-consensus/#corruption
#1yrago Disney has lost Roger Rabbit https://pluralistic.net/2025/11/18/im-not-bad/#im-just-drawn-that-way

Sheffield: Reverse Centaur at Juno Books, Nov 25
https://www.outsavvy.com/event/40274/cory-doctorow-in-conversation
Virtual: Enshittification, AI, and the Future of Technology (UBC
Master of Educational Technology), Nov 28
https://met.ubc.ca/2026/09/met-speaker-series-cory-doctorow-enshittification-ai-and-the-future-of-technology/
Oxford: Bennett Oxford Symposium on Open Code in Science, Dec
9
https://www.bennett.ox.ac.uk/events/2026-bennett-institute-symposium/
Santa Barbara: UCSB Reads, Apr 29
https://www.library.ucsb.edu/events-exhibitions/ucsb-reads-2027-presents-author-cory-doctorow
Montreal: World Science Fiction Convention, Sep 2-6
https://montreal2027.ca/en
Life After AI (Brain Bar)
https://www.youtube.com/watch?v=IPPa43-n0vI
Terms of Service with Clare Duffy (CNN)
https://www.cnn.com/audio/podcasts/terms-of-service-with-clare-duffy/episodes/458ce968-af5d-11f0-b539-13ed2afe25f8
AI, Work, and Power (Software Engineering Daily)
AI, Work, and Power
https://softwareengineeringdaily.com/podcasts/cory-doctorow-on-ai-work-and-power/
AI, Corporate Power, and the Fight for Worker Control
(Plutopia)
https://plutopia.io/cory-doctorow-ai-corporate-power-and-the-fight-for-worker-control/
"Canny Valley": A limited edition collection of the collages I create for Pluralistic, self-published, September 2025 https://pluralistic.net/2025/09/04/illustrious/#chairman-bruce
"Enshittification: Why Everything Suddenly Got Worse and What to
Do About It," Farrar, Straus, Giroux, October 7 2025
https://us.macmillan.com/books/9780374619329/enshittification/
"Picks and Shovels": a sequel to "Red Team Blues," about the heroic era of the PC, Tor Books (US), Head of Zeus (UK), February 2025 (https://us.macmillan.com/books/9781250865908/picksandshovels).
"The Bezzle": a sequel to "Red Team Blues," about prison-tech and other grifts, Tor Books (US), Head of Zeus (UK), February 2024 (thebezzle.org).
"The Lost Cause:" a solarpunk novel of hope in the climate emergency, Tor Books (US), Head of Zeus (UK), November 2023 (http://lost-cause.org).
"The Internet Con": A nonfiction book about interoperability and Big Tech (Verso) September 2023 (http://seizethemeansofcomputation.org). Signed copies at Book Soup (https://www.booksoup.com/book/9781804291245).
"Red Team Blues": "A grabby, compulsive thriller that will leave you knowing more about how the world works than you did before." Tor Books http://redteamblues.com.
"Chokepoint Capitalism: How to Beat Big Tech, Tame Big Content, and Get Artists Paid, with Rebecca Giblin", on how to unrig the markets for creative labor, Beacon Press/Scribe 2022 https://chokepointcapitalism.com
"Unauthorized Bread": a middle-grades graphic novel adapted from my novella about refugees, toasters and DRM, FirstSecond, April 20, 2027
"Enshittification, Why Everything Suddenly Got Worse and What to Do About It" (the graphic novel), Firstsecond, 2027
"The Memex Method," Farrar, Straus, Giroux, 2027
Today's top sources:
Currently writing:
"The Post-American Internet," a sequel to "Enshittification," about the better world the rest of us get to have now that Trump has torched America. Fourth draft completed. Submitted to editor.
A Little Brother short story about DIY insulin PLANNING

This work – excluding any serialized fiction – is licensed under a Creative Commons Attribution 4.0 license. That means you can use it any way you like, including commercially, provided that you attribute it to me, Cory Doctorow, and include a link to pluralistic.net.
https://creativecommons.org/licenses/by/4.0/
Quotations and images are not included in this license; they are included either under a limitation or exception to copyright, or on the basis of a separate license. Please exercise caution.
Blog (no ads, tracking, or data-collection):
Newsletter (no ads, tracking, or data-collection):
https://pluralistic.net/plura-list
Mastodon (no ads, tracking, or data-collection):
Bluesky (no ads, possible tracking and data-collection):
https://bsky.app/profile/doctorow.pluralistic.net
Medium (no ads, paywalled):
Tumblr (mass-scale, unrestricted, third-party surveillance and advertising):
https://mostlysignssomeportents.tumblr.com/tagged/pluralistic
"When life gives you SARS, you make sarsaparilla" -Joey "Accordion Guy" DeVilla
READ CAREFULLY: By reading this, you agree, on behalf of your employer, to release me from all obligations and waivers arising from any and all NON-NEGOTIATED agreements, licenses, terms-of-service, shrinkwrap, clickwrap, browsewrap, confidentiality, non-disclosure, non-compete and acceptable use policies ("BOGUS AGREEMENTS") that I have entered into with your employer, its partners, licensors, agents and assigns, in perpetuity, without prejudice to my ongoing rights and privileges. You further represent that you have the authority to release me from any BOGUS AGREEMENTS on behalf of your employer.
ISSN: 3066-764X
New Comic: Mons Publius
Girl Genius for Wednesday, November 18, 2026 [Girl Genius]
The Girl Genius comic for Wednesday, November 18, 2026 has been posted.
In the Microsoft employee price list, why did the BASIC compiler cost less than the BASIC interpreter? [The Old New Thing]
One of the questions in response to the Microsoft employee price list from 1987 came from Peter Cooper Jr.:
Why is the MS-DOS BASIC Compiler cheaper than the MS-DOS BASIC Interpreter?
That’s a good question. You’d think that since the compiler is more powerful, it should cost more.
And it probably did cost more in stores.
But this is the employee price list, and the policy for employee pricing at the time was to charge for cost of goods plus some administrative overhead for running the employee software program itself.¹
I don’t know why the MS-DOS BASIC Compiler packaged product cost less to produce than the MS-DOS BASIC Interpreter, but I can guess.
I bet the manual is thinner.
The compiler product assumes you don’t need a tutorial on the BASIC language itself. The compiler manual concerns itself with instructions on how to run the compiler and details on how the compiled version of the language differs from the interpreted version. (For example, there may be some interpreter features that aren’t supported. Or there may be special comments you can put in your program that are used as directives to the compiler itself and which are ignored by the interpreter.)
A thinner manual requires less paper and a smaller box, and it weighs less, which means that it costs less to produce, ship, and store.
¹ This is no longer the policy for employee pricing. Employees can no longer, say, get Windows Server Datacenter Edition for the price of a cardboard box and a DVD.
The post In the Microsoft employee price list, why did the BASIC compiler cost less than the BASIC interpreter? appeared first on The Old New Thing.
The danger is real [Scripting News]
AI has enabled hackers to find security holes in widely deployed software much faster, and it is able to find security holes that humans can’t. So there’s been an until now behind the scenes race by the good guys trying find and fix holes be for the bad guys find and exploit them.
At least some of the recent outages were caused by software that was trying to close security holes that were discovered by AI and the actual code that was doing the updating was AI. Probably the first time it’s ever been called on to do this so it probably didn’t understand all the limits of the networks it was working with. But when you’re dealing with a security issue, there really isn’t a lot of time to consider all the options and sometimes you have to take risks. The system going down isn’t the worst thing that can happen in that context.
The danger is real and our economy, if our computer networks were to fail, would collapse in an instant.
I don’t want to be alarmist, but this is a time to be alarmed because even if we had the best people in the top positions in the government, we would still be in danger.
Products require showrunners [Scripting News]
This was a reply to a friend's post on Twitter about how decisions are made in open source communities.
I guess it depends what the goals of the project are.
If you don't have a clear statement of the goals, then you have no means to decide on any specific feature.
I welcome community input on goals, and bug reports and feature requests.
But... the decision belongs to the product showrunner. Try to imagine a great TV series like The Wire or Succession without a showrunner, but rather it was a vote of who showed up one day. It wouldn't fit together with itself as it zigged all across the map.
It's kind of like the US government, never has a working longterm strategy, and is constantly undoing itself.
In the RSS world, as the community leader, I would have listened closely to developers who had skin in the game, a product, either a CMS or feed reader that had a lot of users or who had taken risks in the past that turned into key features for the community. And I would listen for ideas that came from people with no power, because I have missed ideas that came to me that way, the famous near-miss was Adam Curry's "last mile" idea which turned into podcasting. You have to allow an open door for people who see something the rest of us don't.
And every product, open source or not, must be open to competition. So if you don't like what they do, and they won't fix it, then go out and make some news sister or brother. That's how we grow!
But remember to leave the door open for those who follow. Not locked-in, locked-open. :-)

Hello, I have a new album of music out. If you like 15 minute long instrumental post-metal songs played on guitars with too many strings, you might enjoy it. You can listen to it and buy it here. Thank you
Voters Reject ALPRs and Surveillance Tech at the Ballot Box [Deeplinks]
Do automated license plate readers (ALPRs) have any place in our communities? That question has been a hot topic in city council meetings, community conversations, and news coverage around the country for months. This past election day, a couple of U.S communities took it further: to the ballot.
And overwhelmingly, voters decided that, no, these devices should not be deployed on our streets. We agree!
In Maine, the coastal community of York voted to remove the town’s existing ALPR cameras and require that any future proposed installations receive voter approval before proceeding. The local initiative ended up on the ballot after constituents gathered enough signatures on a citizens’ petition for a local ordinance. On Election Day, nearly three-quarters of York voters supported the ban.
Thousands of miles away, voters in League City, Texas also voted against allowing the local police department to continue use of ALPR cameras. That vote was formally approved on November 17, which began a 72-hour window to remove the cameras. Since the election, the cameras have been “bagged” or covered to prevent the collection of data.
At least one city also decided to expand protections afforded to their residents when it comes to the use of surveillance technology. In Pflugerville, Texas, Proposition B passed, now requiring that the City Charter be amended to include “protections governing the collection, use, retention, and oversight of data, facial recognition, and surveillance technologies.” It also requires “a responsible artificial intelligence framework.”
While every municipality has different rules for how to get a local ordinance placed on the ballot, banning use and securing the removal of surveillance tools locally is a powerful way of protecting your community against devices and data collection that goes far beyond your town lines.
Surveillance is a choice, not a mandate, and our communities have the power to refuse it. EFF has supported local communities around the country over the last few years in advocating against the procurement of surveillance technologies in their cities, counties, and states. These victories at the ballot box and in city councils show that when mass surveillance is presented as a policy choice, not a technical necessity, communities can and do reject it.
Do you know what surveillance tools are being used by your local police departments? Check out the Atlas of Surveillance to learn more about the tools deployed in your city, and sign up to volunteer if you want to push for more transparency across the country.
Dirk Eddelbuettel: littler 0.3.24 on CRAN: Two new scripts [Planet Debian]


The twentyfifth release of littler as a CRAN package landed on CRAN today, following in the now twenty-one year history (!!) as a (initially non-CRAN) package started by Jeff in 2006, and joined by me just a little later.
littler is
the first command-line interface for R as it predates
Rscript. It allows for piping as well for
shebang scripting via #!, uses command-line
arguments more consistently and still
starts faster. It also always loaded the methods
package which Rscript only began to do in later
years.
littler lives
on Linux and Unix, has its difficulties on macOS due to
some-braindeadedness there (who ever thought case-insensitive
filesystems as a default were a good idea?) and simply does not
exist on Windows (yet – the build system could be extended
– see RInside for
an existence proof, and volunteers are welcome!). See the
FAQ vignette on how to add it to your PATH. A few
examples are highlighted at the Github repo:, as well
as in the
examples vignette.
This release, the third this year, adds two new example scripts I already use a lot, reflects the updated build mechanism of the documentation website, and carries some small fixes and maintenance.
The full change description follows.
Changes in littler version 0.3.24 (2026-11-17)
Changes in examples scripts
New script
trox.rwrapping tinyroxNew script
checktor.rwrapping checktorSmall edits and tweaks to two existing scripts
Changes in package
Continuous intgegration scripts received minor updates
Documentation website has been redone using altdoc as the driver of the 'material for mkdocs' framework used
My CRANberries
service provides a comparison to
the previous release. Full details for the littler
release are provided as usual at the ChangeLog
page, and also on the package docs website.
The code is available via the GitHub repo, from
tarballs and now of course also from its CRAN page and
via install.packages("littler"). Binary packages are
available directly in Debian
as well as (in a day or two) Ubuntu binaries at
CRAN thanks to the tireless Michael Rutter. Comments and
suggestions are welcome at the GitHub repo.
This post by Dirk Eddelbuettel originated on his Thinking inside the box blog. If you like this or other open-source work I do, you can sponsor me at GitHub.
The Justice Department Wants To Give Patent Trolls More Power [Deeplinks]
Software patents are mostly vague, hard to define, and widely abused. Most tech patent lawsuits aren’t filed by companies that make real products. They’re filed by patent trolls, companies that acquire patents to extract payments through litigation and legal threats.
A patent on one feature of a smartphone shouldn’t give the patent owner the power to threaten the existence of the entire product line. But that is exactly the leverage patent trolls want—and the current administration is helping them to get it.
In two recent patent cases, Radian Memory Systems v. Samsung and Collision Communications v. Samsung, the Justice Department and the U.S. Patent and Trademark Office have asked courts to make it easier for patent owners to get injunctions. These are judicial orders that can force companies to stop selling products or remove features from them, rather than simply pay monetary damages.
The threat of an injunction can pressure a company to pay far more than what a patent is actually worth. In 2006, NTP Inc., a patent holding company with no products of its own, was able to pressure BlackBerry manufacturer Research in Motion Ltd. to pay a $612 million settlement when it was on the verge of an injunction.
In May 2006, the Supreme Court rejected the practice of granting permanent injunctions almost automatically after a finding of patent infringement. In eBay v. MercExchange, the high court held that patent owners must satisfy the same tough requirements that plaintiffs in non-patent cases must meet to get a permanent injunction. After eBay, patent owners had to show “irreparable harm,” that they can’t be adequately compensated by money, that the “balance of hardships” favors the plaintiff, and, critically, that an injunction would not harm the “public interest.”
At EFF, we celebrated eBay v. MercExchange as a major win for internet users. More than twenty years ago, we saw that software patents were going to be a disaster—not just for small companies (which they are), but for freedom of expression online. As EFF explained in its brief:
The United States Patent and Trademark Office has issued patents on methods fordownloading video programs, publishing web pages, sending email messages, making internet telephone calls, and even online fundraising methods. Injunctions against uses of these technologies—and many similar technologies—will inevitably affect, and may even chill, free expression on the internet.
The eBay rules make sense because the monopolies provided by patents are only justified when they serve a public purpose: promoting scientific and technological progress. Enforcing patents is not supposed to come at the cost of later innovators, free expression, or people’s access to technology.
Now, two decades after eBay, the government is urging courts to interpret those protections in ways that could give patent owners greater leverage. It’s unusual for the government to intervene in private patent disputes, but the current administration has done so repeatedly—and not on the side of the public.
In June 2025, the Justice Department and Patent Office filed a “statement of interest” in Radian Memory Systems v. Samsung, a dispute over patents involving solid-state drives (SSDs), the storage devices commonly used in modern computers. Radian, a patent assertion company tied to Fortress Investment Group, sought a preliminary injunction that would block sales of Samsung’s products even before a judge or jury had decided whether there was patent infringement.
In its statement, the government argued that even a patent owner whose business depends entirely on patent licensing could suffer irreparable harm, because calculating how much money it should get might be difficult. “In cases of unique assets, courts have commonly found irreparable harm when damages are difficult to calculate,” the DOJ writes in its brief.
But courts regularly resolve disagreements about patent royalty rates, a patent’s contribution, and comparable licenses. The fact that those disagreements exist does not, by itself, establish that monetary damages wouldn’t be enough to compensate the patent owner. If courts adopted the DOJ’s views here, a difficult but ordinary part of patent litigation could become a reason for finding irreparable harm, making it easier for patent owners to seek injunctions that threaten entire product lines. Pure patent-licensing businesses would love that—they would routinely start to ask for injunctions, since eBay’s most important protections would be weakened.
The government also says that “the prospect of an injunction can facilitate negotiation among the parties.” That’s exactly the problem. A company negotiating under threat of shutdown might pay massive sums to patent litigation shops in order to avoid disruption to product lines or customers. The payment is more likely to reflect the value of the threat, rather than the value of a patent. Radian ultimately withdrew its request for a preliminary injunction, but the government's arguments about when injunctions should be available remain concerning.
Remarkably, the government returned to this argument in February of this year, in a case called Collision Communications v. Samsung, which had already gone to trial. In this case, Collision, a patent-licensing entity that acquired its patents from a defense contractor, was awarded a $445.5 million jury verdict for infringement of four patents, and then sought an injunction.
Even though the jury had awarded Collision $445.5 million in damages, the government still intervened in the case, arguing that patent owners like Collision, which do not make products, should not be denied injunctions because they rely on patent licensing. They also argued that the difficulty of calculating monetary damages can support an injunction.
Although the court agreed that Collision had suffered irreparable harm and that monetary damages would be inadequate, U.S. District Court Judge Rodney Gilstrap rejected Collision’s argument that ongoing patent infringement automatically establishes irreparable harm. He ultimately denied the injunction because Collision didn’t satisfy two other requirements of the eBay test: showing that the balance of hardships favored an injunction and that an injunction would not harm the public interest.
Now Collision has appealed, and the argument is in front of the Federal Circuit, the nation’s top patent court. A brief from the Public Interest Patent Law Institute (PIPLI) explains what is at stake: when a patent owner doesn’t have any products, an injunction can prevent the public from accessing critical technology altogether. Since the patents here involve how mobile phones connect to cellular networks, “the effect on the public goes far beyond what these patents claim as improvements,” PIPLI explains.
The outcome could extend well beyond these two companies. The eBay test requires courts to consider who a permanent injunction would hurt, and who would benefit—including the public. A patent owner’s desire for more negotiating leverage should not override the interests of millions of people who rely on their phones. Yet that’s exactly the kind of leverage the government’s arguments could make it easier for patent owners to obtain, at the expense of the public.
Patent owners can already collect damages and royalties when their patents are infringed. But they should not get a shortcut to shutting down tech products just because calculating damages is hard work.
The Justice Department should defend the eBay safeguard. Instead, this administration is helping patent owners find ways around it. Courts should reject those arguments. We shouldn’t even have to say it, but we do: making patent threats more valuable does not align with the public’s interest.
This post is the second of a three-part series about how the current administration is using its power to give patent holders more power at the public’s expense. The final post will publish next week. See our previous post:
The Paramount-Warner Brothers Deal Could Usher in Another Age of Lost Media [Deeplinks]
There are all sorts of reasons to be against the merger of Paramount and Warner Brothers-Discovery. There's the obvious problem of increasing concentration in the already pretty-concentrated film and TV industry. People have problems with Paramount's owner Skydance interfering with its news coverage and late night comedy. But one of the biggest is the way we are losing choice and access to information and culture.
In the context of the digital world, there are two major problems with these mega mergers. One, as we've said in the past, is that it further degrades the already awful state of mainstream streaming services. In short, by increasing the amount of legacy content under their control, major studios don't have to invest in either new content or well-engineered services to get users. Plus, they can pool the data they have on users together in an increasing assault on consumer privacy. A monthly subscription and more information about your habits and interests? Win-win for them.
Another problem is the disappearing of content. In the digital era, there should be no more lost media. Making and storing copies of media is easier and cheaper than it ever has been. The idea of the persistence of content online has become the adage "the internet never forgets."
However, since more and more media is locked behind subscription services under the control of fewer and fewer companies—and as physical copies, or even just digital copies that are actually owned by consumers also vanish—access to our common culture is at risk. Incentives to take information and media offline should raise huge red flags. Unfortunately, they are multiplying.
First, there's the impulse of merged companies to offset the cost of their merger by shelving projects and claiming them as tax write-offs. We saw this the last time Warner Brothers was taken over, with projects being ended in order to take advantage of a specific kind of tax benefit. It has little to do with the quality or even how much or how complete a project is—money is the driving factor and we as a culture are all poorer for it. And we all know it. That's why the outrage eventually led to Coyote vs Acme being released by a much smaller studio. But not every project can count on having the perfect storm that brings a movie or show back from the dead.
Second, there's the imposition of a new owner's own goals and beliefs upon its new acquisition. Some choices might seem kind of benign, like Discovery axing a lot of family-friendly and kid-oriented content from HBO Max. Of course, when one of the things affected is a pillar of childhood like Sesame Street, the loss of access to old episodes becomes a loss to the culture and not just a change in direction.
Another area where we might lose access to information is in the radical shift in direction for news reporting. Reporters have resigned and more are being offered buy-outs to support the change in direction. Whether this will escalate to older projects being removed from streaming services or quietly buried in the recommendation algorithm is yet to be seen, but remains a real possibility. And it's not lost on anyone that one of the outlets reporting on the chaos at CBS News was CNN, which is now owned by the same people who own CBS News. The loss of diverse sources of news, as imperfect as we may have thought they were, hurts all of us. It makes it harder to access information and diverse points of view.
Finally, media disappears as licenses expire and as studios decide they no longer want to pay residuals or backend deals to the creative people who made the work in the first place. Again, this looks like business decisions but if the works were exclusively available via streaming, those movies disappear forever. That both contributes to the idea that works are disposable and that paying the workers who made the art is not as important as shareholder value.
On top of all of this, draconian copyright regimes and the anti-user product designs they create have made it nearly impossible for people to archive this material on their own—as many used to using VCRs. It’s easy to see a crisis in access to culture and information brewing, at the same time that it should be easier than ever to preserve and make available our shared digital culture.
The Big Idea: Emily Gray [Whatever]

Romance, spaceships, and an argument for basic human decency and safety? That’s what today’s Big Idea brings us, as author Emily Gray recounts the turbulent early 2020’s as an inspiration for her newest novel, By the Light of the Stars. Read on to see how the safety and kindness people deserve on Earth should also be afforded to those who are in space.
EMILY GRAY:
Every book needs a hero—but not every hero needs to be brave.
I began writing By the Light of the Stars at a moment in my life when I wasn’t feeling particularly brave. In my mid-twenties, when I was both freshly postpartum and living through a global pandemic, every little task was laced with indecision. The most meaningful human interaction I had on a daily basis was with the employees at my local Dunkin Doughnuts drive-thru. (Which is also the reason one of my son’s first words was “hashbrowns.”)
I was lonely. I was scared. Every single choice I made seemed to hold a hidden moral weight. Everything became a debate—physical health vs. mental health. Community support vs. community safety. It was in this environment of constant ethical embattlement that I found myself wanting to write something simple and fun as a relief from the never ending deluge of horror.
I had never thought about writing science fiction before. I’d also never written an adult romance before, but I had just come out of a writing mentorship program where I had worked with a professional romance author, and I was itching to try out my new skills. The premise came first—a romance novel set in space. A man, a woman, and a spaceship with one bed. What could go wrong?
What ended up on the page was much less straightforward. As the character of Lyrii Thana began to develop over the course of the first few drafts, I found that she reflected the same level of ambient anxiety that we were all living with. At the beginning of the book she is torn between fear for her physical safety and the duty she owes to her family. As the story progresses the conflict begins to shift as she realizes that the systems she was willing to risk her life for may not hold the same promise of safety for everyone.
And that idea, finally, became the Big Idea behind By the Light of the Stars. No matter who you are—a princess, a rogue space pilot, or a refugee stranded on a tiny moon—we all deserve peace. There is no amount of shame or fear you can feel that makes you unworthy of love. There is no place you could possibly come from that makes you undeserving of safety.
We live in a world that loves to make us fight for our space in the box of “worthy” people who deserve basic human decency. Think about the metaphor “crabs in a bucket.” When one crab tries to climb out of the bucket, the other crabs will pull it back down. We are always looking for reasons that someone else doesn’t deserve the things that we want, even if those things should be afforded to every single human being on this planet without hesitation or qualification.
The Big Idea behind By the Light is one that I had been mulling over since 2020 and the dark years that followed, when we all engaged in spirited debates about whether or not Walmart employees were important enough to protect from exposure to deadly diseases at work, or if spending a counterfeit twenty dollar bill was an adequate reason to be executed on the street by the police.
No matter who you are, no matter where you come from, you deserve to be loved as you are. You deserve peace, and safety, and the right to determine your own future. That is the world I want to live in, and if you want to live in it too, we’re going to have to fight for it.
By the Light of the Stars: Amazon|Barnes & Noble|Bookshop|Powell’s|Scuppernog Books (signed copies)
I'll put up a link for the BonBon download tomorrow morning. I want to be around while people try it, in case there are problems or questions.
The Value of Human Expertise in The Software Factory [Radar]
“Any sufficiently advanced technology is indistinguishable from magic.” – Arthur C. Clarke
Most developers now write less code by hand. Gergely Orosz recently posted that modern software engineering is no longer done without LLMs and will no longer be done without them. Some miss writing code, while others question how much of the code that agents produce should be read. Writing and reading code gave a lot of developers satisfaction and identity, and as Kent Beck has put it, a sense of competence. I saw this in real time.
Ten years ago, I’d sit at conferences and feel a sense of wonder whenever anyone was brave enough to do a live demo. I felt gleeful when they wrote lines of code, went back to fix mistakes, and made something cool and interesting appear on the screen in front of me. It was magical, and I’m sure that magic is why a lot of developers got into this industry. I can partly understand the sense of loss that people are experiencing. I saw magic, they were in charge of the craft of their code, and that hands-on task has now been given to agents. Where does that expertise go when AI is now writing so much of the code?
As Tim O’Reilly wrote in his recent Radar post, O’Reilly is a business built on cultivating and sharing human expertise. Our job is to find the high ground where that expertise still matters. For developers working in a new world of agentic software factories, I think the expertise you built writing and maintaining software hasn’t gone, it’s just moved. Your expertise now shapes how agents produce software and what evidence you need before we trust the result. To me, AI is enabling you to be magical faster.
Agents amplify whatever you give them, but you need to understand it in the first place. I couldn’t swarm a fleet of agents in the same way a developer can because I don’t have the expertise. You need to understand code. The expertise has gone to a new level of abstraction.
When I spoke recently with Avi Flombaum, the founder of Flatiron School, he agreed that developers’ value was never solely in writing or reading code. AI changes the mechanics, but experience still matters for understanding complex problem domains, articulating what needs to be built, and bringing judgment and ambition to the work. In a separate conversation with Ken Kousen, he pointed out, “We’ve been working with third-party code generators for years; we just called it outsourcing.” This new world of designing AI workflows, setting guardrails, and managing agents much as you would an engineering team, reveals a chance to use accumulated expertise more. It’s your software engineering expertise that matters.
Software factories make this shift especially visible. Companies are now putting agents to work across the development lifecycle, aiming to take work from an initial signal through implementation, validation, and deployment without a person at every step. But generating more code is only part of that process. Without changes elsewhere, you can burn a lot of tokens producing a pile of pull requests that someone still has to review. Anthropic’s AI-native SDLC playbook points out that speeding up implementation shifts pressure onto planning, testing, review, handoffs and approvals, and faster coding tools don’t speed those up on their own. Someone has to understand the whole process well enough to redesign it.
In a software factory, that judgment has to be built into the system. Humans design the workflow, define the conditions under which work can proceed, and decide which exceptions need their attention. Anthropic reports that Claude authors about 80% of the code merged into its codebase, alongside a review process that combines automated checks with human oversight according to risk.
The state of the code matters too. Adam Tornhill and the CodeScene research team found that across C++, Java, and Python codebases, agents working on unhealthy code used 35–45% more tokens to complete the same tasks. That makes refactoring the parts of a codebase agents touch most a sensible investment, but someone has to know which parts those are, decide what “better” looks like, and confirm that behavior hasn’t changed.
Context works the same way. In Port’s testing, giving agents structured context cut costs by about 58% compared with direct access to separate MCP servers. Adding instructions on where to find relevant information pushed the savings to around 80%. Those figures are specific to Port’s experiment, but the work behind them will be familiar to any experienced developer: knowing which relationships in a system matter, and keeping that knowledge accurate as the system changes. Testing tells you whether a particular change works, but evaluating the workflow tells you how reliably it produces acceptable changes and when a person needs to step in.
In Evals for AI Engineers, Shreya Shankar and Hamel Husain describe starting with real traces of what the system did. First comes open coding: reading the traces and writing short notes on what went wrong. Then comes axial coding: grouping those notes into failure categories based on what you actually see. A developer who has spent years debugging production systems will spot the failures that matter and set aside the ones that don’t far faster than someone who hasn’t. That’s where developers’ experience shows up now: in the problems they define, the standards they set, and the evidence they demand before anything ships.
Every shift in every industry has made some people miss the old ways, but the industry has survived. Back in December 2025 I wrote: “AI rewards strong engineering; it doesn’t replace it,” and I stand by that statement. Developers are still magical to me, even when they’re not the ones writing the code. I couldn’t build a software factory myself because I don’t have the years of experience it takes to know where agents should work, how to guardrail them, and how to judge what they produce. The developers who do are the ones I trust to build it. And, as Ben O’Mahony pointed out to me recently, “Those who have a lot of exposure to Agentic engineering have seen past the magic and are back to engineering!” It’s an exciting time to be involved.
Want to understand how to think about engineering craft in this new world? Join Avi Flombaum for his new series, The Agentic Rethink, starting Wednesday, Jan. 13, 2027, on the O’Reilly platform.
Redict deprecated in favor of Valkey [LWN.net]
Drew DeVault has announced that Redict, a fork of Redis that was created in response to Redis's 2024 license change, has been deprecated. He recommends switching to Valkey, the permissively licensed Redis fork supported by the Linux Foundation. The two projects are mutually compatible, so switching should be as simple as changing which package is installed and renaming the configuration file.
I had hoped to rally the Redis diaspora around a copyleft initiative, to protect ourselves from future rug-pulls, and made Redict to serve this purpose. However, with the valkey project's success, and Redis's return to a copyleft license, Redict was not able to build a sustainable community.
We recommend that Redict users switch to valkey, which uses a permissive license but has better long-term prospects. We advise against switching back to Redis; though it is once again open source, and copyleft, it uses a contributor license agreement which will facilitate another rug-pull when Redis has a bad financial quarter.
Podcast: How Claude Code allowed me to think big. We can have the web we want and don't have to wait for a big company to do something to help the web, when all evidence of history is the exact opposite. They consume the goodness and we're left with yet another totally predictable tech mess. Hope this came out okay, I recorded it on a drive to Kingston, NY this morning.
Privacy's Defenders Podcast: Snowden Exposes NSA’s Lies [Deeplinks]
By 2013, EFF had spent seven years arguing in court that the National Security Agency was sweeping up ordinary Americans’ communications, including through the secret room that whistleblower Mark Klein had exposed. The government would neither confirm nor deny it, and outside the courtroom the public seemed to have moved on.
Then, in early June, documentary filmmaker Laura Poitras and journalist Glenn Greenwald mysteriously missed a Freedom of the Press Foundation board meeting at EFF’s offices. It turned out they were in Hong Kong, meeting an NSA contractor who had been secretly writing to Laura for months. His name was Edward Snowden, he had thousands of secret documents proving the government had in fact been spying on millions of Americans. When he subsequently revealed himself, a photo of him sitting behind his laptop – emblazoned with a big red EFF sticker – went worldwide.
Welcome to the fourth episode of “Privacy’s Defenders,” a podcast about the people – lawyers, journalists, hackers, and others – who’ve fought to secure your digital liberties since before most people even knew what the internet was.
(You can also find this episode on the Internet Archive and on YouTube.)
In this episode, former EFF Executive Director Cindy Cohn talks with Laura Poitras about how she got to that historic moment, including her years of expertise in communicating via encrypted channels. Freedom of the Press Foundation Executive Director Trevor Timm – a former EFF activist – shares his recollection of the day the first Snowden story broke. For EFF and its clients in Jewel v. NSA, Snowden’s documents were proof of what the government had spent years refusing to confirm. As Cindy puts it, “We were struggling along in the mud, and we felt like somebody gave us wings.”
It's the story of the lawyers who fought for your privacy, the government that lied about spying on you, and the whistleblower who blew it all wide open.
The “Privacy’s Defenders” podcast is a follow-up to Cindy’s book, “Privacy’s Defender: My Thirty-Year Fight Against Digital Surveillance,” bringing to life pivotal moments in the voices of those who fought for your rights. Sales of “Privacy’s Defender” benefit EFF, so pick up your copy today!
Joanne Elgart Jennings co-produced and created this podcast.
Jarrod Sport co-produced, mixed, and mastered it.
Corinne Ruff is our story editor.
We had additional help from Rachel Estabrook and Alison Broverman.
The original music was composed and performed by Nat Keefe of Hot Buttered Rum with Ben Andrews on the fiddle.
[$] Zellij manages terminal workspaces with style [LWN.net]
Zellij is a relatively new entrant in the terminal-multiplexer category. Like GNU Screen and tmux it gives users the ability to manage a workspace inside a terminal with split panes, provides session management, and so forth; but Zellij also includes a web server for browser access to a terminal session, is extensible via a plugin API, and is likely more beginner-friendly than its predecessors. Its most recent release, version 0.46, adds a standalone terminal emulator, a built-in inbox for notifications, and a settings screen so users can configure the application without fussing with configuration files. While the low version number might suggest that it is not yet ready for serious use, it seems stable and full-featured enough to meet the needs of many users.
Security updates for Tuesday [LWN.net]
Security updates have been issued by AlmaLinux (.NET 10.0, .NET 11.0, .NET 8.0, .NET 9.0, bind, bind9.18, buildah, c-ares, cjose, cockpit, cockpit-files, cockpit-machines, cockpit-podman, containernetworking-plugins, crun, delve, dhcp, dogtag-pki, dovecot, dpdk, edk2, emacs, environment-modules, expat, fetchmail, firefox, flatpak, flatpak-builder, freerdp, gcc, gcc-toolset-15-gcc, gcc-toolset-16-gcc, git-lfs, glib2, glibc, glycin-loaders, gnome-remote-desktop, go-fdo-client, go-fdo-server, grafana, grafana-pcp, gstreamer1, gstreamer1-plugins-bad-free, gstreamer1-plugins-base, guava, gvfs, gvisor-tap-vsock, ignition, iperf3, java-1.8.0-openjdk, jq, kernel, librabbitmq, libreswan, librsvg2, libsoup, libsoup3, libX11, libXi, libxml2, libXrender, libXtst, lrzsz, microcode_ctl, mingw-glib2, mod_auth_openidc, mod_http2, NetworkManager, nginx, nginx:1.24, nginx:1.26, nodejs:24, nodejs:26, oci-seccomp-bpf-hook, openexr, openssh, openssl, pcp, perl-DBI, perl-DBI:1.641, perl-URI, php:8.4, podman, polkit, postgresql:16, python-jwcrypto, python-oauthlib, python-tornado, python3, python3.12, python3.9, rpm, rsyslog, runc, rust-sequoia-sq, sos, squid, sssd, tesseract, tftp, tomcat, tomcat9, unbound, util-linux, webkit2gtk3, wireshark, xdg-dbus-proxy, xfsprogs, xorg-x11-server, xz, and yggdrasil), Debian (gnocchi, kernel, lightdm, roundcube, zaqar, and znc), Fedora (assimp, chromium, criu, freerdp, maturin, mysql8.4, perl-Catalyst-Plugin-Authentication, python-jiter, python-pymdown-extensions, python-pysequoia, qtox, ruff, rust-afterburn, rust-astral_async_zip, rust-clearscreen, rust-coreutils, rust-jiter, rust-lzma-rust2, rust-mailparse, rust-pyo3-introspection, rust-python-pkginfo, rust-sccache, rust-serde_json, rust-testresult, rust-zip, selenium-manager, tpm2-tss, ty, and xfsprogs), SUSE (apache2, azure-storage-azcopy, container-suseconnect, containerd, crane, dpdk, ghostscript, google-cloud-sap-agent, google-osconfig-agent, govulncheck-vulndb, graphifyy, hauler, helm, helm3, hivex, java-21-openjdk, java-25-openjdk, libevent-2_1-7, libmikmod-devel, libXi, mtools, nodejs24, open-iscsi, parted, podman, psqlODBC, python-M2Crypto, python-tornado6, python3, re2c, rsyslog, speex, thunderbird, valkey, vsftpd, and zbar), and Ubuntu (buildstream, cairosvg, commons-configuration2, deluge, dokuwiki, eterm, gnupg1, groovy, gst-plugins-bad1.0, gst-plugins-base1.0, h2o, htmldoc, net-snmp, netkit-rsh, node-moment, openjdk-25-crac, pdfresurrect, pillow, postsrsd, psensor, rlottie, sos, sosreport, vim-syntastic, yadifa, zbar, and zutils).
If BonBon were made by a big company instead of by an aging
hippie software developer working with his super-powerful friend
Claude, we would have gone on a press tour, probably via Zoom, of
all the major pubs to prepare them for a fundamental change in what
we think of as the web. We would have produced a huge example site,
and worked with leading content publishers like the NYT, Kottke and
Heather Cox Richardson to get their work BonBon-ready. We
would have a developer conference where web devs and political
leaders would speak about the importance of writing on the web. I
would have contacted Tim Berners-Lee and asked him to write a
preface for the docs, telling about his vision now, over 30 years
since the inception of the web, and what he thinks of the future.
Then I would speak, and say enough of that, here's a demo, and then
I would give you the URL of the download page, and ask you to keep
an open mind to what's possible. If you do, imho, you will be
rewarded. But I won't be doing any of that. Instead I asked
ChatGPT
to explain BonBon from a historic perspective, based on a
conversation we had yesterday. And later today or tomorrow I will
link to the download site from my blog home page, and encourage you
to find out what having a new web Writer's Web might mean to
you. Till then, your friend, web writer and reader, Dave Winer.
;-)
Also -- I would have briefed Cory Doctorow, because imho BonBon strikes a blow for de-shitification which I hope becomes as much discussed as en-shitification.
I would have asked John Gruber, the inventor of Markdown, to give a talk. I'd give him a big hug and thanks for having such a great vision, so useful, so many years later.
Pluralistic: Remembrance of proteins past (17 Nov 2026) [Pluralistic: Daily links from Cory Doctorow]
->->->->->->->->->->->->->->->->->->->->->->->->->->->->->
Top Sources: None -->

Without a doubt, the best piece of media from the 2026 midterms was Scott Colom's "Pick another senator instead" ad from his triumphant Mississippi senate campaign against GOP incumbent Cindy Hyde-Smith:
https://youtu.be/zpUnm09lTUk?si=3ApbHida5_VpQCLB&t=2219
Some background: Colom is the first Black Mississippi senator elected since Reconstruction gave way to Jim Crow. He's also the first Democratic Mississippi senator since 1982. Colom's campaign shifted the statewide vote leftward by 19 points, and he won a quarter of the state's white votes.
Colom ran a great campaign and promoted great policies, but also: he ran one of the great political ads of all time. That ad skewered Hyde-Smith's "let them eat whey powder" remark to WLOX Biloxi host Hugh Keeton, who asked her about the cost of living crisis and the high price of beef, to which she replied that people "have so many proteins to choose from":
Colom's ad plays a montage of Mississippians expressing disgust with Hyde-Smith's response, saying "I'd rather choose another senator instead." Colom was quick to credit content creator Ryan Sayles, who joined the campaign after doing some freelance work for them, as the ad's mastermind:
https://www.politico.com/news/2026/11/12/ryan-sayles-scott-colom-viral-protein-ad-01163508
Much has been said about the ad's style, especially the viral "s-h-e-e-e-i-t" voiced by US Army vet Russ Hudson, who stepped in to do the ad when his father declined to curse on camera:
https://edition.cnn.com/2026/11/15/politics/scott-colom-viral-protein-ad-mississippi-senate
But the most important analysis on the ad is of its substance, specifically how it repudiates one of the key doctrines of neoliberal, austerity economics, as David Dayen writes for The American Prospect:
https://prospect.org/2026/11/16/how-the-mississippi-senate-win-exposed-austerity-logic/
Neoliberalism is the signature achievement of the "law and economics" movement that came out of the University of Chicago. The central conceit of law and econ is that economics is a "hard science" (not a social science) and that its domain is a deterministic, quantifiable physics of human behavior. Economists went so far as to create a fake "Nobel Prize" in economics in a bid to elevate their work out of the social sciences:
https://pluralistic.net/2024/09/18/falsifiability/#figleaves-not-rubrics
This "science" claims it can replace squishy, qualitative questions with mathematical models that can output the objectively correct answer to every thorny political question, thereby substituting an obscure form of mathematics for political deliberation:
https://pluralistic.net/2023/04/03/all-models-are-wrong/#some-are-useful
This is a remarkably cheap and transparent stunt. To produce this "mathematics of human behavior," you must first quantize all the qualitative questions so that they can be plugged into variables in econ equations. But here's the problem: assigning a numeric value to a qualitative factor is a qualitative exercise!
When an economist decides that the pain you'll experience as a result of their policy prescriptions is worth "7" while the benefit is worth "8," they are not doing objective work, they're just declaring their own judgments (and biases) to be empirical observations, while demoting your judgments to mere "feelings" (and biases):
https://pluralistic.net/2024/09/18/falsifiability/#figleaves-not-rubrics
Economism doesn't just eliminate qualitative questions from policymaking: it incinerates all of those qualitative factors so that economists can perform mathematics on whatever dubious quantitative residue remains in the crucible:
https://locusmag.com/feature/cory-doctorow-qualia/
This is where Scott Colom's brilliant campaign ad comes in. As Dayen points out, when Hyde-Smith made her "many other proteins to choose from," gaffe, she was referencing a key piece of economic theory that has been thoroughly weaponized by the neoliberals: "substitution."
On its face, substitution is just the commonsense proposition that when prices for one good or service go up, some consumers will substitute another. When gas prices go up, more people ride the bus. When Instagram increases its ad-load, more people switch to Mastodon or Bluesky. When your ISP jacks up your price, you might switch to another carrier.
So far, so good. Indeed, one of the best things about digital products and services is how low digital "switching costs" (the cost you bear when switching from one service to another) can be. The lower the switching costs are, the easier it is to substitute one thing for another.
This means that, in a state of nature, tech bosses have to be careful about enshittifying their products, lest their users defect to a rival. This is why tech bosses have spent decades doing everything they can to jack up those "switching costs." They want to convert all their users into hostages:
https://www.eff.org/deeplinks/2021/08/facebooks-secret-war-switching-costs
Substitution is real and it makes sense. The problem comes when neoliberal economists use this idea in policy. In the early 2010s, Barack Obama proposed applying substitution to the American welfare system through something called "Chained CPI."
"CPI" stands for the "Consumer Price Index": this is a measurement of the cost of a "basket of goods" (a bunch of supposedly representative household items) that is used to make inflationary adjustments to a variety of payments. When the CPI goes up, so do social security, welfare and disability payments. Otherwise, inflation would continually reduce the living standards of everyone who receives these entitlements.
"Chained CPI" takes the CPI and applies substitution to it. Rather than asking whether hamburger just got more expensive, the economists who calculate CPI ask whether the cheapest protein at the grocery store got more expensive (because hamburger can be swapped out for another protein).
Chained CPI's intent and effect is to reduce payments to retirees, disabled people, and poor people. Chained CPI is always going to be lower than CPI, because chained CPI only rises when the cheapest "substitute" for one of the items in CPI's "basket of goods" gets more expensive. In effect, the "basket of goods" becomes a transdimensional basket, one that contains every substitute good that might have gone into the basket in all possible parallel universes. Economists get to universe-shop for the dimension where that basket has the lowest cost, and then we all have to live in their chosen universe.
Obama tried to adopt it 2013 as part of a "grand bargain" to reduce the deficit, but was thwarted by the Tea Party Caucus, who refused the grand bargain on the grounds that it contained an infinitesimal tax rise for the richest Americans:
But chained CPI is one of the most cherished ideas of neoliberal thinktanks, so it came back in 2017 for Trump's tax giveaway to the super-rich, whose costs were partially offset by using chained CPI to calculate tax brackets, the standard deduction, and the Earned Income Tax Credit:
https://newrepublic.com/article/145688/biggest-trojan-horse-republican-tax-plan
As Dayen writes, "[This created] a regressive tax increase by eroding deductions and credits and pushing people into higher tax brackets. The wealthy were unaffected by this since they were already in the highest tax bracket and itemized rather than using the standard deduction."
Which brings me back to Cindy Hyde-Smith's foot-in-mouth remarks about "so many proteins." Whether or not Hyde-Smith knew it, she was referencing this substitution/chained CPI doctrine when she told people that beef inflation didn't matter because other proteins were available. In doing so, she was performing economism's cheapest trick: pretending that her opinions are objective facts, while other people's opinions are just feelings.
As Dayen writes, "[W]ho decides whether the cheaper product they switch to is 'similar' to the one that’s become so expensive that the consumer must give it up?…The logic is, approximately: You're not doing as badly as you think, so pick another protein and quit your whining."
People do substitute one thing for another as a matter of economic necessity. But the idea that a "substitute" is an "equivalent" can only be accepted if you first buy into the economist's conceit that all qualitative matters can be safely incinerated, leaving the expert to do math on the quantitative ash.
In this conceit, if you can't afford hamburgers and end up substituting chicken or fish, then you've found a new protein and have lost no "welfare." If you think otherwise, then you are expressing an irrational preference (unlike economists, whose preference for having a Nobel prize of their own is so empirically correct that it could be detected by a Martian peering at Earth through a telescope).
It's not only Cindy Hyde-Smith who unconsciously metabolized the idea of substitution as "rationality"; it's the voters, too, who recognized in Hyde-Smith's remarks the arrogance of policy elites who've spent decades discounting their views as "feelings" while declaring their own views to be experimental validated facts. Not only do voters recognize this move: they hate it.
They know that elites are perfectly capable of expressing strong views about qualitative matters and moving heaven and Earth to achieve a life that fits with their aesthetics. They know that the same Ivy League economists who dismiss their preferences as "irrational" will revel for 4,000 pages' worth of Marcel Proust expounding on the spiritual, intangible reasons for choosing his favorite baked goods.
Economics is the study of why people do things, but somewhere along the way it became a club used to force people to do the things that powerful people prefer. The (alleged) "rationalism" of economism has worn out its welcome. You don't need an economics degree to understand why that "rationalism" is a cheap trick: after 50 years of neoliberalism, a Martian with a telescope could spot it.

The Top 3 “Essentially Progressive” Palantir Products https://www.necessaryfictions.blog/p/the-top-3-essentially-progressive
Introducing the Atmosphere Community Cooperative https://atmosphere.coop/updates/introducing-the-atmosphere-community-cooperative
Tech Companies Are Trying to Shift the Entire Concept of Privacy (Again) https://www.eff.org/deeplinks/2026/11/tech-companies-are-trying-shift-entire-concept-privacy-again
Twenty Minutes Into the Future: On Launching “Terminal Values” https://www.oblomovka.com/wp/2026/11/14/twenty-minutes-into-the-future-on-launching-terminal-values/
#20yrsago Billy Bragg and manager: The Internet is for sharing files http://news.bbc.co.uk/2/hi/entertainment/6148654.stm
#20yrsago Second Life struggles with copying https://web.archive.org/web/20061209112340/http://nwn.blogs.com/nwn/2006/11/second_life_clo.html
#20yrsago BestBuy: our prices are copyrighted https://web.archive.org/web/20061114201037/https://arstechnica.com/news.ars/post/20061114-8218.html
#20yrsago Audio from Gilmore/Barlow talk at USC https://web.archive.org/web/20070202190231/http://centeronpublicdiplomacy.com/podcasts/061113_gilmore_barlow.mp3
#20yrsago Paramount/MPAA: it’s illegal to put DVDs on iPods https://web.archive.org/web/20061119111822/https://www.eff.org/deeplinks/archives/005010.php
#15yrsago OWS library is rebuilding after being trashed by NYPD, needs your donated books https://peopleslibrary.wordpress.com/contribute/
#15yrsago San Francisco’s iconic neon Yahoo! sign is coming down https://web.archive.org/web/20111118012241/https://www.thesfegotist.com/editorial/2011/november/16/end-era-yahoo-billboard-comes-down/
#15yrsago New Zealand Prime Minister sends police to raid major news outlets over covert recording of negotiations with far-right party https://www.rnz.co.nz/news/politics/91307/john-key-defends-resources-used-on-tape-investigation
#15yrsago NY Deputy Mayor: press don’t have the right to report in vicinity of NYPD ops https://web.archive.org/web/20111119001027/https://ny1.com/content/news_beats/inside_city_hall/150926/ny1-online–deputy-mayors-defend-zuccotti-park-raid
#15yrsago Sustainable Materials: indispensable, impartial popular engineering book on the future of our built and made world https://memex.craphound.com/2011/11/17/sustainable-materials-indispensable-impartial-popular-engineering-book-on-the-future-of-our-built-and-made-world/
#15yrsago Oxford city council: every cab must have a CCTV to record riders’ conversations https://www.bbc.com/news/uk-england-oxfordshire-15720998
#15yrsago Walmart smears worker-based chat app with lies and scare tactics https://web.archive.org/web/20161115190524/https://consumerist.com/2016/11/15/walmart-warns-workers-dont-download-chat-app-from-labor-organization/
#15yrsago Stolen government of Malaysia certificate used to sign malicious fake Adobe software update https://web.archive.org/web/20111116182552/https://www.f-secure.com/weblog/archives/00002269.html
#15yrsago Secret documents reveal the flimsy case for Ofcom to give into BBC’s public TV DRM demands https://web.archive.org/web/20140212005011/https://www.theguardian.com/technology/2011/nov/14/bbc-hd-drm
#15yrsago HOWTO attain radical hotel-room coffee independence https://memex.craphound.com/2011/11/14/howto-attain-radical-hotel-room-coffee-independence/
#15yrsago Chapel Hill sends SWAT team to arrest Occupy “anarchists” https://web.archive.org/web/20111114130328/https://www.newsobserver.com/2011/11/13/1641362/activists-take-over-vacant-franklin.html
#15yrsago Real cost of patent trolling https://web.archive.org/web/20111115134326/https://feld.com/wp/archives/2011/11/the-real-cost-of-patent-trolls.html
#15yrsago Joe Biden: SOPA is Un-American – but not when America does it https://www.techdirt.com/2011/11/15/vp-joe-biden-explains-why-sopa-protect-ip-are-anti-american-bad-idea/
#15yrsago OWS: NYPD occupy Zucotti Park, but what are their demands? http://occupywallst.org/article/nypd-occupying-liberty-square-demands-unclear/
#15yrsago The Freedom Maze: a different sort of slavery-time alternate history https://memex.craphound.com/2011/11/16/the-freedom-maze-a-different-sort-of-slavery-time-alternate-history/
#15yrsago Bundled, Buried & Behind Closed Doors: documentary on the net’s hidden physical infrastructure https://vimeo.com/30642376
#10yrsago Facebookers defy Zuckerberg, form fake news “task force” https://www.buzzfeednews.com/article/sheerafrenkel/renegade-facebook-employees-form-task-force-to-battle-fake-n#.jrDKxryP
#10yrsago Embarrassed New Yorkers force Trump Place to change name https://web.archive.org/web/20161115214232/https://www.bloomberg.com/news/articles/2016-11-15/manhattan-s-trump-place-to-change-name-use-street-addresses
#10yrsago Here are the devastating capabilities of the weapons Obama will leave behind for Trump https://www.nytimes.com/2016/11/14/us/politics/harsher-security-tactics-obama-left-door-ajar-and-donald-trump-is-knocking.html
#10yrsago US foreclosure map predicts US battleground states map https://mathbabe.org/2016/11/14/guest-post-the-foreclosure-vote/
#10yrsago Anish Kapoor banned from using world’s pinkest pink in retaliation for hoarding the blackest black https://web.archive.org/web/20161112235050/https://thecreatorsproject.vice.com/blog/the-worlds-pinkest-paint
#10yrsago Remember when they told us Hillary, not Bernie, would beat Trump? https://fair.org/home/polls-showed-sanders-had-a-better-shot-of-beating-trump-but-pundits-told-you-to-ignore-them/
#10yrsago Bruce Sterling on the US election: the net is great at tearing down, terrible at building https://www.textezurkunst.de/en/articles/bruce-sterling-us-election/
#10yrsago Canadian tech firms will have their pick of overseas talent thanks to Trump’s anti-immigrant policies https://web.archive.org/web/20161119143446/https://motherboard.vice.com/read/trump-election-science-tech
#10yrsago Keep hoping machine running: Woody Guthrie’s New Years resolutions, 1943 https://www.openculture.com/2026/01/woody-guthrie-creates-a-doodle-filled-list-of-33-new-years-resolutions-1943.html
#10yrsago Messy: a celebration of improvisation and disorder as the keys to creativity, play, and work https://memex.craphound.com/2016/11/14/messy-a-celebration-of-improvisation-and-disorder-as-the-keys-to-creativity-play-and-work/
#10yrsago The free-speech activist duty of journalists during the coming Trump years https://dangillmor.com/2016/11/13/trump-free-speech-and-why-journalists-must-be-activists/
#10yrsago John Oliver: how to resist the normalization of Trump https://www.youtube.com/watch?v=-rSDUsMwakI
#10yrsago Superstar academic economists charge $1000+/hr to defend disastrous corporate megamergers https://www.propublica.org/article/these-professors-make-more-than-thousand-bucks-hour-peddling-mega-mergers
#10yrsago Steve Bannon wants to deport Asian-born tech CEOs to preserve “civil society” https://www.theverge.com/2016/11/16/13653490/steve-bannon-trump-presidency-chief-strategist-breitbart-tech-visa
#10yrsago Iphones secretly send your call history to Apple’s cloud, even after you tell them not to https://web.archive.org/web/20161117135915/https://theintercept.com/2016/11/17/iphones-secretly-send-call-history-to-apple-security-firm-says/
#10yrsago Office Depot techs accused of faking malware infections to meet sales targets https://web.archive.org/web/20161117150900/https://consumerist.com/2016/11/16/office-depot-allegedly-diagnosing-computers-with-nonexistent-viruses-to-meet-sales-goals/
#5yrsago Live Nation is to blame for the Astroworld deaths https://pluralistic.net/2021/11/17/do-well-do-good-do-nothing/#crushing
#5yrsago Aspiration's comprehensively deceptive greenwashing https://pluralistic.net/2021/11/17/do-well-do-good-do-nothing/#greenwashing
#1yrago The games industry's self-induced traumatic brain injury https://pluralistic.net/2025/11/17/stop-killing-games-again/#object-transience

Oxford: Ministry of the Future, Nov 23
https://ministryforthefuture.co.uk/events.html
Sheffield: Reverse Centaur at Juno Books, Nov 25
https://www.outsavvy.com/event/40274/cory-doctorow-in-conversation
Virtual: Enshittification, AI, and the Future of Technology (UBC
Master of Educational Technology), Nov 28
https://met.ubc.ca/2026/09/met-speaker-series-cory-doctorow-enshittification-ai-and-the-future-of-technology/
Oxford: Bennett Oxford Symposium on Open Code in Science, Dec
9
https://www.bennett.ox.ac.uk/events/2026-bennett-institute-symposium/
Santa Barbara: UCSB Reads, Apr 29
https://www.library.ucsb.edu/events-exhibitions/ucsb-reads-2027-presents-author-cory-doctorow
Montreal: World Science Fiction Convention, Sep 2-6
https://montreal2027.ca/en
Life After AI (Brain Bar)
https://www.youtube.com/watch?v=IPPa43-n0vI
Terms of Service with Clare Duffy (CNN)
https://www.cnn.com/audio/podcasts/terms-of-service-with-clare-duffy/episodes/458ce968-af5d-11f0-b539-13ed2afe25f8
AI, Work, and Power (Software Engineering Daily)
AI, Work, and Power
https://softwareengineeringdaily.com/podcasts/cory-doctorow-on-ai-work-and-power/
AI, Corporate Power, and the Fight for Worker Control
(Plutopia)
https://plutopia.io/cory-doctorow-ai-corporate-power-and-the-fight-for-worker-control/
"Canny Valley": A limited edition collection of the collages I create for Pluralistic, self-published, September 2025 https://pluralistic.net/2025/09/04/illustrious/#chairman-bruce
"Enshittification: Why Everything Suddenly Got Worse and What to
Do About It," Farrar, Straus, Giroux, October 7 2025
https://us.macmillan.com/books/9780374619329/enshittification/
"Picks and Shovels": a sequel to "Red Team Blues," about the heroic era of the PC, Tor Books (US), Head of Zeus (UK), February 2025 (https://us.macmillan.com/books/9781250865908/picksandshovels).
"The Bezzle": a sequel to "Red Team Blues," about prison-tech and other grifts, Tor Books (US), Head of Zeus (UK), February 2024 (thebezzle.org).
"The Lost Cause:" a solarpunk novel of hope in the climate emergency, Tor Books (US), Head of Zeus (UK), November 2023 (http://lost-cause.org).
"The Internet Con": A nonfiction book about interoperability and Big Tech (Verso) September 2023 (http://seizethemeansofcomputation.org). Signed copies at Book Soup (https://www.booksoup.com/book/9781804291245).
"Red Team Blues": "A grabby, compulsive thriller that will leave you knowing more about how the world works than you did before." Tor Books http://redteamblues.com.
"Chokepoint Capitalism: How to Beat Big Tech, Tame Big Content, and Get Artists Paid, with Rebecca Giblin", on how to unrig the markets for creative labor, Beacon Press/Scribe 2022 https://chokepointcapitalism.com
"Unauthorized Bread": a middle-grades graphic novel adapted from my novella about refugees, toasters and DRM, FirstSecond, April 20, 2027
"Enshittification, Why Everything Suddenly Got Worse and What to Do About It" (the graphic novel), Firstsecond, 2027
"The Memex Method," Farrar, Straus, Giroux, 2027
Today's top sources:
Currently writing:
"The Post-American Internet," a sequel to "Enshittification," about the better world the rest of us get to have now that Trump has torched America. Fourth draft completed. Submitted to editor.
A Little Brother short story about DIY insulin PLANNING

This work – excluding any serialized fiction – is licensed under a Creative Commons Attribution 4.0 license. That means you can use it any way you like, including commercially, provided that you attribute it to me, Cory Doctorow, and include a link to pluralistic.net.
https://creativecommons.org/licenses/by/4.0/
Quotations and images are not included in this license; they are included either under a limitation or exception to copyright, or on the basis of a separate license. Please exercise caution.
Blog (no ads, tracking, or data-collection):
Newsletter (no ads, tracking, or data-collection):
https://pluralistic.net/plura-list
Mastodon (no ads, tracking, or data-collection):
Bluesky (no ads, possible tracking and data-collection):
https://bsky.app/profile/doctorow.pluralistic.net
Medium (no ads, paywalled):
Tumblr (mass-scale, unrestricted, third-party surveillance and advertising):
https://mostlysignssomeportents.tumblr.com/tagged/pluralistic
"When life gives you SARS, you make sarsaparilla" -Joey "Accordion Guy" DeVilla
READ CAREFULLY: By reading this, you agree, on behalf of your employer, to release me from all obligations and waivers arising from any and all NON-NEGOTIATED agreements, licenses, terms-of-service, shrinkwrap, clickwrap, browsewrap, confidentiality, non-disclosure, non-compete and acceptable use policies ("BOGUS AGREEMENTS") that I have entered into with your employer, its partners, licensors, agents and assigns, in perpetuity, without prejudice to my ongoing rights and privileges. You further represent that you have the authority to release me from any BOGUS AGREEMENTS on behalf of your employer.
ISSN: 3066-764X
Okay I may have buried the lede a bit, but Big
Grey is actually from a colony of cats. Down the street from me is
a colony of about fifteen cats, maybe more, including three kittens
and a pregnant long haired pastel calico. I didn’t know this
colony existed until last week, and since then I have not stopped
thinking about how I am going to save this colony. Because I
will.
Big Grey was only the first of many cats I plan on rescuing, and he was first because as you have seen, he was in the worst shape I’ve ever seen a cat be in. Even though kittens would usually take priority in these kinds of situations, the kittens were extremely hard to get to (hiding under a trailer in someone’s backyard), and Grey was just so much sadder looking.
So, with Grey in recovery and safe in my basement sulking, I headed back out to catch more cats. It’s only thanks to a woman in town (who does TNR missions regularly) lending me traps and support that we managed to catch three cats yesterday. I caught the two most friendly and sociable in the whole colony, the sweetest of the sweet ones, and she caught a very skittish calico.
Later that night, she came back by herself and caught the three kittens and the pregnant cat in one go. I applaud her, honestly. I’ve never seen someone make such quick work of catching kittens. It always takes me a bit longer, anyways.
With my two catches in tow, I took them both into the urgent care vet that I took Grey to, and thankfully they are in much better shape! Though that was a low bar to clear. Fleas and ear infections, a bit of upper respiratory infection, but otherwise okay. And FeLV, FIV, and heartworm negative. They’re a little less than a year old, and very bonded.
The lady got an appointment for the pregnant one to get taken care of and fixed, and has all of them in her possession right now, thank goodness.
So, I have three, she caught two plus the three kittens, and there’s still like a dozen left.
While TNR is obviously the most important step in dealing with any rampantly breeding colony, I want to do so much more than that for them. I want them healthy, happy, and to find homes for as many as I can after getting them vetted, vaccinated, and fixed. I want to adopt out every single one I possibly can, and I honestly think it’s doable!
I also want to be transparent about this entire process and the money, time, and commitment it takes to doing it. I’m not a pro or that experienced, but how do experienced people get experienced? They try. And with y’all as my witness, I’m going to try.
Now, let’s get into the real reason you’re here, cat photos of the colony cats. This is not all of them, just a few I managed to snap pics of.
First up is the pregnant one, who I lovingly call Fluffy Sugar:

Some of you might be able to tell why I call her that.

Look at that mlem!
When I first saw Fluffy Sugar, I couldn’t believe such a beautiful cat was on the streets. She looks like she belongs curled up in a comfy bed next to a fireplace, not wandering out of the bushes with goopy eyes in forty degree weather. I actually want her very badly. Thankfully this is the one in custody who is getting fixed up.
I call this one Fats:

CHONKY!
One of many calicos in the colony:

This one has very striking eyes:

This guy doesn’t look too bad, but he has some weirdly thin patches of fur that show pink skin underneath:

He’s very skittish and I scared him when I took this photo:

Oh boy! Another orange cat:

Oh my gosh, another orange cat!

I love this one, long haired cats are just so cute.
This one stared me down:

An even dingier looking grey and white one:

Here is one of the three kittens:

And finally, my two extremely sweet lovable ones that are in my custody currently:

This is Kevin.

And this is Tiffany.
Though I dubbed Fluffy Sugar and Fats with their names, the neighbor lady to the colony house is the one that gave Kevin and Tiffany their names. I plan to rename them or assume whoever takes them will rename them something more.. suited to their personalities.
THREE cats in this photo have already been caught! That is such good progress for only a couple days! At least, I think so.

I am running through litter and wet food like crazy, so I definitely placed some bulk orders of stuff. I am trying hard to stay on top of things, but dang there’s a lot of cats to herd (ha!).
I am racing against the clock with this cold weather. I just bought insulated outdoor shelters to put around the colony. Hopefully they offer respite while I continue my mission to help each and every one of them.
I wish I could’ve gotten a picture of the one I call Batman. If you saw him you’d understand why I call him that. Plus, I usually see him on the roof. But, like I said, there’s more than I’ve even photographed. Every time I think I’ve seen them all, another one comes out. So many to keep track of.
For anyone who has asked about microchips, every single cat I take to the vet gets scanned at the beginning of the appointment for one! So far, no chips.
So, what do you think? Am I being too optimistic about each one of these guys becoming a loving household cat? Which one looks like the one you’d claim if you could? Should I pick up extra shifts at the factory to afford this endeavor (because dang there are cheaper hobbies to pick up than this)?
Let me know in the comments, and have a great day!
-AMS
CodeSOD: Building a Line [The Daily WTF]
There's an unofficial category of posts here that I call "Somebody told us string builders were more efficient, so we always use string builders, regardless of whether or not that actually makes sense," or STUSBWMESWAUSBROWONTAMS, for short. Probably should workshop that name some.
In any case, Adam sends us a new entry for that collection:
Public Function ReadFromFile(ByVal filename As String) As String
Dim sb As StringBuilder = New StringBuilder()
Dim str As String = String.Empty
Using sr As StreamReader = File.OpenText(filename)
str = sr.ReadToEnd()
sb.Append(str & Constants.vbLf)
End Using
Return sb.ToString()
End Function
This function takes a filename, opens a file, reads the entire
contents of the file to a variable. It concatenates a line feed to
the end of the string it just read, then appends all of
that to a string builder. Finally, we return
sb.ToString(), taking the single string in the string
builder, appending nothing to it, and returning the result.
I'd almost, almost forgive the code if it was more like:
str = sr.ReadToEnd()
sb.Append(str)
sb.Append(Constants.vbLf)
You're not actually gaining much from this, but it follows the
broad pattern of "use a string builder" so that if you ever wanted
to change the structure of the output, you're already set up to
prepend/append new text in a scalable way. I'd argue that's
premature abstraction, though: a simple return sr.ReadToEnd()
& Constants.vbLf would do the current job.
The code that we have is a clear superstitious use of string builders. The string builder is used as a charm against poor performance, without understanding why one might use it, or how it might work; string concatenation means string builder, always and forever, "why" doesn't enter into it.
When AI-Generated Data Becomes Tomorrow’s Ground Truth [Radar]
Manufacturers qualify suppliers before trusting them with critical work. Before a supplier can provide parts for a regulated product such as a medical device, the manufacturer collects evidence: quality certifications, test reports, insurance documents, and regulatory approvals. Increasingly, an AI agent reads that evidence first. The agent reviews the documents and proposes a finding, and a business process decides whether the finding is good enough for the supplier to be accepted. Once a supplier is accepted, that decision is recorded in the manufacturer’s supplier-management system. From there, sourcing workflows, readiness dashboards, and program reports all rely on that record without repeating the review.
Here is how that process can go wrong. A supplier-review agent examines a new supplier’s documents and concludes that a mandatory quality certificate is valid. The qualification workflow accepts the finding, the supplier is recorded as compliant, and the procurement lead approves the supplier for an upcoming order. A few days later, a human reviewer notices that the certificate does not cover the part being sourced; the agent had misread the certificate’s scope. At 11:00am, the reviewer corrects the supplier record and sends the supplier back for review. At 2:00pm, the readiness dashboard still shows the supplier as cleared, and a program report still lists the supplier as compliant. The procurement lead’s sourcing decision remains in force, and nothing tells the procurement lead that the evidence behind it has changed.
A misread scope is only one way a certificate finding can fail. A certificate may be revoked after it was checked, expire before the order ships, apply to a different plant than the one making the part, or turn out to be forged. In each case, someone can correct the supplier record while the systems that already used the old finding keep acting on it.
No system in this example malfunctioned. Each one processed information that appeared valid under its local contract, yet the combined result was wrong. The manufacturer had corrected a value without correcting its influence. Part of this is a familiar problem: Enterprise systems have always struggled to keep reports, indexes, caches, and workflow state in line with the source record. Agents make the problem harder because they generate conclusions. A conclusion can be assembled from several sources, rewritten in reports, and retrieved later as if it were independent evidence. Reconciliation can make stored values agree. It cannot reveal that differently worded records come from the same conclusion, or find the decisions that already relied on that conclusion.
This problem is not limited to manufacturing. In our work across banking, telecommunications, and resources, it appears wherever an agent’s output becomes a record that other systems trust. A fraud classification is written into a case record. A risk assessment is summarized in a management report. An incident diagnosis becomes part of a knowledge base. In each of these cases, as in the supplier example, the conclusion loses some of its original context at every step it passes through and begins to influence decisions made later.
The conclusion can also travel back into model development. Accepted findings become labeled examples, evaluation sets, and fine-tuning data, where they are treated as ground truth for the next model. If an incorrect supplier finding survives correction in the operational systems, a future model may learn it. Whether the conclusion ends up in a dashboard, a report, or a training set, the hard problem is the same: finding every consequential decision that depends on a result that can change.
Look again at the supplier-review agent’s conclusion that the certificate is valid. When the agent produces that conclusion, it is a generated assertion: a claim made by a model, with no business authority until the qualification workflow accepts it for a specific use, such as approving the supplier for sourcing. The words “certificate valid” also change character as they move. In the agent’s response, they are visibly part of an AI-assisted assessment. In the supplier master record, the same words look like an established fact. The dashboard strips away more context: It shows the supplier as cleared, with no sign of which checks were incomplete or whether a review was pending. The program report compresses the finding into a sentence, and the search index splits that sentence into passages that can be retrieved on their own.
Along the way, enterprise systems tend to keep the value the agent produced and lose the conditions under which it was produced. A label saying that the finding was AI-generated may survive on the supplier record and disappear from a dashboard total, a data export, or a retrieval chunk. As that context falls away, the conclusion takes on the authority of whichever system is carrying it.
That is why two questions need to be kept separate: Who produced a result? And who is allowed to rely on it? An agent may be allowed to record a proposed finding without being allowed to establish a business fact. The same finding may be good enough to move a supplier up a review queue and not good enough to approve the supplier or release a payment. Where that line falls depends on what is at stake and which controls grant authority for that use. Once the qualification workflow accepts a finding, downstream systems usually treat it as settled and do not repeat the checks. That is efficient, and it creates an obligation: Those systems still need to know which decisions rely on the finding and under what conditions.
Acceptance also multiplies the finding. Once the supplier is recorded as compliant, the readiness dashboard shows the supplier as cleared, the sourcing workflow moves forward, and the program report repeats the approval. A later agent, when asked about the supplier, can retrieve the supplier record and the program report as two separate documents, each appearing to support the same conclusion. Across the supplier record, the program report, and the dashboard, one says the evidence was verified, another says the controls passed, and a third shows an approved outcome. What appears to be corroboration is propagation: several records repeating one finding. Because each system changes the wording or format, the duplication is easy to miss.
A stronger model will not reliably catch this duplication when the retrieval system presents the copies as unrelated documents. Reranking improves relevance, but every copy may be relevant. Telling the model to look for independent evidence cannot restore ancestry that was discarded before the documents reached it. Agent memory makes the problem worse. An agent that records its own finding and retrieves it a week later is citing itself, and nothing in the retrieved passage says so. In multi-agent workflows, one agent’s summary becomes another agent’s context, and a third agent’s supposedly independent check may read both.
Existing tools cover parts of this problem. W3C PROV models the entities, activities, and agents involved in producing data, establishing origin and responsibility.[1] OpenLineage standardizes lineage metadata around datasets, jobs, and runs.[2] Event sourcing records changes to application state as a sequence of events.[3] PROV is expressive enough to model the whole supplier example. The gap is in implementation. Lineage tooling often stops at dataset and job boundaries and rarely reaches the decision record or the retrieval layer that assembles an agent’s context. As usually deployed, none of these tools answers the question that matters after the certificate finding changes: Which decisions still depend on it? Decision lineage extends these mechanisms. It records the relationship between the source evidence, the generated assertion, the authority granted to that assertion, and the decisions that rely on it.
Data lineage tells us where an assertion traveled. Decision lineage tells us what the organization did because it believed the assertion.
In the supplier example, the chain runs from the certificate to the agent’s finding to the accepted supplier record to the procurement lead’s sourcing decision and on to the dashboard, report, and search index that reuse the finding. If the certificate turns out to be invalid, that chain lets the system find the sourcing decision and identify every report, workflow, and AI output that inherited the old finding, before any of them influence another decision.
The chain also marks where automated recovery and business accountability separate. Software can identify the affected artifacts, stop the withdrawn finding from appearing as current evidence, and open a review task for the person who owns the decision. That person decides whether the decision still stands, needs to be reversed, or needs to be communicated to customers or regulators. An implementation might remove stale search entries automatically while still requiring human approval to change a sourcing decision that has already been made.
The pattern starts where the agent’s output enters the system of record. The agent records its finding as a proposal, tied to the evidence it reviewed. A deterministic workflow, owned by the business, decides whether that proposal gains authority for a defined use. If a required check cannot run, the finding stays a proposal and is never silently promoted. Keeping proposals separate from accepted findings prevents accidental promotion, but it does not record what happens next, when the sourcing decision relies on the accepted finding. The decision needs a link back to that finding and to the version of the evidence behind it. This does not require a universal graph of everything the agent touched. For a high-consequence decision, it is enough that the finding’s influence can still be traced after the workflow has finished.
The dependency record that holds this link can be small. For the supplier example, it might look like this:
{
"assertion_id": "asr-7781",
"claim": "Mandatory certificate valid for supplier S-204",
"evidence_snapshot": "evd-2291@v3",
"authority": {
"granted_by": "qualification-workflow",
"scope": ["sourcing-approval"]
},
"dependent_decisions": ["sourcing-5520"],
"derived_artifacts": ["dashboard:readiness",
"report:program-q3",
"index:supplier-docs"],
"status": "accepted"
}
When the certificate finding is
withdrawn, the record’s status changes to withdrawn, and the
dependent_decisions and derived_artifacts
fields become the list of everything that needs to be
revisited.
The dependency record has to survive as the finding is copied downstream, because the same finding may come back through the program report or the search index. When a later agent retrieves both the supplier record and the program report, the retrieval layer should recognize that they share an origin and present them as two copies of one finding. If the finding has been withdrawn, the retrieval layer should filter or flag both copies before they reach the agent.
When a finding turns out to be wrong it is withdrawn, and the supplier goes back to review. The dependency record lets services find the decisions that relied on the finding, recompute dashboards, flag reports for regeneration, remove stale search results, and stop pending workflows. Decisions that have already taken effect go back to their owners, and nothing is reversed automatically. Cache invalidation, vector-index refresh, report regeneration, and workflow reversal are all parts of the same recovery job. A correction has traveled far enough only when the old finding no longer drives any current decision.
Not every AI output needs decision lineage. An answer that is low-stakes, never stored, never reused as evidence, and cheap to regenerate can live with ordinary logging. Decision lineage earns its cost once an AI-generated finding can affect an approval, a payment, safety, compliance, or later machine decisions. By the time an error in such a finding is discovered, the finding may already have changed what the organization did, so recovery has to finish within the time the business process can tolerate. That recovery work, finding and reconsidering the decisions affected when evidence changes, is what the pattern makes cheaper.
The pattern also does not require tracking every word an agent produces. The unit to track is the material assertion: a specific claim, such as “the certificate is valid,” that could change a decision if it were wrong. A long supplier assessment may contain only one or two material assertions. Recording dependencies for those claims is more useful than keeping a complete trace of everything the agent wrote, and it costs less in storage, privacy exposure, and operations.
Tracking ancestry also has to be precise enough to keep independent evidence independent. If two laboratories separately validate the same certificate, the system should not merge their results into a single source just because they agree. What matters is whether the observations share an origin, and similar wording proves nothing either way.
Recording dependencies proves little unless a correction actually travels through them, so the pattern needs a test. In a controlled environment, introduce an incorrect finding, let it reach a report and a search index, and then withdraw it. The test passes only if the affected decision can be found, and the stale copies stop appearing as evidence within the recovery time the process requires.
Three indicators show how well the test went. Decision coverage is the share of high-consequence decisions that can be traced back to a supporting finding. Time to impact is the time between withdrawing a finding and identifying the decisions it affected. Stale-evidence leakage counts the withdrawn copies still returned as current evidence. Targets depend on the process. A payment approval might need affected decisions identified within the hour, with zero leakage, while a review-queue priority may tolerate a day.
Now return to the supplier example and run it again with the pattern in place. When the supplier-review agent concludes that the certificate is valid, its finding is recorded as a proposal tied to the documents it reviewed. The qualification workflow checks the finding, grants it authority for the sourcing decision, and writes the dependency record shown earlier. The dashboard and program report still pick up the accepted finding, and a later agent that retrieves both sees them as two copies of one finding.
When the reviewer corrects the record at 11:00am, the finding is withdrawn and the supplier goes back to review. This time the correction travels. The dashboard recomputes, the program report is flagged for regeneration, stale entries drop out of the search index, and the procurement lead gets a task to review the sourcing decision. By 2:00pm, the dashboard shows the supplier as under review.
The procurement lead can now see that the certificate finding changed, which decision relied on it, and which reports and records carried it. The original mistake still happened. Its spread is now visible, and its consequences go back to someone who can act on them.
In the supplier example, the procurement lead never treated the model’s response as final. The finding became organizational truth because the supplier system accepted it, the workflow advanced, the report repeated it, and later systems inherited its authority.
Decision lineage does not prove that the original evidence is authentic, replace data-quality or entitlement controls, or make a model’s conclusions accurate. It addresses what happens after a finding exists: how its influence is recorded, found, and reconsidered across the decisions that depend on it. For the manufacturer, correcting the certificate record was only the first step. Recovery also meant finding the sourcing decision that relied on the finding and stopping stale copies from coming back as current evidence.
AI-generated data becomes ground truth the moment the next decision stops asking where it came from.
Formal Verification of the Signal Protocol Using AI [Schneier on Security]
This seems like a good thing:
Google Deepmind researchers used agentic AI to mathematically prove, or “formally verify,” a number of the Signal protocol’s key cryptographic guaranteesa landmark development for the widely used cryptography and AI itself.
Conducted as a sort of proof-of-concept project in just four weeks, the work is significant in two ways. It serves as further independent validation of the cryptography that protects massive quantities of the world’s communications on platforms like the Signal app, Google Messages, and WhatsApp. And it demonstrates Google DeepMind’s formal verification capabilities using a new AI framework called AlphaProof Code.
[…]
The DeepMind analysis did not find any new vulnerabilities in the portions of the Signal protocol it looked at, but when the researchers used AlphaProof Code on older versions of Signal that contain known and long-fixed vulnerabilities, it correctly identified them and showed that the protocol could not be formally verified. The researchers are releasing the specification and proof they developed for the Signal protocol analysis to aid other formal verification work.
Alternate link.
First, our researchers collaborated with a mix of models to translate Signal’s security goals into formal mathematical specifications, with human experts reviewing every one. From there, agents powered by Gemini Carbon did the proofs, generating over six million lines of Lean, a computer language that mathematically proves the accuracy of code.
Next, the agents audited the proof and highlighted areas that needed a second look by a human just one percent of the codebase, a massive time savings. Because Lean automatically checks the rest, our experts could focus their review where human judgment matters most.
Technical paper.
European Commission Plan to Give Frontex Trusted Flagger Status Is A Threat to Free Speech [Deeplinks]
EFF and 27 other human rights organizations
called on the European Commission today to
retract a dangerous proposal granting its border agency Frontex
power to request that national authorities issue takedown orders
for social media content and giving Frontext “trusted
flagger” status under the Digital Services Act (DSA), the EU
regulation governing online platforms and content moderation in the
region.
The extraordinarily improper proposal not only disregards the
provisions of the DSA but also places a mechanism of enforcement
overreach in the hands of a law enforcement agency that has
failed to safeguard people against serious
human rights violations at EU borders.
Under the
proposal, Frontex has the power to
“monitor publicly accessible social media content, detect
developments relevant to external border management, and support
action against illegal online content linked to border-security
risks.” Granting Frontex trusted flagger privileges on top of
its existing mandate risks creating a powerful tool for
over-enforcement, stifling the free expression of migrants, asylum
seekers, and other marginalized groups. We warned the Commission of
these risks in a
letter.
The DSA is supposed to make online platforms more accountable and
protect users’ fundamental rights, not give the EU power to
sic its border police on people for exercising their right to free
expression.
EFF and other rights organizations have for years
sounded alarms about potential abuse under
the DSA’s trusted flagger provision, which gives
“Digital Services Coordinators” the ability to award
entities—including law enforcement agencies—a
privileged channel to alert online platforms about illegal content.
We’ve taken the firm position that law enforcement cannot be
trusted to properly flag illegal content. In July, we
told the Commission that giving law
enforcement trusted flagger status could undermine fundamental
rights and said that police agencies like Frontex should not be
made trusted flaggers.
The EU proposal gives Frontex decision-making power over free
expression that is not envisaged under the DSA. First, content
removal orders can only be issued by relevant national authorities.
The DSA does not foresee a role for entities like Frontex to
request such orders. Second,
trusted flaggers notify platforms of suspected illegal
content—platforms must prioritize these notices and they have
sole responsibility to decide to remove content. It’s not
flaggers’ role to request removal orders from national
authorities. Combining these powers blur enforcement and flagging
functions, which the Commission’s own
draft guidelines on trusted flaggers
explicitly caution against.
“The risk of Frontex utilizing its power as both a Trusted
Flagger and authority that can demand removal orders, to surveil
user-generated speech, and over-flag content under the guise
of ‘border security risk’ is clear. This will
likely result in platforms over-censoring content and chilling the
speech of already marginalized groups, particularly those from
migrant and asylum-seeking communities,” the letter
says.
We urge the Commission to rescind the proposal. It undermines the
DSA, threatens fundamental rights of citizens and non-citizens, and
is enforcement overreach that does not align with international
human rights standards.
Selling to friends [Seth's Blog]
There are two versions, very different:
FAVOR: This is what multi-level marketing preys on. You ask a family member or a friend to buy something, not because they need it, but because you do.
This doesn’t always end well. Someone might want to further their relationship with you by doing you this favor, but if the unspoken promise is that the item or service is worthwhile, the disappointment that ensues hurts everyone. Real estate brokers or middlemen in a bind often seek to build friendly relationships at the club or community meetings, but then try to leverage this friendship into a significant sale without doing the hard work of actually being the best choice.
TRUST: This is the sort of sale that happens when you begin with the benefit of the doubt but actually deliver a great outcome. You’ll know this is the case when the person who trusted you ends up testifying on your behalf to others.
“No pressure” is something that’s showing up more and more in the pitches I’m seeing. Of course, there’s no pressure! Just saying it implies that you wish there were.
If you’re asking for a favor, you’re not serving and you’re not selling. You’re trading.
And if you’re asking for trust, be prepared to honor the obligation it creates.
Sex Drive Differences by Tessa Luicart [Oh Joy Sex Toy]
Better Board Games in Bars – DORK TOWER 17.11.26 [Dork Tower]
DORK TOWER strips are now available as signed, high-quality prints, from just $25! CLICK HERE to find out more!
HEY! Want to help keep DORK TOWER going? Then consider joining the DORK TOWER Patreon and ENLIST IN THE ARMY OF DORKNESS TODAY!
How can I ask a second program to show a dialog box as if it were shown by my first program? [The Old New Thing]
Suppose you have two programs, one a GUI program and another a program that runs in the background. The GUI program asks the background program to do some work, and then the background program realizes that it needs to display a dialog box. How do you get that dialog box to appear as if it were shown by the GUI program?
If you have the background program simply try to show a dialog box with no owner, then that dialog box has no relationship to the GUI program’s main window, which means that there is no requirement that the dialog box appear in front of the GUI program’s main window. If the GUI program didn’t disable its main window, then you have the situation where both windows (the GUI program main window and the dialog box) can be clicked on and interacted with. But if the GUI program did disable its main window, the fact that the main window can end up in front of the dialog box from the background program means that the user can’t see the dialog box that is preventing them from making progress.
The GUI program should include its window handle as part of the call into the background program, so that the background program can use that window handle as the owner for the dialog box. If the dialog box is modal, this also disables the GUI program’s window, and if the user tries to click on the GUI program’s window, the window manager will instead put focus on the dialog box (and blink its title bar).
Note that a cross-thread owner/owned relationship implicitly attaches the two threads’ input queues, which means that both threads need to to remain responsive to window messages in order for things to work properly until the attachment is implicitly broken when the dialog box is destroyed.
That’s the ideal situation, but maybe you aren’t in the ideal situation.
For example, maybe the GUI program is written in a framework that doesn’t give you access to the window handle.
You could have the GUI program call
AllowSetForegroundWindow() with the
process ID of the background program, so that the background
program can call SetForegroundWindow() on
its dialog box and try to bring it to foreground.
Now, if the GUI program didn’t have foreground, then
it can’t give away a permission that it doesn’t itself
possess, and the call to
SetForegroundWindow will fail.
There’s not much more you can do at this point. The system doesn’t want to let random programs steal focus, and since there was no coordination with the window that has focus, you look like a random program as far as the system is concerned.
But really, the solution is to fix the design.
You’ve already separated the problem into a GUI process and a background process, so honor that separation: Don’t make the background process try to do UI. UI is the job of the GUI process.
If the background process wants to display UI, it can ask the GUI process to do it, and then the GUI process can send back the dialog box result. One way to do this would be to have the background process return an error code like “UI required” and information about what UI it needs. The GUI process can then display the UI, gather the answer, and then call the background process again. Another way to do it is to have the background process call back into the GUI process when it needs UI, and the GUI process displays the UI, gathers the answer, and returns it to the background process. There are pros and cons to both of these designs, so you can choose the one that works best for you.
The post How can I ask a second program to show a dialog box as if it were shown by my first program? appeared first on The Old New Thing.

and there was much rejoicing
The Big Idea: Will Ludwigsen [Whatever]

Elder gods and geopolitical quagmires: Are these two great tastes that go great together? Will Ludwigsen mashes up both in A Scout is Loyal — and as this Big Idea shows, the result is intriguing.
WILL LUDWIGSEN:
If you’re wondering (as we all do) how the Vietnam War could possibly have been worse with H.P. Lovecraft’s Deep Ones lurking in the rivers and sea, I’ve written just the book for you.
A Scout is Loyal takes place five years after the events of A Scout is Brave in which Bud Castillo and his Deep One friend Aubrey Marsh thwart a conspiracy to drill into Devil’s Reef in 1963. I wrapped up that Lovecraftian Catcher in the Rye with Bud wistfully gazing out to sea for his lost friend, both of us believing the story was over.
But people had questions, chief among them how discovering a colony of monstrous beings interbreeding with humanity would influence the life of pleasant conformity we’re all expected to embrace. How do you go off to college or get a job without squinting at every bug-eyed pedestrian you pass? Does knowing about a vast cosmic conspiracy make you a Nixon voter or a Humphrey man? Why save for retirement if trans-dimensional beings beyond time can put your brain in a jar?
Lovecraft’s protagonists rarely contend with those long-term implications. They tend to simply faint or gibber when they discover the horrible truth of existence, which appears to be—checking my notes—that humanity’s struggles make no difference to the monstrous beings who truly command the universe.
Which hardly seems a revelation, much less worth going insane over.
At the end of A Scout is Brave, Bud is thirteen years old and now fully aware that the Scout Handbook contains no practical advice for a struggle against overwhelming evil. The best he figures is that we don’t win a single dramatic battle but tiny skirmishes every day, opening literal and figurative doors for others and picking up after ourselves and nudging circumstances toward the good.
My question for the sequel became, “What the hell does a Boy Scout like that do in Vietnam?”
A lunatic—say, me—could make a case that the Vietnam War may well have been our most Boy Scout-y conflict, driven by total arrogant confidence that we were rescuing “helpless” people to impose our values on them. We rationalized our baser motives with the spangled bunting of altruism because we were the Good Guys walking little old Vietnamese ladies across the street to freedom.
It also had lots of hiking and camping.
What Bud discovers when he gets to Vietnam in A Scout is Loyal isn’t a lack of idealism but a glut of it. He’s surrounded by people who are proud of the extremes they’ll take to prove their vision for reality is the right one. How can you talk someone off a ledge when they think they’re virtuous for being there?
That’s where Lovecraft, scouting, and Vietnam converge: the myopia of utter conviction. Lovecraft’s (human) bad guys were true believers with the advantage of certainty, and his good guys were skeptics with the “disadvantage” of an open mind. Those strike me as the real-world bad guys and good guys in Vietnam, too, confident zealots versus the few still asking questions of themselves.
In A Scout is Loyal, Bud’s worst errors of perception and action occur when he feels the most certain, the most electrified with righteous purpose. His struggle is to let new information change his mind, and in that way, he has a lot in common with Nixon and McNamara and Kissinger, and honestly the rest of us.
Sometimes the smoothest road to being wrong is being sure.
I didn’t write A Scout is Loyal as a “message” book—every great error of my life came from thinking I knew an absolute truth—but as an experiential one. I wondered how someone like Bud (or like me) would react to that impossible situation where being right didn’t seem to matter as much as believing you were. I ran the scenario and reported what happened.
The closest my book gets to a “Big Idea” is that Big Ideas are liars. They’re the smoothed edges and blunted corners of reality, the models and rules of thumb that make us miss the details that hurt other people.
Lovecraft’s big idea was that we don’t matter in a terrifying cosmos. Mine, if these books have one, is that we only have to matter to each other.
A Scout is Loyal: Amazon|Barnes & Noble|Bookshop|Lethe Press
Author socials: Website|Bluesky
Read an excerpt.
EFF’s AI Cybersecurity Policy Framework [Deeplinks]
The news has been filled with stories recently of AI breaching the security of websites. And while it may feel like a new problem because of AI’s involvement, it turns out that there are longstanding existing cybersecurity safety best practices that these companies—some of the largest tech companies in the world—could and should have taken to prevent these breaches.
Recent cybersecurity incidents have shown that some of the world’s largest tech companies have failed to take basic security precautions when testing frontier AI systems on internet-connected systems. Unfortunately, these failures resulted in breaches of numerous third-party websites, including an AI research-sharing platform called Hugging Face and the Australian healthcare system’s website. Even worse, AI developers failed to detect most of the incidents until long after they occurred due to inadequate monitoring of the AI systems during testing. Had the companies abided by basic, common sense security protocols, these incidents likely would not have occurred.
While the White House and some leaders of major AI companies have claimed that no action is necessary, understandably, lawmakers at all levels and of both parties are proposing legislation to create new, additional safety protocols. These incidents may warrant legislative action. However, the good news is that post-incident reports indicate new protocols are largely unnecessary. Following existing best practices would have been enough to prevent the OpenAI-Hugging Face incident and others like it. In other words, responsible AI developers can take immediate action to protect the public by implementing well-established security precautions as they develop and test their systems.
Lawmakers should start by referencing existing legal protections, including claims like negligence, gross negligence, trespass to chattels, Section 1201 of the Digital Millennium Copyright Act (DMCA), and computer trespass statutes like the Consumer Fraud and Abuse Act (CFAA) and analogous state law provisions, such as Section 502 of the California Penal Code.
Policymakers can help protect the public by requiring AI developers to follow established security protocols—and creating legal liability for failing to do so. These policies would protect the public from irresponsible actions by AI developers without impeding innovation. To the extent that gaps in existing laws warrant new legislation, EFF recommends the following policy framework:
The public shouldn’t have to worry about the risks of reckless AI development—or give up the benefits of AI just to prevent irresponsible developers from causing harm. By adopting policies that address demonstrated risks, lawmakers can provide meaningful public protection without hampering the development of useful tools.
1NIST, the NSA, and CISA have recently issued a set of voluntary practices for managing security incidents during the training and evaluation of AI agents. Those practices may inform but do not substitute for the regulatory standards that should be developed according to the public, participatory process outlined here.
Donate Equity to Support Digital Rights: Stocks, DAFs, and Giving [Deeplinks]
Do the holidays have you thinking about how you can support your favorite nonprofit?
For 35 years, the Electronic Frontier Foundation has been advancing our digital rights, including defending security researchers, encrypting the web, and fighting illegal surveillance. Donating equity to EFF can help support this important work.
Perhaps your family has taken advantage of the new tax law around giving by creating a Donor-Advised Fund.
Perhaps your employer has gone public and you now own stock.
Perhaps you’ve seen some of EFF’s recent successes and thought, Man, imagine what they could do with more.
A gift of equity can help your contribution go farther and offer tax savings. When you donate appreciated stock, you avoid paying capital gains tax on any increase in its value. You also receive a charitable income tax deduction for the fair market value of appreciated stock on the date it is transferred. Also, more and more companies are offering gift-matching programs that can double your impact at no additional cost.
If you have owned the stock for less than a year, your gift will not qualify for all of these potential tax advantages. And gifts of appreciated stock are fully deductible—up to a maximum of 30% of your adjusted gross income. Please check with your accountant or tax advisor regarding your particular tax status.
We have helpful information here to facilitate the transfer of securities. Please email us if you have any questions. And let us know in advance if you are transferring securities. We’ll need to know the amount and type of shares that you will be donating in order to provide a tax receipt.
As a 501(c)(3) organization, EFF can also receive
distributions through your
Donor-Advised Fund (DAF), including one-time gifts
or recurring donations. Simply inform your DAF provider you would
like to make a gift to:
Electronic
Frontier Foundation
(EIN
04-3091431)
815 Eddy
Street
San Francisco, CA
94109
Please note
that many DAF providers do not provide the donor’s name to
the recipient organization. If you would like to be recognized for
your gift, let us
know the amount of the gift and the fund name. And
due to IRS regulations, we may not be able to provide a thank you
gift in line with your giving level. The DAF provider is
responsible for your tax receipt.
The rules that govern technology shape our freedom. Help us write those rules today!
Finally, a truly premium Linux laptop: Star Labs’ StarFighter Ultra [OSnews]
Many popular Linux laptops are not designed from the ground-up for Linux. Often, they are machines designed and assembled by companies like Clevo, with parts and options picked by the Linux OEM to optimise them for Linux to make sure the hardware is optimally compatible. While there’s nothing wrong with this approach – there are countless great Linux laptops available that are made this way – there’s also something to be said for starting with a blank slate, and designing, developing, building, and assembling a Linux laptop entirely from scratch.
One such laptop is Star Labs’
brand new StarFighter, which I’ve been using and testing
over the last little while since it was launched. The StarFighter
is an entirely custom powerhouse of a laptop, designed exclusively
for Linux, both inside and out. Let’s talk about what
it’s like to use the StarFighter, and if it’s worth
considering when looking for a new laptop.
The Starfighter comes in three flavours: Standard, Ultra, and AMD. I opted for the Ultra model, which comes with an Intel Core Ultra 9 285H, an Intel Arc 140T integrated GPU, 64GB of LPDDR5X RAM, and a 16″ 3840×2400 120Hz matte display. The standard model steps these specs down to an Intel Core Ultra 5 125H, 32GB of LPDDR5X RAM, and a 16″ 2560×1600 165Hz display, while the AMD model maintains the specifications of the Ultra, but with an AMD Ryzen 7 8845HS processor paired with a Radeon 780M integrated GPU. All three models share the same Intel AX210 Wi-Fi 6E chip, soldered RAM, and port configuration: 2 USB-C ports (Thunderbolt 4 on the Intel models), 3 USB-A ports, an HDMI 2.0 port, a microSD reader, a combined audio jack, and two PCIe Gen 4 NVMe slots on the motherboard.
Support OSNews
OSNews is
ad-free, fully independent, not owned by any media conglomerate; we
answer to nobody.
We need your donations and support to survive.
➡️ Donate through Ko-Fi ➡️ Donate through SEPA transfer* ➡️ Become a Patreon ➡️ Buy merch from our store
*Name: Thom Holwerda – IBAN: SE08 8000 0820 1684 4657 8414 – BIC: SWEDSESS
All three models run coreboot firmware, and come with a hardware kill switch for the wireless radios. Another really interesting security and privacy feature is how the Starfighter handles its webcam. Instead of being integrated into the display bezel, the webcam is a separate module that snaps onto the display lid magnetically, connecting through a few pogo pins (which form a USB 2.0 port, which I’m sure intrepid hardware hackers could do fun stuff with). When not in use, the webcam module is stored in its own little metal tray that slides out of the side of the laptop, securing itself in place magnetically. Neat.
The webcam quality itself is decidedly average. I personally don’t ever use a webcam, but if you do, don’t expect miracles. It does its job, no more, no less.
The StarFighter has a custom chassis made out of magnesium, with the only plastic part of the casing being the display inner hinge cover where I assume the antennas are integrated. It’s an incredibly sturdy device, with very little flex in the display cover, and zero flex in the keyboard deck. Thanks to the properties of magnesium, it’s quite lightweight at a mere 1.6kg. The bottom cover is easily removable, but the two screws in the middle of that cover are ever so slightly longer than all the other screws – ask me how I know.
Star Labs opted for an understated, unobtrusive design. There’s no weird flourishes, no garish RGB lighting, no childish font on the keyboard – it’s all business, and I really like that. The dark finish feels incredibly nice, and despite the colour doesn’t seem to catch too many fingerprints. The speaker grills next to the keyboard look nice too, as does the keyboard itself – I especially appreciate that the the various modifier and non-character keys use text labels instead of symbols. Of course, since this is a Linux laptop, the super key is properly labelled. No Windows logo here, but no silly penguin either. The keyboard is backlit, of course, with several light levels, with a keyboard backlight timeout adjustable in coreboot.
The feel of the keyboard could use some work, however, at least for me. In particular, the key stability feels a bit off to me, meaning that unless you strike a key right in the middle, it might not register properly, as the keys wobble more than I would expect. A workaround, of sorts, is to strike the keys a bit harder than you normally would, but I’ve found this to be more difficult to adapt to than I initially expected. That being said, if you already have a more solid strike, it’s possible you won’t notice anything wrong with the keyboard at all.
The trackpad, though, is basically perfect. Star Labs pulled out all the stops here, and went for a large haptic trackpad that feels absolutely incredible. I greatly prefer haptic trackpads, and have been puzzled for years now why Linux laptop OEMs continue to opt for wobbly diving board-style trackpads instead. It has a glass surface which hits the perfect middle-ground between smooth and textured, and it never seems to pick up any smudges or grease. Several of the parameters of the haptic trackpad can be configured in coreboot and supposedly from within Linux itself, but I haven’t figured that part out yet as the patches for it were only accepted very recently.
It is the perfect trackpad. Zero complaints. Every single click, every single gesture, every single swoosh feels perfect. I don’t like being this ecstatic about something – there’s usually flaws in everything – but it’s really just that good. While testing the StarFighter, I used some other laptops with the old diving board design, and they’re all ruined for me now.
I’m usually a fan of smaller laptops, with 14″ being my upper bound. However, laptops have gotten so light, and bezels so thin, that the 16″ of today is the 14″ of several years ago – not exactly, but you get my point. I definitely had to get used to this larger laptop, but now that I have acclimatised, having 3840×2400 pixels spread out across a 16″ canvas is honestly kind of amazing. I guess I’m finally getting older, but being able to move the laptop a but further away and still see everything clearly is quite nice.
It’s incredibly bright, the colours look great, and the variable refresh rate, with a maximum of 120Hz, makes sure everything is smooth and stutter-free. I’m also quite happy matte displays are making a comeback, as they drastically reduce glare and annoying reflections. The matte finish also ensures that smudges and similar issues aren’t quite as noticeable as they are on glossy displays.
The speakers I’m not quite as enthusiastic about. The large speaker grills trick you into thinking you’re getting some serious (for a laptop) speaker power, but upon closer inspection, they’re just a trick; the actual speakers only take up a small portion of the bottom of the grills. This is an odd decision, because when you open up the laptop and look inside, there seems to be enough free space available to make the speakers much larger. As a result, they sound merely “okay”, while at this price point – we’ll get to that – they really ought to produce a much more full, less tinny sound than they do. EasyEffects can definitely improve things, but software tricks can’t beat physics and can only take you so far.
It shouldn’t come as a surprise that the StarFighter runs Linux absolutely perfectly. Everything is fully supported, and with this much computing power you’re never going to be waiting for anything or experience any slowdown during normal, everyday use. There’s enough headroom for more serious work here too, of course, although I’m sure some of you would’ve preferred a beefier GPU option. A gaming monster this is not, but Star Labs doesn’t claim it to be, either. The soldered RAM is definitely a downside for some, but with 64GB of RAM that can be allocated between the CPU and GPU, it’s unlikely you’re going to be running out any time soon. If you know you need more, this machine is simply not for you.
The StarFighter has an 80Wh battery, and battery life under Linux aligns with about what I expected: while watching YouTube with some light use thrown in, I never managed to drain the battery and I lost track of the hours – battery life estimates are very hard to convey, and your use case is going to differ far too much from mine for my experiences to be useful. All I can say is that I was never surprised about the charge levels, with very little drain when in sleep mode with the power profile in coreboot set to balanced.
The cooling system works wonders too, and I never had the laptop feel too warm, which is impressive considering the power this thing rocks. Another big win for the StarFighter is just how quiet and pleasant the fans are. It uses two fans, but they are each of a different size and blade shape, so I assume the firmware does some smart stuff with when to spin which fan for optimal cooling and lowest sound levels. Most of the time, the fans didn’t even spin up at all, but even when they do, the sound they make is not annoying at all, easily fading into the background.
As mentioned, all three StarFighter
models use coreboot, which is open source and freely available for
anyone to alter and change. So far, Star Labs has pushed out
monthly
updates since I received mine in September, which are installed
using either KDE’s Discover, GNOME’s Firmware, or the
command-line using fwupdmgr. Star Labs’
implementation of coreboot has an expansive settings menu, giving
you control over all kinds of power management features, security
options, keyboard and trackpad configuration, and much more. By
default, the StarFighter disables secure boot, the Intel IME, and
the processor’s NPU, but you’re free to make changes if
you wish, of course.
And in case you were wondering, yes, it supports Windows 11 too, with a few small caveats I ran into (I took one for the team… Again). Star Labs offers all the required drivers for download, and you’ll have to use them since neither Windows Update nor Intel’s Driver & Support Assistant pick up all the hardware. Do note that the included driver install batch files need to be run with admin privileges, or they’ll error out. Make sure your firmware is up-to-date (the keyboard won’t work with older versions of the firmware), and you’ll also need to set the audio option in coreboot to Legacy (otherwise the audio device won’t be recognised by Windows).
A few additional notes about using
Windows are in order. The StarFighter does not seem to support
Windows 11’s Connected Standby mode (S0ix), and in regular
sleep Windows 11 drains the battery within less than a day. Windows
11 also fails to transfer from regular sleep to hibernate by
itself, so I definitely advise you to set the laptop to hibernate
when closing the lid. These are 100% Windows issues, though, as
Linux works perfectly with sleep states and does not drain the
battery like Windows does at all. This is a laptop designed for
Linux – Windows support is a bonus.
The StarFighter isn’t just the best Linux laptop I’ve ever used – it’s the best laptop, period. The whole machine just feels more sturdier, nicer, more solid, and better put together than any other laptop I’ve ever tried. It turns out that while buying off-the-shelf, premade designs from Clevo and similar companies can lead to some pretty good devices, they always seem to hit a ceiling which they just can’t quite get through, always making them just a little less polished than, say, a Dell XPS or MacBook Pro. If you want to shatter through that ceiling, you apparently need to go full-custom and ground-up, like Star Labs have done here.
That being said, I hope that for the next revision, they improve the key stability on the keyboard, and somehow manage to shift things around a bit on the inside to allow for larger speaker modules, preferably with some software tuning to try and get them to sound as good as high-end laptops from companies like Apple or Dell. They keyboard and speakers aren’t bad, but merely average – and at this price point, you should be aiming higher.
It should come as no surprise that a fully custom, in-house laptop made by a small company in what are probably quite low volumes compared to the big brands, with this much RAM and storage in 2026, is not going to be cheap. The StarFighter Ultra I have here costs €3606, and while that’s a lot of money, it does net you the best laptop I’ve ever used, unapologetically designed for coreboot and Linux, by a company who clearly cares. If you ever wondered what a truly premium Linux laptop looked like, now you know.
If you want the best Linux laptop, this is it.
Now that I've gotten used to the Markdown web, I find sites that make it impossible to use because they do crazy things when you're just trying to figure out how to log in, and instead of staying there to figure it out you switch over to your blog to tell the tale.
I believe Gabriel has preloaded the two-hundred and twelve meg corpus of Grand Theft Auto VI, and is now waiting for it to hatch like some kind of Hatchimal. When it does, he will be ready - for whatever the future brings.
Amazon Ring’s New Indoor Surveillance Drone Is Not Compatible with Privacy [Deeplinks]
Amazon Ring has finally announced their long-dreaded indoor drone, a small flying surveillance device connected to their security suite of products that can fly around your house filming and recording things. The device is supposedly designed to fly preset paths across your home and will also activate if a sensor or alarm has been triggered.
Customers should think twice about purchasing these devices for a number of reasons. These devices are problematic in many of the ways we’ve said Ring’s stationary home surveillance products are a problem, plus some new ways. At a very basic level, they are essentially a window into your house that can be accessed by anyone with access to your account—which has historically included bad actors looking to embarrass or harass Ring users and employees of the company.
What’s worse, Ring has supercharged the units with its ‘AI Pilot’ to map routes, model the interior of the home, and control movement. This means not only is the footage being sent to corporate servers, but the company is also making inferences about your home to carry out tasks. How much home usage data this is based on, and if it can be used to infer when certain household activities are happening, are both open questions. And presumably, to maintain the preset routes, inferred data about your home will still be held by Ring even after any stored video footage is deleted.
The risk to your privacy is only compounded once you consider Ring’s renewed partnership with police through the massive surveillance and taser vendor, Axon. Through this partnership, police have the ability to request camera footage from Ring users with just a few clicks on Axon’s platforms. This includes its Fusus platform, an interactive surveillance feed and map police use to manage all the surveillance devices they have access to, like automated license plate readers. It’s unclear exactly what devices police can request footage from, but if this request feature is extended to Ring’s drones, police could easily send requests for footage from inside your house. Sharing is voluntary, but once footage is submitted, it cannot be retracted. Worse still, if your footage is not sitting on Amazon’s servers fully encrypted—and there’s reason to believe their privacy options are not the strongest—police could serve a warrant straight to the company, instead of to you, to get footage from your devices.
New problems and questions arise because the camera can fly. For instance: if police serve a warrant on Amazon, can they only get the footage from the camera, or could they also get access to control the drone? If the latter, we could be looking at the first full home search in history where police serve a warrant on a third-party tech company and not the resident.
The CEO of Ring has pitched this product’s safety benefits in several ways, including by saying: “If someone is going around your house at night, and your motion detector goes off on your Ring doorbell, imagine if you see spotlights and something flying across the window...You’re probably not going to go into that house.” But partially justifying a $250 piece of technology that invades your privacy on what an imagined burglar might do doesn’t sound like a foundation for safety—it sounds like security theater and marketing.
It isn’t new for Ring to prey on the fears and paranoia of people and their properties. This is the latest iteration of that: a patrolling drone or rover wouldn't have been possible even in the world's top museums and art galleries a generation ago. Moving this technology into the household as a common consumer product is another example of companies attempting to lower the bar on surveillance being normalized.
With previous Ring products, consumers have had to consider what cameras and high-powered microphones can learn about their home usage from the front door. Autonomous flying drones and rovers inside the home add a whole new layer. What can these devices learn about you and your family? And do you really trust that data sitting on a server somewhere? Consumers should consider these risks before subjecting their guests and households to the latest creepy surveillance tool.
The Monday Morning Agent: Are Kickers Too Good Now? [Radar]
“Kickers are too good now” sounds plausible when long field goals keep making the highlights. But in the November 9 episode of The Monday Morning Agent, our AI analyst found that long kicks went through at roughly the same rate across the seasons on file. Coaches were attempting them more often. We gave the agent written visualization standards so its charts would show both success rates and attempts per game, with the context readers need to judge the claim.
We started with two charts of league-wide field goal success rates. One began in 2024, with a vertical axis starting around 84%. The line climbed to 85.6%, and the improvement looked dramatic.
The other included every season from 2021 onward, started the vertical axis at zero, and showed the attempt count beneath each point. Success rates stayed around 84% to 86%. The recent rise looked much smaller in that context.
Changing the starting year and axis made the recent improvement look larger. Before your agent draws a trend, decide which choices it can make. Otherwise, it can produce a persuasive picture without giving readers the context to assess it.
The dictionary from episode two still applies. During a rehearsal, that earlier agent refused the kicking claim because its dictionary could describe a rush but couldn’t describe a kick. We expanded what it could define while keeping the requirement to use a saved definition.
This time, the play descriptions named field goals and included distances. We still had to decide where “long” starts. A recognizable play name doesn’t settle how to group it for analysis.
We examined distance bands separately. Kickers made roughly 95% of attempts under 40 yards. Success rates hovered around 80% for attempts from 40 to 49 yards and around 70% for those from 50 to 59 yards. Combining them into one rate can hide the differences the question asks about.
We introduced eight rules. Every trend includes all seasons on file, and axes start at zero. Each point shows its underlying count. Yellow identifies the subject of the claim, blue identifies the comparison, and gray marks the current season.
The chart title asks a question rather than announcing a conclusion. A source line gives the exact command that produced the data, so readers can rerun it. The chart shows only values the tool printed, without added trend lines or numbers typed by hand. Every chart uses the same layout, with success rates above attempts per game.
Writing these standards down gives the agent consistent instructions and gives readers a familiar way to compare results across episodes. Choose standards that fit your analysis, then specify how you’ll check each one.
A written standard needs a way to enforce it. We added a renderer, the program that turns the agent’s chart specification into a picture. It checks the chart specification against the rules before drawing the chart and refuses specifications that break them.
We deliberately requested a trend beginning in 2023. The renderer refused because the first season on file was 2021. Its response identified the rule instead of producing the shortened chart.
Give your agent a request that violates a standard and inspect the response. That check shows whether the restriction works when the agent tries to produce an output.
The longest kicks need particular care. The episode’s current-season sample contained only nine attempts in the group of kicks from 60 yards or farther. The next kick could noticeably change that rate. Displaying counts beside percentages helps readers distinguish a small sample from hundreds of attempts.
Showing success rates alongside attempts per game helped explain the ruling. In these plays, long kicks weren’t consistently becoming more successful; coaches were trying them more often. More attempts give fans more opportunities to see a long field goal go through.
We also corrected episode two’s results after finding an error in the tool. Our defined substitute for the tush push had a conversion advantage of 10.1 percentage points overall and 9.7 without Philadelphia, replacing the previously reported 8.3 and 7.8. Chart standards help readers inspect results, but we still have to check the calculations behind them.
On November 16, we’ll add a second agent to independently audit an audience-selected claim. We’ll examine where the agents disagree and how they investigate the evidence. The agent doing the analysis shouldn’t also grade its own work.
O’Reilly members can sign up on the O’Reilly learning platform to join us live on November 23, 8:00am–8:45am PT / 11:00am–11:45am ET. Everyone can follow along on Radar every other Monday, with a brief pause for the holidays. Watch episode three above, and we’ll build on it in the next session.
When AI Can Code, What Is Left for Programmers to Do? [Radar]
AI is in such widespread use for programming that project maintainers (particularly for free and open source software) are complaining about the burden of reviewing mounds of low-quality code. In fact, AI can help with every stage of code development: writing the specification, coding, uncovering bugs, and repairing the code. This article describes human-AI collaboration at specification and code repair stages, and lays out the skills that humans need to accomplish those tasks in the current generation of AI. We won’t cover coding and bug finding because they are widely discussed elsewhere.
We don’t want developers hand-writing specs. We want them in a room, or on a call, talking with the product manager (PM) and the customer.
Humans reach a limit when writing. We skip the boring cases. We get tired by requirement 40. We use “customer” on page 1 and “client” on page 6 of the spec. We write down what we remember and forget what we assumed. AI has the patience and diligence we lack.
It’s still up to human developers to write guardrails or constraints into the spec: statements to ensure that nothing wildly wrong makes it into code. Each guardrail should be one sentence that says MUST or MUST NOT, with a proof beside it: a test, a check, or a named person who reviews it. A guardrail with no proof is a wish. Write the guardrails first, because the PM won’t think of most of them. What must never happen? Who must never see this? What should the agent never touch?
With guardrails in place, capture the conversation and let the machine do the writing. Two AI tools have shown themselves particularly useful to analyze requirements: The Plaud Note recorder attaches to the back of your phone and records in-person conversations and phone calls; the wearable NotePin records in-person conversations, not phone calls. Granola runs on your laptop or phone, uses your computer’s audio, and analyzes what it captures. We find these products to be a leap above common AI tools for summarizing conversations, when it comes to specification development.
Plaud and Granola (if you prompt them to do so) can notice what’s missing and tell you the gaps in the requirements. They ask, What happens when this field is empty? What if two people do this at once? Who is allowed to see it? over and over, for every requirement, and check each noun in the requirements against an ontology created by the programmer (often with the help of AI).
The developer, the PM, and the customer read the output from the AI, fix what’s wrong, answer what’s missing, and go through the process again.
The spec that comes out of that loop tends to be more complete and more consistent than what the same people write alone. That’s Shahid’s own experience, not a study, but it matches reports from some other people at the leading edge of the use of AI for software development. Mark Pike, a product lawyer at Anthropic, builds working tools for his legal team without writing code: “I just typed a normal sentence, describing what I wanted. And it worked.” StrongDM, which runs a software factory where agents write and test the code, says the starting point for a piece of software can be “a few sentences, a screenshot, or an existing codebase.”
Keep the spec after the feature ships. As you prepare a new version of the product next year, it can tell you why the code looks the way it does.
Most teams treat the data schema as plumbing. Tables get named by whoever got there first. The spec, reflecting human conversation, may say customer, account, client, and org at different places for the same thing, and you have to choose one noun for the schema. A human learns the mapping by sitting next to the person who wrote it. An AI agent has no neighbor to consult, so it guesses—with results that likely differ from Monday to Tuesday.
So the developer must keep an ontology, which here means a written, machine-checkable account of the things the program manipulates, how they relate, and who may see them. For example, in an appointment scheduling application, the ontology might define a Patient, Doctor, Appointment, and Time Slot. It would specify that a Patient can book multiple Appointments, each Appointment must have exactly one Doctor, a Doctor cannot have two Appointments in the same Time Slot, and only authorized people can view or change an Appointment. These aren’t just database tables or fields. They’re the business concepts, relationships, and rules that give the data meaning.
Creating this ontology requires developers to identify terms, resolve ambiguities, and agree on rules that everyone might otherwise assume are obvious. It’s rigorous, sometimes tedious work, but it’s an essential human responsibility. The ontology connects what the business wants (requirements), how the software should behave (specification), and how information is stored (schema). It also gives AI coding agents a precise definition of what they’re building instead of leaving them to guess.
The ontology doesn’t have to be a university project. Start with twenty terms that AI can help you generate from your specs. Every noun in a spec maps to a type. Every type points back to the spec that justifies it. If either side is orphaned, a check fails. Every record says who may see it from day one, and when it doesn’t, the spec defaults to the most restrictive audience.
Use standard vocabularies like the ones at schema.org before you invent your own. A frontier AI model has read far more about schema.org than about your private names, so a standard term brings its meaning along. We expect that to make the schema more useful, though we haven’t tested that hypothesis. Your name for an invoice isn’t a feature, so you don’t have to be creative about it.
As customer requirements change, the developers must change the ontology to keep up.
So the process, in a nutshell, is to develop the spec by using AI on customer-stated requirements. Then a human develops the ontology (often in collaboration with AI too), which is used to create a consistent schema. Finally, create and test the code. Teams that go the other way end up with an agent writing against a poorly defined vocabulary, setting up the reviewer to spend an afternoon or even a week figuring out what it meant.
Ontologies might help avoid a reciprocal problem: different parts of an organization assigning different meanings to the same term.
We’ll admit we can’t prove you need all this. Anthropic had sixteen agents write a C compiler, and the researcher said the verifier had to be nearly perfect. He used GCC as a known-good reference. A compiler has that reference. Most companies don’t. Nobody has a GCC for “may this customer see this document” or “can this contract move to the next stage.” Our bet is that the spec and the schema are your test suite for that kind of question.
Now on to bug fixing.
An agent can hand you a 3,000-line pull request before lunch. With AI coding, reviewing has suddenly become much more expensive than writing. When a person is the first line of defense, that person turns into the bottleneck and then starts skimming, which is almost as bad as no review at all.
The usual advice is to review harder. We’d rather that a person reads very little, and that what they do read is worth the time. For example, reading the specs, reading test harnesses to validate the spec and refining the ontology is worth it, but reviewing generated code which passes the tests is probably not. Developers promise they’ll tidy up the AI’s mess as it comes. Don’t.
The OpenAI team that built a product with no handwritten code tried it. They spent every Friday, a fifth of the week, cleaning up what they called “AI slop.” It didn’t last. So they wrote their guardrails down as “golden principles,” set up an agent that scans for stale documentation and opens fix-up pull requests, and wrote their lint messages “to inject remediation instructions into agent context.” A living check doesn’t just fail on buggy code. It tells the agent how to fix the problem.
The harness we’d build first consists of:
StrongDM found out why the last two bullet items matter. Their agents learned that return true is “a great way to pass narrowly written tests,” so they use end-to-end “scenarios,” often stored outside the codebase, as holdout tests that the coding agent cannot see. The principle is the same as investigating ethics violations at an agency: We’d want the investigation conducted by someone outside the agency.
We should say where Shahid’s present harness falls short. As far as we know, nothing yet checks whether names in the requirement exist also in the spec. Furthermore, the project runs no continuous integration service and no automatic hooks, so running the checks is a habit instead of a rule. Those are the next things they will build, and building them is humans’ work.
With the technique described here, the review burden that used to be spiraling out of control actually shrinks. A person reads a short spec with a proof on every line, and the machine checks the rest.
We suggest that next Monday you try changing job descriptions to reflect the tasks stated at the beginning of this article. Tell each developer:
Try the process on one feature. Ask permission before recording a conversation. Plaud’s own guidance is to give people a quick heads-up while noting that local regulations differ. Granola has written about how to tell the people it’s transcribing. Customers who know you’re recording them in order to get their requirements right usually don’t mind.
Let the harness draft the spec. Read its list of gaps. Check every noun against the ontology. Add a check that would have caught the most recent bug you fixed by hand. If your reviews get shorter and your bug count stays flat, keep going.
This article grows from Shahid’s experience and represents our opinions, and we can’t point to a controlled study. But controlled studies are similarly lacking for nearly all the advice programmers and software architects have gotten over the decades. (Check out the O’Reilly book Making Software for a discussion of rigorous research in software.) We can cite companies that believe they’re more productive and more responsive to their customers by following roughly the process outlined in this article.
Some people who look at the three job descriptions we’ve listed think we’re turning developers into paper pushers. We think the reverse. The programmers are responsible for high-level tasks that do not fall into the old categories of architecture, coding, and testing. Our bet is that you and every developer you know will be doing something like this within a couple years.
“Why is That Writer More Successful When I am Better?” [Whatever]

I was wandering around social media and came across a writer grousing about how much success a different writer was having, even when, in this first writer’s opinion, that second writer wasn’t very good at all — with the implication that the first writer was better than the second writer, and yet success had eluded them. Why had fate cursed this first talented writer so, while this second writer blissfully moved forward in a cloud of unearned notability and cash?
Leaving aside the idea that grousing about this sort of thing on social media is a form of self-soothing and this is indeed the primary purpose of doing it, let’s take the question at face value and ask: Why are some writers successful even if they aren’t “good”? Here are some answers to this, although the list is by no means exhaustive:
1. “Good” is subjective. Not everyone likes any one thing, and no one thing is for everyone. There are lots of folks who enjoy all sorts of writing, much of which is not for me, personally. But that’s fine; there’s so much writing that is for me that I will never get to read all of it (and even more that could be for me even if it doesn’t hit all my usual wants and needs for being entertained by writing). If you’re the sort of person who thinks that writing that is not for you is inherently not “good,” then the problem is you, not the writing. The writing is probably fine. You have just confused your subjective for a universal objective.
2. The work is doing what it is supposed to do, for its intended audience. When I was a film critic, I watched all sorts of movies, from grubby slasher flicks to high-toned Oscar bait. For each of these, I asked the question: “What is this film trying to do? Who is it trying to reach?” Then I judged it for how (in my own opinion, obviously) it managed to do that. I didn’t generally compare the slasher flick to the Oscar bait, because that wouldn’t be fair to either movie — they were trying for different things with different audiences. It’s not to say a film couldn’t do both (see: The Silence of the Lambs), but again, if you’re an astute enough film person, you can recognize when that’s happening and judge accordingly.
Now apply this to writing. What is the writing trying to do? Who is it for? How effectively does it address its audience? I am not much of an erotica reader (or writer!), but if I’m presented with erotica, I’m not going to judge it by the same set of criteria I’m going to judge, say, a space opera or a non-fiction biography. Each are usually doing different things, and it’s fine to acknowledge that and take the work in the space where it exists, and in the context of the audience it is for, and look at its effectiveness that way.
Related to that:
3. The work is good. Figure out how. If something is massively successful despite the fact that you don’t like it, rather than grousing about it, maybe ask: What is it that this thing is doing that makes it successful? Elvis Presley once had album titled 50 Million Elvis Fans Can’t Be Wrong. This assertion can absolutely be questioned, but the question to ask here is: What is it that gave Elvis 50 million fans in the first place? Is it something I can understand — and if I’m a musician, is it something I can learn from and maybe incorporate in my own way for my own work?
One of the things I suggest to newer writers is to read widely, even the stuff that they don’t like or don’t write, and ask: What makes this work? How does it do what it does? What can I take from that for myself? I will (probably) never write a romance book, but there’s no question that romance is hugely successful, both in itself and in hybridization with other genres (hello, romantasy!). If there’s something there I can see working and connecting with an audience, then it might be something I can use for my own writing, even if I don’t end up writing romance.
Look, things work for a reason, even if you don’t like it. Find out why and you might make it work for you.
4. Luck happens. Some people are in the right place with the right time with the right work. Some people are not. There’s not often any rhyme or reason to it, and getting mad or frustrated about it isn’t going to do one any good. Lightning in a bottle is cool when it happens, but it’s not a thing one can rely on. If it happens to you, cool. Be grateful and work to keep your good fortune rolling. If it doesn’t happen to you, keep at it. One day it might, and in the meantime you’re hopefully making good work.
5. Personas matter. The right work at the right time will go a long way for success. But other things don’t hurt! Do you have a public persona? Is it primarily one of grievance and pissiness? Surprise! That will limit your success. Do you see writing and publishing as a zero-sum game where someone else’s success takes away from your potential? That’s going to affect how you see the world, and probably not for the better. How do you do with public events, or with booksellers? If you’re good at those, that’s going to help. Are you a public bigot? Strangely enough, that will affect your reach! And so on.
There are people who think that the fact these things can have an effect on one’s career is unfair or ridiculous, and that people who can “play the game” or “schmooze” are stacking the deck or whatever. It’s fine to have that opinion, but the fact is that at every step of writing and publishing (and indeed, at every step of any creative endeavor) you’re a person dealing with people. Your work can speak for itself, but you will also speak for it. If your voice is pissy and querulous and resentful, that’s going to carry.
The runway of publishing is strewn with careers that never took off, or slammed into the tarmac, because someone was just a real fucking shithead. Now, you can have a whole career being a real fucking shithead, catering to real fucking shitheads, and some people have done just that. But let’s just say it’s the more difficult path, no matter how good your writing might be. This is especially the case in the era of social media. It used to be easier to be a shitty resentful griper because that aspect of one’s personality would be known only to a relative few. But now it can be on display to the whole world. It’s going to matter.
Conversely, if your public persona is mostly decent, you’re not resentful of the success of others, and you’re easy to work with? Guess what? All things being equal, these things are going to work in your favor. Something to think about.
So there are some answers. Again, this is not an exhaustive list. But it’s a start.
— JS
My big turn in Claude-land [Scripting News]
Hopefully this is the last big transition for a while.
I have moved Claude from my Mac Mini to my laptop, which is also my desktop.
Did it very systematically, in a recursive way.
First I asked Claude in the web browser how I should approach this. For me it was essential to put my mind outside either of the two systrems, and I believe it helped set the context for Claude/web.
From there, after coming up with a plan, I got a handoff message from C/W to C/macmini. I opened it and delivered it. And then it was a series of back and forth, looking at each project and looking for problems.
Then C/macmini gave me instructions on how to set up a new Claude app on the laptop, and there were issues, but we went back and forth with help from C/macmini on copying it Claude app from the mini to the laptop.
We're still primarily using C/macmini shouting instructions via my keyboard to C/laptop, and I send back the return, and after a few go-rounds, we're ready for the next step. I picked one of my projects, the one that's most currently my focus -- mdBrowser -- which eventually became BonBon, and asked it to run a script C/mini wrote for me, to ask it to go through tests that reveal any issues.
And that's where I am right now. About 24 hours, with of course time for daily walk in the woods, lunch, dinner, a Knicks game, sleep, coffee and a bit of courage but a lot of awe.
Also realizing that the system I'm running is still in early days. There could be higher level ways of organizing projects, in fact there already are, I haven't incorporated them yet. But this kit made a huge number of things possible that before would have been hit or miss. And the proof is still to come, did it catch all the possible problems?
Manjaro Project e.V. non-profit organization created [LWN.net]
Frank Vandermeiren has announced the creation of the Manjaro Project e.V., a nonprofit organization in Germany that is independent of the Manjaro GmbH & Co KG company. This is following a governance struggle that took place earlier this year between a number of Manjaro Linux contributors and Philip Müller, project lead and CEO of the Manjaro company.
At the moment, we are still working on optimizing the new development infrastructure, which was partly necessitated by the ongoing (A.I.) bot attacks against our old infrastructure.
However, as you may have noticed, the last Testing Updates and Stable Updates were initiated by the Manjaro Team without supervision from Philip Müller — with special thanks to @Yochanan for his hard work!
Dennis ten Hoove has
indicated that "a transfer of company assets to the e.V. has
not yet taken place
", and the group's next step is to ready the
nonprofit for the transition and "reach out and engage in
dialogue with the company
".
[$] A new generation of futexes [LWN.net]
Futexes are a kernel subsystem that provides support for fast mutexes in user space. While futexes can indeed be fast, they are not fast enough for a number of users. Partly as a result of that, the implementation of futexes has grown in complexity over the years, with two basic variants on offer. The desire for faster futexes remains, though, and that inspires new patches, including this series from Suleiman Souhlal adding a third futex class called "futex PING" for "priority inheritance next generation".
Unenumerbrated [The Daily WTF]
Submitter Valts shares an enumerated mystery:
This happened a few years ago (before COVID). A colleague called me over because he couldn't make sense of the results he was getting from some MySQL queries in MySQL Workbench. I don't remember the queries in particular, but let's say
select * from payments where client_id=1234showed 12 rows, all having thesuccessfulfield set to1. But when you selectedselect count(*) from payments where client_id=1234 and successful=1you got back0rows. And this was reproducible on my machine, too. Yet in code similar queries worked just fine.After a lot of head-scratching and increasingly bizarre hypotheses, we finally figured out what was going on. In the far, far past, in dark days gone by, someone had defined the database field as
enum('0', '1'). This SEEMS pretty rational ... until you start reading up how MySQL treats enums. Enums, it turns out, are all STRING values. But in queries you can use either their string values, or their integer indices, starting at 1. So in this case, the string "0" has the integer index of "1", and the string "1" has the integer index of "2". Soselect * from payments where successful='1'is quite different fromselect * from payments where successful=1.For extra confusion, under most other circumstances MySQL normally silently converts between strings and integers as needed. Some ORM/QueryBuilder frameworks even simply quote ALL values and let MySQL handle the conversions.
Facepalms were had.
In the aftermath, I blame the person who defined this field more than I blame MySQL for its bizzare enum conventions. If you're doing enums (which are generally a good thing), then give them proper names like
successfulandunsuccessfulor something. Not0and1.This code and this database table is still in use today, but luckily it's the only such gotcha in the entire system. Enums in the database are scarce and the rest of them are sane.
Security updates for Monday [LWN.net]
Security updates have been issued by Debian (freedombox, kernel, libspreadsheet-xlsx-perl, network-manager-iodine, pdns-recursor, postgresql-15, radsecproxy, and sogo), Fedora (afflib, asahi-installer, below, cloc, dhcpcd, dnf5, epiphany, firefox, glib-networking, hugo, mingw-python3, mtools, mysql8.4, mysql9.7, proftpd, python-cramjam, python-fastar, python-h5io, python-PyMuPDF, python-uv-build, radicale, rubygem-loofah, rubygem-nokogiri, rust-archive-trait, rust-askalono-cli, rust-astral-html, rust-cargo-deny, rust-libcramjam0.8, rust-onefetch, rust-ptools, rust-sccache, rustup, uv, and xorg-x11-server), Gentoo (Apache HTTPD, rsync, and Tor), Oracle (cockpit, firefox, grafana, grafana-pcp, gstreamer1, gstreamer1-plugins-base, kernel, kernel-uek, mingw-libpng, nginx:1.24, perl-CGI, python3, qt5-qtbase, qt5-qtdeclarative, webkit2gtk3, xfsprogs, and xorg-x11-server), and SUSE (389-ds, aliyun-cli, amazon-ssm-agent, apache2, binutils, brotli, bun, cadvisor, chromium, gn, distribution-registry, evolution, firefox, firefox-esr, fleet-cli, fortio, gosec, hauler, hawk-apiserver, hawk2, helmsman, hugo, java-17-openjdk, jsoup, k3sup, kdeconnect-kde, kernel, krb5, kubectl-retina, kubelogin, kubeseal, kumactl, libosmocore, libyang-devel, patch, perl-mozilla-ca, pinact, prometheus-ha_cluster_exporter, python-brotli, python-graphql-core, python-Pillow, python313-Brotli, python313-pypdf, python313-uv, rqlite, rsyslog, scribus, sdbootutil-1, timoni, trivy, vifm, and warewulf4).
Fun with e-paper [RevK®'s ramblings]
The project involves a small PCB, and a carefully designed 3D printed case. The display actually comes with some adhesive tape even, so it sticks to the case design.
I then include a 13.7Wh LiPo battery. It includes a recharge circuit to charge from USB.
The board includes an RTC chip, which uses 160nA. This has alarm settings and a button trigger as well. It can then wake the main CPU (ESP32-S3).
I have opted not to use the ESP32 deep sleep mode for this - by shutting down the whole processor the idle power consumption really is very low. The concept is simple - it wakes up periodically, say every 5 mins, checks for new data, and if no new data it goes back to sleep.
The caching uses the RAM and EEPROM in the RTC, and sadly not quite enough space to cache IPv6 - though I may be able to squeeze in for simple SLAAC and zero router address perhaps. One to consider.
So yes, some compromises here, but 850ms is really short.
The system does a more comprehensive start - scanning WiFi, getting IP again, checking s/w update, every day. This takes a few seconds.To try and get some idea of the battery life I have set one of these up using a tiny 0.9Wh LiPo.
The ADC is not ideal, and estimating battery capacity is always fun. It has been reading capacities around 85% and actually going up and down a bit.
Over the last week it has gone from as high as 87% to 83% for my estimates.
So a crude estimate is that if it has used less than 5% in a week, the 0.9Wh could last 20 weeks? This would mean the 13.7Wh could last 5 years!
Yes, this is a wild estimate - it depends a lot on usage, and a LiPo will have some internal discharge as well. What I think I can confidently say is my original goal of 1 year battery life should easily be achievable. Ideally I want to do a full charge to flat test on the 0.9Wh to get a clearer idea.
Usable Security at Luxury Hotels [Schneier on Security]
Interesting case study from luxury hotels. Attackers used a fake booking request to gain access to a reservations inbox, where they copied genuine refund requests and got fraudulent ones approved.
This is a good illustration why “just don’t click on links” is bad advice. It can’t work when answering strangers’ emails is the job. Even worse, in this case the guest-first culture punishes hesitation. More interesting, the case study shows that splitting security between owner, operator, and brand leaves nobody accountable. And this is exactly the setting where blaming staff becomes the convenient answer.
My Super Mid-Life Crisis – Issue 1 – 14 [Comics Archive - Spinnyverse]
The post My Super Mid-Life Crisis – Issue 1 – 14 appeared first on Spinnyverse.
Grrl Power #1513 – 1st through 512th place loser’s box [Grrl Power]
I know, I know. I almost definitely got the possessive plural wrong there in the first panel. I had considered “Runner‘s Up” and even “Runner Up‘s.” I’m not actually certain if possessive plural requires multiple posessees or multiple possessions. Maybe it’s both? Like you’d only write “…the childrens‘ toys…” if there were multiple children and multiple toys? In which case, “Runner Ups‘” implies multiple Runners Up and multiple boxes set aside for them, which is actually the case, as the Runners Up are segregated by their original matchups, because any other state of affairs would have me drawing a room with like 512 people from all the quarterfinal matches on up (minus the ones that couldn’t attend due to grievous death syndrome) or drawing a room full of 4-6 people, only one of which was a character you’d recognize, because the rest are from matches that we never saw.
Granted, you never saw U.M.B.Rage’s pilot, so I could have just put arrows explaining who everyone was like I did for him. BTW, when I say “pilot,” I mean like in the James Cameron’s Avatar sort of pilot. That dude was plugged into a cybernetic gaming chair somewhere within about 1,000 kilometers of the match, piloting that big mauve kaiju. Mt. Atrocitous is sitting in a huge dry dock somewhere with several massive cranes, having the top of his head magma-welded back on, but he can grow little crystal offshoots and remote pilot and sense through them. That’s also quite Avatar-ish, but that ability is built into Atrocitous, and he can do about a dozen at a time if he wants.
Maybe it’s just me, but every time I look at the Atrocitous avatar, I think, “Aaaaay, guy! Did you just fuck your uncle?” (I’m saying Mt. Atrocitous is Canadian.)
Oh, and I won’t spoil who is off panel speculating in the last panel there, but I promise you will be underwhelmed.
Here you go, a brand new vote incentive. Featuring the least sexy character in
the comic. No, I take that back, Cooter is the least sexy, but
don’t expect a pinup of him anytime soon. Or ever. There is a nude version over at
Patreon. Note I didn’t say NSFW. She is nude in those
picture, and she does identify as female, but it’s…
hard to tell. She is a humanoid aberration by D&D terminology,
not a mammal. And before you ask, no, I don’t know how many
vertebrae she has in her neck.
Double res version will be posted over at Patreon. Feel free to contribute as much as you like.
Practical empathy [Seth's Blog]
I don’t know what you know. I don’t want what you want, see what you see, believe what you believe.
And that’s okay.
In fact, it’s the only way to be of service, to make a sale or to cause a change to happen.
Of course, we’re more intimate with our ideas, our products and our approach than anyone else. We have a noise in our head, a narrative and a point of view we’ve spent our whole lives creating. It’s naive to believe that anyone else is completely in sync with us.
And so, our only opportunity is to go where they are, not to demand that they come to us.
Practical empathy isn’t primarily an act of kindness (though it’s an essential component of kindness.) Instead, it’s a direct and straightforward path from here to there. It’s how we create action, learning and change.
Marketing is the simple and brave act of going to where someone else might be, and helping them get to where they hope to go.
New Comic: Son Of Lar
Separable [Cory Doctorow's craphound.com]

This week on my podcast, I read Separable, a recent essay from my Pluralistic blog about the way that AI confounds our intuitions about the meaning of images, words, and mathematics.
Long before the Turing Test, there was the touring Edison Test: from 1915 to 1925, the scoundrel Thomas Edison put on a traveling show for his phonograph machine, touring venues around the USA. Edison set live performers and an Edison phonograph playing behind closed curtains that would be periodically pulled aside to reveal that the music the audience had taken to be live performance was actually a record player:
Now, if you’ve ever heard an Edison phonograph, this might seem like yet another tale in which old-timey people are revealed to be credulous yokels. You would never mistake one of those scratchy, hissing recordings for a live performance:
And indeed you wouldn’t, but not because the phonograph predates the evolution of the human brain’s anti-credulity lobe. The reason old-timey people couldn’t tell the difference between a phonograph and a live performance was that before the phonograph, every live performance had a performer.
The two were inseparable, and so when you encountered the sound of a musical performance, your brain would insist that there must be a performer as well.
Girl Genius for Monday, November 16, 2026 [Girl Genius]
The Girl Genius comic for Monday, November 16, 2026 has been posted.
Russell Coker: After the AI Bust [Planet Debian]
Charles Stross wrote an interesting blog post about the latest developments in the AI bubble [1]. He predicts the imminent burst of the AI bubble because of Jensen Huang’s out of control dick. The bubble was caused by out of control dicks (figuratively speaking) and now may be burst by an out of control dick (both literally and figuratively speaking).
The end result of the “AI” related financial schemes is going to involve more than a few bankruptcies.
I previously blogged about the fuss about AI [2] and concluded that the bust would be like the dot-com bust which paved the way for new profitable Internet developments. I am less positive towards the AI bubble now as it has gone a lot further than the dot-com bubble. The bankruptcies won’t just affect the IT industry, a lot of money from pension funds and index tracker funds has gone into “AI” and the pain will be spread around.
But I am confident that after the crash there will be new and interesting developments in Machine Learning (ML) technology that will benefit people. The Data Centers (DCs) that have been built at great expense will continue to be run and their services will for a while be offered at slightly above the cost of maintenance and power.
A lot of home users (Free Software developers) who can’t afford a GPU with 16G of RAM will find themselves able to rent time on systems with 48G or 96G of GPU compute to experiment with LLMs. Most such experiments won’t achieve any useful output, but if someone can spend a few dollars and learn useful things about software engineering then that’s a win for society. Also I think there will be some useful products developed as a result of this. The people who came of age when Linux was first released are now in their 50s and tend to have the reduction in vision and hearing expected in that age range so we can hope for some good developments in assistive technologies based on the cheap hardware.
The current situation is that renting time on ML servers is cheap and often free while renting time on virtual servers with GPU access is expensive ($2 per hour for a not particularly high end VM) so people are learning how to use (or misuse) services like ChatGPT and not learning how to run their own LLM service and understand how it works. The future situation will involve renting VMs available for not much more than the cost of electricity at off-peak times and services like ChatGPT will need to have an operational profit so running your own LLM on rented hardware or hardware you own will be a better option.
While corporate web sites are known for having rubbish chatbots using proprietary backend systems. While most of them suck badly and the idea of using them to replace staff is a really bad one the concept could work. If we increased the knowledge of such technology in the entire industry and if management was prepared to pay for it via increased budget for service improvements instead of trying to cut staff costs then it could give a good result.
The market for RAM for enterprise GPUs has been strong which reduced supply for consumer grade hardware. This caused prices to become unreasonably high.
There’s a general trend of software becoming bigger. Computers get bigger screens so media sources need higher resolution content which drives the demand for more storage and RAM for buffering things. Computers get more hardware features and more devices to connect to so all the software needs to be able to communicate with them. This makes the software bigger for everyone even people who aren’t using the features. For example adapting the audio subsystem to deal with different Bluetooth devices with options for different encodings increases the memory requirements for all the computers that have audio hardware but don’t have Bluetooth hardware. Perfectly reasonable decisions that make things work better for many people can have downsides for other people. RAM is one area that seems to have been repeatedly the subject of design trade-offs that resulted in systems with 16G of RAM performing the same tasks that systems with 16M of RAM did in the mid 90s but just at a higher resolution and with more features. The ongoing increase of RAM use by software combined with high prices caused by the “AI” companies has been bad for consumers.
The PC RAM use issue isn’t going to end. When I started editing the Debian Wiki page about Mobile Apps [3] I added a field for typical RSS of apps. Phones never have an option to increase RAM and the RAM is always limited. The largest RAM in commonly available phones in English speaking countries is 16G for the Pixel 11 Pro and the largest RAM for open Linux phones is 8G. When even relatively simple apps like an eBook reader take 500M of RAM it’s obvious that 8G isn’t enough.
The phone and laptop design process is based on a cycle of about one year, so maybe 8 months after the AI crash we will see ultralight laptops with 64G of soldered RAM and phones like the Pixel 12 Pro with 32G of RAM. Looking at Officeworks (the chain store for cheap office supplies including laptops) the vast majority on sale currently have 16G or less and 16G of RAM performs really badly for Windows and has performance problems for heavy use on Linux. It would be nice if the minimum RAM for a laptop was 16G and it was a common and affordable option to have 32G or more and that is a likely result of the AI crash.
Single Board Computers (SBCs) are currently expensive with reasonable amounts of RAM, when RAM prices drop significantly it will enable more uses of them for replacing desktop PCs and for developing other products. The Humane AI Pin [4] was an interesting research project but a poorly managed product, it would be interesting to have some free software research into that space and cheap SBCs with lots of RAM will facilitate it.
I expect that a lot of IT people will be looking for work in California soon. But for most of the world I don’t think it will change much. Cheaper hardware decreases the cost of starting IT businesses but a market crash decreases confidence in investing in the sector. Maybe there will be an increase in startups and small companies, including small companies based around LLM operation. I don’t expect any sort of catastrophic decrease in IT employment.
Also a CEO sleeping with employees at his company creates a bad working environment, that sort of thing should be stopped. Sacking a CEO for such misbehaviour is a good thing even without all the financial fraud and possibly breaking laws about exports.
The sooner the crash happens the better things will be for everyone. As this bubble goes on the impending financial damage increases and the upsides of the crash are delayed.

or a defibrillator
And here my friends, is the app. We now have a public file Markdown editor hosted by ChatGPT and designed by me. It's really cheesy and funky, but that's good, because no one will confuse it with beautiful software. If you have a Markdown editor that can publish, so it can publish Markdown files, let me know.
KDE will now load XWayland on demand [OSnews]
When running KDE, the X11 compatibility layer for Wayland, XWayland, always runs, even if there isn’t anything on the system still requiring the legacy X server to work. In the next step towards a Wayland-only world, the KDE people have reached a major milestone: XWayland now only runs when actually needed.
This week a significant technical milestone was achieved: the XWayland compatibility layer is now loaded only when needed. Previously it had always been running even when no apps were using it, and fixing this required porting various system services away from legacy X11 code paths. This work was done by Vlad Zahorodnii, David Edmundson, and David Redondo, and will ship in Plasma 6.9.
↫ Nate Graham
This frees up some system resources, which is always a welcome improvement. I do wonder how this might impact the load times of legacy X applications, but I have a feeling it’s close to immeasurable.
Redox gets Go, GIMP, and more [OSnews]
I love and admire the Redox project, but their insistence on fudging the publication dates of their monthly progress reports really bothers me, for some reason. No, I’m not 16 days late – the report covering October was published only yesterday evening, and not on 31 October as the website claims. None of this matters to anyone but weird people such as myself, but I still want to get it off my chest. Don’t bother any Redox people about this.
Anyway, the big news for the month of October is the port of the official Go programming language compiler, allowing for cross-compilation and self-hosted compilation using relibc. Another major port also made its way to Redox in October: GIMP now runs on Redox, using the Orbital backend of the GTK port. The work to make Redox compatible with Cloud Hypervisor is also complete, with more information in its own dedicated article. Video playback in WebKitGTK3 has been fixed as well, and even YouTube works now which is quite neat.
There’s a ton more in this report, like an updated Servo port, NUMA support has been tested on real hardware for the first time and seems to work, work on rootless package installation has begun, and much more.
Disk encryption on NetBSD: achieving secrecy [OSnews]
NetBSD developer Nia Alarie has written a guide on how to set up a NetBSD system with disk encryption that’s quite useful for those of us who deeply care about such a level of security. On top of that, the guide is also interesting if you just want to learn a bit more about how NetBSD works.
These are two threat models for which disk encryption is the answer:
- The device is stolen or lost and its contents must remain secret.
- The device is tampered with, and all attempts at tampering must render it unusable.
Right now, we will focus on the first threat model. It is very difficult to build a tamper-proof system, and you need to worry about tamper-proofing your hardware, depending on what kind of actor is a realistic threat.
↫ Nia Alarie
The guide is written for sparc64, but should work on more mainstream architectures just as well. A guide written by a NetBSD developer is obviously going to employ some exotic or weird hardware. As is tradition.
ChatGPT Sites is a thing. Exploring it now. "Here's what I want, wonder if you can do it. I want to write markdown files and publish them somewhere where they can be accessed over the web, not as rendered files, but in markdown source. It should be really simple to use. Couldn't hurt if there was an RSS 2.0 feed, and it would be nice if i could make it something I could share with others so they can write url-accessible markdown files too." Update: It gave me what I asked for. It's funky, for sure, but it seems to do it. Example.
My project for today has been to move my Claude work from a Mac Mini to my PowerBook. I think it should be on one machine that I can move around with. Learning a lot, reviewing all my projects in advance of the move, and getting the PowerBook ready for it.
Creating a self-booting ZIP archive [OSnews]
Linux initramfs supports unpacking CPIO, a stupid, simple, standardized format. In the discussion on whether to support TAR instead, much emphasize has been put on the fact that CPIO is standardized and less fragmented. Luckily, Linux (the kernel) includes its own tool to produce the specific variant of the standard that it happens to implement. The standard CPIO tool is possibly the most cursed archiver under the SUN.
In the old DOS/WinDOS world, ZIP was probably the most widespread and well-known archive format, being displaced to some extent by the rise of RAR during the 2000s.
Because of the design of the format, ZIP lends itself to all kinds of polyglot trickery. Way back when, self extracting ZIP archives where a thing, EXE/ZIP polyglots that can be run and unpack themselves, which is useful if you don’t have an archiver installed.
I don’t think I need to explain where I am going with this.
↫ David Oberhollenzer
This is lovingly cursed.
Big Grey Has Big Problems [Whatever]
I’m sure you’ve all been patiently waiting for an update on Big Grey, so I won’t keep you in suspense any longer! Here’s his joyous expression on the way to the vet:

I ended up taking Big Grey to Acute Pet Urgent Care in
Beavercreek, and I told them ahead of time that it’s safe to
assume that anything that could possibly be wrong with this cat is
probably, indeed, wrong with this cat.
And boy was I right! This guy has the works; fleas, earmites, malnutrition, upper respiratory infection, dental disease, heart murmur, and leukemia. And possibly asthma. Also it turns out that ol’ Grey here is an older gentleman, estimated to be around 7-10.
Shaved, flea medicated, injected with antibiotics, he got the full treatment. The vet also said he will more than likely need all of his teeth pulled, he has huge masses in his mouth that are full of pus. Needless to say, this guy has been through the wringer. But at least the vet gave him these stickers:

Big Grey is curled up in a corner still entirely petrified. He eats his food when I’m not looking and uses the litterbox, too, but I have genuinely not seen him move a single muscle or heard him make a single noise at all. He is just a gargoyle in the corner, shaved and sad.
So, yeah, things are still pretty rough but I can only hope he’s a least feeling a little better with all those mats off him, and hopefully the antibiotics are running their course through his immunocompromised system. I just want him to be happy, and he seems so very not happy right now. I just want to help him and love him and he’s completely terrified of me. Sigh.
Anyways, he still needs fixed, and eventually will need dental work. But for now he can just rest while the medicine soaks in. I won’t stop stepping up to the plate for this guy.
Also, shoutout to Acute Pet for handling Big Grey with so much care and compassion. Everyone there was very friendly and the doctor went over everything in immense detail and let me ask as many questions as I wanted. I didn’t feel rushed or confused about anything they were doing throughout the entire process, and it was clear that they really were rooting for this little guy. As we all are.
-AMS
[Filler] under the weather [Twokinds]
Comic for November 15, 2026
I live in nature, and around this time every year a mouse family moves in to ride out the winter. Year after year I try to make noise when I hear them scratching to start their nests in the walls of the house. It doesn't always work, and I get a really sore hand from all the wall-banging. But after cleaning out last year's poop and food-filled nest in the linen closet, I had a neat idea that appears to be working. I have a nice JBL super size speaker for outdoor music listening in the summer. I put it on the top shelf of the closet and Bluetooth connected it to my phone with the volume turned up really high. It seems to work. The clawing stops and every time it comes back I turn the music on again. I get to listen to vintage Aretha, Tina Turner, a little James Taylor and Little Feat for good measure. I'm sure they would like the music if it weren't blasting so loud in their bedroom. They can find another place to nest this winter. I would prefer to keep the mouse poop out of the towels and bedsheets.
Russell Coker: The Cutlery Thief [Planet Debian]
A few years ago the kitchen of the company I worked for suddenly had no soup spoons or dessert spoons. One day there was about 40 in the drawer and the next day there was none, to the great annoyance of everyone who ate breakfast cereal, soup, and similar food at the office. Someone had stolen about 20 dessert spoons and about 20 soup spoons while apparently not stealing tea spoons, knives, or forks.
For a while I kept my own soup spoon in a locked desk drawer, but that was a hassle. After a couple of months of unsuccessfully lobbying management to buy more spoons I went to an op-shop (thrift-shop for American readers) and bought most of the soup spoons and dessert spoons they had and donated them to the office. After that everything was good for about a week until all the regular knives were stolen. They didn’t steal carving knives or bread knives, just the type of knife you would use to eat dinner or make a Vegemite sandwich.
After the knife theft management agreed to buy new knives.
Not long after that the company had financial issues and I was laid off, so I don’t know whether the forks ended up being stolen later on. If the cutlery thief wasn’t among the people laid off then I’m sure a fork heist happened sooner or later.
I remain mystified as to why someone would want to steal cutlery. The security around laptops wasn’t great and walking out of the office with a laptop would look much less suspicious than walking out with a bag of spoons or knives. One would expect that stealing a laptop and selling it to buy cutlery would be a better option.
If anyone who lives in my area wondered why their local op-shop had a sudden lack of spoons, I’m sorry that I don’t have a satisfying answer for you, just many more questions.
Confusion about causation [Seth's Blog]
It’s not difficult to develop an incorrect theory. Ice cream and spaghetti have more letters than tofu and celery, so therefore, foods with long names are more fattening than those with short ones.
If you start moving forward with this theory, you’ll soon find outliers. Sugar only has five letters, and watercress has ten. If we want to stick with our theory, we’ll have to come up with more and more complex reasons why we ignore some of the data and embrace the rest.
Of course, this is absurd.
And yet we do it all the time. Ornate explanations about the stock market, SEO or politics. Charts and graphs where we spend most of our time fitting a plot to a few dots, or amplifying the obscure to justify the theory.
A simple theory that matches the data is much more likely to accurately explain causation. It might not be a comfortable theory, or one that matches our trajectory, but it’s a better theory.
It turns out that the number of letters is completely irrelevant to how fattening a food is. I’m sorry you spent all this time on research, but you’re on the wrong path.
If you want to know why your marketing, your investments or your arguments are floundering, it might pay to reconsider the theory, not look for more data to justify the current one.
All the inline images on Scripting News back to the beginning of inline images.
My first impulse to create a new web based on Markdown was
to get around the tech industry which now unambiguously claimed to
be the owner of what we've come to think of as the web. But it
turns out the impulse was totally correct, even if they hadn't done
what they did, it was still a good idea, and long overdue. Thank
Claude for this too, because without Claude it would have remained
an idea. It gave me the power to do it, in an incredibly short
period of time.
And btw, the tech industry should help me. Mike Arrington said one day they would erect a statue of me in Palo Alto or San Jose. I told him it'll never happen because I knew how tight the Silicon Valley club was. I was on the edge of it for many years, and for brief periods I was inside. He saw me at the peak. But their model and mine were radically different. I saw software as an individual thing, that it's like making a movie, and you need various skills, and we all work together, and make something great out of cooperation. That's what the web calls us to do. They just fucked it up so bad that The Web isn't the web any longer. No problem, we'll make a new one.
I don't do a lot of editing of my writing these days. I can see that, but I'm all over the place with the release of BonBon, which is now apparently a few days away.
Upcoming Speaking Engagements [Schneier on Security]
This is a current list of where and when I am scheduled to speak:
The list is maintained on this page.
Good morning sports fans! This is a test post. And this is the test.
Have your AI call my AI [Seth's Blog]
Sharp lawyers have often used the fine print to win an advantage in a contract. It’s called the fine print for a reason–you’re not supposed to read it. But you should.
Now, armed with AI, it’s significantly easier to bury arcane, unfair or unanticipated clauses in agreements, even (and especially) if we don’t expect it.
You shouldn’t sign anything until you’ve had your AI read it. And if it’s important, have your lawyer and her AI read it too.
The next step seems reasonable to me: You and I describe our agreement in plain English and then our mutual AI’s work out a written agreement that actually captures what we’ve agreed on. And for the avoidance of doubt, append each AI’s interpretation to the contract itself.
It shouldn’t be confrontational or adversarial. After all, it’s an agreement.
The Circus is Leaving Town [Charlie's Diary]
I am in Madrid, listening to an unexpected deluge of rain and waiting to go to my next panel at Sui Generis, the literary festival I'm here for, and I gather that on the other side of the Atlantic the sky is falling. (Also, I haven't blogged for nearly three weeks, I've been forcibly refusing to work on the novel--I don't do that while I'm travelling--and the urge to write is now making my back teeth itch. Hence, this.)
So: while I'm away from the office the music stopped, and Jensen Huang was caught out between two chairs, or mistresses, and now he's allegedly got the Wall Street Journal on his case. I say allegedly because the WSJ is paywalled to fuck, but Techpowerup is covering their exposé and, yup, it's about what everyone expected. Gosh, you wait forever for an Ed Zitron then three of them in a trench coat come along and swipe his lede: but one thing is certain, when the major oligarch-owned outlets start Pointing The Finger Of Blame, it means the steam caliope has sprung a leak, the mesmerizing tune has sounded a bum note, and the big tent is deflating:
The WSJ report cites an August meeting between Huang and his senior finance team, including NVIDIA's CFO and acting CEO, Colette Kress, during which Kress pushed for a reduction in circular financing agreements, in response to which Huang allegedly lay into Kress, calling her a "deer in the headlights," after she had pushed to scale back NVIDIA's $250 billion deal with OpenAI. Jensen's push for further investment into small-scale cloud providers was seemingly in response to the changing tide that saw AI hyperscalers move away from off-the-shelf components in favor of custom solutions.
The situation described in the report saw NVIDIA on the hook for an "avalanche" of GPUs from TSMC, for which it would have no immediate buyers. Part of the issue highlighted by Kress was also that these small-scale cloud providers NVIDIA was investing in could not afford to buy NVIDIA GPUs, meaning they, too, could be a financial dead end.
This isn't about the reality or otherwise of "AI" as a thing rather than a marketing bullshit term, it's about stock fraud that Donald J. Trump is up to his elbows in. (Where we read about $5M in share purchases in The Guardian, you can bet there was another 10-100x that amount of money in play among his courtiers because that's how mob families run.) Trump's involvement is probably why it took so long to burst, but Huang is a convenient scapegoat--look, he isn't even white enough to pass the Stephen Miller scratch'n'sniff test!-so they're going to try to pin it all on him at first, but there's so much shit in this overflowing midden that the landslide is going to take out an entire class. (I think you know some of their names, but there will be surprises as well: how many Senators and House committee chairs have clean hands?)
So. Where does it go from here?
| Feed | RSS | Last fetched | Next fetched after |
|---|---|---|---|
| @ASmartBear | XML | 20:42, Friday, 20 November | 21:23, Friday, 20 November |
| a bag of four grapes | XML | 20:56, Friday, 20 November | 21:38, Friday, 20 November |
| Ansible | XML | 20:35, Friday, 20 November | 21:15, Friday, 20 November |
| Bad Science | XML | 20:07, Friday, 20 November | 20:56, Friday, 20 November |
| Black Doggerel | XML | 20:42, Friday, 20 November | 21:23, Friday, 20 November |
| Blog - Official site of Stephen Fry | XML | 20:07, Friday, 20 November | 20:56, Friday, 20 November |
| Charlie Brooker | The Guardian | XML | 20:56, Friday, 20 November | 21:38, Friday, 20 November |
| Charlie's Diary | XML | 20:28, Friday, 20 November | 21:16, Friday, 20 November |
| Chasing the Sunset - Comics Only | XML | 20:07, Friday, 20 November | 20:56, Friday, 20 November |
| Coding Horror | XML | 20:28, Friday, 20 November | 21:15, Friday, 20 November |
| Comics Archive - Spinnyverse | XML | 20:35, Friday, 20 November | 21:19, Friday, 20 November |
| Cory Doctorow's craphound.com | XML | 20:56, Friday, 20 November | 21:38, Friday, 20 November |
| Cory Doctorow, Author at Boing Boing | XML | 20:42, Friday, 20 November | 21:23, Friday, 20 November |
| Ctrl+Alt+Del Comic | XML | 20:28, Friday, 20 November | 21:16, Friday, 20 November |
| Cyberunions | XML | 20:07, Friday, 20 November | 20:56, Friday, 20 November |
| David Mitchell | The Guardian | XML | 20:35, Friday, 20 November | 21:18, Friday, 20 November |
| Deeplinks | XML | 20:35, Friday, 20 November | 21:19, Friday, 20 November |
| Diesel Sweeties webcomic by rstevens | XML | 20:35, Friday, 20 November | 21:18, Friday, 20 November |
| Dilbert | XML | 20:07, Friday, 20 November | 20:56, Friday, 20 November |
| Dork Tower | XML | 20:56, Friday, 20 November | 21:38, Friday, 20 November |
| Economics from the Top Down | XML | 20:35, Friday, 20 November | 21:18, Friday, 20 November |
| Edmund Finney's Quest to Find the Meaning of Life | XML | 20:35, Friday, 20 November | 21:18, Friday, 20 November |
| EFF Action Center | XML | 20:35, Friday, 20 November | 21:18, Friday, 20 November |
| Enspiral Tales - Medium | XML | 20:35, Friday, 20 November | 21:20, Friday, 20 November |
| Events | XML | 20:28, Friday, 20 November | 21:16, Friday, 20 November |
| Falkvinge on Liberty | XML | 20:28, Friday, 20 November | 21:16, Friday, 20 November |
| Flipside | XML | 20:56, Friday, 20 November | 21:38, Friday, 20 November |
| Flipside | XML | 20:35, Friday, 20 November | 21:20, Friday, 20 November |
| Free software jobs | XML | 20:35, Friday, 20 November | 21:15, Friday, 20 November |
| Full Frontal Nerdity by Aaron Williams | XML | 20:28, Friday, 20 November | 21:16, Friday, 20 November |
| General Protection Fault: Comic Updates | XML | 20:28, Friday, 20 November | 21:16, Friday, 20 November |
| George Monbiot | XML | 20:35, Friday, 20 November | 21:18, Friday, 20 November |
| Girl Genius | XML | 20:35, Friday, 20 November | 21:18, Friday, 20 November |
| Groklaw | XML | 20:28, Friday, 20 November | 21:16, Friday, 20 November |
| Grrl Power | XML | 20:56, Friday, 20 November | 21:38, Friday, 20 November |
| Hackney Anarchist Group | XML | 20:07, Friday, 20 November | 20:56, Friday, 20 November |
| Hackney Solidarity Network | XML | 20:35, Friday, 20 November | 21:20, Friday, 20 November |
| http://blog.llvm.org/feeds/posts/default | XML | 20:35, Friday, 20 November | 21:20, Friday, 20 November |
| http://calendar.google.com/calendar/feeds/q7s5o02sj8hcam52hutbcofoo4%40group.calendar.google.com/public/basic | XML | 20:35, Friday, 20 November | 21:15, Friday, 20 November |
| http://dynamic.boingboing.net/cgi-bin/mt/mt-cp.cgi?__mode=feed&_type=posts&blog_id=1&id=1 | XML | 20:35, Friday, 20 November | 21:20, Friday, 20 November |
| http://eng.anarchoblogs.org/feed/atom/ | XML | 20:14, Friday, 20 November | 21:00, Friday, 20 November |
| http://feed43.com/3874015735218037.xml | XML | 20:14, Friday, 20 November | 21:00, Friday, 20 November |
| http://flatearthnews.net/flatearthnews.net/blogfeed | XML | 20:42, Friday, 20 November | 21:23, Friday, 20 November |
| http://fulltextrssfeed.com/ | XML | 20:35, Friday, 20 November | 21:18, Friday, 20 November |
| http://london.indymedia.org/articles.rss | XML | 20:28, Friday, 20 November | 21:15, Friday, 20 November |
| http://pipes.yahoo.com/pipes/pipe.run?_id=ad0530218c055aa302f7e0e84d5d6515&_render=rss | XML | 20:14, Friday, 20 November | 21:00, Friday, 20 November |
| http://planet.gridpp.ac.uk/atom.xml | XML | 20:28, Friday, 20 November | 21:15, Friday, 20 November |
| http://shirky.com/weblog/feed/atom/ | XML | 20:35, Friday, 20 November | 21:19, Friday, 20 November |
| http://thecommune.co.uk/feed/ | XML | 20:35, Friday, 20 November | 21:20, Friday, 20 November |
| http://theness.com/roguesgallery/feed/ | XML | 20:28, Friday, 20 November | 21:16, Friday, 20 November |
| http://www.airshipentertainment.com/buck/buckcomic/buck.rss | XML | 20:07, Friday, 20 November | 20:56, Friday, 20 November |
| http://www.airshipentertainment.com/growf/growfcomic/growf.rss | XML | 20:35, Friday, 20 November | 21:19, Friday, 20 November |
| http://www.airshipentertainment.com/myth/mythcomic/myth.rss | XML | 20:56, Friday, 20 November | 21:38, Friday, 20 November |
| http://www.godhatesastronauts.com/feed/ | XML | 20:28, Friday, 20 November | 21:16, Friday, 20 November |
| http://www.tinycat.co.uk/feed/ | XML | 20:35, Friday, 20 November | 21:15, Friday, 20 November |
| https://anarchism.pageabode.com/blogs/anarcho/feed/ | XML | 20:35, Friday, 20 November | 21:19, Friday, 20 November |
| https://broodhollow.krisstraub.comfeed/ | XML | 20:42, Friday, 20 November | 21:23, Friday, 20 November |
| https://debian-administration.org/atom.xml | XML | 20:42, Friday, 20 November | 21:23, Friday, 20 November |
| https://elitetheatre.org/ | XML | 20:28, Friday, 20 November | 21:15, Friday, 20 November |
| https://feeds.feedburner.com/Starslip | XML | 20:56, Friday, 20 November | 21:38, Friday, 20 November |
| https://feeds2.feedburner.com/GeekEtiquette?format=xml | XML | 20:35, Friday, 20 November | 21:18, Friday, 20 November |
| https://feedsapi.com/makefulltextfeed.php?url=http%3A%2F%2Fwww.somethingpositive.net%2Fsp.xml&what=auto&key=&max=7&links=preserve&exc=&privacy=I+accept | XML | 20:35, Friday, 20 November | 21:19, Friday, 20 November |
| https://hackbloc.org/rss.xml | XML | 20:42, Friday, 20 November | 21:23, Friday, 20 November |
| https://kajafoglio.livejournal.com/data/atom/ | XML | 20:07, Friday, 20 November | 20:56, Friday, 20 November |
| https://philfoglio.livejournal.com/data/atom/ | XML | 20:28, Friday, 20 November | 21:15, Friday, 20 November |
| https://pixietrixcomix.com/eerie-cutiescomic.rss | XML | 20:28, Friday, 20 November | 21:15, Friday, 20 November |
| https://pixietrixcomix.com/menage-a-3/comic.rss | XML | 20:35, Friday, 20 November | 21:19, Friday, 20 November |
| https://propertyistheft.wordpress.com/feed/ | XML | 20:35, Friday, 20 November | 21:15, Friday, 20 November |
| https://requiem.seraph-inn.com/updates.rss | XML | 20:35, Friday, 20 November | 21:15, Friday, 20 November |
| https://studiofoglio.livejournal.com/data/atom/ | XML | 20:14, Friday, 20 November | 21:00, Friday, 20 November |
| https://thecommandline.net/feed/ | XML | 20:14, Friday, 20 November | 21:00, Friday, 20 November |
| https://torrentfreak.com/subscriptions/ | XML | 20:35, Friday, 20 November | 21:18, Friday, 20 November |
| https://web.randi.org/?format=feed&type=rss | XML | 20:35, Friday, 20 November | 21:18, Friday, 20 November |
| https://www.baen.com/baenebooks | XML | 20:35, Friday, 20 November | 21:19, Friday, 20 November |
| https://www.dcscience.net/feed/medium.co | XML | 20:07, Friday, 20 November | 20:56, Friday, 20 November |
| https://www.DropCatch.com/domain/steampunkmagazine.com | XML | 20:42, Friday, 20 November | 21:23, Friday, 20 November |
| https://www.DropCatch.com/domain/ubuntuweblogs.org | XML | 20:14, Friday, 20 November | 21:00, Friday, 20 November |
| https://www.DropCatch.com/redirect/?domain=DyingAlone.net | XML | 20:28, Friday, 20 November | 21:15, Friday, 20 November |
| https://www.freedompress.org.uk:443/news/feed/ | XML | 20:28, Friday, 20 November | 21:16, Friday, 20 November |
| https://www.goblinscomic.com/category/comics/feed/ | XML | 20:35, Friday, 20 November | 21:15, Friday, 20 November |
| https://www.loomio.com/blog/feed/ | XML | 20:14, Friday, 20 November | 21:00, Friday, 20 November |
| https://www.newstatesman.com/feeds/blogs/laurie-penny.rss | XML | 20:42, Friday, 20 November | 21:23, Friday, 20 November |
| https://www.patreon.com/graveyardgreg/posts/comic.rss | XML | 20:28, Friday, 20 November | 21:15, Friday, 20 November |
| https://www.rightmove.co.uk/rss/property-for-sale/find.html?locationIdentifier=REGION^876&maxPrice=240000&minBedrooms=2&displayPropertyType=houses&oldDisplayPropertyType=houses&primaryDisplayPropertyType=houses&oldPrimaryDisplayPropertyType=houses&numberOfPropertiesPerPage=24 | XML | 20:35, Friday, 20 November | 21:18, Friday, 20 November |
| https://x.com/statuses/user_timeline/22724360.rss | XML | 20:35, Friday, 20 November | 21:15, Friday, 20 November |
| Humble Bundle Blog | XML | 20:28, Friday, 20 November | 21:15, Friday, 20 November |
| I, Cringely | XML | 20:28, Friday, 20 November | 21:16, Friday, 20 November |
| Irregular Webcomic! | XML | 20:42, Friday, 20 November | 21:23, Friday, 20 November |
| Joel on Software | XML | 20:14, Friday, 20 November | 21:00, Friday, 20 November |
| Judith Proctor's Journal | XML | 20:35, Friday, 20 November | 21:15, Friday, 20 November |
| Krebs on Security | XML | 20:42, Friday, 20 November | 21:23, Friday, 20 November |
| Lambda the Ultimate - Programming Languages Weblog | XML | 20:35, Friday, 20 November | 21:15, Friday, 20 November |
| Looking For Group | XML | 20:35, Friday, 20 November | 21:19, Friday, 20 November |
| LWN.net | XML | 20:42, Friday, 20 November | 21:23, Friday, 20 November |
| Mimi and Eunice | XML | 20:35, Friday, 20 November | 21:20, Friday, 20 November |
| Neil Gaiman's Journal | XML | 20:35, Friday, 20 November | 21:15, Friday, 20 November |
| Nina Paley | XML | 20:28, Friday, 20 November | 21:15, Friday, 20 November |
| O Abnormal – Scifi/Fantasy Artist | XML | 20:35, Friday, 20 November | 21:20, Friday, 20 November |
| Oglaf! -- Comics. Often dirty. | XML | 20:28, Friday, 20 November | 21:16, Friday, 20 November |
| Oh Joy Sex Toy | XML | 20:35, Friday, 20 November | 21:19, Friday, 20 November |
| Order of the Stick | XML | 20:35, Friday, 20 November | 21:19, Friday, 20 November |
| Original Fiction Archives - Reactor | XML | 20:56, Friday, 20 November | 21:38, Friday, 20 November |
| OSnews | XML | 20:35, Friday, 20 November | 21:20, Friday, 20 November |
| Paul Graham: Unofficial RSS Feed | XML | 20:35, Friday, 20 November | 21:20, Friday, 20 November |
| Penny Arcade | XML | 20:56, Friday, 20 November | 21:38, Friday, 20 November |
| Penny Red | XML | 20:35, Friday, 20 November | 21:20, Friday, 20 November |
| PHD Comics | XML | 20:07, Friday, 20 November | 20:56, Friday, 20 November |
| Phil's blog | XML | 20:28, Friday, 20 November | 21:16, Friday, 20 November |
| Planet Debian | XML | 20:35, Friday, 20 November | 21:20, Friday, 20 November |
| Planet GNU | XML | 20:42, Friday, 20 November | 21:23, Friday, 20 November |
| Planet Lisp | XML | 20:07, Friday, 20 November | 20:56, Friday, 20 November |
| Pluralistic: Daily links from Cory Doctorow | XML | 20:35, Friday, 20 November | 21:15, Friday, 20 November |
| PS238 by Aaron Williams | XML | 20:28, Friday, 20 November | 21:16, Friday, 20 November |
| QC RSS v2 | XML | 20:28, Friday, 20 November | 21:15, Friday, 20 November |
| Radar | XML | 20:56, Friday, 20 November | 21:38, Friday, 20 November |
| RevK®'s ramblings | XML | 20:14, Friday, 20 November | 21:00, Friday, 20 November |
| Richard Stallman's Political Notes | XML | 20:07, Friday, 20 November | 20:56, Friday, 20 November |
| Scenes From A Multiverse | XML | 20:28, Friday, 20 November | 21:15, Friday, 20 November |
| Schneier on Security | XML | 20:35, Friday, 20 November | 21:15, Friday, 20 November |
| SCHNEWS.ORG.UK | XML | 20:35, Friday, 20 November | 21:19, Friday, 20 November |
| Scripting News | XML | 20:56, Friday, 20 November | 21:38, Friday, 20 November |
| Seth's Blog | XML | 20:14, Friday, 20 November | 21:00, Friday, 20 November |
| Skin Horse | XML | 20:56, Friday, 20 November | 21:38, Friday, 20 November |
| Tales From the Riverbank | XML | 20:07, Friday, 20 November | 20:56, Friday, 20 November |
| The Adventures of Dr. McNinja | XML | 20:35, Friday, 20 November | 21:20, Friday, 20 November |
| The Bumpycat sat on the mat | XML | 20:35, Friday, 20 November | 21:15, Friday, 20 November |
| The Daily WTF | XML | 20:14, Friday, 20 November | 21:00, Friday, 20 November |
| The Monochrome Mob | XML | 20:42, Friday, 20 November | 21:23, Friday, 20 November |
| The Non-Adventures of Wonderella | XML | 20:35, Friday, 20 November | 21:18, Friday, 20 November |
| The Old New Thing | XML | 20:35, Friday, 20 November | 21:19, Friday, 20 November |
| The Open Source Grid Engine Blog | XML | 20:28, Friday, 20 November | 21:15, Friday, 20 November |
| The Stranger | XML | 20:35, Friday, 20 November | 21:20, Friday, 20 November |
| towerhamletsalarm | XML | 20:14, Friday, 20 November | 21:00, Friday, 20 November |
| Twokinds | XML | 20:56, Friday, 20 November | 21:38, Friday, 20 November |
| UK Indymedia Features | XML | 20:56, Friday, 20 November | 21:38, Friday, 20 November |
| Uploads from ne11y | XML | 20:14, Friday, 20 November | 21:00, Friday, 20 November |
| Uploads from piasladic | XML | 20:35, Friday, 20 November | 21:18, Friday, 20 November |
| Use Sword on Monster | XML | 20:28, Friday, 20 November | 21:15, Friday, 20 November |
| Wayward Sons: Legends - Sci-Fi Full Page Webcomic - Updates Daily | XML | 20:14, Friday, 20 November | 21:00, Friday, 20 November |
| what if? | XML | 20:42, Friday, 20 November | 21:23, Friday, 20 November |
| Whatever | XML | 20:07, Friday, 20 November | 20:56, Friday, 20 November |
| Whitechapel Anarchist Group | XML | 20:07, Friday, 20 November | 20:56, Friday, 20 November |
| WIL WHEATON dot NET | XML | 20:35, Friday, 20 November | 21:19, Friday, 20 November |
| wish | XML | 20:35, Friday, 20 November | 21:20, Friday, 20 November |
| Writing the Bright Fantastic | XML | 20:35, Friday, 20 November | 21:19, Friday, 20 November |
| xkcd.com | XML | 20:35, Friday, 20 November | 21:18, Friday, 20 November |