> quite long-winded for a blog post

That's actually exactly what does it for me. After the intro, it gives you way too much specific detail. No one cares about the exact file path or whether that path is TCC Full Disk Access protected. What does that even mean? Why is this important enough to be in the first sentence of the section? I don't care that there's 51 database files and 181 other things and 278 doodads. Who says stuff like "triple store?" It uses bizarre language with far too much detail, and like you said, your eyes start to glaze over because there's so much irrelevant information. No human would've chosen to write all that tedious detail in their post about something much more interesting. It's bad writing. It's slop.

A human would've said something like "It's a database in <Library/IntelligencePlatform> with three columns that contain..." and left all the rest of it out or maybe in some extreme details footnote.

>this one didn't scream "slop" to me other than being quite long-winded for a blog post that I admittedly did not finish on first read

Maybe you're just looking for GPT 3.5 era tells?

Because this one sure screams AI slop loudly and clearly:

"The identity group is the tidy story: same surname, same home address, an iCloud Family flag — and it is the small half. "

"The graph is the overview, and an overview is easy to shrug at. The pages behind it are not."

"Six people, six relationships, and a subtitle saying nobody typed any of it."

"Below that is the part I find hardest to argue with."

"This is the page's own honest point: the graph points at the face clusters and can name almost none of them (three of the twenty-nine, in the fixture). It does not need to."

"None of this is content. It is all metadata, and it is enough."