4 ms·
The use-cases could be, for example, payment processors storing customer data, encrypted webmail (where you're able to search w/o downloading all your emails),
by michwill 12y ago
The use-cases could be, for example, payment processors storing customer data, encrypted webmail (where you're able to search w/o downloading all your emails), "encrypted evernote" :-)
Yes, it will be open source once available
- bcg1 12y agoOh, sounds good. So even though you can't get at the data on the server, you are able verify that it is unchanged with correct timestamps, etc. Sounds smart, useful. I presume then that you can support searching on the client side by downloading an encrypted index or something like that? Thanks for the good work guys, best of luck with your project and (ad)venture.
- michwill 12y agoWe support client-side search, that' the whole point. But we don't even have to download all the index, only log(index_size)
- mcintyre1994 12y agoThat's for full text search? This sounds really cool! Excuse the not-very-sophisticated question because I'm not really familiar with the data structures a database typically uses, how do your index sizes compare to a typical sql database or similar indexed similarly for the same sort of queries?
- michwill 12y agoIndex sizes are pretty similar (consider the same). Having the index end-to-end encrypted imposes some limitations though. You have to do several requests when you want to do one query which is obviously slower. Though, still practical. And since the CPU logic happens on the client, in some cases (many simultaneous clients) the performance can be actually better.
- deleted 12y ago[deleted]