Do pay attention. The hash function employed is specifically designed to be resistant to basic image manipulation. If you put a kiddie abuse image into photoshop and convert it to a photo of the Eiffel Tower that would obviously yield a different hash. But then it wouldn’t be a kiddie abuse image, which is the whole point of having an identifying hash.
It is software scanning an image.
It is software, decididing what resembles (!!) something bad.
Apple - of course - always releases perfect software without any bugs. Ermmm…. In the exceptional cases, ermmm… where bugs crop up, they are immediately removed. Ermmm…. Sometimes. Or not. Whatever the reason.
iOS is currently at version 14.7.2.
You can view this is quick reaction on Apples part, but you could also ask the question: Why so many updates, down to few days apart? In less than a year. Software, that has been through several public beta tests, and hopefully internal Apple quality control and code vetting. Or a sign of sloppy on bad programming, where fixing one bug, introduces a new or many new bugs, to be fixed later?
What to look for is based on what someone, you don’t know, has asked (forced?) Apple to look for. That Apple legally cannot verify; in many countries the thought of Apple being allowed to verify anything not heavily “redacted” would be regarded as hilarious.
In other words, YOU also have to blindly trust, that everything released to Apple has been produced consciously and thorough with the best of intentions - without errors or willfull malice.
Do you believe, that all… ermmm… distinguished members of US Congress would even qualify for such a feat in matters far less critical for the well-being of countless innocent people around the world?
Will Apple even want or be able or even be allowed to keep a public tally of unwanted “side effects”? Would you want to be the target of a ‘side effect’?
Criteria you do not know, code you have no insight to - you or competent programmers cannot, ermmm, are not allowed to verify the quality, the reach and the basic workings of the code, as it looks now.
This code will be made available for use by third parties: presumably vetted (or not) by Apple. If governments are involved, Apples vetting procedure may turn out be just “Yessir. Will do!”, where some - if not all - governments are involved. They can - maybe - protest, but in most cases this will not necessarily have any effect. Public protest on Apples part on technical matters unknown to anyone is a no-no. Unless Apple leaves that market, Apple does, what the authorities demand. Law varies a LOT between countries, and especially ermmm…. ”interpretation” leave governments a LOT of “wiggling room”.
If you get flagged in the end, how will you be treated? Depending on who you are: color, religion and - especially - wealth and influence. The latter two is the only universally mitigating circumstances.
Will treatment even be equal in all states or counties of the US?
What about treatment in the roughly 200 countries of this world? Some have dramatically different views on human rights and how suspects can be treated.
Innocent or not.
Note: I have - until now - not even mentioned the issue of “privacy”, which you may choose to volunteer to give up. Others may not.
Regards