If you are running a business built on books, or hope to, direct-to-consumer sales need to be a part of your strategy. Direct sales (along with print-on-demand) have exploded in popularity, and for good reason.
“What are those reasons!?” I hear you asking.
Well, they are myriad. You may decide to sell direct because you want more control over the customer journey. Or maybe you want to get paid faster for your book sales. Or maybe you want the opportunity to collect customer data so you can see who’s buying your books and actually start building your business. These are all great reasons, but the benefits go beyond that. Incorporating direct sales into your book business allows you to create an infrastructure that scales with you as your audience and business grow.
There are a few different ways you can introduce direct sales into your workflow:
Sell at in-person events - this provides a great opportunity to meet your readers, get feedback, and create unique experiences with book signings and other activations.
Hand-fulfill orders through your website - as orders come in through your website, you manually pack and ship each one. This is time-consuming, but can also create opportunities for you to delight your readers by adding in handwritten notes, bookmarks, stickers, and other freebies.
Integrate with a POD + Dropshipping provider - that would be us. There are others, but you didn’t come to the Lulu blog to hear about them. Lulu has several ways for you to take advantage of direct sales:
Lulu Direct - integrate your Shopify, Wix, or WooCommerce website with our global printing and fulfillment network, so when orders come in through your website, we take care of the order fulfillment. Perfect for anyone who wants to white-label their book business and collect data on who actually buys their books.
Buy Button - if you don’t have a website, create a button, link, or QR code to sell books directly from your newsletter, social media profiles, email campaigns, business cards, or collateral. Perfect for creators who don’t have a website yet but want to sell directly and boost conversion rates.
Order Import Tool - place multiple orders with one simple upload. Perfect for large orders containing multiple projects and customers, crowdfunding campaigns, and pre-orders.
Best of all, no matter which option you choose, you never have to worry about shipping or inventory! So you can focus on other things, like growing your business.
There are, of course, many questions you might have about direct sales and how they actually work. And I’m here to answer them for you. Here are some of the most commonly asked questions about selling direct with Lulu.
What Is Lulu Direct?
A good place to start! When you publish a book using Lulu Direct, your customers will buy directly from you. Lulu will handle printing and shipping the book to your customer while you pay Lulu for printing and shipping costs. These costs can be passed on to your customer in your retail price and shipping options.
Lulu Direct connects Lulu's global print-on-demand services to your website using popular ecommerce platforms like Shopify, Wix, or WooCommerce. It also includes access to the Order Import tool for shipping orders to a variety of customers, and the Direct Buy Button for fast, easy embedded checkout.
What Products Can I Print and Sell Through Lulu Direct?
All of them! You'll have access to all 3,000+ print book and calendar format combinations Lulu offers and the freedom to design your interior and cover PDFs.
You can build a diverse catalog by offering multiple products for sale. Each product can include variants such as hardcover, softcover, or magazine formats, all fulfilled automatically and shipped to your buyers globally.
See Lulu’s product specifications to find all of your binding, size, ink, and finish options.
Please note: ebooks are not eligible for Lulu Direct at this time.
Why Should I Use Lulu Direct?
I’m glad you asked. Lulu Direct connects Lulu’s print-on-demand and fulfillment to your website. Using Lulu Direct brings several benefits to your content business, including:
Retain 100% of your revenue
White-label shipping for all orders
Collect customer data
Fully automated sales, printing, and shipping
Support for multiple product variants
Bulk ordering with the Order Import tool
Faster payouts
If you know your audience and want to grow your bookselling business, Lulu Direct is the perfect way to build strong customer relationships while scaling your brand.
When you use Lulu Direct to sell your book, customers buy from you directly. You control the price and know exactly how much you'll earn from every sale. With white-label receipts, your customers only see you and your brand when they order your book.
Direct sales are a great addition to any marketing strategy, and Lulu Direct makes it easy for you to automate the manual aspects while getting actionable insights about your customers and business. Getting clarity on who’s actually buying your books creates opportunities for growth, connection, and community. You don’t need a third-party retailer to have a successful book-selling business. You just need the infrastructure that allows you to act like one yourself.
Your Free Lulu Account
Create a free Lulu account today to self-publish your book and have your book printed for you, a friend, or readers all over the world.
Pete Hegseth and Trump got a dubious win today: a 2-1 panel of the DC Circuit found that the designation of Anthropic as a supply chain risk was not unlawful. It dismissed Anthropic’s challenge despite (1) a different court having found the exact opposite not that long ago; (2) being predicated on a statutory interpretation of “supply chain risk” that would effectively deem most AI models, and potentially all software, a supply chain risk; (3) having made this designation selectively and punitively; and (4) it resulting in Anthropic being disqualified from selling its model to any government agency, including those without same concern the DC Circuit credited the military with having.
To some extent the difference in the two decisions can be explained by the two different statutes at issue. Hegseth claimed the authority to make “supply chain risk” designations under two separate ones, 10 U.S.C. § 3252, which was at issue in the California challenge, and 41 U.S.C. § 4713, which was at issue in this case. Congress is also partly to blame for this mess, because in writing the statutory definition for “supply chain risk” in the 4713 statute it created more space for dubious interpretations like this one (“Whatever paradigmatic examples individual members of Congress may have had in mind, the statutory definition is not limited to “adversar[ies],” 10 U.S.C. § 3252(d)(4), and instead covers “any person,” which cannot refer only to foreign entities, 41 U.S.C. § 4713(k)(6).”). The statute also constrained how such designations could be challenged, sending them all directly to the DC Circuit, rather than a district court, which is why Anthropic’s challenge of the Hegseth action ended up in two separate cases.
But a bizarre situation has still resulted where one court has said that Anthropic’s First Amendment and due process rights had been violated, and another has now said they weren’t, even though the same action was involved with both. Anthropic argued that the California district court’s earlier decision should have been controlling, but the DC Circuit disagreed:
Anthropic contends that the Northern District’s decision is preclusive as well as persuasive. But because the Department’s designation authority is much broader under section 4713 than it is under section 3252, the issues flagged by Anthropic are not the same in both cases. So, for example, the Northern District’s determination that the section 3252 designation was arbitrary does not control our determination whether the section 4713 designation was arbitrary. Likewise, the Northern District’s determination of exigency under section 3252 does not control our determination of exigency under section 4713. In any event, Congress gave this Court exclusive jurisdiction to review procurement actions taken pursuant to section 4713 designations, see 41 U.S.C. § 1327(b)(1), and it specifically barred other courts from reviewing any other “action taken under” section 4713, see id. § 1327(a). That strict “allocation of jurisdiction” to this Court makes it inappropriate to constrain our review based on the Northern District’s judgment. Restatement (Second) of Judgments § 28 (1982); see Shaw v. State of Cal. Dep’t of Alcoholic Beverage Control, 788 F.2d 600, 607–09 (9th Cir. 1986); Lyons v. Westinghouse Elec. Corp., 222 F.2d 184, 188–89 (2d Cir. 1955) (L. Hand, J.).
Instead, because the DC Circuit read the statutory authority Hegseth drew from differently, apparently given its textual differences, it found Hegseth entitled to take the action that he did. But it is a dubious reading that would have broad implications the court did not address. In short, because Anthropic would still have control over its model, the court found that it could be considered to have the power to “manipulate” it, even after being deployed in government, and that made it a supply chain risk.
The Secretary reasonably concluded that removing Anthropic from the Department’s supply chain was necessary to protect national security by reducing supply chain risk to the Department’s information systems. Specifically, the Secretary credited a joint recommendation from two senior Department officials that Claude might be “subject to manipulation” by Anthropic “in such a manner as to inhibit the DoW’s use thereof.” App. 178. Likewise, he credited Under Secretary Michael’s conclusion that Anthropic might “manipulat[e]” the “design, integrity, and operation” of the Department’s Claude models, potentially causing “critical defense system[s] failing to engage” as intended by the Department. Id. at 182.
The record in this case amply supports the Secretary’s conclusion. To begin, it is undisputed that Anthropic can and does control how Claude responds—or fails to respond—to user prompts. Anthropic’s Chief Science Officer explained how the company “seek[s] to embed safety considerations directly into the model itself.” App. 8. Its CEO explained how such training gives the model an “identity, character, values, and personality” of its own, tethered to a “constitution” developed to impose “high-level principles and values” on Claude itself. Id. at 93–94. And the head of its public-sector business explained: “Model training is the primary mechanism through which Anthropic can influence the behavior of models used by the Department.” Id. at 276. Anthropic disclaims any ability to access or alter a model that has already been delivered to the Department, see id., despite the “technical measures” that it uses to police compliance with usage restrictions by private customers, id. at 8. Nonetheless, extant models reflect Claude’s “[c]onstitutional” training. Id. at 274–75. Moreover, Anthropic may encode additional restrictions each time it delivers any “new version of the model” to Department contractors. Id. at 276. Finally, it is undisputed that such model restrictions are vitally important to Anthropic, which describes them as lying “at the core of [its] mission.” Id. at 2.
The record also indicates that Anthropic’s model training is effective in enforcing usage restrictions and that, as a result, Claude has refused to answer legitimate queries from government users. Anthropic itself explained how early, commercially available versions of Claude frustrated Department and intelligence-community users by refusing prompts to evaluate classified materials. App. 255. Likewise, as Under Secretary Michael explained, the Department learned in 2025 that Claude had refused to process CDC prompts to support research to prevent the spread of infectious diseases. Id. at 212. Anthropic responds that these glitches reflected safety features appropriately built into models sold to private companies and were resolved after Anthropic engineers worked with the relevant government stakeholders. Id. at 255–56, 261–62. Perhaps so, but the point here is not that these model or usage restrictions were arbitrary; instead, it is that Anthropic’s model training does effectively enforce contractual usage restrictions.
Finally, the record reveals a recent, serious dispute about the scope of the contractual prohibitions on lethal autonomous warfare and mass domestic surveillance. Under Secretary Michael describes the incident in general but striking terms: [O]ne of Anthropic’s executives questioned the propriety of the potential use of their software for a sensitive military operation abroad despite that use being permitted under the existing Terms of Service. This led to alarm by the DoW and the prime contractor who provides Anthropic software, and raised material doubts as to whether they would cause their software to stop working or cause some other disastrous action that would put our warfighters[’] lives in danger. App. 181. Anthropic does not say much about this incident, except to suggest that it reflected a misunderstanding. Id. at 236–37. But regardless, Anthropic has made clear that it views the contractual prohibition on mass domestic surveillance as urgent to support “democratic values,” id. at 146, and the contractual prohibition on lethal autonomous warfare as urgent to avoid “put[ting] America’s warfighters and civilians at risk” of a catastrophic AI mistake, id. at 147. For its part, the Department has made clear that it views an “any lawful use” authorization to be critical to its “AI-first” strategic plan. Id. at 202, 206. With such diametrically opposed positions and with contractual limitations that are hardly self-defining, the prospect for disputes is apparent.
In sum, the Department reasonably feared that Anthropic might manipulate Claude’s design to prevent it from performing national-security functions that the Department deems contractually authorized and necessary.
The nightmare hypo that the court credited was what if the military had some sensitive plans that depended on Claude’s use, which Anthropic then changed on the fly, which jeopardized the mission. But there are multiple problems with the court’s acceptance of the government’s argument here.
For one, if the court’s statutory interpretation about the power to affect the operation of delivered software were correct, then pretty much any software product, at least those still subject to vendor-supplied updates, could be considered supply chain risks, given that any update could make substantive changes. In any case, it would seem to mean that any AI model would be too risky for the government to use, because there is nothing unusual about Anthropic’s model-control architecture—to the extent Anthropic could still control its model, so could any other AI vendor potentially control theirs. Whether they would or not would depend on the contract restraining them, and the only thing potentially different about Anthropic is that it did not want to be contractually obligated to allow certain functions that Hegseth really wanted—functions that were ethically dubious at best and monstrously dangerous at worst.
But because that contractual reluctance upset Trump and Hegseth, they singled Anthropic out, alone, for negative treatment, turning their pique that “we can’t agree with Anthropic on how the software would need to be designed for us to be able to buy it” into “and because we can’t agree then NO ONE ELSE IN THE GOVERNMENT CAN EVER USE IT.” Per the DC Circuit, such an overbroad measure—after all, not every agency had the same concerns about changeability that the military might, yet Hegseth was deciding for them, too, whether they could use Claude, even when its architecture created no particular risk to them—and clearly punitive measure was perfectly fine because it implicated the implicit “national security” exception to the First Amendment the Founders apparently wrote into it in invisible ink.
To succeed on such a First Amendment retaliation claim, the plaintiff or petitioner must prove that (1) it engaged in protected speech, (2) the government took materially adverse action against it, and (3) the speech caused the materially adverse action. See Houston Cmty. Coll. Sys. v. Wilson, 595 U.S. 468, 477–79 (2022); Aref v. Lynch, 833 F.3d 242, 258 (D.C. Cir. 2016). Anthropic has satisfied the first and second prongs of this test, but not the third. The First Amendment squarely protects Anthropic’s advocacy regarding the safe and appropriate use of AI products. Moreover, the Department’s exclusion of Claude from its supply chain plainly qualifies as a materially adverse action. However, we can discern no causal connection between the two. Instead, the record makes clear that the Department removed Anthropic from its supply chain not because of its advocacy, but because Anthropic refused to agree to a contract term the Department deemed essential to national security.
Because Anthropic wouldn’t do the deal Hegseth wanted to do, he was therefore entitled to declare it too risky for anyone in the government to use, without it being seen as punishing Anthropic for its disinclination.
Anthropic points to various pungent statements in the Secretary’s February 27 social media post. Among other things, the Secretary denounced Anthropic’s “sanctimonious rhetoric,” “virtue-signaling,” and “Silicon Valley ideology.” App. 77. Such rhetoric seldom provides a sound basis for judging the lawfulness of federal executive action. See, e.g., Mullin v. Doe, 146 S. Ct. 2121, 2139 (2026); Trump v. Hawaii, 585 U.S. at 700–02. In any event, for all its flourishes, the Secretary’s social media post squarely addresses Anthropic’s refusal to provide the “all lawful uses” contractual authorization. He described Anthropic’s behavior as a “textbook case of how not to do business” with the Pentagon. App. 77 (emphasis added). He reiterated the Department’s demand for “full, unrestricted access to Anthropic’s models for every lawful purpose in defense of the Republic.” Id. (cleaned up). And he characterized Anthropic’s refusal to provide that access as imposing an unacceptable “veto power over the operational decisions of the United States military.” Id. The nub of this dispute was contractual, and the First Amendment did not require the Department to continue a contractual relationship that it viewed as creating a national-security risk.
Per the DC Circuit panel, the First Amendment takes a backseat to the President and his Secretary’s determination that a technology can ever be used by the government, no matter what.
This case raises profoundly difficult questions about the appropriate military uses of an almost unimaginably powerful new technology. The Secretary raises the deeply sobering prospect of overly constrained AI models shutting down unexpectedly and thus causing important military operations to fail. Anthropic raises the deeply sobering prospect of unconstrained AI models hallucinating inappropriate targets for lethal military force. Both possibilities present obvious national-security concerns. But in our Republic, it is the President and the Secretary of War who must determine how best to balance the competing risks. In doing so here, the Secretary did not transgress any limits on his authority under the Supply Chain Security Act or the Constitution. Accordingly, we deny the petitions for review.
Which cannot possibly be right if the Bill of Rights is to have any meaning in limiting government power, and especially not on a record like this. Yet here we are.
The Metric Is Not the Mission is a ten-part examination of how Big Tech moved from building and expanding the open internet to increasingly shaping it around its own metrics, incentives and assumptions. Across the series, the argument follows the evolution of the platform economy—from the optimism of the early internet to the growing tensions around power, prediction, geopolitics, accountability and the future of digital life.
The series will be published in two parts each week over five weeks, with each installment building on the one before it. At the end of the series, the complete essay will be brought together in a single PDF edition, providing the full argument in one place.
Part II — When They Still Understood Us
Part I looked at the slow transformation taking place beneath the daily controversies surrounding Big Tech. This second part goes back to the beginning, asking what these companies originally understood about people and how the metrics that once measured their success gradually became the definition of it.
It has become fashionable to tell the story of Big Tech as though it were always destined to end here. In retrospect, it is easy to portray the rise of the major platforms as the inescapable march of surveillance capitalism, monopolistic ambition, and unchecked technological power. That narrative is emotionally satisfying because it offers clear villains and a comforting sense of inevitability. It also happens to be incomplete.
Cory Doctorow has given this deterioration a memorable name: “enshittification.” His argument is that platforms initially serve users well, then, once users and business customers are locked in, progressively shift value away from both toward shareholders, degrading the service in the process. It is a powerful account of how platforms become extractive. But it is not quite the argument here. The deeper problem is not simply that Big Tech has learned to extract more from us but that it has become increasingly convinced that because it can measure and predict our behavior, it understands us and, by extension, the societies it has come to mediate. The failure is therefore not only economic; it is also epistemic. The metric has become a substitute for the mission.
One cannot understand why these companies now appear increasingly disconnected from the societies they helped shape without first acknowledging that, for a remarkably long time, they understood those societies exceptionally well.
Technology succeeds when it solves technical problems. It changes the world when it solves human ones.
That was the genius of the first generation of internet platforms. Their founders did not invent friendship, curiosity, creativity or community. They simply recognized that the internet had reached a stage where these deeply human instincts required new forms of expression. The web of the late 1990s was exhilarating, but it was also fragmented, uneven and, for many people, intimidating. Finding information often required patience. Discovering interesting websites depended on chance as much as design. Publishing demanded a degree of technical literacy that excluded far more people than it empowered. The internet was open, but openness alone does not necessarily produce accessibility.
The great platforms emerged not because they sought to replace the internet but because they made it intelligible. Google transformed an expanding wilderness of information into something navigable. Wikipedia demonstrated that knowledge could be organized through collaboration rather than hierarchy. YouTube lowered the barriers to publishing so dramatically that expertise escaped universities, broadcasters and production studios. Facebook addressed an even more fundamental challenge. It recognized that the internet was no longer simply about information; it had become about people. Until then, maintaining relationships online had been surprisingly cumbersome. Email was too formal, instant messaging too ephemeral, personal websites too static. Facebook reduced social interaction to something almost frictionless. Its success lay not in technological sophistication but in psychological intuition.
This is easy to forget because the platforms that dominate our lives today bear only a partial resemblance to the ones that first captured our imagination. Facebook did not begin as an endless stream of algorithmically selected content. It was, in essence, a digital address book enriched by photographs, conversations, and the ordinary rituals of everyday life. It became valuable because it mirrored existing relationships rather than attempting to manufacture new ones. There was comfort in discovering former classmates, following the lives of distant relatives, or organizing gatherings that would otherwise have required dozens of emails and phone calls. The platform expanded social life without yet attempting to redefine it.
YouTube offered a similarly modest promise. It was not originally designed to maximize engagement or optimize watch time. It functioned more like an immense public archive whose value derived from its unpredictability. One could arrive searching for a lecture on astronomy and leave having discovered a forgotten jazz performance, a documentary on Greek history, or a repair manual for a washing machine. Recommendation existed, but it remained subordinate to curiosity. Users still felt as though they were exploring rather than being guided.
Even Twitter (now X), before it became a battleground for politics, culture wars, and performative outrage, captured something important about the changing nature of public conversation. It collapsed distance between journalists, academics, politicians, and ordinary citizens in ways that would have seemed extraordinary only a few years earlier. For all its imperfections, it suggested that expertise and authority might become more accessible rather than less.
Looking back, what united these companies was not simply technological innovation but a particular philosophy of the internet. They assumed that openness generated value. The more people connected, the richer the network became. Every new participant increased the possibilities for everyone else. Economists describe this as a network effect, but the phrase barely captures its cultural significance. Participation itself became the source of optimism. The internet appeared to be validating one of the oldest liberal ideas: that societies flourish when individuals are free to exchange ideas, collaborate voluntarily, and build institutions from the bottom up.
It is difficult to overstate how persuasive this vision became. Most governments celebrated the digital economy as an engine of innovation. Investors poured unprecedented sums into technology because the opportunities seemed limitless. Civil society organizations embraced online platforms as tools for democratic participation and global advocacy. Even critics of globalization often regarded the internet as an exception, a domain where openness appeared to distribute power rather than concentrate it.
For a brief historical moment, these interests aligned. What was good for technology companies often appeared to be good for users, for markets, and, in many respects, for the internet itself. The incentives reinforced one another. Companies grew by making the network more useful. Users benefited from larger communities. Developers built new services on open standards. The web expanded because success depended on drawing people further into its richness rather than confining them within a single destination.
History, however, has an inconvenient habit of changing the problems that institutions are asked to solve. The sociologist Robert K. Merton once observed that organizations often become prisoners of their own success. Practices that were rational under one set of conditions gradually harden into routines, and routines into orthodoxies. Institutions continue refining the solutions that once made them indispensable even as the environment around them evolves. Success breeds confidence; confidence breeds certainty; certainty eventually makes adaptation more difficult than persistence.
There is no reason to believe technology companies are exempt from this pattern. If anything, their extraordinary success may have accelerated it.
The platforms that once competed to help users navigate an open internet eventually found themselves managing ecosystems of unprecedented scale. Their priorities changed almost imperceptibly. The models they developed during the internet’s age of expansion proved astonishingly effective at connecting people, organizing information, and lowering the costs of participation. The metrics through which they evaluated success, such as growth, engagement, scale, and network effects, were not arbitrary inventions of venture capital. They reflected a period during which connecting more people genuinely created more value for everyone involved. The problem is that the world changed while the metrics remained stable. A measure that once indicated success gradually became the definition of success itself.
There is an obvious parallel here with Goodhart’s Law: when a measure becomes a target, it ceases to be a good measure. The principle, first articulated by economist Charles Goodhart in the context of monetary policy, describes what happens when an indicator that works as a proxy for an underlying objective is turned into the objective itself. But the problem here is slightly different. The issue is not simply that platforms began gaming their metrics, or that users learned to optimize for them. It is that the metrics gradually became so deeply embedded in the companies’ understanding of success that the distinction between the measure and the mission was lost. The metric did not merely distort the objective; it quietly became the objective.
None of this happened because a group of executives gathered in a boardroom and decided to undermine the open internet. Institutional change is rarely so theatrical. More often, it emerges from countless rational decisions made in pursuit of perfectly reasonable objectives: improve the user experience, reduce friction, personalize recommendations, increase safety, remove inconvenience. Each adjustment appears modest in isolation but collectively they alter the character of the system itself.
This is where history becomes quietly ironic. The companies that had once understood the internet better than anyone else slowly began to forget what had made the internet exceptional in the first place. They continued to believe they were connecting the world, even as they increasingly replaced the world with carefully curated representations of it. They accumulated unprecedented quantities of information about human behavior while becoming progressively less attentive to the human condition.
The distinction is subtle, but it may prove to be the defining story of this technological era. To observe behavior is not the same as understanding experience. A platform can know how long we hesitate before clicking a link, which videos hold our attention for an extra seven seconds, or what sequence of images is most likely to keep us scrolling late into the night. It can infer preferences with astonishing accuracy. It can predict patterns that would have been unimaginable a generation ago. Yet prediction, however sophisticated, remains an impoverished form of understanding. It reveals what people do. It says far less about why they do it, what they fear, what they hope for, or what kind of society they are trying to build together.
That difference, almost invisible at first, is where the story begins to change.
Konstantinos Komaitis, PhD, is a veteran of developing and analysing Internet policy to ensure an open and global Internet.
Our fun links this week include Jev, the super fast new AI classifier, and Persodex, the context layer for your Contacts (PS. hit Ben up if you’re in New York in mid-October).
A ton of attention was paid recently to some offhand statements from OpenAI and Microsoft employees that surfaced in filings in the NY Times’ ongoing case against OpenAI, which has been consolidated into a much larger class action lawsuit. As I argued earlier, that struck me as something of a nothingburger of a story, because it should have no impact on the actual legal questions regarding copyright infringement and fair use. However, on Wednesday evening, OpenAI and Microsoft filed something far more stunning, accusing Susman Godfrey (which represents the plaintiffs in the consolidated case) of effectively end-running basic rules of discovery and evidence by (1) paying for research to supply evidence its clients lacked, (2) hiding from the defendants that it had paid for that research, and (3) sneaking the paid-for research into the case outside the normal expert process.
This filing should be seen as the massive bombshell (if not fraud on the court) that people tried to make out that earlier filing to be. Professor Ed Lee, who runs ChatGPT is Eating the World (which tracks all of the various AI lawsuits), has called this an “explosive motion.” But it’s a little bit complex to understand why, which is why it will not get nearly as much attention as some offhand comments by a Microsoft employee.
To understand why this is such a big deal, we need to take a few steps back to explain. There are a bunch of different cases going on in the US regarding whether or not AI training is “fair use” and therefore not a copyright infringement. There were two important rulings in California last year, one after the other, where one judge (William Alsup) found training to be somewhat obviously fair use, while the other judge (Vince Chhabria) found it to be somewhat obviously not fair use.
As often happens in fair use cases, a lot of time is spent on the “effect on the market” argument, and part of that is whether or not the new works “dilute” the market for earlier works. In the Anthropic case, Alsup didn’t buy the claims of dilution, which is maybe not surprising, since he found training to be fair use. But perhaps more interesting is that in the Meta case, Chhabria — even as he found against fair use — wasn’t persuaded about the “dilution” argument:
As for the potentially winning argument—that Meta has copied their works to create a product that will likely flood the market with similar works, causing market dilution—the plaintiffs barely give this issue lip service, and they present no evidence about how the current or expected outputs from Meta’s models would dilute the market for their own works.
That was a federal judge signalling to potential plaintiffs, if you’re bringing infringement cases like this, maybe find some evidence of dilution?
And… that happened. Earlier this year, a preprint came out on Arxiv seemingly providing evidence on that specific point, claiming that “Generative AI floods and dilutes the market for books” written by four researchers, most notably Jane Ginsburg, who is one of the most famous copyright scholars around (though is also well known as one of the most extreme copyright maximalists, not to mention a general hater on a broad interpretation of fair use). But the lead name on the paper is Tuhin Chakrabarty, a recent PhD. (2024) grad who is now a computer science professor at SUNY Stony Brook. Chakrabarty received his PhD. from Columbia University, where Ginsburg teaches.
A friend had sent me that report when it came out and I found the analysis… perplexing. I had put it on my list of things to write about, but never got to it. Thankfully, Thad McIlroy, who runs “The Future of Publishing” and has been a long term contributing editor at Publishers Weekly, took it upon himself to examine the paper and found it deeply problematic, mainly because they relied on Kindle Unlimited to get copies of the books that they used for the analysis. But as McIlroy points out, that’s distortionary for many reasons regarding how KU works, and suggests that many of the underlying assumptions in the paper simply don’t hold up to scrutiny:
But the author earns income on KU solely on the number of actual pages of their book that are read by a subscriber. Just getting downloaded provides no income. The complex formula is well-described here. There is no method available to estimate the page reads for a book, nor the KU income. Chakrabarty writes, “We measure Kindle Unlimited as whether a title is available on the service, not as how much of it readers actually read. The panel does not tell us whether a given unit is a Kindle Unlimited borrow, a page read allocation, or an ordinary purchase.”
An interesting aspect of KU is that a book’s income there may relate far more closely to quality than it does under royalty systems. If a reader downloads a low-quality AI-generated book on KU, starts to read it, and recognizes the low quality, they will stop reading and move onto another book. The author will earn an insignificant amount of money. On the other hand, if a reader buys the same book, the author receives their full royalty (unless the reader goes to the trouble of returning the book and seeking a refund).
An AI-generated book on KU will only earn significant page revenue if readers find it to be of quality sufficient to match the genre books they are used to reading on the platform.
With these factors in mind, the prevalence of Kindle Unlimited titles in this study appears to be a distorting influence. First, AI-generated books are more likely to appear on Kindle Unlimited than they are more broadly on the Amazon Kindle platform. Second, there is no clear method available to estimate a book’s actual KU income.
Even more bizarre, when McIlroy shared a copy of his critique with Chakrabarty, he was dismissed on moral grounds, because McIlroy has argued for ethical ways to use AI in publishing, which Chakrabarty claims is “morally not okay with me.” That alone should raise some serious red flags about the objectiveness of Chakrabarty in this research. He did not come to this with an open mind. He came bearing a grudge.
A few months earlier, Chakrabarty and Ginsburg (along with Xinyue Liu, who was also an author of the paper above, and who appears to be a first or second year PhD. student working for Charkrabarty) put out another paper called “Alignment Whack-A-Mole: Finetuning Activates Verbatim Recall of Copyrighted Books in Large Language Models.” That piece claimed there was evidence that AI models “store copies of copyrighted works” and even pointed out that this “undermine[s] a key premise of recent fair use rulings.” Indeed, it calls out the Alsup and Chhabria rulings in the paper itself, and effectively notes that they’re responding to the judge’s concerns regarding the effect on the market.
In short, Chakrabarty, Liu, and Ginsburg have been publishing research that attempts to fill in the gaps that multiple judges had called out, and to help plaintiffs argue that training is not fair use. This was especially important because if such evidence was widely available, other plaintiffs would have brought it up. But they have not. Likely because it doesn’t really exist unless you stretch your methodology to its breaking point.
Of course, my biases are known: I’m quite convinced that training AI on copyrighted works is fair use, and I find the argument that slop books “dilute” non-slop books to be beyond nonsensical. Similarly, knowing a little bit (just enough to be dangerous) about how LLM training works, makes it difficult for me to believe that models are, in fact, holding full copies of works they are trained on. That’s just not how they work. But you don’t have to take my word for it. A. Feder Cooper, a well-known computer science professor at Yale who has (somewhat famously) done research on getting LLM’s to spit out “memorized books,” or other full works, had some pretty blunt criticisms of the “whack-a-mole” paper:
As will become clear soon, I think the paper has significant methodological and presentation problems. I’ve spent considerable time reviewing and re-reviewing the paper, and have consulted with two trusted senior colleagues who are experts on memorization to gut-check my reading. And, in brief, I’m confident that Alignment Whack-a-Mole’s headline claims are incorrect. These results rest on aspecific memorization metric and elicitation methodologythat I don’t think hold up to scrutiny, anddon’t support the broad claimsthe paper makes. At best, I think the claims are seriously overstated; at worst, the large majority are wrong. I can’t tell which because the paper doesn’t report enough detail to distinguish the two.
That alone should be concerning, but the media — including the NY Times — really loved to report on these studies, even as their methodology seemed questionable to some experts, and despite the clear potential conflict of interest.
Now, that takes us to the claims in the OpenAI filing from earlier this week: it’s that the plaintiffs’ lawyers at Susman Godfrey secretly paid at least Chakrabarty to do these studies, hid that fact, and then took further steps to launder the studies as non-biased expertise. It appears this wasn’t just a conflict of interest at work, it was a conflict piled upon a conflict, and then potential fraud on the court.
Unable to muster any evidence of harm after years of discovery, Class Plaintiffs’ counsel Susman Godfrey L.L.P. (“Class Counsel” or “Susman”) paid Stony Brook University professor Dr. Tuhin Chakrabarty to research “[h]ow AI generated books dilute the market for human authors.” Declaration of Victor Chiu ISO Motion to Strike (“Chiu Decl.”), Ex. A. Dr. Chakrabarty then coauthored a working, non-peer-reviewed paper purporting to show exactly that (the “Chakrabarty Paper”). The paper was initially self-published on July 22, 2026. Susman had disclosed Dr. Chakrabarty and one of his co-authors as retained experts months earlier—but the resumes Susman provided omitted that Susman had funded Dr. Chakrabarty’s research. Neither Dr. Chakrabarty nor the other disclosed expert ever served an expert report in this case. And after Defendants specifically objected that Dr. Chakrabarty’s resume was incomplete, Susman provided what it represented was an “updated resume” that still omitted Susman’s own funding of his market-dilution research.
Now, some people will point out that it’s not uncommon for companies to pay for research and then use that research elsewhere in ways that are beneficial to them. That’s absolutely true. The problem here isn’t who paid for the research, but the lengths the plaintiffs’ lawyers went to in hiding who paid for it from the court (and from OpenAI and Microsoft)… and how the evidence was laundered into the case long past the normal deadline where it could have been challenged.
Normally, if you bring expert witnesses into a case, the other side gets to challenge their expertise and any research findings that they’re providing. But here, the class plaintiffs’ lawyers took a bunch of steps that at least suggest they deliberately sought to make that effectively impossible with this bit of research. They had named Chakrabarty as a potential witness, providing an incomplete resume for him, but then didn’t use him as such. Instead, they did a kind of evidence two step to get it into the case in a way that would make it harder to challenge:
On July 22, 2026—after the deadlines for all expert reports had passed—Dr. Chakrabarty, Dr. Dhillon, Xinyue Liu, and Professor Jane Ginsburg uploaded to the internet a working paper titled “Generative AI floods and dilutes the market for books.”… They then uploaded two subsequent versions of the paper on July 26, 2026 and August 3, 2026, respectively…. The paper remains identified as a “Working Paper Under Review.” …
The Chakrabarty Paper purports to “measure[] how generative AI” impacts “a real book market once its output reache[s] the catalog and compete[s] for sales.” … Its abstract asserts that the research “bear[s] directly on the market-effect question at the center of the fair use defense to copyright infringement.” … The July 22 and July 26 versions of the Chakrabarty Paper did not disclose that it was funded by Susman and did not make any of its underlying data available. … The August 3 version of the Chakrabarty Paper again did not disclose its funding source. …
[…..]
On Sunday, August 2, 2026, the afternoon before Mr. Lasinski’s deposition, Class Plaintiffs served a supplemental report devoted entirely to the Chakrabarty Paper and which cited the July 26, 2026 version. … At his deposition the next day, Mr. Lasinski testified that he did not analyze any of the data underlying the Chakrabarty Paper…. Mr. Lasinski also testified that he had never spoken with Dr. Chakrabarty or any of his co-authors “about this paper or any other matters related to this litigation.” … When Mr. Lasinski was asked whether he understood that Dr. Chakrabarty and Dr. Dhillon “were retained as experts by Plaintiffs in this matter,” counsel from Susman objected: “I’m not sure why this is appropriate to ask Mr. Lasinski about.” … Mr. Lasinski ultimately testified that he did not “know that this means that [Dr. Chakrabarty and Dr. Dhillon] were retained.”
Mr. Lasinski likewise did not know who had funded the research he was relying upon. When asked whether “the study was funded by Plaintiffs in this case or the Susman Godfrey firm,” Mr. Lasinski testified: “I don’t know the funding sources,” but “to be clear . . . funding something like this would be inconsistent with what I’ve known the Susman Godfrey firm to do.” … Counsel from Susman, who was defending the deposition, did not correct the record or comment on the issue of funding.
Got that? After the deadlines for expert reports were past, the Susman lawyers filed a “supplemental report” from a different expert, Lasinski, which was all about this report that Chakrabarty et al had only just published, effectively getting it into evidence after the deadline passed, and through a non-author of the paper, who had little actual knowledge of the paper’s methodology or data. And, yes, it’s notable that Lasinski said it would be “inconsistent” with what he knew of Susman Godfrey for the firm to fund something like this. Meanwhile, the Susman lawyers in the room objected to questions about whether the paper’s authors were retained experts, and then said nothing at all when Lasinski vouched that the firm wouldn’t fund such research. How… interesting.
There’s also the bit about how the lawyers for OpenAI and Microsoft figure this out:
After Mr. Lasinski’s deposition, OpenAI independently located a substantially similar version of Dr. Chakrabarty’s resume on his website…. Unlike the “updated” resume Susman provided in February, however, the version OpenAI found contains a section specifying $100,000 in “Funding” from Susman in December 2025:
The resume identifies the $100,000 as an “Unrestricted Gift for sponsored research” on “How AI generated books dilutes the market for human authors?”—the same subject covered in the Chakrabarty Paper and in Mr. Lasinski’s supplemental report….
Thus, according to Dr. Chakrabarty’s own resume, Susman’s funding had begun approximately two months before Susman provided Defendants with his supposedly “updated” resume, and the stated subject of that funding was the same market-dilution issue addressed by the Chakrabarty Paper and Mr. Lasinski’s supplemental report. Neither of the resumes Class Plaintiffs provided in February disclosed that the research was sponsored or the source of funding...
That looks bad! This looks worse:
Two days later, on August 27, 2026, Dr. Chakrabarty changed the resume on his public-facing website and removed the reference to Susman’s $100,000 gift. Chiu Decl. ¶ 15, Ex. M. The revised resume now states, in fine print and barely legible font, that “[a] previous version of [Dr. Chakrabarty’s] resume stated that [he] received an unrestricted gift for sponsored research from Susman Godfrey LLP in the amount of $100,000. This was incorrect as the research was done for In re Mosaic LLM litigation for which [his] institution was compensated in a lesser amount:”
Even taken at face value, the revised resume does not deny that Susman funding facilitated the research presented in the Chakrabarty Paper. Whether the money was nominally earmarked for this MDL or the In re Mosaic LLM Litigation case, it supported the same researcher investigating the same market dilution question that is the subject of the Chakrabarty Paper, which in turn is the subject of Mr. Lasinski’s supplemental report.
OpenAI and Microsoft have asked the court to toss the paper entirely, and it’s the plaintiffs’ key evidence on dilution, the exact thing Chhabria said was missing in the Meta case. But also, they point out that this appears to be an attempted fraud on the court.
The Lasinski Supplement is not just late; it instead appears to be a deliberate effort to gain an advantage by evading Rule 26. “It is troublesome, to say the least, for a party to engage a consulting, non-testifying expert; pay for that individual to conduct and publish a study, or otherwise affect or influence the study; engage a testifying expert who relies upon the study; and then cloak the details of the arrangement with the consulting expert . . . in order to conceal it from a party opponent and the Court.” … To make matters worse, Susman appears to have concealed its funding of the Chakrabarty Paper from Class Plaintiffs’ own expert, Mr. Lasinski, despite asking him to rely on it. Dr. Chakrabarty himself was also apparently ignorant of the fact that the tens of thousands of dollars Susman was funneling his way to conduct market-dilution research and publish papers was tied to a specific litigation, much less which one. And Class Plaintiffs have now completed the maneuver: their summary judgment submissions rely extensively on the Chakrabarty Paper and describe it to the Court simply as an “academic stud[y],” without disclosing that their own counsel funded the underlying research.
This maneuver deprived Defendants of the opportunity to fully analyze and rebut the Chakrabarty Paper—and the Court of the ability to properly assess its reliability. Had Class Plaintiffs properly disclosed the Chakrabarty Paper and underlying data and materials, Defendants would have evaluated the data on which the study is based, deposed Dr. Chakrabarty and his co-authors, and tested the study’s methodology and conclusions through the ordinary discovery process. Instead, Defendants were only able to depose Mr. Lasinski, who knew nothing about Dr. Chakrabarty’s underlying data and who mistook the Chakrabarty Paper to reflect neutral, independent research.
Courts recognize that it is “fundamentally unfair” for a party “to supplement the record with reports of alleged ‘consulting experts’”—like Dr. Chakrabarty here—“whose identity and opinions have been shielded [from disclosure].”
The Court also has the inherent authority to preclude the Lasinski Supplement and Chakrabarty Paper to “prevent [Class Plaintiffs] from perpetrating a fraud on the court,” Yukos Capital S.A.R.L. v. Feldman, 977 F.3d 216, 235 (2d Cir. 2020), or interfering with the judicial system’s ability to impartially adjudicate this action. Such interference includes concealing counsel’s role in creating purportedly neutral scientific evidence. See Hazel-Atlas Glass Co. v. Hartford-Empire Co., 322 U.S. 238, 251 (1944) (vacating judgment obtained using an article ghostwritten by counsel but presented as the work of a disinterested expert).
That is what Susman did here. When disclosing Dr. Chakrabarty as an expert, Susman omitted that it funded the research subject of the Chakrabarty Paper, continued to omit that funding even after providing what it represented was an “updated resume,” and allowed Mr. Lasinski to testify at his deposition that Susman would not provide such funding. And even since its funding of the research has come to light, Susman has refused to answer straightforward questions about the nature of its relationship with Dr. Chakrabarty and his co-authors. As Mr. Lasinski himself acknowledges, it would be “inconsistent” for a law firm to fund a study for litigation and then present it through an expert as neutral academic literature.
Once again, the issue isn’t even that the research is sketchy (although… it is). Nor is it that the research was paid for by an interested party (though… it was). The main issue is that the funding appears to have been deliberately hidden from the defendants, and then the sketchy, paid-for research was laundered into the case through a different expert after the deadline for expert reports had passed.
Literally everything about this bit of research — which is a key plank in the anti-fair use argument — comes out of this as suspect.
This Smart & Interactive Self-Rotating Cat Toy Ball is a USB-rechargeable toy featuring 360-degree rolling movements, obstacle avoidance, and changing LED lights to help keep cats entertained. It’s built out of scratch-resistant and bite-resistant materials, the ball is tough enough to withstand rough play from high-energy kittens and adult cats alike. It’s on sale for $20.
Note: The Techdirt Deals Store is powered and curated by StackSocial. A portion of all sales from Techdirt Deals helps support Techdirt. The products featured do not reflect endorsements by our editorial team.
On Monday we wrote about Donald Trump’s direct attack on the First Amendment and the free press by banning reporters from the White House. As we expected, a judge on Thursday morning issued a Temporary Restraining Order, blocking the White House from continuing this unconstitutional action, though (as happened the last time Trump tried this) the court relied on Fifth Amendment due process rather than reaching the First Amendment question.
Plaintiffs are also likely to succeed in showing that their hard passes were revoked without constitutionally adequate due process. The “general rule” is that “individuals must receive notice and an opportunity to be heard before the Government deprives them” of a constitutionally protected interest…. Indeed, the Supreme Court has “described the root requirement of the Due Process Clause as being that an individual be given an opportunity for a hearing before he is deprived of any significant property interest.” Cleveland Bd. of Educ. v. Loudermill, 470 U.S. 532, 542 (1985) (citation omitted). Karem also holds that, because of the substantial interests at stake, before the Government can revoke the White House-issued hard pass of a reporter it must promulgate rules or standards governing the conduct that would lead to such revocation. See 960 F.3d at 665. And the reporter must “receive fair notice not only of the conduct that would subject him to punishment, but also of the magnitude of the sanction that the White House might impose.”
Still, on this record, Defendants offer little to back up their asserted national security interest to justify revocation of Plaintiffs’ hard passes. So this interest does not tilt these factors in their favor, especially given that Plaintiffs have shown a likelihood of success on the merits.
For one thing, nothing in the record that predates this suit suggests that the revocation of Plaintiffs’ hard passes was motivated by national security concerns. Certainly, that is not what President Trump said when he announced that he was “banning” Plaintiffs from the White House—instead, he focused on the alleged lack of truthfulness and negativity of Plaintiffs’ reporting.3 And even the justifications provided to Plaintiffs after this case was filed are ambiguous about the true purpose of the revocations: while Defendants’ letters to Plaintiffs mention national security concerns, they purport to identify reporting that “threatened national security and/or spread falsehoods,” leaving open the possibility that all the stories fall into the later bucket, rather than the former.
Of course, it wouldn’t be the Trump presidency if his White House didn’t start out by ignoring the TRO. According to Politico (one of the banned outlets):
A POLITICO reporter was denied access to the White House Thursday and his press credentials confiscatedafter a judge orderedthe Trump administration overnight to immediately restore access for news organizations that President Donald Trump banned from the complex last week.
MS NOW and CNN said their reporters were also denied entry. The three outlets have been barred from the White House since Saturday, following an order from Trump to do so “as a result of their constant ‘reporting’ FAKE NEWS!”
And so, the news orgs rushed back to court to point out that the White House was violating the TRO, which judges generally don’t take kindly to:
Early this morning the Court issued a Temporary Restraining Order directing “that Defendants (except for President Trump) and their agents, representatives, and all persons or entities acting in concert with them shall immediately return, reinstate, and restore the White House ‘hard pass’ press credentials held by employees of CNN, MS NOW, and POLITICO that were revoked on or about September 18, 2026.” Dkt. 24 (the “Order”). This morning journalists from each of CNN, MS NOW, and POLITICO attempted to enter the White House and were turned away. A Secret Service agent confiscated the hard pass of journalists from all three organizations. And when Plaintiff Betsy Klein, whose hard pass was confiscated on Saturday, September 19, requested to have her hard pass returned, her request was denied and she was refused access to the White House complex.
The judge ordered the White House to respond to the non-compliance notice by 12:30pm, and quickly received a declaration from Micah Stopperich, the Director of White House Press Operations, that the passes had been restored as of 9:07am, and that previously confiscated badges had been dropped at the entry gate to return to the journalists they had been taken from. Yet reporters say they were still being turned away until around noon, well after that supposed 9:07am restoration. They eventually regained some access to the White House.
But hours later, journalists from two of the same outlets were turned away from the arrival ceremony for Trump’s state dinner with Xi Jinping. As MS NOW itself reported:
Hours after regaining access, MS NOW White House reporter Laura Barrón-López was denied entry Thursday evening to the arrival ceremony on the portico ahead of the White House state dinner for Chinese President Xi Jinping. MS NOW had requested credentials for the event but never received a response. A CNN producer and correspondent were also denied access. When Barrón-López asked why she was being turned away, a White House staffer told her to “talk to Steven,” seemingly referring to White House communications director Steven Cheung.
According to CNN, the White House told them that CNN could not send a reporter to cover Xi’s arrival, only a photojournalist and an audio technician. The White House will surely argue that credentials for a specific event aren’t the same as the hard passes covered by the TRO. But blocking the reporters while allowing only CNN’s camera crew (a restriction not imposed on any other network) is exactly the kind of petty gamesmanship that the pending preliminary injunction briefing will have to deal with.
It’s unclear how the White House thinks any of this helps. It’s unconstitutional, and it makes the administration look petty: An administration that insists it’s the champion of free speech can’t even manage to let reporters in the door after a judge orders it to.
I’ve written a lot this year about how Republicans hijacked the $42.5 billion Broadband, Equity, Access, and Deployment (BEAD) program (created by the 2021 infrastructure bill) and immediately set about weakening oversight standards, eliminating enforcement of stuff like broadband affordability, speed, and equitable deployment, and making it a priority to heavily subsidize Elon Musk for LEO satellite broadband networks he had already planned to deploy anyway.
All of the chaos and changes have resulted in endless delays, and a lot of promising providers backing out of the BEAD program entirely. That includes electric cooperatives, many of which have been pushing affordable fiber optics into their existing, very rural electrical footprints.
The Trump NTIA process has been so filled with cronyism, delays, changes, new pointless regulations and chaos, a third or more of U.S. cooperatives say they’ll no longer participate:
“63 electric cooperatives across 27 states received provisional BEAD awards to offer reliable high-speed broadband to some of the most challenging eligible locations in the country. But delayed implementation and shifting guidance have created a program defined by uncertainty and confusion. Instead of accelerating deployment, continual revisions to the program have discouraged participation,” said Matheson.
“To date, 20 of the 63 electric cooperatives originally slated to participate in BEAD have withdrawn from the program. Many others are considering withdrawal, citing concerns over the application of extra-statutory pole attachment requirements as a condition of participation,” he added.”
Cooperatives are annoyed, in part, about new pole-attachment regulations the NTIA applied that make installations much more time-consuming and complex. The Communications Act explicitly exempted electric cooperatives and municipal utilities from federal pole regulation because such providers serve the public interest and are often the only ones willing to connect rural Americans.
Many incumbent telecoms control local poles, and make pole fiber attachment extra annoying to forestall competition. I’d suspect the new restrictions — from an administration that generally demonizes corporate oversight and regulation — are at the direct request of companies like AT&T, worried that popular cooperatives might gobble up market share in markets they theoretically could serve in the future.
It’s worth reminding you: Republicans spent the entirety of the last few years insisting that BEAD was a giant government boondoggle, and that once in office they’d fix it. This claim was routinely propped up by the likes of Ezra Klein at the New York Times, who hasn’t had a single solitary thing to say about U.S. broadband access policy in the two-years since Trumpism retook control of the program.
Congress originally set aside $42.5 billion to improve U.S. broadband. The Trump administration effectively tried to cut the program in half, insisting that Elon Musk’s expensive, congested satellite service would be “good enough” for a lot of these locations. The Trump administration then very clearly tried to wander off with the remaining money, and continues to be very murky about when states will receive it.
Fixing U.S. broadband requires a coordinated array of solutions. Some communities are helped by municipally-owned broadband. Some are helped by the local electrical cooperative getting into fiber and expanding cheap fiber access to rural communities. Others are best served by public-private partnerships between local governments and private providers.
The Trump administration’s BEAD changes have worked tirelessly to redirect a lot of money away from these popular, highly localized solutions, and funnel as much money as possible into the back pocket of incumbent monopolies like AT&T and Comcast, or billionaires like Elon Musk.
Other smaller and mid-sized providers are increasingly backing away from participating in the program entirely, either because of new restrictions and delays, or because the cost of deployment is skyrocketing due to wars, tariffs, and other Trump bumbling. As more BEAD bidders back away from participation or existing awards, more and more money will be funneled to Musk for substandard service so Trump Republicans can pretend the problem of U.S. broadband access has been “fixed.”
In states like California, Trump officials are insisting that California won’t receive any of its already-scheduled $1.86 billion BEAD grant award if they do literally anything telecom monopolies don’t like, whether that’s holding big telecom affordable for high prices, or enforcing the state’s net neutrality law.
It’s a cronyistic mess that’s starting to see growing bipartisan anger even in states like Texas, and it’s poised to get much, much louder as the long-delayed money to states truly begins to flow next year. Right now, a lot of people in state broadband policy are hesitant to publicly comment because they’re worried the Trump administration will sever their grant awards entirely.
Jennifer is a marketer, project manager and impresario. We’ve worked together on projects, and it’s always a delight. She and I sat down to talk about the hard work of what’s next.
As of Wednesday, President Trump’s press ban had kept CNN, MS NOW and Politico off White House grounds for five days, with the network television pool still refusing in solidarity to operate. So the three outlets upped the stakes by seeking a temporary restraining order at an emergency hearing Wednesday afternoon. Early Thursday, U.S. District Judge Timothy Kelly, as expected, ordered the Trump regime to “immediately return, reinstate, and restore” the White House hard passes held by journalists at CNN, MS NOW and Politico.
Then things got hairy. The next morning, reporters from all three outlets were still being turned away at the White House gates. The outlets told the court that “a Secret Service agent confiscated the hard pass of journalists from all three organizations.” Their lawyers told Kelly that top White House officials had “repeatedly violated” his order. Axios reported that the White House had defied the court, and press freedom advocates called for officials to be held in contempt. Even Senate Majority Leader John Thune (R-SD) said the White House should “follow the court order.”
Kelly gave the administration until 12:30 p.m. to respond, and that seemed to do the trick. The barred journalists began returning to the grounds around noon. Shortly before the deadline, the White House filed a sworn declaration stating that the passes had been waiting at the gate since just before 10 a.m., contradicting what several journalists experienced.
But the reprieve was short-lived. By evening, the White House was again keeping CNN and MS NOW journalists away, this time from Chinese President Xi Jinping’s arrival for a state dinner.
As I wrote in The Big Picture earlier this week, the ban dates to last Friday, when Trump announced on Truth Social that he was barring the three outlets “as a result of their constant ‘reporting’ FAKE NEWS!” On Saturday morning, Secret Service officers confiscated MS NOW reporters’ badges at a West Wing entrance and turned away reporters from CNN and Politico. On Monday, the outlets and three of their White House reporters sued. As I noted then, legal takes on Trump’s position had “reached a rare consensus: they are uniformly against it.” The outlets’ lawyer, Theodore Boutrous Jr., called the case “the [Jim] Acosta case times at least 78,” a nod to the number of journalists whose hard passes were pulled.
Kelly’s ruling took the form of a temporary restraining order, or TRO—an emergency tool courts use to quickly freeze things in place until a fuller hearing. Here, the status quo meant putting the reporters back where they stood before Trump’s ban, with their hard passes in hand.
The TRO lasts 14 days. It binds every defendant except Trump himself, along with their agents, representatives and “all persons or entities acting in concert with them.” Before anyone’s hackles rise, omitting the president follows a long-standing federal court practice against directing orders to a sitting president. Judges generally aim relief at the officials who carry out a president’s decisions. Here, those are the White House aides and Secret Service officers who issue, deactivate and collect the passes.
A fuller hearing comes next, on the plaintiffs’ motion for a preliminary injunction, an order that would keep the ban blocked while the lawsuit continues. Kelly set a quick schedule. The outlets must file their request by Monday, Sept. 28, the administration must respond by Friday, Oct. 2, and the outlets’ reply is due Monday, Oct. 5, with a hearing to follow. Kelly wrote that he “intends to rule expeditiously.”
Pay attention to the difference between the TRO and a preliminary injunction. Federal law lets the losing side immediately appeal an order granting a preliminary injunction. A TRO is usually unappealable, since it is meant to last only days.
That distinction often doesn’t register with this White House. It has appealed TROs in other recent cases despite the general rule, and CBS News reported Thursday that the Justice Department is expected to appeal this one swiftly—but so far, nothing.
Kelly’s ruling is sound
Trump won’t get far even if he does appeal the TRO. Let’s review the basics.
To win a TRO, a party must convince the judge of four things:
that it will probably win the case
that it will suffer harm a later ruling can’t undo
that the balance of hardships tips in its favor
that the order serves the public interest
Kelly called that “a high bar” and found the outlets had cleared it.
The outlets raised two constitutional claims. Under the First Amendment, they argued that Trump punished them for the content of their reporting. Under the Fifth Amendment, which bars the government from depriving people of liberty or property without due process, they argued that their passes were pulled with no notice and no chance to respond.
Kelly needed only one viable claim to grant relief. He found the outlets likely to succeed “at least on their Fifth Amendment procedural due process claim,” leaving the First Amendment question for later. Not coincidentally, he took the same approach in Jim Acosta’s case in 2018.
Two precedents from the D.C. Circuit—the appeals court whose rulings bind Kelly—drove the ruling. As I discussed in my earlier piece, Sherrill v. Knight (1977) involved Robert Sherrill, a correspondent for The Nation denied a pass on Secret Service security grounds. The court held that a reporter’s interest in a White House press pass is a liberty interest the Fifth Amendment protects. In Karem v. Trump (2020), the court sided with Playboy correspondent Brian Karem, whose pass Trump’s first White House had suspended. It reaffirmed that “a duly issued hard pass may not be suspended without due process.” Together, Sherrill and Karem require the White House to publish, in advance, the rules whose violation could cost a reporter a pass and to give fair notice of both the prohibited conduct and the potential penalty.
Kelly found that the White House had met none of those requirements. The government did not dispute that the reporters received no notice or opportunity to respond before losing their passes. No standards were in place before the reporting the White House objected to. The only standard it offered appeared in letters sent Sept. 22, the day after the outlets sued, faulting them for violating “standards of professionalism and decorum.” Kelly called that standard “so vague it hardly does the trick.” He also noted that the White House had renewed CNN reporter Betsy Klein’s pass several months after she published some of the very stories it later cited against her.
The Justice Department offered two responses. First, it argued that Sherrill and Karem were wrongly decided. Kelly replied, “Maybe—but this Court is bound by D.C. Circuit precedent, full stop.” Second, it argued that the letters gave the outlets a chance to respond after the fact. Courts sometimes allow that in “extraordinary circumstances,” and the government said national security made this case one of them. Kelly explained that the exception covers situations such as freezing the assets of international drug traffickers, where advance warning would let the money vanish. Here, some cited stories were months or years old, and Kelly described them as “routine.”
Kelly was also “skeptical—at least on this record—that Defendants’ interest in safeguarding national security is the actual motivation for, or is even advanced by, the revocation of Plaintiffs’ hard passes.” Nothing from before the lawsuit pointed to national security. Trump’s own announcement focused on “the alleged lack of truthfulness and negativity” of the outlets’ reporting, not national security. The government offered no evidence of how any of the stories had harmed national security. Its declarations came from Defense Department officials with zero direct knowledge of how reporters work at the White House (par for the course in Hegseth’s Pentagon). In most cases, the reporters who wrote the cited stories did not even hold hard passes.
The morning at the gate
Kelly’s order reached the White House overnight early Thursday. According to the White House’s sworn declaration, the press operations office learned of it at 7:10 a.m. and began restoring access at 7:25. Reporters from the three outlets were arriving at the gates about the same time.
Then the ketchup started to hit the wall. MS NOW White House reporter Laura Barrón-López and a producer were denied entry and had their passes confiscated, while a second MS NOW producer was let in. A Politico reporter was turned away and had his credentials confiscated. CNN’s Klein and a photojournalist were turned away at 9 a.m., and Klein was refused three more times. When Klein asked for the pass officers had taken from her the previous Saturday, her request “was denied and she was refused access to the White House complex,” the outlets told the court.
In short, hours after a federal judge ordered the passes returned, Secret Service officers were collecting more of them. The outlets asked Kelly for an immediate hearing, stressing that time was short because CNN was scheduled to serve as the television pool for Xi’s visit that evening. Legal analyst Shan Wu told Axios that the administration risked being held in contempt, further damaging its credibility with the judge. Seth Stern, director of advocacy at the Freedom of the Press Foundation, warned that the court must act: “Court orders are just paper unless they’re enforced.”
The White House has done something similar before. In April 2025, days after U.S. District Judge Trevor McFadden ordered the Associated Press’s access restored, the White House still barred an AP reporter and photographer from an Oval Office news conference. At the time, it was asking an appeals court to put that ruling on hold.
Inside the White House, multiple advisers and officials told CNN they had no idea what the plan was, describing a sense of internal chaos, also known as Thursday at the Trump White House. Reuters reported that it was unclear whether the Secret Service was refusing to comply or whether reactivating the passes electronically was simply lagging.
Facing Kelly’s 12:30 p.m. deadline, the White House TACOed, even as it insisted the confiscated passes had been at the press gate since before 10 a.m. If so, no one told the Secret Service. CNN reported that its journalists and MS NOW’s were still being turned away as late as 11 a.m. Klein and the photojournalist were let in around noon. Kelly then called off the emergency hearing and, as former U.S. Attorney Joyce Vance reported, told the outlets they could return after 6 p.m. if problems persisted.
The Xi visit
The standoff at the gates coincided with Xi’s state visit. Xi arrived at the White House around 10 a.m., while CNN’s Klein was still being turned away. That afternoon, Trump posted on Truth Social that CNN and MS NOW had “refused to cover” his morning arrival at the White House:
“The event was magnificent — Actually made for Television but, because they’re Fake News, and because they knew how good it would be, they didn’t want credit to be given to ‘TRUMP,’ they refused to be there.”
During a photo session with Chinese photographers, Trump quipped that Xi had the friendliest press corps in the world (they kind of have to be) and that Chinese reporters ask Xi’s permission to speak (gross). CNN’s Alayna Treene reported that American and Chinese photographers had been separated from the pool and brought in for two photo opportunities and that Trump made the remarks during the second.
The fight resumed that evening. The White House had solicited names from CNN to cover Xi’s arrival for the state dinner, and the network submitted its usual team. About an hour before Xi arrived, the White House said CNN could send only a photojournalist and an audio technician. When a CNN reporter and producer tried to enter, a press wrangler turned them away and told them to “talk to” White House Communications Director Steven Cheung, a defendant in the lawsuit. Barrón-López, hours after regaining her pass, was also denied entry to the state dinner arrivals; MS NOW said it had requested credentials and never received a response. When Barrón-López asked why, a White House staffer told her to “talk to Steven.”
The status of the television press pool also remained unresolved. Through Thursday night, the five networks that make up the pool were still declining to take part, and no major American network aired live coverage of Xi’s day at the White House.
Object permanence: 9/11 x Viridians; Announcing Wikipedia; Infinite Copyright Mickey; Floppy shoulder bag; Wells Fargo's long sleaze; Corbyn wins Labour leadership; Interop v internet monopolies; The billionaires aren't all right; RIP Mike Ford; PGP didn't cause 9/11; Flying Solaris boxen; "Unelectable" Corbyn; Algorithmic management; "That's Disgusting!"; Tax breaks for repair expenses; Climate denial driven by economic doctrine; "100% pumpkin" has no pumpkin; Copyright reversion; "Scholars of the Night"; Apple threatens EU.
The thing about a maddening itch between your shoulder blades is that it feels so good when you scratch it, and even better when someone else scratches it, and better still if that person hits the right spot because they love you and they've performed this service for you so often and attentively that they know exactly which spot to hit.
One of the recurring themes in Spider Robinson's short stories and novels is people who have close relationships suddenly realizing that they have acquired a psychic link. He comes up with endless ways to play this scene out, but my favorite – I think it's from one of the later Callahan's tales – is when one person scratches another between the shoulder blades and hits the exact right spot the very first time and they realize that they are now psychically linked.
Maybe it's a primate grooming reflex, maybe it's receiving a gesture of love and care. Maybe those are the same things. Having your itch scratched for you feels good. Not just primates, either: cats with the flexibility to reach any part of their body with all four of their paws and their teeth will nevertheless purr like a badly-tuned diesel outboard when you scratch them just right.
Since the outset, the free software/open source movement has extolled the virtues of technological self-determination, which is to say, deciding how the computers and programs you use will work. This is often described as "scratching your own itch."
There is no question that scratching your own itch in this way is hugely and enduringly satisfying. On my laptop, I have a variety of little scripts and keybindings and bits of automation that I've built up over the years and every time I use one of these, I get a little hit of brain-reward.
The latest: I got tired of alt-tabbing to get to the file explorer, only to discover that I'd closed all my file explorer windows, meaning I had to mouse over to the dock and open a new one. So I bound "Windows key + E" to opening a file explorer after reading a message board post from an ex-Windows user who'd done this (apparently this is a standard Windows keybinding).
I've fully retrained my fingers to type Win-E rather than alt-tab when I want to get at a graphic filesystem and every time I do, I get the tiniest little pleasant jolt of pleasure. I scratched my own itch!
But even better than this are the little scripts that other people have thoughtfully made for me over the years. The oldest of these still in daily use is more than 20 years old, a bash script called "boingpic" (from when I was still working on Boing Boing). When I run this, it iterates interactively through the files ending with "jpg" or "png" on my Desktop, tells me how wide they are, prompts me to resize them or hit enter to keep their size, and then rsyncs them to the directory on my server that corresponds to https://craphound.com/images/.
If this strikes you as weird and inefficient, that's fine, because it does exactly what I need it to do, and I've memorized it through long, long use. And on top of all that, boingpic.sh was written for me by my dear old friend Seth David Schoen, when we were one of a bare handful of EFF staffers in the early oughts and hung out together all the time. Every time I use it, it reminds me of Seth, and good times, and I feel good.
For centuries, people have fought for the right to self-determination. The disability rights rallying cry "Nothing about us without us" actually dates back to 16th century Poland (it was the basis for the formation of a Polish parliament that wrested power away from the king). Any parent who has avoided a conflict over getting dressed for school by swapping out "Put your clothes on right now!" for "Which would you rather put on first, your shirt or your socks?" knows how far even a little autonomy can go.
I worked as a computer programmer from the age of 17 to about the age of 29, and while I was never a spectacular coder, I was good at it, and I wrote a lot of code for myself that precisely met my needs, which always felt great. It's one of the reasons I have always championed low-code/no-code software development tools, from Logo to Hypercard to Visual Basic to Scratch. Sure, the code that you write with one of these tools might not be "efficient" from a CPU/memory-usage perspective, but the point is that you write it. You don't have to convince someone else to do you a favor, you don't have to part with any of your money – and you don't have to try to get someone else to understand what you mean when you describe the tool you want.
When I worked at Bakka Books (the world's oldest surviving science fiction bookstore, in Toronto), we organized our inventory using an extremely idiosyncratic Filemaker database created by the store's then-owner, John Rose. John lovingly tended that Filemaker app, tweaking it on his days off to make it better suited to the very specific needs of a science fiction bookstore with a giant used section and an important sideline in keeping collectors' want-lists that we consulted whenever we bought more used books. There are doubtless "better" bookstore stock-keeping systems (including the one that Bakka uses now, in its latest incarnation as BakkaPhoenix), but that Filemaker app was John, a presence in the store even when he wasn't there, embodying his management and literary and retail theories on a MacSE by the cash-register.
I am highly skeptical of vibe-coding in the sense of writing code for other people to use. But when I meet people who've vibe-coded their own apps for their own use to scratch their own itches, I completely get their excitement. They've scratched their own itch! I know exactly how good that feels:
Sure, I have concerns about this kind of personal vibe-coding, the biggest of which is that if you aren't a skilled programmer, you might end up vibe-coding an app that you can't adequately assess, so it might contain subtle defects that make you vulnerable to security risks and/or expose your sensitive information to the public internet. But there are domains and use-cases where I am totally willing to accept that vibe-coding can enhance someone else's life in important ways, by letting them build exactly the widget they need, and if (when) it breaks, they can just do it again.
This is even better than "nothing about us without us." It's not just insisting that someone else "gather your requirements" before producing a tool that you will rely on and require. This is you, producing that tool for yourself, which means that you might be able to embed features and affordances into it that you can't even articulate, let alone defend. There's something undeniably great about scratching your own itch and hitting exactly the right spot.
Even so: the experience of working through your requirements with someone else is clarifying and disciplining, because while you are the domain expert on your needs, that doesn't mean you're the domain expert on how to address those needs. You have the worm's eye view of your life and your needs, while an expert can have the bird's eye view that comes from working with many people, exposing them to many ways of solving problems, including ones you've never thought of.
Darren, the contractor who put in our new kitchen a couple years ago, had ideas for cabinet- and appliance-placement that had been refined by seeing, demolishing, building and revising orders of magnitude more kitchens than we had ever cooked in, and moreover, he clearly cared about our long-term happiness in our own home. The kitchen is great.
That care makes all the difference. Skilled craftspeople can bring expertise to the project that doesn't trump your needs, but can be co-equal with them. Scratching your own itch is great, having your itch scratched by someone who cares enough about you to know where your itch is, that's even better. But best of all is for that person to find the itch you didn't even know you had and scratch that, too. That's something that relies on the human connection that the best free/open source projects embody, the co-creation and community between developers and users.
If you've ever filed a bug against a free/open project and worked through the testing the devs need to squash it, you've experienced that co-creation. The devs want their code to work, because they care about the users, and you as a user can help other users and the devs by reciprocating that care through conscientious, patient, attentive bug reporting and testing.
I think that so much of the outrage about slop code – floods of garbagey pull requests and bug reports – is the result of the collapse of this dynamic. Slop's not merely annoying or time-wasting: it's a betrayal of the love and care that goes into writing and maintaining code for others. Your cat can scratch any part of its body, but it wants you to scratch it, and it will hiss at you and even claw at you if you scratch it the wrong way.
"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
“Once Is Enemy Action,” a science fiction novel about the origins of modern technofascism. Today's words: 511 (19222 total).
"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.
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.
"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.
After more than a year of hard work, we are thrilled to announce the launch of F-Droid
2.0, a complete redesign of the official F-Droid app and the largest app update
in 10 years.
For more than a decade, F-Droid has helped people discover and install free and
open source Android apps. F-Droid 2.0 builds on that foundation with a modern
interface, better app discovery, improved search, and a simpler experience that
works well, whether you’re new to F-Droid or have been using it for years.
This isn’t just a visual refresh. The user experience was redesigned to
integrate smoothly with current Android patterns, like Material Design, while
keeping familiar F-Droid interactions in place. Key components were reworked and
rewritten using Kotlin Compose, the standard toolkit these days, creating a
foundation that will help us deliver improvements more quickly in the years
ahead.
We are excited to begin rolling out F-Droid 2.0 to users over the coming weeks
after 14 test releases.
What has changed?
One of our main goals for F-Droid 2.0 was to make it easier to discover,
install, and maintain the apps you rely on. We simplified the main
navigation into three core areas: Discover, Search and My Apps. Categories are
now integrated into Discover, making it easier to browse and explore, while My
Apps provides a central place to manage installed apps, updates, and potential
issues. Settings and Nearby Swap are still only a tap away from the top bar, but
no longer compete for space in the main navigation.
Discoverability improvements
Helping people discover relevant free and open source software (FOSS) was one of the
primary goals of F-Droid 2.0. As the F-Droid ecosystem has grown to thousands of
applications, finding the right app has become increasingly challenging. The new
release introduces improvements throughout the app from browsing and categories
to search to make it easier to find software that matches your needs. And of
course, F-Droid does this without tracking you, or trying to “engage” you to
spend increasingly more time in the app.
A redesigned Discover experience
The new Discover screen helps uncover apps you might otherwise miss. In addition
to highlighting newly added and recently updated apps, it now showcases the most
downloaded apps in the repository. Whether you’re new to F-Droid or looking for
something different, Discover provides several ways to explore the growing
ecosystem of free and open source Android applications.
More useful categories
Categories play an important role in helping users browse the repository, so
we’ve expanded and refined them significantly, including more specialized
categories that make it easier to find specific types of apps, such as VPNs,
firewalls, password managers, launches and navigation tools. Here is what you
can expect:
First, we’ve significantly expanded the category system. Instead of relying on a small number of broad categories, F-Droid now includes many more specialized categories, helping you get closer to the kind of app you want in just a few taps, even before you start searching.
Second, to make this expanded category system easier to navigate, we’ve introduced higher-level “meta” categories in the Discover screen. These group related categories together and provide a more approachable entry point for browsing the growing F-Droid ecosystem.
Finally, categories now play a larger role throughout the app. Their names and descriptions are used to improve app discovery and help guide users toward relevant free and open source applications.
As an example of this effort, we’ve completely reworked the Games
category. Rather than grouping all games together, F-Droid 2.0 now distinguishes
between 17 different game genres, making it much easier to find the kinds of
games you actually enjoy playing.
Search that understands what you’re looking for
Search has also been significantly improved. In addition to app names, it can
now search app descriptions, categories, and translated content. This makes it
easier to find apps based on what they do rather than what they’re called.
We’ve also made major improvements for users searching in Chinese, Japanese, and
Korean. The new search system provides much better support for CJK writing
systems, helping users find relevant apps more reliably in their own language.
Search also remembers your recent queries, allowing you to quickly return to
previous searches without having to type them again.
Powerful filtering, made approachable
Browsing and searching are only part of the story. F-Droid 2.0 also introduces
powerful filtering options that help you narrow down large lists of apps to
exactly what you’re looking for.
Filters can be combined using multiple criteria, such as app category, device
compatibility, or anti-features. For example, you can choose to view only Action
Games that are compatible with your device and exclude apps that depend on
non-free network services.
To help users discover these and other advanced capabilities, F-Droid 2.0
introduces onboarding screens throughout the app. Rather than hiding features
behind complex settings, the app provides contextual guidance to help both new
and experienced users get the most out of F-Droid.
For the longest time, the experience of clicking install or update was forced to
be second rate by Android. Now, thanks largely to pressure from the EU’s Digital
Markets Act (DMA) and anti-trust actions around the world, Android offers all
app stores an option for a smoother and more automatic install and update
experience than before. F-Droid 2.0 includes groundbreaking work on utilizing
these new abilities. This allows F-Droid to use a unified installer for all
F-Droid installs, whether built into the OS or you installed it on your device
yourself. The unified installer makes use of the new pre-approval API, so that
on supported devices the user can confirm right after deciding to install the
app, instead of after the app was downloaded. That brings the F-Droid install
experience on official Android devices much closer to what the built-in app
store can provide.
What moved, and what was removed
A redesign of this size means making careful decisions about what belongs in the
new app, what can be handled differently, and what no longer makes sense to
carry forward. Some familiar features have changed, moved, or been removed as
part of making F-Droid 2.0 more streamlined and easier to maintain, without
sacrificing core functionality or features users rely on.
Update checks now happen automatically
F-Droid 2.0 now fetches and installs app updates by default. If you prefer more
control, no worries, your existing preferences are still respected.
Some users missed the pull-to-refresh gesture for checking all repositories for
updates. In F-Droid 2.0, the pulling gesture is exclusively for scrolling. This
is now possible because the app can now automatically check for updates in the
background. Rather than preserving a familiar action, we focused on removing the
need for it. The best refresh button is the one you never have to press.
Users who want more control still have fine-grained and manual update options
available. If you used pull-to-refresh to manually trigger updates, that is now
available under the action overflow menu, e.g. the “three dots”, on the My Apps
screen.
Data usage settings
F-Droid gives you control of what get’s downloaded when. This helps fit our
diverse users around the world, who have varying requirements. Many users have
cheap access to mobile data, while mobile data is prohibitively expensive for
others. Some users have heightened privacy requirements, so they need to
control their network traffic. While others are using limited devices which bog
down when F-Droid updates in the background. The settings which control all this
were reworked to make adapting F-Droid to your needs more intuitive.
Privacy and security features
Some F-Droid users operate in environments where simply having certain apps
installed or even using F-Droid can attract unwanted attention. To help support
these users, F-Droid has long included a set of privacy and security features
designed to protect both the user and their data.
One key privacy tool is Tor, and F-Droid has long supported using Tor for all
network connections, and using Tor Onion Services for repositories and mirrors.
The landscape of how Tor is integrated into Android has changed quite a bit
since Tor support was first integrated. Now there is TorVPN, Orbot, TorServices
and more. We took this opportunity to simplify the settings and remove the
auto-detection that was no longer reliable. If you enabled “Use Tor”, that will
be migrated to generic Proxy Settings. Going forward, Tor VPN is the recommended
approach for easy Tor support, and the Proxy Settings are still available for
those who need manual control.
Another key part is the set of “panic” features, which allow users to quickly
remove some specific kinds of sensitive information from their device in
emergency situations. These features are still included in F-Droid 2.0 and
remain an important part of supporting users with elevated security needs.
Notably, the F-Droid app hiding feature has been simplified, to give users an
accurate idea of the kind of protection they can expect. F-Droid was one of the
first apps that began providing app hiding features to protect user privacy,
including our “panic” feature which disguised the F-Droid app as a simple
calculator app. This simple feature was requested by many users, and since then
Orbot, TorVPN, Signal and others have added such masking features. Over time, a
standard design has emerged across widely used apps, and we have adopted this
design in the new release as well. This feature is designed so that users can
better understand the limits of the disguise. Instead of the mask looking and
functioning as a simple calculator app, now the mask only affects the app icon,
name and nothing else. This informs users that the F-Droid app will still appear
in the “Apps” settings and would be detectable during forensic inspection. This
change will hopefully make it easier for users to understand the limits of this
feature, while still utilizing it when needed.
One feature that has not yet returned is the ability to remove and wipe apps as
a response to a panic trigger app like Ripple. We recognize that some users
rely on this functionality for privacy and personal safety reasons and
understand it is more than a usability feature. However, it requires highly
specialized work to maintain, and given the small user base, we felt it should
no longer block so many other important improvements.
The app-wiping feature remains an important feature. We would
especially welcome feedback from people who use it, to help us
understand how and when it is used, so we can evaluate the best path
forward as we continue improving F-Droid 2.0. Users who rely on
the current app-wiping implementation may opt to postpone updating to
F-Droid 2.0 while we evaluate bringing the feature back.
For Android versions that integrate F-Droid
F-Droid is designed to be integrated into any version of Android or AOSP, as we
can see in CalyxOS, emteriaOS, iodéOS, Lineage-for-microG and ShiftOS. Each OS
can include their own repositories by default using the “additional repos”
mechanism. If you use one of these OSes, these will be visible in your
Repositories overview. For additional info on what changed, check out this
blog post.
Also, F-Droid Privileged Extension (FPE) is not currently supported by 2.0. That
means even if FPE is installed, F-Droid 2.0 won’t use it. This overhaul focused
on full featured support for the Android “session” installer. That lets F-Droid
run background updates on any recent Android version without requiring FPE. Like
with any of the changes here, we welcome feedback.
Lowering the barrier for contributors
While many of the improvements in F-Droid 2.0 are visible on the surface, some
of the most important changes happened behind the scenes.
All new code in this effort uses modern Android code standards and designs. This
gives us a codebase that is easier to maintain, test, and easier to extend with
new features in the future.
One of the goals of the rewrite was to lower the barrier for new
contributors. Android development has changed significantly over the past
decade, and F-Droid 2.0 is now built using Kotlin, the language that has become
the standard for modern Android development. This makes it easier for developers
familiar with today’s Android ecosystem to contribute to the project.
The new user interface is built with Jetpack Compose, the standard toolkit for
Android applications. Beyond simplifying development, this helped us align
F-Droid more closely with Material Design, the design system used throughout
Android. As a result, F-Droid feels more familiar to Android users while
remaining true to its own identity and values.
Most importantly, these changes provide a foundation for the next decade of
F-Droid development. By reducing maintenance burden and making contributions
easier, we can spend more time improving the experience for users and less time
fighting technical debt. Some new tools also depend on fixes in Android itself,
one such fix was added in Android 7 forcing us to drop support for Android 6. As
always, old F-Droid releases will continue to work on old Android versions.
A community effort
F-Droid 2.0 is one of the largest and most ambitious projects in our
history. Bringing it to life required much more than software development. It
involved user research, design, testing, documentation, community feedback,
quality assurance, lots of new code, a security audit and countless discussions
about how F-Droid should evolve over the next decade.
This work was made possible by the support of many organizations and
individuals. Torsten Grote’s development work on the new app was funded by
NLnet through the
Mobifree
fund. The Open Technology Fund’s User Experience & Discovery
Lab supported user research and design
work, bringing in Ura Design to help conduct user testing,
develop user stories, and refine our Human Interface Guidelines.
As part of this effort, the Open Technology Fund’s Security Lab
in conjunction with Convocation conducted an independent
security review of F-Droid 2.0. We analysed and addressed all findings relevant
to the new application, helping ensure that the release meets the high security
standards our users expect. We look forward to sharing the full audit report
once it has been cleared for publication.
Just as importantly, F-Droid 2.0 reflects the contributions of many
volunteers. Community members contributed code, testing, bug reports, design
feedback, translations, documentation, UX discussions, and countless ideas
throughout the redesign process. Both long-time contributors and people making
their first contribution helped shape the final result.
Finally, this work would not have been possible without your support. Donations help fund many of the less
visible but essential activities that grants don’t always cover, including
community management, handling the issue backlog, quality assurance, release
management, and project coordination. These contributions help keep F-Droid
healthy long after a specific grant-funded project has ended.
The journey continues
F-Droid 2.0 represents a major milestone, but it is not the end of the story.
Rebuilding the app has given us a stronger foundation, yet there is still plenty
of work ahead.
As the rollout reaches more users, we expect to learn a great deal from
real-world usage. Community feedback has shaped F-Droid 2.0 from its earliest
design discussions through many alpha and RC releases, and it will continue to
guide future improvements. Some ideas did not make it into the initial release,
while other features are still evolving as we gather feedback and refine their
design.
In the coming months, we will continue improving performance, accessibility, app
discovery, and overall usability. We’ll also keep listening to users as they
adapt to the new experience and help us identify opportunities for further
improvement.
Like every major F-Droid release before it, version 2.0 is not a destination,
it’s the beginning of the next chapter.
The future of Nearby
One area that continues to evolve is Nearby, the feature that allows users to
share apps directly between devices without relying on a central server.
The broader F-Droid 2.0 redesign gave us an opportunity to rethink Nearby from
the ground up. We have been working on a new implementation based on improved
connection methods that should make sharing apps more reliable and easier to
use.
This work is not quite ready for inclusion in the initial F-Droid 2.0 release,
but development is actively underway
and the foundations are already in place. If Nearby sharing is important to you,
now is an excellent time to get involved. Community feedback and testing can
help shape the next generation of the feature before it reaches a wider
audience.
How you can help
F-Droid 2.0 is the result of thousands of hours of work from developers,
designers, testers, translators, donors, and community members around
the world. Now that it is reaching users, we’d love your help making it
even better.
If you’re receiving the update, take some time to explore the new
experience and let us know what you think. Whether you’ve found a bug,
have an idea for an improvement, or simply want to tell us what works
well, your feedback helps guide future development.
If you’d like to get more involved, there are many ways to contribute.
Help us test, translate and review
You can help test upcoming features, improve translations and
documentation, review issues, contribute code, or join discussions about
the future of the project. New contributors are always welcome.
Consider donating to F-Droid
And if you’re able, please consider supporting F-Droid financially. Donations
through Liberapay or
OpenCollective help fund the ongoing work that
keeps the project healthy between major releases, from infrastructure and
quality assurance to community support and project coordination.
F-Droid 2.0 is a major milestone, but the work continues. Thank you for helping
us build a free, open, and sustainable app ecosystem for Android.
I don’t believe we’re each born with a purpose. We have more freedom than that, the freedom to choose the impact we’ll make.
Our work, though, does have a purpose. The change we seek to make. The people we’re here to make it for.
When we commit to work with purpose, it transforms us as well as the people we’re engaging with.
Who’s it for, what’s it for… if we can continue to return to the purpose of this product, this meeting, this ad–then we can find a common language and coordinate our efforts to make a difference.
Resistance pushes us in many ways. It pushes us to imagine that our work isn’t for us, we’re just biding time until we get to the real stuff. It pushes us to deny responsibility or to blame the system. And mostly, it pushes us to refuse to name the purpose of how we’re spending our time.
Stuck is just another word for being conflicted about our purpose. The knot holds us back because we’ve become entangled in goals that are mutually exclusive.
幼稚園 (ようちえん) — kindergarten 幼児 (ようじ) — young child 幼い (いとけない) — very young 幼いころ (おさないころ) — when one was a very young child 幼なじみ (おさなじみ) — childhood friend 乳幼児 (にゅうようじ) — infants 幼稚園児 (ようちえんじ) — kindergartener 幼い頃 (おさないころ) — when one was a very young child 幼少 (ようしょう) — infancy 幼稚 (ようち) — infancy