Oh, that wasn’t a dig at you! I just find it entertaining how the same technology with the same risks and impact on the future web are treated completely differently based on what company puts their name on the blog post.

FWIW both use cases seem good to me, Kagi’s for using the privacy enhancing properties and Cloudflare’s for decreasing the need for their CAPTCHA/bot blocking software to be cranked up to the level it’s at now. For now only Safari and Kagi’s addons are using the tech (Cloudflare turned off their experiment) so there’s no reason to be bothered at the moment anyway.