This kind of ambiguity is rampant in technical writing. Example: "There are situations where developers do X instead of Y which is the wrong thing to do." Wait, is X wrong or Y?! You go ahead and assume X is wrong and then figure out later they meant Y is wrong or vice versa. Argh!
I'm not the person you asked, but if I rephrase your question to "Then why do some places with low crime have less police?", then the answer just seems to be common sense.
I worked with Nick's brother Paul for many years at F5. Several years ago I asked him if Nick was Satoshi and he said Nick denied being Satoshi and Paul also added that it wouldn't make sense because "He still owes me money!". Pretty funny. But I guess he could have fooled his own brother.
https://www.reuters.com/markets/us/citigroup-wins-appeal-ove...