Between Google trying to bury its search under an “AI” chat and me moving most most of my website over to a new domain, I’ve been checking to see how well-indexed the old and new pages are at various search engines.

“Marineland of the Pacific” seemed to be a good phrase to test. Marginalia Search still has the old location for my Remembering Marineland (or not) post, but that search also turned up a page with scans of a Marineland ad flyer from 1962.

As someone who’s spent a lot more time hiking the Palos Verdes Peninsula than visiting an ocean theme park that closed when I was a child (not to mention way too much time updating OpenStreetMap), I was immediately drawn to the map…which strangely enough, shows Crenshaw Boulevard running over the hill, down through the Portuguese Bend landslide and connecting to Palos Verdes Drive South along the coast, just east of Wayfarer’s Chapel.

Simplified map of the Palos Verdes Peninsula showing Palos Verdes Drive around the peninsula, Marineland on one of the promonitories, major roads connecting to Los Angeles (Sepulveda, Hawthorne, Crenshaw, Western), and roads going *over* the hill including Hawthorne, Crest, and...wait, Crenshaw?

Wait, did Crenshaw actually connect sometime in the past? If so, how?

Today, Crenshaw runs up to the top of the hill and stops just past Crest Road, at Del Cerro Park. A dirt road continues past a locked gate, narrowing to a switchbacked path through the Portuguese Bend Nature Reserve. A landslide below it has been moving slowly for decades, preventing much in the way of construction on the land. Some people bought land and built houses on adjustable stilts so they could level the house every few months.

The first time I checked out the view from Del Cerro back in 2011, I took this photo of the area to the east, where Crenshaw appears on that map.

Looking out along a hillside sloping down to the ocean. Most of it is dry chaparral, with some clusters of darker trees, and a jumbled suburban neighborhood off in the distance as it levels out near the base. A dirt road snakes its way around the curves.

Over the last few years the land has been sliding faster, and a lot of the area has been closed for safety. Wayfarer’s Chapel has been dismantled to prevent it from flat out collapsing.

It’s no longer possible to connect Crenshaw to the coast.

But had it connected in the past, and been wiped out by the landslide? I went looking for the history, and found some articles that answered my question. I must have read this 2023 LA Times article when it was published, which means I’d forgotten a key detail about Crenshaw Boulevard’s relation to the landslide:

It caused it.

Crenshaw never connected to the coast. An extension was planned, and initial construction reactivated an ancient landslide in 1956, as crews moved enough dirt around to shift the underlying structure out of balance. At the time, the Portuguese Bend section hadn’t moved in roughly 4,800 years. In the 70 years since, it hasn’t really stopped.

If the map was drawn when the park was new, it would have been reasonable to assume that the road would be completed soon enough, and draw it in early. (“It’s finished on the map!”) But the scan shows a 1962 copyright date at the bottom. That’s six years into the landslide, more than enough time to realize the road was never going to be completed and paint over it for the latest printing. That makes me wonder why they hadn’t fixed it by then.

A story’s been making the rounds about a software project that enforced a no-LLM-use policy by using prompt injection to delete itself. An “AI” agent-using coder filed a bug report (understandable), but filled it with a bunch of long-winded, clearly LLM-generated comments.

I looked at those comments. I can’t say I read them, because my eyes started glazing over a couple of paragraphs in. The contrast with the posts by the maintainer and other commenters is…stark.

Though I did notice the bit about how nobody reads the docs, which seems rather telling.

One of the problems with letting an “AI” write for you: If you aren’t reading it, and you assume the person at the other end is just going to summarize it anyway, there’s no motivation to make it readable. And no motivation to think about it and narrow down what’s important. And if you’re rewriting the prompt to focus on what matters most, consider that the prompt would get the idea across more effectively.

We finished re-watching Deep Space Nine a few days ago. Quark’s rants in the second-to-last episode about rolling back the reforms regarding gender and worker protections, complaining that Ferengi society has been infected by a disease, and declaring that if he becomes Nagus he’ll bring back what made Ferenginar great again sound eerily familiar.

There’s even a bit about a latinum-plated toilet seat — I mean waste extractor.

It certainly sounds more like what Musk, Trump and Hegseth have actually been saying and doing than any other kind of “making Star Trek real”. Unless Musk’s obsession with eugenics and passing on his genes is enough stronger than his racism that he plans to make sure Khan exists. (Eeeeew.)

Wait, maybe that’s why Khan is white in the Kelvin timeline.

Seriously, though, the Ferengi have always been an extreme caricature of American culture and capitalism taken to absurd lengths. They were even compared to “Yankee traders” in their first appearance on TNG. In 2016, Trump campaigned as an extreme characature of a conservative, the kind that viewers a decade earlier would have dismissed as unrealistic. And since he won, the GOP embraced that caricature and has remade itself into a political/business alliance that makes Quark look downright progressive by comparison.

After all, Quark once brought up the horrors of Earth’s history: slavery, devastating wars, etc. Ferengi never had government death squads rounding people up off the street for being undesirables. They would have just let someone new in town pay the requisite fee and let them go about their business like a civilized culture.

In retrospect, it’s wild that so many tech people who were hyper-aware of the fact that Microsoft’s dominance in the 1990s and 2000s was due to more to marketing (“never underestimate Microsoft on marketing”) than technical merits…fell for the idea that a “marketplace of ideas” would coalesce around the best ideas, and not just the loudest ones.

I’ve long disliked the term “culture war,” partly because it’s tossed around in a way that trivializes the issues and partly because “War on whatever” framing tends to confuse the issues.

But I keep thinking of a line in Cat Valente’s novel Space Opera about what war is. And when it comes down to it, what we’ve got now is a war: It’s about who gets to be treated as a person, and who doesn’t:

But in the end, all wars are more or less the same. If you dig down through the layers of caramel corn and peanuts and choking, burning death, you’ll find the prize at the bottom and the prize is a question and the question is this: Which of us are people and which of us are meat?

I really wish GNOME’s “Oh No! Something went wrong!” screen would let me restart just the crashed components instead of forcing me to log out completely. Or let me decide if I’m willing to continue without whatever crashed. If the audio broke, and I’m not doing anything that needs sound right now, it shouldn’t block me! — just like if the extension I’m

Heck, I’d even settle for just being able to interact with the applications that are still running. I can see them on the overview, and the thumbnails still update! Fortunately I haven’t had it happen while I was editing something, but I’d sure like to be able to click on “save” if I need to!

When I first started using Linux, it was a lot less stable than it is today, but when something broke, I always felt like I could fix it. Even if a window manager crashed, I could relaunch it and pick up where I left off.

I keep coming back to GNOME, but it has an infurating tendency to weld the hood shut on things that “just work” most of the time, because you should never need to fix that issue! (See also: Geary not offering manual sync, GNOME Software wanting to reboot the system when you update Firefox, etc.)

»All pages site-wide with this tag