WEBVTT - Tech Glossary: From DLL to GPS

0:00:04.400 --> 0:00:07.800
<v Speaker 1>Welcome to tech Stuff, a production from I Heart Radio.

0:00:12.240 --> 0:00:15.240
<v Speaker 1>Hey there, and welcome to tech Stuff. I'm your host,

0:00:15.400 --> 0:00:18.239
<v Speaker 1>Jonathan Strickland. I'm an executive producer with I Heart Radio

0:00:18.280 --> 0:00:21.200
<v Speaker 1>and I love all things tech, and we are continuing

0:00:21.320 --> 0:00:24.919
<v Speaker 1>our episodes that give a sort of glossary overview of

0:00:25.040 --> 0:00:30.160
<v Speaker 1>some common acronyms and initialisms within tech and include a

0:00:30.200 --> 0:00:33.319
<v Speaker 1>little bit of backstory for each one. And because I'm

0:00:33.320 --> 0:00:36.360
<v Speaker 1>a chatty feller, in the first episode, we started off

0:00:36.400 --> 0:00:40.279
<v Speaker 1>with two f A or two factor authentication, and we

0:00:40.440 --> 0:00:44.239
<v Speaker 1>ended with d l C or downloadable content. So we're

0:00:44.280 --> 0:00:47.320
<v Speaker 1>gonna pick up right where we left off and continue

0:00:47.360 --> 0:00:51.680
<v Speaker 1>on down the alphabet. So next up is d l L.

0:00:52.320 --> 0:00:56.440
<v Speaker 1>This is Microsoft's approach to what is called a shared library,

0:00:56.960 --> 0:00:59.560
<v Speaker 1>and by that I mean that it's a file that

0:00:59.640 --> 0:01:03.840
<v Speaker 1>contain means non volatile resources that can be used by

0:01:04.000 --> 0:01:07.759
<v Speaker 1>different computer programs. Volatile in this case refers to whether

0:01:07.840 --> 0:01:10.840
<v Speaker 1>or not the information is changeable or or it gets

0:01:10.880 --> 0:01:14.119
<v Speaker 1>wiped out when the device is powered off. So these

0:01:14.160 --> 0:01:18.080
<v Speaker 1>libraries remain unchanged when the computer power is off, and

0:01:18.120 --> 0:01:20.320
<v Speaker 1>they are right back when the computer power is back on,

0:01:20.760 --> 0:01:24.520
<v Speaker 1>and that information persists even after the machine shuts down.

0:01:24.920 --> 0:01:28.760
<v Speaker 1>These libraries hold assets that other programs might need to

0:01:28.880 --> 0:01:32.400
<v Speaker 1>access in the process of, you know, the programs doing

0:01:32.480 --> 0:01:34.960
<v Speaker 1>whatever it is they're supposed to do. So, if you've

0:01:34.959 --> 0:01:38.600
<v Speaker 1>ever seen a file that has the d l L extension,

0:01:39.040 --> 0:01:42.440
<v Speaker 1>that's a dynamic link library and it means you're on

0:01:42.480 --> 0:01:45.920
<v Speaker 1>a PC that's running on Windows. Getting into more detail

0:01:46.040 --> 0:01:49.480
<v Speaker 1>would pretty much require a dedicated episode. So just think

0:01:49.600 --> 0:01:52.560
<v Speaker 1>of d l L files as being a resource cash

0:01:52.880 --> 0:01:56.280
<v Speaker 1>for programs running on a Windows computer. And if you've

0:01:56.280 --> 0:01:59.400
<v Speaker 1>ever had any sort of program give you an error

0:01:59.400 --> 0:02:02.800
<v Speaker 1>because it couldn't find a DLL file, that's what it's

0:02:02.800 --> 0:02:09.920
<v Speaker 1>looking for. Next is d n S or domain name system,

0:02:10.000 --> 0:02:12.840
<v Speaker 1>so you know how you can type in addresses in

0:02:12.840 --> 0:02:15.919
<v Speaker 1>a web browser to go to specific web pages, like

0:02:16.080 --> 0:02:19.640
<v Speaker 1>you know, YouTube dot com takes you to YouTube, and

0:02:19.760 --> 0:02:24.000
<v Speaker 1>Netflix dot com takes you to Netflix, and Facebook dot

0:02:24.040 --> 0:02:26.960
<v Speaker 1>com takes you to a wretched hive of scum and villainy.

0:02:28.160 --> 0:02:32.079
<v Speaker 1>Might be tiny bit of editorializing that made its way

0:02:32.080 --> 0:02:35.920
<v Speaker 1>in there, My apologies. Well, anyway, d n S is

0:02:35.960 --> 0:02:40.200
<v Speaker 1>the underlying system that makes all that possible. It's this

0:02:40.280 --> 0:02:43.720
<v Speaker 1>system that acts kind of like a massive address book

0:02:44.000 --> 0:02:47.440
<v Speaker 1>for all things Internet, not just the Web, but the

0:02:47.480 --> 0:02:51.320
<v Speaker 1>web stuff is probably the easiest to explain, typically because

0:02:51.360 --> 0:02:54.840
<v Speaker 1>it's how a lot of us interact with the Internet. Now,

0:02:55.080 --> 0:02:58.520
<v Speaker 1>every machine on the Internet has a numerical address in

0:02:58.560 --> 0:03:01.920
<v Speaker 1>the form of an I P address. But as we

0:03:02.040 --> 0:03:05.920
<v Speaker 1>established with binary language and machine code in the previous episode,

0:03:06.320 --> 0:03:10.239
<v Speaker 1>we humans do not handle tons of numbers super well,

0:03:11.040 --> 0:03:13.440
<v Speaker 1>so it would be really hard for us to remember

0:03:13.760 --> 0:03:16.760
<v Speaker 1>specific I P addresses if we had to rely purely

0:03:16.840 --> 0:03:21.000
<v Speaker 1>on putting in those numerical addresses. And by the way,

0:03:21.040 --> 0:03:23.520
<v Speaker 1>that's just for I p v four addresses, which is

0:03:23.720 --> 0:03:26.480
<v Speaker 1>outdated these days. You would really need to learn I

0:03:26.639 --> 0:03:30.960
<v Speaker 1>p v six addresses. Those are even longer strings of characters,

0:03:31.000 --> 0:03:34.400
<v Speaker 1>and they include not only numbers, but some letters as well.

0:03:35.000 --> 0:03:38.520
<v Speaker 1>More on that in a later entry. So the DNS

0:03:39.000 --> 0:03:43.440
<v Speaker 1>establishes which domain names relate to which IP addresses, and

0:03:43.440 --> 0:03:46.080
<v Speaker 1>it makes it way easier to navigate the Internet for

0:03:46.160 --> 0:03:49.680
<v Speaker 1>those of us incapable of committing strings of seemingly random

0:03:49.800 --> 0:03:52.960
<v Speaker 1>letters and numbers to memory. There's a lot more to

0:03:53.000 --> 0:03:56.240
<v Speaker 1>be said about d n s, including the various attacks

0:03:56.280 --> 0:03:59.840
<v Speaker 1>that hackers sometimes launch against the d n s, but

0:04:00.040 --> 0:04:04.360
<v Speaker 1>we can save that for other episodes. Next is DOSS

0:04:04.480 --> 0:04:09.000
<v Speaker 1>or d O S. That stands for disc Operating System,

0:04:09.040 --> 0:04:11.640
<v Speaker 1>and more often than not it refers to an operating

0:04:11.680 --> 0:04:15.760
<v Speaker 1>system that was derived from IBM S personal computers. There

0:04:15.800 --> 0:04:19.400
<v Speaker 1>have been many different flavors of DOSS, which share a

0:04:19.440 --> 0:04:23.800
<v Speaker 1>few elements in common. They are text based operating systems,

0:04:24.040 --> 0:04:26.599
<v Speaker 1>so in other words, you navigate these by typing out

0:04:26.680 --> 0:04:29.480
<v Speaker 1>various commands in a in a prompt, and you do

0:04:29.560 --> 0:04:33.200
<v Speaker 1>that to move through directories and folders. There's no Windows,

0:04:33.240 --> 0:04:36.440
<v Speaker 1>there's no know icons to click on. You're typing these

0:04:36.480 --> 0:04:39.719
<v Speaker 1>commands out, and you also type in commands to execute

0:04:39.760 --> 0:04:42.960
<v Speaker 1>specific files, so to run a program that's stored on

0:04:43.000 --> 0:04:46.800
<v Speaker 1>a computer. Before Windows, this was how people would interact

0:04:46.839 --> 0:04:50.080
<v Speaker 1>with computers that had hard drive storage. Prior to that,

0:04:50.120 --> 0:04:53.520
<v Speaker 1>your average user would typically just insert a disk into

0:04:53.600 --> 0:04:56.800
<v Speaker 1>a disk drive and the computer's boot process would launch

0:04:56.920 --> 0:05:01.000
<v Speaker 1>directly into that disks associated program. Although you would actually

0:05:01.080 --> 0:05:04.000
<v Speaker 1>navigate to a disk drive and executed program that way.

0:05:04.040 --> 0:05:08.080
<v Speaker 1>That was also possible for PCs. Windows would end up

0:05:08.120 --> 0:05:12.440
<v Speaker 1>replacing DOSS, and on Apple computers, the Mac operating System

0:05:12.560 --> 0:05:18.800
<v Speaker 1>replaced Apple's version of DOSSDAS was a pretty lightweight operating system,

0:05:18.920 --> 0:05:21.360
<v Speaker 1>and that meant you could reserve more of your computer's

0:05:21.520 --> 0:05:25.120
<v Speaker 1>resources to store and run the programs that you wanted

0:05:25.160 --> 0:05:29.560
<v Speaker 1>to execute, and some old fogies like yours truly got

0:05:29.600 --> 0:05:33.520
<v Speaker 1>really salty wind. Windows came along because it demanded way

0:05:33.520 --> 0:05:37.400
<v Speaker 1>more computational resources than Doss did. So while Windows was

0:05:37.520 --> 0:05:42.480
<v Speaker 1>inarguably easier to navigate and leagues more intuitive than Doss

0:05:42.560 --> 0:05:47.200
<v Speaker 1>ever was, it also encroached on precious computational resources, and

0:05:47.360 --> 0:05:50.680
<v Speaker 1>some folks like me got grouchy about it and held

0:05:50.720 --> 0:05:52.560
<v Speaker 1>out for a long time until pretty much all of

0:05:52.600 --> 0:05:55.520
<v Speaker 1>the software that was out there in the world required

0:05:56.080 --> 0:06:00.160
<v Speaker 1>a Windows operating system as the foundation. Not that I'm

0:06:00.200 --> 0:06:06.440
<v Speaker 1>still bitter nearly forty years later. Next is d p I.

0:06:07.080 --> 0:06:10.360
<v Speaker 1>This stands for dots per inch and it's typically used

0:06:10.400 --> 0:06:14.279
<v Speaker 1>to refer to the resolution of printed or scanned material.

0:06:14.839 --> 0:06:19.520
<v Speaker 1>So with displays and screens and monitors, we talk about

0:06:19.640 --> 0:06:22.760
<v Speaker 1>resolution in terms of the number of pixels that are

0:06:22.920 --> 0:06:26.919
<v Speaker 1>on display within a full screen, right, So greater pixel

0:06:27.040 --> 0:06:30.920
<v Speaker 1>density means that you have higher resolution. So another way

0:06:30.920 --> 0:06:33.280
<v Speaker 1>to think of it is to imagine that you are

0:06:33.920 --> 0:06:37.800
<v Speaker 1>tasked with making a yellow smiley face image and you're

0:06:37.839 --> 0:06:40.720
<v Speaker 1>given a frame that frame is one foot square, and

0:06:40.760 --> 0:06:43.360
<v Speaker 1>you're gonna make this image using wooden blocks that are

0:06:43.400 --> 0:06:46.120
<v Speaker 1>painted a single color. You're giving a bunch of yellow

0:06:46.200 --> 0:06:48.839
<v Speaker 1>blocks and a bunch of black blocks. Each of these

0:06:48.839 --> 0:06:53.400
<v Speaker 1>blocks is one inch square, so you've got a foot

0:06:53.440 --> 0:06:56.440
<v Speaker 1>by a foot, so you can fit twelve squares across

0:06:56.440 --> 0:06:59.880
<v Speaker 1>and twelve squares down and you make your little smiley

0:07:00.000 --> 0:07:04.119
<v Speaker 1>face image. It would be a very blocky smiley face.

0:07:04.279 --> 0:07:06.800
<v Speaker 1>But let's say you keep that same frame, so it's

0:07:06.800 --> 0:07:09.720
<v Speaker 1>one ft by one ft, But now you're given blocks

0:07:09.760 --> 0:07:13.640
<v Speaker 1>that are half an inch square, so they're half the size,

0:07:13.760 --> 0:07:16.400
<v Speaker 1>half the width, and half the length, and now you

0:07:16.440 --> 0:07:19.680
<v Speaker 1>can fit way more squares in. While it's gonna look

0:07:19.680 --> 0:07:22.160
<v Speaker 1>a little better. Maybe you go down to a quarter

0:07:22.280 --> 0:07:26.320
<v Speaker 1>of an inch for a square, and as those blocks

0:07:26.320 --> 0:07:28.240
<v Speaker 1>get smaller, you can fit more of them into the

0:07:28.280 --> 0:07:31.960
<v Speaker 1>same physical space, and you create smoother lines as a result,

0:07:32.240 --> 0:07:35.240
<v Speaker 1>giving your image a higher resolution. Well, the same is

0:07:35.280 --> 0:07:39.360
<v Speaker 1>true for displays and well for printers. So dots per

0:07:39.440 --> 0:07:43.120
<v Speaker 1>inch is the resolution of the number of dots of

0:07:43.200 --> 0:07:47.520
<v Speaker 1>half tone that uh can appear per inch of paper.

0:07:48.000 --> 0:07:51.280
<v Speaker 1>Generally speaking, a higher dp I means that you get

0:07:51.320 --> 0:07:55.200
<v Speaker 1>a more clear, sharp and detailed print job. But just

0:07:55.280 --> 0:07:59.040
<v Speaker 1>like photo resolution, there is a point of diminishing returns

0:07:59.120 --> 0:08:03.400
<v Speaker 1>in which boosting that DPI number even higher might not

0:08:03.640 --> 0:08:08.640
<v Speaker 1>lead to a noticeable improvement. It might on paper, to

0:08:08.760 --> 0:08:11.800
<v Speaker 1>use a pun be an improvement, but you might not

0:08:11.800 --> 0:08:14.440
<v Speaker 1>be able to actually see it. It's not unusual to

0:08:14.480 --> 0:08:17.760
<v Speaker 1>have printers with a high dpi in excess of around

0:08:17.760 --> 0:08:23.040
<v Speaker 1>two thousand. Next is dr M. This is the dreaded

0:08:23.200 --> 0:08:27.800
<v Speaker 1>digital rights management. This refers to copyright holders attempting to

0:08:27.800 --> 0:08:31.680
<v Speaker 1>control the consumption of digital media in some way. So

0:08:31.880 --> 0:08:35.320
<v Speaker 1>let's take a step back for a minute. When I

0:08:35.400 --> 0:08:39.240
<v Speaker 1>was a kid, if I had been anaird, well, which

0:08:39.280 --> 0:08:40.839
<v Speaker 1>I wasn't. I was a good kid. But let's say

0:08:40.840 --> 0:08:43.840
<v Speaker 1>that I was a rotten kid. Maybe I might go

0:08:43.960 --> 0:08:49.040
<v Speaker 1>down to the local Turtles music store in Gainesville, Georgia,

0:08:49.120 --> 0:08:51.200
<v Speaker 1>and I decide I'm going to try and shoplift a

0:08:51.200 --> 0:08:54.480
<v Speaker 1>cassette tape of I don't know Bruce Springsteen's greatest hits.

0:08:55.080 --> 0:08:57.280
<v Speaker 1>If I had done that, well, I mean, first of all,

0:08:57.320 --> 0:08:59.360
<v Speaker 1>I would have been a thief, But on top of that,

0:08:59.559 --> 0:09:02.760
<v Speaker 1>I would have deprived that Turtles from being able to

0:09:02.800 --> 0:09:06.360
<v Speaker 1>sell that particular cassette. The store would be unable to

0:09:06.360 --> 0:09:08.800
<v Speaker 1>sell it because it's gone right, I mean, the physical

0:09:08.840 --> 0:09:12.040
<v Speaker 1>copy is in my hands. So stores had to come

0:09:12.080 --> 0:09:16.080
<v Speaker 1>up with various methods to discourage or prevent shoplifting. But

0:09:16.200 --> 0:09:19.240
<v Speaker 1>then skip ahead a few decades now you're in a

0:09:19.360 --> 0:09:22.800
<v Speaker 1>world with digital files, and that world is very different.

0:09:22.840 --> 0:09:25.560
<v Speaker 1>For one thing, it is way easier to make copies

0:09:25.600 --> 0:09:28.160
<v Speaker 1>of digital files than it would be with physical media.

0:09:28.400 --> 0:09:31.400
<v Speaker 1>Not that you couldn't make physical copies. We could, it

0:09:31.480 --> 0:09:35.120
<v Speaker 1>was just very time consuming and by the way, big

0:09:35.120 --> 0:09:37.920
<v Speaker 1>companies weren't huge fans of even that kind of copying

0:09:38.000 --> 0:09:41.800
<v Speaker 1>back in the day. So various media companies came up

0:09:41.840 --> 0:09:45.559
<v Speaker 1>with ways to limit or restrict how users could experience

0:09:45.640 --> 0:09:50.280
<v Speaker 1>and more specifically, how they could copy media. So, for example,

0:09:50.640 --> 0:09:53.600
<v Speaker 1>there might be copy protection on a file that only

0:09:53.640 --> 0:09:56.319
<v Speaker 1>allows it to be copied a certain amount of times

0:09:56.320 --> 0:09:59.559
<v Speaker 1>before it's lockdown, so you can only install this file

0:10:00.080 --> 0:10:02.880
<v Speaker 1>on a certain number of machines, and then after that

0:10:03.280 --> 0:10:05.960
<v Speaker 1>the code would not allow you to transfer it to

0:10:06.000 --> 0:10:10.000
<v Speaker 1>a new device. Um Or there might be DRM that

0:10:10.200 --> 0:10:14.360
<v Speaker 1>connects to the Internet where it phones home back to

0:10:14.480 --> 0:10:18.720
<v Speaker 1>whatever the I P holders system is and keeps them

0:10:18.760 --> 0:10:22.960
<v Speaker 1>informed about how that media is being used. The goal

0:10:23.040 --> 0:10:27.520
<v Speaker 1>of DRM is mostly to prevent piracy and to stop

0:10:27.559 --> 0:10:32.720
<v Speaker 1>the unlicensed sharing of technology, and I frequently think of

0:10:32.720 --> 0:10:35.520
<v Speaker 1>it in terms of media. That's the example that I

0:10:35.559 --> 0:10:39.120
<v Speaker 1>always go to. However, DRM can actually cover all sorts

0:10:39.160 --> 0:10:43.200
<v Speaker 1>of technologies beyond even digital files. That includes hardware, like

0:10:43.240 --> 0:10:48.400
<v Speaker 1>physical hardware, including stuff like tractors. So why tractors. Well,

0:10:48.480 --> 0:10:51.680
<v Speaker 1>let's say you're a company like John Dear, because John

0:10:51.760 --> 0:10:54.839
<v Speaker 1>Deer does this, and you make tractors, and you know

0:10:55.240 --> 0:10:57.600
<v Speaker 1>that somewhere down the line, people are going to need

0:10:57.640 --> 0:11:00.400
<v Speaker 1>to have those tractors repaired or have some sort of

0:11:00.440 --> 0:11:04.040
<v Speaker 1>maintenance done on them. By including dr M, you can

0:11:04.080 --> 0:11:07.800
<v Speaker 1>make sure that only licensed mechanics, which are people who

0:11:07.880 --> 0:11:10.880
<v Speaker 1>have paid you for the privilege of being able to

0:11:10.920 --> 0:11:13.600
<v Speaker 1>work on these types of machines. They're the only ones

0:11:13.600 --> 0:11:19.040
<v Speaker 1>who can legally repair John Dear tractors. Because the Digital

0:11:19.080 --> 0:11:22.840
<v Speaker 1>Millennium Copyright Act or d m c A made it

0:11:22.960 --> 0:11:27.679
<v Speaker 1>illegal to try and circumvent dr M, So even if

0:11:27.720 --> 0:11:31.360
<v Speaker 1>you were a mechanically savvy farmer and you wanted to

0:11:31.400 --> 0:11:34.520
<v Speaker 1>do your own repairs, you would not be allowed to

0:11:34.520 --> 0:11:37.319
<v Speaker 1>do that legally. You would have to break the law

0:11:37.360 --> 0:11:39.840
<v Speaker 1>because you'd have to get around the DRM to do it,

0:11:40.240 --> 0:11:42.480
<v Speaker 1>or I guess you could go through the trouble to

0:11:42.600 --> 0:11:45.800
<v Speaker 1>apply and become a licensed mechanic with John Dear, but

0:11:45.840 --> 0:11:48.960
<v Speaker 1>I think that's probably going too far. So one of

0:11:49.000 --> 0:11:52.120
<v Speaker 1>the really big issues with DRM is that it can

0:11:52.160 --> 0:11:56.520
<v Speaker 1>have unintended consequences and make it more difficult to legally

0:11:56.679 --> 0:11:59.920
<v Speaker 1>make use of a product that you've actually purchased yourself.

0:12:00.320 --> 0:12:04.760
<v Speaker 1>So in many ways, DRM can actually end up encouraging piracy.

0:12:05.120 --> 0:12:09.160
<v Speaker 1>And that's because frequently pirates will actually work to strip

0:12:09.320 --> 0:12:13.280
<v Speaker 1>DRM out of products. That removes all those restrictions, which

0:12:13.320 --> 0:12:16.520
<v Speaker 1>again affect not just people who are trying to steal stuff,

0:12:16.520 --> 0:12:20.160
<v Speaker 1>it affects people who have legitimately purchased things. The moral

0:12:20.240 --> 0:12:22.240
<v Speaker 1>of the story, I think is that if you make

0:12:22.320 --> 0:12:25.760
<v Speaker 1>it harder for people to use something legally, they are

0:12:25.840 --> 0:12:30.040
<v Speaker 1>far more likely to turn to illegal means to do so. Anyway,

0:12:30.160 --> 0:12:33.160
<v Speaker 1>dr M comes in all different forms, Some are less

0:12:33.160 --> 0:12:36.400
<v Speaker 1>obnoxious than others, and I do want to make this clear.

0:12:36.520 --> 0:12:39.760
<v Speaker 1>I get the motivation for using it. I mean, companies

0:12:39.840 --> 0:12:42.920
<v Speaker 1>make revenue off their intellectual property. They don't want to

0:12:42.920 --> 0:12:46.840
<v Speaker 1>see that go away, so it's in their best interests

0:12:46.920 --> 0:12:50.480
<v Speaker 1>to try and find ways to protect that. It's just

0:12:50.559 --> 0:12:53.319
<v Speaker 1>that a lot of the d r M approaches seem

0:12:53.400 --> 0:12:58.160
<v Speaker 1>to not quite achieve that goal and instead just create frustrations.

0:12:59.760 --> 0:13:03.760
<v Speaker 1>Net is DVD and I included this one because I mean,

0:13:03.800 --> 0:13:06.400
<v Speaker 1>I'm pretty sure everyone out there knows what a DVD is,

0:13:06.480 --> 0:13:09.840
<v Speaker 1>but the actual initialism used to trip me up all

0:13:09.840 --> 0:13:11.680
<v Speaker 1>the time, because I grew up in the era in

0:13:11.720 --> 0:13:15.720
<v Speaker 1>which compact discs or c d s first debuted and

0:13:15.800 --> 0:13:19.680
<v Speaker 1>they transformed the music industry, and then DVDs came around

0:13:19.720 --> 0:13:21.880
<v Speaker 1>to do the same for the home video market and

0:13:21.880 --> 0:13:25.880
<v Speaker 1>then beyond, so the humble VHS tape eventually faded away

0:13:25.880 --> 0:13:28.560
<v Speaker 1>as a result, And I always used to think that

0:13:28.679 --> 0:13:34.079
<v Speaker 1>DVD stood for digital video disc. But that ain't it,

0:13:34.320 --> 0:13:36.160
<v Speaker 1>or at least that's not the whole story. And I'm

0:13:36.160 --> 0:13:38.080
<v Speaker 1>sure a lot of you out there are way smarter

0:13:38.160 --> 0:13:40.200
<v Speaker 1>than I am, way more informed than I am, and

0:13:40.240 --> 0:13:44.280
<v Speaker 1>you're all shouting the real name, which is digital versatile

0:13:44.400 --> 0:13:48.160
<v Speaker 1>disc now, to be fair, at least according to some sources,

0:13:48.360 --> 0:13:52.480
<v Speaker 1>the original name was digital video disc. But at some

0:13:52.559 --> 0:13:56.080
<v Speaker 1>point the manufacturers who were putting this together figured that

0:13:56.679 --> 0:13:59.880
<v Speaker 1>this could give people the impression that DVDs are only

0:14:00.080 --> 0:14:05.000
<v Speaker 1>good for storing video content because people can get very

0:14:05.120 --> 0:14:08.240
<v Speaker 1>narrow focused on this sort of stuff. But of course

0:14:08.320 --> 0:14:12.720
<v Speaker 1>DVDs can hold all sorts of different types of digital information,

0:14:13.080 --> 0:14:16.920
<v Speaker 1>so that was why they swapped out video for versatile

0:14:17.400 --> 0:14:19.840
<v Speaker 1>that would replace video. Except no one really paid much

0:14:19.880 --> 0:14:22.880
<v Speaker 1>attention to that, and they just still called DVD digital

0:14:23.000 --> 0:14:26.800
<v Speaker 1>video disc or just DVD. They never bothered to call

0:14:26.880 --> 0:14:31.520
<v Speaker 1>it the full thing anyway. Light compact discs DVDs are

0:14:31.560 --> 0:14:34.600
<v Speaker 1>a type of optical storage, which means we use light

0:14:34.840 --> 0:14:38.800
<v Speaker 1>to read and write information on those discs. Companies like

0:14:38.880 --> 0:14:42.840
<v Speaker 1>Sony and Phillips started working on DVD technology not long

0:14:42.920 --> 0:14:47.360
<v Speaker 1>after releasing the first compact discs. So the c D

0:14:47.680 --> 0:14:51.600
<v Speaker 1>allowed for the storage of large digital files like high

0:14:51.680 --> 0:14:55.680
<v Speaker 1>quality audio files, but with a refinement, these companies knew

0:14:55.720 --> 0:14:59.080
<v Speaker 1>that they could cram even more information onto a disk.

0:14:59.600 --> 0:15:03.160
<v Speaker 1>So for about a decade uh two different big groups

0:15:03.200 --> 0:15:05.520
<v Speaker 1>of companies began to work on the next generation of

0:15:05.520 --> 0:15:09.720
<v Speaker 1>optical discs, and it came down to two competing formats.

0:15:09.760 --> 0:15:13.280
<v Speaker 1>So in this corna you had Sony and Phillips that

0:15:13.400 --> 0:15:17.120
<v Speaker 1>had developed a technology that they called the Multimedia c

0:15:17.320 --> 0:15:21.320
<v Speaker 1>D or m M c D, and in this corna

0:15:21.440 --> 0:15:24.440
<v Speaker 1>you had Tashiba and Time Warner a couple of other companies,

0:15:24.840 --> 0:15:27.800
<v Speaker 1>and they had really led the development on a format

0:15:27.840 --> 0:15:32.680
<v Speaker 1>called super Density discs or s D. Seeing how two

0:15:32.760 --> 0:15:36.760
<v Speaker 1>competing formats could ultimately hurt the market. As anyone who

0:15:36.800 --> 0:15:39.560
<v Speaker 1>has been a consumer during a format war can tell you,

0:15:40.000 --> 0:15:42.560
<v Speaker 1>the group's ultimately decided that it would make way more

0:15:42.600 --> 0:15:46.080
<v Speaker 1>sense for them to collaborate and make a common format

0:15:46.480 --> 0:15:49.680
<v Speaker 1>that combined elements of both s D and m M

0:15:49.920 --> 0:15:55.080
<v Speaker 1>c D. That is what became DVD. DVD players went

0:15:55.120 --> 0:15:58.840
<v Speaker 1>on sale in Japan in n took another year for

0:15:58.880 --> 0:16:01.120
<v Speaker 1>them to come out over in the United States. And

0:16:01.200 --> 0:16:04.280
<v Speaker 1>the DVD could really hold way more information than a

0:16:04.360 --> 0:16:06.640
<v Speaker 1>c D. In fact, if you had a dual layer,

0:16:06.800 --> 0:16:10.520
<v Speaker 1>double sided DVD, you can store more than ten times

0:16:10.560 --> 0:16:14.520
<v Speaker 1>the amount of information that could fit on a compact disc. Well,

0:16:14.880 --> 0:16:17.800
<v Speaker 1>we are finally through the d s. Everyone and when

0:16:17.880 --> 0:16:21.200
<v Speaker 1>we come back will jump on those ease. But I

0:16:21.200 --> 0:16:23.560
<v Speaker 1>only have a couple of them, so stay tuned. We're

0:16:23.560 --> 0:16:35.200
<v Speaker 1>gonna take a quick break, and our first e goes

0:16:35.280 --> 0:16:39.200
<v Speaker 1>to e f F. So in technology, this stands for

0:16:39.240 --> 0:16:44.760
<v Speaker 1>the Electronic Frontier Foundation. Back in a trio of guys

0:16:44.800 --> 0:16:48.960
<v Speaker 1>decided to form a nonprofit organization dedicated to defending civil

0:16:49.000 --> 0:16:53.400
<v Speaker 1>liberties in the digital world. And these founders included a

0:16:53.440 --> 0:16:56.000
<v Speaker 1>programmer who was perhaps best known for his role in

0:16:56.040 --> 0:17:00.160
<v Speaker 1>developing the spreadsheet software Lotus one, two three. That was

0:17:00.280 --> 0:17:04.399
<v Speaker 1>Mitch Kapor. Then there's an activist and developer named John

0:17:04.440 --> 0:17:08.320
<v Speaker 1>Gilmour who worked on many different types of software, including

0:17:08.720 --> 0:17:12.840
<v Speaker 1>tons of software under the GANOW license, so more about

0:17:12.880 --> 0:17:17.520
<v Speaker 1>GNU in the future. And then there was John Perry Barlow,

0:17:17.640 --> 0:17:22.480
<v Speaker 1>who was, among many many other things, a lyricist for

0:17:22.520 --> 0:17:26.159
<v Speaker 1>the band The Grateful Dead. Now, those three men shared

0:17:26.200 --> 0:17:29.280
<v Speaker 1>a common passion for the defense of civil liberties, and

0:17:29.280 --> 0:17:32.679
<v Speaker 1>they saw technology as being both a great enabler of

0:17:32.760 --> 0:17:36.080
<v Speaker 1>liberty as well as a potential threat to it depending

0:17:36.080 --> 0:17:39.560
<v Speaker 1>on how it's used. The inciting incident that led to

0:17:39.600 --> 0:17:42.119
<v Speaker 1>the formation of the e f F revolved around a

0:17:42.200 --> 0:17:46.280
<v Speaker 1>games publisher called Steve Jackson Games. And when I say

0:17:46.359 --> 0:17:50.480
<v Speaker 1>games publisher, I mean hard copy stuff like board games

0:17:50.520 --> 0:17:53.600
<v Speaker 1>and role playing games and card games, not video games

0:17:53.640 --> 0:17:57.159
<v Speaker 1>or computer games. So some famous ones include shay Geek,

0:17:57.400 --> 0:18:00.280
<v Speaker 1>which is sort of a comedy card game, or money Skin,

0:18:00.520 --> 0:18:05.919
<v Speaker 1>another comedy card game, This one fantasy oriented. There's Illuminati,

0:18:05.960 --> 0:18:09.440
<v Speaker 1>which is a game of various conspiracies competing against each

0:18:09.440 --> 0:18:12.880
<v Speaker 1>other in a way. And then there's girp's the Generic

0:18:13.000 --> 0:18:16.280
<v Speaker 1>Universal role Playing System and their tons of other ones.

0:18:16.800 --> 0:18:20.320
<v Speaker 1>So what does a company that makes board games and

0:18:20.440 --> 0:18:23.000
<v Speaker 1>RPGs and card games have to do with the e

0:18:23.160 --> 0:18:27.040
<v Speaker 1>f FF. Well, back in nine Steve Jackson had his

0:18:27.080 --> 0:18:30.960
<v Speaker 1>company headquarters in Austin, Texas, and they were raided by

0:18:31.000 --> 0:18:36.840
<v Speaker 1>the Secret Service. What all, right, now, stay with me. So,

0:18:37.000 --> 0:18:41.399
<v Speaker 1>in the late eighties, someone got hold of a proprietary

0:18:41.560 --> 0:18:45.320
<v Speaker 1>document that belonged to Bell South. They were able to

0:18:45.720 --> 0:18:48.600
<v Speaker 1>get hold of this and then they shared it. That

0:18:48.680 --> 0:18:52.840
<v Speaker 1>document pertained to the nine one one emergency system, and

0:18:52.880 --> 0:18:56.080
<v Speaker 1>the fear was that if hackers were able to exploit

0:18:56.119 --> 0:18:59.280
<v Speaker 1>that system, they might come up the works and thus

0:18:59.320 --> 0:19:02.000
<v Speaker 1>people who actually had to report emergencies would have no

0:19:02.040 --> 0:19:04.720
<v Speaker 1>way of doing it. So it represented sort of a

0:19:04.760 --> 0:19:07.920
<v Speaker 1>major threat. The Secret Service got involved to find out

0:19:08.000 --> 0:19:10.959
<v Speaker 1>who was at fault, who had who was responsible, and

0:19:11.000 --> 0:19:14.240
<v Speaker 1>to to go after them, and they found that the

0:19:14.320 --> 0:19:19.320
<v Speaker 1>document had been posted on a bulletin board system or BBS. Now,

0:19:19.359 --> 0:19:22.879
<v Speaker 1>I guess I could have included BBS in our tech glossary,

0:19:22.960 --> 0:19:27.560
<v Speaker 1>but BBS is a pretty outdated term these days. It's

0:19:27.600 --> 0:19:31.200
<v Speaker 1>essentially a predecessor to the kind of stuff you would

0:19:31.200 --> 0:19:34.720
<v Speaker 1>see with the Internet, where someone would have special software

0:19:35.080 --> 0:19:37.800
<v Speaker 1>that would allow other people to dial into their computer

0:19:38.119 --> 0:19:40.040
<v Speaker 1>so their computer could host all sorts of stuff like

0:19:40.080 --> 0:19:43.240
<v Speaker 1>message boards and games and files and that kind of thing.

0:19:43.600 --> 0:19:47.440
<v Speaker 1>People could dial into that computer or BBS and access

0:19:47.480 --> 0:19:52.199
<v Speaker 1>those things anyway. The guy who ran this particular BBS,

0:19:52.200 --> 0:19:56.040
<v Speaker 1>but again not necessarily the actual person responsible for posting

0:19:56.119 --> 0:19:59.920
<v Speaker 1>the file there, was an employee of Steve Jackson Game.

0:20:00.560 --> 0:20:03.480
<v Speaker 1>So the Secret Service decided they would seize all of

0:20:03.520 --> 0:20:06.359
<v Speaker 1>this guy's computers, but they would also seize all of

0:20:06.400 --> 0:20:09.280
<v Speaker 1>the computers of his employer to make certain that this

0:20:09.359 --> 0:20:15.040
<v Speaker 1>proprietary document wasn't getting spread around. This was a crushing

0:20:15.359 --> 0:20:18.720
<v Speaker 1>blow to Steve Jackson Games and Steve Jackson himself. His

0:20:18.760 --> 0:20:21.960
<v Speaker 1>company just couldn't conduct business while the computers were in

0:20:22.000 --> 0:20:26.400
<v Speaker 1>Secret Service custody, and eventually Steve Jackson Games got their

0:20:26.400 --> 0:20:29.399
<v Speaker 1>computers back, but it was clear that the Secret Service

0:20:29.400 --> 0:20:32.960
<v Speaker 1>had really combed through the internal emails inside the company,

0:20:33.200 --> 0:20:36.800
<v Speaker 1>and Steve Jackson wanted to pursue civil action against the

0:20:36.840 --> 0:20:40.199
<v Speaker 1>Secret Service for damages and wanted to lean on a

0:20:40.240 --> 0:20:44.920
<v Speaker 1>civil rights organization to help with that lawsuit, but there

0:20:44.960 --> 0:20:49.120
<v Speaker 1>really wasn't such any organization in existence that would really

0:20:49.160 --> 0:20:53.240
<v Speaker 1>fit the bill. That's what precipitated the formation of the

0:20:53.280 --> 0:20:58.439
<v Speaker 1>Electronic Frontier Foundation. Today, the e f F helps in

0:20:58.680 --> 0:21:02.919
<v Speaker 1>similar legal cases that revolve around civil liberties and technology.

0:21:03.200 --> 0:21:07.320
<v Speaker 1>The e f F sometimes helps fund lawsuits or supplies

0:21:07.400 --> 0:21:11.920
<v Speaker 1>expertise in technical and digital matters, and the organization isn't

0:21:11.960 --> 0:21:14.560
<v Speaker 1>without critics. There's some people who argue that the e

0:21:14.760 --> 0:21:17.920
<v Speaker 1>f F has really helped tech companies kind of entrenched

0:21:17.920 --> 0:21:22.760
<v Speaker 1>themselves and protect themselves against regulation and other matters that

0:21:24.000 --> 0:21:27.399
<v Speaker 1>maybe didn't lead to the right outcome. But you know,

0:21:27.800 --> 0:21:30.600
<v Speaker 1>it's it's kind of like anything with humans. There's stuff

0:21:30.600 --> 0:21:34.879
<v Speaker 1>that is good and stuff that's not so good. Next,

0:21:34.920 --> 0:21:37.439
<v Speaker 1>we have e O L. So in the movie Tron,

0:21:38.040 --> 0:21:40.560
<v Speaker 1>e O L was the Master Control programs way of

0:21:40.680 --> 0:21:43.080
<v Speaker 1>ending a line of communication. I mean it literally meant

0:21:43.359 --> 0:21:46.040
<v Speaker 1>end of line. There's the end of Line club in

0:21:46.080 --> 0:21:49.440
<v Speaker 1>the Tron Legacy film. But in this case, I actually

0:21:49.440 --> 0:21:53.119
<v Speaker 1>mean e O L as end of life, meaning the

0:21:53.160 --> 0:21:55.600
<v Speaker 1>stage of a products life cycle. In which it's just

0:21:55.640 --> 0:21:59.120
<v Speaker 1>gonna get worse from here on out. So, for example,

0:21:59.520 --> 0:22:02.919
<v Speaker 1>let's take Windows XP, which is a very or was

0:22:02.960 --> 0:22:06.160
<v Speaker 1>a very popular operating system. There's still people out there

0:22:06.160 --> 0:22:08.719
<v Speaker 1>who are using it today, despite the fact that it's

0:22:08.760 --> 0:22:12.520
<v Speaker 1>sadly outdated. Microsoft released Windows XP way back in two

0:22:12.520 --> 0:22:15.480
<v Speaker 1>thousand one, and that system dominated the market share for

0:22:15.520 --> 0:22:19.360
<v Speaker 1>operating systems on personal computers at the time. And while

0:22:19.400 --> 0:22:23.120
<v Speaker 1>Microsoft would release the successor to Windows XP in two

0:22:23.160 --> 0:22:26.639
<v Speaker 1>thousand and seven, it actually continued to release service packs

0:22:26.680 --> 0:22:30.200
<v Speaker 1>for Windows XP up through two thousand eight, and even

0:22:30.240 --> 0:22:34.280
<v Speaker 1>provided extended support until two thousand fourteen. But by then

0:22:34.440 --> 0:22:37.520
<v Speaker 1>Microsoft was really pushing people to please, for the love

0:22:37.560 --> 0:22:41.880
<v Speaker 1>of technology, update to a more recent operating system. Companies

0:22:42.200 --> 0:22:46.520
<v Speaker 1>can't continue to support old software indefinitely and still dedicate

0:22:46.560 --> 0:22:51.359
<v Speaker 1>resources to making new stuff. Plus, fewer pieces of current

0:22:51.440 --> 0:22:55.119
<v Speaker 1>software were actually compatible with this older Windows operating system,

0:22:55.440 --> 0:22:58.280
<v Speaker 1>and so really, by two thousand eight, Windows XP was

0:22:58.440 --> 0:23:02.160
<v Speaker 1>entering its e o L phase. Microsoft would stop updating

0:23:02.160 --> 0:23:05.840
<v Speaker 1>it and the product would grow increasingly obsolete over time.

0:23:06.520 --> 0:23:09.880
<v Speaker 1>Another example of e o L is easy to see

0:23:09.880 --> 0:23:13.760
<v Speaker 1>with smartphones. Smartphones depend upon the interaction of hardware, that

0:23:13.840 --> 0:23:18.200
<v Speaker 1>being the actual smartphone mobile device and software that being

0:23:18.200 --> 0:23:21.120
<v Speaker 1>the operating system for that device, on top of which

0:23:21.160 --> 0:23:24.800
<v Speaker 1>all the apps live. So with Apple, we are now

0:23:24.880 --> 0:23:28.520
<v Speaker 1>on IO S Sport Team, and the oldest iPhone capable

0:23:28.600 --> 0:23:32.439
<v Speaker 1>of running that version of iOS is the iPhone six S.

0:23:32.680 --> 0:23:34.680
<v Speaker 1>That one is the one that originally launched in two

0:23:34.680 --> 0:23:38.959
<v Speaker 1>thousand fifteen. Older iPhones before the success, even if they

0:23:38.960 --> 0:23:42.000
<v Speaker 1>are still operational, are firmly in the e o L

0:23:42.080 --> 0:23:44.399
<v Speaker 1>phase because they can no longer keep pace with the

0:23:44.480 --> 0:23:47.480
<v Speaker 1>latest operating systems, which means fewer apps are going to

0:23:47.600 --> 0:23:51.360
<v Speaker 1>run on them and they will become increasingly useless as

0:23:51.359 --> 0:23:55.440
<v Speaker 1>time goes on. For companies, e OL might arrive much

0:23:55.440 --> 0:23:59.120
<v Speaker 1>earlier than for customers, so a company will end sales

0:23:59.160 --> 0:24:01.960
<v Speaker 1>and marketing effort around a product that it designates as

0:24:02.000 --> 0:24:04.720
<v Speaker 1>being in e o L. Essentially, the company says, we're

0:24:04.760 --> 0:24:06.719
<v Speaker 1>no longer going to sell this stuff. We're going to

0:24:06.720 --> 0:24:09.440
<v Speaker 1>sell the next version of this or you know, some

0:24:09.560 --> 0:24:12.920
<v Speaker 1>improved version of this, and they focus on that instead.

0:24:13.160 --> 0:24:16.600
<v Speaker 1>So they say we're done dedicating resources to supporting this

0:24:17.200 --> 0:24:20.280
<v Speaker 1>so that we can sell more stuff, more new stuff.

0:24:20.520 --> 0:24:23.160
<v Speaker 1>So a company could actually start stop selling a product

0:24:23.600 --> 0:24:26.280
<v Speaker 1>but continue supporting it for a while longer. In the

0:24:26.280 --> 0:24:30.200
<v Speaker 1>case of Microsoft, for example, they stopped selling XP long

0:24:30.280 --> 0:24:34.919
<v Speaker 1>before they stopped actually providing support for it. Next is

0:24:35.000 --> 0:24:37.760
<v Speaker 1>fact f a Q. I included this one even though

0:24:37.800 --> 0:24:40.959
<v Speaker 1>I think probably everyone listening to this already knows it.

0:24:41.480 --> 0:24:45.240
<v Speaker 1>It of course stands for frequently asked questions. Anyone who

0:24:45.240 --> 0:24:47.879
<v Speaker 1>has ever served as a point of contact for any

0:24:48.080 --> 0:24:52.320
<v Speaker 1>organization knows that of the time, you're answering the same

0:24:52.359 --> 0:24:56.000
<v Speaker 1>basic questions repeatedly throughout the day. So one way to

0:24:56.040 --> 0:24:59.240
<v Speaker 1>address that is to create a fact and that has

0:24:59.280 --> 0:25:02.800
<v Speaker 1>those basic answers already in there, so people can see

0:25:02.840 --> 0:25:05.399
<v Speaker 1>them right off the bat. So when people use the fact,

0:25:05.680 --> 0:25:07.880
<v Speaker 1>it frees up the time of the person who otherwise

0:25:07.920 --> 0:25:11.080
<v Speaker 1>would have to respond, and you know, it just makes

0:25:11.119 --> 0:25:15.200
<v Speaker 1>it easier to find answers. In general, the term fact

0:25:15.240 --> 0:25:19.359
<v Speaker 1>actually predates the web, possibly emerging from the electronic mailing

0:25:19.400 --> 0:25:23.240
<v Speaker 1>lists and Usenet groups in the nineteen eighties. Next, we

0:25:23.320 --> 0:25:28.160
<v Speaker 1>have f c C. This stands for the Federal Communications Commission,

0:25:28.359 --> 0:25:31.600
<v Speaker 1>part of the United States government. It's easiest for me

0:25:31.680 --> 0:25:34.560
<v Speaker 1>to just quote the f CC's website to describe what

0:25:34.640 --> 0:25:38.639
<v Speaker 1>it does. So here it is quote The Federal Communications

0:25:38.640 --> 0:25:44.959
<v Speaker 1>Commission regulates interstate and international communications by radio, television, wire, satellite,

0:25:45.160 --> 0:25:48.600
<v Speaker 1>and cable in all fifty states, the District of Columbia,

0:25:48.960 --> 0:25:53.760
<v Speaker 1>and US territories. An independent US government agency overseen by Congress,

0:25:53.960 --> 0:25:57.439
<v Speaker 1>the Commission is the federal agency responsible for implementing and

0:25:57.600 --> 0:26:03.800
<v Speaker 1>enforcing America's communications laws and regulations. So that organization formed

0:26:03.840 --> 0:26:07.119
<v Speaker 1>after the passing of the Communications Act of nineteen thirty four,

0:26:07.400 --> 0:26:10.840
<v Speaker 1>and it has helped shape the landscape of technology quite

0:26:10.840 --> 0:26:13.760
<v Speaker 1>a bit in the United States, sometimes for the better

0:26:14.040 --> 0:26:18.240
<v Speaker 1>and sometimes not. The FCC is supposed to promote competition

0:26:18.280 --> 0:26:22.960
<v Speaker 1>between various communications companies while also encouraging innovation and investment

0:26:23.080 --> 0:26:26.679
<v Speaker 1>in services so that people get access to stuff like

0:26:26.720 --> 0:26:31.360
<v Speaker 1>broadband connectivity. But a quick look at the telecommunications landscape

0:26:31.359 --> 0:26:33.719
<v Speaker 1>in America tells you that for a lot of folks,

0:26:33.800 --> 0:26:37.479
<v Speaker 1>the whole competition thing really isn't a thing. It's not

0:26:37.520 --> 0:26:41.679
<v Speaker 1>that prominent. I mean, over the years, through various mergers

0:26:41.720 --> 0:26:45.160
<v Speaker 1>and acquisitions, we've seen many regions get carved out by

0:26:45.240 --> 0:26:49.040
<v Speaker 1>one or maybe two telecommunications companies. And I don't know

0:26:49.080 --> 0:26:51.600
<v Speaker 1>what it's like where you live, however, at my home,

0:26:51.800 --> 0:26:53.840
<v Speaker 1>because I checked it this morning, just to make sure.

0:26:54.520 --> 0:26:59.280
<v Speaker 1>We only have one telecommunications provider that offers connectivity at

0:26:59.359 --> 0:27:03.800
<v Speaker 1>high speed needs at my place, and even that isn't fiber.

0:27:03.880 --> 0:27:06.679
<v Speaker 1>I don't get fiber connectivity where I live. And I

0:27:06.720 --> 0:27:09.920
<v Speaker 1>live in the city of Atlanta, y'all. I mean, I'm

0:27:10.200 --> 0:27:12.800
<v Speaker 1>not in like the sticks or something. I'm in the

0:27:12.800 --> 0:27:16.680
<v Speaker 1>city limits. But enough about me griping about my personal

0:27:17.000 --> 0:27:21.160
<v Speaker 1>lack of connectivity. The FCC has also played an inconsistent

0:27:21.280 --> 0:27:25.040
<v Speaker 1>role in terms of ensuring net neutrality in the United States.

0:27:25.240 --> 0:27:28.240
<v Speaker 1>The concept of net neutrality includes a lot of stuff,

0:27:28.560 --> 0:27:31.520
<v Speaker 1>but one of the big ones is all content should

0:27:31.520 --> 0:27:35.480
<v Speaker 1>be treated equally across all service providers. So, in other words,

0:27:35.840 --> 0:27:37.920
<v Speaker 1>if there's a company that's both an I s P

0:27:38.400 --> 0:27:41.879
<v Speaker 1>and a content company, that I s P should not

0:27:42.000 --> 0:27:46.200
<v Speaker 1>prioritize its own traffic over that from other content providers.

0:27:46.720 --> 0:27:49.440
<v Speaker 1>There's a lot more to it than that. Net neutrality

0:27:49.520 --> 0:27:54.080
<v Speaker 1>is a very big topic, and during certain political administrations,

0:27:54.080 --> 0:27:57.000
<v Speaker 1>the FCC has pushed to create rules and policies that

0:27:57.080 --> 0:28:01.399
<v Speaker 1>strengthen net neutrality, such as under the Obama administration, while

0:28:01.440 --> 0:28:05.640
<v Speaker 1>in others the FCC has largely dismantled those same systems,

0:28:05.680 --> 0:28:09.359
<v Speaker 1>such as during Trump's presidency fun times. And the reason

0:28:09.400 --> 0:28:11.600
<v Speaker 1>for that change, by the way, is that the leadership

0:28:11.720 --> 0:28:15.680
<v Speaker 1>of the f c C comes by appointment by whomever

0:28:15.880 --> 0:28:20.320
<v Speaker 1>is president at that time, and so as presidential administrations change,

0:28:20.640 --> 0:28:24.400
<v Speaker 1>so too does the f c C. Anyway, you'll hear

0:28:24.440 --> 0:28:27.400
<v Speaker 1>a lot about the FCC being involved in various tech

0:28:27.440 --> 0:28:33.280
<v Speaker 1>related issues here in the United States. Next up flops. Now,

0:28:33.320 --> 0:28:36.320
<v Speaker 1>this doesn't just describe that one stage play I was

0:28:36.359 --> 0:28:38.920
<v Speaker 1>in back in two thousand two. Now, this is an

0:28:38.960 --> 0:28:43.560
<v Speaker 1>acronym that stands for floating point operations per second. So

0:28:43.720 --> 0:28:45.800
<v Speaker 1>if you remember when I talked about c p U

0:28:45.960 --> 0:28:49.120
<v Speaker 1>s in the previous episode, I mentioned that we measure

0:28:49.160 --> 0:28:52.840
<v Speaker 1>their performance in part by clock cycles, which is kind

0:28:52.880 --> 0:28:56.840
<v Speaker 1>of like how many instructions the CPU can execute per second.

0:28:57.440 --> 0:29:00.480
<v Speaker 1>But there's another way to measure computer perform mormants, and

0:29:00.520 --> 0:29:03.440
<v Speaker 1>that's in how many floating point operations it can handle

0:29:03.480 --> 0:29:07.160
<v Speaker 1>per second. So what is a floating point Well, you

0:29:07.160 --> 0:29:10.720
<v Speaker 1>can think of it as being similar to scientific note notation,

0:29:10.840 --> 0:29:14.200
<v Speaker 1>So you know, really big or really small numbers are

0:29:14.240 --> 0:29:17.400
<v Speaker 1>difficult to handle, even for computers, especially computers that have

0:29:17.440 --> 0:29:20.080
<v Speaker 1>to handle both at the same time. A computer has

0:29:20.120 --> 0:29:23.160
<v Speaker 1>a limit to how many digits it can hold at

0:29:23.200 --> 0:29:26.120
<v Speaker 1>any given moment. So floating points are a way to

0:29:26.200 --> 0:29:30.200
<v Speaker 1>indicate very large or very small numbers and makes them

0:29:30.280 --> 0:29:34.240
<v Speaker 1>much easier to handle and process. When we talk about supercomputers,

0:29:34.240 --> 0:29:37.040
<v Speaker 1>we typically refer to the number of flops those computers

0:29:37.040 --> 0:29:41.640
<v Speaker 1>can handle. The fastest supercomputer by this metric today is

0:29:41.680 --> 0:29:46.640
<v Speaker 1>the Fugaku, which is incredible. It's set an insane record

0:29:46.960 --> 0:29:51.200
<v Speaker 1>of four hundred forty two headah flops using the HPL

0:29:51.320 --> 0:29:54.520
<v Speaker 1>computer benchmark. It's a way of testing how many floating

0:29:54.520 --> 0:29:58.240
<v Speaker 1>operations are floating point operations I should say a computer

0:29:58.320 --> 0:30:02.160
<v Speaker 1>can complete in a second. So in the tech world, uh,

0:30:02.320 --> 0:30:04.440
<v Speaker 1>what does peda flop mean? Well, we use the word

0:30:04.520 --> 0:30:07.560
<v Speaker 1>kilo or the prefix kilo for thousand, we use mega

0:30:07.840 --> 0:30:12.200
<v Speaker 1>for a million, Giga for billion, terra for trillion, and

0:30:12.280 --> 0:30:17.080
<v Speaker 1>petta is for quadrillion, which means the Fugaku supercomputer reached

0:30:17.160 --> 0:30:21.640
<v Speaker 1>four hundred forty two quadrillion floating point operations per second

0:30:21.960 --> 0:30:25.800
<v Speaker 1>against this particular benchmark, which is pretty astounding, right. But

0:30:25.840 --> 0:30:29.520
<v Speaker 1>according to Tech Republic, Fugaku was also able to achieve

0:30:29.880 --> 0:30:33.680
<v Speaker 1>two point oh exa flops against the benchmark of high

0:30:33.680 --> 0:30:40.360
<v Speaker 1>performance computing Artificial intelligence workload or hpc AI another benchmark test.

0:30:40.880 --> 0:30:45.680
<v Speaker 1>So an exa flop is one quintillion flops. It's even

0:30:45.760 --> 0:30:48.640
<v Speaker 1>more like it's just the sucker is fast, is what

0:30:48.680 --> 0:30:52.840
<v Speaker 1>I'm saying. But typically when we're talking about flops, we're

0:30:52.840 --> 0:30:56.760
<v Speaker 1>talking about high performance compute. We're not talking about you know,

0:30:56.880 --> 0:31:01.120
<v Speaker 1>your standard laptop. Next is FPS. This one's actually tricky

0:31:01.160 --> 0:31:04.440
<v Speaker 1>because there are a few different FPS initialisms, and some

0:31:04.520 --> 0:31:07.000
<v Speaker 1>of them can actually apply to the same stuff but

0:31:07.080 --> 0:31:10.240
<v Speaker 1>in different ways. So, for example, in the world of

0:31:10.320 --> 0:31:14.520
<v Speaker 1>video games, you can have FPS, meaning a first person shooter,

0:31:14.840 --> 0:31:16.880
<v Speaker 1>which is a type of game in which your perspective

0:31:16.960 --> 0:31:19.400
<v Speaker 1>is from the first person point of view and you

0:31:19.480 --> 0:31:23.720
<v Speaker 1>run around, you know, shooting stuff. But FPS can also

0:31:23.880 --> 0:31:27.680
<v Speaker 1>stand for frames per second, as in the number of

0:31:27.800 --> 0:31:32.480
<v Speaker 1>rendered frames presented to a viewer each second, and this

0:31:32.600 --> 0:31:35.480
<v Speaker 1>version of FPS can apply to all sorts of games,

0:31:35.560 --> 0:31:38.840
<v Speaker 1>including first person shooter games, So you can talk about

0:31:38.880 --> 0:31:42.120
<v Speaker 1>the FPS for an FPS, which is a lot of fun.

0:31:42.240 --> 0:31:46.360
<v Speaker 1>Right anyway, frames per second is important for creating a

0:31:46.480 --> 0:31:50.400
<v Speaker 1>smooth video experience. So our vision tricks us if we

0:31:50.480 --> 0:31:53.640
<v Speaker 1>see a series of similar images and they're presented to

0:31:53.720 --> 0:31:56.680
<v Speaker 1>us in quick succession. We experienced this as if we're

0:31:56.720 --> 0:31:59.920
<v Speaker 1>watching something that's actually in motion, that the image itself

0:32:00.080 --> 0:32:03.320
<v Speaker 1>is moving. That's the whole basic foundation for film and

0:32:03.400 --> 0:32:06.880
<v Speaker 1>for animation. So with a classic film like something that's

0:32:06.920 --> 0:32:11.200
<v Speaker 1>actually on film itself, we watched the playback of images

0:32:11.280 --> 0:32:14.240
<v Speaker 1>at a rate of twenty four frames per second. That's

0:32:14.240 --> 0:32:16.440
<v Speaker 1>fast enough to make it seem as though we're watching

0:32:16.640 --> 0:32:19.600
<v Speaker 1>moving images, but in fact, if you just stop the projector,

0:32:20.000 --> 0:32:24.280
<v Speaker 1>you would see you're just looking at a series of photographs. Well,

0:32:24.280 --> 0:32:27.800
<v Speaker 1>in the digital world, fps is important too, and a

0:32:27.920 --> 0:32:31.200
<v Speaker 1>higher FPS typically means a better experience for the viewer,

0:32:31.560 --> 0:32:35.120
<v Speaker 1>particularly with video games. Higher FPS can help a gamer

0:32:35.160 --> 0:32:38.360
<v Speaker 1>make better choices while playing and time things out just right,

0:32:38.480 --> 0:32:40.640
<v Speaker 1>picking up on details that they might miss if they

0:32:40.640 --> 0:32:44.280
<v Speaker 1>had a lower FPS. But just as we saw with resolution,

0:32:44.360 --> 0:32:47.239
<v Speaker 1>there's a law of diminishing returns at play here, so

0:32:47.280 --> 0:32:50.240
<v Speaker 1>once you get over a certain FPS, which varies from

0:32:50.240 --> 0:32:54.320
<v Speaker 1>person to person, the benefits become less obvious as they

0:32:54.320 --> 0:32:57.640
<v Speaker 1>crank up. There are other fps is within the tech

0:32:57.680 --> 0:33:01.040
<v Speaker 1>world to like fast packet switching that refers to how

0:33:01.080 --> 0:33:05.200
<v Speaker 1>certain systems handled data transmissions across the system, but there's

0:33:05.240 --> 0:33:07.800
<v Speaker 1>no need to jump into all that here, All right,

0:33:08.960 --> 0:33:11.440
<v Speaker 1>I got a couple more f's to get through after

0:33:11.480 --> 0:33:22.840
<v Speaker 1>this break, so stick around for f's sake. Next up,

0:33:22.840 --> 0:33:25.200
<v Speaker 1>we got the f t C, and we're back to

0:33:25.280 --> 0:33:28.440
<v Speaker 1>another U. S government agency similar to what we talked

0:33:28.440 --> 0:33:31.640
<v Speaker 1>about with f c C, but the f t C

0:33:32.200 --> 0:33:35.560
<v Speaker 1>stands for the Federal Trade Commission. So while the f

0:33:35.680 --> 0:33:38.960
<v Speaker 1>c C specifically focuses on laws and regulations that relate

0:33:39.000 --> 0:33:43.120
<v Speaker 1>to communications, which includes telecommunications and the Internet and radio

0:33:43.160 --> 0:33:46.680
<v Speaker 1>and etcetera, the f t C is primarily focused on

0:33:46.800 --> 0:33:50.880
<v Speaker 1>enforcing antitrust laws and protecting consumers in the United States.

0:33:51.360 --> 0:33:54.200
<v Speaker 1>So in this case, the word trust refers to an

0:33:54.320 --> 0:33:58.160
<v Speaker 1>entity or sometimes a small group of entities that dominates

0:33:58.320 --> 0:34:02.560
<v Speaker 1>an industry and uses areas means to maintain that dominance

0:34:02.960 --> 0:34:06.440
<v Speaker 1>by keeping other companies from being able to compete. So

0:34:06.920 --> 0:34:11.719
<v Speaker 1>that can include stuff like fixing prices to undercut smaller competitors,

0:34:11.760 --> 0:34:16.040
<v Speaker 1>and these smaller competitors might not have the financial ability

0:34:16.120 --> 0:34:19.880
<v Speaker 1>to survive and they're effectively starved out because the dominant

0:34:19.880 --> 0:34:23.280
<v Speaker 1>company could sell stuff at a loss and just endure

0:34:23.360 --> 0:34:26.560
<v Speaker 1>that loss while waiting for the other businesses to die,

0:34:26.960 --> 0:34:29.920
<v Speaker 1>and at that point the company can then drive prices

0:34:29.960 --> 0:34:33.120
<v Speaker 1>way up because there's no competition for consumers to turn to.

0:34:33.719 --> 0:34:36.200
<v Speaker 1>So the FTC gets involved in a lot of the

0:34:36.239 --> 0:34:39.839
<v Speaker 1>tech world because we see some massive consolidations going on

0:34:40.120 --> 0:34:44.800
<v Speaker 1>within the space, whether it's Facebook gobbling up another social platform,

0:34:44.920 --> 0:34:49.360
<v Speaker 1>or Amazon buying up another marketplace, either real world or online,

0:34:49.880 --> 0:34:53.360
<v Speaker 1>or Google buying up pretty much everything in sight. The

0:34:53.480 --> 0:34:56.880
<v Speaker 1>FTC plays apart in making certain that companies are playing

0:34:56.880 --> 0:35:00.239
<v Speaker 1>by the rules, and like the f c C, this

0:35:00.360 --> 0:35:04.600
<v Speaker 1>isn't always you know, apparent, but then I guess it

0:35:04.600 --> 0:35:07.560
<v Speaker 1>all depends on how you interpret what the rules actually are.

0:35:08.000 --> 0:35:11.239
<v Speaker 1>On the consumer protection side, the FTC is also the

0:35:11.320 --> 0:35:16.360
<v Speaker 1>agency responsible for enforcing stuff like KAPPA, the Children's Online

0:35:16.400 --> 0:35:19.840
<v Speaker 1>Privacy Protection Act that we recently talked about. Because KAPPA

0:35:19.920 --> 0:35:23.120
<v Speaker 1>mostly relates to how companies collect and use children's information

0:35:23.160 --> 0:35:26.319
<v Speaker 1>by using the Internet, you might be tempted to think

0:35:26.360 --> 0:35:28.960
<v Speaker 1>that it's the f c C that would be in charge,

0:35:29.120 --> 0:35:31.640
<v Speaker 1>but that's just not the case. So it can get

0:35:31.680 --> 0:35:34.200
<v Speaker 1>a bit confusing when you're talking about the f c

0:35:34.440 --> 0:35:38.399
<v Speaker 1>C versus the f TC, and I sometimes mix up

0:35:38.440 --> 0:35:41.680
<v Speaker 1>the two myself. I've been guilty of it. The FTC, however,

0:35:41.800 --> 0:35:44.120
<v Speaker 1>is also older than the f c C. It traces

0:35:44.200 --> 0:35:48.640
<v Speaker 1>its history all the way back to nineteen fourteen. Moving

0:35:48.640 --> 0:35:52.840
<v Speaker 1>on f TP. You down with f TP, Yeah, you

0:35:52.880 --> 0:35:56.640
<v Speaker 1>know me? All right, I'm kind of dating myself here.

0:35:56.719 --> 0:36:00.120
<v Speaker 1>I'm actually very curious if producer Tari even recognized is

0:36:00.160 --> 0:36:04.240
<v Speaker 1>that reference? Okay? So, f t P stands for File

0:36:04.480 --> 0:36:07.719
<v Speaker 1>Transfer Protocol, and a protocol is just a set of

0:36:07.840 --> 0:36:11.880
<v Speaker 1>rules or instructions. So from a high level, this is

0:36:11.920 --> 0:36:16.280
<v Speaker 1>the set of rules that the guide how you transfer

0:36:16.360 --> 0:36:18.799
<v Speaker 1>files across networks. And when I say you, I really

0:36:18.840 --> 0:36:24.280
<v Speaker 1>mean how systems transfer files from one machine to another

0:36:24.440 --> 0:36:28.080
<v Speaker 1>across a network. It's one of the underlying technologies for

0:36:28.120 --> 0:36:31.680
<v Speaker 1>the Internet, with others being things like email and the

0:36:31.719 --> 0:36:35.479
<v Speaker 1>World Wide Web and stuff like that. FTP is also

0:36:35.520 --> 0:36:38.160
<v Speaker 1>one of the older protocols with regard to the Internet.

0:36:38.239 --> 0:36:42.680
<v Speaker 1>It was first outlined back in ninete. And that's it

0:36:42.760 --> 0:36:46.319
<v Speaker 1>for the f Alright, let's move on to g and

0:36:46.400 --> 0:36:49.680
<v Speaker 1>first up, we've got g d p R and we

0:36:49.719 --> 0:36:52.800
<v Speaker 1>start off with a biggie. This stands for General Data

0:36:52.840 --> 0:36:56.840
<v Speaker 1>Protection Regulation and it refers to a regulation in in

0:36:56.960 --> 0:37:01.319
<v Speaker 1>law in the European Union, and it concerns itself with

0:37:01.400 --> 0:37:06.239
<v Speaker 1>the privacy and data protection of EU citizens. So in

0:37:06.280 --> 0:37:09.960
<v Speaker 1>the EU member countries drafted out rules to protect privacy

0:37:09.960 --> 0:37:13.279
<v Speaker 1>and personal information and gave EU citizens more of a

0:37:13.400 --> 0:37:16.480
<v Speaker 1>say in how their data could be collected and used.

0:37:17.040 --> 0:37:20.520
<v Speaker 1>G d PR puts the onus on companies to follow

0:37:20.600 --> 0:37:25.800
<v Speaker 1>these rules or potentially face huge fines. Over in the

0:37:25.880 --> 0:37:29.920
<v Speaker 1>United States, the explosive growth of the Internet far outpaced

0:37:30.000 --> 0:37:35.400
<v Speaker 1>privacy laws, which in the US of been fairly lucy

0:37:35.440 --> 0:37:38.279
<v Speaker 1>goosey like there's only a few privacy laws or like

0:37:38.400 --> 0:37:42.240
<v Speaker 1>outright privacy laws in the United States. So as a result,

0:37:42.880 --> 0:37:45.960
<v Speaker 1>these companies that were web based had established some pretty

0:37:46.000 --> 0:37:49.920
<v Speaker 1>aggressive strategies when it comes to collecting, using, and sharing

0:37:50.000 --> 0:37:53.880
<v Speaker 1>personal information. In fact, there's an entire industry based around

0:37:54.000 --> 0:37:57.839
<v Speaker 1>establishing huge databases of personal info and then charging other

0:37:57.880 --> 0:38:02.960
<v Speaker 1>companies to access those databases. Our information are. Personal info

0:38:03.320 --> 0:38:07.000
<v Speaker 1>is the currency of much of modern technology. While the

0:38:07.040 --> 0:38:10.319
<v Speaker 1>member states of the EU wanted to create rules to

0:38:10.400 --> 0:38:14.719
<v Speaker 1>restrict how companies could do this with EU citizens, so

0:38:14.840 --> 0:38:18.080
<v Speaker 1>they wouldn't be given free regin to collect and exploit data.

0:38:18.160 --> 0:38:21.160
<v Speaker 1>They would actually need to follow specific rules, which includes

0:38:21.239 --> 0:38:25.080
<v Speaker 1>alerting users to any points of data collection, as well

0:38:25.120 --> 0:38:28.120
<v Speaker 1>as to declare how and why that data will be used.

0:38:28.800 --> 0:38:32.120
<v Speaker 1>The restrictions meant that companies had to change how they

0:38:32.200 --> 0:38:36.319
<v Speaker 1>handled information, and that in itself became a kind of

0:38:36.440 --> 0:38:39.800
<v Speaker 1>micro industry. We had a lot of consultants that worked

0:38:39.840 --> 0:38:43.160
<v Speaker 1>with tech companies to make certain that their policies and

0:38:43.280 --> 0:38:46.960
<v Speaker 1>processes were compliant with g d p R, because otherwise

0:38:47.280 --> 0:38:51.239
<v Speaker 1>things could get super expensive, really fast. They also tend

0:38:51.280 --> 0:38:54.600
<v Speaker 1>to involve some pretty negative press. If a company is

0:38:54.600 --> 0:38:57.400
<v Speaker 1>found to have violated g DPR, it's not a good look.

0:38:58.080 --> 0:39:01.240
<v Speaker 1>The passing of g d p R effectively since shock

0:39:01.320 --> 0:39:04.440
<v Speaker 1>waves through the tech industry, which at that point really

0:39:04.520 --> 0:39:07.640
<v Speaker 1>wasn't used to governments getting that proactive in the protection

0:39:07.640 --> 0:39:10.960
<v Speaker 1>of citizen data, and g DPR has gone on to

0:39:11.040 --> 0:39:14.360
<v Speaker 1>inspire some places, like the state of California, to draft

0:39:14.480 --> 0:39:17.719
<v Speaker 1>privacy acts that essentially use g DPR as the basis

0:39:17.800 --> 0:39:22.279
<v Speaker 1>for that law. There are some exemptions to g d

0:39:22.440 --> 0:39:26.080
<v Speaker 1>p R, though, for example, law enforcement is not required

0:39:26.120 --> 0:39:30.080
<v Speaker 1>to abide by g DPR, and in matters of national security,

0:39:30.200 --> 0:39:33.960
<v Speaker 1>g DPR does not apply. G DPR has also changed

0:39:34.000 --> 0:39:37.120
<v Speaker 1>a bit since passing. Originally, there was this concept called

0:39:37.120 --> 0:39:40.680
<v Speaker 1>the right to be forgotten, which generally meant that an

0:39:40.719 --> 0:39:43.399
<v Speaker 1>EU citizen would have the right to request that their

0:39:43.440 --> 0:39:48.000
<v Speaker 1>personal information be deleted from any online sources, including stuff

0:39:48.040 --> 0:39:51.600
<v Speaker 1>like online search engines. But critics pointed out that this

0:39:51.640 --> 0:39:54.759
<v Speaker 1>policy was flawed. So let's say that we've got a

0:39:54.760 --> 0:39:59.000
<v Speaker 1>case where a public figure does something truly terrible, newsworthy

0:39:59.080 --> 0:40:03.759
<v Speaker 1>and terrible, like they've committed a crime of some sort. Uh,

0:40:04.560 --> 0:40:08.800
<v Speaker 1>if that person were to then follow this this process,

0:40:08.840 --> 0:40:12.359
<v Speaker 1>they might be able to demand that all mention of

0:40:12.400 --> 0:40:15.360
<v Speaker 1>that crime get a race from the internet, which you

0:40:15.360 --> 0:40:18.640
<v Speaker 1>could argue as against the public good. So these days,

0:40:18.840 --> 0:40:22.279
<v Speaker 1>the right to be forgotten is now known as the

0:40:22.400 --> 0:40:26.280
<v Speaker 1>right of a racer. And uh, it's not the band

0:40:26.320 --> 0:40:29.480
<v Speaker 1>eraser I tried to discover a little something to make

0:40:29.560 --> 0:40:34.319
<v Speaker 1>me sweeter. No, it's a it's it's a process that's

0:40:34.320 --> 0:40:37.200
<v Speaker 1>a little more limited. It cannot go nearly as far

0:40:37.280 --> 0:40:40.360
<v Speaker 1>as the right to be forgotten. And uh, it includes

0:40:40.400 --> 0:40:43.880
<v Speaker 1>stuff like you have to put in the request of

0:40:43.920 --> 0:40:46.880
<v Speaker 1>a ratier within a certain amount of time from publication

0:40:46.960 --> 0:40:50.920
<v Speaker 1>or else you missed the boat. Also, there's the consideration

0:40:50.960 --> 0:40:54.400
<v Speaker 1>about whether or not removing the information would represent a

0:40:54.400 --> 0:40:56.600
<v Speaker 1>public harm, or if it would be more harmful to

0:40:56.680 --> 0:41:00.200
<v Speaker 1>the individual if that information were to remain up. There

0:41:00.200 --> 0:41:02.520
<v Speaker 1>are a lot of different parts to it. In other words,

0:41:03.840 --> 0:41:07.520
<v Speaker 1>next up is Gift, and this is one of our

0:41:07.560 --> 0:41:11.879
<v Speaker 1>more contentious entries on this list. So obviously I still

0:41:11.920 --> 0:41:16.640
<v Speaker 1>pronounce g I F as GIF. I do not pronounce

0:41:16.719 --> 0:41:22.360
<v Speaker 1>it as jeff. The initialism stands for Graphics Interchange Format

0:41:22.800 --> 0:41:26.640
<v Speaker 1>and it's a subtype of bitmap image formats. The online

0:41:26.640 --> 0:41:30.759
<v Speaker 1>service provider compu Serve developed the GIFT file format in

0:41:30.800 --> 0:41:34.680
<v Speaker 1>the nineteen eighties, led by developer Steve will Hit. Now

0:41:34.719 --> 0:41:39.680
<v Speaker 1>Steve Wilhit pronounces it Jeff and that therefore he's wrong,

0:41:40.239 --> 0:41:43.760
<v Speaker 1>which I'm joking. I'm not. He's not really wrong. In fact,

0:41:44.200 --> 0:41:48.080
<v Speaker 1>the various dictionaries say that both pronunciations are acceptable, but

0:41:48.520 --> 0:41:54.480
<v Speaker 1>I mean, come on. The G stands for graphic, not giraffic. Anyway,

0:41:54.719 --> 0:41:57.200
<v Speaker 1>will Heights team was looking for a way to create

0:41:57.239 --> 0:41:59.920
<v Speaker 1>image files that didn't take up an enormous amount of

0:42:00.040 --> 0:42:03.759
<v Speaker 1>file space. So this was before the Worldwide Web, but

0:42:03.840 --> 0:42:08.080
<v Speaker 1>people were using online service providers and bulletin boards and

0:42:08.200 --> 0:42:11.360
<v Speaker 1>they wanted a way of being able to share images

0:42:11.600 --> 0:42:15.319
<v Speaker 1>or to download images, and the Gift team created a

0:42:15.360 --> 0:42:19.279
<v Speaker 1>format that limited color selection to two fifty six colors,

0:42:19.320 --> 0:42:22.120
<v Speaker 1>which helped keep file sizes down, and they used a

0:42:22.120 --> 0:42:25.279
<v Speaker 1>compression algorithm to kind of squitch these file sizes down,

0:42:25.640 --> 0:42:29.440
<v Speaker 1>and the gift was born. The compression algorithm identifies repeating

0:42:29.480 --> 0:42:32.600
<v Speaker 1>patterns within an image and then takes those patterns and

0:42:32.640 --> 0:42:36.160
<v Speaker 1>simplifies them for the purposes of expressing them within the file.

0:42:36.719 --> 0:42:39.080
<v Speaker 1>So this means that let's say you've got an image

0:42:39.120 --> 0:42:41.240
<v Speaker 1>that has a lot of, you know, a particular shade

0:42:41.239 --> 0:42:45.160
<v Speaker 1>of blue in one section, the file can essentially say, hey,

0:42:45.200 --> 0:42:48.560
<v Speaker 1>over here, in this part defined by these parameters, all

0:42:48.600 --> 0:42:51.319
<v Speaker 1>of that is just blue, rather than laying out that

0:42:51.520 --> 0:42:55.440
<v Speaker 1>each blue pixel is individually in each position. Now I

0:42:55.520 --> 0:42:58.880
<v Speaker 1>am oversimplifying here, but that from a high level is

0:42:58.960 --> 0:43:01.840
<v Speaker 1>kind of what was going on on. By stringing together

0:43:01.920 --> 0:43:05.279
<v Speaker 1>a sequence of gifts, it's possible to have them play

0:43:05.280 --> 0:43:08.120
<v Speaker 1>in a loop, and thus we get the animated gift.

0:43:08.560 --> 0:43:10.799
<v Speaker 1>Though many of the animated gifts we see today are

0:43:10.840 --> 0:43:14.080
<v Speaker 1>actually small video files that just kind of you know,

0:43:14.120 --> 0:43:17.000
<v Speaker 1>they use code to make them behave in a way

0:43:17.040 --> 0:43:20.400
<v Speaker 1>that we think of as animated gifts. But it turns

0:43:20.400 --> 0:43:25.480
<v Speaker 1>out that the video coding technology has actually outpaced gift code,

0:43:26.000 --> 0:43:28.920
<v Speaker 1>so we tend to see small video files rather than

0:43:28.960 --> 0:43:33.000
<v Speaker 1>actual gifts. However, the gift name has stuck around, even

0:43:33.000 --> 0:43:37.160
<v Speaker 1>though it's not necessarily a gift file extension. Next up

0:43:37.280 --> 0:43:41.799
<v Speaker 1>is GPS. This stands for Global Positioning System. Often we

0:43:41.880 --> 0:43:44.520
<v Speaker 1>refer to a device, like, you know, something that we

0:43:45.080 --> 0:43:48.400
<v Speaker 1>use in a car, as a GPS, by which we

0:43:48.440 --> 0:43:52.400
<v Speaker 1>mean a navigational device that relies upon this Global positioning

0:43:52.440 --> 0:43:56.480
<v Speaker 1>system to calculate that devices position relative to the surface

0:43:56.480 --> 0:43:59.000
<v Speaker 1>of the Earth. That's a wordy way of saying that

0:43:59.200 --> 0:44:02.319
<v Speaker 1>the devices using information from satellites to figure out where

0:44:02.360 --> 0:44:05.239
<v Speaker 1>the heck it is. Back in the nineteen seventies, the

0:44:05.239 --> 0:44:08.120
<v Speaker 1>Department of Defense in the United States began working on

0:44:08.160 --> 0:44:11.400
<v Speaker 1>what would become the GPS, and it would take a

0:44:11.400 --> 0:44:14.560
<v Speaker 1>couple of decades to complete it. But by the early

0:44:14.640 --> 0:44:18.400
<v Speaker 1>nineteen nineties, the full complement of twenty four satellites that

0:44:18.440 --> 0:44:22.360
<v Speaker 1>were part of this original plan were up in orbit,

0:44:22.560 --> 0:44:25.760
<v Speaker 1>and they were needed so that you could get global

0:44:25.840 --> 0:44:29.360
<v Speaker 1>coverage for GPS. Otherwise, before that, you know, coverage was

0:44:29.400 --> 0:44:32.880
<v Speaker 1>sporadic based upon whether or not you had the appropriate

0:44:32.960 --> 0:44:37.200
<v Speaker 1>number of satellites within range of you in orbit. Now

0:44:37.200 --> 0:44:40.120
<v Speaker 1>these satellites are not in geosynchronous orbit with the Earth,

0:44:40.280 --> 0:44:43.720
<v Speaker 1>so in other words, they're not remaining in a fixed

0:44:43.760 --> 0:44:47.319
<v Speaker 1>position relative to a point on the Earth's surface, so

0:44:47.560 --> 0:44:50.160
<v Speaker 1>they are in an orbit that's at a different rate

0:44:50.239 --> 0:44:55.640
<v Speaker 1>than the Earth's rotation, also a different trajectory than Earth's rotation,

0:44:56.480 --> 0:44:59.680
<v Speaker 1>and that's why you need to have multiple satellites, like

0:44:59.680 --> 0:45:03.359
<v Speaker 1>twenty four of them to maintain constant coverage, because satellites

0:45:03.360 --> 0:45:06.960
<v Speaker 1>pass out of range at certain points and other satellites

0:45:06.960 --> 0:45:10.000
<v Speaker 1>will come into range. That's why you need that many

0:45:10.120 --> 0:45:14.080
<v Speaker 1>up there. The satellites send out signals that receivers on Earth,

0:45:14.239 --> 0:45:16.799
<v Speaker 1>like the one in your car can pick up, or

0:45:16.840 --> 0:45:19.279
<v Speaker 1>the one on your phone for that matter, And each

0:45:19.400 --> 0:45:22.759
<v Speaker 1>signal sent by a satellite contains some information that it's

0:45:22.760 --> 0:45:25.440
<v Speaker 1>really important. One of it those pieces of information is

0:45:25.440 --> 0:45:29.680
<v Speaker 1>a precise time stamp that says exactly when the satellite

0:45:29.719 --> 0:45:32.840
<v Speaker 1>broadcast that that signal, and also there's some data that

0:45:32.880 --> 0:45:38.160
<v Speaker 1>indicates that particular satellites orbital location. So the receiver has

0:45:38.200 --> 0:45:40.920
<v Speaker 1>to pick up signals from at least three satellites to

0:45:40.960 --> 0:45:45.279
<v Speaker 1>get a physical location. Because of the time stamp, the

0:45:45.320 --> 0:45:49.320
<v Speaker 1>receiver quote unquote knows how long that signal had traveled

0:45:49.800 --> 0:45:52.640
<v Speaker 1>from the satellite to the receiver. The receiver has to

0:45:52.719 --> 0:45:56.440
<v Speaker 1>compare this against its own time reading, typically from an

0:45:56.440 --> 0:45:59.480
<v Speaker 1>atomic clock. But more on that in the second Now,

0:45:59.480 --> 0:46:02.480
<v Speaker 1>this means that the receiver knows how far away it

0:46:02.719 --> 0:46:06.600
<v Speaker 1>is from the satellite, because the satellite communication travels at

0:46:06.640 --> 0:46:09.520
<v Speaker 1>the speed of light. So you just take the amount

0:46:09.520 --> 0:46:11.480
<v Speaker 1>of time it took for the signal to go from

0:46:11.560 --> 0:46:13.680
<v Speaker 1>when it was broadcast to when it was picked up

0:46:13.680 --> 0:46:16.640
<v Speaker 1>by the receiver, and you use that to figure out

0:46:16.680 --> 0:46:19.520
<v Speaker 1>how many miles it traveled in that span of time

0:46:19.520 --> 0:46:21.920
<v Speaker 1>because it was traveling at the speed of light. So

0:46:22.040 --> 0:46:24.880
<v Speaker 1>then you could draw a sphere around the satellite, like

0:46:24.920 --> 0:46:28.319
<v Speaker 1>a virtual sphere, that represents all the points that are

0:46:28.480 --> 0:46:32.319
<v Speaker 1>that distance away from the satellite in every single direction. Now,

0:46:32.360 --> 0:46:35.319
<v Speaker 1>granted you're only interested in the points that make an

0:46:35.360 --> 0:46:37.680
<v Speaker 1>intersection with the Earth, but there will be a lot

0:46:37.719 --> 0:46:41.560
<v Speaker 1>of those. So then you want to compare that with

0:46:41.680 --> 0:46:44.759
<v Speaker 1>other satellites. You need at least three, and then you're

0:46:44.800 --> 0:46:49.680
<v Speaker 1>looking at the intersection of where these different spheres meet,

0:46:50.480 --> 0:46:53.520
<v Speaker 1>and with three satellites you get two points where the

0:46:53.560 --> 0:46:57.200
<v Speaker 1>spheres will all intersect. One of those two points will

0:46:57.280 --> 0:47:00.399
<v Speaker 1>definitely be on the surface of Earth. The other one

0:47:00.520 --> 0:47:03.759
<v Speaker 1>may or may not be. So, then by looking at

0:47:03.760 --> 0:47:05.439
<v Speaker 1>the point that's actually on the surface of the Earth,

0:47:05.520 --> 0:47:07.960
<v Speaker 1>the receiver says, Okay, now I know where I am

0:47:08.040 --> 0:47:11.320
<v Speaker 1>because I'm able to tell by the distance I am

0:47:11.400 --> 0:47:16.000
<v Speaker 1>from these three different satellites. It's really really neat um.

0:47:16.040 --> 0:47:20.600
<v Speaker 1>It's it's kind of similar to um triangulation, but not

0:47:20.719 --> 0:47:25.240
<v Speaker 1>exactly the same. Anyway, with four satellites, you can actually

0:47:25.239 --> 0:47:27.319
<v Speaker 1>eliminate the need for the receiver to have access to

0:47:27.360 --> 0:47:30.560
<v Speaker 1>its own atomic clock to make certain to correct for errors.

0:47:31.160 --> 0:47:33.520
<v Speaker 1>And there's a lot more to it than that. For example,

0:47:33.680 --> 0:47:37.319
<v Speaker 1>until the nineteen nineties, within the US, civilian use of

0:47:37.360 --> 0:47:41.439
<v Speaker 1>GPS was really limited because GPS was meant for military use,

0:47:41.880 --> 0:47:47.120
<v Speaker 1>so civilian receivers they existed, but they also purposefully introduced

0:47:47.239 --> 0:47:51.840
<v Speaker 1>errors into the display, so you could not use a

0:47:51.880 --> 0:47:54.520
<v Speaker 1>GPS to get a specific reading of your location. You

0:47:54.520 --> 0:47:57.440
<v Speaker 1>can get kind of a general reading, so you wouldn't

0:47:57.440 --> 0:47:59.480
<v Speaker 1>be able to use it to do stuff like make

0:47:59.600 --> 0:48:03.120
<v Speaker 1>turn I turned directions in real time because your receiver's

0:48:03.120 --> 0:48:07.359
<v Speaker 1>location readoubt could be off by several hundred feet, so

0:48:07.480 --> 0:48:10.879
<v Speaker 1>it could be like turn left, you're gonna turn left

0:48:10.920 --> 0:48:13.000
<v Speaker 1>either in a hundred feet or it might be three

0:48:13.320 --> 0:48:17.760
<v Speaker 1>feet behind you, so not very useful. But then later

0:48:17.800 --> 0:48:21.480
<v Speaker 1>on President Clinton lifted that restriction, and since then we've

0:48:21.520 --> 0:48:23.799
<v Speaker 1>been able to use GPS receivers to help us get

0:48:23.800 --> 0:48:26.319
<v Speaker 1>to where we're going. Or you know, if you're using

0:48:26.360 --> 0:48:29.080
<v Speaker 1>Apple Maps, you can use it to drive into a river.

0:48:29.800 --> 0:48:33.320
<v Speaker 1>I'm kidding. I'm just using a very outdated joke about

0:48:33.360 --> 0:48:38.000
<v Speaker 1>the reliability of Apple Maps, which obviously has improved significantly

0:48:38.200 --> 0:48:40.759
<v Speaker 1>since it first launched, so it's an unfair joke for

0:48:40.800 --> 0:48:43.960
<v Speaker 1>me to make. These days, there are more than thirty

0:48:44.000 --> 0:48:47.280
<v Speaker 1>five GPS satellites out in orbit, and the technology also

0:48:47.400 --> 0:48:50.240
<v Speaker 1>is a great way to explore the concepts of general

0:48:50.280 --> 0:48:54.000
<v Speaker 1>and special relativity, because you have to have an understanding

0:48:54.040 --> 0:48:56.520
<v Speaker 1>of both of those things in order to correct for

0:48:56.600 --> 0:49:00.239
<v Speaker 1>the issues of time dilation. But that's a complicate, aided

0:49:00.280 --> 0:49:02.839
<v Speaker 1>subject for another time. In fact, I have covered that

0:49:03.280 --> 0:49:06.160
<v Speaker 1>in past episodes, so check that out if you want

0:49:06.160 --> 0:49:10.759
<v Speaker 1>to learn how it is that GPS proves that Einstein

0:49:10.880 --> 0:49:14.960
<v Speaker 1>was right. It's pretty fascinating stuff, all right, And that's

0:49:15.000 --> 0:49:17.759
<v Speaker 1>it for this episode. We're gonna leave off here. We're

0:49:17.760 --> 0:49:20.960
<v Speaker 1>gonna pick back up in our next one to continue

0:49:21.000 --> 0:49:24.160
<v Speaker 1>our glossary that will be next week, starting on Monday,

0:49:24.320 --> 0:49:26.560
<v Speaker 1>and we'll continue to work our way through these various

0:49:26.600 --> 0:49:30.959
<v Speaker 1>acronyms and initialisms to kind of demystify the world of tech,

0:49:31.160 --> 0:49:34.760
<v Speaker 1>which gets very reliant on jargon and acronyms and stuff

0:49:35.120 --> 0:49:36.640
<v Speaker 1>to the point where it can feel kind of like

0:49:36.680 --> 0:49:39.319
<v Speaker 1>it's excluding others on purpose. And I don't dig that.

0:49:39.680 --> 0:49:42.160
<v Speaker 1>I like to be inclusive, so we're gonna keep on going.

0:49:42.640 --> 0:49:44.759
<v Speaker 1>In the meantime, if you have suggestions for topics I

0:49:44.760 --> 0:49:47.359
<v Speaker 1>should cover in future episodes of tech Stuff, reach out

0:49:47.400 --> 0:49:49.200
<v Speaker 1>to me. The best way to do that is on Twitter.

0:49:49.440 --> 0:49:53.000
<v Speaker 1>The handle we use is tech Stuff hs W and

0:49:53.040 --> 0:50:01.840
<v Speaker 1>I'll talk to you again really soon. Text Stuff is

0:50:01.880 --> 0:50:05.040
<v Speaker 1>an I Heart Radio production. For more podcasts from I

0:50:05.160 --> 0:50:08.759
<v Speaker 1>Heart Radio, visit the i Heart Radio app, Apple Podcasts,

0:50:08.880 --> 0:50:10.840
<v Speaker 1>or wherever you listen to your favorite shows.