WEBVTT - How Periscope Works 0:00:04.360 --> 0:00:07.520 Get in Text with Technology with tex staff Chrome hast 0:00:07.720 --> 0:00:14.880 Works dot com as Welcome to Text Stuff. I'm Jonathan 0:00:14.920 --> 0:00:17.800 Strickland and today and you're going to talk about how 0:00:18.000 --> 0:00:22.000 periscope works. And a few of you are actually watching 0:00:22.040 --> 0:00:25.599 this live, which means you get to see what I'm 0:00:25.640 --> 0:00:29.200 saying before this podcast goes live. So if you're listening 0:00:29.200 --> 0:00:32.600 to this on your little podcast tracker, just know you 0:00:32.640 --> 0:00:35.720 had the opportunity to see the magic as it was happening. 0:00:35.920 --> 0:00:37.600 But you can talk to the people who were there 0:00:37.840 --> 0:00:41.040 and they'll tell you the story anyway. Really, today's episode 0:00:41.080 --> 0:00:44.839 is about Periscope and another app called mere Cat, and 0:00:44.920 --> 0:00:48.600 to a wider extent, the trend towards live streaming in general. 0:00:49.080 --> 0:00:51.640 So live streaming has been around for a while. It's 0:00:51.680 --> 0:00:54.880 not that new um and it's been growing in popularity 0:00:54.960 --> 0:00:57.000 for quite some time, and in some circles it's kind 0:00:57.000 --> 0:00:59.560 of old news. There were a lot of early examples 0:00:59.600 --> 0:01:02.760 like you Stream and justin TV, which I've talked about 0:01:02.800 --> 0:01:05.880 before on Tech Stuff, and those allowed users the chance 0:01:05.959 --> 0:01:09.800 to broadcast using a simple setup of a computer, a microphone, 0:01:09.920 --> 0:01:12.080 a webcam and as long as you had a good 0:01:12.080 --> 0:01:16.640 Internet connection, you were good to go. Then came Twitch. 0:01:17.480 --> 0:01:19.880 Twitch is really I think we have to thank Twitch 0:01:20.160 --> 0:01:25.280 for truly bringing live streaming to a new level. It 0:01:25.360 --> 0:01:27.679 started off as kind of a spinoff of justin TV, 0:01:28.160 --> 0:01:31.039 but it went on to be so incredibly successful that 0:01:31.080 --> 0:01:35.760 it eclipsed Justin TV, got way bigger, and eventually it 0:01:35.840 --> 0:01:39.800 replaced it completely. Justin TV went away, Twitch stayed. Twitch 0:01:39.880 --> 0:01:42.720 is a service designed to allow gamers to stream their 0:01:42.720 --> 0:01:46.360 gaming activities live to an audience, and gamers can use 0:01:46.400 --> 0:01:48.720 various setups to broadcast not only the game they're playing, 0:01:48.760 --> 0:01:51.880 but a video of themselves as they play. It very 0:01:51.920 --> 0:01:55.400 popular service out there. At the same time, there were 0:01:55.560 --> 0:01:59.520 video calling services that became popular, stuff like Skype, FaceTime, 0:01:59.600 --> 0:02:02.240 Google Hangouts, all of these making it easier to use 0:02:02.280 --> 0:02:04.320 a mobile device to do a live video call with 0:02:04.360 --> 0:02:07.960 someone else. And you could do a live broadcast hangout 0:02:07.960 --> 0:02:10.320 from Google to stream through YouTube if you wanted to. 0:02:10.440 --> 0:02:13.720 But there wasn't really a streamlined way to use a 0:02:13.760 --> 0:02:18.000 mobile device to live stream content to a broad audience. 0:02:18.120 --> 0:02:22.079 It just wasn't easy. So back in two thousand thirteen, 0:02:22.400 --> 0:02:25.920 there was a man named Cavan b Core who was 0:02:25.960 --> 0:02:28.919 traveling to Istanbul and at the time he was the 0:02:28.960 --> 0:02:33.520 general manager and senior executive of Blackboard Mobile. He had 0:02:33.560 --> 0:02:36.320 become a member of the senior executive team after his company, 0:02:36.520 --> 0:02:40.680 Terribly Clever Design, had been acquired, and his interest up 0:02:40.680 --> 0:02:42.760 to that point had been in developing apps that made 0:02:42.760 --> 0:02:45.639 it easy for students and faculty to access and use 0:02:45.800 --> 0:02:50.840 campus data. Also, around that time, Istanbul was not a 0:02:50.960 --> 0:02:55.040 terribly safe place to be. There were these escalating political protests. 0:02:55.320 --> 0:02:58.120 They were getting violent, they were going on in the city, 0:02:58.520 --> 0:03:02.280 and he wanted to know if these protests were happening 0:03:02.440 --> 0:03:05.360 in geographic regions close to where he was planning on 0:03:05.480 --> 0:03:08.680 staying when he traveled Istanbul, and he was having trouble 0:03:08.840 --> 0:03:12.000 finding that information online and news outlets. He said they 0:03:12.040 --> 0:03:15.000 moved too slowly, they were too general, they weren't specific enough. 0:03:15.240 --> 0:03:17.600 He wanted to be able to look in on very 0:03:17.639 --> 0:03:21.639 particular places within Istanbul, and he used Twitter to keep 0:03:21.680 --> 0:03:24.680 an eye on the situation in real time, but found 0:03:24.760 --> 0:03:27.040 himself wishing that there was some way he could view 0:03:27.160 --> 0:03:30.360 live video of the scene from there. Now you could 0:03:30.480 --> 0:03:33.880 watch recorded video after he'd been uploaded and processed, but 0:03:33.960 --> 0:03:38.360 by then it's it's pretty late. So after all of that, 0:03:39.680 --> 0:03:42.640 knowing that tons of people have smartphones, tons of people 0:03:42.680 --> 0:03:46.000 have the ability to shoot video and record video. Why 0:03:46.040 --> 0:03:48.920 not have a live streaming app that combines something like 0:03:49.040 --> 0:03:51.840 a video recording program with a video calling service and 0:03:51.920 --> 0:03:54.360 make it live streaming. So he would go on to 0:03:54.480 --> 0:03:58.280 partner with a guy named Joe Bernstein to create such 0:03:58.320 --> 0:04:00.840 an app. Now, they you that it would need to 0:04:00.880 --> 0:04:03.760 give people the opportunity to turn a phone into a 0:04:03.800 --> 0:04:08.360 camera and broadcast that live across the Internet. They also 0:04:08.400 --> 0:04:10.760 saw the need to make the experience interactive rather than 0:04:10.800 --> 0:04:15.480 a simple stream to viewer experience. So they also knew 0:04:15.520 --> 0:04:18.000 that the experience needed to be interactive and not just 0:04:18.080 --> 0:04:21.799 a simple stream to viewer experience. So for example, I'm 0:04:21.839 --> 0:04:24.960 streaming right now on Periscope as I record this, and 0:04:25.000 --> 0:04:27.839 I can look on my app and see responses. I 0:04:27.839 --> 0:04:30.640 can see people chatting about what's happening. I can see 0:04:30.640 --> 0:04:34.320 people giving me hearts if they enjoy it, and as 0:04:34.480 --> 0:04:38.279 as people are saying it's awesome and how to back 0:04:38.360 --> 0:04:42.599 you ps shaggy. So anyway, these two envision and app 0:04:42.640 --> 0:04:45.880 that would allow people to share anything from an historic 0:04:45.920 --> 0:04:51.400 event unfolding in real time to just simple everyday activities 0:04:51.400 --> 0:04:53.960 of their daily lives. They also wanted to include features 0:04:53.960 --> 0:04:56.560 that would allow viewers to interact in some way by 0:04:56.560 --> 0:05:00.839 giving feedback or questions, or just generally express love for 0:05:00.920 --> 0:05:04.960 what's going on. So the two founded Periscope in February 0:05:05.279 --> 0:05:09.400 two thousand fourteen. And what's the first thing you do 0:05:09.480 --> 0:05:12.839 when you've found a new internet startup company, That's right, 0:05:13.200 --> 0:05:16.200 you beg for money. They sought a round of seed 0:05:16.320 --> 0:05:19.840 investment from Angel Investors, which included Scott Belski of Adobe, 0:05:20.040 --> 0:05:22.960 and they raised a few million bucks to start off. Now. 0:05:23.000 --> 0:05:26.760 Their pitch included describing periscope as being similar to teleporting 0:05:26.800 --> 0:05:29.000 to a distant location to see what is going on 0:05:29.080 --> 0:05:32.240 at that exact moment, and it held a little bit 0:05:32.240 --> 0:05:36.679 more of a exciting prospect than just watching a prerecorded video. 0:05:36.720 --> 0:05:40.280 You could actually be their live while it's happening. Now. 0:05:40.320 --> 0:05:44.080 In lateen they met with Jessica ver Really, the director 0:05:44.200 --> 0:05:47.760 of corporate Development and Strategy for Twitter, and for Really 0:05:47.880 --> 0:05:52.200 was impressed and introduced them to Twitter CEO Dick Costolo 0:05:52.360 --> 0:05:55.520 and Twitter co founder Jack Dorsey, who were in turn 0:05:56.120 --> 0:06:01.479 also impressed. So this goes on. They end up having 0:06:01.480 --> 0:06:04.760 a great conversation and before long, Twitter makes an offer 0:06:04.800 --> 0:06:08.360 to buy Periscope to acquire the company, and apparently some 0:06:08.440 --> 0:06:12.080 other entities were also interested in buying Periscope, so that 0:06:12.160 --> 0:06:15.159 helped push up the price. The founder said that it 0:06:15.279 --> 0:06:20.040 was a fortuitous timing. The amount itself was not made public, 0:06:20.640 --> 0:06:22.719 but a lot of early reports said it was somewhere 0:06:22.720 --> 0:06:26.120 in between seventy and a hundred million dollars, so not 0:06:26.279 --> 0:06:30.240 chump change. Periscope accepted Twitter's offer and the company was 0:06:30.320 --> 0:06:33.560 acquired in January two thousand fifteen. But Twitter kept it 0:06:33.680 --> 0:06:36.200 quiet for a little bit longer for reasons I will 0:06:36.200 --> 0:06:38.960 get into in a moment. Let's just say it was 0:06:39.000 --> 0:06:42.880 a gotcha kind of approach. See net reported that according 0:06:42.920 --> 0:06:47.400 to a regulatory filing, Twitter had spent eighty six point 0:06:47.440 --> 0:06:52.040 six million dollars total on two acquisitions. That was Periscope 0:06:52.200 --> 0:06:55.239 as acquisition number one, and a social media startup company 0:06:55.279 --> 0:06:58.400 called Niche or Niche if you prefer, and people a 0:06:58.480 --> 0:07:01.520 Niche said the purchase was a about thirty million dollars 0:07:01.560 --> 0:07:03.679 for their company, so that I put Periscope in around 0:07:03.680 --> 0:07:07.000 fifty six million dollars or so, so less than what 0:07:07.080 --> 0:07:10.800 some reports were saying. And honestly, there are a lot 0:07:10.800 --> 0:07:13.000 of different accounts for this, and it hasn't been made 0:07:13.000 --> 0:07:16.400 completely public, so somewhere between fifty six million dollars and 0:07:16.400 --> 0:07:20.920 a hundred million dollars. That's a small margin of error, right. Anyway, 0:07:21.720 --> 0:07:23.920 another live streaming app was getting a lot of buzz 0:07:24.520 --> 0:07:30.720 right around spring of this year called mere Cat. So 0:07:31.600 --> 0:07:34.920 mere Cat launched in late February two fifteen, and it 0:07:34.960 --> 0:07:39.280 was built by a group called Life on Air Incorporated. 0:07:40.040 --> 0:07:42.840 That was a team headed by Ben Ruben, and mere 0:07:42.920 --> 0:07:46.280 Cat was leveraging Twitter's social graphs, so you could sign 0:07:46.320 --> 0:07:49.920 into mere Cat through Twitter and access your followers. That way, 0:07:49.960 --> 0:07:53.000 followers could get alerts whenever you were going live on Merecat, 0:07:53.320 --> 0:07:57.160 they could comment on videos, but those videos, those comments 0:07:57.200 --> 0:07:59.840 were going through Twitter, so actually the comments on Mercat 0:08:00.000 --> 0:08:04.160 would get published onto Twitter to everybody. Not everyone was 0:08:04.200 --> 0:08:07.800 crazy about that. Mere Cat made a particularly big splash 0:08:07.880 --> 0:08:10.840 at a little event called south By Southwest, And if 0:08:10.880 --> 0:08:14.760 you're not familiar with south By Southwest, it's a gigantic 0:08:15.120 --> 0:08:18.720 festival that takes place in Austin. It incorporates music and 0:08:18.800 --> 0:08:24.400 movies and what they call interactive or internet based uh 0:08:24.600 --> 0:08:28.160 stuffed lost startup companies end up using south By Southwest 0:08:28.200 --> 0:08:30.560 is a place to either launch a new product or 0:08:30.560 --> 0:08:34.320 to announce new features to existing products. It's really a 0:08:34.360 --> 0:08:36.599 place if you aren't going to interactive, It's really a 0:08:36.600 --> 0:08:40.280 place for you to network, literally, to meet other people 0:08:40.600 --> 0:08:43.840 and convince them that your stuff is the important stuff 0:08:44.240 --> 0:08:46.959 and that people should really pay attention to you. It's 0:08:47.040 --> 0:08:48.959 if you can get people on board with your product 0:08:49.040 --> 0:08:52.120 of south by Southwest that usually spills over to a 0:08:52.200 --> 0:08:55.960 lot of attention immediately following it. So mere Cat raised 0:08:55.960 --> 0:09:00.120 about twelve million dollars in March two thousand fifteen. But 0:09:00.240 --> 0:09:04.600 that same month, that's when Twitter announced that it had 0:09:04.640 --> 0:09:07.199 purchased Periscope. It had done that back in January, but 0:09:07.280 --> 0:09:09.920 kept it quiet until March, and I think a big 0:09:09.960 --> 0:09:12.120 reason for it was to steal a lot of thunder 0:09:12.120 --> 0:09:14.600 from meercat. Twitter also did something else that some people 0:09:14.600 --> 0:09:19.000 thought was kind of dirty pool. Twitter cut the social 0:09:19.040 --> 0:09:23.120 graphic access off of mere Cat. So mere Cat had 0:09:23.120 --> 0:09:28.240 been depending upon Twitter to use that that platform to 0:09:28.400 --> 0:09:31.760 leverage the value of their service, and now Twitter saying, yeah, 0:09:31.800 --> 0:09:33.959 you know, we're gonna come out with our own now, 0:09:34.160 --> 0:09:37.080 so you don't get to do that, And that caused 0:09:37.080 --> 0:09:39.600 a bit of a stir so. Merecat and Periscope do 0:09:39.720 --> 0:09:42.520 similar things. They both allow users to live stream from 0:09:42.520 --> 0:09:45.559 their mobile devices, and both allow followers to watch and 0:09:45.600 --> 0:09:48.960 comment on them. But mere cats comments at the time 0:09:49.040 --> 0:09:52.040 all went through Twitter, so some people would be reluctant 0:09:52.080 --> 0:09:54.520 to comment on a video as it's happening because they 0:09:54.559 --> 0:09:57.840 know that the entire world could see the messages. And 0:09:57.920 --> 0:10:02.000 mere cats broadcasts, at least first, were truly live, so 0:10:02.040 --> 0:10:04.559 if you missed it, they were gone. You had no 0:10:04.640 --> 0:10:08.440 opportunity to see that stuff. You had to be there. Uh. Now, 0:10:08.480 --> 0:10:11.200 you can use some additional tools to expand Mercat's features 0:10:11.240 --> 0:10:13.680 so that you can watch videos after they've happened, or 0:10:13.760 --> 0:10:16.920 you can comment outside of Twitter. You can actually comment 0:10:17.000 --> 0:10:19.920 within merecat itself, but at the time that was not 0:10:19.960 --> 0:10:23.160 the case. Periscope when it launched, had a few more 0:10:23.200 --> 0:10:25.920 bells and whistles. So let's talk about what the app 0:10:26.000 --> 0:10:28.640 looks like and what it's features are. So this is 0:10:28.640 --> 0:10:30.439 gonna be really boring to the people who are watching 0:10:30.520 --> 0:10:34.000 right now because you already know you're doing it. But 0:10:34.080 --> 0:10:36.600 for everybody else, here's what periscope is all about. Oh 0:10:36.640 --> 0:10:39.800 and by the way, tech Crunch really dissed Meercat. When 0:10:39.840 --> 0:10:42.760 it came out, tech Crunch called it a rough shot 0:10:42.840 --> 0:10:47.760 app built in ten days ouch uh. In fact, it 0:10:47.800 --> 0:10:50.280 took about eight weeks according to Ruben to build it, 0:10:50.320 --> 0:10:53.720 but still and it took years of developed development beyond that. 0:10:54.280 --> 0:10:57.080 So let's talk about periscope, what it looks like and 0:10:57.240 --> 0:11:00.640 the features it has. First. Obviously, the most important thing 0:11:00.679 --> 0:11:03.440 is you can live stream from your mobile device. You 0:11:03.480 --> 0:11:05.800 can do this to the general public like I am 0:11:05.800 --> 0:11:08.240 doing right now. Anyone who has a link to that 0:11:08.320 --> 0:11:10.880 periscope can see what you are doing. Or you can 0:11:10.920 --> 0:11:14.359 broadcast to just your followers or a subset of your followers. 0:11:15.160 --> 0:11:18.080 Viewers can watch live streams on computers, but if they 0:11:18.080 --> 0:11:20.200 do that, they can only be passive viewers. There's no 0:11:20.240 --> 0:11:23.360 interactivity built into the browser version of periscope right now. 0:11:23.679 --> 0:11:25.839 If you want that interactivity, you have to download the 0:11:25.840 --> 0:11:28.160 app to your smartphone, and if you watch a live 0:11:28.200 --> 0:11:31.040 stream through the periscope app, you can interact by chatting 0:11:31.160 --> 0:11:34.400 or you tap the screen and that sends hearts. Now 0:11:34.440 --> 0:11:36.920 the hearts show up on screen. Can anyone Can anyone 0:11:36.960 --> 0:11:38.640 send me some hearts while I talk about this. That 0:11:38.800 --> 0:11:41.120 makes me feel better. But the hearts show up on 0:11:41.200 --> 0:11:44.080 screen and indicate that people are enjoying what they see. 0:11:44.240 --> 0:11:48.040 Hearts have also come into play in rankings, so accounts 0:11:48.040 --> 0:11:50.360 that get a lot of hearts get more visibility in 0:11:50.440 --> 0:11:54.280 the periscope app. Um when you start looking for periscopes 0:11:54.320 --> 0:11:56.720 to watch, the ones that accumulate a lot of hearts 0:11:57.240 --> 0:11:59.880 are the ones that go to the top of those lists. 0:12:00.360 --> 0:12:04.520 I am so far behind the leaders in this space 0:12:05.080 --> 0:12:09.559 that unless you just obsessively tapped the screen every time 0:12:09.600 --> 0:12:11.880 I go on periscope, I won't ever show up on 0:12:11.920 --> 0:12:15.319 that list, which is okay. And unlike Merecat, the chatting 0:12:15.320 --> 0:12:17.959 doesn't go to Twitter. All of that chat remains in 0:12:18.000 --> 0:12:20.640 the periscope app, so you don't have to worry about 0:12:20.640 --> 0:12:24.640 broadcasting your questions or comments to the whole world. It's 0:12:24.679 --> 0:12:27.400 just the people who are watching. Although if you do 0:12:27.480 --> 0:12:31.960 watch the video stream after it goes offline, then you 0:12:32.000 --> 0:12:34.559 still have that issue. Oh and I see that I'm 0:12:34.600 --> 0:12:37.480 stuttering a bit online, so that's fun. Once a stream 0:12:37.559 --> 0:12:41.480 is done, it stays available for twenty four hours before disappearing, 0:12:41.480 --> 0:12:43.520 so you can save a stream to your mobile device 0:12:43.559 --> 0:12:46.040 if you have enough storage on your device to do that, 0:12:46.080 --> 0:12:48.240 and then you can upload it to YouTube or some 0:12:48.280 --> 0:12:51.520 other service if you wanted to. Now, if you haven't 0:12:51.559 --> 0:12:54.800 download the Periscope app, you probably aren't really aware of 0:12:54.840 --> 0:12:58.000 how it looks or or you know what it looks 0:12:58.040 --> 0:13:00.520 like rather or how it works. First, you have to 0:13:00.520 --> 0:13:03.000 download the app and install it, obviously, that's your first step. 0:13:03.280 --> 0:13:05.040 And then you have to sign into Periscope. You can 0:13:05.080 --> 0:13:07.559 do that either by using your Twitter handle and password 0:13:07.679 --> 0:13:10.960 or through your phone number. So if you don't have Twitter, 0:13:11.120 --> 0:13:13.880 you don't. You don't have to have it to use Periscope. 0:13:13.920 --> 0:13:16.280 It's just a lot of functionality will be taken out 0:13:16.320 --> 0:13:19.520 if you don't have Twitter. So I'm going to concentrate 0:13:19.559 --> 0:13:22.800 on the Android version because I own an Android phone, 0:13:23.200 --> 0:13:26.160 so that's what I'll be talking about. But the iOS 0:13:26.240 --> 0:13:28.840 one is very similar. It's the same features. I just 0:13:28.880 --> 0:13:31.480 can't necessarily say the layout is exactly the same. They 0:13:31.520 --> 0:13:35.360 may be slightly different. But on the Android version, you've 0:13:35.400 --> 0:13:37.520 got three icons at the top left of the screen 0:13:37.559 --> 0:13:40.360 when you log in. One lists any live streams from 0:13:40.400 --> 0:13:43.760 the folks you follow on Periscope. It also lists any 0:13:43.800 --> 0:13:45.760 streams from the past twenty four hours that came from 0:13:45.760 --> 0:13:48.960 those accounts, including your own. Then there's a glob BiCon 0:13:49.080 --> 0:13:51.600 that let that lists the live streams from around the 0:13:51.600 --> 0:13:53.800 world that you might be interested in. And then there's 0:13:53.800 --> 0:13:56.440 a little cluster of people icon that lists the people 0:13:56.480 --> 0:13:58.760 you follow on Twitter who are also on Periscope, so 0:13:58.760 --> 0:14:01.760 you can follow them on para Scope as well, assuming 0:14:01.760 --> 0:14:04.880 you logged into Periscope through Twitter, that is. And under 0:14:04.920 --> 0:14:07.960 that list of the folks you know is a list 0:14:08.000 --> 0:14:10.600 of the most loved accounts, and those are the accounts 0:14:10.600 --> 0:14:13.319 that have accumulated the most hearts. That's the list I'm 0:14:13.360 --> 0:14:17.199 never ever going to be on. Now. In the upper 0:14:17.280 --> 0:14:20.000 right corner of the people page is a link to 0:14:20.040 --> 0:14:22.400 your accounts, so you can click on that and see 0:14:22.440 --> 0:14:25.080 how you stack up, like how many people do you follow, 0:14:25.160 --> 0:14:28.760 how many people follow you? How many hearts have you accumulated? 0:14:29.320 --> 0:14:31.680 As of this recording right now, this is my third 0:14:31.840 --> 0:14:35.760 periscope broadcast I've ever done, and before I started recording, 0:14:35.800 --> 0:14:38.320 I had around a hundred fifty followers and just over 0:14:38.560 --> 0:14:41.000 eight hundred hearts, So we'll see how many I have 0:14:41.080 --> 0:14:45.760 at the end. Probably not that many more, but that's 0:14:45.800 --> 0:14:48.280 that that tells you I'm at eight hundred. The top 0:14:48.480 --> 0:14:54.000 periscopers have millions and millions of hearts, so I'm not 0:14:54.120 --> 0:14:56.720 in that league. There's also a camera icon on the 0:14:56.760 --> 0:14:59.080 screen and that initiates the live stream, so if you 0:14:59.120 --> 0:15:01.680 touch that icon, it'll prompt you to make a few 0:15:01.720 --> 0:15:04.360 more choices. One thing is you can set the live 0:15:04.400 --> 0:15:07.800 stream to either public or private. A private livestream can 0:15:07.840 --> 0:15:10.080 go out to all your followers or just specific people 0:15:10.120 --> 0:15:13.600 you designate. So I could do a Periscope livestream to 0:15:13.760 --> 0:15:16.760 a single person if I wanted to. Uh, it won't 0:15:16.760 --> 0:15:18.560 all show up to the public. They won't be able 0:15:18.600 --> 0:15:23.000 to view that stream. At least the video stream won't 0:15:23.040 --> 0:15:25.160 show up to the public. There was a problem in 0:15:25.200 --> 0:15:30.480 Periscope's early design that involved Twitter and private video titles. 0:15:30.520 --> 0:15:33.760 So if the Twitter option was on and you created 0:15:33.800 --> 0:15:36.800 a private event, the title of the stream would get 0:15:36.880 --> 0:15:40.240 tweeted out. Only the people you authorized would actually be 0:15:40.280 --> 0:15:43.480 able to watch the stream, but the title went to everyone. 0:15:43.600 --> 0:15:50.000 So if you made a title that was oh, raunchy, 0:15:50.160 --> 0:15:52.680 or you know, you were making an insold or something 0:15:52.680 --> 0:15:54.560 and you thought it was funny because only the people 0:15:54.640 --> 0:15:57.360 who are following you were going to see it, here's 0:15:57.360 --> 0:15:58.960 the problem. It would go out on your Twitter feed. 0:15:59.000 --> 0:16:01.520 If you had that at debated, and everyone would see 0:16:01.520 --> 0:16:03.400 the title. They couldn't see the video, but they would 0:16:03.400 --> 0:16:06.000 know what you were talking about, so that was an issue. 0:16:06.520 --> 0:16:08.680 If your periscope account is linked to Twitter, you can 0:16:08.720 --> 0:16:10.720 choose to tweet out the live stream to your followers, 0:16:10.760 --> 0:16:13.480 which I did at the beginning of this stream. And 0:16:13.560 --> 0:16:15.920 you also need to give your stream a name, so 0:16:16.240 --> 0:16:18.120 you have to title it. My first pair of scope 0:16:18.200 --> 0:16:21.520 was I think called Walking Tibbalt. Tibled, by the way, 0:16:21.720 --> 0:16:24.520 is the name of my puppy dog, and he is 0:16:24.520 --> 0:16:26.960 a puppy and I think that's where seven hundred of 0:16:27.000 --> 0:16:29.640 the eight hundred hearts I have came from. So those 0:16:29.640 --> 0:16:32.040 hearts really don't belong to me. They belonged to Tibalt, 0:16:32.160 --> 0:16:36.600 and he earned them, so I'm not upset. Once you're ready, 0:16:36.640 --> 0:16:40.880 you hit the start broadcasting button and you go. That's it. 0:16:40.880 --> 0:16:43.080 It's streaming. People who follow you on Periscope will get 0:16:43.120 --> 0:16:46.200 a notification if they have push notifications turned on that 0:16:46.280 --> 0:16:48.560 you are live, and if you send a message through Twitter, 0:16:48.800 --> 0:16:51.200 that will get more folks following you and watching you. 0:16:51.760 --> 0:16:54.560 Now that also means you'll get notifications when the people 0:16:54.640 --> 0:16:57.360 you follow go live as well. Those notifications will pop 0:16:57.400 --> 0:17:00.240 up on your mobile device. You can open the up 0:17:00.280 --> 0:17:03.040 and watch and interact at that point. And Periscope can 0:17:03.120 --> 0:17:05.600 use both the forward facing and rear facing cameras on 0:17:05.640 --> 0:17:07.880 a mobile device. You can switch between the two either 0:17:07.920 --> 0:17:10.600 by double tapping on the screen, or you can swipe down, 0:17:10.880 --> 0:17:13.400 which pulls up some settings and you can change it there. 0:17:13.840 --> 0:17:16.159 This lets you show people your point of view or 0:17:16.200 --> 0:17:18.960 pull it back so you can have a camera face 0:17:19.240 --> 0:17:21.520 focused on your face so you can address the camera directly. 0:17:22.520 --> 0:17:24.959 Some other things to keep in mind when you're using periscope. 0:17:25.440 --> 0:17:27.520 If you have the location data on your of your 0:17:27.560 --> 0:17:31.960 phone turned on and you activate that on periscope, it 0:17:32.000 --> 0:17:35.639 will show where you are to people who are viewing 0:17:35.680 --> 0:17:38.800 the stream. This can be a privacy concern to In fact, 0:17:38.920 --> 0:17:42.120 I think originally it was set on by default. Now 0:17:42.119 --> 0:17:45.160 it's set off, at least on mine by default, so 0:17:45.480 --> 0:17:47.640 if I want to, I can choose that and let 0:17:47.680 --> 0:17:49.960 people know where I am. But some people have pointed 0:17:49.960 --> 0:17:52.080 out this could be a privacy concern. If you were 0:17:52.119 --> 0:17:54.720 to broadcast where you were, then that could be a 0:17:54.760 --> 0:17:57.439 safety issue depending upon who you are and who's watching, 0:17:58.200 --> 0:18:02.000 especially if you're broadcasting from your home and you don't 0:18:02.080 --> 0:18:05.439 generally make that information publicly available, it could be a 0:18:05.440 --> 0:18:07.600 big issue. Some other things to keep in mind when 0:18:07.640 --> 0:18:10.119 using periscope. If you have the location data on your 0:18:10.160 --> 0:18:14.040 phone turned on and uh and you don't want people 0:18:14.320 --> 0:18:17.120 to know exactly where you are, you should switch that off. 0:18:17.160 --> 0:18:20.320 You should also keep in mind that maybe the neighbors 0:18:20.359 --> 0:18:23.640 around you don't want the world to know where they live, 0:18:24.280 --> 0:18:27.720 so just courtesy is something that you have to keep 0:18:27.760 --> 0:18:30.360 in mind. Also, there is a limit on how many 0:18:30.359 --> 0:18:32.720 people can chat on a stream. Not that I'm ever 0:18:32.760 --> 0:18:35.080 going to hit that, but once that limit is reached, 0:18:35.440 --> 0:18:37.600 anyone else trying to chat will see that they can't 0:18:37.640 --> 0:18:40.280 say anything they're blocked from chatting, And that's to make 0:18:40.520 --> 0:18:43.040 sure that the video isn't completely drowned out by chat 0:18:43.080 --> 0:18:46.040 messages for these super popular feeds, the ones that get 0:18:46.480 --> 0:18:50.480 millions of hearts in a particular stream. Some other features 0:18:50.520 --> 0:18:53.119 that are useful in periscope include the ability to block 0:18:53.200 --> 0:18:55.280 someone in chat, which is really helpful if you find 0:18:55.320 --> 0:18:57.840 someone to be particularly annoying, and you can also block 0:18:57.880 --> 0:19:00.560 someone in general so that they won't to you when 0:19:00.640 --> 0:19:04.080 you go live from that point forward. Also important if 0:19:04.080 --> 0:19:08.800 someone's trolling you. Unfortunately, there are a lot of female 0:19:08.920 --> 0:19:13.240 users who have loved the functionality of periscope but have 0:19:13.359 --> 0:19:16.760 received some terrible harassment, and it's a good thing that 0:19:16.760 --> 0:19:20.200 that feature exists so that they can at least address 0:19:20.280 --> 0:19:23.720 that themselves. It's unfortunate that it happens, uh, And I 0:19:23.800 --> 0:19:26.000 certainly hope that all of my tech stuff fans are 0:19:26.080 --> 0:19:27.880 the type who would never do that sort of thing. 0:19:27.880 --> 0:19:30.720 I'm pretty sure you're not. You always are awesome to me. 0:19:31.520 --> 0:19:36.800 So how does periscope work? We've got the what it does, 0:19:37.240 --> 0:19:41.800 but how does it work? Well? Not everything has been revealed, 0:19:41.840 --> 0:19:45.359 but I imagine that it's relying upon a specific protocol. 0:19:45.760 --> 0:19:48.840 It's called h t t P Live Streaming, also known 0:19:48.840 --> 0:19:52.040 as h l S. It's kind of a real time 0:19:52.040 --> 0:19:57.080 communications protocol and that allows for the transmission of video streams. UH. 0:19:57.200 --> 0:20:01.600 Generally speaking, it works by using a very common approach. 0:20:01.600 --> 0:20:04.720 I mean, it's your basic web server approach. You've got 0:20:04.720 --> 0:20:08.760 a web server that's designed to distribute video content. So 0:20:08.880 --> 0:20:11.879 you start broadcasting from your mobile device. The data that 0:20:11.960 --> 0:20:15.000 you are creating goes out over the network, whether that's 0:20:15.000 --> 0:20:19.640 a cellular network or a WiFi network, and then travels 0:20:19.680 --> 0:20:23.320 to the web server, the periscope web server. The web 0:20:23.359 --> 0:20:26.680 server then encodes the stream, probably in an h dot 0:20:26.720 --> 0:20:29.560 to six four format for the video, and then some 0:20:29.600 --> 0:20:33.520 standard file format for the audio MP three or a 0:20:33.640 --> 0:20:37.399 C three something like that that gets encapsulated by the 0:20:37.440 --> 0:20:41.280 impact to transport stream to be carried out to periscope viewers. 0:20:42.040 --> 0:20:44.320 And the viewers are using either the app or the 0:20:44.359 --> 0:20:46.720 browser interface to watch the streams, and these are the 0:20:46.760 --> 0:20:52.040 clients in the basic classic server client relationship. You probably 0:20:52.040 --> 0:20:55.120 have heard that phrase a thousand times to talk about 0:20:55.119 --> 0:20:58.560 the Internet. So the client in this case would either 0:20:58.560 --> 0:21:01.800 be the browser or the up on your smartphone, and 0:21:01.840 --> 0:21:04.919 typically the client has the resources necessary to assemble the 0:21:04.960 --> 0:21:08.640 broadcast data those bits that are coming into the device 0:21:08.960 --> 0:21:13.240 into a viewable flow of video. So on mobile devices 0:21:13.280 --> 0:21:15.600 that would be the app on your laptop, that would 0:21:15.600 --> 0:21:17.879 be a browser or desktop. I don't know why I 0:21:17.880 --> 0:21:19.960 just said laptop. I guess they just assume people don't 0:21:20.080 --> 0:21:23.840 use desktops anymore. Sorry, gamers, I love you. I have 0:21:23.880 --> 0:21:26.920 a desktop at home too. As the app becomes more popular, 0:21:26.960 --> 0:21:30.320 scalability becomes an issue. So as the system gets used 0:21:30.359 --> 0:21:32.919 more heavily, it can dynamically adjust the quality of the 0:21:32.960 --> 0:21:35.440 transmitted video. So, in other words, if a lot of 0:21:35.440 --> 0:21:38.400 people are periscoping from a particular location at a time 0:21:38.440 --> 0:21:41.520 where a lot of people are are loading up the service, 0:21:42.200 --> 0:21:46.200 the quality of the video can be downgraded to adjust 0:21:46.280 --> 0:21:49.160 for that. But obviously that only works for a little 0:21:49.160 --> 0:21:52.160