I do think considering the average use case is paramount. That's why I think remote encrypted contacts storage should have never been implemented: most people w

I do think considering the average use case is paramount. That's why I think remote encrypted contacts storage should have never been implemented: most people won't choose strong passwords. Giving them the false notion that their sensitive stored data is cryptographically indecipherable is wrong. As it stands now, people who create a Signal PIN aren't even warned about the security implications of using weak numeric PINs, which is among the worst of all possible worlds. If this feature is critical, it should have been gated behind prominent passphrase entropy warnings, along with the data being put at risk [1], or it should have enforced actual strength requirements. Signal is still better than most other messengers. I am mostly comparing it to its former self. And its former self worked flawlessly without needing to upload persisted contacts information. 1. https://github.com/signalapp/Signal-Android/blob/main/libsignal/service/src/main/proto/StorageService.proto https://github.com/signalapp/Signal-Android/blob/main/libsig...