michael@0: WEBVTT
michael@0: 
michael@0: NOTE Validate on http://quuz.org/webvtt/
michael@0: NOTE http://developer.mozilla.org/en-US/docs/HTML/WebVTT/
michael@0: 
michael@0: denny01
michael@0: 00:00:22.750 --> 00:00:25.500 align:middle position:50%
michael@0: <v Denny Dude>Hi. I'm here to introduce <b>Procom</b>,</v>
michael@0: 
michael@0: denny02
michael@0: 00:00:25.500 --> 00:00:28.000 align:middle position:50%
michael@0: <v Denny Dude>the <i>new</i> protected communications platform.</v>
michael@0: 
michael@0: denny03
michael@0: 00:00:28.000 --> 00:00:32.500 align:middle position:50%
michael@0: <v Denny Dude>I'm a user myself, and with me is <b>Cally Code</b> the developer.</v>
michael@0: 
michael@0: denny04
michael@0: 00:00:32.500 --> 00:00:36.500 align:middle position:50%
michael@0: <v Denny Dude>First off, <b>Procom</b> is a project composed of <i>several applications</i></v>
michael@0: 
michael@0: denny05
michael@0: 00:00:36.500 --> 00:00:39.500 align:middle position:50%
michael@0: <v Denny Dude>that share logic yielding <i>protected communication.</i></v>
michael@0: 
michael@0: denny06
michael@0: 00:00:39.500 --> 00:00:42.000 align:middle position:50%
michael@0: <v Denny Dude>Let's consider the possibilities.</v>
michael@0: 
michael@0: boss01
michael@0: 00:00:42.000 --> 00:00:47.500 align:middle position:50%
michael@0: <v Anna Boss>Just <i>what are</i> the possibilities? What kind of use cases does <b>Procom</b> serve?</v>
michael@0: 
michael@0: denny07
michael@0: 00:00:47.500 --> 00:00:50.500 align:middle position:50%
michael@0: <v Denny Dude>Well, it includes sending instant messages, chatting...</v>
michael@0: 
michael@0: denny08
michael@0: 00:00:50.500 --> 00:00:54.000 align:middle position:50%
michael@0: <v Denny Dude>voice calls, video streaming, and more.</v>
michael@0: 
michael@0: secretary01
michael@0: 00:00:57.500 --> 00:00:59.000 align:middle position:50%
michael@0: <v Waldo Secretary>Oh my! I'm so bored...</v>
michael@0: 
michael@0: secretary02
michael@0: 00:00:59.000 --> 00:01:02.500 align:middle position:50%
michael@0: <v Waldo Secretary>Waiting for customers to call on this <i>old fashioned</i> phone.</v>
michael@0: 
michael@0: secretary03
michael@0: 00:01:02.500 --> 00:01:04.250 align:middle position:50%
michael@0: <v Waldo Secretary>They can't reach us over the <b>Internet</b>,</v>
michael@0: 
michael@0: secretary04
michael@0: 00:01:04.250 --> 00:01:08.000 align:middle position:50%
michael@0: <v Waldo Secretary>because smartphone apps don't support <b>WebRTC</b> yet.</v>
michael@0: 
michael@0: cally01
michael@0: 00:01:10.250 --> 00:01:14.500 align:middle position:50%
michael@0: <v Cally Code>Sheesh, what's this guy blabbing about, I'm Cally Code the developer.</v>
michael@0: 
michael@0: cally02
michael@0: 00:01:14.500 --> 00:01:20.000 align:middle position:50%
michael@0: <v Cally Code>and I'm here to engineer the <b>Procom
michael@0: platform</b> and the first round of applications.</v>
michael@0: 
michael@0: cally03
michael@0: 00:01:20.000 --> 00:01:23.750 align:middle position:50%
michael@0: <v Cally Code>I'll implement the platform while designing text, voice,</v>
michael@0: 
michael@0: cally04
michael@0: 00:01:23.750 --> 00:01:27.000 align:middle position:50%
michael@0: <v Cally Code>and video based clients across <b>several platforms.</b></v>
michael@0: 
michael@0: boss02
michael@0: 00:01:27.500 --> 00:01:30.000 align:middle position:50%
michael@0: <v Anna Boss>Wait a minute Cally, I'm the <b>boss</b>.</v>
michael@0: 
michael@0: boss03
michael@0: 00:01:30.000 --> 00:01:34.500 align:middle position:50%
michael@0: <v Anna Boss>How are you going to avoid the pitfalls of <i>cross platform</i> development, Cally?</v>
michael@0: 
michael@0: cally05
michael@0: 00:01:35.000 --> 00:01:39.000 align:middle position:50%
michael@0: <v Cally Code>I'll start with a <b>NodeJS</b> project and <b>Socket.IO.</b></v>
michael@0: 
michael@0: cally06
michael@0: 00:01:39.000 --> 00:01:42.000 align:middle position:50%
michael@0: <v Cally Code>Then I'll write a <i>RTCPeerConnection()</i> backend...</v>
michael@0: 
michael@0: cally07a
michael@0: 00:01:42.000 --> 00:01:45.000 align:middle position:50%
michael@0: <v Cally Code>and have clients call <i>getUserMedia()</i>.</v>
michael@0: 
michael@0: cally07b
michael@0: 00:01:45.000 --> 00:01:47.000 align:middle position:50%
michael@0: <v Cally Code>Once I've created <i>data channels</i></v>
michael@0: 
michael@0: cally08
michael@0: 00:01:47.000 --> 00:01:51.750 align:middle position:50%
michael@0: <v Cally Code>and taken care of <b>NAT traversal</b> the <b>WebRTC</b> components are finished.</v>
michael@0: 
michael@0: denny09
michael@0: 00:01:52.000 --> 00:01:56.000 align:middle position:50%
michael@0: <v Denny Dude>Okay, it's clear that <b>Procom</b> is <i>WebRTC-centric</i>...</v>
michael@0: 
michael@0: denny10
michael@0: 00:01:56.000 --> 00:02:00.750 align:middle position:50%
michael@0: <v Denny Dude>but what about the leading mobile
michael@0: platforms that lack a proper <i>web runtime</i>?</v>
michael@0: 
michael@0: denny11
michael@0: 00:02:00.750 --> 00:02:03.500 align:middle position:50%
michael@0: <v Denny Dude>How will you bootstrap web applications on <i>those</i>?</v>
michael@0: 
michael@0: cally09
michael@0: 00:02:04.000 --> 00:02:07.000 align:middle position:50%
michael@0: <v Cally Code>We'll <u>re</u>-use the same logic across platforms</v>
michael@0: 
michael@0: cally10a
michael@0: 00:02:07.000 --> 00:02:09.000 align:middle position:50%
michael@0: <v Cally Code>even those lacking <i>web runtimes</i></v>
michael@0: 
michael@0: cally10b
michael@0: 00:02:09.000 --> 00:02:12.750 align:middle position:50%
michael@0: <v Cally Code>by rendering a web view via <b>Coordova</b> or <b>Phonegap</b>.</v>
michael@0: 
michael@0: cally11a
michael@0: 00:02:13.250 --> 00:02:16.000 align:middle position:50%
michael@0: <v Cally Code>By leveraging the plug in nature of <b>Coordova</b>,</v>
michael@0: 
michael@0: cally11b
michael@0: 00:02:16.000 --> 00:02:19.000 align:middle position:50%
michael@0: <v Cally Code>we can abstract and provide features requiring...</v>
michael@0: 
michael@0: cally11c
michael@0: 00:02:19.000 --> 00:02:23.000 align:middle position:50%
michael@0: <v Cally Code>sensors like <i>accelerometers</i> and <i>proximity</i> sensors.</v>
michael@0: 
michael@0: boss04a
michael@0: 00:02:23.000 --> 00:02:26.000 align:middle position:50%
michael@0: <v Anna Boss>That certainly helps. How will we test <b>Procom</b></v>
michael@0: 
michael@0: boss04b
michael@0: 00:02:26.000 --> 00:02:28.750 align:middle position:50%
michael@0: <v Anna Boss>to verify that it meets requirements?</v>
michael@0: 
michael@0: cally12a
michael@0: 00:02:28.750 --> 00:02:33.000 align:middle position:50%
michael@0: <v Cally Code>We'll employ the <b>QUnit</b> testing framework
michael@0: and have a tiered support model...</v>
michael@0: 
michael@0: cally12b
michael@0: 00:02:33.000 --> 00:02:37.500 align:middle position:50%
michael@0: <v Cally Code>just like <b>jQuery</b> does in order
michael@0: to target a dozen platforms.</v>
michael@0: 
michael@0: denny12
michael@0: 00:02:38.000 --> 00:02:43.000 align:middle position:50%
michael@0: <v Denny Dude>Wow, a dozen platforms. Ubiquity! Ubiquity, ubiquity!</v>
michael@0: 
michael@0: boss05
michael@0: 00:02:44.000 --> 00:02:48.500 align:middle position:50%
michael@0: <v Anna Boss>Cally, how will we package <b>Procom</b> for distribution on so many platforms?</v>
michael@0: 
michael@0: cally13a
michael@0: 00:02:49.000 --> 00:02:54.000 align:middle position:50%
michael@0: <v Cally Code>Boss, we think its best to deploy <i>WGT web widgets</i>.</v>
michael@0: 
michael@0: cally13b
michael@0: 00:02:54.000 --> 00:02:59.500 align:middle position:50%
michael@0: <v Cally Code>Some platforms can work with them directly and we'll
michael@0: automate a repackaging system for the others.</v>
michael@0: 
michael@0: secretary05
michael@0: 00:03:00.500 --> 00:03:06.000 align:middle position:50%
michael@0: <v Waldo Secretary>It seems this would free us all from the <i>vendor</i>
michael@0: <i>lock-in</i> that many providers so cynically enforce.</v>
michael@0: 
michael@0: denny13a
michael@0: 00:03:06.500 --> 00:03:07.500 align:middle position:50%
michael@0: <v Denny Dude>Why yes!</v>
michael@0: 
michael@0: denny13b
michael@0: 00:03:07.500 --> 00:03:10.500 align:middle position:50%
michael@0: <v Denny Dude><i>WGT widgets</i> should fit our design nicely</v>
michael@0: 
michael@0: denny13c
michael@0: 00:03:10.500 --> 00:03:12.750 align:middle position:50%
michael@0: <v Denny Dude>but do you think that we could extend deployment...</v>
michael@0: 
michael@0: denny13d
michael@0: 00:03:12.750 --> 00:03:16.250 align:middle position:50%
michael@0: <v Denny Dude>to embed our packages in browsers and other web applications?</v>
michael@0: 
michael@0: cally14
michael@0: 00:03:17.000 --> 00:03:21.500 align:middle position:50%
michael@0: <v Cally Code>Yes, that's one reason for sticking to <i>web standards</i> in the first place.</v>
michael@0: 
michael@0: boss06
michael@0: 00:03:22.500 --> 00:03:26.000 align:middle position:50%
michael@0: <v Anna Boss>What about <i>cryptography</i>? Do standard web interfaces exist for that?</v>
michael@0: 
michael@0: cally15a
michael@0: 00:03:27.000 --> 00:03:28.000 align:middle position:50%
michael@0: <v Cally Code>Well Boss.</v>
michael@0: 
michael@0: cally15b
michael@0: 00:03:28.000 --> 00:03:32.000 align:middle position:50%
michael@0: <v Cally Code>The <b>W3C</b> has produced the <b>Web Cryptography API</b> standard...</v>
michael@0: 
michael@0: cally15c
michael@0: 00:03:32.000 --> 00:03:34.000 align:middle position:50%
michael@0: <v Cally Code>...but it's not stable yet.</v>
michael@0: 
michael@0: cally15d
michael@0: 00:03:34.000 --> 00:03:36.500 align:middle position:50%
michael@0: <v Cally Code>Until it matures we have good alternatives</v>
michael@0: 
michael@0: cally15e
michael@0: 00:03:36.500 --> 00:03:39.500 align:middle position:50%
michael@0: <v Cally Code>like the <b>Stanford</b> JavaScript crypto library.</v>
michael@0: 
michael@0: cally15f
michael@0: 00:03:39.500 --> 00:03:44.750 align:middle position:50%
michael@0: <v Cally Code>Or implement selectively using <i>native</i>
michael@0: <i>interfaces</i> and plug in via <b>Cordova</b>.</v>
michael@0: 
michael@0: denny14
michael@0: 00:03:45.250 --> 00:03:51.500 align:middle position:50%
michael@0: <v Denny Dude>Oh good! The latter would allow us to optionally tap
michael@0: into <i>hardware crypto processors</i> if they prove secure.</v>
michael@0: 
michael@0: cally16
michael@0: 00:03:52.000 --> 00:03:57.750 align:middle position:50%
michael@0: <v Cally Code>That's right. Like the <i>Intel</i> and <i>AMD</i> implementations, namely <b>AES-NI</b>.</v>
michael@0: 
michael@0: boss07a
michael@0: 00:03:58.500 --> 00:04:00.500 align:middle position:50%
michael@0: <v Anna Boss>Cally, how about the <i>server components</i>?</v>
michael@0: 
michael@0: boss07b
michael@0: 00:04:01.000 --> 00:04:05.500 align:middle position:50%
michael@0: <v Anna Boss>Won't they suffer from typical security problems once put in the <i>cloud</i>?</v>
michael@0: 
michael@0: cally17a
michael@0: 00:04:06.000 --> 00:04:10.000 align:middle position:50%
michael@0: <v Cally Code>Well we'll learned from the mistakes of <i>so many</i> service providers.</v>
michael@0: 
michael@0: cally17b
michael@0: 00:04:10.250 --> 00:04:21.750 align:middle position:50%
michael@0: <v Cally Code><b>Procom</b> will not store keys, anonymize user identities with <b>Tor</b>,
michael@0: and will encrypt all channels via <b>TLS</b> and <b>SRTP</b>, or <b>DTLS</b> and <b>ZRTP</b>.</v>
michael@0: 
michael@0: cally17c
michael@0: 00:04:22.000 --> 00:04:26.750 align:middle position:50%
michael@0: <v Cally Code>The <b>Procom</b> seed service will even employ a <i>dead man's switch</i> by default.</v>
michael@0: 
michael@0: boss08a
michael@0: 00:04:27.250 --> 00:04:28.750 align:middle position:50%
michael@0: <v Anna Boss>Wow, that's a handful.</v>
michael@0: 
michael@0: boss08b
michael@0: 00:04:29.250 --> 00:04:34.250 align:middle position:50%
michael@0: <v Anna Boss>I guess another factor is the open nature of the
michael@0: design and freedom to <i>self host</i> the platform.</v>
michael@0: 
michael@0: denny15a
michael@0: 00:04:37.750 --> 00:04:39.000 align:middle position:50%
michael@0: <v Denny Dude>I've lost track.</v>
michael@0: 
michael@0: denny15b
michael@0: 00:04:39.250 --> 00:04:47.500 align:middle position:50%
michael@0: <v Denny Dude>How does <b>Procom</b>'s focus on web interfaces, open source, standards,
michael@0: and data encryption relate to the <i>future</i> of communication?</v>
michael@0: 
michael@0: cally18a
michael@0: 00:04:48.250 --> 00:04:54.750 align:middle position:50%
michael@0: <v Cally Code>These aspects help <b>Procom</b> benefit users with
michael@0: ubiquity, freedom, and security all at once.</v>
michael@0: 
michael@0: cally18b
michael@0: 00:04:55.000 --> 00:04:58.500 align:middle position:50%
michael@0: <v Cally Code>That's what makes <b>Procom</b> unique among rivals.</v>
michael@0: 
michael@0: boss09a
michael@0: 00:04:59.250 --> 00:05:00.250 align:middle position:50%
michael@0: <v Anna Boss>Sounds great!</v>
michael@0: 
michael@0: boss09b
michael@0: 00:05:00.500 --> 00:05:03.750 align:middle position:50%
michael@0: <v Anna Boss>Get to work you two while I spread the word about <b>Procom</b>.</v>
michael@0: 
michael@0: crowd01
michael@0: 00:05:04.500 --> 00:05:10.500 align:middle position:50%
michael@0: <v Audience>Cheer!</v>