WEBVTT - Tech Glossary: From ISDN to P2P

0:00:04.400 --> 0:00:07.800
<v Speaker 1>Welcome to Tech Stuff, a production from my Heart Radio.

0:00:12.200 --> 0:00:15.120
<v Speaker 1>Hey there, and welcome to tech Stuff. I'm your host,

0:00:15.280 --> 0:00:18.920
<v Speaker 1>Jonathan Strickland. I'm an executive producer with I Heart Radio

0:00:18.960 --> 0:00:21.439
<v Speaker 1>and I love of all things tech. And we are

0:00:21.600 --> 0:00:25.560
<v Speaker 1>back on the tech glossary topic, in which we look

0:00:25.600 --> 0:00:29.200
<v Speaker 1>at the various initialisms and acronyms used in the tech

0:00:29.280 --> 0:00:32.400
<v Speaker 1>world and figure out what they actually mean. In the

0:00:32.479 --> 0:00:35.800
<v Speaker 1>last episode, we worked up to I r C or

0:00:35.920 --> 0:00:39.520
<v Speaker 1>Internet Relay Chat. I made a joke that I can

0:00:39.920 --> 0:00:42.559
<v Speaker 1>get through all the eyes in that episode because I

0:00:42.680 --> 0:00:46.200
<v Speaker 1>can stands for Internet Corporation for assigned names and numbers.

0:00:46.240 --> 0:00:48.880
<v Speaker 1>But I actually have a few more eyes to cover

0:00:49.000 --> 0:00:51.279
<v Speaker 1>before we move on, So I made a liar out

0:00:51.280 --> 0:00:54.120
<v Speaker 1>of myself. Let's do it, and we're gonna start with

0:00:54.560 --> 0:01:00.400
<v Speaker 1>I S d N that stands for Integrated Services Digital Network.

0:01:00.720 --> 0:01:04.080
<v Speaker 1>This requires a bit of a backstory. So way back

0:01:04.120 --> 0:01:08.200
<v Speaker 1>in the day, we only had what's called the plane

0:01:08.200 --> 0:01:12.160
<v Speaker 1>old telephone service or pots POTS, So that's kind of

0:01:12.200 --> 0:01:15.840
<v Speaker 1>a bonus acronym right there, and actually we still do

0:01:16.000 --> 0:01:18.480
<v Speaker 1>have that in some regard. But let's get back to

0:01:18.520 --> 0:01:22.480
<v Speaker 1>business here. Back before the nineteen sixties, all the telephone

0:01:22.480 --> 0:01:28.680
<v Speaker 1>connections depended upon actual interconnected physical wires and mechanical systems

0:01:28.800 --> 0:01:34.800
<v Speaker 1>and analog signals. So as more lines were joining the system,

0:01:34.840 --> 0:01:38.080
<v Speaker 1>and again these were analog signals passed over twisted pair

0:01:38.240 --> 0:01:43.080
<v Speaker 1>cables of wire, it became increasingly messy. Right as more

0:01:43.120 --> 0:01:47.200
<v Speaker 1>people and companies and places started to add phone lines,

0:01:47.280 --> 0:01:49.640
<v Speaker 1>it started to get to be a real mess and

0:01:49.680 --> 0:01:53.440
<v Speaker 1>analog systems were not great at supplying reliable long distance

0:01:53.480 --> 0:01:59.240
<v Speaker 1>communications service where you had to interconnect between different regional networks.

0:01:59.320 --> 0:02:02.800
<v Speaker 1>Around the nineteen fifties, the telephone companies began to work

0:02:02.840 --> 0:02:07.520
<v Speaker 1>on automating various systems and one potential solution, the one

0:02:07.560 --> 0:02:10.000
<v Speaker 1>that turned out to be the winner, was to migrate

0:02:10.080 --> 0:02:13.840
<v Speaker 1>from a purely analog telephone system to a voiceover digital

0:02:14.000 --> 0:02:18.040
<v Speaker 1>line system. Now that digital system also allowed for the

0:02:18.080 --> 0:02:22.800
<v Speaker 1>transmission of digital data, not just you know, voice, but

0:02:23.200 --> 0:02:26.200
<v Speaker 1>other types of information, and in the late nineteen eighties,

0:02:26.240 --> 0:02:29.520
<v Speaker 1>a part of the United Nations called the International Telecommunications

0:02:29.639 --> 0:02:34.200
<v Speaker 1>Union or i t U, another bonus initialism, began to

0:02:34.400 --> 0:02:38.000
<v Speaker 1>recommend the I s d N standard for data transmission

0:02:38.000 --> 0:02:42.920
<v Speaker 1>over phone lines. But there were actually two competing versions

0:02:43.080 --> 0:02:46.000
<v Speaker 1>of I S d N. There was not a standardized

0:02:46.080 --> 0:02:49.240
<v Speaker 1>version at first, that caused a lot of delays as

0:02:49.280 --> 0:02:52.760
<v Speaker 1>far as implementation and roll out, until a unified standard

0:02:52.760 --> 0:02:55.960
<v Speaker 1>emerged in the nineteen nineties, so I s d N

0:02:56.040 --> 0:02:58.519
<v Speaker 1>finally kind of entered the scene and allowed for faster

0:02:58.720 --> 0:03:03.600
<v Speaker 1>data transmission speeds or more accurately, greater data throughput. More

0:03:03.639 --> 0:03:06.400
<v Speaker 1>on that in a little bit, But before too long,

0:03:06.680 --> 0:03:10.520
<v Speaker 1>other technologies like DSL and cable modems would replace I

0:03:10.760 --> 0:03:13.040
<v Speaker 1>s d N. Now you still find I s d

0:03:13.240 --> 0:03:16.080
<v Speaker 1>N in some places, and I should probably do a

0:03:16.120 --> 0:03:18.480
<v Speaker 1>full episode about it in the future to really talk

0:03:18.520 --> 0:03:24.160
<v Speaker 1>about its development, its history, and its implementation. But these

0:03:24.160 --> 0:03:27.359
<v Speaker 1>episodes are already going far beyond what I expected, so

0:03:27.520 --> 0:03:31.040
<v Speaker 1>I will spare you. Let's move on. I SP This

0:03:31.120 --> 0:03:34.000
<v Speaker 1>is an easy one. It stands for Internet service provider.

0:03:34.360 --> 0:03:38.600
<v Speaker 1>These are the companies that provide Internet connectivity services to customers.

0:03:38.880 --> 0:03:41.600
<v Speaker 1>Those customers might be people, and they might be businesses

0:03:41.680 --> 0:03:45.520
<v Speaker 1>or other organizations or very organized people. I guess some

0:03:45.680 --> 0:03:49.680
<v Speaker 1>I s p s also offer other services, uh, usually

0:03:49.720 --> 0:03:53.800
<v Speaker 1>directly connected to Internet services, and uh, you know, some

0:03:53.920 --> 0:03:57.520
<v Speaker 1>other I s p s end up offering services that

0:03:57.560 --> 0:04:01.320
<v Speaker 1>are related to telecommunications. So, for example, there are I

0:04:01.520 --> 0:04:03.640
<v Speaker 1>s P s that might say, all right, well, if

0:04:03.680 --> 0:04:06.840
<v Speaker 1>you purchase service from us, not only will you have

0:04:06.960 --> 0:04:11.720
<v Speaker 1>Internet connectivity, will also give you an email address, we

0:04:12.120 --> 0:04:15.880
<v Speaker 1>will host a personal website for you. We might have

0:04:15.960 --> 0:04:18.960
<v Speaker 1>other software that you have access to. And then you've

0:04:19.000 --> 0:04:21.599
<v Speaker 1>got you know, things like cable companies that are also

0:04:21.760 --> 0:04:24.960
<v Speaker 1>I s p s, and they'll bundle Internet service with

0:04:25.040 --> 0:04:27.800
<v Speaker 1>cable TV or telephone service. You get the idea. It's

0:04:27.839 --> 0:04:31.800
<v Speaker 1>pretty common thing now. Back in the nineteen nineties, there

0:04:31.800 --> 0:04:34.680
<v Speaker 1>were around ten thousand I s p s in the world,

0:04:34.800 --> 0:04:37.119
<v Speaker 1>with the United States laying claim to more than half

0:04:37.160 --> 0:04:39.760
<v Speaker 1>of them. And if you've listened to my episodes on

0:04:39.800 --> 0:04:42.719
<v Speaker 1>earth Link, you heard me talk about one of those

0:04:42.760 --> 0:04:44.760
<v Speaker 1>I s p s. And these I s p s

0:04:44.800 --> 0:04:48.080
<v Speaker 1>frequently focused on specific regions, and hey, you know, the

0:04:48.080 --> 0:04:50.960
<v Speaker 1>Internet is a global thing. So these companies were relying

0:04:51.000 --> 0:04:55.640
<v Speaker 1>on bigger telecommunications companies to actually connect various you know,

0:04:55.839 --> 0:05:01.120
<v Speaker 1>computers together on the Internet. But telecommunications companies like telephone

0:05:01.120 --> 0:05:05.640
<v Speaker 1>companies and cable companies already had this infrastructure in place

0:05:06.080 --> 0:05:10.919
<v Speaker 1>to deliver services to customers that could easily be converted

0:05:11.000 --> 0:05:14.560
<v Speaker 1>over or added onto with the Internet speeds, so you

0:05:14.600 --> 0:05:18.080
<v Speaker 1>could have Internet be there in addition to the other

0:05:18.120 --> 0:05:22.039
<v Speaker 1>services you provided, and these regional I sp s just

0:05:22.040 --> 0:05:25.320
<v Speaker 1>couldn't match that, right, They just didn't have that that

0:05:25.400 --> 0:05:28.960
<v Speaker 1>kind of infrastructure. And so there are still regional I

0:05:29.200 --> 0:05:31.599
<v Speaker 1>s p s. They do exist, but they essentially sit

0:05:31.720 --> 0:05:36.560
<v Speaker 1>on top of these other larger telecommunication company I s

0:05:36.600 --> 0:05:39.000
<v Speaker 1>p s. And I bring this up because there may

0:05:39.040 --> 0:05:41.279
<v Speaker 1>be cases in the United States and which it looks

0:05:41.320 --> 0:05:44.200
<v Speaker 1>like you might have multiple I s P options in

0:05:44.240 --> 0:05:48.400
<v Speaker 1>your area, but it's probably that all of the smaller

0:05:48.440 --> 0:05:52.080
<v Speaker 1>ones are just piggybacking on the infrastructure of the big one.

0:05:53.040 --> 0:05:57.520
<v Speaker 1>So what they're doing is they're essentially leasing space, if

0:05:57.520 --> 0:05:59.560
<v Speaker 1>you want to think of it that way, on the

0:05:59.640 --> 0:06:06.599
<v Speaker 1>tele communication companies technology, and then they resell that to customers. Now,

0:06:06.640 --> 0:06:09.280
<v Speaker 1>the price that these regional I s p s get

0:06:09.839 --> 0:06:11.960
<v Speaker 1>isn't the same price that you would pay to have

0:06:12.040 --> 0:06:15.000
<v Speaker 1>Internet access. However, you might be paying more with the

0:06:15.040 --> 0:06:17.280
<v Speaker 1>regional I s P and they might try and make

0:06:17.320 --> 0:06:20.320
<v Speaker 1>it up make up for it with additional services like

0:06:20.360 --> 0:06:24.360
<v Speaker 1>those software packages I was talking about earlier. Okay, let's

0:06:24.360 --> 0:06:30.080
<v Speaker 1>move on I T. Okay. I included I T because

0:06:30.160 --> 0:06:33.159
<v Speaker 1>Jen Barber didn't know what it meant. And it means

0:06:33.240 --> 0:06:38.920
<v Speaker 1>information technology jen. The term originates from the late nineteen seventies,

0:06:38.960 --> 0:06:43.040
<v Speaker 1>which coincidentally marks the earliest days of the first personal computers,

0:06:43.520 --> 0:06:47.279
<v Speaker 1>and Miriam Webster defines it as quote the technology involving

0:06:47.279 --> 0:06:51.120
<v Speaker 1>the development, maintenance, and use of computer systems, software, and

0:06:51.200 --> 0:06:55.120
<v Speaker 1>networks for the processing and distribution of data end quote.

0:06:55.440 --> 0:06:58.559
<v Speaker 1>And that definition is a pretty broad one, and made

0:06:58.600 --> 0:07:02.920
<v Speaker 1>even larger with the era of big data, which necessitates

0:07:03.080 --> 0:07:07.320
<v Speaker 1>more robust networks and more sophisticated methods of data analysis.

0:07:07.640 --> 0:07:11.720
<v Speaker 1>And today we typically associate i T with networks in

0:07:11.760 --> 0:07:14.960
<v Speaker 1>general and the Internet in particular, but clearly the term

0:07:15.000 --> 0:07:19.240
<v Speaker 1>can apply to all sorts of computer systems. Okay, we're

0:07:19.360 --> 0:07:23.400
<v Speaker 1>killing it, let's keep moving. JPEG This stands for Joint

0:07:23.640 --> 0:07:28.600
<v Speaker 1>Photographic Experts Group, a joint committee that forms specifically for

0:07:28.640 --> 0:07:33.160
<v Speaker 1>the purposes of establishing standards for the coding of still pictures.

0:07:33.640 --> 0:07:37.520
<v Speaker 1>But when we use JPEG, we usually mean the file

0:07:37.600 --> 0:07:41.600
<v Speaker 1>format that this group created, not the group itself, So

0:07:41.640 --> 0:07:46.480
<v Speaker 1>we mean JPEG or JPG as a file extension of

0:07:46.520 --> 0:07:51.720
<v Speaker 1>file type. So the JPEG file format is an image file. Specifically,

0:07:51.760 --> 0:07:56.280
<v Speaker 1>it's a lossy compression file format, which means it's a

0:07:56.280 --> 0:08:00.440
<v Speaker 1>way to code still images, but you manage file size

0:08:00.560 --> 0:08:03.960
<v Speaker 1>by losing some of the data associated with that file.

0:08:04.280 --> 0:08:06.400
<v Speaker 1>Like a raw image file. If you were to take,

0:08:06.840 --> 0:08:09.600
<v Speaker 1>you know, a really nice digital camera and take a

0:08:09.640 --> 0:08:13.160
<v Speaker 1>photo of it, a raw image file is really really big,

0:08:13.720 --> 0:08:17.280
<v Speaker 1>and that could be a bit of a problem. With JPEG.

0:08:17.440 --> 0:08:19.280
<v Speaker 1>You compress that down, but you lose some of the

0:08:19.320 --> 0:08:23.120
<v Speaker 1>information in the process, and the higher the compression you choose,

0:08:23.440 --> 0:08:26.040
<v Speaker 1>the more data you have to lose in the process,

0:08:26.120 --> 0:08:29.240
<v Speaker 1>and as a result, the image will not look as good.

0:08:29.280 --> 0:08:32.000
<v Speaker 1>The more you compress it, the worst the image is

0:08:32.040 --> 0:08:35.320
<v Speaker 1>going to look, but the smaller the file size. There

0:08:35.440 --> 0:08:38.360
<v Speaker 1>was a need for this kind of file type because

0:08:38.400 --> 0:08:42.720
<v Speaker 1>the Internet in general, and the Web in particular, really

0:08:43.160 --> 0:08:45.240
<v Speaker 1>needed that in order to take off. Most of the

0:08:45.280 --> 0:08:48.080
<v Speaker 1>world was dependent upon dial up speeds in the early

0:08:48.160 --> 0:08:51.520
<v Speaker 1>days of the Web, and dial up speeds were not

0:08:51.800 --> 0:08:54.840
<v Speaker 1>terribly fast. Anyone who used a dial up modem to

0:08:54.920 --> 0:08:57.520
<v Speaker 1>log into say a bulletin board system back in the

0:08:57.640 --> 0:09:03.960
<v Speaker 1>nineteen eighties, before really the the dawn of the consumer Internet,

0:09:04.679 --> 0:09:09.720
<v Speaker 1>they know that it could take forever to download an image,

0:09:10.320 --> 0:09:12.840
<v Speaker 1>and by forever, I just mean like a crazy long

0:09:12.880 --> 0:09:16.800
<v Speaker 1>amount of time. But these compression formats like JPEG meant

0:09:16.840 --> 0:09:20.520
<v Speaker 1>that you could get images with smaller file sizes, which

0:09:20.559 --> 0:09:24.360
<v Speaker 1>meant faster download times for those files. This was also

0:09:24.440 --> 0:09:28.280
<v Speaker 1>important for stuff like email, which frequently has pretty strict

0:09:28.320 --> 0:09:30.840
<v Speaker 1>limits on how large a message can be before you

0:09:30.840 --> 0:09:32.480
<v Speaker 1>can send it out, like if it goes over that

0:09:32.920 --> 0:09:36.920
<v Speaker 1>you get that little annoying message saying you've exceeded the

0:09:36.920 --> 0:09:40.800
<v Speaker 1>the size allowed for sending out an email. The JPEG

0:09:40.840 --> 0:09:44.120
<v Speaker 1>standard took off like gangbusters and was a big part

0:09:44.160 --> 0:09:46.880
<v Speaker 1>of why the web itself was able to take off.

0:09:47.320 --> 0:09:50.559
<v Speaker 1>It allowed for an experience that incorporated more images, and

0:09:50.600 --> 0:09:54.400
<v Speaker 1>the committee introduced other JPEG standards later on, but the

0:09:54.400 --> 0:09:58.199
<v Speaker 1>original JPEG format was so popular that the subsequent standards

0:09:58.840 --> 0:10:01.800
<v Speaker 1>didn't really get much action, even though they had, you know,

0:10:01.920 --> 0:10:07.160
<v Speaker 1>arguably superior compression algorithms. Moving on, now we have a

0:10:07.160 --> 0:10:10.480
<v Speaker 1>trio here, and really it's just a an indication of

0:10:10.559 --> 0:10:15.640
<v Speaker 1>a whole series of things, which is kbps, mbps, and

0:10:15.760 --> 0:10:20.920
<v Speaker 1>g bps. These all referenced data throughput. Kbps is kill

0:10:20.960 --> 0:10:24.240
<v Speaker 1>a bits per second or thousands of bits per second,

0:10:24.880 --> 0:10:29.480
<v Speaker 1>mbps is megabits per second or millions of bits per second,

0:10:29.840 --> 0:10:34.000
<v Speaker 1>and g bps is gigabits per second or billions of

0:10:34.080 --> 0:10:37.280
<v Speaker 1>bits per second, and a bit is a single unit

0:10:37.440 --> 0:10:41.400
<v Speaker 1>of binary information. It's either a zero or a one,

0:10:41.800 --> 0:10:43.680
<v Speaker 1>so you can think of it kind of like a

0:10:43.720 --> 0:10:48.360
<v Speaker 1>physical switch that has two positions off or on. Sometimes

0:10:48.720 --> 0:10:52.880
<v Speaker 1>people confuse a word like mega bit with the word megabyte,

0:10:53.360 --> 0:10:57.160
<v Speaker 1>but a byte is actually eight bits. To go into

0:10:57.360 --> 0:11:00.240
<v Speaker 1>why this is would actually require a pretty long story race,

0:11:00.240 --> 0:11:02.600
<v Speaker 1>so I'll save that for a different episode. But it

0:11:02.679 --> 0:11:06.400
<v Speaker 1>is good to know that megabit and megabyte are two

0:11:06.440 --> 0:11:09.880
<v Speaker 1>different things. So if you have a connection and your

0:11:09.880 --> 0:11:13.719
<v Speaker 1>connection speed is one hundred megabits per second for downloads,

0:11:13.800 --> 0:11:15.720
<v Speaker 1>and then you go to download a file that's one

0:11:15.800 --> 0:11:19.520
<v Speaker 1>hundred megabytes, you have a hundred megabits per second. That

0:11:19.559 --> 0:11:22.320
<v Speaker 1>doesn't mean that you could download a hundred megabyte file

0:11:22.480 --> 0:11:26.000
<v Speaker 1>in one second. That that's different. Also, we tend to

0:11:26.040 --> 0:11:30.880
<v Speaker 1>think of this as download speeds, Like a one hundred

0:11:30.880 --> 0:11:34.520
<v Speaker 1>megabit per second connection is a faster connection than a

0:11:34.600 --> 0:11:37.640
<v Speaker 1>one kill a bit per second connection, but it's slower

0:11:37.640 --> 0:11:40.640
<v Speaker 1>than a hundred gigabit per second, which told be phenomenal.

0:11:41.080 --> 0:11:45.319
<v Speaker 1>But the way we're describing this as kind of inaccurate.

0:11:45.320 --> 0:11:48.240
<v Speaker 1>We use it this way, because it's how we experience

0:11:48.880 --> 0:11:51.280
<v Speaker 1>this by by figuring out how long it takes us

0:11:51.280 --> 0:11:55.720
<v Speaker 1>to transfer certain amounts of information over a connection. But really,

0:11:55.760 --> 0:11:59.640
<v Speaker 1>by and large, all the data traveling across networks is

0:12:00.120 --> 0:12:03.320
<v Speaker 1>moving at the same speed. I'm kind of oversimplifying, but

0:12:03.400 --> 0:12:05.880
<v Speaker 1>largely this is true. So in other words, if I

0:12:05.880 --> 0:12:08.480
<v Speaker 1>have a connection that is just fifty six kill a

0:12:08.520 --> 0:12:12.400
<v Speaker 1>bits per second, like I'm using a dial up modem

0:12:12.440 --> 0:12:15.040
<v Speaker 1>and I'm getting fifty six kill a bits per second download,

0:12:15.840 --> 0:12:19.280
<v Speaker 1>that's fifty six thousand bits per second. But you are

0:12:19.320 --> 0:12:21.839
<v Speaker 1>on a fiber connection, you're pulling down a gigabit per

0:12:21.920 --> 0:12:25.600
<v Speaker 1>second it's or one billion bits per second. While your

0:12:25.679 --> 0:12:28.080
<v Speaker 1>connection is better than mine, you're gonna get way more

0:12:28.160 --> 0:12:31.600
<v Speaker 1>data per second than I am. The actual speed of

0:12:31.640 --> 0:12:34.679
<v Speaker 1>the data traveling across these connections is pretty much the same.

0:12:34.800 --> 0:12:38.440
<v Speaker 1>It's just that your connection allows for way more data

0:12:38.440 --> 0:12:42.120
<v Speaker 1>to travel at that speed. The mind does. This is

0:12:42.160 --> 0:12:44.920
<v Speaker 1>easier to understand with an analogy. So let's say we've

0:12:44.920 --> 0:12:48.360
<v Speaker 1>got a really big room full of people, and all

0:12:48.400 --> 0:12:51.480
<v Speaker 1>the people in this room can walk at the same

0:12:51.520 --> 0:12:54.800
<v Speaker 1>top speed, and we'll say it's just three miles that's

0:12:54.840 --> 0:12:58.560
<v Speaker 1>their top speed of walking. We've got three doorways out

0:12:58.600 --> 0:13:01.800
<v Speaker 1>of this room. One doorway is wide enough just to

0:13:01.880 --> 0:13:05.000
<v Speaker 1>let one person through at a time, Doroy number two

0:13:05.040 --> 0:13:07.080
<v Speaker 1>is wide enough to let two people out at a time,

0:13:07.360 --> 0:13:10.680
<v Speaker 1>and Doroy number three is super wide. It allows twenty

0:13:10.760 --> 0:13:14.679
<v Speaker 1>people to leave at a time, shoulder to shoulder. Now

0:13:15.360 --> 0:13:18.079
<v Speaker 1>that last doorway is going to allow way more people

0:13:18.080 --> 0:13:20.240
<v Speaker 1>to exit the room in a given amount of time

0:13:20.480 --> 0:13:23.959
<v Speaker 1>than the other two would, But all the people are

0:13:24.000 --> 0:13:26.640
<v Speaker 1>still walking at that same top speed of three miles

0:13:26.679 --> 0:13:29.200
<v Speaker 1>per hour. So when someone says they have a fast

0:13:29.240 --> 0:13:33.599
<v Speaker 1>Internet connection, you can be that person to say, well, actually,

0:13:33.960 --> 0:13:36.559
<v Speaker 1>you have an Internet connection with a high data throughput,

0:13:37.080 --> 0:13:39.600
<v Speaker 1>and then you can probably escort yourself out of the

0:13:39.640 --> 0:13:41.959
<v Speaker 1>area because no one will want to be around you.

0:13:42.200 --> 0:13:45.880
<v Speaker 1>Trust me, I know this from experience. Here in the

0:13:45.960 --> 0:13:50.200
<v Speaker 1>United States, the national benchmark for broadband speeds is twenty

0:13:50.240 --> 0:13:54.080
<v Speaker 1>five megabits per second. That's twenty five megabits per second

0:13:54.160 --> 0:13:57.480
<v Speaker 1>download speed coming from the Internet to your device. In

0:13:57.520 --> 0:14:01.559
<v Speaker 1>other words, then it's three megabit per second up that's

0:14:01.760 --> 0:14:05.000
<v Speaker 1>going from your device up to the Internet. So it's

0:14:05.600 --> 0:14:08.480
<v Speaker 1>it's not the same coming down as it is going up.

0:14:08.520 --> 0:14:12.680
<v Speaker 1>For most Internet connections, it's not, you know, symmetrical. In

0:14:12.679 --> 0:14:16.400
<v Speaker 1>other words, it's asymmetrical. Well, we got that standard for

0:14:16.559 --> 0:14:19.520
<v Speaker 1>that benchmark here in the United States back in two

0:14:19.600 --> 0:14:23.760
<v Speaker 1>thousand fifteen. Before that, the US definition of broadband was

0:14:24.040 --> 0:14:28.760
<v Speaker 1>embrace yourself for megabits per second down one megabit per

0:14:28.800 --> 0:14:31.720
<v Speaker 1>second up. And I am not joking, and that is

0:14:31.760 --> 0:14:35.200
<v Speaker 1>pretty low. So with the twenty five megabits down three

0:14:35.200 --> 0:14:38.520
<v Speaker 1>megabits up benchmark for broadband, we learned in the US

0:14:39.000 --> 0:14:42.160
<v Speaker 1>from census data back in twenty nineteen that twenty three

0:14:42.840 --> 0:14:46.160
<v Speaker 1>of people in the US lack a wired broadband connection.

0:14:46.760 --> 0:14:50.160
<v Speaker 1>This has been the center of numerous political issues, including

0:14:50.160 --> 0:14:52.960
<v Speaker 1>the f c cs stance on whether or not it

0:14:53.000 --> 0:14:57.479
<v Speaker 1>has the authority to classify broadband internet as a utility

0:14:58.000 --> 0:15:01.440
<v Speaker 1>or something that is a basic right for all citizens.

0:15:01.880 --> 0:15:05.320
<v Speaker 1>That's something that is a It's an ongoing debate, and

0:15:05.360 --> 0:15:09.840
<v Speaker 1>it changes largely because the FCC itself changes every time

0:15:10.160 --> 0:15:13.320
<v Speaker 1>there's a change in an administration at the top of

0:15:13.680 --> 0:15:18.800
<v Speaker 1>US politics gets pretty complicated. Moving on, let's talk about

0:15:19.120 --> 0:15:22.440
<v Speaker 1>land and W. LAND So land or l a N

0:15:22.800 --> 0:15:26.560
<v Speaker 1>stands for local area network. This just refers to a

0:15:26.600 --> 0:15:31.040
<v Speaker 1>series of interconnected computer devices within a limited area. So

0:15:31.080 --> 0:15:34.480
<v Speaker 1>this could be as large as a college campus or

0:15:34.560 --> 0:15:37.800
<v Speaker 1>as small as a really cramped computer dorm room. It

0:15:37.840 --> 0:15:39.920
<v Speaker 1>doesn't all have to take place in colleges. But just

0:15:40.000 --> 0:15:42.640
<v Speaker 1>trust me on that last one. It's that counts as

0:15:42.640 --> 0:15:47.200
<v Speaker 1>a land. Now, the Internet is the network of networks,

0:15:48.080 --> 0:15:51.120
<v Speaker 1>but a land does not necessarily have to connect out

0:15:51.280 --> 0:15:53.800
<v Speaker 1>to the Internet. It can be self contained. So you

0:15:53.880 --> 0:15:56.960
<v Speaker 1>might create a land to work on stuff that probably

0:15:57.000 --> 0:16:00.440
<v Speaker 1>shouldn't be Internet accessible. That allows you to have what's

0:16:00.480 --> 0:16:03.520
<v Speaker 1>called an air gap, which means there's just no direct

0:16:03.640 --> 0:16:07.440
<v Speaker 1>link between that system and the Internet at large. Or

0:16:07.480 --> 0:16:10.080
<v Speaker 1>you might just have a land to facilitate a specific

0:16:10.120 --> 0:16:13.520
<v Speaker 1>type of computing. The example I always think about is

0:16:13.600 --> 0:16:16.560
<v Speaker 1>back in the nineties with the popularity of land parties

0:16:16.960 --> 0:16:20.360
<v Speaker 1>that referred to when geeks like me would go and

0:16:20.560 --> 0:16:23.680
<v Speaker 1>carry our computers with us to meet up with other geeks,

0:16:24.000 --> 0:16:26.640
<v Speaker 1>and then we would all link our computers together with

0:16:26.720 --> 0:16:31.080
<v Speaker 1>actual physical cables, or sometimes it would be gaming consoles

0:16:31.240 --> 0:16:34.240
<v Speaker 1>instead of computers, but you get what I'm saying, and

0:16:34.320 --> 0:16:37.160
<v Speaker 1>we'd link things together in order to play multiplayer games.

0:16:37.720 --> 0:16:42.160
<v Speaker 1>Because before internet broadband speeds made online gaming really feasible,

0:16:42.720 --> 0:16:45.560
<v Speaker 1>this was how we would you know the hoops we

0:16:45.640 --> 0:16:47.600
<v Speaker 1>jumped through in order to create a network to play

0:16:47.640 --> 0:16:53.320
<v Speaker 1>games like Descent and Duke Nukem three D against each other. Typically,

0:16:53.560 --> 0:16:56.640
<v Speaker 1>it's also how e sports tend to work. They use

0:16:56.760 --> 0:17:00.520
<v Speaker 1>local area networks so that one team or player doesn't

0:17:00.560 --> 0:17:04.280
<v Speaker 1>have a distinct advantage or disadvantage due to a difference

0:17:04.320 --> 0:17:07.560
<v Speaker 1>in paying times. A ping, by the way, refers to

0:17:07.720 --> 0:17:11.439
<v Speaker 1>a signal scent from one computer to another, typically like

0:17:11.520 --> 0:17:14.919
<v Speaker 1>a server, and then the return signal comes back, and

0:17:14.960 --> 0:17:17.960
<v Speaker 1>it's a way of measuring the lag between those two

0:17:17.960 --> 0:17:21.040
<v Speaker 1>connection points. And you don't want one team to be

0:17:21.080 --> 0:17:24.800
<v Speaker 1>a disadvantage just because they're they're ping was worse, because

0:17:24.840 --> 0:17:28.720
<v Speaker 1>that doesn't indicate whether they were better players or not,

0:17:28.880 --> 0:17:32.520
<v Speaker 1>or poorer players are not. So local area networks are

0:17:32.520 --> 0:17:34.720
<v Speaker 1>a way to kind of eliminate that, or at least

0:17:34.760 --> 0:17:39.400
<v Speaker 1>reduce it. A w land or w L a N

0:17:39.520 --> 0:17:43.840
<v Speaker 1>is surprise, surprise, a wireless land. So this is a

0:17:43.880 --> 0:17:47.080
<v Speaker 1>network that does the same thing as a local area network,

0:17:47.359 --> 0:17:50.560
<v Speaker 1>only without the physical cables. And like a land, a

0:17:50.760 --> 0:17:53.960
<v Speaker 1>w land doesn't necessarily have to connect out to the

0:17:53.960 --> 0:17:56.439
<v Speaker 1>Internet as a whole. It can, but it doesn't have

0:17:56.560 --> 0:18:00.480
<v Speaker 1>to these days, broadband speeds allow for on line and

0:18:00.520 --> 0:18:04.840
<v Speaker 1>even cloud based gaming and computational uses without the need

0:18:04.880 --> 0:18:07.600
<v Speaker 1>for land parties, though some folks will still go and

0:18:07.640 --> 0:18:10.040
<v Speaker 1>do them, and to be honest, nothing really replaces the

0:18:10.080 --> 0:18:12.879
<v Speaker 1>experience of, you know, going to a land party and

0:18:12.960 --> 0:18:16.840
<v Speaker 1>playing with or against other people in the same physical location,

0:18:17.400 --> 0:18:21.080
<v Speaker 1>where the talking of smack can become an art form.

0:18:21.119 --> 0:18:26.040
<v Speaker 1>It's typically also a little less um objectively terrible than

0:18:26.080 --> 0:18:28.600
<v Speaker 1>what you would find with online chat that is like

0:18:29.359 --> 0:18:32.639
<v Speaker 1>the worst, but in person it tends to not quite

0:18:32.680 --> 0:18:35.560
<v Speaker 1>get that extreme though I guess one downside is that

0:18:35.600 --> 0:18:38.879
<v Speaker 1>you can't easily mute another player that that player is

0:18:38.920 --> 0:18:40.879
<v Speaker 1>saying next to you and annoying the heck out of you,

0:18:41.240 --> 0:18:44.000
<v Speaker 1>unless you know, you happen to have some duct tape handy.

0:18:44.280 --> 0:18:47.439
<v Speaker 1>By the way, always carry duct tape. We've got more

0:18:47.480 --> 0:18:49.080
<v Speaker 1>to go, but I feel like we've picked up the

0:18:49.080 --> 0:18:51.080
<v Speaker 1>pace a little bit and when we come back, will

0:18:51.080 --> 0:19:02.280
<v Speaker 1>continue going down the alphabet, but first a quick break. Okay,

0:19:02.359 --> 0:19:05.359
<v Speaker 1>we're back, and now let's pick up with l c D.

0:19:05.880 --> 0:19:10.119
<v Speaker 1>This stands for liquid crystal display, which probably sounds a

0:19:10.160 --> 0:19:13.480
<v Speaker 1>little odd. After all, the general definition for a crystal

0:19:14.040 --> 0:19:16.760
<v Speaker 1>is that a crystal is a type of solid material

0:19:16.880 --> 0:19:21.159
<v Speaker 1>in which the constituent components are in a highly ordered structure,

0:19:21.960 --> 0:19:25.520
<v Speaker 1>like a lattice or scaffolding. So if you were to

0:19:25.520 --> 0:19:28.919
<v Speaker 1>take a piece of quartz or table salt and you

0:19:29.000 --> 0:19:31.640
<v Speaker 1>looked at it under a really powerful microscope, you would

0:19:31.680 --> 0:19:35.360
<v Speaker 1>see these this what looks like a fairly smooth surfaces

0:19:35.400 --> 0:19:38.440
<v Speaker 1>in fact made up of these repeated patterns of lattice

0:19:38.560 --> 0:19:45.080
<v Speaker 1>like structures that form the overall you know, solid substance.

0:19:45.760 --> 0:19:50.040
<v Speaker 1>But if crystal is a subset of solid materials, then

0:19:50.119 --> 0:19:53.679
<v Speaker 1>what the heck is a liquid crystal? How can you

0:19:53.800 --> 0:19:57.760
<v Speaker 1>have a liquid crystal? Well, we use the term liquid

0:19:57.760 --> 0:20:00.920
<v Speaker 1>crystals to describe stuff that as a state of matter

0:20:01.119 --> 0:20:05.119
<v Speaker 1>that has some elements of crystalline solid features and some

0:20:05.200 --> 0:20:08.119
<v Speaker 1>elements of a liquid material. So, in other words, you

0:20:08.200 --> 0:20:10.840
<v Speaker 1>might have a substance that, like a liquid, will take

0:20:10.880 --> 0:20:13.679
<v Speaker 1>on the shape of whatever container it's in, you know,

0:20:13.800 --> 0:20:16.240
<v Speaker 1>like a bowl of water. You wouldn't have a square

0:20:16.280 --> 0:20:17.920
<v Speaker 1>of water just sitting in the middle of a bowl,

0:20:17.960 --> 0:20:20.399
<v Speaker 1>though the water conforms to the shape of the bowl.

0:20:21.000 --> 0:20:23.080
<v Speaker 1>But if you were to look at that liquid under

0:20:23.119 --> 0:20:26.160
<v Speaker 1>a microscope, you would see that it's molecules are all

0:20:26.200 --> 0:20:30.200
<v Speaker 1>in a specific orientation, more like a crystalline structure. These

0:20:30.200 --> 0:20:33.320
<v Speaker 1>are really cool substances and they allow for all sorts

0:20:33.320 --> 0:20:38.000
<v Speaker 1>of neat applications. So with a liquid crystal display, these

0:20:38.000 --> 0:20:42.280
<v Speaker 1>crystals make images right, well, not exactly all right, So

0:20:42.480 --> 0:20:46.119
<v Speaker 1>there are liquid crystals that, when exposed to an electric current,

0:20:46.200 --> 0:20:50.320
<v Speaker 1>will change shape. There's a type called twisted pneumatics that

0:20:50.440 --> 0:20:53.639
<v Speaker 1>do this, and as the name suggests, these crystals have

0:20:53.680 --> 0:20:56.840
<v Speaker 1>a naturally twisted shape. But when you apply a current

0:20:56.960 --> 0:21:00.280
<v Speaker 1>to them, they will untwist to some degree, and the

0:21:00.320 --> 0:21:03.680
<v Speaker 1>degree to which they untwist depends upon the voltage of

0:21:03.720 --> 0:21:09.960
<v Speaker 1>that current. So by precisely controlling a voltage of a current,

0:21:10.440 --> 0:21:13.800
<v Speaker 1>you can then precisely control how much these liquid crystals

0:21:13.840 --> 0:21:17.520
<v Speaker 1>are able to untwist. And in addition, liquid crystals in

0:21:17.720 --> 0:21:21.720
<v Speaker 1>l c D s can transmit and change polarized light. Now,

0:21:21.720 --> 0:21:25.000
<v Speaker 1>a full discussion on what polarized light is and how

0:21:25.040 --> 0:21:29.199
<v Speaker 1>it works is well beyond this particular podcast episode, but

0:21:29.280 --> 0:21:32.199
<v Speaker 1>basically this means that through filters you can change the

0:21:32.280 --> 0:21:34.720
<v Speaker 1>orientation of light, and with l c D s you

0:21:34.760 --> 0:21:37.880
<v Speaker 1>can change which light is able to pass through into,

0:21:38.160 --> 0:21:40.600
<v Speaker 1>you know, a display or from a display to view,

0:21:41.040 --> 0:21:44.240
<v Speaker 1>and that determines what you see on that display. L

0:21:44.280 --> 0:21:47.439
<v Speaker 1>c D s require typically a backlight. There are some

0:21:47.600 --> 0:21:51.520
<v Speaker 1>that rely on reflective material, so it relies on light

0:21:51.560 --> 0:21:54.520
<v Speaker 1>from your environment hitting the display and then you see

0:21:55.000 --> 0:21:59.600
<v Speaker 1>the reflection. But with things like l c D monitors

0:21:59.640 --> 0:22:03.199
<v Speaker 1>and tell visions, we're talking about a backlit device, and

0:22:03.240 --> 0:22:06.000
<v Speaker 1>because of that, l c D s traditionally have limitations

0:22:06.000 --> 0:22:09.919
<v Speaker 1>when it comes to displaying a high contrast ratio. Contrast

0:22:10.160 --> 0:22:13.280
<v Speaker 1>refers to the difference between the brightest colors a display

0:22:13.280 --> 0:22:16.879
<v Speaker 1>can show versus the darkest colors it can show. And

0:22:16.920 --> 0:22:20.960
<v Speaker 1>because l c D monitors and televisions have a backlight,

0:22:21.640 --> 0:22:24.159
<v Speaker 1>that affects how dark you can get because there's always

0:22:24.200 --> 0:22:28.199
<v Speaker 1>a little bit of bleed through with light. The history

0:22:28.240 --> 0:22:30.800
<v Speaker 1>and tech of l c D s is truly fascinating stuff,

0:22:31.040 --> 0:22:34.600
<v Speaker 1>so I'll save that for a future episode. Next, we

0:22:34.640 --> 0:22:37.680
<v Speaker 1>have L E D and O l E D. Luckily,

0:22:37.800 --> 0:22:40.280
<v Speaker 1>we have some tech that frequently pops up when you're

0:22:40.280 --> 0:22:43.080
<v Speaker 1>talking about displays, and here we go, and L E

0:22:43.160 --> 0:22:46.800
<v Speaker 1>D is a light emitting diode and an O l

0:22:46.800 --> 0:22:50.720
<v Speaker 1>E D is an organic light emitting diode. So obviously

0:22:50.720 --> 0:22:53.320
<v Speaker 1>we need to define some stuff here, right, So first

0:22:53.320 --> 0:22:56.760
<v Speaker 1>of all, what in the blue blazes is a diode.

0:22:57.200 --> 0:22:59.880
<v Speaker 1>It is a component in electronics that acts as kind

0:22:59.880 --> 0:23:03.600
<v Speaker 1>of like a one way street for electrical current. So

0:23:03.640 --> 0:23:07.200
<v Speaker 1>a diode will allow current to pass in one direction,

0:23:07.640 --> 0:23:10.880
<v Speaker 1>but it will prevent it from going the opposite direction.

0:23:11.359 --> 0:23:15.920
<v Speaker 1>Diodes are one of the basic elements in circuitry and electronics,

0:23:15.960 --> 0:23:18.920
<v Speaker 1>and it's a type of semiconductor. And there's a lot

0:23:18.960 --> 0:23:22.760
<v Speaker 1>more to be said, but we can't spend all podcasts

0:23:22.760 --> 0:23:26.080
<v Speaker 1>talking about it. So an l e ED or light

0:23:26.160 --> 0:23:29.960
<v Speaker 1>emitting diode is a subset of diodes. So it allows

0:23:30.000 --> 0:23:33.320
<v Speaker 1>electricity or current rather to pass one way but not

0:23:33.400 --> 0:23:36.320
<v Speaker 1>the other. And as the name suggests, it's a diode

0:23:36.320 --> 0:23:40.639
<v Speaker 1>that emits light as current flows through it. Essentially, electrons

0:23:40.680 --> 0:23:43.879
<v Speaker 1>get pushed to higher energy levels, and when the electrons

0:23:43.920 --> 0:23:47.160
<v Speaker 1>are moving back down to their normal energy levels, they

0:23:47.160 --> 0:23:49.800
<v Speaker 1>have to release that excess energy and they do that

0:23:49.880 --> 0:23:52.960
<v Speaker 1>in the form of photons. You know, the particles of light.

0:23:54.359 --> 0:23:56.879
<v Speaker 1>L E d s don't need as much energy to

0:23:56.920 --> 0:24:00.119
<v Speaker 1>produce light as other light sources. They are far are

0:24:00.160 --> 0:24:04.040
<v Speaker 1>more energy efficient than say, incandescent bulbs. They're even more

0:24:04.119 --> 0:24:07.520
<v Speaker 1>energy efficient than fluorescent lights. They also last a lot

0:24:07.560 --> 0:24:10.879
<v Speaker 1>longer than either of those two types of lights, so

0:24:11.080 --> 0:24:14.439
<v Speaker 1>LED light bulbs are great though they tend to be

0:24:14.480 --> 0:24:19.359
<v Speaker 1>pretty expensive, particularly compared to fluorescence and the old incandescence,

0:24:19.760 --> 0:24:22.280
<v Speaker 1>but they last a lot longer and the amount of

0:24:22.359 --> 0:24:25.360
<v Speaker 1>energy they use is much lower, so switching to them

0:24:25.600 --> 0:24:28.760
<v Speaker 1>can save money over the long term. It's just that

0:24:28.960 --> 0:24:33.560
<v Speaker 1>upfront cost is a high one. And LED television uses

0:24:33.720 --> 0:24:36.400
<v Speaker 1>l e d s as the backlight source, and they

0:24:36.400 --> 0:24:39.119
<v Speaker 1>have great optical range and as I mentioned, they have

0:24:39.240 --> 0:24:42.399
<v Speaker 1>high energy efficiency which brings down the power consumption on

0:24:42.480 --> 0:24:45.320
<v Speaker 1>flat panel televisions that use L e d s. They've

0:24:45.320 --> 0:24:47.840
<v Speaker 1>been around since two thousand five, and they tend to

0:24:47.880 --> 0:24:51.840
<v Speaker 1>have better contrast ratios than your typical, you know, normal

0:24:52.000 --> 0:24:55.360
<v Speaker 1>l C D. Television's pre L e ED and organic

0:24:55.480 --> 0:24:58.600
<v Speaker 1>light emitting diode is an L e ED that contains

0:24:58.640 --> 0:25:04.159
<v Speaker 1>an organic compound on film, and that compound film is electroluminescent,

0:25:04.640 --> 0:25:07.399
<v Speaker 1>which means that lights up when current passes through it.

0:25:08.320 --> 0:25:10.439
<v Speaker 1>One of the many cool things about O l e

0:25:10.560 --> 0:25:13.720
<v Speaker 1>d s is that, since we're talking about a film,

0:25:13.760 --> 0:25:16.919
<v Speaker 1>you can actually create O l e D based displays

0:25:17.000 --> 0:25:21.280
<v Speaker 1>that are extremely thin and are in fact flexible. You

0:25:21.320 --> 0:25:23.840
<v Speaker 1>have to have the right electronics behind it that are

0:25:23.840 --> 0:25:27.720
<v Speaker 1>also flexible, but you can have flexible displays. So oh

0:25:27.840 --> 0:25:31.639
<v Speaker 1>lad displays have led to some really cool features, you know,

0:25:31.680 --> 0:25:35.400
<v Speaker 1>like bending TVs or curving TVs, or televisions that can

0:25:35.480 --> 0:25:40.200
<v Speaker 1>fold up or unfold or unrolled. Then smartphones as well,

0:25:40.280 --> 0:25:43.760
<v Speaker 1>we've seen some at least concepts of that. So these

0:25:43.800 --> 0:25:48.520
<v Speaker 1>malleable display technologies depend on oh lads, and most of

0:25:48.560 --> 0:25:51.480
<v Speaker 1>them cost more than my house did. Well, at least

0:25:51.920 --> 0:25:54.520
<v Speaker 1>that used to be the case. These days, you can

0:25:54.560 --> 0:25:58.200
<v Speaker 1>find oh LED televisions capable of displaying resolutions of four

0:25:58.320 --> 0:26:03.919
<v Speaker 1>K or higher starting at around dollars. That is not

0:26:04.080 --> 0:26:07.679
<v Speaker 1>chump change, I know, but it's still way less expensive

0:26:07.880 --> 0:26:10.800
<v Speaker 1>than the earliest oh LED TVs, which cost in the

0:26:11.000 --> 0:26:14.320
<v Speaker 1>tens of thousands of dollars when they first hit the market.

0:26:15.720 --> 0:26:19.320
<v Speaker 1>Moving on next, we have MAC. Mac is the name

0:26:19.359 --> 0:26:22.919
<v Speaker 1>of the fictional boxer in the punch Out series, but

0:26:23.040 --> 0:26:26.680
<v Speaker 1>it also stands for Media Access Control, and we typically

0:26:26.680 --> 0:26:31.440
<v Speaker 1>see it paired with the word address, giving us MAC address.

0:26:31.600 --> 0:26:35.440
<v Speaker 1>This refers to a unique identifier for a network interface

0:26:35.480 --> 0:26:39.800
<v Speaker 1>controller or n i C, so there's another bonus initialism.

0:26:39.840 --> 0:26:43.240
<v Speaker 1>This is used to identify a specific element connected to

0:26:43.480 --> 0:26:46.640
<v Speaker 1>a computer network, and it just takes a little thinking

0:26:46.680 --> 0:26:49.880
<v Speaker 1>to realize how this is necessary. Right, if you're connecting

0:26:50.160 --> 0:26:53.280
<v Speaker 1>various machines together in a network, you need some way

0:26:53.320 --> 0:26:56.880
<v Speaker 1>to identify every single device connected, or else you would

0:26:56.920 --> 0:27:00.160
<v Speaker 1>never know how to send information from one specific machineing

0:27:00.480 --> 0:27:03.359
<v Speaker 1>to another. It would be more like a giant party

0:27:03.440 --> 0:27:06.359
<v Speaker 1>line with all machines just broadcasting to the rest of

0:27:06.359 --> 0:27:09.280
<v Speaker 1>the network, and that would be chaos. You wouldn't know

0:27:09.320 --> 0:27:12.280
<v Speaker 1>who was saying what, and it would all be jumbled up.

0:27:12.560 --> 0:27:15.000
<v Speaker 1>It's bad enough to think about just in terms of communication,

0:27:15.080 --> 0:27:17.200
<v Speaker 1>but when you get to stuff like file transfers and

0:27:17.240 --> 0:27:20.760
<v Speaker 1>the like, it would just be untenable. So a MAC

0:27:20.800 --> 0:27:24.679
<v Speaker 1>address usually is something that is burned into a particular

0:27:24.760 --> 0:27:28.600
<v Speaker 1>network interface controller, So it's actually like a permanent thing

0:27:28.920 --> 0:27:31.880
<v Speaker 1>as part of a piece of hardware that connects as

0:27:31.960 --> 0:27:35.359
<v Speaker 1>part of the network um and it's determined by whatever

0:27:35.440 --> 0:27:38.439
<v Speaker 1>company manufactured that controller. So you could think of it

0:27:38.640 --> 0:27:42.159
<v Speaker 1>kind of like a serial number that's tattooed onto the controller,

0:27:42.440 --> 0:27:46.360
<v Speaker 1>and each tattoo is unique in that network. Now, sometimes

0:27:46.359 --> 0:27:49.719
<v Speaker 1>a MAC address is only mostly permanent, which means there

0:27:49.720 --> 0:27:51.600
<v Speaker 1>are actually some methods in which a person like a

0:27:51.640 --> 0:27:55.760
<v Speaker 1>network administrator could change a MAC address for a specific

0:27:55.800 --> 0:27:59.000
<v Speaker 1>piece of hardware. Now for the fun bit, these network

0:27:59.040 --> 0:28:04.159
<v Speaker 1>interface controller and their unique MAC addresses. These are necessary

0:28:04.200 --> 0:28:07.560
<v Speaker 1>within a single network. So let's say we've got two

0:28:07.760 --> 0:28:11.600
<v Speaker 1>n i c s connected inside Network A. They would

0:28:11.600 --> 0:28:15.320
<v Speaker 1>each need a unique MAC address or else nothing would work.

0:28:15.760 --> 0:28:18.800
<v Speaker 1>But let's say we've actually got two separate networks. We've

0:28:18.800 --> 0:28:21.560
<v Speaker 1>got network A and we've got network B. And we

0:28:21.640 --> 0:28:24.440
<v Speaker 1>find out that there's an n i C in Network

0:28:24.440 --> 0:28:27.400
<v Speaker 1>A and it has the exact same MAC address as

0:28:27.440 --> 0:28:30.200
<v Speaker 1>an n I C network B. Does everything fall apart?

0:28:30.240 --> 0:28:35.159
<v Speaker 1>Then nope. These unique MAC addresses are only necessary within

0:28:35.400 --> 0:28:38.200
<v Speaker 1>a single network. So when you have two different n

0:28:38.200 --> 0:28:41.520
<v Speaker 1>i c s connecting to separate networks, they can have

0:28:41.640 --> 0:28:45.040
<v Speaker 1>the same MAC address, no problem, there's no conflict there.

0:28:45.520 --> 0:28:47.280
<v Speaker 1>There's a lot more to say than that, but you know,

0:28:47.480 --> 0:28:49.160
<v Speaker 1>you know the old song and dance at this point.

0:28:50.080 --> 0:28:54.640
<v Speaker 1>MIDI is next. This is Musical Instrument Digital Interface m

0:28:54.800 --> 0:28:58.760
<v Speaker 1>I d I. This is one of my favorite technologies.

0:28:59.080 --> 0:29:02.280
<v Speaker 1>It's a technical ANDERD that is sort of like an umbrella.

0:29:02.560 --> 0:29:06.000
<v Speaker 1>So under this technical standard, you have specifications for digital

0:29:06.040 --> 0:29:10.480
<v Speaker 1>interfaces as well as the connectors that connect these various

0:29:10.480 --> 0:29:16.360
<v Speaker 1>digital interfaces to things like electric musical instruments and computers.

0:29:16.400 --> 0:29:20.360
<v Speaker 1>And you have a communications protocol, and this allows various

0:29:20.400 --> 0:29:24.000
<v Speaker 1>electronic audio and computer equipment to quote unquote talk to

0:29:24.080 --> 0:29:28.320
<v Speaker 1>each other. So a MIDI keyboard like a musical keyboard,

0:29:28.360 --> 0:29:32.440
<v Speaker 1>like a synthesizer, a synthesizer specifically with MIDI, that is,

0:29:32.920 --> 0:29:35.800
<v Speaker 1>with the right connectors, you could connect that directly to

0:29:35.840 --> 0:29:38.600
<v Speaker 1>a computer or to a digital audio station that in

0:29:38.680 --> 0:29:41.560
<v Speaker 1>turn connects to a computer. And it could be any

0:29:41.640 --> 0:29:44.520
<v Speaker 1>kind of computer as well. Like I always think of

0:29:44.680 --> 0:29:47.320
<v Speaker 1>big desktops because I think of the big like production

0:29:47.920 --> 0:29:49.800
<v Speaker 1>type stuff. But you can have a laptop, it could

0:29:49.800 --> 0:29:51.479
<v Speaker 1>be a smartphone, it could be a tablet. As long

0:29:51.520 --> 0:29:55.320
<v Speaker 1>as you have the compatible connectors that allow you to

0:29:56.000 --> 0:29:58.680
<v Speaker 1>insert that into the system, it would work. And the

0:29:58.720 --> 0:30:02.400
<v Speaker 1>MIDI protocol emerge in the nineteen eighties as electronic music

0:30:02.520 --> 0:30:06.720
<v Speaker 1>was really evolving, digital instruments and digital editing tools were

0:30:06.840 --> 0:30:09.000
<v Speaker 1>changing the industry. But that also meant there needed to

0:30:09.040 --> 0:30:12.400
<v Speaker 1>be some sort of standardized way to handle all this stuff,

0:30:12.640 --> 0:30:14.920
<v Speaker 1>or else we would again run into that problem where

0:30:14.920 --> 0:30:18.240
<v Speaker 1>you have a billion different proprietary formats that emerge, and

0:30:18.280 --> 0:30:23.360
<v Speaker 1>they make things difficult. Interestingly, MIDI does not transmit any

0:30:23.400 --> 0:30:26.720
<v Speaker 1>sort of audio signal. You may have listened to music

0:30:26.800 --> 0:30:30.800
<v Speaker 1>played back from a MIDI file, but that file doesn't

0:30:30.800 --> 0:30:34.120
<v Speaker 1>actually contain any sound. You can think of it more

0:30:34.520 --> 0:30:38.720
<v Speaker 1>as that file contains the description of sound instructions for

0:30:38.920 --> 0:30:43.200
<v Speaker 1>creating sound. So it's kind of like telling a system

0:30:43.240 --> 0:30:47.160
<v Speaker 1>you need to play this specific note at this specific

0:30:47.200 --> 0:30:51.320
<v Speaker 1>time for this long and with this an intonation and

0:30:51.440 --> 0:30:54.560
<v Speaker 1>with this amount of volume, the and through many an

0:30:54.560 --> 0:30:59.520
<v Speaker 1>engineer could change really really minute tiny things about digital recording,

0:31:00.320 --> 0:31:05.200
<v Speaker 1>how a note gets expressed. It's really neat stuff. This means,

0:31:05.240 --> 0:31:07.440
<v Speaker 1>by the way, that if you have a MIDI keyboard,

0:31:07.640 --> 0:31:10.320
<v Speaker 1>meaning a you know, like a musical keyboard that is

0:31:10.440 --> 0:31:14.160
<v Speaker 1>MIDI compliant, that keyboard has to have some other component

0:31:14.240 --> 0:31:17.920
<v Speaker 1>inside of it that actually generates the sound you could

0:31:17.960 --> 0:31:22.520
<v Speaker 1>create if you wanted to a purely MIDI keyboard without

0:31:22.560 --> 0:31:24.760
<v Speaker 1>that kind of component, but that would mean that if

0:31:24.760 --> 0:31:26.840
<v Speaker 1>you were to play that keyboard, you wouldn't actually be

0:31:26.920 --> 0:31:29.720
<v Speaker 1>generating any You couldn't like feed that to a speakers

0:31:29.760 --> 0:31:32.720
<v Speaker 1>or anything. It wouldn't create sound. I mean the only

0:31:32.760 --> 0:31:34.920
<v Speaker 1>sound you would get was that percussive sound of your

0:31:34.960 --> 0:31:38.560
<v Speaker 1>fingers hitting the keys, which kind of seems like it

0:31:38.560 --> 0:31:40.680
<v Speaker 1>would be a type of performance art that I would

0:31:40.720 --> 0:31:44.000
<v Speaker 1>really rather not sit through. One of the best analogies

0:31:44.040 --> 0:31:45.800
<v Speaker 1>I've seen, and I really wish that I had come

0:31:45.880 --> 0:31:48.960
<v Speaker 1>up with this one, is that MIDI is to digital

0:31:49.040 --> 0:31:53.480
<v Speaker 1>music the way old piano roles were for player pianos.

0:31:53.520 --> 0:31:56.720
<v Speaker 1>So a piano role doesn't generate sound on its own,

0:31:56.800 --> 0:32:00.160
<v Speaker 1>It only works when you put it through a player piano. Know.

0:32:01.080 --> 0:32:04.040
<v Speaker 1>The real beauty of this is how Middy allows for

0:32:04.080 --> 0:32:07.920
<v Speaker 1>the computational control of musical expression, which can come in

0:32:07.960 --> 0:32:11.520
<v Speaker 1>awfully handy if you're seeking out a particular sound and

0:32:11.680 --> 0:32:14.240
<v Speaker 1>vibe for a piece of music. Even if you don't

0:32:14.560 --> 0:32:19.200
<v Speaker 1>use the electronic digital version as your final product, it

0:32:19.280 --> 0:32:21.400
<v Speaker 1>might give you the feeling you want, so that when

0:32:21.400 --> 0:32:23.280
<v Speaker 1>you record it for real z s with you know,

0:32:23.360 --> 0:32:27.400
<v Speaker 1>quote unquote real musical instruments. I object to that phrase,

0:32:27.440 --> 0:32:29.840
<v Speaker 1>but some people use it. It means that then you

0:32:29.880 --> 0:32:34.800
<v Speaker 1>could replicate what you had created digitally. Now I've done

0:32:34.840 --> 0:32:37.720
<v Speaker 1>episodes about Mindy, so if you're interested in learning more,

0:32:37.840 --> 0:32:40.520
<v Speaker 1>be sure to do a search on the tech Stuff archives.

0:32:41.360 --> 0:32:44.320
<v Speaker 1>When we come back, we'll finish out the MS and

0:32:44.440 --> 0:32:56.760
<v Speaker 1>it's with a biggie. But first, let's take a quick break. Okay,

0:32:56.960 --> 0:33:02.360
<v Speaker 1>MP three and impact All right, here we go. MP

0:33:02.600 --> 0:33:06.479
<v Speaker 1>three stands for IMPEG Audio Layer three. But then that

0:33:06.560 --> 0:33:09.400
<v Speaker 1>raises the question of what the heck does IMPEG stand for?

0:33:09.560 --> 0:33:14.360
<v Speaker 1>And we got to get there. So IMPEG technically stands

0:33:14.360 --> 0:33:18.600
<v Speaker 1>for the Moving Picture Experts Group. So you remember earlier

0:33:18.640 --> 0:33:21.479
<v Speaker 1>in this episode about JPEG's and how that came out

0:33:21.520 --> 0:33:24.840
<v Speaker 1>of a subcommittee that was working on the digital coding

0:33:25.080 --> 0:33:29.080
<v Speaker 1>of still images. This is kind of similar, except IMPEG

0:33:29.240 --> 0:33:33.560
<v Speaker 1>brings together various working groups of engineers from different organizations

0:33:33.880 --> 0:33:37.560
<v Speaker 1>to create standardized ways to encode different kinds of media,

0:33:38.120 --> 0:33:41.880
<v Speaker 1>which includes, but is not exclusive to video. And that

0:33:41.960 --> 0:33:44.240
<v Speaker 1>gets a little confusing, right, I mean, you would think

0:33:44.280 --> 0:33:48.120
<v Speaker 1>that a group called the Moving Picture Experts Group would

0:33:48.160 --> 0:33:51.920
<v Speaker 1>be concerning itself only with moving pictures like a video.

0:33:52.680 --> 0:33:55.120
<v Speaker 1>The group came together in the late nineteen eighties, and

0:33:55.120 --> 0:33:59.440
<v Speaker 1>while the primary effort was in encoding video digitally, that

0:33:59.720 --> 0:34:03.960
<v Speaker 1>includes the necessity of encoding audio as well, because a

0:34:04.040 --> 0:34:08.160
<v Speaker 1>lot of video has audio associated with it, and encoding

0:34:08.280 --> 0:34:12.640
<v Speaker 1>also includes compression because raw media files like video and

0:34:12.680 --> 0:34:16.759
<v Speaker 1>audio are pretty darn big, like way too large to

0:34:16.880 --> 0:34:21.000
<v Speaker 1>transmit easily over network connections. Way back in the nineties,

0:34:21.120 --> 0:34:25.520
<v Speaker 1>those were slow connections and it just wasn't feasible. So

0:34:25.600 --> 0:34:28.719
<v Speaker 1>these working groups in this alliance innovated in ways to

0:34:28.880 --> 0:34:33.440
<v Speaker 1>code video and audio digitally in ways that computers can handle,

0:34:33.800 --> 0:34:36.520
<v Speaker 1>and to compress file sizes down so they weren't quite

0:34:36.560 --> 0:34:39.880
<v Speaker 1>so huge and you could actually transfer them from one

0:34:39.920 --> 0:34:43.359
<v Speaker 1>computer to another without it taking a week. I think

0:34:43.400 --> 0:34:46.000
<v Speaker 1>most folks when they use the word IMPEG, or rather

0:34:46.120 --> 0:34:49.560
<v Speaker 1>I guess the acronym IMPEG, they actually mean the file

0:34:49.719 --> 0:34:54.160
<v Speaker 1>extension IMPEG or MPG. This is just one of the

0:34:54.239 --> 0:34:59.680
<v Speaker 1>formats that this particular working group spawned. An IMPEG file

0:35:00.239 --> 0:35:04.000
<v Speaker 1>is a compressed video file format. Uh. It's one that

0:35:04.200 --> 0:35:08.160
<v Speaker 1>used either IMPEG one or IMPEG two file compression. But

0:35:08.239 --> 0:35:11.160
<v Speaker 1>these days most of the time we're talking about IMPEG

0:35:11.239 --> 0:35:14.840
<v Speaker 1>two because that's the type of file compression designed for

0:35:15.160 --> 0:35:19.719
<v Speaker 1>higher definition video. IMPEG one was like VHS level definition.

0:35:19.760 --> 0:35:21.920
<v Speaker 1>Because you gotta remember this was coming out in the

0:35:22.000 --> 0:35:25.480
<v Speaker 1>late eighties when VHS was still a thing, so not

0:35:25.640 --> 0:35:29.440
<v Speaker 1>very practical for today's video. It's the enhanced version of

0:35:29.480 --> 0:35:32.920
<v Speaker 1>IMPEG compression is IMPEG two. Some folks use IMPEG as

0:35:32.960 --> 0:35:36.000
<v Speaker 1>shorthand for just video file even if the video file

0:35:36.120 --> 0:35:39.600
<v Speaker 1>isn't an IMPEG format, so that can get a little confusing.

0:35:40.040 --> 0:35:43.839
<v Speaker 1>But then that raises the question what about MP three. Well,

0:35:43.880 --> 0:35:48.000
<v Speaker 1>that's a coding format specifically for digital audio, and it's

0:35:48.000 --> 0:35:51.080
<v Speaker 1>a lossy form of compression, which means that in the

0:35:51.120 --> 0:35:55.080
<v Speaker 1>process of compressing the audio file to a smaller size,

0:35:55.560 --> 0:35:59.520
<v Speaker 1>the protocol ditches some of the information from that original

0:35:59.680 --> 0:36:03.160
<v Speaker 1>raw audio file. So how does the MP three process

0:36:03.320 --> 0:36:07.840
<v Speaker 1>quote unquote know which information it should lose? And it's

0:36:07.880 --> 0:36:13.160
<v Speaker 1>all based on psychoacoustics, or how we perceive sound, and moreover,

0:36:13.680 --> 0:36:16.920
<v Speaker 1>which sounds might be beyond the scope of human hearing.

0:36:17.800 --> 0:36:22.239
<v Speaker 1>For example, because of our limitations in our perception, it

0:36:22.400 --> 0:36:25.400
<v Speaker 1>is very hard for us to hear a soft sound

0:36:25.840 --> 0:36:30.279
<v Speaker 1>that's played immediately after a very loud sound. So let's

0:36:30.280 --> 0:36:34.280
<v Speaker 1>say you've got a digital audio file and that has

0:36:34.320 --> 0:36:37.719
<v Speaker 1>a very soft sound played right after a really loud one.

0:36:38.280 --> 0:36:42.759
<v Speaker 1>The MP three compression algorithm essentially says, heck, no one's

0:36:42.760 --> 0:36:45.560
<v Speaker 1>gonna be able to hear this little soft sound anyway,

0:36:45.640 --> 0:36:47.560
<v Speaker 1>So we might as well lose it if you can't

0:36:47.560 --> 0:36:50.160
<v Speaker 1>hear it, it doesn't need to be there, and snip

0:36:50.200 --> 0:36:52.160
<v Speaker 1>that a little bit of data doesn't make it into

0:36:52.200 --> 0:36:56.040
<v Speaker 1>the compressed file. Similarly, there may be some sounds within

0:36:56.120 --> 0:37:00.120
<v Speaker 1>that digital audio recording that are below or above the

0:37:00.200 --> 0:37:04.080
<v Speaker 1>threshold of human hearing when it comes to pitch, so

0:37:04.200 --> 0:37:08.240
<v Speaker 1>we typically define this as consisting of tones between twenty hurts,

0:37:08.280 --> 0:37:11.919
<v Speaker 1>which is a very very low pitch, and twenty thousand hurts,

0:37:11.920 --> 0:37:14.479
<v Speaker 1>which is a very high pitch, and most folks start

0:37:14.560 --> 0:37:17.919
<v Speaker 1>to lose the ability to hear the higher pitches as

0:37:17.960 --> 0:37:21.319
<v Speaker 1>they age. This has led to some interesting technologies, such

0:37:21.360 --> 0:37:24.960
<v Speaker 1>as sounds designed to annoy young people that old people

0:37:25.000 --> 0:37:29.640
<v Speaker 1>can't hear, so it's used to help discourage loitering in

0:37:29.719 --> 0:37:33.560
<v Speaker 1>blazes like convenience stores. True Story and n P three

0:37:33.600 --> 0:37:37.560
<v Speaker 1>algorithm could trim away all frequencies that are identified as

0:37:37.600 --> 0:37:42.120
<v Speaker 1>being outside the scope of typical human hearing. The MP

0:37:42.239 --> 0:37:45.400
<v Speaker 1>three compression algorithm is kind of a sliding scale, so

0:37:45.440 --> 0:37:48.200
<v Speaker 1>you can set parameters as to how much you want

0:37:48.239 --> 0:37:51.760
<v Speaker 1>to compress the file size that in turn will affect

0:37:51.760 --> 0:37:55.719
<v Speaker 1>how drastically the algorithm will alter the raw audio, So

0:37:55.760 --> 0:37:58.560
<v Speaker 1>this can result in a compressed file that just doesn't

0:37:58.880 --> 0:38:02.200
<v Speaker 1>sound good. And there are plenty of audio files who

0:38:02.200 --> 0:38:05.800
<v Speaker 1>will just turn their noses up at lossy compression formats

0:38:05.880 --> 0:38:09.919
<v Speaker 1>like MP three no matter what level of compression you use,

0:38:10.239 --> 0:38:13.040
<v Speaker 1>and they prefer lossless file formats that keep all the

0:38:13.120 --> 0:38:16.040
<v Speaker 1>information there. And in some cases they have a point,

0:38:16.200 --> 0:38:21.120
<v Speaker 1>but in others, well, your own experience might vary drastically

0:38:21.239 --> 0:38:25.040
<v Speaker 1>from someone else's. My own hearing must be shot because,

0:38:25.120 --> 0:38:27.960
<v Speaker 1>at least in some cases, I have trouble telling the

0:38:28.000 --> 0:38:32.280
<v Speaker 1>difference between a decent MP three and a lossless audio

0:38:32.360 --> 0:38:36.160
<v Speaker 1>format of the same file played on the same set

0:38:36.160 --> 0:38:40.960
<v Speaker 1>of equipment. Moving on next, we have n f C.

0:38:41.400 --> 0:38:45.200
<v Speaker 1>This stands for near field communications and we're back on

0:38:45.360 --> 0:38:48.759
<v Speaker 1>more protocols. So in this case, we're talking about communications

0:38:48.800 --> 0:38:53.200
<v Speaker 1>protocols that allow for electronic communication between two devices that

0:38:53.280 --> 0:38:56.360
<v Speaker 1>are pretty darn close to each other. And by pretty

0:38:56.440 --> 0:38:58.399
<v Speaker 1>darn close, I mean they have to be at at

0:38:59.000 --> 0:39:02.640
<v Speaker 1>maximum four centimeters apart or one and a half inches.

0:39:02.960 --> 0:39:06.120
<v Speaker 1>You get beyond that and the NFC range doesn't work.

0:39:06.719 --> 0:39:10.920
<v Speaker 1>NFC allows for low throughput data exchanges, meaning you wouldn't

0:39:11.000 --> 0:39:15.279
<v Speaker 1>use NFC two, say, transfer a digital movie from a

0:39:15.320 --> 0:39:18.640
<v Speaker 1>computer to a smartphone or tablet. The protocols just don't

0:39:18.640 --> 0:39:21.880
<v Speaker 1>allow for that, at least not on any time scale

0:39:22.040 --> 0:39:26.360
<v Speaker 1>that would be convenient. Instead, NFC is meant to transfer

0:39:26.600 --> 0:39:30.960
<v Speaker 1>small bits of data for specific purposes. For example, you

0:39:31.040 --> 0:39:35.120
<v Speaker 1>might use an NFC enabled device to tap to pay

0:39:35.160 --> 0:39:38.080
<v Speaker 1>for something with a compatible payment system. You've got a

0:39:38.120 --> 0:39:41.680
<v Speaker 1>credit cards stored in your smartphone, your smartphone's got NFC chip.

0:39:42.120 --> 0:39:45.600
<v Speaker 1>The vendor you go to has an NFC pay area.

0:39:45.960 --> 0:39:48.239
<v Speaker 1>You just tap your phone to that and it makes

0:39:48.280 --> 0:39:52.080
<v Speaker 1>the little communications transfer and boom your set. There are

0:39:52.160 --> 0:39:54.719
<v Speaker 1>electronic ticket systems that use this kind of stuff where

0:39:54.719 --> 0:39:57.080
<v Speaker 1>you can use your phone as like an electronic ticket

0:39:57.120 --> 0:39:59.400
<v Speaker 1>to get into a venue and no one has to

0:39:59.440 --> 0:40:01.400
<v Speaker 1>scan a kee our code or anything like that. You

0:40:01.480 --> 0:40:05.680
<v Speaker 1>just tap your phone. NFC allows for the communication between

0:40:05.719 --> 0:40:09.680
<v Speaker 1>your device and the venue device, and boom, once it's authenticated,

0:40:09.760 --> 0:40:11.800
<v Speaker 1>you get to go in. That's the kind of stuff

0:40:11.840 --> 0:40:15.200
<v Speaker 1>that we're talking about here. And while you wouldn't use

0:40:15.320 --> 0:40:20.480
<v Speaker 1>NFC to transmit large files directly, you could use NFC

0:40:20.680 --> 0:40:24.759
<v Speaker 1>to facilitate some other type of connection between devices that

0:40:24.840 --> 0:40:28.400
<v Speaker 1>does allow for larger file transfers. So, for example, you

0:40:28.480 --> 0:40:30.920
<v Speaker 1>might be able to tap your phone against the computer

0:40:31.239 --> 0:40:34.280
<v Speaker 1>that happens to store, you know, like a particular digital

0:40:34.320 --> 0:40:38.120
<v Speaker 1>movie you want to transfer, and NFC might be used

0:40:38.120 --> 0:40:42.160
<v Speaker 1>to establish a wireless network link between your smartphone and

0:40:42.200 --> 0:40:44.839
<v Speaker 1>the computer, and then the movie would transfer over this

0:40:45.200 --> 0:40:48.400
<v Speaker 1>wireless network link. It wouldn't be using NFC itself to

0:40:48.440 --> 0:40:51.480
<v Speaker 1>do that. NFC would just be used to initiate that connection.

0:40:52.360 --> 0:40:56.920
<v Speaker 1>One popular example of NFC technology is the Ambo, a

0:40:56.960 --> 0:41:00.319
<v Speaker 1>collection of toys from Nintendo that use NFC chips to

0:41:00.400 --> 0:41:03.200
<v Speaker 1>allow the toys to connect with Nintendo game systems like

0:41:03.239 --> 0:41:06.319
<v Speaker 1>the Wii U and the Nintendo Switch. If you're not

0:41:06.360 --> 0:41:09.600
<v Speaker 1>familiar with these things, So there are these little toys

0:41:09.600 --> 0:41:12.719
<v Speaker 1>that have, you know, a flat base, so you might

0:41:12.760 --> 0:41:16.399
<v Speaker 1>have Mario or or Samus or think characters like that

0:41:16.520 --> 0:41:21.759
<v Speaker 1>link Zelda, so they're typically famous Nintendo characters. You buy

0:41:21.800 --> 0:41:25.960
<v Speaker 1>these toys and then on certain games with these systems,

0:41:26.000 --> 0:41:28.680
<v Speaker 1>you can bring the toy in close contact with the

0:41:28.719 --> 0:41:32.640
<v Speaker 1>game system, and doing so unlocks new features in the game,

0:41:32.960 --> 0:41:35.640
<v Speaker 1>which might mean that you can play as a new character,

0:41:36.360 --> 0:41:39.120
<v Speaker 1>or you unlock levels that you didn't have access to before,

0:41:39.280 --> 0:41:41.920
<v Speaker 1>or you get a new set of moves or equipment.

0:41:41.960 --> 0:41:44.399
<v Speaker 1>All sorts of stuff like that. It's a pretty neat

0:41:44.440 --> 0:41:49.080
<v Speaker 1>implementation of NFC technology. Other simple uses of NFC can

0:41:49.120 --> 0:41:52.480
<v Speaker 1>include anything from sharing information so it's like the equivalent

0:41:52.520 --> 0:41:56.640
<v Speaker 1>of exchanging business cards but you're doing it digitally, or

0:41:57.040 --> 0:41:59.640
<v Speaker 1>using an old mobile device to transfer settings to a

0:41:59.680 --> 0:42:02.040
<v Speaker 1>new one. So you buy a new phone, you bring

0:42:02.080 --> 0:42:04.360
<v Speaker 1>your new phone in close contact with your old phone.

0:42:04.640 --> 0:42:08.080
<v Speaker 1>Your old phone says this is how this owner likes things,

0:42:08.239 --> 0:42:11.440
<v Speaker 1>and your new phone immediately adopts those settings, so that

0:42:11.520 --> 0:42:14.960
<v Speaker 1>way your phone's already the way you like it. I've

0:42:15.000 --> 0:42:19.600
<v Speaker 1>done that multiple times with my various phones. Moving on,

0:42:20.120 --> 0:42:24.240
<v Speaker 1>we have o e M. This stands for original equipment manufacturer,

0:42:24.440 --> 0:42:26.719
<v Speaker 1>and typically we use o e M to describe a

0:42:26.760 --> 0:42:30.520
<v Speaker 1>company that's in the business of making components that are

0:42:30.600 --> 0:42:33.560
<v Speaker 1>used in the products of other companies. So, in other words,

0:42:33.800 --> 0:42:35.680
<v Speaker 1>and o e M is a type of company that

0:42:35.760 --> 0:42:38.759
<v Speaker 1>might make the circuit board you find in a particular

0:42:38.800 --> 0:42:42.360
<v Speaker 1>electronic device marketed by I don't know, let's say Atari.

0:42:42.640 --> 0:42:46.160
<v Speaker 1>So Atari makes the device, or at least markets and

0:42:46.200 --> 0:42:48.800
<v Speaker 1>sells it, but some of the components in that device

0:42:48.920 --> 0:42:52.600
<v Speaker 1>come from other companies O e M s. Sometimes this

0:42:52.640 --> 0:42:54.960
<v Speaker 1>gets a bit muddy. So, for example, let's say you

0:42:54.960 --> 0:42:57.319
<v Speaker 1>were to buy a computer off the shelf of a

0:42:57.360 --> 0:43:00.880
<v Speaker 1>store like Best Buy, and let say that that computer

0:43:00.960 --> 0:43:03.920
<v Speaker 1>was made by Dell, and it has the Windows operating

0:43:03.960 --> 0:43:07.239
<v Speaker 1>system on it. Well, Dell doesn't make Windows. That's a

0:43:07.360 --> 0:43:10.600
<v Speaker 1>Microsoft product. So in this case, the computer you buy

0:43:10.800 --> 0:43:13.759
<v Speaker 1>is a Dell computer, but Microsoft is an O E.

0:43:13.920 --> 0:43:16.720
<v Speaker 1>M because that's the company that made the operating system

0:43:16.800 --> 0:43:22.879
<v Speaker 1>that this computer is using. Next, we've got O T T. Yeah,

0:43:22.960 --> 0:43:26.040
<v Speaker 1>you know me, this is over the top. That's what

0:43:26.120 --> 0:43:28.200
<v Speaker 1>O T T stands for, over the top. Now I

0:43:28.200 --> 0:43:31.560
<v Speaker 1>could get super silly on this and explain that over

0:43:31.600 --> 0:43:34.840
<v Speaker 1>the Top is a nineteen seven action film starring Sylvester

0:43:34.920 --> 0:43:37.480
<v Speaker 1>Stallone in which he plays a truck driver who competes

0:43:37.480 --> 0:43:41.200
<v Speaker 1>in professional arm wrestling tournaments and ultimately competes in a

0:43:41.280 --> 0:43:43.799
<v Speaker 1>tournament that will win him a new truck and the

0:43:43.880 --> 0:43:47.320
<v Speaker 1>love of his son. And yes, that is a real movie,

0:43:47.760 --> 0:43:50.440
<v Speaker 1>and I love it, and it is not good. It

0:43:50.560 --> 0:43:53.759
<v Speaker 1>is not a good movie, but I love it anyway.

0:43:53.960 --> 0:43:57.520
<v Speaker 1>And that's what O T T is in my heart.

0:43:57.760 --> 0:44:01.080
<v Speaker 1>But in tech, O T T actually stands for over

0:44:01.120 --> 0:44:03.839
<v Speaker 1>the top. In the case of a media service, So

0:44:03.920 --> 0:44:06.919
<v Speaker 1>the media service goes over the top of some other

0:44:06.960 --> 0:44:10.320
<v Speaker 1>traditional service like cable TV. So with O T T

0:44:10.920 --> 0:44:14.520
<v Speaker 1>you get media delivered over Internet connectivity as opposed to

0:44:14.560 --> 0:44:18.279
<v Speaker 1>something like a cable feed or satellite feed. So all

0:44:18.320 --> 0:44:23.440
<v Speaker 1>those streaming services like Disney Plus, Netflix, HBO, Max, Peacock,

0:44:23.560 --> 0:44:26.520
<v Speaker 1>Hulu and all the rest, all those count as O

0:44:26.800 --> 0:44:32.399
<v Speaker 1>T T services. Next, we've got P to the new

0:44:32.520 --> 0:44:36.200
<v Speaker 1>number two P so P the number two P that

0:44:36.320 --> 0:44:39.480
<v Speaker 1>stands for peer to peer, and in this case the

0:44:39.600 --> 0:44:42.759
<v Speaker 1>two is T O peer to peer. This is a

0:44:42.840 --> 0:44:47.480
<v Speaker 1>distributed approach to networking. The individual machines in a peer

0:44:47.480 --> 0:44:50.560
<v Speaker 1>to peer network are nodes that connect with each other,

0:44:51.160 --> 0:44:54.920
<v Speaker 1>and they can distribute workloads across the various nodes. This

0:44:55.000 --> 0:44:59.160
<v Speaker 1>is different from the traditional client server network because if

0:44:59.200 --> 0:45:01.600
<v Speaker 1>you had just a P or client server network, you

0:45:01.600 --> 0:45:05.560
<v Speaker 1>would have a centralized server that would then communicate with

0:45:05.760 --> 0:45:10.160
<v Speaker 1>each individual client. The clients in the client server network

0:45:10.400 --> 0:45:13.240
<v Speaker 1>would not communicate with each other. They wouldn't be like nodes.

0:45:13.280 --> 0:45:15.799
<v Speaker 1>They would just communicate with the server. They might be

0:45:15.840 --> 0:45:18.520
<v Speaker 1>able to communicate with each other using the server as

0:45:18.560 --> 0:45:22.040
<v Speaker 1>kind of a mediator, but they wouldn't directly connect to

0:45:22.040 --> 0:45:25.439
<v Speaker 1>each other. So and appeer to peer network. You can

0:45:25.600 --> 0:45:28.479
<v Speaker 1>have the nodes communicate directly with each other and work

0:45:28.640 --> 0:45:32.080
<v Speaker 1>directly with each other. That opens up all sorts of possibilities.

0:45:32.480 --> 0:45:35.759
<v Speaker 1>For example, in certain computational problems, you can have the

0:45:35.840 --> 0:45:39.000
<v Speaker 1>various computers on the p TWOP network lend a hand

0:45:39.360 --> 0:45:42.440
<v Speaker 1>and speed up the time it takes to solve that problem.

0:45:42.600 --> 0:45:45.600
<v Speaker 1>Or you can have p TWOP networks share files quickly

0:45:45.719 --> 0:45:49.440
<v Speaker 1>through the network itself. File sharing networks gave p t

0:45:49.520 --> 0:45:51.840
<v Speaker 1>P a really bad name in the late nineties and

0:45:51.840 --> 0:45:56.200
<v Speaker 1>early two thousand's. There is nothing wrong with sharing files

0:45:56.239 --> 0:45:58.960
<v Speaker 1>if you have the authority to do it, like if

0:45:58.960 --> 0:46:02.600
<v Speaker 1>you have the perm mission to share files, but a

0:46:02.640 --> 0:46:05.160
<v Speaker 1>lot of folks took the opportunity to use p t

0:46:05.280 --> 0:46:08.360
<v Speaker 1>P networks to distribute files that they didn't actually have

0:46:08.440 --> 0:46:12.000
<v Speaker 1>the rights to do that with, namely stuff like music

0:46:12.080 --> 0:46:16.320
<v Speaker 1>files and software. P TWOP allowed for the rapid sharing

0:46:16.400 --> 0:46:22.400
<v Speaker 1>of files across networks, uh exacerbated by organizations that specifically

0:46:22.560 --> 0:46:26.279
<v Speaker 1>made software that that prioritize that sort of stuff, and

0:46:26.320 --> 0:46:30.799
<v Speaker 1>that saw a spike in digital music privacy, which then

0:46:30.880 --> 0:46:33.920
<v Speaker 1>led to big media companies bringing the hammer down on

0:46:34.040 --> 0:46:37.680
<v Speaker 1>various people accused of pirating music files and it got

0:46:38.200 --> 0:46:43.000
<v Speaker 1>real ugly. But there's nothing inherently wrong or bad about

0:46:43.040 --> 0:46:46.319
<v Speaker 1>PTP networks. It's how you use a tool that makes

0:46:46.360 --> 0:46:50.719
<v Speaker 1>it good or bad in most cases. Anyway, all right,

0:46:51.280 --> 0:46:54.120
<v Speaker 1>that's enough for this episode. When we come back in

0:46:54.200 --> 0:46:56.920
<v Speaker 1>our next one. In this series, we will continue through

0:46:56.960 --> 0:47:00.680
<v Speaker 1>the ps and we still got probably two more episodes left.

0:47:00.719 --> 0:47:02.600
<v Speaker 1>I'm looking at I'm just looking at the list of

0:47:02.600 --> 0:47:06.799
<v Speaker 1>acronyms I have and feeling the weight of them on

0:47:06.840 --> 0:47:09.480
<v Speaker 1>my shoulders. But we we will get through them, and

0:47:09.520 --> 0:47:12.120
<v Speaker 1>then we'll move on to totally different types of topics.

0:47:12.719 --> 0:47:15.799
<v Speaker 1>And on that note, if you have suggestions for things

0:47:15.840 --> 0:47:17.600
<v Speaker 1>I should cover and tech stuff, reach out to me

0:47:17.640 --> 0:47:19.600
<v Speaker 1>on Twitter. A few of you have been doing that recently.

0:47:19.600 --> 0:47:22.439
<v Speaker 1>It's been awesome, and let me know what you would

0:47:22.480 --> 0:47:25.560
<v Speaker 1>like me to talk about. The Twitter handle for the

0:47:25.600 --> 0:47:29.040
<v Speaker 1>show is tech Stuff hs W, and I'll talk to

0:47:29.040 --> 0:47:37.879
<v Speaker 1>you again really soon. Text Stuff is an I Heart

0:47:37.960 --> 0:47:41.719
<v Speaker 1>Radio production. For more podcasts from my Heart Radio, visit

0:47:41.760 --> 0:47:44.799
<v Speaker 1>the i Heart Radio app, Apple Podcasts, or wherever you

0:47:44.880 --> 0:47:46.240
<v Speaker 1>listen to your favorite shows.