Hacker News new | past | comments | ask | show | jobs | submit login

not yet - but this is very high on our priority list! If we had built in encryption in this first step, then it wouldn't extended development time by many months. Instead, we chose to release sync first, prove the core local-first technology works and is scalable, and add in encryption in phase 2. The basic protocols and data structures are designed with encryption in mind, so we're excited to start work on that very soon.



I'll add to Wulf's note that we on the team are privacy-conscious, listen to us talk about it here: https://museapp.com/podcast/18-privacy/

We designed the architecture to allow full Signal-style e2ee, but given that there are only two engineers on this we had to cut scope on that for the first release. Now we'll be listening to what our customers ask for in terms of where to prioritize in the roadmap. We have quite a few medical professionals and attorneys using Muse in their professional lives, so we've already heard from some of them on this topic.




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: