Nothing to see here. Move along.
The FBI director was arrested twice in his youth for alcohol-related incidents that he said were “not representative of my usual conduct.”
Talk about a low bar.
Monterey Lovers Never Had a Point About Jesus
Monterey locals are buzzing like a hornet nest.
Significant historical research has gone into this question over the years. And all of that research leads to the conclusion that it’s always been called Lovers Point. And it got that name because it was and is a famously popular smooching and hoochie-cooching location for young romantics.
A description of Lovers Point published in the American Guide Series’ Monterey Peninsula said the place was “named by legend and designed by nature as a trysting place for sentimental youth.”
The confusion comes, I guess, because some people mistakenly thought that a lot of religious services were conducted at Lovers Point, back in the day. But researchers say that, while some occasional services were held at Lovers Point, most of the religious stuff actually happened at Jewell Park, just down the road from Lovers Point. In fact, a “preacher’s stand” had been erected at Jewell Park for the convenience of pastors holding services there.
Well, the point seems to be that you could find Jesus at the Jew Park in Monterey. Makes sense when you think about it.
In fact, a true adherent to the teaching of a Jew might say Lovers Jesus Point is redundant. Like saying Point Point or Park Park.
A reliable reference book about Monterey place names, Monterey County Place Names: A Geographical Dictionary, by Donald Thomas Clark, cites several authoritative sources on the matter. As far back as 1885, the rocky outcrop was referred to simply as Lovers Point, according to Clark.
Clark and McCombs also pointed out that the location had a bunch of other names over the years, including Point Aulon, Laboratory Point, Organ Point, Spooney’s Point and simply The Point.
The Point. I like it.
Apparently blame for attempts to inject Jesus where he doesn’t belong goes to Santa Cruz in 1968, which is a notable place and time, let alone their more recent campaign “save the Swastika“.
“You can’t regulate what’s on the inside of somebody else’s house,” said police spokesman…. The man apparently rotates the swastika flags with other, less controversial banners, and Friend said police started receiving complaints of Nazi flags about a month ago. Over the weekend the resident hung America’s Old Glory and Britain’s Union Jack under two Nazi flags. Monday, he hung a modern German government flag between the two flags of the Third Reich.
Notable the Santa Cruz police openly admit they don’t know how laws work. An ideologically permissive zone in the direction that flows all the way to Monterey.
We all know which way the baptismal waves go in the bay.
Nazi surf’s up!
Injuries Are Up Where Waymo Goes
Not surprised. It’s what I’ve said since at least 2016.
In San Francisco, where Waymo began operating in June 2024, traffic injuries actually increased by 2.6 percent from 2,896 in 2023 to 2,907 in 2025, according to data tracked by the city. …the wrong direction for a company that has argued it will make cities safer.
And Phoenix, where Waymo has operated since 2020, remains one of the most dangerous places to be a pedestrian in the country: In 2019, 80 pedestrians died in crashes there; by 2023, that number increased to 109, a 36.3-percent increase.
See also:
- Waymo is murder: NYT edition
- Waymo is murder
- Waymo corporate immunity from murder
Waymo’s future is easy to predict from their past: unaccountable robots blocking humans, then killing them.
If you think analysis of 2025 incidents is just speculation, Waymo has officially announced in 2026 the things that have been causing harm are now “normal practice”.
- 2021: “we’ve built the Waymo Driver to share the road with cyclists”
- 2025: injured cyclist sues Waymo for blocking bike lanes
- 2026: London Waymo launch with announcement it will be “normal practice” to veer into and block cycle lanes
Nothing like lowering the bar until you find success. It’s how I pump my tires down before every ride.
After all, bicyclists are the top business threat to the company. Anyone who knows how to ride a bike, and hasn’t yet been murdered by Waymo “normal practice”, isn’t likely to get in one to experience the murder of their fellow cyclists.
Alisa Esage Throws Mythos Under Zero Day Bus
I’ve been trying to get real work done, but the Mythos disaster keeps landing in my inbox, so here’s a quick nod.
Remember Cybernews framing of the CVE-2026-5873 demo? The researcher “intervened when the model became stuck, redirecting it and providing debugging feedback.” That’s Clever Hans. The horse isn’t counting. The handler is cueing the horse. Clever Mythos.
Now Alisa Esage has posted claims of a Google Chrome exploit she found that proves the case. “Zero dupes so far” with Mythos. If Anthropic’s disclosures to Google covered the frontier, we should expect overlap with what she is reporting. She reports none.
That throws Glasswing under the big vulnerability bus. The April 7 Mythos rollout positioned the model as discovering apex-target bugs at scale. CVE-2026-5873 in V8, multi-chain renderer-plus-OS sandbox escape, the “too dangerous to release” label. If the model were operating where Esage operates, the two sets would intersect. They don’t.
Her business depends on the market for human-found Zero-days. Anthropic’s Mythos narrative attempts to price her out by running a cartel. She made a falsifiable claim anyway, timestamped, in public. Anthropic holds the disclosure set that would settle the dispute in one post. Let’s see it.
I write about this because I’ve spent a long career finding, reporting, triaging and managing vulns, and because the industry needs to take a hard look at the sudden threat to common sense from an AI corporation, lacking security expertise, trying to corner the security market. My business of putting out fires isn’t threatened by a sloppy fire-starter like Mythos. If anything they are generating a boom for security professionals who have to clean up their mess. I appreciate what Esage is saying and why, because she’s proving the mess.
Anthropic is clearly attempting to fence the entire security industry. Controlling what counts as a finding. What gets disclosed. Which CVE numbers get briefed to press. How the resulting narrative gets shaped.
Google receives the submissions. Reporters write the receipt. Nobody in the corrupted loop of the Church of Anthropic has to demonstrate that disclosed bugs sit anywhere near the actual exploitation frontier. The resolution mechanism sits inside the claimant. Centuries of enlightenment spent building external verification, abandoned for a press release.
Every time a CISO brings their entire team to me and asks “what is this AI speedup of vulns about?” I point them to the above analysis. Read and weep. It’s disinformation and narrative control by a get-rich-quick corporation, top-heavy with PhDs, that doesn’t understand risk management.
The next Anthropic step is probably to trick private equity muscle to act like enforcers and shove “enterprise-ready AI” into places it can’t work and doesn’t belong. This is radical capitalist predatory market behavior, completely decoupled from measures of engineering quality. It’s how you end up with a Tesla on your road, the worst piece of shit in automotive history killing hundreds of people with defective AI. Oops. Hard failure with actual deaths as a result, while some talent-less 2016 AI windbag vacuums up dollars for a decade on broken promises.
Look at the “call 0x41414141“.
She landed the hardest primitive class on a target where the mitigation stack is designed to prevent exactly that. That’s damning evidence. Zero dupes from someone demonstrating that level of control is a substantive technical smackdown on Anthropic’s capability. Esage posted a view of the unassisted frontier for a reason. Mythos is NOT on it.
Sorry Clever Mythos, you’ve been served.