Why is this not done?
Why is this not done?
If the client is doing it, you need to come up with a system that is resilient to people using a bunch of different devices, getting new phones, etc.
This is a theme about building Signal: they're doing everything on hard mode, because they start from the premise that they don't get to know everyone's contacts. Virtually every other mainstream messaging system, including the ground-up E2E encrypted ones, keep a complete plaintext contact database serverside.
What is the problem with "people using a bunch of different devices, getting new phones, etc" in what I suggested?
If I make a fresh install, then next time a friend messages me, it costs them a few seconds of delay in sending their first message because my client asks them to prove themself.
I don't see the problem, but I imagine there are problems since smarter people than me are not doing it this way. I'd like to understand what I am missing here.
I guess tweaking the difficulty to be actually difficult for a server farm, yet possible for an old device would be the main problem.
We should try to bring this down, not up. And bitcoin showed how quickly the technology catches up with such requirements by using GPUs, ASICs etc.