17 ms·
This is definitely a big concern and I have thought a lot about it. Storing data like whitelists, whitelist requests, etc. on the device instead of server is pr
by davidajackson 7y ago
This is definitely a big concern and I have thought a lot about it. Storing data like whitelists, whitelist requests, etc. on the device instead of server is probably going to be the best way to minimize potential issues around privacy. One way to do that is to locally store the whitelist and to route the call to the device and then have the device reject the call if not in the whitelist. But it’s slightly more complex than that, because PINs are an option here too. This is an area that I'm going to be working hard on exploring.
I intentionally haven’t added SMS filtering because of these privacy concerns.
I definitely want to focus on privacy because I am as privacy conscious as everyone else on here.
- VentureCurious 7y agoA bloom filter of my contact’s phone numbers that is updated on my device and checked on the server could be a good privacy approach. A small number of false positives (robo calls getting through) would be acceptable if the device still filters or presents the option to accept. PINs could also be a bloom filter on the server, then the device filters on whether the specific PIN entered was single use or has been revoked.
- winrid 7y agoI'd just use the bloom filter a pre reqs to doing an actual query.