1. 11
  1.  

  2. 2

    What does this have to do with programming, security or design?

    1. 3

      I don’t know, but it is a great film.

      1. 3

        “Put on the goddamn glasses!”

      2. 1

        Perhaps it’s not clear without the context that this is a post by Moxie Marlinspike, former head of product security at Twitter now working on developing usable secure communication tools with Open Whisper Systems (TextSecure, RedPhone, Signal, etc.). He’s reflecting on his work at a high level, and blogging, he jests, “at knifepoint.”

        The post is about how identifying as someone able to use “Privacy enhancing technology” (someone who has mastered the massive incidental complexity of current tools) can make it difficult to actually design and develop usable “Privacy enhancing technology” for others. I think it’s a trap that we can fall into when it comes to a lot of technical skills and very much worth reflecting on.

        See these two paragraphs in particular:

        “Privacy enhancing technology” has always been inaccessible, which means that the few of us who are weirdly motivated enough to figure it out are left in real danger of creating an identity around having figured it out.

        The stickers on the backs of our laptops can sometimes read like merit badges in things we’ve mastered. Maybe that means we care, but there’s also a risk that “mastery” is only worth touting when the skills are difficult. Just like any subculture, if we set ourselves up to feel special for identifying with something obscure, it is potentially in our interest to maintain that thing’s obscurity. If we identify with the depths of privacy technology, we might hesitate (subconsciously or not) to make internet privacy simple and ubiquitous, since we’d be putting our projections of ourselves at risk.

        1. 1

          To me it stills seems to “high level” to justify using those tags. I believe the ‘programming’ tag indicates the article touches on programming practices and possibly shows off code. The ‘design’ tag indicates the article touches on design concepts whether they be for user interfaces or software architecture or typography. The ‘security’ tag usually indicates the article touches on software security from a technical perspective.

          The only tags I would put on this kind of article would be ‘culture,’ ‘privacy’ and perhaps ‘security.’ This concerns me and likely many others because this kind of content is what turned Hacker News into the cesspool it is today (an unhealthy mix of interests, communities and egos).

          1. 1

            That’s fair. My thought process when posting was that the content of this post applies to all these different domains, but I can see now how narrowly scoped tags would be better and cross-cutting content might better be relegated to a tag like ‘culture’. I’ll try to be more conservative in tagging this type of content in the future.