WEBVTT - TechStuff Gets MegaUploaded

0:00:02.360 --> 0:00:05.360
<v Speaker 1>Get in touch with technology with tech Stuff from how

0:00:05.400 --> 0:00:13.960
<v Speaker 1>stuff works dot com. Hello everyone, and welcome to tech stuff.

0:00:13.960 --> 0:00:15.640
<v Speaker 1>My name is Chris Polette and I am an editor

0:00:15.640 --> 0:00:18.239
<v Speaker 1>at how stuff works dot com, stating incrust from me

0:00:18.280 --> 0:00:24.680
<v Speaker 1>as usual as senior writer Jonathan st Hey. There, So, um, today,

0:00:24.680 --> 0:00:29.720
<v Speaker 1>we wanted to talk about a controversial subject, a couple

0:00:29.720 --> 0:00:32.960
<v Speaker 1>of different controversial subjects. Right, there's a mega controversy, yes,

0:00:33.440 --> 0:00:37.720
<v Speaker 1>mega upload, and uh, many of you have probably heard

0:00:37.720 --> 0:00:39.800
<v Speaker 1>about mega upload. Some of you may have even used

0:00:39.840 --> 0:00:42.120
<v Speaker 1>the service. Some of you may be going to mega

0:00:42.240 --> 0:00:44.440
<v Speaker 1>upload dot com right now and wondering if you're in

0:00:44.440 --> 0:00:47.839
<v Speaker 1>trouble because you see that there's a big takedown notice

0:00:47.880 --> 0:00:51.600
<v Speaker 1>where the site used to be. But we wanted to

0:00:51.600 --> 0:00:54.560
<v Speaker 1>talk about what it is, what the controversy is around it,

0:00:54.720 --> 0:00:58.680
<v Speaker 1>what the various legal issues are surrounding it, and a

0:00:58.720 --> 0:01:03.120
<v Speaker 1>lot about the Uh. I guess flamboyant is an appropriate word,

0:01:03.440 --> 0:01:11.240
<v Speaker 1>uh head of mega upload Kim dot com. Yes, um, yeah,

0:01:11.280 --> 0:01:14.360
<v Speaker 1>So I guess we can start off why not at

0:01:14.400 --> 0:01:18.119
<v Speaker 1>the beginning, back in two thousand five Kim dot com.

0:01:18.120 --> 0:01:20.559
<v Speaker 1>And when I say at the beginning, I'll go back

0:01:20.600 --> 0:01:22.480
<v Speaker 1>further than this later on and we talk about the

0:01:22.560 --> 0:01:28.160
<v Speaker 1>legal issues, but he founded a site. UH turned out

0:01:28.160 --> 0:01:30.480
<v Speaker 1>to be a family of sites, but we tend to

0:01:30.520 --> 0:01:34.240
<v Speaker 1>just call it mega upload. And the idea behind this

0:01:34.600 --> 0:01:40.520
<v Speaker 1>was kind of like a very specific implementation of cloud storage.

0:01:41.640 --> 0:01:46.920
<v Speaker 1>So the idea was that users could upload files to

0:01:47.080 --> 0:01:50.280
<v Speaker 1>this service, mega upload, and then allow other people to

0:01:50.440 --> 0:01:55.520
<v Speaker 1>download those files and on its own. If that's all

0:01:55.560 --> 0:01:59.520
<v Speaker 1>we say, that's not there's nothing controversial about that. That's

0:01:59.560 --> 0:02:05.680
<v Speaker 1>just a method of distributing data. The problem comes in

0:02:06.120 --> 0:02:08.520
<v Speaker 1>as to the nature of that data and whether or

0:02:08.560 --> 0:02:13.880
<v Speaker 1>not that data had any intellectual property rights associated with it.

0:02:13.919 --> 0:02:17.240
<v Speaker 1>That perhaps the user who uploaded the file did not

0:02:17.440 --> 0:02:22.280
<v Speaker 1>have access to our authorization to uh to distribute that file,

0:02:22.400 --> 0:02:25.120
<v Speaker 1>and that's the crux of the problem. So mega upload

0:02:25.360 --> 0:02:28.919
<v Speaker 1>is what we call locker site, and you you create

0:02:28.960 --> 0:02:31.920
<v Speaker 1>a locker where you upload the files other people can

0:02:31.960 --> 0:02:34.600
<v Speaker 1>download them and UH. And there are some interesting things

0:02:34.600 --> 0:02:39.920
<v Speaker 1>about mega upload. For example, UH, uploading a file didn't

0:02:40.120 --> 0:02:44.280
<v Speaker 1>guarantee that file was going to be stored there forever. UH.

0:02:44.320 --> 0:02:48.120
<v Speaker 1>The the service would actually delete files out of its

0:02:48.160 --> 0:02:53.800
<v Speaker 1>storage if they were not being downloaded enough. At least

0:02:53.800 --> 0:02:56.280
<v Speaker 1>that was sort of the that was the allegation that

0:02:56.360 --> 0:03:00.000
<v Speaker 1>the United States government made against mega upload. When building

0:03:00.040 --> 0:03:03.280
<v Speaker 1>its case, they said that in order for a file

0:03:03.400 --> 0:03:05.639
<v Speaker 1>to be hosted, it had to be popular, It had

0:03:05.639 --> 0:03:08.360
<v Speaker 1>to reach a certain threshold of popularity, and if people

0:03:08.360 --> 0:03:10.680
<v Speaker 1>stopp downloading it, the file would no longer be hosted

0:03:10.680 --> 0:03:14.560
<v Speaker 1>on mega upload UM. So that's kind of a way

0:03:14.560 --> 0:03:17.480
<v Speaker 1>of to conserve space. You know, the files that are

0:03:17.480 --> 0:03:21.040
<v Speaker 1>really popular stay available. Files no one seems to want

0:03:21.200 --> 0:03:23.840
<v Speaker 1>go away, and you don't have to worry about hosting

0:03:24.040 --> 0:03:27.760
<v Speaker 1>a file forever. Because of course, the more popular the

0:03:27.800 --> 0:03:33.480
<v Speaker 1>site got, the larger it's UM requirements were to for

0:03:33.480 --> 0:03:37.000
<v Speaker 1>for hosting space because I mean, these digital files are

0:03:37.000 --> 0:03:41.480
<v Speaker 1>taking up hard drive space somewhere on servers, so you

0:03:41.520 --> 0:03:44.280
<v Speaker 1>have to be able to, uh to meet that demand.

0:03:44.360 --> 0:03:47.000
<v Speaker 1>And one way of doing that is to phase out

0:03:47.120 --> 0:03:53.480
<v Speaker 1>any files that are not particularly sought after. Yeah. Now

0:03:53.520 --> 0:03:56.800
<v Speaker 1>you might be saying, you know, well, how is this

0:03:56.920 --> 0:04:03.520
<v Speaker 1>different from something like dropbox or perhaps YouTube um? And

0:04:03.600 --> 0:04:07.960
<v Speaker 1>there are big differences, UM, because some of the charges

0:04:08.160 --> 0:04:13.240
<v Speaker 1>that have been filed basically accused the people behind mega

0:04:13.360 --> 0:04:16.279
<v Speaker 1>upload UM. Kim dot com is sort of the face

0:04:16.360 --> 0:04:19.800
<v Speaker 1>of mega upload, but the he had a handful of

0:04:19.839 --> 0:04:23.680
<v Speaker 1>partners who were closely were you know, working on it

0:04:23.720 --> 0:04:26.760
<v Speaker 1>with him very closely. Um. So the people behind mega

0:04:26.839 --> 0:04:33.640
<v Speaker 1>upload have been charged with basically, um, not only providing

0:04:33.720 --> 0:04:37.680
<v Speaker 1>storage space, but knowing what was in that storage space

0:04:37.760 --> 0:04:43.280
<v Speaker 1>and encouraging people to upload popular content which may or

0:04:43.440 --> 0:04:49.040
<v Speaker 1>may not have been um, you know, stuff that violated copyright.

0:04:49.160 --> 0:04:51.520
<v Speaker 1>And and that's really that that's you know, the question.

0:04:51.520 --> 0:04:54.080
<v Speaker 1>Those are the questions that you know, how how far

0:04:54.360 --> 0:04:57.840
<v Speaker 1>did it go? Allegations. The allegations actually go so far

0:04:57.880 --> 0:05:01.839
<v Speaker 1>as to claim that the uh, the owners of mega

0:05:01.920 --> 0:05:06.800
<v Speaker 1>upload paid out money to people in order to encourage

0:05:06.839 --> 0:05:10.560
<v Speaker 1>them to upload popular files. And by popular, we're talking

0:05:10.560 --> 0:05:14.640
<v Speaker 1>about stuff that violates intellectual property. Uh. When you when

0:05:14.640 --> 0:05:16.840
<v Speaker 1>you just say popular, that could be anything, but in

0:05:17.120 --> 0:05:21.200
<v Speaker 1>the case that was brought against mega upload and its founders,

0:05:21.560 --> 0:05:24.880
<v Speaker 1>they're specifically talking about things like movies or music. Really

0:05:24.960 --> 0:05:27.760
<v Speaker 1>movies is the big one, but it's not just movies.

0:05:27.800 --> 0:05:30.800
<v Speaker 1>It's television and music as well. Saying all right, well,

0:05:31.440 --> 0:05:37.120
<v Speaker 1>there are people uploading entire libraries of files to your site. Uh,

0:05:37.160 --> 0:05:39.440
<v Speaker 1>they don't have the authorization to do that. People are

0:05:39.640 --> 0:05:46.080
<v Speaker 1>essentially using mega upload to perpetuate piracy, and so ultimately,

0:05:46.160 --> 0:05:48.400
<v Speaker 1>and when you look at this, you can figure out

0:05:48.440 --> 0:05:54.200
<v Speaker 1>there are certain industries that are very much pushing for

0:05:55.040 --> 0:05:59.040
<v Speaker 1>action against Mega upload. It's it's pretty safe to say

0:05:59.080 --> 0:06:03.400
<v Speaker 1>that this was not just a government agency saying, oh,

0:06:03.560 --> 0:06:05.200
<v Speaker 1>here's a bad guy, we need to go after him.

0:06:05.279 --> 0:06:09.520
<v Speaker 1>This these are industries that are using political pressure to

0:06:09.760 --> 0:06:13.919
<v Speaker 1>go after a company that they see as a threat

0:06:13.960 --> 0:06:17.240
<v Speaker 1>to their business model. Then, in itself is not necessarily

0:06:17.279 --> 0:06:20.359
<v Speaker 1>a bad thing. You want to protect your business, you know, otherwise,

0:06:20.400 --> 0:06:24.360
<v Speaker 1>if you don't protect your business, you go out of business. However,

0:06:24.400 --> 0:06:29.760
<v Speaker 1>there are some questions as to the execution of this

0:06:30.000 --> 0:06:34.200
<v Speaker 1>and whether or not it oversteps bounds. For example, a

0:06:34.320 --> 0:06:37.960
<v Speaker 1>mega upload we haven't mentioned this yet. It is a company.

0:06:38.000 --> 0:06:41.440
<v Speaker 1>It's a company that's based The company itself is based

0:06:41.440 --> 0:06:45.400
<v Speaker 1>out of Hong Kong. So that raises some questions because

0:06:45.880 --> 0:06:50.000
<v Speaker 1>it's the United States that's primarily going after Kim dot

0:06:50.000 --> 0:06:54.560
<v Speaker 1>Com and the other people behind Mega Upload, and the

0:06:54.640 --> 0:06:58.000
<v Speaker 1>United States does not have jurisdiction in Hong Kong. On

0:06:58.080 --> 0:07:01.360
<v Speaker 1>top of that, Kim dot com, um and the other

0:07:01.400 --> 0:07:04.560
<v Speaker 1>people who were rounded up we'll talk about the roundup

0:07:04.560 --> 0:07:08.040
<v Speaker 1>in a second. They were all in New Zealand, also

0:07:08.560 --> 0:07:13.680
<v Speaker 1>last I checked, not within the jurisdiction of the United States. Yeah, um,

0:07:14.320 --> 0:07:17.080
<v Speaker 1>pretty sure. I mean I could be wrong. It could

0:07:17.080 --> 0:07:19.520
<v Speaker 1>be that in the Hobbit, I'll see that, you know,

0:07:19.720 --> 0:07:24.040
<v Speaker 1>federal agents are knocking down the enemy's door and uh

0:07:24.120 --> 0:07:30.120
<v Speaker 1>and in Mirkwood spoiler alert. But it would surprise me. Um, however,

0:07:30.240 --> 0:07:32.800
<v Speaker 1>some of the company's servers were based here in the

0:07:32.920 --> 0:07:35.840
<v Speaker 1>United States. That that was one thing. Yeah, but that

0:07:35.920 --> 0:07:39.800
<v Speaker 1>was done on purpose. Um why was that down on purpose? Well?

0:07:39.880 --> 0:07:45.160
<v Speaker 1>Remember when I mentioned YouTube a few minutes ago. Um, well, YouTube,

0:07:45.800 --> 0:07:51.480
<v Speaker 1>from time to time people upload content to the site

0:07:51.520 --> 0:07:55.080
<v Speaker 1>that infringes on someone's copyright. You know, they take and

0:07:55.200 --> 0:07:58.440
<v Speaker 1>rip a movie and stick it on YouTube, which is

0:07:59.080 --> 0:08:03.120
<v Speaker 1>pretty much blatantly illegal. The thing is, what the idea

0:08:03.320 --> 0:08:07.960
<v Speaker 1>is that under current uh United States law, the copyright

0:08:08.000 --> 0:08:10.600
<v Speaker 1>owner can contact YouTube and say, hey, take that down.

0:08:10.640 --> 0:08:13.680
<v Speaker 1>And YouTube is supposed to take it down, and and

0:08:13.760 --> 0:08:18.760
<v Speaker 1>Kim Kim dot com has said that Mega Upload did that. Um.

0:08:18.840 --> 0:08:21.720
<v Speaker 1>Now see there there's there's what is called safe Haven,

0:08:21.960 --> 0:08:24.679
<v Speaker 1>which was part of the d m C a Digital

0:08:24.720 --> 0:08:28.680
<v Speaker 1>millennium right, and basically it says, hey, look, you know

0:08:29.080 --> 0:08:32.240
<v Speaker 1>you're providing the storage space online that doesn't make you

0:08:32.280 --> 0:08:37.200
<v Speaker 1>necessarily liable for what people do with that space. If

0:08:37.240 --> 0:08:41.240
<v Speaker 1>they put uh material up there that infringes upon someone's copyright,

0:08:41.960 --> 0:08:43.839
<v Speaker 1>as long as you take it down when you're asked

0:08:43.840 --> 0:08:46.319
<v Speaker 1>to by the copyright holder, that's not it's not your

0:08:46.320 --> 0:08:48.640
<v Speaker 1>fault that that people do that. What they're saying that

0:08:48.679 --> 0:08:54.760
<v Speaker 1>Mega upload did, however, was um basically not only uh

0:08:55.280 --> 0:08:59.000
<v Speaker 1>host that they didn't necessarily take it down immediately upon

0:08:59.080 --> 0:09:01.640
<v Speaker 1>being asked. They might have been selective in what they

0:09:01.679 --> 0:09:06.280
<v Speaker 1>took down, and they were encouraging people to post popular content.

0:09:06.920 --> 0:09:11.160
<v Speaker 1>So they're saying, no, you guys don't qualify for safe haven.

0:09:11.520 --> 0:09:14.199
<v Speaker 1>This is completely different. And they're being brought up on

0:09:14.280 --> 0:09:19.840
<v Speaker 1>criminal charges um, which is different than a simple lawsuit. Hey,

0:09:19.840 --> 0:09:22.880
<v Speaker 1>we're suing you because you did not take this down. Yeah.

0:09:22.880 --> 0:09:25.760
<v Speaker 1>The the d m c A is very uh it

0:09:25.840 --> 0:09:28.800
<v Speaker 1>lays this out in a very specific way that the

0:09:28.840 --> 0:09:32.600
<v Speaker 1>ideas that it will protect these service providers so that

0:09:32.640 --> 0:09:36.960
<v Speaker 1>they are not um shouldered with all the responsibility for

0:09:37.080 --> 0:09:39.920
<v Speaker 1>providing what is a valuable service to people who might

0:09:40.040 --> 0:09:42.640
<v Speaker 1>use it in ways for which it was not intended

0:09:43.200 --> 0:09:46.400
<v Speaker 1>or in illegal ways. Uh. So you can argue whether

0:09:46.480 --> 0:09:49.520
<v Speaker 1>or not Mega upload was intended for illegal use or not.

0:09:49.640 --> 0:09:54.000
<v Speaker 1>That's in fact the federal h federal officials are very

0:09:54.080 --> 0:09:57.560
<v Speaker 1>much making that argument. But UH for the d m

0:09:57.600 --> 0:09:59.720
<v Speaker 1>c A to apply for that safe haven to apply,

0:10:00.640 --> 0:10:07.840
<v Speaker 1>the the owners of the service cannot knowingly host illegal material.

0:10:08.200 --> 0:10:10.360
<v Speaker 1>That they are told about the illegal material, they have

0:10:10.440 --> 0:10:13.640
<v Speaker 1>to remove it. One of the allegations against Kim dot

0:10:13.679 --> 0:10:16.440
<v Speaker 1>Com and mega upload is that when they were told

0:10:16.440 --> 0:10:19.680
<v Speaker 1>about illegal material, what they would do is remove a

0:10:19.800 --> 0:10:23.439
<v Speaker 1>link to that illegal material, but they would not remove

0:10:23.760 --> 0:10:26.040
<v Speaker 1>the file itself. So in other words, the file still

0:10:26.040 --> 0:10:30.440
<v Speaker 1>exists on mega upload. They just removed whatever link was reported. Well,

0:10:30.480 --> 0:10:32.679
<v Speaker 1>the way mega upload worked was that if you were

0:10:32.720 --> 0:10:34.920
<v Speaker 1>to try and upload a file, Let's say that let's

0:10:34.920 --> 0:10:38.160
<v Speaker 1>say Chris and I have decided to UH to throw

0:10:38.200 --> 0:10:41.640
<v Speaker 1>caution to the wind and embrace our darker natures and

0:10:41.760 --> 0:10:47.360
<v Speaker 1>to UH to dive headfirst into the world of illicit

0:10:47.559 --> 0:10:52.080
<v Speaker 1>film trading online. And so Chris and I both have

0:10:52.280 --> 0:10:54.480
<v Speaker 1>the same idea. At the same time, we have both

0:10:54.480 --> 0:10:58.440
<v Speaker 1>decided that now is the time for us to upload

0:10:58.920 --> 0:11:03.120
<v Speaker 1>a copy of the Steven Spielberg Mega hit Howard the Duck,

0:11:03.720 --> 0:11:06.560
<v Speaker 1>And so Chris uploads Howard the Duck before I do,

0:11:06.760 --> 0:11:11.200
<v Speaker 1>because he has a better internet connection. So that Howard

0:11:11.200 --> 0:11:14.240
<v Speaker 1>the Duck file that specific hash gets uploaded up to

0:11:14.480 --> 0:11:17.040
<v Speaker 1>mega upload, and then I do the same thing. Now

0:11:17.160 --> 0:11:19.440
<v Speaker 1>the file that I'm using is based off the same

0:11:19.480 --> 0:11:21.679
<v Speaker 1>one that Chris made, so it's got the same data,

0:11:21.800 --> 0:11:25.400
<v Speaker 1>same everything. When I uploaded, mega upload looks and says, oh,

0:11:25.400 --> 0:11:28.360
<v Speaker 1>wait a minute, I've already got this file. So instead

0:11:28.360 --> 0:11:30.920
<v Speaker 1>of uploading this to your locker, why don't you, uh,

0:11:31.080 --> 0:11:33.600
<v Speaker 1>would you prefer it if we just um linked to

0:11:33.720 --> 0:11:37.320
<v Speaker 1>it and added another link to the already existing file

0:11:37.360 --> 0:11:40.160
<v Speaker 1>because it's the same information. This way, you don't have

0:11:40.200 --> 0:11:42.880
<v Speaker 1>to upload the whole thing. You just add the link.

0:11:43.200 --> 0:11:45.480
<v Speaker 1>And you say, because you don't want to have to,

0:11:45.720 --> 0:11:47.600
<v Speaker 1>you know, come up your internet connection all that time,

0:11:47.720 --> 0:11:50.000
<v Speaker 1>or I say, in this case, because it's using my example,

0:11:50.240 --> 0:11:53.479
<v Speaker 1>I said, sure, just put the link in. Well. The complaint,

0:11:53.720 --> 0:11:56.600
<v Speaker 1>one of the complaints that the FEDS made against mega

0:11:56.640 --> 0:12:01.080
<v Speaker 1>upload is that if you were the content owner, if

0:12:01.120 --> 0:12:03.520
<v Speaker 1>you're the intellectual property rights owner of Howard the Duck

0:12:04.400 --> 0:12:06.280
<v Speaker 1>of the film Howard the Duck, and you wanted to

0:12:06.280 --> 0:12:09.640
<v Speaker 1>protect it, and you saw that there was a link

0:12:09.840 --> 0:12:14.440
<v Speaker 1>to a mega upload locker that contained that movie. You

0:12:14.480 --> 0:12:17.360
<v Speaker 1>would send that complaint to Mega upload and then they

0:12:17.360 --> 0:12:22.520
<v Speaker 1>would apparently remove the link, the specific link you mentioned. However,

0:12:23.480 --> 0:12:26.079
<v Speaker 1>I also have a link to that content. It's a

0:12:26.120 --> 0:12:30.120
<v Speaker 1>different link. It's the same file, which means that because

0:12:30.160 --> 0:12:32.800
<v Speaker 1>they did not delete the file itself, there's still a

0:12:32.840 --> 0:12:35.680
<v Speaker 1>pathway to get to that file. All they did was

0:12:35.760 --> 0:12:39.000
<v Speaker 1>close off one path, but they left another path open.

0:12:39.640 --> 0:12:43.000
<v Speaker 1>That's the allegation. That's what the federal federal officers are saying.

0:12:43.000 --> 0:12:46.040
<v Speaker 1>They're saying, well, yeah, you would remove this link, but

0:12:46.120 --> 0:12:48.480
<v Speaker 1>the file still existed and there were still other links

0:12:48.520 --> 0:12:51.000
<v Speaker 1>to that file, so you didn't solve the problem. All

0:12:51.040 --> 0:12:55.400
<v Speaker 1>you did was close one door, but there were you know, however,

0:12:55.920 --> 0:12:59.120
<v Speaker 1>other many doors open, so people could still get to

0:12:59.200 --> 0:13:03.240
<v Speaker 1>it and the problem was not fixed. Um. So that's

0:13:03.320 --> 0:13:07.600
<v Speaker 1>that's one of the main arguments here. Now. The way

0:13:07.600 --> 0:13:10.319
<v Speaker 1>this all went down was way back on January nine,

0:13:10.600 --> 0:13:16.199
<v Speaker 1>two twelve. Do you remember January two thousand twelve, back

0:13:16.240 --> 0:13:17.920
<v Speaker 1>when we were wondering if Apple was going to have

0:13:17.960 --> 0:13:20.320
<v Speaker 1>an iPad three and no idea that they would also

0:13:20.360 --> 0:13:25.720
<v Speaker 1>have an iPod pot iPad four that same year. Um,

0:13:25.760 --> 0:13:28.600
<v Speaker 1>that's just a light dig so on January nineteenth, the

0:13:28.880 --> 0:13:35.000
<v Speaker 1>Department of Justice seized the UH mega upload dot com

0:13:35.120 --> 0:13:38.000
<v Speaker 1>site and all of its family of sites like mega

0:13:38.080 --> 0:13:41.160
<v Speaker 1>video and things like that, and they shut it down

0:13:42.080 --> 0:13:46.440
<v Speaker 1>and they began to pursue a criminal case against the

0:13:46.480 --> 0:13:52.480
<v Speaker 1>owners and operators of that site. On January two thousand twelve,

0:13:52.880 --> 0:13:57.600
<v Speaker 1>Hong Kong Customs ended up freezing assets belonging to the

0:13:57.640 --> 0:14:02.960
<v Speaker 1>company and UH on that. On January twenty, in New Zealand,

0:14:03.720 --> 0:14:11.000
<v Speaker 1>UH New Zealand police, acting under the the direction of

0:14:11.280 --> 0:14:17.320
<v Speaker 1>United States federal officers, led a raid against a mansion

0:14:17.559 --> 0:14:21.720
<v Speaker 1>that was being leased by Kim dot com UM and

0:14:21.960 --> 0:14:25.920
<v Speaker 1>had happened to have several other Mega upload people there

0:14:25.960 --> 0:14:28.120
<v Speaker 1>at the time because they were celebrating his birthday, so

0:14:28.160 --> 0:14:33.400
<v Speaker 1>they timed it out to raid on his birthday. UH

0:14:34.640 --> 0:14:40.200
<v Speaker 1>they went in, they seized around seventeen million dollars worth

0:14:40.240 --> 0:14:44.720
<v Speaker 1>of assets, including vehicles and art, so stuff that was

0:14:44.760 --> 0:14:50.200
<v Speaker 1>not related directly to the website. But the federal officers

0:14:50.240 --> 0:14:53.400
<v Speaker 1>claimed that these are things that Kim dot com bought

0:14:53.960 --> 0:14:59.360
<v Speaker 1>through money laundering and other means. UM specifically that that

0:14:59.440 --> 0:15:04.160
<v Speaker 1>allegation s and that Mega upload paid people to upload

0:15:04.680 --> 0:15:07.840
<v Speaker 1>illegal material to their site. Um and if you're wondering

0:15:07.840 --> 0:15:10.320
<v Speaker 1>how does mega upload make money, because we didn't really

0:15:10.320 --> 0:15:13.120
<v Speaker 1>talk about that. There's two ways you could be a subscriber,

0:15:13.480 --> 0:15:16.040
<v Speaker 1>but that's really the it's kind of a minor way

0:15:16.040 --> 0:15:20.200
<v Speaker 1>that they generate revenue. They mostly generate rate revenue through ads. Well,

0:15:20.240 --> 0:15:24.120
<v Speaker 1>they serve up ads over when when you're downloading, that's

0:15:24.120 --> 0:15:26.000
<v Speaker 1>when the ads get served to you. So if you

0:15:26.080 --> 0:15:28.560
<v Speaker 1>download a file, that's when you start seeing these ads.

0:15:28.600 --> 0:15:31.880
<v Speaker 1>So there's an incentive to provide as many downloads as

0:15:31.920 --> 0:15:34.960
<v Speaker 1>possible because the more downloads there are, the more ads

0:15:35.040 --> 0:15:39.640
<v Speaker 1>Mega upload serves, the more money it gets. So that's

0:15:39.640 --> 0:15:43.560
<v Speaker 1>where a lot of this cash came from. So uh

0:15:43.600 --> 0:15:48.200
<v Speaker 1>that that all went down on January and went pretty quickly,

0:15:49.400 --> 0:15:53.640
<v Speaker 1>but dot com And was not resting. He hired on

0:15:53.720 --> 0:15:58.080
<v Speaker 1>some lawyers and began to fight back against the actions

0:15:58.120 --> 0:16:01.760
<v Speaker 1>taken against him and against Mega Upload. So March five,

0:16:01.840 --> 0:16:05.120
<v Speaker 1>two thousand twelve, the United States files for an extradition

0:16:05.320 --> 0:16:08.560
<v Speaker 1>request for in New Zealand courts, saying we want to

0:16:08.600 --> 0:16:11.920
<v Speaker 1>extradite him to the US and try him there for crimes.

0:16:12.400 --> 0:16:15.840
<v Speaker 1>Keeping in mind again Hong Kong Company New Zealand resident

0:16:15.960 --> 0:16:19.440
<v Speaker 1>actually New Zealand citizen. He or he I guess resident

0:16:19.480 --> 0:16:21.240
<v Speaker 1>is the right word. He did apply for residency and

0:16:21.280 --> 0:16:25.320
<v Speaker 1>was granted it. He's actually German, German born. Yeah, see

0:16:25.320 --> 0:16:27.240
<v Speaker 1>what you could tell by the dot com last name.

0:16:27.640 --> 0:16:30.960
<v Speaker 1>Actually he changed that name. He changed that name partially

0:16:30.960 --> 0:16:33.360
<v Speaker 1>because of his his childhood. Yeah, he was. He was.

0:16:33.720 --> 0:16:39.000
<v Speaker 1>His original name is Kim Schmitz. And actually his his

0:16:39.720 --> 0:16:43.000
<v Speaker 1>past is definitely one of the reasons why there's so

0:16:43.080 --> 0:16:47.360
<v Speaker 1>much interest in him and why I think, uh, the

0:16:47.440 --> 0:16:50.440
<v Speaker 1>United States government felt fairly confident going after him because

0:16:50.480 --> 0:16:53.520
<v Speaker 1>he he is not He doesn't have a squeaky clean past.

0:16:54.320 --> 0:16:58.080
<v Speaker 1>He was he was tried for embezzlement. He was a

0:16:58.120 --> 0:17:04.040
<v Speaker 1>teenage internet sensation in a sense and like an investment sensation,

0:17:04.560 --> 0:17:09.720
<v Speaker 1>and was was accused of with charges of insider trading.

0:17:10.359 --> 0:17:18.240
<v Speaker 1>And sorry, keep trying to interrupt, I shouldn't I apologize. Um.

0:17:18.280 --> 0:17:21.679
<v Speaker 1>There's a great article in Wired magazine and on Wired

0:17:21.720 --> 0:17:25.800
<v Speaker 1>dot com about him that Charles Graber wrote, UM actually

0:17:25.800 --> 0:17:30.960
<v Speaker 1>brought the dead Tree version with me. Subscribe to to it. Um,

0:17:31.040 --> 0:17:34.080
<v Speaker 1>But yeah, it's definitely it's a really did you read

0:17:34.080 --> 0:17:36.879
<v Speaker 1>this in your research? UM? I thought it was a

0:17:36.920 --> 0:17:42.199
<v Speaker 1>really good balanced article. Because it talks about some of

0:17:42.359 --> 0:17:45.240
<v Speaker 1>his more positive you know, attempts to be more positive

0:17:45.600 --> 0:17:47.720
<v Speaker 1>and some of his past which has been you know,

0:17:47.840 --> 0:17:49.520
<v Speaker 1>not always on the up and up. I mean he

0:17:49.840 --> 0:17:53.520
<v Speaker 1>in school, he wasn't really a dedicated student. He preferred

0:17:53.520 --> 0:17:56.560
<v Speaker 1>to uh apparently likes to sleep late, and he liked

0:17:56.600 --> 0:17:59.840
<v Speaker 1>to skip class and sleep in basically, but he got

0:17:59.840 --> 0:18:04.200
<v Speaker 1>an interested in computers when he was a teenager and

0:18:04.200 --> 0:18:06.480
<v Speaker 1>and really embraced it. He took off with it. Yeah,

0:18:06.560 --> 0:18:12.120
<v Speaker 1>he hacked into some pretty uh pretty notable systems like NASA.

0:18:12.800 --> 0:18:17.840
<v Speaker 1>So he's definitely got He's definitely got a history of

0:18:17.880 --> 0:18:22.560
<v Speaker 1>being somewhat of a mischief maker. But he got a

0:18:22.560 --> 0:18:25.480
<v Speaker 1>good scare when he was a kid too. He got

0:18:25.560 --> 0:18:28.960
<v Speaker 1>in trouble with the law, and uh, basically I get

0:18:29.000 --> 0:18:30.840
<v Speaker 1>the sense or at least the article paints him and

0:18:30.960 --> 0:18:34.160
<v Speaker 1>somebody who uh say, you know, once he got done

0:18:34.200 --> 0:18:36.320
<v Speaker 1>with that, said hey, I I really don't want to

0:18:36.320 --> 0:18:38.359
<v Speaker 1>mess with this again. But the thing is too he

0:18:38.440 --> 0:18:41.480
<v Speaker 1>also and this also does not paint or did not

0:18:41.640 --> 0:18:48.120
<v Speaker 1>did not help him with this um recent arrest. And uh,

0:18:48.240 --> 0:18:53.160
<v Speaker 1>he kind of paints himself as a high roller gangster type. Yeah,

0:18:53.160 --> 0:18:57.480
<v Speaker 1>he's that seventeen million dollars with the art some of

0:18:57.480 --> 0:18:59.359
<v Speaker 1>those cars that they see, He's like some of the

0:18:59.400 --> 0:19:02.879
<v Speaker 1>cars were hundreds of thousands of dollars in value for

0:19:02.920 --> 0:19:06.439
<v Speaker 1>an individual car. One of us associates said, Hey, you know,

0:19:06.480 --> 0:19:09.800
<v Speaker 1>we have a big car with a license plate that

0:19:09.800 --> 0:19:13.120
<v Speaker 1>says mafia on it. But we're we're fooling around. We're

0:19:13.119 --> 0:19:16.439
<v Speaker 1>not serious about that stuff, right. It's but the government

0:19:18.480 --> 0:19:20.280
<v Speaker 1>doing it on purpose. They're thinking of it as like

0:19:20.440 --> 0:19:23.000
<v Speaker 1>giant toys. He also had a helicopter. I mean, he

0:19:23.040 --> 0:19:29.000
<v Speaker 1>had lots of stuff. On April thirty, two thousand twelve, uh,

0:19:29.920 --> 0:19:34.480
<v Speaker 1>a New Zealand judge found that some of the assets

0:19:34.520 --> 0:19:38.919
<v Speaker 1>in that raid were improperly seized and that paperwork was

0:19:38.960 --> 0:19:42.280
<v Speaker 1>not correctly filed, and as a result, they returned about

0:19:42.280 --> 0:19:46.800
<v Speaker 1>seven fifty thousand dollars worth of assets to um to

0:19:47.000 --> 0:19:49.840
<v Speaker 1>dot com, who, by the way, was having some problems

0:19:50.200 --> 0:19:54.480
<v Speaker 1>getting bail for a while, not not having not coming

0:19:54.560 --> 0:19:57.120
<v Speaker 1>up with the money, but just getting the the option

0:19:57.160 --> 0:20:01.320
<v Speaker 1>of being able to post bail. Judge initially denied him that,

0:20:02.280 --> 0:20:05.120
<v Speaker 1>saying that because he had a helicopter and because he

0:20:05.200 --> 0:20:09.320
<v Speaker 1>was a man of pretty uh substantial means that he

0:20:09.560 --> 0:20:13.320
<v Speaker 1>was a flight risk, and also citing his past as well,

0:20:13.880 --> 0:20:16.399
<v Speaker 1>uh where he had a little bit of a history

0:20:16.440 --> 0:20:21.440
<v Speaker 1>of hopping around a bit, uh, apparently to dodge authorities

0:20:21.440 --> 0:20:27.640
<v Speaker 1>and investigations. Uh. But then another judge found later they said, well, yeah,

0:20:27.680 --> 0:20:30.120
<v Speaker 1>but we seized all his assets. He's not going anywhere,

0:20:30.119 --> 0:20:33.280
<v Speaker 1>so we're going to grant him the option to post bail. Uh.

0:20:33.400 --> 0:20:36.840
<v Speaker 1>So that that did change well April three, when he

0:20:36.880 --> 0:20:38.840
<v Speaker 1>got about seven or fifty thou dollars worth of the

0:20:38.840 --> 0:20:41.320
<v Speaker 1>assets returned, including several of the cars. So it's not

0:20:41.359 --> 0:20:45.040
<v Speaker 1>like it was just a big suitcase full of cash. Uh.

0:20:45.680 --> 0:20:49.480
<v Speaker 1>June two thousand twelve, a New Zealand judge ruled that

0:20:49.520 --> 0:20:53.680
<v Speaker 1>the search warrants were dot COM's property were not valid

0:20:53.800 --> 0:20:57.640
<v Speaker 1>because they were too general. Yeah. Yeah. And in addition

0:20:57.680 --> 0:21:01.920
<v Speaker 1>to that, there has been a question over whether um

0:21:02.040 --> 0:21:05.400
<v Speaker 1>or not the use of force that not not that

0:21:05.640 --> 0:21:08.920
<v Speaker 1>you know, they shot their way in, but they came

0:21:09.000 --> 0:21:14.480
<v Speaker 1>in with weapons and things that we're not supposedly allowed

0:21:14.520 --> 0:21:19.240
<v Speaker 1>against um citizens of New Zealand. So there is some

0:21:19.400 --> 0:21:23.800
<v Speaker 1>question as to that that not only were the warrants

0:21:24.280 --> 0:21:27.960
<v Speaker 1>not specific enough, but whether or not that the use

0:21:28.080 --> 0:21:32.199
<v Speaker 1>of the techniques that they used during the raid on

0:21:32.359 --> 0:21:35.480
<v Speaker 1>his house, whether that was appropriate and and they kicked

0:21:35.520 --> 0:21:38.359
<v Speaker 1>the door down basically yeah, well, and dot Com for

0:21:38.440 --> 0:21:42.080
<v Speaker 1>his part, retreated to a safe room inside his house

0:21:42.200 --> 0:21:45.760
<v Speaker 1>and apparently had a couple of firearms in there with him,

0:21:45.800 --> 0:21:50.159
<v Speaker 1>which made it made it look not good. He didn't

0:21:50.520 --> 0:21:54.480
<v Speaker 1>he apparently was not holding the weapons, but he would

0:21:54.560 --> 0:21:58.399
<v Speaker 1>have had access to them. And his response was that

0:21:58.480 --> 0:22:00.840
<v Speaker 1>he thought that you know, he know what to think

0:22:00.880 --> 0:22:03.880
<v Speaker 1>because all these people were trying to break into his home,

0:22:04.000 --> 0:22:07.000
<v Speaker 1>so he retreated to the safe room in his house. Uh.

0:22:07.080 --> 0:22:11.399
<v Speaker 1>The um the officers say that he was trying trying

0:22:11.440 --> 0:22:17.159
<v Speaker 1>to escape and or delete incriminating evidence. They claimed that

0:22:17.200 --> 0:22:20.199
<v Speaker 1>he had a basically a panic button that would have

0:22:20.240 --> 0:22:24.920
<v Speaker 1>erased all of mega uploads files and he hold out

0:22:25.200 --> 0:22:31.480
<v Speaker 1>will he hold off candy like button? Good times well.

0:22:31.480 --> 0:22:35.040
<v Speaker 1>In July tenth, two thousand twelve, the extradition hearings were

0:22:35.119 --> 0:22:40.440
<v Speaker 1>deferred until March two thousand thirteen, and New Zealand judge

0:22:40.440 --> 0:22:45.159
<v Speaker 1>said the United States must prove that he was aware

0:22:45.200 --> 0:22:49.320
<v Speaker 1>of and supporting internet piracy to support an extradition claim.

0:22:49.440 --> 0:22:53.800
<v Speaker 1>And then on September two twelve, the Prime Minister of

0:22:53.880 --> 0:22:57.200
<v Speaker 1>New Zealand called for an investigation to determine if government

0:22:57.280 --> 0:23:01.639
<v Speaker 1>officials had been spying on dot Com and his associates illegally.

0:23:02.359 --> 0:23:06.600
<v Speaker 1>So it's a very thorny uh issue as far as

0:23:06.640 --> 0:23:09.680
<v Speaker 1>the laws concerned. In fact, it gets even more complicated.

0:23:09.680 --> 0:23:15.359
<v Speaker 1>There are some who say, uh, some being dot COM's lawyer, really,

0:23:15.720 --> 0:23:19.440
<v Speaker 1>who say that the United States case against dot Com

0:23:19.560 --> 0:23:25.919
<v Speaker 1>is attempting to use civil complaints as a criminal charge,

0:23:26.119 --> 0:23:28.960
<v Speaker 1>which that that's not how that works. Civil courts and

0:23:28.960 --> 0:23:31.119
<v Speaker 1>criminal courts in the United States. That's those are two

0:23:31.160 --> 0:23:34.680
<v Speaker 1>different things. But that at least some of the case

0:23:34.800 --> 0:23:38.919
<v Speaker 1>against dot Com is uh is based in would be

0:23:38.920 --> 0:23:41.159
<v Speaker 1>based in a civil court, not a criminal court, and

0:23:41.240 --> 0:23:45.120
<v Speaker 1>yet they're using it as a criminal charge against him,

0:23:45.280 --> 0:23:49.040
<v Speaker 1>and other parts of the criminal charges would depend wholly

0:23:49.160 --> 0:23:52.000
<v Speaker 1>upon how that civil case played out, so they can't

0:23:52.680 --> 0:23:55.679
<v Speaker 1>If that's in fact true, they would not be able

0:23:55.760 --> 0:24:00.800
<v Speaker 1>to uh to to lay these charges against dot Com

0:24:00.880 --> 0:24:04.440
<v Speaker 1>until after the civil case was tried and there was

0:24:04.480 --> 0:24:08.320
<v Speaker 1>an outcome. UM. I think it's more complex from there.

0:24:08.720 --> 0:24:12.720
<v Speaker 1>So it's it's uh. It's as a messy, messy situation,

0:24:12.840 --> 0:24:15.160
<v Speaker 1>and as of the recording of this podcast, we can't

0:24:15.200 --> 0:24:18.159
<v Speaker 1>be sure what the outcome is going to be. Uh,

0:24:18.200 --> 0:24:20.920
<v Speaker 1>there have been there's been more fallout from this beyond

0:24:21.080 --> 0:24:27.120
<v Speaker 1>just the press. UM. Anonymous decided to get involved UM,

0:24:27.160 --> 0:24:30.720
<v Speaker 1>which is kind of hard to say because Anonymous is

0:24:30.720 --> 0:24:34.360
<v Speaker 1>such a vaguely defined group that it could be two

0:24:34.359 --> 0:24:37.240
<v Speaker 1>people and Anonymous who want to do something and then

0:24:37.240 --> 0:24:41.680
<v Speaker 1>the entire group gets uh. UM pointed at as saying

0:24:41.680 --> 0:24:44.439
<v Speaker 1>they're the ones responsible. Now, it could very well be

0:24:44.480 --> 0:24:48.520
<v Speaker 1>that of Anonymous all was behind us, or even percent

0:24:48.600 --> 0:24:51.080
<v Speaker 1>was behind it, But by the very nature of the group,

0:24:51.359 --> 0:24:55.720
<v Speaker 1>which is a decentralized activist group, you can't be sure,

0:24:56.560 --> 0:25:00.600
<v Speaker 1>which is part of what protects them. Well. Anyway, some

0:25:00.680 --> 0:25:05.080
<v Speaker 1>people apparently belonging to Anonymous, at least according to those

0:25:05.119 --> 0:25:07.639
<v Speaker 1>who are looking into this, and it could be that

0:25:07.680 --> 0:25:11.240
<v Speaker 1>that's all not true as well, UM started to launch

0:25:11.320 --> 0:25:16.000
<v Speaker 1>attacks against websites UM, particularly websites belonging to the Department

0:25:16.000 --> 0:25:19.160
<v Speaker 1>of Justice, the United States Department of Justice, in retaliation

0:25:19.400 --> 0:25:22.639
<v Speaker 1>for the raids that were and and the shutdown of

0:25:22.720 --> 0:25:26.720
<v Speaker 1>mega Upload. So you had distributed denial of service attacks

0:25:26.760 --> 0:25:30.760
<v Speaker 1>going out across the Internet, fired from the canon of

0:25:30.240 --> 0:25:33.159
<v Speaker 1>h of activists who may or may not belong to

0:25:33.200 --> 0:25:38.640
<v Speaker 1>anonymous um as another another salvo in this battle between

0:25:39.440 --> 0:25:44.119
<v Speaker 1>well multiple parties at this point. Yeah, yeah, and UM

0:25:44.680 --> 0:25:48.040
<v Speaker 1>to complicate matters. Now that you know Kim dot com

0:25:48.119 --> 0:25:50.760
<v Speaker 1>is out on his own, he's also and again this

0:25:50.920 --> 0:25:53.960
<v Speaker 1>is fairly recent um as at the time we're recording this,

0:25:54.160 --> 0:25:59.360
<v Speaker 1>that he's created a new service, just Mega. In fact,

0:25:59.440 --> 0:26:02.640
<v Speaker 1>it's m dot g A, which is using the gabon

0:26:03.800 --> 0:26:07.320
<v Speaker 1>H Is that how you pronounce it? Um anyway, Yes,

0:26:07.400 --> 0:26:09.920
<v Speaker 1>they're using their country code. So it's my dot g

0:26:10.119 --> 0:26:14.040
<v Speaker 1>A and that's on launching one on one year to

0:26:14.119 --> 0:26:18.680
<v Speaker 1>the day of his arrest January. The new service is

0:26:18.680 --> 0:26:22.240
<v Speaker 1>supposed to go online. And uh, from what I've read

0:26:22.280 --> 0:26:26.159
<v Speaker 1>about the new service, it's supposed to circumvent the quote

0:26:26.200 --> 0:26:29.520
<v Speaker 1>unquote problems. You'll see why I said that, Uh put

0:26:29.520 --> 0:26:34.159
<v Speaker 1>in the fake scare quotes um for uh for this

0:26:34.240 --> 0:26:38.400
<v Speaker 1>because they won't be able to see what's inside these lockers. Yeah.

0:26:38.440 --> 0:26:42.439
<v Speaker 1>Everything gets encrypted when you upload a file. Uh, it

0:26:42.480 --> 0:26:46.040
<v Speaker 1>gets encrypted within your browser. Yeah, and it so, in

0:26:46.080 --> 0:26:49.960
<v Speaker 1>other words, the owners of Mega would never be able

0:26:50.040 --> 0:26:53.520
<v Speaker 1>to see what content was stored on their service at all.

0:26:53.600 --> 0:26:58.240
<v Speaker 1>It would all just be meaningless encrypted, uh information, Right,

0:26:58.320 --> 0:27:01.760
<v Speaker 1>So they So even if you were an intellectual property

0:27:01.840 --> 0:27:05.360
<v Speaker 1>rights holder and you went to Mega and said, um,

0:27:05.400 --> 0:27:10.200
<v Speaker 1>this file is violating our intellectual property, they'd say, well,

0:27:10.240 --> 0:27:13.000
<v Speaker 1>we can't tell that because for us, it's just meaningless

0:27:13.160 --> 0:27:17.000
<v Speaker 1>jumble of symbols. It doesn't there's no file here as

0:27:17.000 --> 0:27:19.240
<v Speaker 1>far as we can see. Yeah. Also, there will be

0:27:19.280 --> 0:27:23.280
<v Speaker 1>no servers in the United States jurisdiction according to what

0:27:23.320 --> 0:27:25.400
<v Speaker 1>I've read, So that would but that would protect them

0:27:25.400 --> 0:27:28.080
<v Speaker 1>on those counts, or at least would come closer to

0:27:28.119 --> 0:27:30.639
<v Speaker 1>protecting them, right. Yeah. The way you would access one

0:27:30.680 --> 0:27:33.159
<v Speaker 1>of these files, of course, that you would get if

0:27:33.200 --> 0:27:35.280
<v Speaker 1>you were to upload a file like let's say I

0:27:35.359 --> 0:27:38.920
<v Speaker 1>upload a file of Howard the Duck and it's encrypted

0:27:38.960 --> 0:27:42.320
<v Speaker 1>into Mega, I would want. Part of that transaction would

0:27:42.320 --> 0:27:44.160
<v Speaker 1>be I would get a key that I could share

0:27:44.160 --> 0:27:48.119
<v Speaker 1>with other people that would allow them to decrypt whatever

0:27:48.160 --> 0:27:50.400
<v Speaker 1>the file was. Yes, so I could send the key

0:27:50.440 --> 0:27:53.200
<v Speaker 1>to Chris and say, saved you the trouble, big guy,

0:27:53.840 --> 0:27:56.280
<v Speaker 1>here's the movie, and he could go and download it

0:27:56.320 --> 0:27:58.359
<v Speaker 1>because he has the key. Anyone who does not have

0:27:58.440 --> 0:28:00.280
<v Speaker 1>the key would not be able to see what the

0:28:00.320 --> 0:28:03.159
<v Speaker 1>heck that file was. Yes, and that would prevent the

0:28:03.920 --> 0:28:07.960
<v Speaker 1>problem of needing D duplication. UM. You know, the same

0:28:08.000 --> 0:28:10.359
<v Speaker 1>file taking up filespace now it basically know that the

0:28:10.400 --> 0:28:13.920
<v Speaker 1>same UH information was up there, but it wouldn't say

0:28:14.000 --> 0:28:18.439
<v Speaker 1>what that information was specifically, so so they would have

0:28:18.440 --> 0:28:22.680
<v Speaker 1>a better chance of pleading UH safe harbor in that case.

0:28:22.840 --> 0:28:28.760
<v Speaker 1>It's mostly to obviously protect the owner and caretakers of

0:28:28.840 --> 0:28:31.680
<v Speaker 1>mega But all this being said, you know, we've talked

0:28:31.680 --> 0:28:33.199
<v Speaker 1>a lot about the piracy, and we've talked a lot

0:28:33.240 --> 0:28:37.040
<v Speaker 1>about the the allegations against mega upload UM and I

0:28:37.119 --> 0:28:39.520
<v Speaker 1>probably should have said this much earlier in the podcast,

0:28:39.600 --> 0:28:44.520
<v Speaker 1>but there are very legitimate ways to use these services

0:28:44.560 --> 0:28:48.280
<v Speaker 1>that have nothing to do with violating intellectual property, property

0:28:48.400 --> 0:28:52.440
<v Speaker 1>or piracy or anything like that. Like if I have

0:28:53.080 --> 0:28:55.800
<v Speaker 1>content that belongs to me and I want to be

0:28:55.880 --> 0:28:58.520
<v Speaker 1>able to distribute it to all wide network and I

0:28:58.560 --> 0:29:02.680
<v Speaker 1>cannot host it myself, something like one of these sites

0:29:02.800 --> 0:29:05.640
<v Speaker 1>could be very useful. You know, I may not have

0:29:05.800 --> 0:29:09.920
<v Speaker 1>any other distribution platform that I can use to get

0:29:09.960 --> 0:29:13.720
<v Speaker 1>my content out there. So there are plenty of use

0:29:13.760 --> 0:29:18.280
<v Speaker 1>cases where there's nothing wrong with using a site like

0:29:18.400 --> 0:29:23.160
<v Speaker 1>mega upload to either distribute or to get access to material.

0:29:23.600 --> 0:29:27.080
<v Speaker 1>It's only in the case where that is unauthorized use

0:29:27.200 --> 0:29:31.920
<v Speaker 1>of intellectual property. That is the problem. Now that raises

0:29:31.960 --> 0:29:36.600
<v Speaker 1>a question of well, what percentage of activity on mega

0:29:36.680 --> 0:29:43.840
<v Speaker 1>upload uh revolved around intellectual property theft? And whether and

0:29:43.960 --> 0:29:47.800
<v Speaker 1>if it was a lot, were the founders aware of

0:29:47.840 --> 0:29:51.880
<v Speaker 1>it or even complicit in it. Those are the points

0:29:51.920 --> 0:29:55.320
<v Speaker 1>that need to be hashed out in court. I've also

0:29:55.400 --> 0:29:58.520
<v Speaker 1>seen at least one judge in the United States say

0:29:58.920 --> 0:30:03.800
<v Speaker 1>that he doubts this will ever go to court in

0:30:03.920 --> 0:30:09.280
<v Speaker 1>the US. He thinks that there are enough problematic factors

0:30:09.320 --> 0:30:13.320
<v Speaker 1>involved in the whole raid and seizing of the property

0:30:13.360 --> 0:30:16.280
<v Speaker 1>that will prevent it from ever having its stay in

0:30:16.320 --> 0:30:20.560
<v Speaker 1>court in in the US. So we'll see, it's very possible.

0:30:20.880 --> 0:30:25.080
<v Speaker 1>It does look like it was not the um not

0:30:25.200 --> 0:30:29.800
<v Speaker 1>the smoothest raid I've ever seen, at least from a

0:30:29.800 --> 0:30:34.360
<v Speaker 1>paperwork standpoint. So yeah, we'll have to wait and see

0:30:34.400 --> 0:30:36.240
<v Speaker 1>if that if that's how it plays out. But it's

0:30:36.240 --> 0:30:40.240
<v Speaker 1>an interesting case, and it is somewhat worrisome because even

0:30:40.280 --> 0:30:44.480
<v Speaker 1>if you were to say that the founder and owners

0:30:44.480 --> 0:30:49.920
<v Speaker 1>of mega upload, we're all actively encouraging piracy, that reflects

0:30:49.960 --> 0:30:53.880
<v Speaker 1>poorly on other file sharing services that may be very

0:30:54.000 --> 0:30:58.480
<v Speaker 1>much dedicated to fighting piracy on their own service, but

0:30:58.720 --> 0:31:01.760
<v Speaker 1>now they are brought into question because they just happen

0:31:01.840 --> 0:31:04.240
<v Speaker 1>to have the same distribution model more or less as

0:31:04.280 --> 0:31:09.440
<v Speaker 1>Mega mega upload, and UH, that hurts everybody. So it's

0:31:09.440 --> 0:31:12.280
<v Speaker 1>not you know, even if you think, oh, well, I

0:31:12.320 --> 0:31:15.560
<v Speaker 1>never pirate stuff and I would never upload those kind

0:31:15.600 --> 0:31:18.240
<v Speaker 1>of files to a service, it can still affect you

0:31:18.560 --> 0:31:21.200
<v Speaker 1>it because it might mean that some other service that

0:31:21.240 --> 0:31:23.920
<v Speaker 1>you use and you trust ends up getting caught in

0:31:24.000 --> 0:31:28.600
<v Speaker 1>this blast and uh ends up not being able to

0:31:28.640 --> 0:31:32.600
<v Speaker 1>continue its services. It also raises another question. I know

0:31:32.640 --> 0:31:34.560
<v Speaker 1>that there are a lot of people who had stuff

0:31:34.640 --> 0:31:37.560
<v Speaker 1>up on mega upload and now they don't have access

0:31:37.560 --> 0:31:40.560
<v Speaker 1>to it. So there are people who saying, wait a minute,

0:31:40.920 --> 0:31:43.440
<v Speaker 1>I owned the content that I put up on mega

0:31:43.520 --> 0:31:46.200
<v Speaker 1>upload that belongs to me, and now I can't get

0:31:46.240 --> 0:31:49.960
<v Speaker 1>to it. Yeah. And and it's funny because the article

0:31:50.000 --> 0:31:54.400
<v Speaker 1>in Wired ends with um, the judge wanting to release

0:31:54.520 --> 0:31:57.400
<v Speaker 1>information about the case to the media but wants all

0:31:57.400 --> 0:31:59.920
<v Speaker 1>the media outlets to have that access and exactly the

0:32:00.120 --> 0:32:03.760
<v Speaker 1>same time and saying, wow, if we just had a

0:32:03.760 --> 0:32:06.880
<v Speaker 1>way to do that, and that would be something obviously

0:32:06.960 --> 0:32:09.880
<v Speaker 1>that that's sort of an allusion to, yes, you could

0:32:09.960 --> 0:32:13.000
<v Speaker 1>do that with something like mega upload and um, yeah,

0:32:13.080 --> 0:32:19.040
<v Speaker 1>I mean the it seems like the the apparently the

0:32:19.080 --> 0:32:22.240
<v Speaker 1>service had been used by a great many people to

0:32:22.800 --> 0:32:26.760
<v Speaker 1>distribute content that they owned, that it was perfectly legal

0:32:26.800 --> 0:32:31.000
<v Speaker 1>to use the way they were using it. Um So yeah,

0:32:31.320 --> 0:32:34.840
<v Speaker 1>I think, Um, it's interesting to see. I think the

0:32:34.960 --> 0:32:37.880
<v Speaker 1>article sort of makes it sound like or or at

0:32:37.920 --> 0:32:41.760
<v Speaker 1>least gives me the impression that this situation is sort

0:32:41.800 --> 0:32:45.760
<v Speaker 1>of something of their own making, because they made themselves

0:32:45.760 --> 0:32:49.040
<v Speaker 1>appear to be up to something because it was fun

0:32:49.120 --> 0:32:51.920
<v Speaker 1>to play that way that there may not there may

0:32:51.920 --> 0:32:56.560
<v Speaker 1>not have been any attempt at anything impro improper, but

0:32:56.920 --> 0:32:59.640
<v Speaker 1>people were using it improperly, and there wasn't, you know,

0:32:59.720 --> 0:33:03.640
<v Speaker 1>as much to discourage improper use as there could have

0:33:03.760 --> 0:33:08.400
<v Speaker 1>been perhaps, Um so it's yeah, I think I think

0:33:08.440 --> 0:33:12.760
<v Speaker 1>they they contributed to their own problems. Um. And it's

0:33:12.840 --> 0:33:15.600
<v Speaker 1>cases like this that give rise to propose pieces of

0:33:15.680 --> 0:33:21.600
<v Speaker 1>legislation like the Stop Online Piracy Act that are both

0:33:21.840 --> 0:33:24.120
<v Speaker 1>related to this. Yeah, so you've got, I mean, you've

0:33:24.120 --> 0:33:27.360
<v Speaker 1>got these are other things that can affect all of

0:33:27.480 --> 0:33:31.800
<v Speaker 1>us in a negative way. Uh, And we need to

0:33:31.880 --> 0:33:36.520
<v Speaker 1>really think about it before, you know, allowing proper intellectual

0:33:36.600 --> 0:33:40.520
<v Speaker 1>property owners to just run rampant over the legal system.

0:33:40.560 --> 0:33:44.080
<v Speaker 1>Now that being said, I still think that they deserve

0:33:44.200 --> 0:33:47.000
<v Speaker 1>some sort of support system to protect their intellectual property.

0:33:47.360 --> 0:33:48.800
<v Speaker 1>You know, I don't. I don't think it should be

0:33:49.480 --> 0:33:52.920
<v Speaker 1>uh open season and that you can grab anything you want,

0:33:52.960 --> 0:33:57.719
<v Speaker 1>anytime you want, with no care about, you know, purchasing it,

0:33:57.800 --> 0:34:00.680
<v Speaker 1>Because if we were to all live that way, a

0:34:00.680 --> 0:34:03.680
<v Speaker 1>a lot of people would stop making content because there

0:34:03.680 --> 0:34:06.080
<v Speaker 1>would be no reason to do it, you know. I mean,

0:34:06.320 --> 0:34:09.000
<v Speaker 1>some people would make content because they love to create

0:34:09.040 --> 0:34:11.319
<v Speaker 1>things and they love to share it. But a lot

0:34:11.320 --> 0:34:13.720
<v Speaker 1>of the content that we love, the stuff that everyone

0:34:13.719 --> 0:34:16.000
<v Speaker 1>wants to get their hands on, would not exist because

0:34:16.040 --> 0:34:19.000
<v Speaker 1>no one would make it because there's no money in it. So,

0:34:19.960 --> 0:34:25.160
<v Speaker 1>you know, there's there's definitely a complex issue here, but uh,

0:34:25.160 --> 0:34:27.480
<v Speaker 1>it's it's one of those things. Why the reason why

0:34:27.520 --> 0:34:30.000
<v Speaker 1>I'm paying attention to the mega upload case is because

0:34:30.120 --> 0:34:32.400
<v Speaker 1>I know this is the sort of thing that inspires

0:34:33.560 --> 0:34:39.600
<v Speaker 1>various lobbies to UH petition UH legislators to create laws

0:34:39.640 --> 0:34:45.200
<v Speaker 1>that often go well beyond what the original intention of

0:34:45.200 --> 0:34:47.000
<v Speaker 1>that law was meant to do. You know, it might

0:34:47.120 --> 0:34:49.840
<v Speaker 1>the intention might be we need to protect these people

0:34:50.040 --> 0:34:54.360
<v Speaker 1>or these companies because their property is getting stolen, but

0:34:54.520 --> 0:34:57.680
<v Speaker 1>the actual implications go so far beyond it as to

0:34:58.360 --> 0:35:02.520
<v Speaker 1>well potentially cripple the internet it yea, So it's uh,

0:35:02.560 --> 0:35:05.160
<v Speaker 1>you know, it's an interesting story. Um. We'll definitely keep

0:35:05.200 --> 0:35:08.640
<v Speaker 1>our eyes on it and see how it develops and maybe,

0:35:08.760 --> 0:35:11.520
<v Speaker 1>uh maybe Mega will become an even bigger story than

0:35:11.560 --> 0:35:15.440
<v Speaker 1>Mega upload ever was. Yeah, that's true. It's possible, especially

0:35:15.480 --> 0:35:18.759
<v Speaker 1>with the encryption. So he's also gonna he's planning on

0:35:18.800 --> 0:35:22.359
<v Speaker 1>a music streaming service as well. Yeah, I mean they

0:35:22.400 --> 0:35:25.040
<v Speaker 1>had a music storage service already, so that doesn't really

0:35:25.080 --> 0:35:27.440
<v Speaker 1>surprise me. And they even had a video streaming service,

0:35:27.480 --> 0:35:30.439
<v Speaker 1>so it's kind of a considering the popularity of music

0:35:30.480 --> 0:35:33.319
<v Speaker 1>streaming over the last two years, that doesn't really surprise me.

0:35:33.800 --> 0:35:36.040
<v Speaker 1>So we'll see how that all comes out and whether

0:35:36.160 --> 0:35:40.839
<v Speaker 1>or not dot Com gets out of this one um,

0:35:40.960 --> 0:35:43.479
<v Speaker 1>or you know, maybe he ends up courting even more

0:35:44.160 --> 0:35:47.319
<v Speaker 1>trouble in the future. He seems like the kind of

0:35:47.320 --> 0:35:49.640
<v Speaker 1>personality who sort of thrives on this sort of thing

0:35:49.719 --> 0:35:51.640
<v Speaker 1>to a point. I mean, no one thrives in having

0:35:51.640 --> 0:35:54.759
<v Speaker 1>seventeen million dollars worth of stuff taken from them, no,

0:35:54.880 --> 0:35:58.800
<v Speaker 1>but he does like attention. It seems like he would

0:35:58.800 --> 0:36:04.839
<v Speaker 1>like attention for uh being a role model of sorts UM,

0:36:04.960 --> 0:36:07.399
<v Speaker 1>but uh, you know, I don't know that he wants

0:36:07.400 --> 0:36:10.759
<v Speaker 1>to be seen as a uh a rule breaker, maybe

0:36:10.760 --> 0:36:13.719
<v Speaker 1>a rule bender. But yeah, I would encourage people to

0:36:13.760 --> 0:36:17.319
<v Speaker 1>check out that article because, uh, it's interesting. It's really

0:36:17.880 --> 0:36:22.239
<v Speaker 1>it paints a very good picture I think of good

0:36:22.280 --> 0:36:25.600
<v Speaker 1>and bad that that that he's associated with, and whether

0:36:25.680 --> 0:36:27.680
<v Speaker 1>or not it kind of gives you an idea of

0:36:28.400 --> 0:36:31.640
<v Speaker 1>the charges, the depth of the charges, um that are

0:36:31.680 --> 0:36:34.279
<v Speaker 1>being leveled against him. Um. And we also if you're

0:36:34.280 --> 0:36:37.839
<v Speaker 1>interested in in having a better understanding of different file

0:36:37.920 --> 0:36:41.879
<v Speaker 1>sharing techniques and cloud storage, we have articles about those

0:36:41.920 --> 0:36:43.879
<v Speaker 1>on the site as well on on how stuff Works

0:36:43.920 --> 0:36:46.360
<v Speaker 1>dot com. So check those out, and if you have

0:36:46.400 --> 0:36:49.520
<v Speaker 1>any suggestions for future episodes, I recommend you write us.

0:36:49.840 --> 0:36:53.239
<v Speaker 1>Our email address is tech stuff at Discovery dot com

0:36:53.440 --> 0:36:55.480
<v Speaker 1>or let us know on Facebook or Twitter or handle

0:36:55.520 --> 0:36:58.200
<v Speaker 1>at both of those is tech Stuff, hs W and

0:36:58.239 --> 0:37:00.279
<v Speaker 1>Chris and I will talk to you again really soon.

0:37:01.760 --> 0:37:04.279
<v Speaker 1>For more on this and thousands of other topics, visit

0:37:04.320 --> 0:37:09.640
<v Speaker 1>how stuff Works dot com.