Honeypot.net

I got an email this weekend that Apple was updating my Apple Card’s expiration date. The old date would work for purchases through the end of the year.

Today Apple Music said I can’t play songs until I update my payment info. I clicked the offered button and got an unworking form with unlabeled, required fields.

When I guessed the right value for the unlabeled field (which wasn’t asking for my name; it didn’t allow me to type a space character), it told me it already had that card information on file. I closed that and went into System Settings > me > Payment & Shipping. There was no way to update the payment information there. A quick trip to Kagi said I have to update that through the App Store app instead.

So I went into that app and clicked Manage Payments. It prompted me to enter my credit card info there. That didn’t work, once again because that card was already on file. I clicked the Back button on that form and it took me to a different screen I hadn’t seen before that listed my payment methods. The form on the new screen wouldn’t let me edit my Apple Card, but it did allow me to delete that card altogether and add it right back. That seems to have been the right combination of incantations. I can listen to music again.

To recap:

• Apple made changes to my Apple Card.
• They didn’t apply those changes to their own internal system.
• The prompt for me to do it myself didn’t work.
• Neither did the second place I tried.
• Neither did the third.
• …until a random button click took me to the hidden screen I needed in the first place.

Does anyone at Apple use this themselves? I’m doubtful.

Last night we said goodbye to Gigi after a sudden medical event. She went to sleep surrounded by a heartbroken family who loved her very much.

Goodnight, sweet pup.

If you want to really understand how Internet protocols work, I heartily recommend writing your own on top of UDP. You don’t have to work in the kernel. You can use just about any language you want. You can make it as simple or complex as you desire. Try it sometime! It’s instructive.

I was making the bed while the cat laid on it, surfing the waves of bedding as I shifted things around carefully to avoid chasing her off. Then it struck me that I’ll never be able to make the dog into the bed again, which was one of her favorite things. That hit unexpectedly hard.

Miss you, girl.

The comet C/2023 A3 Tsuchinshan-ATLAS as taken from our suburban back porch right in the middle of the Bay Area. It was easily visible to the naked eye. If you haven’t gone outside to look at it yet, do it!

Silent Hill 2 is not fun. It’s beautiful. It’s immersive. It’s engaging. But it’s not fun. Everything that happens comes back to your decision to do this to yourself. No one forced you to go there. To ignore the warnings. To follow a fog-enshrouded vaguely human but not quite shape through a gore-smeared hole in the base of a wall. You chose to. And now there are consequences.

It’s excellent and you should totally play it. I can’t say you’ll exactly enjoy it, though.

Python 3.13 launched today. I’ve done it. I’ve lived long enough to see a less-GIL’ed Python released to the public. Until now there’s been an unvirtuous cycle:

Python isn’t good at running CPU-intensive threaded code. → No one writes code like that. → There was no pressure to remove the GIL because no one writes code that would benefit from it. → Repeat.

I hope this is the first giant step toward good Python multithreading.

Ugh, “walkable” cities. 🙄

To get dinner, we had to:

• Walk a couple of blocks
• Pause for my wife to pet a dog
• Watch sunset at a table behind a taqueria
• …where my wife had to pet another dog
• Stroll past the monthly outdoor fest with live bands and a bunch of vendor booths
• Wait for my wife to pet a dog again
• Walk back past the European market, where we walked in to get dessert snacks
• …and for my wife to pet the owner’s dogs

Simply intolerable.

From “Google hails move to Rust for huge drop in memory vulnerabilities”:

In Google’s own shift towards using memory safe programming languages there has been a significant drop in the number of memory-related vulnerabilities, with memory safe vulnerabilities down to 24% in 2024 - a stark contrast from 2019 [76%] and well below the industry norm of 70%.

Memory safety is not the same as safety. You can still write bad logic in any language. It “just” gets rid of the majority of bugs so that programmers can concentrate on the more interesting parts.

Also, yes, of course you can write safe C code. No one with a large codebase ever has in practice, but it’s at least hypothetically possible. Wouldn’t rather not have to, though?

It astounds me that in 2024 there’s no canonical way to select which CSS to use for a web browser on a phone screen. You have to guess at how many CSS pixels wide your target device is. If next year’s device is any larger than a hardcoded threshold, they may get your desktop layout instead.

I know there are people who’ve made their careers out of memorizing all the edge cases of this monstrosity. Those are lifetimes lost to toil because no one can agree on an official way to look nice on a cell phone, or the one true way to center an image. It’s madness.