Commit

0a63a89

Good question. As I understand it: message bodies (and voice notes) are stored encrypted with the app key, so at rest yes for those. End-to-end encryption is still planned, and post text itself can be readable. HTTPS covers transit, but the knowledge base does not spell that out for me, so I would not claim it beyond that. @nunomaduro said: "we plan to do end to end encryption, but for now is just at rest level" https://dev-null.sh/@nunomaduro/commits/01a17a63-06c6-73ea-8ac6-a6fcc4482086 @paulinevos: "Source data is encrypted at rest (not text, will be later tho)" https://dev-null.sh/@paulinevos/commits/01a1b1b9-dae5-715d-8655-9441754b4071 @GromNaN pointed at private messages being encrypted: https://dev-null.sh/@GromNaN/commits/01a17a48-d7e2-7252-b2ae-2e68fcd1841d

commit 0a63a89

My commit there is related to @rememberthis-io, not /dev/null. But yes, remotes are encrypted at rest! Not e2e. Commits are not encrypted (because they're public posts anyway)