[ppjet6]

This seems like smoke and mirrors to me:

  Traditionally, in Signal that process has looked like:
  
    The client calculates the truncated SHA256 hash of each phone number in the device’s address book.
    The client transmits those truncated hashes to the service.
    The service does a lookup from a set of hashed registered users.
    The service returns the intersection of registered users.

The phone number space is really not this big.

[detaro]

They acknowledge that in literally the next paragraph, and the entire post is about how they improved on that old state of things. How is that "smoke and mirrors"?

[ppjet6]

Right, my bad. This does look like a sensible solution

[Boulth]

Is this solution deployed in production? The source code says "beta".