WEBVTT - TechStuff Twitches

0:00:03.360 --> 0:00:06.440
<v Speaker 1>Get in touch with technology with tech stuff from half

0:00:06.480 --> 0:00:14.200
<v Speaker 1>stuff dot com either everyone, and welcome to text stuff.

0:00:14.240 --> 0:00:17.479
<v Speaker 1>I'm Jonathan Strickland and I'm Lauren. Before we get into this,

0:00:17.560 --> 0:00:21.119
<v Speaker 1>I just want to alert listeners ahead of time. I've

0:00:21.160 --> 0:00:24.440
<v Speaker 1>got a cold, so I'm going to sound a little weird.

0:00:24.840 --> 0:00:28.360
<v Speaker 1>He's kind of raspy. Is it's a little bit tom? Wait? Yeah,

0:00:28.400 --> 0:00:31.240
<v Speaker 1>you know the piano has been drinking and Jonathan has

0:00:31.280 --> 0:00:34.560
<v Speaker 1>been on an airplane. So that's where we're at. Today's

0:00:34.640 --> 0:00:38.680
<v Speaker 1>episode is brought to us courtesy of a little listener mail.

0:00:39.280 --> 0:00:43.120
<v Speaker 1>This one is from Daniel via actual email. Yeah, apparently

0:00:43.280 --> 0:00:45.880
<v Speaker 1>people still use that. By the way, guys, we've seen

0:00:46.000 --> 0:00:49.960
<v Speaker 1>a big upswing and listener and email and Facebook and Twitter.

0:00:50.400 --> 0:00:52.880
<v Speaker 1>We love it. Keep up the great so so much.

0:00:52.920 --> 0:00:55.400
<v Speaker 1>We're sending we We love every single note that we receive.

0:00:55.480 --> 0:00:58.240
<v Speaker 1>Even if we are too incredibly stressed out to respond

0:00:58.280 --> 0:01:00.000
<v Speaker 1>to all of you. We love you, Thank you so much.

0:01:00.040 --> 0:01:02.360
<v Speaker 1>I'm trying desperately to get through all the backlogs, so

0:01:02.480 --> 0:01:04.759
<v Speaker 1>if you have written, I am working my way back

0:01:04.800 --> 0:01:08.560
<v Speaker 1>to you, babe. Anyway, Daniel, he wrote to us to say,

0:01:08.760 --> 0:01:10.360
<v Speaker 1>I don't know if you did this before, but we've

0:01:10.400 --> 0:01:13.600
<v Speaker 1>recently had the news then online gaming streaming service called

0:01:13.680 --> 0:01:17.360
<v Speaker 1>Twitch is surpassing live streaming services like you Stream, w

0:01:17.560 --> 0:01:22.080
<v Speaker 1>w E Network live Stream, and other streaming services by volume. However,

0:01:22.160 --> 0:01:24.640
<v Speaker 1>I don't really hear about it outside of gamer groups,

0:01:24.680 --> 0:01:27.039
<v Speaker 1>which is odd to me. Can you all get into

0:01:27.080 --> 0:01:30.000
<v Speaker 1>the details about how Twitch works, or maybe into live

0:01:30.080 --> 0:01:33.280
<v Speaker 1>streaming in general. It's a growing trend in recent years.

0:01:33.360 --> 0:01:36.360
<v Speaker 1>I can only see getting bigger as gaming audiences grow.

0:01:36.840 --> 0:01:39.360
<v Speaker 1>You know what, Daniel, We agree it's a great topic.

0:01:39.440 --> 0:01:42.560
<v Speaker 1>It's one that's become incredibly important as of the week.

0:01:42.560 --> 0:01:45.840
<v Speaker 1>We're recording this podcast because they're Okay. So there's this

0:01:45.920 --> 0:01:47.960
<v Speaker 1>rumor going around, and at this point it's a very

0:01:48.000 --> 0:01:52.160
<v Speaker 1>strong rumor, although the parties that are involved are still

0:01:52.240 --> 0:01:55.240
<v Speaker 1>not commenting officially on it, that Google in the form

0:01:55.280 --> 0:02:00.320
<v Speaker 1>of YouTube is interested in purchasing Twitch for a billion dollars.

0:02:00.360 --> 0:02:03.880
<v Speaker 1>So this was a story broken by Variety originally, and

0:02:03.920 --> 0:02:07.360
<v Speaker 1>then it was corroborated by the Wall Street Journal, although

0:02:07.360 --> 0:02:11.520
<v Speaker 1>again no one from either Twitch nor Google is is

0:02:11.600 --> 0:02:14.639
<v Speaker 1>commenting on the subject. By the time this podcast comes out,

0:02:14.880 --> 0:02:16.840
<v Speaker 1>it may very well be that all of this is

0:02:17.240 --> 0:02:20.320
<v Speaker 1>supremely old news and that the the deal has either

0:02:20.440 --> 0:02:24.720
<v Speaker 1>been agreed upon or declined, but we don't as we're

0:02:24.760 --> 0:02:27.480
<v Speaker 1>recording this, don't know the outcome al right where we

0:02:27.560 --> 0:02:32.160
<v Speaker 1>are recording this on May twenty and um, and yeah,

0:02:32.200 --> 0:02:34.040
<v Speaker 1>these these two sources. By the way, Variety in the

0:02:34.040 --> 0:02:37.480
<v Speaker 1>Wall Street Journal reported different stories, um that the sale

0:02:37.639 --> 0:02:40.480
<v Speaker 1>is already certain, or that the talks are in early stages,

0:02:40.560 --> 0:02:43.160
<v Speaker 1>and that Twitch might just sell stake in their company

0:02:43.240 --> 0:02:45.560
<v Speaker 1>instead of selling the entire company as a whole. Right,

0:02:45.760 --> 0:02:49.280
<v Speaker 1>And even though official sources are not doing any talking

0:02:49.320 --> 0:02:51.600
<v Speaker 1>about it right now, anonymous sources have done a lot

0:02:51.639 --> 0:02:54.880
<v Speaker 1>of talking. For for example, Verage reported that other companies,

0:02:54.880 --> 0:02:59.280
<v Speaker 1>including Microsoft we're also according Twitch, but have been turned down. Um.

0:02:59.320 --> 0:03:01.960
<v Speaker 1>At any rate, It's it's a really interesting news item

0:03:01.960 --> 0:03:05.720
<v Speaker 1>for for both the gaming industry and the live streaming industry.

0:03:05.800 --> 0:03:08.640
<v Speaker 1>And I guess video on the internet as a whole, yeah,

0:03:08.800 --> 0:03:11.000
<v Speaker 1>And keeping in mind that video on the internet is

0:03:11.000 --> 0:03:14.240
<v Speaker 1>still a very young thing. I mean, it wasn't that

0:03:14.320 --> 0:03:16.560
<v Speaker 1>long ago that you didn't have any sort of video

0:03:16.600 --> 0:03:19.080
<v Speaker 1>hosting services. And the way you would get video on

0:03:19.120 --> 0:03:21.960
<v Speaker 1>the internet is that someone would save a video file

0:03:22.280 --> 0:03:24.760
<v Speaker 1>and you'd have to download the whole thing to watch it.

0:03:25.160 --> 0:03:27.680
<v Speaker 1>So this is a this is kind of showing the

0:03:27.720 --> 0:03:32.280
<v Speaker 1>next step in in the the world of video online.

0:03:32.320 --> 0:03:35.560
<v Speaker 1>So we've got the prerecorded stuff, which YouTube has got

0:03:35.640 --> 0:03:38.560
<v Speaker 1>pretty sewn up at least for user generated. Then you've

0:03:38.560 --> 0:03:41.440
<v Speaker 1>got the pre record stuff that is made by studios

0:03:41.440 --> 0:03:44.200
<v Speaker 1>and television networks. Now that's all over the place like Netflix, Hulu,

0:03:44.240 --> 0:03:47.240
<v Speaker 1>all that kind of stuff. And then you have broadcast

0:03:47.280 --> 0:03:50.080
<v Speaker 1>where you're doing a live streaming event, which is what

0:03:50.160 --> 0:03:53.400
<v Speaker 1>Twitch and other services like Twitch are all about. So

0:03:53.800 --> 0:03:56.119
<v Speaker 1>how does that work? Why is it such a big

0:03:56.120 --> 0:03:59.200
<v Speaker 1>deal of why why would Google even be interested in it?

0:03:59.320 --> 0:04:01.800
<v Speaker 1>A lettle in one billion dollars worth of interest in Yeah,

0:04:01.880 --> 0:04:03.640
<v Speaker 1>So we thought we would first go into a little

0:04:03.640 --> 0:04:06.240
<v Speaker 1>bit of history. We like to always look back into

0:04:06.280 --> 0:04:09.920
<v Speaker 1>how things became what they are. So let's, uh, let's

0:04:09.960 --> 0:04:11.880
<v Speaker 1>just think we're not going to get into the way

0:04:11.880 --> 0:04:14.880
<v Speaker 1>back machine because this is pretty recent history. Lauren and

0:04:14.920 --> 0:04:17.839
<v Speaker 1>I both lived through this history. It wasn't going on

0:04:17.880 --> 0:04:20.760
<v Speaker 1>immediately around us, but we were technically alive while it

0:04:20.839 --> 0:04:22.920
<v Speaker 1>was happening, yes, which is relatively rare for the two

0:04:23.000 --> 0:04:24.440
<v Speaker 1>of us. For lots of the history that we do

0:04:24.480 --> 0:04:26.800
<v Speaker 1>on this show. Yeah, there was a period in when

0:04:26.839 --> 0:04:29.680
<v Speaker 1>I was dead to the world. So anyway, Twitch is

0:04:29.839 --> 0:04:31.560
<v Speaker 1>kind of a first of all, it's a spinoff of

0:04:31.560 --> 0:04:35.400
<v Speaker 1>another company. It's so in order to understand where Twitch

0:04:35.440 --> 0:04:37.360
<v Speaker 1>came from, you have to go back a little further

0:04:37.400 --> 0:04:40.080
<v Speaker 1>and look at the origin of this other company, Justin

0:04:40.160 --> 0:04:44.520
<v Speaker 1>TV exactly who, which was founded by Justin Cohn, Emmett Sheer,

0:04:44.640 --> 0:04:48.479
<v Speaker 1>Michael Cybel, and Kyle Vauched. And so here's the thing.

0:04:48.920 --> 0:04:53.120
<v Speaker 1>Even that company was the product of some other some

0:04:53.160 --> 0:04:55.960
<v Speaker 1>other work done by this group of people that didn't

0:04:55.960 --> 0:04:58.320
<v Speaker 1>work out so much. You see, you had this group

0:04:58.360 --> 0:05:03.479
<v Speaker 1>who created a web calendar software called Keiko. This was

0:05:03.560 --> 0:05:06.080
<v Speaker 1>from a group who had gone to Yale together I think,

0:05:06.160 --> 0:05:10.760
<v Speaker 1>and formed the company soon after graduation. And so they

0:05:11.080 --> 0:05:16.320
<v Speaker 1>were approached by a brand new seed company called y Combinator.

0:05:16.320 --> 0:05:20.000
<v Speaker 1>And a seed company is all about finding startups to

0:05:20.000 --> 0:05:24.400
<v Speaker 1>to finance, to fund, hoping that those startups will blossom

0:05:24.560 --> 0:05:28.080
<v Speaker 1>and therefore those investments will end up making huge returns

0:05:28.160 --> 0:05:31.520
<v Speaker 1>in return. You also see these companies that otherwise might

0:05:31.560 --> 0:05:35.520
<v Speaker 1>not have a chance grow into something really interesting. Right.

0:05:35.560 --> 0:05:39.040
<v Speaker 1>Part of that same batch was both Reddit and Infogami,

0:05:39.120 --> 0:05:40.880
<v Speaker 1>which is one of those companies that was started by

0:05:40.880 --> 0:05:44.160
<v Speaker 1>Aaron Schwartz. Yeah, so amazing group of people, right, So

0:05:44.240 --> 0:05:47.680
<v Speaker 1>not just the smarty pants folks behind Kiko, but these

0:05:47.720 --> 0:05:50.320
<v Speaker 1>other groups as well. I mean, Reddit is now one

0:05:50.360 --> 0:05:53.840
<v Speaker 1>of the more popular sites on the Internet has a

0:05:53.880 --> 0:05:57.320
<v Speaker 1>flourishing community, although it's a community that has its own

0:05:57.440 --> 0:06:00.599
<v Speaker 1>uh issues and in fighting. Well yeah, I think the

0:06:00.640 --> 0:06:04.240
<v Speaker 1>more popular Reddit gets, the more irritated the hardcore audience.

0:06:05.279 --> 0:06:07.880
<v Speaker 1>But the same thing happened to dig so it'll be

0:06:07.880 --> 0:06:09.560
<v Speaker 1>interesting to see what happens with Reddit. But that's a

0:06:09.600 --> 0:06:14.160
<v Speaker 1>totally different podcast. So here's the thing about kiko um.

0:06:14.200 --> 0:06:18.120
<v Speaker 1>It was, according to Justin con himself, not that great

0:06:18.160 --> 0:06:20.560
<v Speaker 1>of a product, and the reason he gave behind that

0:06:20.640 --> 0:06:24.320
<v Speaker 1>was that he and his fellow programmers didn't really need

0:06:24.360 --> 0:06:26.880
<v Speaker 1>a calendar. He said, I was going to college, I

0:06:26.920 --> 0:06:30.360
<v Speaker 1>had two classes, I had classes on on two days

0:06:30.400 --> 0:06:33.200
<v Speaker 1>of the week, and otherwise I was sitting around programming.

0:06:33.279 --> 0:06:35.680
<v Speaker 1>So what the heck do I need a schedule for?

0:06:36.240 --> 0:06:38.520
<v Speaker 1>It does not useful to me. So since I didn't

0:06:38.560 --> 0:06:40.880
<v Speaker 1>need it, I wasn't using it, and since I don't

0:06:41.080 --> 0:06:45.520
<v Speaker 1>use it, the products we were making weren't very compelling.

0:06:46.360 --> 0:06:49.040
<v Speaker 1>And then Google calendar comes out and everyone's like, well,

0:06:49.880 --> 0:06:51.640
<v Speaker 1>so they decided what we're gonna do is we're gonna

0:06:51.680 --> 0:06:53.840
<v Speaker 1>sell this company for as much as we can so

0:06:53.880 --> 0:06:56.640
<v Speaker 1>that we can pay back our investors and then constrate

0:06:56.800 --> 0:06:59.160
<v Speaker 1>something else. So of course, they sold their company the

0:06:59.200 --> 0:07:03.680
<v Speaker 1>way any sane person would. They listed it on eBay,

0:07:03.920 --> 0:07:06.719
<v Speaker 1>and it's sold on eBay for some two and fifty

0:07:06.720 --> 0:07:09.800
<v Speaker 1>eight thousand dollars to a Canadian company called two Cows

0:07:10.320 --> 0:07:13.280
<v Speaker 1>to Cows. Two Cows. Yeah, yeah, they have two cows,

0:07:13.320 --> 0:07:15.360
<v Speaker 1>twice as many cows as someone who has one cow.

0:07:15.960 --> 0:07:19.920
<v Speaker 1>So yeah, except its spelled t u c ows, but yeah,

0:07:20.000 --> 0:07:22.160
<v Speaker 1>it's it's It was funny because they were going for

0:07:22.200 --> 0:07:25.720
<v Speaker 1>just fifty dollars. They wanted fifty grand. They were hoping

0:07:25.880 --> 0:07:28.120
<v Speaker 1>they could get fifty grand so they could pay off

0:07:28.160 --> 0:07:30.800
<v Speaker 1>their investors, and then they saw that it had hit

0:07:30.840 --> 0:07:33.000
<v Speaker 1>eighty grand and they thought, oh, we got some walk

0:07:33.040 --> 0:07:35.800
<v Speaker 1>in money now, and it finally sold for two eight

0:07:35.840 --> 0:07:39.520
<v Speaker 1>thousand dollars on eBay. All right, yeah, yeah, two two

0:07:39.520 --> 0:07:42.400
<v Speaker 1>cows and a calendar app that. Yeah, that's great. I

0:07:42.440 --> 0:07:45.000
<v Speaker 1>had no idea you could actually list a company on eBay,

0:07:45.040 --> 0:07:48.360
<v Speaker 1>and the idea that that's involved in the terms of

0:07:48.400 --> 0:07:52.520
<v Speaker 1>service blows my mind. Anyway, they successfully sell Keiko, and

0:07:52.520 --> 0:07:56.840
<v Speaker 1>in two thousand seven, Justin and Emmett pitched this idea

0:07:56.920 --> 0:08:00.200
<v Speaker 1>of justin dot TV to Paul Graham. Paul Graham was

0:08:00.240 --> 0:08:04.920
<v Speaker 1>the guy who founded the y Combinator Seed company, and

0:08:05.040 --> 0:08:07.920
<v Speaker 1>the premise originally was not for some sort of live

0:08:07.960 --> 0:08:11.840
<v Speaker 1>broadcast uh service for the general public, all right, It

0:08:11.880 --> 0:08:13.720
<v Speaker 1>was sort of a curiosity. The idea was to just

0:08:13.840 --> 0:08:19.040
<v Speaker 1>put a webcam um basically on on Kan's head and

0:08:19.560 --> 0:08:22.120
<v Speaker 1>have it broadcast twenty four hours a day, seven days

0:08:22.120 --> 0:08:23.760
<v Speaker 1>a week. So I think that he was doing so

0:08:23.800 --> 0:08:26.680
<v Speaker 1>it was justin TV, justin TV, right, it was. It

0:08:26.760 --> 0:08:28.720
<v Speaker 1>was like it was a kind of life casting, except

0:08:28.720 --> 0:08:31.120
<v Speaker 1>instead of having the camera turned back on himself, it

0:08:31.200 --> 0:08:35.240
<v Speaker 1>was more or less from his perspective and view. Yeah, yeah,

0:08:35.280 --> 0:08:38.800
<v Speaker 1>there's some great stories about weird things that happening. Within

0:08:38.880 --> 0:08:42.600
<v Speaker 1>the first week of going live, apparently his audience felt

0:08:42.600 --> 0:08:46.960
<v Speaker 1>that it was not the most compelling of of entertainment,

0:08:47.280 --> 0:08:50.480
<v Speaker 1>that watching a guy sit in an apartment and code

0:08:50.920 --> 0:08:54.040
<v Speaker 1>was not necessarily the most interesting subject matter, that it

0:08:54.080 --> 0:08:56.280
<v Speaker 1>needed a little bit of spice, so um, so they

0:08:56.360 --> 0:08:58.480
<v Speaker 1>provided it to the audience. Provided the spice this is

0:08:58.520 --> 0:08:59.680
<v Speaker 1>where you know, it's kind of like when you hear

0:08:59.720 --> 0:09:03.680
<v Speaker 1>about a news outlet making the news. In this case,

0:09:03.720 --> 0:09:06.520
<v Speaker 1>it was the audience making the contact content. How do

0:09:06.600 --> 0:09:10.319
<v Speaker 1>they make the content? They contact the police and say

0:09:10.360 --> 0:09:13.640
<v Speaker 1>that there was a report of a stabbing incident in

0:09:14.160 --> 0:09:17.240
<v Speaker 1>Justin Kahn's apartment. So the police pay a little visit.

0:09:17.280 --> 0:09:20.679
<v Speaker 1>By the way, this entire incident is preserved on YouTube

0:09:20.720 --> 0:09:22.880
<v Speaker 1>if you want to watch it. And so you hear

0:09:23.480 --> 0:09:26.960
<v Speaker 1>the cops knocking at the door, they come inside. They

0:09:27.040 --> 0:09:30.440
<v Speaker 1>explained that they got a report about stabbing. Pretty quickly,

0:09:30.480 --> 0:09:34.880
<v Speaker 1>Justin figures out, Hey, the it's our users who have

0:09:35.000 --> 0:09:37.680
<v Speaker 1>decided that this is this would be entertaining to watch.

0:09:38.120 --> 0:09:42.440
<v Speaker 1>What a bunch of scamps um. There were other incidents

0:09:42.440 --> 0:09:45.120
<v Speaker 1>that were similar, where they would call in fake fires

0:09:45.360 --> 0:09:47.680
<v Speaker 1>and there were like six or seven fire trucks lined

0:09:47.720 --> 0:09:52.080
<v Speaker 1>outside of Justin's apartment legally culpable scamps that. Yeah, So

0:09:52.200 --> 0:09:56.200
<v Speaker 1>eventually they decided, hey, you know this, Uh, this idea

0:09:56.840 --> 0:10:00.440
<v Speaker 1>isn't working because Justin's just not interesting enough off to

0:10:00.520 --> 0:10:03.439
<v Speaker 1>keep everyone's attention. Uh. There are other incidents as well.

0:10:03.480 --> 0:10:06.840
<v Speaker 1>There are plenty of videos online that explained the hijinks

0:10:06.880 --> 0:10:09.959
<v Speaker 1>these guys got up to But what happened was they

0:10:10.000 --> 0:10:13.959
<v Speaker 1>decided this isn't sustainable, it's not entertaining, So what can

0:10:14.040 --> 0:10:17.640
<v Speaker 1>we do. How can we modify what we've built into

0:10:17.720 --> 0:10:22.160
<v Speaker 1>something that actually resonates with people. So they revisit the

0:10:22.200 --> 0:10:25.240
<v Speaker 1>idea and they discussed different approaches, and they came up

0:10:25.280 --> 0:10:28.600
<v Speaker 1>with this idea of using the justin TV as a

0:10:28.640 --> 0:10:33.200
<v Speaker 1>platform for other people to broadcast things live over the Internet.

0:10:33.720 --> 0:10:37.760
<v Speaker 1>So this was the democratization of live broadcast. YouTube had

0:10:37.800 --> 0:10:43.280
<v Speaker 1>created the democratization of of sharing video. But but you didn't.

0:10:43.320 --> 0:10:45.560
<v Speaker 1>You couldn't do live events on YouTube at the time,

0:10:46.240 --> 0:10:49.000
<v Speaker 1>So what would where would you go if you wanted

0:10:49.040 --> 0:10:52.120
<v Speaker 1>to have like a live call in show, for example,

0:10:52.760 --> 0:10:55.040
<v Speaker 1>and you were using maybe Skype for people to call

0:10:55.120 --> 0:10:57.960
<v Speaker 1>in so that you could answer questions live on the air,

0:10:58.120 --> 0:11:01.200
<v Speaker 1>You didn't really have that option. But because people couldn't

0:11:01.280 --> 0:11:03.480
<v Speaker 1>hear you and then respond to you in real time,

0:11:03.920 --> 0:11:07.079
<v Speaker 1>twitch or not twitch. But justin TV was a chance

0:11:07.120 --> 0:11:09.720
<v Speaker 1>of doing that. So it's kind of interesting. They said

0:11:09.760 --> 0:11:11.640
<v Speaker 1>that the only reason they were able to do it

0:11:11.720 --> 0:11:16.440
<v Speaker 1>is because while they had been developing justin dot tv, uh,

0:11:16.480 --> 0:11:18.640
<v Speaker 1>they had advanced the technology to a point that brought

0:11:18.720 --> 0:11:22.400
<v Speaker 1>the cost of streaming video down significantly to just like

0:11:22.480 --> 0:11:24.680
<v Speaker 1>a couple of cents or a couple of fractions of

0:11:24.679 --> 0:11:29.240
<v Speaker 1>assent UH for a minute of video, which was important

0:11:29.240 --> 0:11:32.079
<v Speaker 1>because you know, depending upon how much bandwidth you were using,

0:11:32.080 --> 0:11:34.120
<v Speaker 1>your I s P might be charging you quite a

0:11:34.120 --> 0:11:36.760
<v Speaker 1>bit for it. Oh sure, but at that rate, with

0:11:36.880 --> 0:11:42.640
<v Speaker 1>a combination of advertising revenue from from ads and also

0:11:42.760 --> 0:11:45.520
<v Speaker 1>money from investors, they could kind of plug along, yeah exactly.

0:11:45.559 --> 0:11:49.160
<v Speaker 1>The ad supported videos helped them recapture some of the costs,

0:11:49.160 --> 0:11:52.960
<v Speaker 1>and they also got some pretty significant funding, like their

0:11:53.040 --> 0:11:56.599
<v Speaker 1>their first round UH netted them about two million dollars.

0:11:56.640 --> 0:11:59.120
<v Speaker 1>They would later get I think twenty million a couple

0:11:59.120 --> 0:12:02.320
<v Speaker 1>of years down the road. So they were getting money

0:12:02.400 --> 0:12:05.880
<v Speaker 1>from investors who said, this is the future of this

0:12:06.000 --> 0:12:09.559
<v Speaker 1>kind of internet delivery system. Plus they were thinking ahead

0:12:09.600 --> 0:12:12.240
<v Speaker 1>of how can we monetize this so that once once

0:12:12.280 --> 0:12:15.240
<v Speaker 1>we get past that investment period, how do we keep

0:12:15.240 --> 0:12:18.640
<v Speaker 1>making money? And that was through the ad support, So

0:12:19.160 --> 0:12:21.960
<v Speaker 1>they began to think, how can we really make it

0:12:22.000 --> 0:12:24.160
<v Speaker 1>easier for people to find the stuff they want? Because

0:12:24.200 --> 0:12:27.400
<v Speaker 1>as more people join, it gets crowded, right, and you're like, well,

0:12:27.559 --> 0:12:29.400
<v Speaker 1>there's a ton of people on here, but I'm only

0:12:29.440 --> 0:12:33.600
<v Speaker 1>interested in one specific topic. Uh. And so they started

0:12:33.600 --> 0:12:36.440
<v Speaker 1>to make categories and things like people who wanted to

0:12:36.480 --> 0:12:39.600
<v Speaker 1>talk about business, or people who wanted to talk about fashion,

0:12:39.720 --> 0:12:43.000
<v Speaker 1>or people wanted to talk about sports or video games,

0:12:43.320 --> 0:12:47.120
<v Speaker 1>and the video games category began to get incredibly popular,

0:12:47.240 --> 0:12:50.880
<v Speaker 1>something that mystified justin by the way you can watch

0:12:50.920 --> 0:12:53.120
<v Speaker 1>video interviews, and he said, I just didn't get it.

0:12:53.160 --> 0:12:57.200
<v Speaker 1>People were playing video games and streaming their video game

0:12:57.280 --> 0:13:00.520
<v Speaker 1>experience online and other people were watching it. What's up

0:13:00.520 --> 0:13:03.600
<v Speaker 1>with that? He just he was like, I didn't understand it,

0:13:03.640 --> 0:13:06.320
<v Speaker 1>but I realized that other people found it valuable, So

0:13:06.360 --> 0:13:08.440
<v Speaker 1>we knew that it was something we had to look at.

0:13:09.240 --> 0:13:11.559
<v Speaker 1>So they start thinking, well, you know, this makes a

0:13:11.640 --> 0:13:13.679
<v Speaker 1>lot of sense. We've we've got all these people who

0:13:13.720 --> 0:13:17.960
<v Speaker 1>are um watching stuff. We should try and take advantage

0:13:17.960 --> 0:13:23.160
<v Speaker 1>of that. So they ultimately on June six, two eleven,

0:13:23.280 --> 0:13:26.959
<v Speaker 1>launched twitch dot tv in public beta as a completely

0:13:27.080 --> 0:13:30.120
<v Speaker 1>separate brand. Now, this was the idea of let's take

0:13:30.160 --> 0:13:33.960
<v Speaker 1>that video game content that everyone is streaming and create

0:13:34.000 --> 0:13:37.320
<v Speaker 1>a product specifically for that, with tools built in to

0:13:37.440 --> 0:13:40.240
<v Speaker 1>help people do that more smoothly, so they don't have

0:13:40.320 --> 0:13:43.600
<v Speaker 1>to create their own system at home to make it work.

0:13:43.640 --> 0:13:45.800
<v Speaker 1>We're going to try and integrate it in as many

0:13:45.840 --> 0:13:49.640
<v Speaker 1>different approaches as possible so that more people can do this,

0:13:49.679 --> 0:13:53.320
<v Speaker 1>because it's clearly a runaway success story, and it made

0:13:53.400 --> 0:13:55.679
<v Speaker 1>much more sense to create a new brand than to

0:13:55.800 --> 0:13:58.280
<v Speaker 1>just nestle it under justin dot tv. In fact, Twitch

0:13:58.320 --> 0:14:01.439
<v Speaker 1>dot tv was getting bigger than just dot tv. Yeah,

0:14:01.520 --> 0:14:04.760
<v Speaker 1>they they basically immediately found an audience. They started with

0:14:04.840 --> 0:14:09.320
<v Speaker 1>some three point two million unique visitors per month. Yep. Yeah,

0:14:09.440 --> 0:14:13.560
<v Speaker 1>they they've increased that a little bit. Yes, about a

0:14:13.679 --> 0:14:17.520
<v Speaker 1>year later, they would hit twenty million unique visitors per month. Yeah,

0:14:17.600 --> 0:14:20.520
<v Speaker 1>and I think they're at forty five million currently, so

0:14:20.720 --> 0:14:24.760
<v Speaker 1>it is essentially doubled, like year over year, more than

0:14:24.800 --> 0:14:27.239
<v Speaker 1>doubled on that first one. So that was pretty impressive.

0:14:27.280 --> 0:14:29.400
<v Speaker 1>And you know, keep in mind that back in June

0:14:29.400 --> 0:14:31.560
<v Speaker 1>two th eleven, it was just in beta. It wasn't

0:14:31.560 --> 0:14:36.120
<v Speaker 1>even the full release yet. So they started having lots

0:14:36.120 --> 0:14:39.239
<v Speaker 1>of Like there's certain games that that definitely drove participation,

0:14:39.320 --> 0:14:41.520
<v Speaker 1>StarCraft too being a big one. Anything that you can

0:14:41.520 --> 0:14:45.120
<v Speaker 1>get big tournaments going for exactly. So, and you know

0:14:45.160 --> 0:14:49.200
<v Speaker 1>there are places like in South Korea where StarCraft tournaments are,

0:14:49.520 --> 0:14:52.400
<v Speaker 1>like the super Bowl is here in the United States,

0:14:52.720 --> 0:14:56.040
<v Speaker 1>so you get these enormous crowds live audiences watching these

0:14:56.280 --> 0:14:58.640
<v Speaker 1>well only here in the US. It just it never

0:14:58.720 --> 0:15:02.880
<v Speaker 1>really caught on that way, mostly because production costs or

0:15:02.920 --> 0:15:05.480
<v Speaker 1>something like that. If you wanted to televise it, we're

0:15:05.560 --> 0:15:09.520
<v Speaker 1>so high that you would have trouble getting the audience

0:15:09.600 --> 0:15:13.080
<v Speaker 1>large enough to justify that expense. But the overhead for

0:15:13.160 --> 0:15:16.840
<v Speaker 1>Twitch is way lower. I mean, you don't have as

0:15:16.880 --> 0:15:21.960
<v Speaker 1>many employees for one thing, the infrastructure is once you've

0:15:22.200 --> 0:15:26.520
<v Speaker 1>made the investment, much less expensive than television. So it

0:15:26.600 --> 0:15:29.280
<v Speaker 1>was sort of the perfect platform for that and it

0:15:29.360 --> 0:15:32.720
<v Speaker 1>really took off. It also allows the audience to talk

0:15:32.720 --> 0:15:35.080
<v Speaker 1>to each other during the event in a way that

0:15:35.240 --> 0:15:39.000
<v Speaker 1>the normal broadcast television obviously doesn't allow unless you invite

0:15:39.040 --> 0:15:41.400
<v Speaker 1>a lot of your friends over right, or you have

0:15:41.720 --> 0:15:43.880
<v Speaker 1>some app where you can watch the show and talk

0:15:43.920 --> 0:15:46.120
<v Speaker 1>with other fans. But we've seen this over and over

0:15:46.200 --> 0:15:49.840
<v Speaker 1>that television makes it. It's really hard to get something

0:15:49.880 --> 0:15:52.920
<v Speaker 1>like that to work from a television platform and poured

0:15:52.920 --> 0:15:56.920
<v Speaker 1>it over into an online interactive platform. Usually you see

0:15:56.920 --> 0:15:59.000
<v Speaker 1>people just use either Twitter or Facebook for that kind

0:15:59.000 --> 0:16:01.800
<v Speaker 1>of thing, right, And in eleven that wasn't so much

0:16:01.840 --> 0:16:04.160
<v Speaker 1>the case quite yet, No, no, you know, so this

0:16:04.320 --> 0:16:06.280
<v Speaker 1>in this case, you have a platform that by its

0:16:06.360 --> 0:16:09.960
<v Speaker 1>very nature allows for that kind of thing. However, as

0:16:09.960 --> 0:16:13.520
<v Speaker 1>of eleven it's still was not profitable and would not

0:16:13.640 --> 0:16:17.160
<v Speaker 1>become I think it technically has never been profitable for

0:16:17.240 --> 0:16:23.000
<v Speaker 1>a full year. They are estimating that as it will be, right,

0:16:23.160 --> 0:16:25.680
<v Speaker 1>But well, well we'll see. You have to get that

0:16:25.880 --> 0:16:30.840
<v Speaker 1>great balance of AD dollars and user base in order

0:16:30.880 --> 0:16:33.880
<v Speaker 1>to make it profitable. And of course the bigger it gets,

0:16:34.080 --> 0:16:35.760
<v Speaker 1>the more of an investment you have to make in

0:16:35.800 --> 0:16:39.880
<v Speaker 1>the company's infrastructure. Right. Of course, us a few things

0:16:39.960 --> 0:16:43.640
<v Speaker 1>that helped out greatly with that. Yeah. Yeah. For one thing,

0:16:43.920 --> 0:16:47.760
<v Speaker 1>you've got the fact that both Sony and Microsoft gave

0:16:47.800 --> 0:16:52.120
<v Speaker 1>Twitch a big thumbs up. Right, they announced partnerships that

0:16:52.160 --> 0:16:56.080
<v Speaker 1>would allow a native app on both of those gaming

0:16:56.080 --> 0:16:59.760
<v Speaker 1>platforms to integrate Twitch tv. Right. So, with the case

0:16:59.800 --> 0:17:02.560
<v Speaker 1>of of PlayStation four, there's a button on the controller

0:17:02.560 --> 0:17:04.840
<v Speaker 1>where you can start sharing what you're playing. It's a

0:17:04.880 --> 0:17:07.560
<v Speaker 1>little more complex with Xbox one. Uh. And in both

0:17:07.600 --> 0:17:10.800
<v Speaker 1>cases it was a feature that was not immediately implemented

0:17:10.800 --> 0:17:13.399
<v Speaker 1>as soon as the consoles came out, but was implemented

0:17:13.440 --> 0:17:16.639
<v Speaker 1>a little bit later on the life cycle of those consoles,

0:17:17.119 --> 0:17:19.000
<v Speaker 1>I say life cycle, and these things haven't even been

0:17:19.000 --> 0:17:21.639
<v Speaker 1>out a full year yet. Yeah, it's really interesting to

0:17:21.720 --> 0:17:24.720
<v Speaker 1>see that they were throwing their support behind this because

0:17:24.760 --> 0:17:28.160
<v Speaker 1>they could see both Sony and Microsoft could see that

0:17:28.480 --> 0:17:30.960
<v Speaker 1>this this was a trend that was growing, that people

0:17:31.160 --> 0:17:34.360
<v Speaker 1>were eager to share their experiences and more people were

0:17:34.400 --> 0:17:37.680
<v Speaker 1>eager to to eat it all up. So I mean,

0:17:37.760 --> 0:17:40.639
<v Speaker 1>I've watched play throughs online. Of course, the playthroughs I

0:17:40.640 --> 0:17:43.680
<v Speaker 1>watched tend to be done for for comedic purposes, where

0:17:43.680 --> 0:17:45.679
<v Speaker 1>it's a bunch of guys who are playing who know

0:17:45.760 --> 0:17:48.440
<v Speaker 1>each other really well, and they're really doing it as

0:17:48.520 --> 0:17:51.520
<v Speaker 1>a way of entertaining other people, Like that's the whole

0:17:51.520 --> 0:17:55.040
<v Speaker 1>purpose of it. They're not playing a game competitively against others,

0:17:55.040 --> 0:17:57.520
<v Speaker 1>which is what a lot of the Twitch TV stuffs for.

0:17:58.200 --> 0:18:01.359
<v Speaker 1>Not everything, but also you have you have streamed yourself

0:18:01.440 --> 0:18:04.160
<v Speaker 1>on Twitch, haven't you? I did. I did for twenty

0:18:04.160 --> 0:18:08.560
<v Speaker 1>five hours straight. I did a stream of me just

0:18:08.760 --> 0:18:12.440
<v Speaker 1>playing Minecraft. It was for the Extra Life charity, which

0:18:12.520 --> 0:18:15.680
<v Speaker 1>raises money for to buy video games and video game

0:18:15.720 --> 0:18:19.720
<v Speaker 1>systems for kids who are in hospitals and uh, so

0:18:19.840 --> 0:18:21.199
<v Speaker 1>I was part of this. It was kind of like

0:18:21.200 --> 0:18:24.679
<v Speaker 1>a Pledge Drive type thing. And for twenty five hours

0:18:24.680 --> 0:18:27.959
<v Speaker 1>I played and and streamed it live, and I always

0:18:28.000 --> 0:18:30.480
<v Speaker 1>had at least one or two people watching. Sometimes I

0:18:30.520 --> 0:18:33.240
<v Speaker 1>would have you know, a few dozen watching at a time.

0:18:33.920 --> 0:18:36.240
<v Speaker 1>UH And I even had a thing where for certain

0:18:36.359 --> 0:18:41.800
<v Speaker 1>levels of contributions, I would build uh monuments within Minecraft,

0:18:42.000 --> 0:18:44.879
<v Speaker 1>and the more money you made, the bigger and more

0:18:45.040 --> 0:18:48.119
<v Speaker 1>rare the monument would be, like the materials would be

0:18:48.119 --> 0:18:53.080
<v Speaker 1>more rare. So some people were incredibly generous and I

0:18:53.160 --> 0:18:56.640
<v Speaker 1>had to go and find the rarest materials and Minecraft

0:18:56.880 --> 0:18:59.399
<v Speaker 1>within twenty five hours and still build it. Like actually,

0:18:59.400 --> 0:19:01.320
<v Speaker 1>I was like, all, so for the first eighteen hours,

0:19:01.400 --> 0:19:04.959
<v Speaker 1>I'm just mining and then for the last seven hours

0:19:04.960 --> 0:19:07.880
<v Speaker 1>I'll be building. So yeah, it was actually a lot

0:19:07.920 --> 0:19:10.080
<v Speaker 1>of fun. But because of Twitch, I was able to

0:19:10.080 --> 0:19:12.200
<v Speaker 1>stream it live and people could check in on me

0:19:12.240 --> 0:19:14.600
<v Speaker 1>and see that I was actually doing this thing that

0:19:14.640 --> 0:19:17.200
<v Speaker 1>I had said I would do. UM And I also,

0:19:17.280 --> 0:19:19.719
<v Speaker 1>you know, I got to have an ongoing conversation with

0:19:19.760 --> 0:19:22.159
<v Speaker 1>folks through chat. He would chat to me and I

0:19:22.160 --> 0:19:24.680
<v Speaker 1>would answer that questions live while playing and and kind

0:19:24.680 --> 0:19:27.639
<v Speaker 1>of keep you motivated while you were doing this ridiculous marathon.

0:19:27.800 --> 0:19:30.720
<v Speaker 1>Sometime around our number nineteen or twenty, I definitely needed

0:19:30.720 --> 0:19:33.200
<v Speaker 1>some more motivation. Not to mention coffee. I think that's

0:19:33.240 --> 0:19:35.640
<v Speaker 1>the wall that they talked about in Marathon ng UM.

0:19:35.640 --> 0:19:39.639
<v Speaker 1>In September, Twitch sold an undisclosed stake in the company

0:19:39.720 --> 0:19:43.080
<v Speaker 1>to investors, raising that twenty million dollars that you mentioned earlier,

0:19:43.119 --> 0:19:45.760
<v Speaker 1>and a lot of that went to supporting their rollout

0:19:45.800 --> 0:19:48.479
<v Speaker 1>into the PS four and Xbox one. Yeah. Now, if

0:19:48.480 --> 0:19:51.800
<v Speaker 1>you're looking at today's numbers, according to Mercury News that

0:19:51.920 --> 0:19:56.359
<v Speaker 1>this was astounding. Twitch dot tv accounts forty percent of

0:19:56.520 --> 0:20:01.080
<v Speaker 1>all United States live streaming online. That's more than any

0:20:01.080 --> 0:20:06.159
<v Speaker 1>other live streaming site, including ESPN, NBC Sports and YouTube Live. Um.

0:20:06.400 --> 0:20:08.600
<v Speaker 1>This is all according to Quilt, which is a company

0:20:08.640 --> 0:20:12.360
<v Speaker 1>that helps networks manage bandwidth demand for video online and

0:20:12.440 --> 0:20:15.159
<v Speaker 1>announced that they had begun working with Twitch in April.

0:20:16.520 --> 0:20:21.280
<v Speaker 1>Twitch tv receives more than forty million unique visitors each month,

0:20:21.359 --> 0:20:24.440
<v Speaker 1>which I think we mentioned before. But yeah, that's a lot.

0:20:25.000 --> 0:20:28.359
<v Speaker 1>Like sure, if you look at YouTube, YouTube is getting

0:20:28.359 --> 0:20:31.720
<v Speaker 1>a billion, okay, but YouTube has Google behind it and

0:20:31.840 --> 0:20:35.399
<v Speaker 1>is adding a hundred hours of footage every minute, right,

0:20:35.840 --> 0:20:37.919
<v Speaker 1>This is this is considering that this is something that

0:20:38.000 --> 0:20:40.960
<v Speaker 1>was a spinoff of another company and has only been

0:20:41.440 --> 0:20:45.920
<v Speaker 1>around for for less than four full years, it's phenomenal. Yeah,

0:20:45.920 --> 0:20:47.879
<v Speaker 1>and its users spend an average of a hundred and

0:20:47.960 --> 0:20:52.840
<v Speaker 1>six minutes per day watching streams average. That is also insane.

0:20:52.920 --> 0:20:56.040
<v Speaker 1>That's so not to spoil it, but that's going to

0:20:56.160 --> 0:20:57.960
<v Speaker 1>come into play when we have our conversation of why

0:20:57.960 --> 0:20:59.800
<v Speaker 1>the heck would Google wants to spend a billion dollars

0:20:59.800 --> 0:21:01.760
<v Speaker 1>on the yes. To put all of this in perspective

0:21:01.800 --> 0:21:05.040
<v Speaker 1>a little bit, In February, a company called deep Field,

0:21:05.080 --> 0:21:07.919
<v Speaker 1>which does Internet data analysis for media companies like the

0:21:07.920 --> 0:21:11.280
<v Speaker 1>Wall Street Journal, Ransom numbers and reported that Twitch accounts

0:21:11.320 --> 0:21:14.640
<v Speaker 1>for one point eight percent of United States peak internet traffic,

0:21:14.880 --> 0:21:18.359
<v Speaker 1>which places it fourth overall after Netflix, which stands at

0:21:19.040 --> 0:21:24.840
<v Speaker 1>Google and Apple four point three. That also puts it

0:21:24.920 --> 0:21:28.359
<v Speaker 1>ahead of companies like Hulu, Facebook, and Valve, all of

0:21:28.359 --> 0:21:31.280
<v Speaker 1>which come in a couple tents of a percentage point lower.

0:21:31.480 --> 0:21:35.120
<v Speaker 1>That's pretty amazing. I mean, now, granted, these are all

0:21:35.200 --> 0:21:39.480
<v Speaker 1>different things, right because with Google, the fact that is

0:21:39.520 --> 0:21:43.160
<v Speaker 1>Google is pretty impressive considering that that's it's text based. Yeah, yeah,

0:21:43.160 --> 0:21:46.199
<v Speaker 1>it's not just uh, I mean, I guess Google that

0:21:46.200 --> 0:21:49.359
<v Speaker 1>probably also includes YouTube, so that's probably some video in

0:21:49.400 --> 0:21:52.199
<v Speaker 1>there too. But yeah, it's still impressive. The fact that

0:21:52.600 --> 0:21:55.240
<v Speaker 1>Valve is so far back is also impressive because you're

0:21:55.280 --> 0:21:59.680
<v Speaker 1>talking about like not just uh, online gaming, but that's

0:21:59.760 --> 0:22:02.320
<v Speaker 1>a gaming delivery service, you know, if people are buying

0:22:02.359 --> 0:22:05.800
<v Speaker 1>games on Steam. But um, yeah, still pretty impressive. Well,

0:22:06.200 --> 0:22:11.320
<v Speaker 1>we're gonna next tackle exactly how this whole system works,

0:22:11.359 --> 0:22:13.720
<v Speaker 1>but before we do that, let's take a quick break

0:22:13.880 --> 0:22:17.040
<v Speaker 1>to thank our sponsor. Alright, so we're back. Let's talk

0:22:17.080 --> 0:22:21.040
<v Speaker 1>about how this company actually delivers live streaming. That was

0:22:21.119 --> 0:22:24.720
<v Speaker 1>Daniel's question, how does it work? Now? A lot of

0:22:24.760 --> 0:22:27.760
<v Speaker 1>live streaming is using a very similar method, But first

0:22:27.920 --> 0:22:30.919
<v Speaker 1>it's good to say what it does not do, right,

0:22:30.960 --> 0:22:34.840
<v Speaker 1>because it's an intrinsically different system than for example, YouTube. Yeah,

0:22:34.840 --> 0:22:38.119
<v Speaker 1>so YouTube, you've got prerecorded user videos for the most part.

0:22:38.200 --> 0:22:40.760
<v Speaker 1>I mean, YouTube has some live stuff now, but the

0:22:40.760 --> 0:22:44.600
<v Speaker 1>bulk of its business is prerecorded video. So with that,

0:22:44.960 --> 0:22:47.320
<v Speaker 1>I would, for example, if I were uploading a video,

0:22:47.400 --> 0:22:50.280
<v Speaker 1>it would upload to YouTube, then it processes and it's

0:22:50.320 --> 0:22:55.920
<v Speaker 1>stored on YouTube servers actually usually multiple servers. Redundancy. Hey,

0:22:56.040 --> 0:22:58.000
<v Speaker 1>we said at the same time, we were being redundant.

0:22:58.440 --> 0:23:02.240
<v Speaker 1>So we're trying to it serve it up from a disk.

0:23:02.480 --> 0:23:05.560
<v Speaker 1>You know. That's YouTube actually pulls the video from some

0:23:05.720 --> 0:23:10.119
<v Speaker 1>saved part on some server or servers and serves it

0:23:10.240 --> 0:23:12.000
<v Speaker 1>up to you when you say I want to watch

0:23:12.040 --> 0:23:15.880
<v Speaker 1>this video now. That is completely different from the way

0:23:15.960 --> 0:23:18.800
<v Speaker 1>live streaming works. And one of the things that made

0:23:18.840 --> 0:23:23.399
<v Speaker 1>it possible was that, uh, this idea of peering networks.

0:23:23.720 --> 0:23:26.080
<v Speaker 1>So I'll get to that, but but also to explain

0:23:26.160 --> 0:23:30.840
<v Speaker 1>how peering networks are different, your basic uh server client

0:23:30.920 --> 0:23:34.800
<v Speaker 1>relationship is very centralized. You've got a server that has

0:23:34.840 --> 0:23:37.439
<v Speaker 1>all the information on it, and then you use a

0:23:37.480 --> 0:23:40.639
<v Speaker 1>client like a browser that then sends a query to

0:23:40.720 --> 0:23:42.720
<v Speaker 1>the server which says, oh, I know what you want,

0:23:42.760 --> 0:23:46.000
<v Speaker 1>you want this and sends it to you. Centralized right right,

0:23:46.040 --> 0:23:48.120
<v Speaker 1>And that means that if too many people are trying

0:23:48.119 --> 0:23:50.560
<v Speaker 1>to access that server at the same time, you're going

0:23:50.600 --> 0:23:53.560
<v Speaker 1>to run into a little bit of lags exactly, which

0:23:53.600 --> 0:23:55.680
<v Speaker 1>comes down on to your end because the server is

0:23:55.680 --> 0:23:57.680
<v Speaker 1>going to say, oh, hey, wait a minute, I'm doing

0:23:57.680 --> 0:23:59.520
<v Speaker 1>this other thing and this other thing, and and it

0:23:59.640 --> 0:24:03.320
<v Speaker 1>resolves and basically a load bar exactly. Yeah, the same

0:24:03.359 --> 0:24:06.919
<v Speaker 1>sort of thing. Like if Lauren had, uh, you know

0:24:07.240 --> 0:24:09.080
<v Speaker 1>she has she has cookies at her desk, and the

0:24:09.280 --> 0:24:11.879
<v Speaker 1>entire office comes to her at the same time to

0:24:11.920 --> 0:24:15.280
<v Speaker 1>get a cookie each It's gonna take a while because,

0:24:15.880 --> 0:24:17.600
<v Speaker 1>you know, it may be that she has a variety

0:24:17.640 --> 0:24:19.920
<v Speaker 1>of cookies and we each want a different type of cookies.

0:24:19.920 --> 0:24:22.880
<v Speaker 1>So Lauren, being Lauren, wants to be fair to everybody

0:24:23.000 --> 0:24:25.440
<v Speaker 1>and tries to make sure that this happens. But Lauren,

0:24:25.600 --> 0:24:28.679
<v Speaker 1>also being Lauren, gets overwhelmed with the fact that a

0:24:28.680 --> 0:24:32.000
<v Speaker 1>whole bunch of cookie hungry maniacs are approaching her and

0:24:32.160 --> 0:24:35.240
<v Speaker 1>wigs out. I mean, it just happens. So that would

0:24:35.240 --> 0:24:37.320
<v Speaker 1>be an issue of client server. So how can you

0:24:37.320 --> 0:24:39.639
<v Speaker 1>get around that. Well, if Lauren was able to clone

0:24:39.640 --> 0:24:43.200
<v Speaker 1>herself and every single version of Lauren had a box

0:24:43.200 --> 0:24:45.439
<v Speaker 1>of cookies, and all of the box of cookies had

0:24:45.480 --> 0:24:48.400
<v Speaker 1>identical types of cookies in them, like the whole variety,

0:24:48.720 --> 0:24:51.120
<v Speaker 1>we could all go to different Lauren's to get our cookies.

0:24:51.440 --> 0:24:54.080
<v Speaker 1>The interesting thing is that you know, they'd all have

0:24:54.200 --> 0:24:58.080
<v Speaker 1>exactly the cookie we would want. I want a cookie,

0:24:58.320 --> 0:25:01.520
<v Speaker 1>I like this bizarre university. Well that's the that's kind

0:25:01.560 --> 0:25:04.560
<v Speaker 1>of the nature of appearing. So the other issue here

0:25:04.920 --> 0:25:06.959
<v Speaker 1>is that if you have the prerecorded material, you can

0:25:07.000 --> 0:25:10.800
<v Speaker 1>do something called over subscribing bandwidth. Now, that just means

0:25:10.840 --> 0:25:13.240
<v Speaker 1>that you can serve more data than the network can

0:25:13.240 --> 0:25:16.240
<v Speaker 1>actually accommodate at any given time. So let's say that

0:25:16.280 --> 0:25:19.119
<v Speaker 1>I've got a five gigabyte limit on how much data

0:25:19.160 --> 0:25:21.680
<v Speaker 1>i can push out at any given time, but I've

0:25:21.680 --> 0:25:25.000
<v Speaker 1>got seven gigabytes of demand, all right. The way that

0:25:25.080 --> 0:25:28.280
<v Speaker 1>over subscription works is that I send out messages that

0:25:28.359 --> 0:25:30.719
<v Speaker 1>tell all the different clients that are trying to access

0:25:30.800 --> 0:25:33.760
<v Speaker 1>my stuff. Hey, I'm getting to you. Here's some of

0:25:33.800 --> 0:25:37.840
<v Speaker 1>the information. More of its coming right now, but just

0:25:37.840 --> 0:25:39.760
<v Speaker 1>just you know what, do a little song and dance

0:25:39.760 --> 0:25:42.840
<v Speaker 1>for the user. That's when you get the little buffer thing. Right.

0:25:42.960 --> 0:25:45.679
<v Speaker 1>So with YouTube, if a video is buffering mainly, that

0:25:45.800 --> 0:25:49.040
<v Speaker 1>just means that the service has a lot of traffic

0:25:49.080 --> 0:25:51.080
<v Speaker 1>and it's trying to serve all of that traffic at

0:25:51.080 --> 0:25:53.720
<v Speaker 1>the same time. So you're getting bits and bits of

0:25:53.800 --> 0:25:56.080
<v Speaker 1>data that are buffering slowly, so that once you hit

0:25:56.119 --> 0:25:59.040
<v Speaker 1>a certain threshold, you can push play and watch your

0:25:59.119 --> 0:26:03.480
<v Speaker 1>video and everything goes well, yeah, exactly. Hypothetically, exactly. Yeah,

0:26:03.520 --> 0:26:06.240
<v Speaker 1>if if, if it has buffered enough, you can push

0:26:06.240 --> 0:26:08.240
<v Speaker 1>play and you can watch the video all the way

0:26:08.280 --> 0:26:11.879
<v Speaker 1>through because at that point you're getting data faster than

0:26:11.920 --> 0:26:14.760
<v Speaker 1>the video is completing. Now, anyone who's ever seen video

0:26:14.760 --> 0:26:16.520
<v Speaker 1>buffer in the middle of a video know that that

0:26:16.560 --> 0:26:19.160
<v Speaker 1>knows that that doesn't always work, you know. Sometimes it's

0:26:19.160 --> 0:26:21.720
<v Speaker 1>just one of those things where the playback catches up

0:26:22.040 --> 0:26:23.760
<v Speaker 1>to the amount of data that's come in and you

0:26:23.760 --> 0:26:27.159
<v Speaker 1>have to wait longer. Okay, so how is how is

0:26:27.200 --> 0:26:32.000
<v Speaker 1>this peering structure different? Alright? So it's decentralized. So instead

0:26:32.000 --> 0:26:35.439
<v Speaker 1>of having that centralized server that all the different clients

0:26:35.440 --> 0:26:40.040
<v Speaker 1>are contacting, you have a system, a network architecture where

0:26:40.320 --> 0:26:44.120
<v Speaker 1>multiple servers are using copies of the same sort of thing,

0:26:44.480 --> 0:26:46.679
<v Speaker 1>and all of them can take on a part of

0:26:46.720 --> 0:26:49.879
<v Speaker 1>the work. So instead of one server where you you know,

0:26:49.920 --> 0:26:52.000
<v Speaker 1>you're just souping it up as fast as it can

0:26:52.000 --> 0:26:54.520
<v Speaker 1>go so it can work as best as it possibly can,

0:26:55.040 --> 0:26:59.120
<v Speaker 1>you distribute it across an entire network. Google actually does

0:26:59.119 --> 0:27:02.640
<v Speaker 1>this for their search, So for a Google Search query,

0:27:02.720 --> 0:27:05.439
<v Speaker 1>they have an entire network of servers that work together.

0:27:05.560 --> 0:27:08.080
<v Speaker 1>That's why if you ever do that Google search and

0:27:08.080 --> 0:27:10.480
<v Speaker 1>you look and it says it took point zero zero

0:27:10.560 --> 0:27:14.920
<v Speaker 1>zero zero zero eight three seconds to to answer this query.

0:27:15.000 --> 0:27:17.919
<v Speaker 1>That's why, because I've got this distributed network, So just

0:27:17.920 --> 0:27:20.359
<v Speaker 1>think of it as a group of people all taking

0:27:20.480 --> 0:27:26.240
<v Speaker 1>some of the load so that no one server is overworked. Now,

0:27:26.280 --> 0:27:29.320
<v Speaker 1>these servers can be located in different data centers, which

0:27:29.320 --> 0:27:31.720
<v Speaker 1>could be all the way across the world. They don't

0:27:31.840 --> 0:27:34.560
<v Speaker 1>have to be co located with anything or next to

0:27:34.600 --> 0:27:39.000
<v Speaker 1>each other. And because of this, you've got these individual

0:27:39.080 --> 0:27:42.760
<v Speaker 1>nodes which have this peering architecture that they're they're the peers,

0:27:43.160 --> 0:27:45.480
<v Speaker 1>so that each individual server is a peer in this

0:27:45.560 --> 0:27:49.119
<v Speaker 1>peering architecture, and they act as both suppliers and consumers

0:27:49.119 --> 0:27:52.119
<v Speaker 1>of resources. So each peer makes part of its computer

0:27:52.160 --> 0:27:54.720
<v Speaker 1>resources available to the other peers. This is that sharing,

0:27:54.960 --> 0:27:58.520
<v Speaker 1>that distribution of the load of any given computer request.

0:27:58.960 --> 0:28:01.399
<v Speaker 1>So this way you can get a bunch of you know,

0:28:01.480 --> 0:28:05.000
<v Speaker 1>average servers together and network them together and get a

0:28:05.000 --> 0:28:07.760
<v Speaker 1>better performance than if you just invest in that one

0:28:07.800 --> 0:28:11.600
<v Speaker 1>super fast server. It also makes it cheaper because you

0:28:11.640 --> 0:28:13.520
<v Speaker 1>can just get off the shelf parts to build your

0:28:13.560 --> 0:28:17.520
<v Speaker 1>servers instead of buying you know, the next ultra fast exactly.

0:28:17.880 --> 0:28:19.879
<v Speaker 1>So it and Again, this is also what allows you

0:28:19.920 --> 0:28:22.840
<v Speaker 1>to be have a lot of redundancy because you can

0:28:22.920 --> 0:28:26.680
<v Speaker 1>you can get a bunch of inexpensive parts as opposed to, well,

0:28:26.800 --> 0:28:29.200
<v Speaker 1>we blew all our money on this one really fast

0:28:29.240 --> 0:28:32.320
<v Speaker 1>machine that can't live up to our expectations. So what

0:28:32.480 --> 0:28:34.760
<v Speaker 1>happens I mean, because I'm sure that with the number

0:28:34.760 --> 0:28:37.160
<v Speaker 1>of people who are using this service, what happens if

0:28:37.320 --> 0:28:42.040
<v Speaker 1>demand exceeds even this capacity? Okay, so if there were

0:28:42.080 --> 0:28:46.200
<v Speaker 1>no overflow method, you would all get a buffering message

0:28:46.200 --> 0:28:49.120
<v Speaker 1>at the same time. Because all of these servers are

0:28:49.120 --> 0:28:51.400
<v Speaker 1>working together. It's this whole It's like it's an all

0:28:51.480 --> 0:28:55.680
<v Speaker 1>or nothing kind of situation. Now. Uh, the the peak

0:28:55.880 --> 0:28:59.920
<v Speaker 1>use of Twitch was something like ten times the amount

0:29:00.080 --> 0:29:02.560
<v Speaker 1>of the average use, which meant that they had to

0:29:02.600 --> 0:29:06.680
<v Speaker 1>build a network that could withstand ten times the normal

0:29:06.800 --> 0:29:08.719
<v Speaker 1>use at least, and in fact, you want to have

0:29:08.800 --> 0:29:11.960
<v Speaker 1>more than that to have a comfortable buffer. But even

0:29:12.000 --> 0:29:14.280
<v Speaker 1>if it goes beyond that. This is something they've learned

0:29:14.280 --> 0:29:17.360
<v Speaker 1>from their just in TV days, they wanted the ability

0:29:17.400 --> 0:29:20.560
<v Speaker 1>to have an overflow capacity where they use something called

0:29:20.560 --> 0:29:24.280
<v Speaker 1>a content delivery network or c d N. Now, this

0:29:24.360 --> 0:29:27.880
<v Speaker 1>is a specific type of business. It's a distributed system

0:29:27.880 --> 0:29:30.880
<v Speaker 1>of servers, so again sort of appeering network, but this

0:29:30.920 --> 0:29:34.000
<v Speaker 1>is kind of appeering network for higher So you would

0:29:34.320 --> 0:29:36.880
<v Speaker 1>use this if you wanted to create content and you

0:29:36.880 --> 0:29:39.160
<v Speaker 1>want to be able to distribute it to a wide

0:29:39.200 --> 0:29:42.200
<v Speaker 1>audience on a live basis. This is the sort of

0:29:42.240 --> 0:29:44.200
<v Speaker 1>approach you would want to take. And this is what

0:29:44.680 --> 0:29:47.640
<v Speaker 1>some companies like Netflix, they depend upon the sort of

0:29:47.680 --> 0:29:51.160
<v Speaker 1>networks to deliver the stuff that they make. Some companies

0:29:51.200 --> 0:29:53.840
<v Speaker 1>invest in their own, like twitch tv has its own network,

0:29:53.880 --> 0:29:57.080
<v Speaker 1>but again, if it exceeds that capacity, they can then

0:29:57.160 --> 0:29:59.560
<v Speaker 1>say tap the shoulder of the c d N and

0:29:59.600 --> 0:30:03.240
<v Speaker 1>say can you take over some of this stuff. Now,

0:30:03.280 --> 0:30:06.040
<v Speaker 1>for these cases, it does mean that the company, whether

0:30:06.080 --> 0:30:09.040
<v Speaker 1>it's twitched TV or some other media company, has to

0:30:09.120 --> 0:30:11.680
<v Speaker 1>pay for those services. You know, it's not a free thing,

0:30:12.200 --> 0:30:14.760
<v Speaker 1>but it does mean that there's at least a safety

0:30:14.800 --> 0:30:18.200
<v Speaker 1>net there. Should Let's say that that there's some huge

0:30:18.240 --> 0:30:21.200
<v Speaker 1>event that happens on twitch tv that really gets the

0:30:21.360 --> 0:30:24.080
<v Speaker 1>entire gaming world interested and they all want to watch

0:30:24.160 --> 0:30:27.520
<v Speaker 1>it at the same time live streaming, then they might

0:30:27.560 --> 0:30:31.800
<v Speaker 1>need to use that kind of resource because the demand

0:30:32.080 --> 0:30:36.880
<v Speaker 1>would exceed the capacity. They also developed a load balancing

0:30:37.040 --> 0:30:40.080
<v Speaker 1>software called Usher to help out a little bit in

0:30:40.080 --> 0:30:43.040
<v Speaker 1>in high demand situations like that, Yeah, this is really

0:30:43.120 --> 0:30:47.880
<v Speaker 1>really cool stuff. So Usher is kind of the the

0:30:47.880 --> 0:30:52.240
<v Speaker 1>the traffic manager. Right. Usher identifies what requests are and

0:30:52.280 --> 0:30:54.960
<v Speaker 1>how to fulfill those requests in what in other words,

0:30:54.960 --> 0:30:57.560
<v Speaker 1>how how many servers it needs to call upon in

0:30:57.640 --> 0:31:00.080
<v Speaker 1>order to handle the demand that's coming in. Right, So,

0:31:00.160 --> 0:31:04.360
<v Speaker 1>let's say that I'm going to stream the playing uh,

0:31:04.480 --> 0:31:07.320
<v Speaker 1>I don't know, some game, like I'm gonna go back

0:31:07.360 --> 0:31:09.800
<v Speaker 1>and play through some of the Halo games and I'm

0:31:09.800 --> 0:31:12.880
<v Speaker 1>gonna stream them live. Now, in that case, there's probably

0:31:12.920 --> 0:31:14.880
<v Speaker 1>not going to be a huge demand. There aren't that

0:31:14.920 --> 0:31:17.520
<v Speaker 1>many people who are that interested in watching a bald

0:31:17.520 --> 0:31:22.520
<v Speaker 1>guy fail miserably at playing Halo. Um until you try,

0:31:22.600 --> 0:31:24.800
<v Speaker 1>that's true. But I'm assuming that this would not be

0:31:24.880 --> 0:31:27.400
<v Speaker 1>one that Usher would be like ho Alert the media.

0:31:27.840 --> 0:31:31.840
<v Speaker 1>So Usher, when getting the message that I'm going to

0:31:31.880 --> 0:31:36.160
<v Speaker 1>stream this video and then analyzing how much of the

0:31:36.240 --> 0:31:39.600
<v Speaker 1>resources available we're going to be necessary for to deliver

0:31:39.720 --> 0:31:42.800
<v Speaker 1>upon that would contact various servers to make sure that

0:31:42.840 --> 0:31:45.320
<v Speaker 1>it was covered. And usually we're talking about a capacity

0:31:45.360 --> 0:31:48.240
<v Speaker 1>that exceeds what it expects for the demand. Now, if

0:31:48.240 --> 0:31:52.720
<v Speaker 1>it were some uh star Craft two champions that never

0:31:52.760 --> 0:31:55.160
<v Speaker 1>faced each other before, and they were going to have

0:31:55.280 --> 0:31:58.360
<v Speaker 1>a tournament style game against each other to determine who

0:31:58.520 --> 0:32:02.560
<v Speaker 1>is the true champion StarCraft Too. That could be huge,

0:32:02.600 --> 0:32:05.600
<v Speaker 1>and Usher would then make that determination and contact the

0:32:05.680 --> 0:32:09.600
<v Speaker 1>various servers that would all be copying the stream so

0:32:09.680 --> 0:32:12.120
<v Speaker 1>that they could share it up to UH to anyone

0:32:12.200 --> 0:32:15.400
<v Speaker 1>that would wanted to watch it. So then you've got

0:32:16.160 --> 0:32:18.600
<v Speaker 1>all these different factors that come into play that Usher

0:32:18.640 --> 0:32:21.719
<v Speaker 1>will take into considerations, So not just how popular are

0:32:21.720 --> 0:32:23.520
<v Speaker 1>the stream is going to be, but how much is

0:32:23.520 --> 0:32:27.000
<v Speaker 1>it gonna cost to serve up the live video? Because

0:32:27.040 --> 0:32:30.480
<v Speaker 1>like I said, bandwidth is not necessarily free. And Usher

0:32:30.560 --> 0:32:32.200
<v Speaker 1>can sit there and look and say which one of

0:32:32.240 --> 0:32:34.680
<v Speaker 1>these options is going to be the cheapest. Now, in

0:32:34.720 --> 0:32:38.520
<v Speaker 1>some cases, like with that StarCraft Too example, cheapest may

0:32:38.560 --> 0:32:41.480
<v Speaker 1>not be the best response because they want to make

0:32:41.520 --> 0:32:45.800
<v Speaker 1>sure that their customers, the viewers, are satisfied. So they

0:32:45.880 --> 0:32:48.200
<v Speaker 1>might say, all right, you know what, We're gonna incur

0:32:48.320 --> 0:32:49.880
<v Speaker 1>a cost on this, but what we want to do

0:32:49.960 --> 0:32:52.600
<v Speaker 1>is make sure we have the lowest latency possible so

0:32:52.600 --> 0:32:55.600
<v Speaker 1>that people who are watching are not experiencing like a

0:32:55.720 --> 0:33:00.440
<v Speaker 1>thirty second lag behind the action, so then sure can

0:33:00.480 --> 0:33:05.240
<v Speaker 1>prioritize on the fly. And it apparently the controls here

0:33:05.360 --> 0:33:09.880
<v Speaker 1>are incredibly precise so that you can tweak exactly which

0:33:09.920 --> 0:33:13.160
<v Speaker 1>things are the most important for any given situation. So

0:33:13.200 --> 0:33:15.320
<v Speaker 1>it's very versatile in that way, which I thought was

0:33:15.400 --> 0:33:18.920
<v Speaker 1>really really cool. Now every single server in that peer

0:33:18.960 --> 0:33:22.040
<v Speaker 1>network can actually act as two different things. It can

0:33:22.080 --> 0:33:24.560
<v Speaker 1>act as an edge server or it can act as

0:33:24.560 --> 0:33:27.560
<v Speaker 1>an origin server. So edge servers these are the machines

0:33:27.600 --> 0:33:30.320
<v Speaker 1>that are actually serving up the video streams that we're watching.

0:33:30.560 --> 0:33:32.480
<v Speaker 1>So if you log into twitch tv so that you

0:33:32.480 --> 0:33:35.520
<v Speaker 1>can watch someone else, you're getting that video feed from

0:33:35.520 --> 0:33:38.239
<v Speaker 1>an edge server. Now, the person who is making that

0:33:38.400 --> 0:33:41.720
<v Speaker 1>video is sending it to what is called an origin server.

0:33:41.920 --> 0:33:45.080
<v Speaker 1>That's the that's the machine that's accepting the incoming video,

0:33:45.160 --> 0:33:47.400
<v Speaker 1>so it can distribute it to the edge servers. And

0:33:47.440 --> 0:33:50.280
<v Speaker 1>because all the machines can do either role, it makes

0:33:50.320 --> 0:33:53.600
<v Speaker 1>it an incredibly flexible approach to delivering live video. And

0:33:53.680 --> 0:33:56.840
<v Speaker 1>that's why twitch dot tv works. If it had a

0:33:56.920 --> 0:34:00.959
<v Speaker 1>designated origin server and then designated servers, you would be

0:34:01.000 --> 0:34:04.600
<v Speaker 1>limited by that capacity. Now, if you could actually visualize

0:34:04.640 --> 0:34:08.240
<v Speaker 1>all these connections it would look very much like a tree.

0:34:08.920 --> 0:34:12.719
<v Speaker 1>So as people start to tune into a particular video stream,

0:34:12.760 --> 0:34:15.239
<v Speaker 1>you would have more and more branches forming off of

0:34:15.280 --> 0:34:18.640
<v Speaker 1>the trunk of that tree, so that those servers would

0:34:18.640 --> 0:34:21.319
<v Speaker 1>be able to deliver up the video most effectively to

0:34:21.480 --> 0:34:25.080
<v Speaker 1>those users. Because of course users aren't centralized either, right,

0:34:25.360 --> 0:34:27.720
<v Speaker 1>You could have users from all over the world tuning

0:34:27.719 --> 0:34:30.520
<v Speaker 1>in for any given video stream. So you want to

0:34:30.520 --> 0:34:32.799
<v Speaker 1>make sure that you can deliver the video stream the

0:34:32.840 --> 0:34:36.200
<v Speaker 1>best possible way to any individual user, uh, in the

0:34:36.239 --> 0:34:38.719
<v Speaker 1>way that it's going to make financial sense. So I mean,

0:34:39.080 --> 0:34:41.880
<v Speaker 1>that's why Usher, I thought, is so impressive because it

0:34:41.920 --> 0:34:45.400
<v Speaker 1>can take all that into account. Now, how is this

0:34:45.560 --> 0:34:48.279
<v Speaker 1>actually working on the back end? Like what's going on?

0:34:48.440 --> 0:34:51.520
<v Speaker 1>So with YouTube, you know you're saving two disk, but

0:34:51.880 --> 0:34:55.719
<v Speaker 1>with Twitch you aren't Twitch and justin TV do not

0:34:56.000 --> 0:34:58.919
<v Speaker 1>save video to a disk to serve it up. They

0:34:59.000 --> 0:35:04.319
<v Speaker 1>save the video stream within the server's memory. So the

0:35:04.480 --> 0:35:07.080
<v Speaker 1>video that's going to the origin server is saved and

0:35:07.120 --> 0:35:09.760
<v Speaker 1>its memory, it is making copies of that video stream

0:35:09.880 --> 0:35:13.680
<v Speaker 1>as it's being generated, sends those copies to the edge servers.

0:35:13.920 --> 0:35:17.120
<v Speaker 1>Those copies stay in the edge server's memory, which then

0:35:17.200 --> 0:35:19.799
<v Speaker 1>make a copy of that stream and send it to

0:35:20.000 --> 0:35:23.160
<v Speaker 1>the clients, the browsers that people are using to watch

0:35:23.200 --> 0:35:25.480
<v Speaker 1>the video stream. So it's copies and copies and copies.

0:35:26.719 --> 0:35:29.239
<v Speaker 1>Now that's not to say that they don't save this

0:35:29.360 --> 0:35:32.400
<v Speaker 1>information to disk. They do, but that's for archival purposes,

0:35:32.440 --> 0:35:35.239
<v Speaker 1>so you can go back and watch a video that's

0:35:35.239 --> 0:35:39.240
<v Speaker 1>been recorded previously. But it's not that that disk saving

0:35:39.239 --> 0:35:42.440
<v Speaker 1>things is what's coming into play here exactly while you're

0:35:42.440 --> 0:35:44.759
<v Speaker 1>watching it live. It has nothing to do with the

0:35:44.800 --> 0:35:47.120
<v Speaker 1>fact that it's also being saved to disk. That's that's

0:35:47.120 --> 0:35:50.680
<v Speaker 1>a completely separate thing that's going on. So when you're

0:35:50.680 --> 0:35:55.279
<v Speaker 1>watching your browser, your your client is sending in a

0:35:55.320 --> 0:36:01.520
<v Speaker 1>request via HTTP, so hypertext protocol good, all fun stuff.

0:36:03.400 --> 0:36:06.200
<v Speaker 1>We'll do an episode on it someday, I promise. But anyway,

0:36:06.560 --> 0:36:10.040
<v Speaker 1>it sends the HTTP request and Usher then accepts the

0:36:10.080 --> 0:36:12.759
<v Speaker 1>request because you know, he's a good guy. Uh, then

0:36:12.840 --> 0:36:15.920
<v Speaker 1>he decided I'm sorry, I'm thinking the software Usher decides

0:36:15.960 --> 0:36:18.920
<v Speaker 1>which server to connect you to, which edge server you

0:36:18.960 --> 0:36:21.880
<v Speaker 1>would be connected to, and then the video servers themselves,

0:36:21.960 --> 0:36:24.799
<v Speaker 1>they're they're very simple. They're just either acting as edge

0:36:24.880 --> 0:36:27.560
<v Speaker 1>or origin servers, so they're not making this determination at all.

0:36:27.600 --> 0:36:31.760
<v Speaker 1>That's all the usher software stuff, so and multiple data centers.

0:36:32.280 --> 0:36:36.360
<v Speaker 1>The data centers are actually located in proximity to major

0:36:36.520 --> 0:36:40.799
<v Speaker 1>peering exchanges on the Internet. Now, appearing exchange is not

0:36:40.960 --> 0:36:44.719
<v Speaker 1>the same thing as peer to peer networks. It's two

0:36:44.719 --> 0:36:48.320
<v Speaker 1>different concepts. Appearing exchange is a point on the Internet

0:36:48.320 --> 0:36:52.680
<v Speaker 1>where two major networks end up connecting to each other.

0:36:52.719 --> 0:36:55.680
<v Speaker 1>So remember the Internet is a network of networks, right,

0:36:56.040 --> 0:36:58.880
<v Speaker 1>So when you've got two big networks, like two big

0:36:59.000 --> 0:37:02.800
<v Speaker 1>Internet service provid witers for example, to have a connection point,

0:37:03.400 --> 0:37:06.279
<v Speaker 1>the purpose for that is to allow stuff that came

0:37:06.360 --> 0:37:10.680
<v Speaker 1>from one network to cross over and enter another network.

0:37:10.960 --> 0:37:14.919
<v Speaker 1>And these period exchanges their agreements essentially that say, hey,

0:37:15.040 --> 0:37:17.279
<v Speaker 1>as long as you let the stuff that comes from

0:37:17.320 --> 0:37:20.560
<v Speaker 1>my network travel across your network, all of the stuff

0:37:20.600 --> 0:37:23.359
<v Speaker 1>that comes from your network travel across my network, and

0:37:23.360 --> 0:37:26.120
<v Speaker 1>we're all even, Stephen. Now, this is one of the

0:37:26.200 --> 0:37:30.200
<v Speaker 1>points that net neutrality really makes important. They say, this

0:37:30.280 --> 0:37:33.840
<v Speaker 1>relationship is why we don't have to worry about any

0:37:33.880 --> 0:37:36.840
<v Speaker 1>particular part of the network holding the rest of the

0:37:36.840 --> 0:37:40.160
<v Speaker 1>Internet hostage by saying, if you want your traffic to

0:37:40.200 --> 0:37:41.880
<v Speaker 1>travel on my network, you're gonna have to pay me

0:37:42.200 --> 0:37:46.319
<v Speaker 1>x amount of money per x amount of data. That

0:37:46.360 --> 0:37:49.520
<v Speaker 1>would be bad. That would that would I mean it

0:37:49.520 --> 0:37:51.279
<v Speaker 1>would be bad. It would break the Internet the way

0:37:51.280 --> 0:37:53.960
<v Speaker 1>we have it today because you would make an uneven

0:37:54.000 --> 0:37:56.719
<v Speaker 1>playing ground, and if other networks followed suit, it would

0:37:56.760 --> 0:38:00.080
<v Speaker 1>just become this thing where you would have your the

0:38:00.080 --> 0:38:02.440
<v Speaker 1>the stuff you would have access to would be completely

0:38:02.480 --> 0:38:07.839
<v Speaker 1>dependent upon what originated on your network, who how much,

0:38:08.040 --> 0:38:11.880
<v Speaker 1>or who wasn't paying who? Yeah. Yeah, So that's anyway

0:38:11.920 --> 0:38:15.839
<v Speaker 1>again tangential. But the reason why the peering exchanges are

0:38:15.880 --> 0:38:17.960
<v Speaker 1>important is that by putting your data centers close to

0:38:18.000 --> 0:38:22.719
<v Speaker 1>peering exchanges, you have a much closer connection to individual networks.

0:38:22.880 --> 0:38:25.480
<v Speaker 1>Because this is kind of like the crossroads. If you're

0:38:25.480 --> 0:38:28.000
<v Speaker 1>able to plant yourself near the crossroads, you can connect

0:38:28.000 --> 0:38:30.000
<v Speaker 1>to all those different roads that split off from it

0:38:30.200 --> 0:38:33.040
<v Speaker 1>very easily. It's a very strategic move on the part

0:38:33.040 --> 0:38:35.919
<v Speaker 1>of Justin dot tv and Twitch dot tv. So really

0:38:35.960 --> 0:38:39.120
<v Speaker 1>the only thing left to talk about is the user experience.

0:38:39.440 --> 0:38:43.800
<v Speaker 1>You've got a browser, You've got a embettable player inside

0:38:43.840 --> 0:38:46.759
<v Speaker 1>that browser. That's what's handling the incoming video to play

0:38:46.760 --> 0:38:49.480
<v Speaker 1>it on your your screen. Same sort of thing is

0:38:49.520 --> 0:38:52.160
<v Speaker 1>like an inbettable YouTube player or blit TV, I mean,

0:38:52.200 --> 0:38:55.600
<v Speaker 1>any of those inbeatable players are doing the basic same thing.

0:38:55.680 --> 0:38:58.279
<v Speaker 1>That's just that's just the interface that allows you to

0:38:58.360 --> 0:39:01.120
<v Speaker 1>watch whatever the data is. So really there's not a

0:39:01.160 --> 0:39:03.760
<v Speaker 1>whole lot going on the client side. There's some load

0:39:03.800 --> 0:39:06.000
<v Speaker 1>balancing stuff that comes from the client side, but not

0:39:06.040 --> 0:39:07.719
<v Speaker 1>by not a whole lot. Most of it's on the

0:39:07.760 --> 0:39:10.640
<v Speaker 1>back end. Um and and same thing for the broadcaster.

0:39:10.719 --> 0:39:12.800
<v Speaker 1>There's not a whole lot going on that the broadcaster

0:39:12.840 --> 0:39:15.000
<v Speaker 1>has to manage. They basically just turn on their webcam

0:39:15.360 --> 0:39:17.520
<v Speaker 1>and to use the client and go. Yeah, you might

0:39:17.560 --> 0:39:20.640
<v Speaker 1>have to have a little extra software depending upon where

0:39:20.719 --> 0:39:24.120
<v Speaker 1>your video is coming from, like UH. For example, when

0:39:24.120 --> 0:39:26.920
<v Speaker 1>I needed to stream when I was playing Minecraft on

0:39:26.960 --> 0:39:29.680
<v Speaker 1>the PC UH and I needed to stream that online,

0:39:29.719 --> 0:39:32.319
<v Speaker 1>I had to download another piece of software that would

0:39:32.360 --> 0:39:35.239
<v Speaker 1>allow me to take the video from the game and

0:39:35.360 --> 0:39:38.800
<v Speaker 1>upload it to twitch Live. But there are lots of

0:39:38.840 --> 0:39:40.759
<v Speaker 1>different ways of doing that. And then when you've got

0:39:40.760 --> 0:39:42.879
<v Speaker 1>things like the Xbox one and the PS four, it's

0:39:42.920 --> 0:39:46.600
<v Speaker 1>incorporated directly into the consoles through the firmware, so that

0:39:46.719 --> 0:39:49.319
<v Speaker 1>one that's taken care of it for you. Right. This

0:39:49.480 --> 0:39:51.680
<v Speaker 1>ease of usability, I think is why it is in

0:39:51.719 --> 0:39:54.200
<v Speaker 1>fact so stink and popular. Um and and you know

0:39:54.200 --> 0:39:57.000
<v Speaker 1>there's that forty five million unique users per month that

0:39:57.040 --> 0:40:00.239
<v Speaker 1>we mentioned earlier is really is nothing to sneeze. No,

0:40:00.360 --> 0:40:02.520
<v Speaker 1>that's huge. And and and it's not just that there are

0:40:02.520 --> 0:40:04.120
<v Speaker 1>a lot of them. It's like the other thing you

0:40:04.200 --> 0:40:06.400
<v Speaker 1>pointed out, Lauren, it's there's a lot of them that

0:40:06.440 --> 0:40:10.719
<v Speaker 1>are watching a really long time. Yeah. They boast that

0:40:10.920 --> 0:40:13.640
<v Speaker 1>per week as a fall that was more viewers than

0:40:13.719 --> 0:40:17.560
<v Speaker 1>Breaking Bed, Tosh point O and the NFL preseason combined.

0:40:17.760 --> 0:40:21.239
<v Speaker 1>That's yeah, I mean that's a significant audience. And you know,

0:40:21.320 --> 0:40:24.719
<v Speaker 1>again they're really engaged. I mean, if I go to

0:40:24.800 --> 0:40:26.880
<v Speaker 1>YouTube and I'll watch a video, a lot of those

0:40:26.960 --> 0:40:29.160
<v Speaker 1>videos tend to be three to ten minutes long. You know,

0:40:29.239 --> 0:40:31.200
<v Speaker 1>there's some that are longer, and I'll watch those two

0:40:31.239 --> 0:40:34.239
<v Speaker 1>depending upon what I'm interested in. You go, maybe a

0:40:34.280 --> 0:40:36.040
<v Speaker 1>link along the side catches your eye and you watch

0:40:36.080 --> 0:40:38.279
<v Speaker 1>something else, but probably you're going to click away. Yeah,

0:40:38.320 --> 0:40:40.879
<v Speaker 1>you don't necessarily stay there for you know, more than

0:40:41.280 --> 0:40:43.520
<v Speaker 1>one or two videos. If you do, I mean, that's

0:40:43.520 --> 0:40:47.320
<v Speaker 1>cool too, but that's probably not the average person's experience.

0:40:47.680 --> 0:40:49.359
<v Speaker 1>You know, like a lot of people watch a YouTube

0:40:49.440 --> 0:40:52.560
<v Speaker 1>video when it's embedded in something else like a Facebook post.

0:40:52.719 --> 0:40:55.040
<v Speaker 1>The typical Twitch user, on the other hand, will stay

0:40:55.080 --> 0:40:57.239
<v Speaker 1>on the site for hours that that average of a

0:40:57.320 --> 0:41:00.280
<v Speaker 1>hundred and six minutes per day that we mentioned are earlier.

0:41:00.960 --> 0:41:02.719
<v Speaker 1>If that's an average, that means there are a lot

0:41:02.800 --> 0:41:06.640
<v Speaker 1>of people watching way longer than that. Oh right, yeah. Um,

0:41:06.800 --> 0:41:09.200
<v Speaker 1>And and the demographic that's going to twitch is a

0:41:09.239 --> 0:41:12.160
<v Speaker 1>really desirable one. The majority is under thirty five. I

0:41:12.160 --> 0:41:14.800
<v Speaker 1>think it's twenty one to twenty nine is the main,

0:41:15.120 --> 0:41:19.200
<v Speaker 1>main portion that that's the group of people that you say, hey,

0:41:19.239 --> 0:41:22.239
<v Speaker 1>these people buy stuff. Yeah, you've got lots of money

0:41:22.320 --> 0:41:24.959
<v Speaker 1>and you're probably willing to give it to me. Yeah,

0:41:25.000 --> 0:41:27.279
<v Speaker 1>so you aren't smart enough yet to know not to know.

0:41:27.400 --> 0:41:30.879
<v Speaker 1>I'm just kidding. I'm just kidding. But yeah. And it's

0:41:30.920 --> 0:41:35.239
<v Speaker 1>also largely male, although there's a growing audience and broadcast

0:41:35.280 --> 0:41:38.440
<v Speaker 1>group of ladies as well. So we're starting to see

0:41:38.719 --> 0:41:42.840
<v Speaker 1>that that demographic is slowly changing. I mean, obviously gaming

0:41:42.880 --> 0:41:47.280
<v Speaker 1>has been very much male domin Yeah, but we're starting

0:41:47.320 --> 0:41:50.000
<v Speaker 1>to see a lot of females get into it because

0:41:50.360 --> 0:41:53.840
<v Speaker 1>they find gaming just as awesome of course, And and

0:41:53.920 --> 0:41:57.600
<v Speaker 1>as as the community changes and as the general standards

0:41:57.600 --> 0:42:01.160
<v Speaker 1>of the industry change, all of that is hopefully fingers

0:42:01.200 --> 0:42:05.399
<v Speaker 1>crossed going to change gender lines, right, So it's it's

0:42:05.440 --> 0:42:08.560
<v Speaker 1>again a growing market, So that's another reason why it's desirable.

0:42:09.000 --> 0:42:11.040
<v Speaker 1>But I mean that kind of engagement where you're going

0:42:11.080 --> 0:42:14.520
<v Speaker 1>to stay focused on something for on average a hundred

0:42:14.600 --> 0:42:19.280
<v Speaker 1>and six minutes. That is why Google is so interested

0:42:19.520 --> 0:42:22.400
<v Speaker 1>in in twitch dot tv. Not only is it lives,

0:42:22.440 --> 0:42:24.719
<v Speaker 1>not only have they done live streaming, and they've done

0:42:24.719 --> 0:42:29.439
<v Speaker 1>it well, they keep people there. Yeah. Yeah, as of now,

0:42:29.560 --> 0:42:33.000
<v Speaker 1>YouTube has really only been toying with live streaming. It

0:42:33.239 --> 0:42:36.960
<v Speaker 1>just opened their YouTube Live services up to the general

0:42:37.040 --> 0:42:41.319
<v Speaker 1>population in December and they haven't really done I mean,

0:42:41.320 --> 0:42:43.279
<v Speaker 1>it hasn't really seen that much traffic. Yeah. The only

0:42:43.280 --> 0:42:46.440
<v Speaker 1>other thing you can use is like the Google Hangouts,

0:42:46.520 --> 0:42:49.839
<v Speaker 1>where you can do a hangout broadcast and that ends

0:42:49.920 --> 0:42:53.320
<v Speaker 1>up broadcasting on YouTube as well, plus on Google Plus

0:42:53.320 --> 0:42:55.320
<v Speaker 1>and that kind of stuff. Um, and I've used that

0:42:55.360 --> 0:42:56.840
<v Speaker 1>a couple of times when I've been a guest on

0:42:56.920 --> 0:43:00.120
<v Speaker 1>other shows. Really I wasn't the one using it, they was.

0:43:00.239 --> 0:43:03.640
<v Speaker 1>I was participating in it. But yeah, it's still like

0:43:03.640 --> 0:43:06.040
<v Speaker 1>you said, it's a niche compared to someone like Twitch

0:43:06.080 --> 0:43:09.359
<v Speaker 1>dot tv that has just this huge audience. So what

0:43:09.360 --> 0:43:14.600
<v Speaker 1>would it mean if Google and Twitch joint forces to

0:43:14.760 --> 0:43:17.200
<v Speaker 1>rule the galaxy. Well, first of all, they might not

0:43:17.320 --> 0:43:20.200
<v Speaker 1>be able to. On a federal level, The Feds might

0:43:20.239 --> 0:43:25.040
<v Speaker 1>try to block this deal based on anti competition by saying, hey, Google,

0:43:25.080 --> 0:43:27.880
<v Speaker 1>you've already got YouTube, You've got you've got user generated

0:43:28.040 --> 0:43:31.040
<v Speaker 1>video sewn up pretty much. Yeah, you're the biggest content

0:43:31.160 --> 0:43:33.560
<v Speaker 1>player and you're trying to merge with the biggest content

0:43:33.640 --> 0:43:36.560
<v Speaker 1>streamer and that's really not okay. So that's a pity.

0:43:36.560 --> 0:43:38.920
<v Speaker 1>So that's a possibility. But if it goes through, it

0:43:38.960 --> 0:43:43.520
<v Speaker 1>would mean access to Twitch users to Google's incredible infrastructure,

0:43:43.920 --> 0:43:47.759
<v Speaker 1>um therefore improving the video quality and uh and lag

0:43:47.840 --> 0:43:51.200
<v Speaker 1>times that users are currently experiencing, which I mean Twitch

0:43:51.239 --> 0:43:54.120
<v Speaker 1>has said themselves that they were not prepared for the

0:43:54.200 --> 0:43:56.000
<v Speaker 1>kind of growth that they have seen and that it's

0:43:56.000 --> 0:43:59.640
<v Speaker 1>a fabulous problem to have. But yeah, it's still a problem.

0:43:59.640 --> 0:44:02.400
<v Speaker 1>It's still problem. So, like I said, Google has a

0:44:02.400 --> 0:44:05.640
<v Speaker 1>lot of experience with this kind of peering relationship, using

0:44:05.640 --> 0:44:08.440
<v Speaker 1>it for other things as well. So h So, in

0:44:08.800 --> 0:44:13.400
<v Speaker 1>at least on a philosophical level, it's from from architecture,

0:44:13.560 --> 0:44:18.120
<v Speaker 1>it's a good fit. I don't know how close twitches

0:44:18.239 --> 0:44:21.040
<v Speaker 1>architecture resembles that of Google on a practical level, but

0:44:21.080 --> 0:44:24.040
<v Speaker 1>philosophically they are very similar, right, and it's so it

0:44:24.080 --> 0:44:27.560
<v Speaker 1>could mean really good things there. It could hypothetically mean

0:44:27.719 --> 0:44:30.880
<v Speaker 1>more money for the people who are broadcasting. Twitch currently

0:44:30.920 --> 0:44:35.680
<v Speaker 1>has some four thousand partner casters who who are paid

0:44:35.880 --> 0:44:37.960
<v Speaker 1>for their casts. Yeah, when you get a certain number

0:44:38.120 --> 0:44:41.400
<v Speaker 1>of subscribers, you tend to get the attention of Twitch.

0:44:41.880 --> 0:44:44.880
<v Speaker 1>So let's say that you suddenly hits some new thousand subscribers,

0:44:44.880 --> 0:44:48.880
<v Speaker 1>which is going to say, hey, we should work together. Yeah,

0:44:48.920 --> 0:44:51.960
<v Speaker 1>this could be beneficial for everyone. Um, but Google could

0:44:52.040 --> 0:44:55.799
<v Speaker 1>possibly do even more for these content creators and if

0:44:55.800 --> 0:44:59.960
<v Speaker 1>nothing else, integrate more seamlessly with searching with YouTube, increasing

0:45:00.320 --> 0:45:06.759
<v Speaker 1>both ad revenue and audience participation. Alternately, it could mean

0:45:06.960 --> 0:45:10.840
<v Speaker 1>changes to the contracts of these professional live streamers, especially

0:45:10.840 --> 0:45:15.520
<v Speaker 1>considering YouTube's pretty strict policies about copyrighted material and on

0:45:15.840 --> 0:45:19.040
<v Speaker 1>region locking. Yeah. I mean a thing that a lot

0:45:19.120 --> 0:45:22.680
<v Speaker 1>of streamers do is they'll they'll have live music. Well

0:45:22.680 --> 0:45:24.160
<v Speaker 1>not live music. I don't think that they have a

0:45:24.160 --> 0:45:26.280
<v Speaker 1>band in their living right, but they have sometimes playing

0:45:26.280 --> 0:45:28.880
<v Speaker 1>in the background while they are playing a game, and

0:45:28.960 --> 0:45:31.120
<v Speaker 1>YouTube is not excited about that sort of thing. Well,

0:45:31.160 --> 0:45:33.279
<v Speaker 1>more importantly, the music in this reason not I'm not

0:45:33.320 --> 0:45:36.359
<v Speaker 1>excited about that. They don't necessarily want their music associated

0:45:36.360 --> 0:45:41.399
<v Speaker 1>with There's also some control issues, like Nintendo historically has

0:45:41.400 --> 0:45:45.520
<v Speaker 1>been very very protective of their of their video games,

0:45:45.560 --> 0:45:49.160
<v Speaker 1>and people who have put up, uh YouTube videos of

0:45:49.200 --> 0:45:51.560
<v Speaker 1>them playing the Nintendo games, a lot of them have

0:45:51.719 --> 0:45:56.399
<v Speaker 1>experienced takedown because Nintendo said, you know what, we want

0:45:56.440 --> 0:45:59.040
<v Speaker 1>to have full control of this experience. We don't like

0:45:59.200 --> 0:46:02.760
<v Speaker 1>the idea of other people being able to do that.

0:46:02.880 --> 0:46:05.239
<v Speaker 1>Nintendo started to ease up a little bit on that

0:46:05.440 --> 0:46:08.799
<v Speaker 1>more recently, but it's traditionally been an issue, and so

0:46:08.880 --> 0:46:12.600
<v Speaker 1>there's no guarantee that every single game publisher is going

0:46:12.640 --> 0:46:15.760
<v Speaker 1>to be totally cool. That's a whole that's a whole

0:46:15.840 --> 0:46:18.560
<v Speaker 1>other issue that I really wish that Nintendo would get with.

0:46:19.360 --> 0:46:21.880
<v Speaker 1>But back back on on the Google deal side, it

0:46:22.200 --> 0:46:26.359
<v Speaker 1>could hypothetically get other demographics than just gamers into this

0:46:26.480 --> 0:46:29.680
<v Speaker 1>live internet streaming kind of stick. Yeah, it's kind of

0:46:29.719 --> 0:46:33.240
<v Speaker 1>the whole purpose of justin dot tv in the first place.

0:46:33.680 --> 0:46:35.719
<v Speaker 1>But Twitch dot tv was the one that took that

0:46:35.800 --> 0:46:37.799
<v Speaker 1>was the part that took off off of justin dot tv.

0:46:37.880 --> 0:46:41.640
<v Speaker 1>And now now that people are getting more familiar or

0:46:41.719 --> 0:46:44.720
<v Speaker 1>aware of this, and also now that Twitch has grown

0:46:44.760 --> 0:46:48.480
<v Speaker 1>it into a very usable process, yeah, that we might

0:46:48.520 --> 0:46:53.520
<v Speaker 1>see more people get into this kind of live broadcast platform. Yeah,

0:46:53.560 --> 0:46:56.600
<v Speaker 1>for for events large and small, for for entertainment, maybe

0:46:56.600 --> 0:47:01.359
<v Speaker 1>for for science kind of discovery broadcasts, for news. I've

0:47:01.400 --> 0:47:04.239
<v Speaker 1>seen a couple of podcasts use this sort of thing

0:47:04.360 --> 0:47:07.000
<v Speaker 1>as to live stream when they were actually recording, so

0:47:07.080 --> 0:47:10.280
<v Speaker 1>you could follow along. Now, before any of you ask,

0:47:10.800 --> 0:47:13.839
<v Speaker 1>that's not gonna happen with us. I think in this

0:47:13.920 --> 0:47:17.440
<v Speaker 1>in this recording alone, we've stopped to cough about nineteen times.

0:47:17.480 --> 0:47:19.480
<v Speaker 1>I in fact, had to stop to cough before I

0:47:19.520 --> 0:47:25.319
<v Speaker 1>recorded this line. She actually started the line, stopped coughed. Yeah, no,

0:47:25.320 --> 0:47:29.080
<v Speaker 1>no one, no one wants that we both have congestion issues.

0:47:29.200 --> 0:47:31.399
<v Speaker 1>So yeah, if you guys were watching live right now,

0:47:31.760 --> 0:47:35.160
<v Speaker 1>it would be cough cough cough cough cough, three paragraphs

0:47:35.200 --> 0:47:38.279
<v Speaker 1>worth of information cough cough cough. Yeah, that that how

0:47:38.320 --> 0:47:42.120
<v Speaker 1>it works. Section took us forever because of me, So yeah,

0:47:42.280 --> 0:47:44.120
<v Speaker 1>we will not be doing that. And even when we're

0:47:44.120 --> 0:47:47.920
<v Speaker 1>feeling well, still not doing it so, but but at

0:47:47.920 --> 0:47:49.920
<v Speaker 1>any rate, I mean, you know this, this could this

0:47:49.920 --> 0:47:53.520
<v Speaker 1>could hypothetically change television as we know it. This could

0:47:53.560 --> 0:47:57.760
<v Speaker 1>be the bridge between network broadcasts and internet viewing. Yeah,

0:47:57.880 --> 0:48:01.720
<v Speaker 1>we could actually see very re regionalized approaches to stuff

0:48:01.760 --> 0:48:05.680
<v Speaker 1>as well as you know, more global appeal kind of broadcasts.

0:48:06.520 --> 0:48:10.800
<v Speaker 1>I've seen some communities do kind of a local news

0:48:10.840 --> 0:48:13.760
<v Speaker 1>broadcast for that community. This sort of thing would allow.

0:48:13.840 --> 0:48:16.720
<v Speaker 1>It's kind of like the public access in that sense,

0:48:16.719 --> 0:48:20.719
<v Speaker 1>and that it's a live way to communicate information out

0:48:20.760 --> 0:48:25.120
<v Speaker 1>whether it's entertainment or educational or news or whatever. You

0:48:25.160 --> 0:48:28.879
<v Speaker 1>can do that on a specific schedule. The other advantageos,

0:48:28.920 --> 0:48:31.880
<v Speaker 1>of course, it does record the videos, so even if

0:48:31.880 --> 0:48:33.680
<v Speaker 1>you aren't able to tune in live, you can still

0:48:33.719 --> 0:48:36.520
<v Speaker 1>watch it, which gives an advantage over other types of

0:48:36.560 --> 0:48:39.759
<v Speaker 1>live broadcasts. Sure, and it's it's on demand all the time.

0:48:39.760 --> 0:48:42.839
<v Speaker 1>It's on the internet. Anyone in the world hypothetically can

0:48:42.920 --> 0:48:45.480
<v Speaker 1>tune into this. Yeah. So let's say that you move

0:48:45.560 --> 0:48:47.720
<v Speaker 1>away from your hometown, but you want to keep tabs

0:48:47.800 --> 0:48:50.480
<v Speaker 1>on it. That could potentially be a way of that happening.

0:48:50.880 --> 0:48:54.440
<v Speaker 1>Or if one performer becomes very popular and and explodes

0:48:54.520 --> 0:48:57.719
<v Speaker 1>across you know, into other communities. That's wonderful. We're still

0:48:57.760 --> 0:49:03.240
<v Speaker 1>waiting make us explode people, you know, in popularity that is, yes, please,

0:49:03.239 --> 0:49:06.279
<v Speaker 1>thank you. Most of my atoms where they are. Yeah,

0:49:06.400 --> 0:49:10.120
<v Speaker 1>I'm pretty fond of where my my constituent atoms happen

0:49:10.160 --> 0:49:13.040
<v Speaker 1>to be as well. So anyway, that's that's the lowdown

0:49:13.160 --> 0:49:16.320
<v Speaker 1>on Twitch dot tv. It'll be really interesting to see

0:49:16.440 --> 0:49:21.720
<v Speaker 1>how this Xbox and PlayStation incorporation ends up, um shaking out. Yeah,

0:49:21.760 --> 0:49:23.680
<v Speaker 1>and whether or not the Google deal goes through. Of course,

0:49:23.719 --> 0:49:26.040
<v Speaker 1>all of you guys know possibly by the time this

0:49:26.080 --> 0:49:29.200
<v Speaker 1>podcast goes live, whether or not that happened, we are

0:49:29.200 --> 0:49:31.839
<v Speaker 1>still in the dark as of the recording, so I'm

0:49:31.880 --> 0:49:34.759
<v Speaker 1>really curious to see how it works out. Yeah. I

0:49:34.800 --> 0:49:37.400
<v Speaker 1>really think it's an exciting development. Thank you so much

0:49:37.480 --> 0:49:40.279
<v Speaker 1>Daniel for the question. Yeah. And and also I mean,

0:49:40.320 --> 0:49:42.640
<v Speaker 1>you know, for for everyone out there who uses Twitch

0:49:42.760 --> 0:49:46.759
<v Speaker 1>and is worried about the deal, uh, you know, I

0:49:47.200 --> 0:49:50.600
<v Speaker 1>understand it's it's scary whenever Google buys a property that

0:49:50.640 --> 0:49:53.880
<v Speaker 1>you are very fond of, especially giving Google's habit of

0:49:54.320 --> 0:49:56.200
<v Speaker 1>you know, saying huh, I don't know how to do

0:49:56.239 --> 0:49:59.560
<v Speaker 1>this anyway, and then shut it down. Yeah. Yeah, but

0:49:59.680 --> 0:50:02.040
<v Speaker 1>you know, I think that it could very much be

0:50:02.160 --> 0:50:05.920
<v Speaker 1>an excellent opportunity for many industries. So I think. Uh.

0:50:06.280 --> 0:50:08.239
<v Speaker 1>The other important thing to take away from this is

0:50:08.280 --> 0:50:11.000
<v Speaker 1>the idea of Microsoft trying to buy Twitch and being

0:50:11.000 --> 0:50:14.200
<v Speaker 1>turned down should give all of you Sony PlayStation four

0:50:14.239 --> 0:50:17.319
<v Speaker 1>owners a big sigh of relief. I mean, I can

0:50:17.400 --> 0:50:20.480
<v Speaker 1>only imagine if and Google has someone of a vested

0:50:20.520 --> 0:50:23.520
<v Speaker 1>interest in this. But Google doesn't have its own gaming

0:50:23.600 --> 0:50:27.400
<v Speaker 1>console out. You could argue that Android is a platform

0:50:27.480 --> 0:50:30.080
<v Speaker 1>for games, but it's just one platform. It's not the

0:50:30.480 --> 0:50:33.719
<v Speaker 1>main purpose for Android. Um. But you know, since they

0:50:33.760 --> 0:50:37.440
<v Speaker 1>don't have a vested interest necessarily, and whether Microsoft succeeds

0:50:37.480 --> 0:50:40.600
<v Speaker 1>over Sony, you don't have to worry about Twitch suddenly

0:50:40.640 --> 0:50:43.200
<v Speaker 1>losing support for something like the PlayStation four, which is

0:50:43.239 --> 0:50:46.440
<v Speaker 1>something I would legitimately worry about if Microsoft had bought Twitch,

0:50:46.719 --> 0:50:48.800
<v Speaker 1>I would really be curious to see how they would

0:50:49.200 --> 0:50:53.279
<v Speaker 1>resist that urge. So at least that that danger is

0:50:53.280 --> 0:50:56.400
<v Speaker 1>not on the table anymore. Daniel, thank you again for

0:50:56.480 --> 0:50:59.080
<v Speaker 1>your suggestion. If you would like to send us a

0:50:59.080 --> 0:51:02.040
<v Speaker 1>message like Daniel did, well, if you want to be

0:51:02.080 --> 0:51:04.359
<v Speaker 1>just like Daniel, you need to do the email thing

0:51:04.640 --> 0:51:08.719
<v Speaker 1>and our email addresses tech stuff at Discovery dot com,

0:51:08.840 --> 0:51:11.200
<v Speaker 1>or you can drop us a line on Facebook or Twitter.

0:51:11.280 --> 0:51:13.560
<v Speaker 1>Our handle is tech stuff hs W. Hey, we got

0:51:13.600 --> 0:51:16.719
<v Speaker 1>a tumbler too, which is awesome. Text Stuff HSW for

0:51:16.760 --> 0:51:19.400
<v Speaker 1>that as well, so check that out. Leave us a message,

0:51:19.480 --> 0:51:21.960
<v Speaker 1>let's know what you think, give us suggestions for topics,

0:51:22.000 --> 0:51:27.400
<v Speaker 1>and we will talk to you again really soon for

0:51:27.520 --> 0:51:29.840
<v Speaker 1>more on this and thousands of other topics because it

0:51:29.920 --> 0:51:40.880
<v Speaker 1>how staff works dot com