4 ms·
Appreciate this comment, and I'll try to explain a bit more of what takes place under the hood. The codebase of Slimbox can not read the content of your emails
by makemills 6y ago
Appreciate this comment, and I'll try to explain a bit more of what takes place under the hood.
The codebase of Slimbox can not read the content of your emails. Slimbox does not look at the content of the email or the header in fact to determine what is clutter. We instead use the Gmail API to effectively search for clutter.
In a traditional IMAP-based environment, you're right that one would have to process email headers, but the Gmail API allows us to find clutter more efficiently – hence the bold claim regarding the speed of our service.
The only user data that we store in our encrypted database is the user's email address, name, and a list of the senders. We only store this list of senders in order to allow for a UI to enable the user to easily manage senders (the only "read" operation).
I agree it would be ideal if we didn't even have to store the "from" address, and we've looked into obfuscating this as data as well.
- matlin 6y agoThat all makes sense and I think you guys are absolutely doing the right things for what's available to you. I've dealt with the woes of making something relatively straightforward with the Gmail API and having to include a whole FAQ of why Gmail's "This app can ruin your inbox and steal your info" warning isn't accurate to how the app works. I am currently working on making building services with user data a much simpler process but until then keep up the great communication and transparency!
- makemills 6y agoThank you! I just checked out what you're building with Aspen. This looks amazing. Love the clear language too, and the idea that users get their own "tiny piece of the cloud" – such a clear concept. Reminds me of what Tim-Berners Lee is trying to do with Solid, but written in simple terms. Good luck!