3 ms·
A thing long overdue, I’d say! Have you thought about making some ELI5 explainer on how the algo essentially works? The post you link to is already a great st
by wizzard0 4y ago
A thing long overdue, I’d say!
Have you thought about making some ELI5 explainer on how the algo essentially works?
The post you link to is already a great start, I feel like it’s just a question of a little editing work and maybe more examples
— for the nerds to get interested and actually read the paper
— for the users to understand privacy properties better (eg why this is better than TLS in case of a server infected with malware, etc
— and also things which it doesn’t do, which would calm anxiety in those who /need/ to understand the limitations to feel safe
— and to keep devs from thinking it’s a magic pixie dust and over-promising users, only to get hacked
- blintz 4y agoA big part of this company has turned out to be figuring out how to explain FHE :) I'm working on a higher-level "why/how to use this" blog post that should help. Thanks for the suggestions!
- mike_d 4y agoAn advisor once told me "never build a business where your customers don't know they have the problem you solve." Aside from the Apple and Googles of the world, how do you convince engineers and their managers that your solution solves a problem? Sure privacy is nice, but most consumers either don't think about it or simply assume it isn't private no matter what you tell them.
- kobalsky 4y agoI'm trying to understand too so please correct me if this is wrong. As I was able to gather it's like, you send them a camera which can only hold one picture. Then they use this camera to scan every document they have. The trick is that this camera will only save the picture, without revealing them which one, of the record you are interested in. When they finish scanning all the documents, they send you back the camera which now has a single picture of the document you wanted, and than only you can access.