There are specific details about how the mechanism works like the cookie name (__obi) that can help defenders.

I'm not aware of any filter lists that blocks based on cookie name. It's almost always done at the URL level. Moreover it's bog standard 3rd party cookie tracking. At least for the purposes of "help defenders", there's nothing in the blog post that couldn't be found in 10s with browser devtools.

▲

zahlman 4 hours ago | parent [-]

> there's nothing in the blog post that couldn't be found in 10s with browser devtools.

The audience of people who can read and understand an explanation like this one is probably quite a bit larger than the ones who can replicate the experiment themselves.

	▲	TeMPOraL 4 hours ago \| parent \| next [-]
		And larger still than the ones who would bother to replicate the experiment themselves. Yeah, I could tell few sentences in that it's Claude-written article. The style has become that distinctive. Hell, a third of the articles I opened on the HN front page today carried that distinctive style. Doesn't really matter if the content is worth it (and I just realized that recognizing Claude in this also makes me wary of ways this could paper over key details - at this point I start to recognize from my own experience where Claude may be papering over something it didn't actually bother to check).
	▲	gruez 4 hours ago \| parent \| prev [-]
		That just goes back to my original point, which is that this is AI slop and everyone would be better off if OP referenced a canonical description of what's happening, rather than wasting everyone's time by generating 1200 words of AI slop for them to wade through, all for some "threat intelligence" newsletter.