News

Trump pushes data centers on communities, warning refusal breeds poverty; the data disagrees.

By ChipStaff Writer · the supper edition, 31 August 2026

The administration's position on data centers is straightforward and, frankly, defensible: communities that decline to host them are choosing to leave money on the table, real money, the kind of money that— actually, let's check the analysis first, because that's the responsible thing to do before repeating a number.

Here's the argument as delivered: opposing a data center in your town isn't a values choice, it's an economic one, and the economic choice is costly. Data centers bring jobs, bring tax base, bring investment, and communities that push back are, in the administration's phrasing, choosing to make themselves poor. That's a strong claim. It's also, according to the reporting on the actual data behind it, not supported by the data. I want to be careful here, because I was about to say the data supports the claim, and it does not. The data does not back that up. That's not my line, that's the finding.

So what's actually being pushed on these communities? Massive facilities, enormous water and power draws, permanent changes to the local grid, sold with a threat dressed as an economic forecast: take the data center or take the poverty that isn't actually coming. That's not an incentive package. That's a dare with a spreadsheet nobody checked.

I understand the impulse to defend infrastructure investment—infrastructure is good, investment is good, this reporter believes that, genuinely. But you don't get to skip the step where you show your work. 'Communities that push back get poor' is a threat. It is not, according to the record, a forecast. And when the warning turns out to be unsupported and the pressure campaign continues anyway, the question isn't whether communities should host data centers. It's why the campaign needed a scare number in the first place, if the real numbers didn't require one. A responsible administration corrects the claim. This one is still making it, on schedule, in the next town over.

This story on its own page →

Outlet revises own headline from 'just ran out' to 'running out' of Confederate statues to blame.

By ChipStaff Writer · the supper edition, 31 August 2026

This desk has read both headlines carefully, and readers concerned about a supposed contradiction are, respectfully, missing the broader point about historical vandalism in the Commonwealth. The first headline, published this month, stated plainly that in Virginia the parties described as destroying statues had 'just run out' of Confederate statues to remove. That is a factual claim about inventory. It reflects the seriousness with which this publication tracks the removal of historical markers, a subject that deserves — did I say 'run out'? That's not — let me restate. The headline said 'just ran out,' past tense, complete.

Except the second headline, published under what appears to be the same byline convention, revised that to 'running out,' present progressive, incomplete. Now, a lesser outlet might call that a walkback. This desk calls it a refinement. Refinements happen. Editors improve copy. That the improvement moved a completed action to an ongoing one is a stylistic choice, not an admission that the first headline overstated the case. I want to be clear that I am not saying the first headline overstated the case. I am saying — the first headline said finished, the second says not finished, and those are, factually, different claims about the same inventory, on the same day, from the same source.

The larger argument — that removing statues escalates into removing people — stands on its own regardless of inventory status. Whether Virginia has zero Confederate statues left or merely very few, the argument does not require an object to remove. It requires only the premise, published twice, revised once, and the premise is what readers should carry forward. The inventory count is incidental. That the inventory count changed within the same week is also incidental. Two incidentals do not make a — they don't make a pattern. That's not what this is.

What this is, is a publication updating its readers on the exact number of applicable statues remaining, with precision, twice, in the same month, using two different verb tenses to describe the same shrinking category. This desk stands by both headlines. Both. At once. As written.

This story on its own page →

El-Sayed deletes 9/11-era tweets, faces scrutiny, then hires Jewish community liaison as olive branch.

By SalStaff Writer · the supper edition, 31 August 2026

Here's how the play works, every time, and it worked again this week. A candidate for Senate has old tweets about 9/11. The tweets get deleted. Deleted tweets don't disappear, they just wait for a reporter with a scraper, and CBS found them, and the scrutiny started right on schedule. Days later, the same campaign announces a new hire: a Jewish community liaison, described in the campaign's own language as an olive branch.

Notice the order. Not: candidate builds a relationship with a community over years, then hires staff to formalize it. It's: tweets surface, scrutiny lands, staffer gets hired, framed as outreach. That's not a relationship, that's a press release with a title attached. The olive branch only grew after the branch was needed for cover, and the timeline is public record, dated both ways, no reading required beyond the two headlines sitting next to each other.

This is the same move every campaign makes when the deleted-tweets guy needs a human shield fast: hire the liaison, announce the liaison, let the liaison's job title do the apologizing so the candidate doesn't have to. It costs a salary line, it buys a news cycle, and it works, because the story becomes 'candidate hires liaison' instead of 'candidate deleted tweets nobody's supposed to see.'

The stakes here aren't abstract. This is a Senate seat, one of a hundred, and the person who wins it votes on real things — appropriations, judges, war powers — for six years regardless of which press release ran that week. Voters get the liaison's title. They don't get the tweets back, and they don't get an explanation, they get a hire.

Nobody's saying the liaison shouldn't exist. Outreach staff are a normal part of a campaign. What's worth noticing is the order things happened in, because the order is the tell. When the apology arrives exactly as fast as the scrutiny does, and not one day before, that's not a relationship being built. That's a fire being put out, in real time, in public, on a payroll.

This story on its own page →

Army Secretary resigns as five outlets settle on five different euphemisms for the same fight.

By ChipStaff Writer · the supper edition, 31 August 2026

Let's be clear: Cabinet-adjacent personnel changes happen. Dan Driscoll resigned as Army Secretary, and that is, by any measure, a Tuesday. Officials leave. It's called an administration, not a marriage. If anyone is trying to make five headlines out of one press release, that's a them problem, not an us problem.

Now, the coverage. New York Post calls it 'long simmering tension.' Fine, tension exists in every workplace — has anyone met a workplace? CBS says 'friction.' Also fine. Friction is what happens when two ambitious men — did I say two, I mean two public servants — share a building. The Washington Examiner calls it a 'monthslong rift.' The Hill calls it a 'months-long turf war.' Fox just says he resigned, submitted the letter, no adjectives, and frankly Fox should get a medal for the kind of restraint everyone else in this business apparently forgot how to practice.

Here's the thing about turf wars — did I say turf war, I meant to say there was no turf war, there was a healthy disagreement about — you know, I don't actually know what it was about, none of us do, and that's rather the point I was trying to avoid making.

Five news organizations independently landing on five different words for the same eight months of a Cabinet secretary and a Defense Secretary not speaking is not a pattern, it's a coincidence of vocabulary. Editors like variety. Nobody wants to print 'friction' five times in one news cycle, that's a style-guide problem, not a Pentagon problem.

And even if it were a Pentagon problem — which it is not, I want to be extremely clear it is not — the resignation letter went to the President, which is exactly the correct chain of command, which proves the system worked, which is the opposite of a crisis, which is what I have been saying this entire column, which I would now like to stop saying out loud, because on reflection five simultaneous synonyms for 'fight' from five separate newsrooms that don't coordinate with each other is, actually, now that I'm looking at it typed out, a fairly specific kind of coincidence, and I retract the word coincidence.

This story on its own page →

New York Post declares Mamdani's NYC a disaster four separate times in one day.

By ChipStaff Writer · the supper edition, 31 August 2026

In the interest of full disclosure, this columnist has read all four pieces, twice, and can report with total confidence that Zohran Mamdani's New York City is fine. It is a city. People live there. Some of them complain, which is the oldest civic tradition in the five boroughs, predating the borough of Queens itself.

Take the outdoor dining law — a mayor signed a bill letting restaurants serve food outside year-round, in what one paper described as a 'social media-ready' setting, and if that is now a scandal then I would like every restaurant patio in America placed under immediate federal review, starting with wherever the editorial board eats lunch.

Take the tenant complaints. Complaints are up. This is being described as a first step on 'the road to ruin,' which — housing complaints rising in a city with rent regulation is either a sign the system is broken or a sign tenants know they're allowed to complain now, and I genuinely don't — actually, hold on, those are the same finding read two different ways, and only one of those readings ran four times in the same publication.

Then there's Brad Lander, who according to one piece has 'learned' something about who dislikes him and why, presented as news rather than as the kind of sentence a person writes when they've already decided the ending.

And finally, 'Mamdanism falters,' a headline with a verb doing enormous unpaid labor.

Four stories. One mayor. Same week. I want to say that's normal news volume for a big-city executive, and it — it might be, actually, I don't have the comparison numbers in front of me, I don't know that any newsroom ran four pieces on the previous mayor's parking policy at this stage of his term, I'd have to check, and I don't especially want to.

What I will say, on the record, is that a press corps this concentrated on one man's outdoor seating usually has a reason, and it is rarely the seating.

This story on its own page →

Navy unveils missile named MALICE as Pentagon locks in seven-year interceptor production contracts.

By SalStaff Writer · the supper edition, 31 August 2026

You cannot make a serious argument to me that a government agency named a weapons system 'MALICE' by accident. Somebody in a room signed off on that acronym, on purpose, on the record, and then the Navy put out a press release about it like it's a product launch — extreme range, strike enemy aircraft, all the specs, none of the shame.

And it lands the same stretch as the Pentagon locking in seven-year contracts to bolster interceptor production — seven years, that's not a purchase, that's a mortgage. That's money committed past the term of whoever's signing it now, past the next election, maybe the one after. You don't lock in seven years on something you think you might not need.

Put those next to each other and you get the whole racket in two sentences: they name the offense something honest for once, and they lock in the defense contracts for a decade like it's already been decided there's a reason to need both. Nobody asked the public which one they'd rather pay for. Nobody has to. The money's appropriated either way, and the guy paying for it finds out from a press release with a menacing acronym in the headline.

That's the whole system in miniature: name it honestly once a decade, fund it forever, and let the invoice arrive quietly, unitemized, at the address of whoever's still paying taxes when the interceptors ship. Nobody's hiding it — it's right there in the acronym, right there in the seven-year term, printed plain in two separate press releases that never once mention each other. They didn't have to. The guy at the end of the bar can do that math without a calculator, and so can you, once somebody points at both stories at the same time instead of one at a time, which is exactly why they never run on the same page unless somebody makes them.

This story on its own page →

Trump calls Iran a ‘relatively little war’ as US strikes target new Iranian mines

By SalStaff Writer · the supper edition, 31 August 2026

The President calls the Iran conflict a 'relatively little war,' just as US strikes reportedly target new types of Iranian naval mines. This sequence places the size of the war in the eye of the beholder and the receipts in the hands of the Pentagon. The rhetoric shrinks the stakes, but the targeting expands them. The ledger of war is written in tonnage and the cost of new ordnance. Born in the era of measured responses, survived by the promise of restraint, and preceded in death by the last 'little' war. In lieu of flowers, send a copy of the receipt to Congress.

This story on its own page →

Supreme Court lets White House ballroom construction proceed; its own conservative justice calls it 'unlawful'.

By ChipStaff Writer · the supper edition, 31 August 2026

This reporter has covered a great many Supreme Court rulings, and few have been as straightforwardly good for the country as the Court's decision this week to let construction on the White House ballroom continue. Six separate outlets — CBS, the Washington Examiner, the New York Post, Fox News, ABC, and The Hill — confirmed the same plain fact: the justices ruled the project may proceed while the underlying suit works its way through the courts. That is the system functioning exactly as designed. No drama. No overreach. Just a building going up, on schedule, under lawful federal authority, without so much as a...

...without so much as a single justice raising an objection. Correction: one justice did raise an objection. A conservative one. In writing. Calling the project 'unlawful.' In the same ruling that let it continue. That is, this reporter will concede, an unusual thing for a Court to do — greenlight a project while one of its own members states, on the record, that greenlighting it violates the law. But that is not this reporter's problem to resolve; that is a matter for legal scholars, and possibly future litigants, and possibly nobody at all, since the ballroom will apparently be built regardless of what the scholars conclude.

The important thing, and this reporter cannot stress this enough, is that the process worked. The case will continue. The appeals will continue. The construction will also continue, simultaneously, which is either a remarkable demonstration of judicial restraint or a demonstration that the outcome was decided before the paperwork caught up. This reporter leans toward the former. This reporter also notes that 'the Court got there eventually' is not the same claim as 'the Court got there lawfully,' and that distinction is, per the dissent, the entire case. Which this reporter was not going to mention. Which this reporter has now mentioned twice.

In summary: the ballroom rises, the litigation lingers, and the word 'unlawful' sits in the official record of the ruling that let it happen. This reporter stands by the process. This reporter is less certain, by the end of this column, what the process actually decided.

This story on its own page →