@soatok I have read your series :) What I am saying is that, unless I don't recall it correctly, your focus is not on what metadata is available to Signal servers.
For operation purposes, they necessarily have more data than what they claim (i.e. just the phone number, the IP address of the last connection, date of creation and date of last connection).
They have the remaining prekeys from which you can infer when/how many new conversations were created.
Having stuff (like contacts) in the secure enclave is great, but secure enclaves don't have storage, so when you need to restart the task running in the enclave, either you loose all the data, or you store it on disk in an encrypted form to load it back in in the new task. Where is the encryption key for that data? It has to be known by the operators, unless I am mistaken, and if that key is known by the operator, they can decrypt the data on disk.... so the data ain't really secure from the operator and the DoJ?
Signal has to store a token per account to request notification from the Google/Apple notification services. This token is tied to the Signal identity and to a Google/Apple account, so that's something that authorities would want to have, isn't it?
And these are a sample of the data that Signal has to have. I'm not even talking about the data they claim they don't collect and for which we can just blinding trust them.
So yeah, maybe my reply was lazy. But I did publish a conference that required significant work. Let's not ignore that, please.