0xb1c41c71…cbfcsent to0x86030dbb…3c05·#16,348,347·0xc73c745d…0798e1
devcarrot: I recommend we vote against this. The main issue I have is that this creates a man-in-the-middle attack vector either by whomever is operating the platform or any defects in the software that's used and a false sense of security. Skiff may be interesting as it encrypts skiff-to-skiff emails (in this case emails sent between `@nouns.email` users) and incoming emails at rest but it doesn't magically grant the user the ability to have encrypted communications with "all emails sent and received"; emails from, to, and including non-Skiff users are still sent in plaintext. I believe the prop made this detail ambiguous at best.
I'm also concerned around a centralized location for Nouners' emails, this would be an attractive target for attackers.
I wish the Skiff team the best and would personally be interested in playing with their platform, but I don't believe this proposal should pass due to the ambiguity around privacy.