No mention of end to end encryption, or encrypted storage. I suppose the primary target is enterprise and people who like when it just works, because I can hardly see a product designed for my "personal data" not allow encryption (unless the business is based around using this data ;))
Also, insert rant about node.js on the desktop and atom-shell because it's a piece of shit here.
Hi @pikzen, thanks for the comment. One of the advantages of our platform is that you're actually paying for us to run it---so we don't have to sell user data to get by.
We don't specifically support end-to-end encryption in the base email API because a centralized holder of keys is little better than no encryption at all. End-to-end encryption is something we'd love to see built on top of the platform though.
We're prepping something special for existing members of the developer program, details will follow shortly :) Unfortunately the timing didn't align perfectly with the TC article, but we definitely haven't forgotten you.
13 comments
[ 2.7 ms ] story [ 48.2 ms ] threadEdit: nope, they actually explained it themselves:
The word ‘nilas’ actually means “young sea ice” that will grow into icebergs.
1. https://nilas.com/docs 2. https://github.com/inboxapp/inbox
Also, insert rant about node.js on the desktop and atom-shell because it's a piece of shit here.
We don't specifically support end-to-end encryption in the base email API because a centralized holder of keys is little better than no encryption at all. End-to-end encryption is something we'd love to see built on top of the platform though.
The repo is available at https:/github.com/MLstate/PEPS
There's also no clear picture as how Nilas any better than other services. What incentive is there to use Nilas over other products?