<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0" xmlns:cc="http://cyber.law.harvard.edu/rss/creativeCommonsRssModule.html">
    <channel>
        <title><![CDATA[Stories by jakeok on Medium]]></title>
        <description><![CDATA[Stories by jakeok on Medium]]></description>
        <link>https://medium.com/@clpwn?source=rss-1df638796b7d------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/0*9p7n99HIipHRXFtv.jpeg</url>
            <title>Stories by jakeok on Medium</title>
            <link>https://medium.com/@clpwn?source=rss-1df638796b7d------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Tue, 17 Nov 2026 05:00:16 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@clpwn/feed" rel="self" type="application/rss+xml"/>
        <webMaster><![CDATA[yourfriends@medium.com]]></webMaster>
        <atom:link href="http://medium.superfeedr.com/" rel="hub"/>
        <item>
            <title><![CDATA[Open design problems in privacy]]></title>
            <link>https://medium.com/@clpwn/open-design-problems-in-privacy-7919cd8d11f9?source=rss-1df638796b7d------2</link>
            <guid isPermaLink="false">https://medium.com/p/7919cd8d11f9</guid>
            <dc:creator><![CDATA[jakeok]]></dc:creator>
            <pubDate>Thu, 09 Oct 2014 22:48:24 GMT</pubDate>
            <atom:updated>2014-10-09T22:56:18.696Z</atom:updated>
            <content:encoded><![CDATA[<p><em>Solve these, find your happy place.</em></p><p>After talking with some fellow usability dorkos, there appear to be a couple of outstanding, open design problems in the privacy realm that nobody’s addressed well.</p><p>Here are some things I want to see.</p><h3>Encompassing design language</h3><p>Much of both the visual and written language we use in the security universe can be quickly summed up as incomprehensible to those outside the field.</p><p>We need a visual and written language spec for cryptographic and general privacy concepts that are necessary<em> </em>to convey to users for the sake of preserving security. Some examples:</p><ul><li>Identity (long-term keys)</li><li>Infoleak (what information am I giving away by doing X?)</li><li>Anomaly indicators of various severities (key changes, missing messages, etc.)</li><li>Past and future content security level (is this message secure? what about this one when I hit send?)</li></ul><p>Oh and speaking of weird security terminology…</p><h3>Fingerprints and authentication</h3><p>Verifying that there isn’t a third party capable of seeing messages being transmitted between you and your (hopefully) loved one(s) is <strong>not easy </strong>and it <strong>should be easy.</strong></p><p>We’ve seen SAS, we’ve seen hex fingerprints, we’ve seen all kinds of visual fingerprint encodings. What’s the best way to let people verify there’s no middleperson in a way that’s friendly for meatspace as well as other authenticated channels? Should we care about this issue, or rely on the fact that most of the time, MITM doesn’t happen and take advantage of that in the form of <a href="https://en.wikipedia.org/wiki/User:Dotdotike/Trust_Upon_First_Use">TOFU</a>?</p><p>Maybe we can just give out cryptographic friendship bracelets to everyone that verifies their fingerprints when you shake hands and bypass this issue all together. Either way this is a <em>new burden </em>placed on users migrating from an app that isn’t private to learn what this is.</p><h3>Transcript consistency</h3><p>In the course of a conversation (group or otherwise), lost messages and otherwise inconsistent message history can be a very jarring wrench thrown into your important discussion. In many ways, it’s akin to talking to somebody who is constantly spacing out, forcing you to ask “did you understand that?” without end.</p><p>Especially in group conversations and without a guarantee of messages ever arriving, is there a good way to indicate that the conversation’s context is different for one or more parties? What message is Beyonce actually responding to? That is, is everyone on the same page or not? It’s not easy to do this in a way that’s useful to the user while not overloading them with unnecessary information. I don’t think we have a solution that is goldilocks.</p><p>On top of that, it’s very hard to tell if these inconsistencies are malicious or a side-effect of an honest bad network connection.</p><h3>Your thing</h3><p>Right now this is a list of wants from the perspective of our work on <a href="https://whispersystems.org/">Open Whisper Systems</a> projects.</p><p>If you work on privacy and see a category not here, send me an email (<a href="/service/mailto:me@jake.su">me@jake.su</a>) or say hi on twitter, <a href="https://twitter.com/clpwn">@clpwn</a>.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=7919cd8d11f9" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>