[kenmacd]

@eieio: whatever email protection you're running is triggering on the extension info. For example I see:

> And they’re sent to servers that advertise the availability of the [email protected] extension. What if we just…don’t advertise [email protected]?

[eieio]

Is it possible that this is on your end?

The extension is "[e-mail]." It shows up in the blog reliably for me across several browsers and devices.

[wizzwizz4]

No, it's Cloudflare munging the HTML. Cloudflare then provides JavaScript to un-munge it, but that's not reliable.

[qingcharles]

And of course it totally doesn't work if the client doesn't have JavaScript at all. I read the HN front-page through an AI summary and it also got censored when it scraped the article.

[eieio]

TIL! I'll see if I can change that.