WEBVTT - Tech Glossary: From SEO to Y2K

0:00:04.400 --> 0:00:07.800
<v Speaker 1>Welcome to tech Stuff, a production from I Heart Radio.

0:00:12.039 --> 0:00:15.120
<v Speaker 1>Hey there, and welcome to tech Stuff. I'm your host,

0:00:15.320 --> 0:00:18.840
<v Speaker 1>Jonathan Strickland. I'm an executive producer with I Heart Radio

0:00:18.960 --> 0:00:22.320
<v Speaker 1>and I love of all things tech. And Okay, I

0:00:22.360 --> 0:00:25.680
<v Speaker 1>think we are now down to the home stretch here,

0:00:25.880 --> 0:00:29.800
<v Speaker 1>So if you've just joined us. Over the past several

0:00:29.880 --> 0:00:34.320
<v Speaker 1>long episodes, we've been going through popular acronyms and initialisms

0:00:34.440 --> 0:00:37.440
<v Speaker 1>in tech to explain what they mean and kind of

0:00:37.479 --> 0:00:40.600
<v Speaker 1>give some background on each of them. This is the

0:00:40.760 --> 0:00:46.040
<v Speaker 1>sixth and final episode for all those terms. Keeping in

0:00:46.080 --> 0:00:49.199
<v Speaker 1>mind that we did skip a couple, but that'll just

0:00:49.240 --> 0:00:51.479
<v Speaker 1>have to wait for a follow up at some point.

0:00:51.960 --> 0:00:55.800
<v Speaker 1>We are currently in the SYS, so let's get right

0:00:55.840 --> 0:01:00.440
<v Speaker 1>to it and not waste any more time. First is

0:01:00.800 --> 0:01:05.800
<v Speaker 1>s EO. This stands for Search Engine Optimization, and it's

0:01:05.840 --> 0:01:09.880
<v Speaker 1>pretty much what it sounds like. SEO covers a suite

0:01:10.000 --> 0:01:14.280
<v Speaker 1>of strategies and best practices that give web page creators

0:01:14.640 --> 0:01:18.560
<v Speaker 1>a better chance of ranking well in various search engines.

0:01:19.040 --> 0:01:23.200
<v Speaker 1>And really, when we say search engines, we mostly mean Google.

0:01:23.840 --> 0:01:28.920
<v Speaker 1>According to Global Stats, Google accounts for staggering ninety two

0:01:28.959 --> 0:01:33.319
<v Speaker 1>point two percent of the search engine market share so really,

0:01:34.280 --> 0:01:37.000
<v Speaker 1>focusing on anything else doesn't make any sense. You're just

0:01:37.080 --> 0:01:40.160
<v Speaker 1>you're targeting such a small audience that should really focus

0:01:40.200 --> 0:01:44.080
<v Speaker 1>on Google. But let's talk a little bit about why

0:01:44.360 --> 0:01:47.080
<v Speaker 1>s EO is such a big deal in the first place. Well,

0:01:47.120 --> 0:01:50.640
<v Speaker 1>according to Statista, a different site that tracks these sorts

0:01:50.680 --> 0:01:54.640
<v Speaker 1>of things, nearly thirty percent of all web traffic is

0:01:54.680 --> 0:01:58.560
<v Speaker 1>funneled through search. That was back in twenty nineteen at least,

0:01:58.880 --> 0:02:02.480
<v Speaker 1>so nearly a third of all traffic on the Internet

0:02:02.560 --> 0:02:06.200
<v Speaker 1>is dependent upon search. Search represents a way for people

0:02:06.240 --> 0:02:09.760
<v Speaker 1>to discover web content, but only if you rank well

0:02:09.880 --> 0:02:13.200
<v Speaker 1>enough to be found in a search right. If your

0:02:13.320 --> 0:02:18.280
<v Speaker 1>web page isn't showing up pretty early on in search results,

0:02:18.800 --> 0:02:20.440
<v Speaker 1>you might as well not even be in the listing

0:02:20.480 --> 0:02:23.639
<v Speaker 1>at all. And here's another statistic. This one is according

0:02:23.720 --> 0:02:28.920
<v Speaker 1>to webfx, only twenty of users ever bother to go

0:02:29.080 --> 0:02:32.040
<v Speaker 1>beyond the first page of search results. So that means

0:02:32.160 --> 0:02:36.160
<v Speaker 1>seventy of people using the web will use a search

0:02:36.200 --> 0:02:38.720
<v Speaker 1>result that appears on the first page and they never

0:02:38.760 --> 0:02:41.919
<v Speaker 1>go beyond that first page, which means if your website

0:02:41.919 --> 0:02:45.079
<v Speaker 1>doesn't pop up in that first page for whatever relevant

0:02:45.080 --> 0:02:48.280
<v Speaker 1>search criteria match your sight, then you're not going to

0:02:48.400 --> 0:02:52.680
<v Speaker 1>get very much web traffic through search, and it gets worse. Actually,

0:02:52.760 --> 0:02:55.519
<v Speaker 1>when you look at search results, you really only see

0:02:55.560 --> 0:02:58.240
<v Speaker 1>the first few listed before you need to start scrolling

0:02:58.280 --> 0:03:02.480
<v Speaker 1>down the page. We would typically call the search results

0:03:02.520 --> 0:03:06.680
<v Speaker 1>that appear below the screen as being below the fold.

0:03:07.040 --> 0:03:10.320
<v Speaker 1>That's term the dates back to newspapers, and some folks

0:03:10.520 --> 0:03:13.560
<v Speaker 1>won't even go beyond the fold, right, They'll just look

0:03:13.560 --> 0:03:15.840
<v Speaker 1>at the first view and they won't even scroll down.

0:03:15.880 --> 0:03:18.560
<v Speaker 1>So you really need to have your page rank very

0:03:18.639 --> 0:03:22.000
<v Speaker 1>high in search results for whatever the relevant search queries

0:03:22.040 --> 0:03:26.040
<v Speaker 1>are for your web page. Google uses a ranking system

0:03:26.080 --> 0:03:29.880
<v Speaker 1>for search results that has changed several times since it

0:03:29.919 --> 0:03:33.400
<v Speaker 1>first appeared. Now, in the old days, the criteria that

0:03:33.480 --> 0:03:37.520
<v Speaker 1>really determined where a specific result would appear within search

0:03:37.920 --> 0:03:40.880
<v Speaker 1>would include stuff like how old the site was, was

0:03:40.920 --> 0:03:43.920
<v Speaker 1>it had it been around for a while? Uh, how

0:03:43.920 --> 0:03:47.440
<v Speaker 1>many other sites were linking to this page? The idea

0:03:47.480 --> 0:03:49.520
<v Speaker 1>being that if a lot of other sites are linking

0:03:49.640 --> 0:03:53.520
<v Speaker 1>into a specific one, that specific one should be pretty good, right.

0:03:53.520 --> 0:03:56.119
<v Speaker 1>It's kind of like wisdom of the crowd and other

0:03:56.160 --> 0:03:59.920
<v Speaker 1>stuff like that really played a big part. Today it's

0:04:00.280 --> 0:04:03.160
<v Speaker 1>even more complicated, and that's what gave birth to the

0:04:03.240 --> 0:04:07.000
<v Speaker 1>idea of search engine optimization. So the goal is to

0:04:07.160 --> 0:04:10.680
<v Speaker 1>give a web page every advantage so that it has

0:04:10.720 --> 0:04:13.800
<v Speaker 1>the best chance of ranking high in search results for

0:04:14.200 --> 0:04:17.200
<v Speaker 1>the irrelevant queries. And a lot of the strategies in

0:04:17.440 --> 0:04:22.120
<v Speaker 1>s c O are individually pretty small, they can seem insignificant,

0:04:22.600 --> 0:04:25.800
<v Speaker 1>but when they're used collectively, they can all make a

0:04:25.839 --> 0:04:29.679
<v Speaker 1>big difference. That is, until Google changes its algorithm again

0:04:29.720 --> 0:04:33.320
<v Speaker 1>and all your strategies no longer work, which is a thing.

0:04:33.880 --> 0:04:36.960
<v Speaker 1>The dependence on search engines can become a really limiting

0:04:37.040 --> 0:04:41.120
<v Speaker 1>factor on web based companies. For websites that generate revenue

0:04:41.160 --> 0:04:44.760
<v Speaker 1>through ads and those that depend on search traffic, it

0:04:44.800 --> 0:04:47.839
<v Speaker 1>can be devastating when Google makes a change. A site

0:04:47.880 --> 0:04:51.240
<v Speaker 1>could be doing really well in search one quarter, and

0:04:51.279 --> 0:04:54.240
<v Speaker 1>then its performance the following quarter might plummet because of

0:04:54.240 --> 0:04:57.839
<v Speaker 1>a change in Google's algorithm, and that means that revenue

0:04:57.880 --> 0:05:01.920
<v Speaker 1>will plummet as well. It's tough these days. Search isn't

0:05:01.960 --> 0:05:04.640
<v Speaker 1>the only area that companies need to focus on. Social

0:05:04.680 --> 0:05:08.039
<v Speaker 1>networks are another big source of web traffic, and so

0:05:08.160 --> 0:05:11.080
<v Speaker 1>there are similar strategies meant to encourage people to visit

0:05:11.120 --> 0:05:15.400
<v Speaker 1>sites through links on platforms like Twitter, and Facebook. Moving

0:05:15.440 --> 0:05:19.839
<v Speaker 1>on next, we have s m S or Short Message Service,

0:05:20.560 --> 0:05:23.560
<v Speaker 1>which is kind of another way to say text messaging.

0:05:24.200 --> 0:05:28.160
<v Speaker 1>SMS is on top of communication protocols that both determine

0:05:28.200 --> 0:05:32.839
<v Speaker 1>how messages can transmit over telecommunications lines and also places

0:05:32.880 --> 0:05:36.839
<v Speaker 1>some limits on those communications. For example, the SMS allows

0:05:36.839 --> 0:05:39.760
<v Speaker 1>for transmission of messages of up to one hundred sixty

0:05:39.839 --> 0:05:43.160
<v Speaker 1>characters per message. This is why Twitter had a one

0:05:43.240 --> 0:05:46.880
<v Speaker 1>hundred forty character limit for a really long time. Twitter

0:05:47.000 --> 0:05:50.320
<v Speaker 1>was built to work with SMS so that people could

0:05:50.360 --> 0:05:54.240
<v Speaker 1>tweet or receive tweets via text on their phones, and

0:05:54.360 --> 0:05:56.520
<v Speaker 1>you know, twenty characters were says aside for stuff like

0:05:56.760 --> 0:06:02.880
<v Speaker 1>user handles. A variant of SMS, MMS or Multimedia Messaging Service,

0:06:03.160 --> 0:06:07.400
<v Speaker 1>which can send audio, video, and images via cellular communication.

0:06:08.320 --> 0:06:13.520
<v Speaker 1>All right, moving on s little oh big C SO

0:06:13.839 --> 0:06:15.720
<v Speaker 1>s o C, and there are actually quite a few

0:06:15.720 --> 0:06:18.720
<v Speaker 1>tech related topics that have the acronym s O C.

0:06:19.160 --> 0:06:22.719
<v Speaker 1>If you're actually talking all caps, you might mean Security

0:06:22.800 --> 0:06:26.440
<v Speaker 1>Operations center, which is a centralized department in charge of

0:06:26.480 --> 0:06:31.719
<v Speaker 1>dealing with computer security, typically within a company or other organization. Uh,

0:06:31.920 --> 0:06:34.880
<v Speaker 1>you could mean BIGES, little oh big C and talk

0:06:34.920 --> 0:06:38.320
<v Speaker 1>about separation of concerns. That refers to an approach in

0:06:38.400 --> 0:06:42.280
<v Speaker 1>computer programming, but I actually wanted to look at a

0:06:42.320 --> 0:06:46.279
<v Speaker 1>different version of s OC, that being system on a chip.

0:06:47.040 --> 0:06:49.719
<v Speaker 1>This is a type of integrated circuit that includes all

0:06:49.760 --> 0:06:53.520
<v Speaker 1>the basic components of a computer all on a single chip.

0:06:54.000 --> 0:06:58.120
<v Speaker 1>So that would include a processor, computer memory, some form

0:06:58.200 --> 0:07:02.040
<v Speaker 1>of storage, and in put in output ports. So as

0:07:02.080 --> 0:07:05.680
<v Speaker 1>the name suggests, it's a full computer system all located

0:07:05.760 --> 0:07:09.000
<v Speaker 1>on a single chip. This is all about manaturization and

0:07:09.040 --> 0:07:11.800
<v Speaker 1>building out mobile devices that have lots of features in them,

0:07:12.200 --> 0:07:15.040
<v Speaker 1>so they tend to be pretty power efficient as well.

0:07:15.440 --> 0:07:18.600
<v Speaker 1>And you can find s OC and stuff like smartphones

0:07:18.760 --> 0:07:21.840
<v Speaker 1>or car systems or Internet of Things devices. And that's

0:07:21.880 --> 0:07:25.160
<v Speaker 1>just a start. There are also lots of research facilities

0:07:25.200 --> 0:07:29.720
<v Speaker 1>that use system on a chip design for various scientific projects.

0:07:29.800 --> 0:07:32.600
<v Speaker 1>And they can even be used in laptops and small

0:07:32.680 --> 0:07:36.600
<v Speaker 1>PCs because they can be powerful and really efficient when

0:07:36.680 --> 0:07:39.440
<v Speaker 1>it comes to how much power they consume, how much

0:07:39.440 --> 0:07:43.280
<v Speaker 1>electricity they need to operate. Okay, burning through it, let's

0:07:43.280 --> 0:07:46.880
<v Speaker 1>get to the next one. S q L. This stands

0:07:46.920 --> 0:07:51.800
<v Speaker 1>for structured query language. This language relates to databases and

0:07:51.880 --> 0:07:54.320
<v Speaker 1>think of all the stuff you might do with a database,

0:07:54.440 --> 0:07:57.360
<v Speaker 1>such as you might want to update records in the database,

0:07:57.440 --> 0:07:59.240
<v Speaker 1>you might want to search a database, you might want

0:07:59.240 --> 0:08:03.400
<v Speaker 1>to pull U S Pacific record. All of those basic things. Well,

0:08:03.760 --> 0:08:07.520
<v Speaker 1>s q L is useful when you're dealing with structured data.

0:08:08.000 --> 0:08:11.080
<v Speaker 1>Some engineers at IBM originally developed s q L in

0:08:11.120 --> 0:08:14.480
<v Speaker 1>the nineteen seventies. Back then it was actually called Sequel.

0:08:14.760 --> 0:08:17.880
<v Speaker 1>Some people will still refer to s q L as Sequel,

0:08:18.560 --> 0:08:21.000
<v Speaker 1>but the company that really took the ball and ran

0:08:21.120 --> 0:08:25.080
<v Speaker 1>with it was Oracle, which built an entire industry around

0:08:25.200 --> 0:08:28.920
<v Speaker 1>database construction and management. So if you ever see s

0:08:29.000 --> 0:08:31.440
<v Speaker 1>q L, that's what it's in reference to. It's this

0:08:32.000 --> 0:08:37.080
<v Speaker 1>language that tends to be used regarding databases. Next, we

0:08:37.120 --> 0:08:41.120
<v Speaker 1>have S s D solid state drive. Now, in a

0:08:41.120 --> 0:08:43.840
<v Speaker 1>previous episode in this series, we talked about h d

0:08:43.960 --> 0:08:47.080
<v Speaker 1>d s, or hard disk drives, and how those storage

0:08:47.120 --> 0:08:51.320
<v Speaker 1>devices use physical platters to store data magnetically. A solid

0:08:51.360 --> 0:08:55.320
<v Speaker 1>state drive is a different type of data storage system.

0:08:55.480 --> 0:08:59.400
<v Speaker 1>Rather than using spinning platters and magnetic storage, s s

0:08:59.480 --> 0:09:02.880
<v Speaker 1>D s use an integrated circuit to store data. The

0:09:02.920 --> 0:09:06.559
<v Speaker 1>most common method is to use what is called flash memory.

0:09:06.600 --> 0:09:09.880
<v Speaker 1>This is a non volatile form of computer storage and

0:09:10.000 --> 0:09:13.480
<v Speaker 1>just as a reminder. That means that the information stored

0:09:13.520 --> 0:09:17.400
<v Speaker 1>in this kind of format will remain intact even if

0:09:17.480 --> 0:09:21.160
<v Speaker 1>the computer were to lose power. You can erase and

0:09:21.280 --> 0:09:24.480
<v Speaker 1>right over stuff that's stored in flash memory, so it's

0:09:24.480 --> 0:09:27.760
<v Speaker 1>not like it's set in stone, but otherwise information will

0:09:27.800 --> 0:09:32.120
<v Speaker 1>remain persistent within flash memory. S s d s have

0:09:32.440 --> 0:09:35.959
<v Speaker 1>several advantages over h d ds. For one thing, they

0:09:35.960 --> 0:09:39.679
<v Speaker 1>have no moving parts and so they are silent, and

0:09:39.920 --> 0:09:43.400
<v Speaker 1>HDD requires a motor to spin the platters, and depending

0:09:43.440 --> 0:09:46.760
<v Speaker 1>on the make of the hard disk drive, it can

0:09:46.840 --> 0:09:49.360
<v Speaker 1>sometimes be kind allowed when it starts to spin up

0:09:49.360 --> 0:09:52.560
<v Speaker 1>to speed. Uh They s s d s are are

0:09:52.640 --> 0:09:55.800
<v Speaker 1>more resistant to physical damage as well. If you were

0:09:55.840 --> 0:09:58.280
<v Speaker 1>to drop a hard disk drive, you would run the

0:09:58.360 --> 0:10:01.640
<v Speaker 1>risk of knocking the platters out of alignment or breaking

0:10:01.720 --> 0:10:04.920
<v Speaker 1>some mechanical component. But ss d s are a bit

0:10:04.960 --> 0:10:08.800
<v Speaker 1>more shock resistant than that. They are not damage proof.

0:10:09.000 --> 0:10:13.040
<v Speaker 1>I don't mean to suggest that they're like Superman and invulnerable.

0:10:13.720 --> 0:10:16.880
<v Speaker 1>S s d s are also typically much smaller, I

0:10:16.920 --> 0:10:20.520
<v Speaker 1>mean physically smaller than hard disk drives. That's also a

0:10:20.559 --> 0:10:23.400
<v Speaker 1>big advantage. It means you can make smaller form factors

0:10:23.400 --> 0:10:27.040
<v Speaker 1>for computers, as well as making lighter computers as well.

0:10:27.520 --> 0:10:29.600
<v Speaker 1>This gets to be pretty important when you're working with

0:10:29.640 --> 0:10:33.320
<v Speaker 1>stuff like laptops and portable computers and smartphones and that

0:10:33.400 --> 0:10:37.040
<v Speaker 1>kind of thing. Computers can pull information from ss d

0:10:37.200 --> 0:10:40.800
<v Speaker 1>s much more quickly than they can from HDDs. For

0:10:40.840 --> 0:10:44.200
<v Speaker 1>that reason, solid state drives are the preferred long term

0:10:44.240 --> 0:10:47.640
<v Speaker 1>storage solution for people who need to run very low

0:10:47.720 --> 0:10:53.000
<v Speaker 1>latency applications. That includes gamers. A good solid state drive

0:10:53.080 --> 0:10:55.520
<v Speaker 1>means that you have little to know load times when

0:10:55.559 --> 0:10:58.920
<v Speaker 1>you're initiating a program. So let's say you're playing a

0:10:58.960 --> 0:11:03.760
<v Speaker 1>really you know, resource intensive game. Let's say it's something

0:11:03.800 --> 0:11:08.200
<v Speaker 1>like a big open world game like an Assassin's Creed game. Well,

0:11:08.200 --> 0:11:10.559
<v Speaker 1>with a solid state drive, you might be able to

0:11:10.679 --> 0:11:14.400
<v Speaker 1>run all over the world map in that game and

0:11:14.480 --> 0:11:17.640
<v Speaker 1>never encounter a loading screen. That's a pretty big deal

0:11:17.800 --> 0:11:22.160
<v Speaker 1>for gamers. Generally speaking, solid state drives are much more

0:11:22.160 --> 0:11:24.720
<v Speaker 1>expensive than hard disk drives if you're looking at it

0:11:24.800 --> 0:11:28.719
<v Speaker 1>on a per gigabyte basis. Also, it's easier and far

0:11:28.840 --> 0:11:33.120
<v Speaker 1>less expensive to find really high capacity hard disk drives

0:11:33.400 --> 0:11:36.680
<v Speaker 1>compared to solid state drives. When you start looking at

0:11:36.679 --> 0:11:40.640
<v Speaker 1>the multi terrabyte range of storage, hard disk drives are

0:11:40.720 --> 0:11:45.840
<v Speaker 1>significantly less expensive than solid state drives, so it's not

0:11:45.960 --> 0:11:48.800
<v Speaker 1>as easy as saying that solid state drives are outright

0:11:48.920 --> 0:11:51.720
<v Speaker 1>better than hard disk drives. It actually depends on what

0:11:51.840 --> 0:11:55.040
<v Speaker 1>you want to use storage for and how much you

0:11:55.200 --> 0:11:57.800
<v Speaker 1>have to spend on it, like how much money you've got.

0:11:58.320 --> 0:12:01.400
<v Speaker 1>For gamers, solid state drive might be important for holding

0:12:01.520 --> 0:12:05.000
<v Speaker 1>whatever games are in current rotation of play, and then

0:12:05.040 --> 0:12:08.000
<v Speaker 1>you might want to supplemental hard disk drive that's standing

0:12:08.040 --> 0:12:11.199
<v Speaker 1>by that holds onto other titles that aren't in your

0:12:11.200 --> 0:12:16.080
<v Speaker 1>current player rotation. That's just an example. Moving on S

0:12:16.080 --> 0:12:20.000
<v Speaker 1>s i D. This stands for Service set identify Er.

0:12:21.000 --> 0:12:23.000
<v Speaker 1>This is more or less a fancy way of saying

0:12:23.160 --> 0:12:26.880
<v Speaker 1>network name. They can be up to thirty two characters long.

0:12:27.120 --> 0:12:31.040
<v Speaker 1>There's no minimum length, though, and routers typically come with

0:12:31.120 --> 0:12:34.240
<v Speaker 1>a default S s I D, usually something that relates

0:12:34.240 --> 0:12:38.200
<v Speaker 1>to whatever company manufactured that router, followed by some letters

0:12:38.280 --> 0:12:42.360
<v Speaker 1>or numbers or both. Generally speaking, it's usually a good

0:12:42.400 --> 0:12:45.600
<v Speaker 1>idea to go into the settings of your router. You

0:12:45.600 --> 0:12:48.080
<v Speaker 1>can usually find some pretty easy instructions on how to

0:12:48.160 --> 0:12:52.839
<v Speaker 1>log into your local router. It's not typically very hard,

0:12:53.000 --> 0:12:56.200
<v Speaker 1>and then you change the default name of your network

0:12:56.480 --> 0:12:59.840
<v Speaker 1>to something else. You can also pretty much name it

0:13:00.000 --> 0:13:03.000
<v Speaker 1>anything you like within those thirty two characters. So, for example,

0:13:03.480 --> 0:13:06.280
<v Speaker 1>I can use my phone to serve as a WiFi hotspot,

0:13:06.679 --> 0:13:10.720
<v Speaker 1>which I do occasionally whenever I can't access reliable WiFi,

0:13:11.240 --> 0:13:13.559
<v Speaker 1>but you know I do happen to have a strong

0:13:13.600 --> 0:13:16.240
<v Speaker 1>cell signal. I can use it as as sort of

0:13:16.240 --> 0:13:20.280
<v Speaker 1>like a WiFi modem. My phone's hot spot name is

0:13:20.520 --> 0:13:25.200
<v Speaker 1>totally trustworthy WiFi because I think that's funny, and because

0:13:25.200 --> 0:13:27.000
<v Speaker 1>it's the sort of name that would give other folks

0:13:27.080 --> 0:13:29.400
<v Speaker 1>just a bit of a pause before they would try

0:13:29.400 --> 0:13:31.920
<v Speaker 1>to connect to it, because like, but if it's totally

0:13:32.000 --> 0:13:36.439
<v Speaker 1>not trustworthy, I also protect it with a pretty strong password,

0:13:36.480 --> 0:13:38.760
<v Speaker 1>so actually connecting to that network is kind of tough.

0:13:39.360 --> 0:13:41.559
<v Speaker 1>But the reason you want to go in and change

0:13:41.600 --> 0:13:44.679
<v Speaker 1>the default name and password is because some companies use

0:13:44.679 --> 0:13:48.520
<v Speaker 1>a blanket default password, like using admin as a log

0:13:48.559 --> 0:13:50.920
<v Speaker 1>in and the word password as password, and that could

0:13:50.920 --> 0:13:53.520
<v Speaker 1>mean that someone else might get access to your network

0:13:53.600 --> 0:13:56.959
<v Speaker 1>and cause all sorts of mischief, from attempting to snoop

0:13:57.000 --> 0:13:59.840
<v Speaker 1>on what you're doing, to using your network as part

0:13:59.840 --> 0:14:03.400
<v Speaker 1>of like a bottan net attack on a target Typically,

0:14:03.679 --> 0:14:06.840
<v Speaker 1>routers have a sticker somewhere on them that lists the

0:14:06.840 --> 0:14:09.920
<v Speaker 1>default S s I D, though obviously if you go

0:14:10.040 --> 0:14:13.200
<v Speaker 1>through in settings and you change this, then that default

0:14:13.280 --> 0:14:16.120
<v Speaker 1>is no longer going to apply. You can use settings

0:14:16.120 --> 0:14:18.360
<v Speaker 1>on your computer or smartphone to look at S s

0:14:18.400 --> 0:14:20.920
<v Speaker 1>i D s within range. So if you were to

0:14:20.920 --> 0:14:23.760
<v Speaker 1>come into possession of a router and you discovered it

0:14:23.800 --> 0:14:26.040
<v Speaker 1>along the way that someone had changed the S s

0:14:26.080 --> 0:14:28.880
<v Speaker 1>i D, you could scan the available networks and look

0:14:28.960 --> 0:14:31.520
<v Speaker 1>to see if you could find the strongest signals and

0:14:31.640 --> 0:14:35.040
<v Speaker 1>try to identify which one is your actual router. Of course,

0:14:35.080 --> 0:14:38.200
<v Speaker 1>if someone also changed the default password, you might be

0:14:38.280 --> 0:14:41.720
<v Speaker 1>kind of stuck. Though. Many of these machines also have

0:14:41.880 --> 0:14:44.560
<v Speaker 1>a reset button so that you can reset it to

0:14:44.960 --> 0:14:49.720
<v Speaker 1>the UH the manufacturer default settings and get into it.

0:14:49.800 --> 0:14:52.760
<v Speaker 1>That way. You can also change settings on your router

0:14:52.920 --> 0:14:55.320
<v Speaker 1>so that it won't broadcast the S s i D

0:14:55.320 --> 0:14:58.800
<v Speaker 1>to nearby devices. That means that in this case, when

0:14:58.800 --> 0:15:02.200
<v Speaker 1>people search for networks, they won't see yours as they're

0:15:02.240 --> 0:15:04.920
<v Speaker 1>scanning the S s i D s. You can only

0:15:05.000 --> 0:15:08.720
<v Speaker 1>connect to such a network if you already know the

0:15:09.000 --> 0:15:12.200
<v Speaker 1>S s I D and you specifically direct your device

0:15:12.240 --> 0:15:16.200
<v Speaker 1>to connect with it. That requires manually changing wireless settings

0:15:16.200 --> 0:15:19.120
<v Speaker 1>on your device. Now, this sounds like it's a pretty

0:15:19.120 --> 0:15:21.360
<v Speaker 1>powerful way to protect yourself, but really it's more of

0:15:21.400 --> 0:15:24.440
<v Speaker 1>a surface level protection. Hiding your S S I D

0:15:24.600 --> 0:15:28.160
<v Speaker 1>might save you from the nubiast of nubes when it

0:15:28.200 --> 0:15:30.920
<v Speaker 1>comes to you know, bad actors, but folks who know

0:15:30.960 --> 0:15:33.920
<v Speaker 1>what they're doing can still track network traffic with the

0:15:34.000 --> 0:15:37.280
<v Speaker 1>right know how and the right tools. Maybe I'll reach

0:15:37.320 --> 0:15:40.120
<v Speaker 1>out to friend of the show, Shannon Morris to guests

0:15:40.120 --> 0:15:42.080
<v Speaker 1>on an episode to talk about the steps you can

0:15:42.120 --> 0:15:44.800
<v Speaker 1>take to best secure your home network. I think that

0:15:44.840 --> 0:15:49.000
<v Speaker 1>would be a valuable conversation to have. Okay, we've got

0:15:49.040 --> 0:15:51.720
<v Speaker 1>some acronyms and initialisms, but we're starting to head into

0:15:51.720 --> 0:15:55.240
<v Speaker 1>the home stretch. We're first going to take a quick break.

0:16:03.000 --> 0:16:06.480
<v Speaker 1>We're back and we're starting with S s L and

0:16:06.520 --> 0:16:10.320
<v Speaker 1>I reference this a little bit with HTTPS. SSL stands

0:16:10.360 --> 0:16:14.600
<v Speaker 1>for Secure Socket Layer. Uh, this is actually an outdated term.

0:16:14.680 --> 0:16:17.680
<v Speaker 1>The more current version is the t l S or

0:16:17.760 --> 0:16:21.960
<v Speaker 1>transport layer security. But in either case, the purpose is

0:16:22.040 --> 0:16:27.040
<v Speaker 1>to authenticate and encrypt communication links between networked computers. So

0:16:27.080 --> 0:16:31.360
<v Speaker 1>these are protocols that allow for secure and secret communications. Now,

0:16:31.360 --> 0:16:34.800
<v Speaker 1>when I say secret communications, I don't mean that the

0:16:34.840 --> 0:16:39.000
<v Speaker 1>fact that communication is happening is a secret. S s

0:16:39.160 --> 0:16:42.160
<v Speaker 1>L and t l s do not hide the fact

0:16:42.200 --> 0:16:47.040
<v Speaker 1>that communication is happening between computers. Instead, they encrypt and

0:16:47.200 --> 0:16:50.800
<v Speaker 1>obvious skate the nature of that communication. So it's kind

0:16:50.840 --> 0:16:54.000
<v Speaker 1>of like seeing two of your friends whispering to each other.

0:16:54.600 --> 0:16:56.680
<v Speaker 1>You know, you know they're up to no good, but

0:16:56.760 --> 0:17:00.280
<v Speaker 1>you don't know what they're specifically plotting. You might even

0:17:00.320 --> 0:17:03.200
<v Speaker 1>suspect that they're whispering about you, but you can't be

0:17:03.280 --> 0:17:05.959
<v Speaker 1>certain because you're not able to hear what they're saying.

0:17:06.400 --> 0:17:09.600
<v Speaker 1>So what I'm saying is, I know you're up to something,

0:17:09.880 --> 0:17:13.320
<v Speaker 1>Lena and Shay, and I don't approve, not one bit.

0:17:14.119 --> 0:17:17.720
<v Speaker 1>Knock it off. All right, all right, that got a

0:17:17.720 --> 0:17:21.399
<v Speaker 1>little personal. Let's let's get back on track. S s

0:17:21.680 --> 0:17:25.280
<v Speaker 1>L and t l s work by binding websites with

0:17:25.320 --> 0:17:29.200
<v Speaker 1>a digital document called an x dot five oh nine certificate,

0:17:29.600 --> 0:17:33.880
<v Speaker 1>which assigns pairs of keys to those websites. One key

0:17:34.040 --> 0:17:36.000
<v Speaker 1>is a public key. This is the key that the

0:17:36.000 --> 0:17:39.639
<v Speaker 1>website can share with the world. Anyone communicating with this

0:17:39.680 --> 0:17:43.760
<v Speaker 1>website through a browser does so using the public key,

0:17:43.800 --> 0:17:47.080
<v Speaker 1>which encrypts the messages that are sent to that website.

0:17:47.480 --> 0:17:51.000
<v Speaker 1>The only way to decrypt those messages to change it

0:17:51.040 --> 0:17:55.480
<v Speaker 1>back into meaningful information is to use the private key.

0:17:55.520 --> 0:17:58.600
<v Speaker 1>The website retains the private key for itself, it does

0:17:58.680 --> 0:18:02.640
<v Speaker 1>not share the private key. This way, all communications sent

0:18:02.680 --> 0:18:06.080
<v Speaker 1>to the website can only be decoded by the website alone,

0:18:06.600 --> 0:18:09.320
<v Speaker 1>unless some other entity were just about gain possession of

0:18:09.359 --> 0:18:12.200
<v Speaker 1>the private key or use a method like brute force

0:18:12.280 --> 0:18:15.200
<v Speaker 1>to try and replicate the private key. That brute force

0:18:15.320 --> 0:18:18.800
<v Speaker 1>thing is possible, depending upon the nature of the key. However,

0:18:18.840 --> 0:18:22.600
<v Speaker 1>it might be so difficult as to be practically impossible.

0:18:22.640 --> 0:18:25.879
<v Speaker 1>So in other words, yeah, you could, in theory be

0:18:26.000 --> 0:18:27.720
<v Speaker 1>able to do it, but it might take such a

0:18:27.760 --> 0:18:31.400
<v Speaker 1>long time to accomplish that you would be long dead

0:18:31.440 --> 0:18:34.320
<v Speaker 1>by the time of your computer finally managed it. In

0:18:34.359 --> 0:18:39.040
<v Speaker 1>addition to encrypting information, the website can digitally signed documents

0:18:39.080 --> 0:18:42.480
<v Speaker 1>that anyone with the public key can verify as being authentic.

0:18:43.040 --> 0:18:47.040
<v Speaker 1>So ss L and t l s help ensure that

0:18:47.119 --> 0:18:51.400
<v Speaker 1>private information like say a credit card number, remains secure

0:18:51.640 --> 0:18:55.680
<v Speaker 1>and that the entity you're sharing that information with is authenticated,

0:18:55.760 --> 0:18:59.399
<v Speaker 1>so you know for sure with whom you're sharing that information.

0:19:00.040 --> 0:19:03.520
<v Speaker 1>It's why it's important to look for that HTTPS or

0:19:03.600 --> 0:19:07.680
<v Speaker 1>that closed padlock symbol in your browser whenever you're interacting

0:19:07.720 --> 0:19:11.520
<v Speaker 1>with a site and sharing sensitive information. Next up, we

0:19:11.560 --> 0:19:15.879
<v Speaker 1>have TCP i P. Now collectively, these make up the

0:19:15.960 --> 0:19:21.000
<v Speaker 1>Internet Protocol Suite. Individually, these refer to the Transmission Control

0:19:21.080 --> 0:19:24.800
<v Speaker 1>Protocol or TCP and the Internet Protocol or i P,

0:19:25.280 --> 0:19:27.960
<v Speaker 1>and we nearly always referred to both of them together,

0:19:28.240 --> 0:19:31.760
<v Speaker 1>as they represent the set of communication protocols that allow

0:19:31.840 --> 0:19:35.159
<v Speaker 1>computers to connect together in a network and you know,

0:19:35.920 --> 0:19:40.560
<v Speaker 1>actually do stuff. These days, it seems natural that various

0:19:40.600 --> 0:19:43.720
<v Speaker 1>computational devices should be able to link up with each

0:19:43.720 --> 0:19:47.280
<v Speaker 1>other and communicate. It's been that way for decades now.

0:19:47.560 --> 0:19:51.080
<v Speaker 1>But once upon a time this wasn't true. Computers were

0:19:51.240 --> 0:19:55.720
<v Speaker 1>self contained silos. They served important purposes, but they did

0:19:55.760 --> 0:20:00.520
<v Speaker 1>so in isolation. Different computers made from different men factors

0:20:00.600 --> 0:20:05.159
<v Speaker 1>had proprietary means of operation, meaning there was no common language,

0:20:05.320 --> 0:20:08.360
<v Speaker 1>if you will, So even if you could connect two

0:20:08.440 --> 0:20:12.480
<v Speaker 1>different computers together, they wouldn't necessarily be able to interoperate.

0:20:12.880 --> 0:20:14.679
<v Speaker 1>It would be kind of like putting me on the

0:20:14.680 --> 0:20:18.080
<v Speaker 1>phone with someone who could only speak and understand Mandarin.

0:20:18.600 --> 0:20:20.800
<v Speaker 1>That person and I would be unable to make any

0:20:20.840 --> 0:20:25.440
<v Speaker 1>sort of meaningful conversation. In the nineteen sixties, the Department

0:20:25.440 --> 0:20:29.920
<v Speaker 1>of Defenses Advanced Research Project Agency, then called ARPA these

0:20:30.000 --> 0:20:33.199
<v Speaker 1>days we know it as DARPA set out to create

0:20:33.240 --> 0:20:37.040
<v Speaker 1>the means for computers to connect with one another in networks.

0:20:37.440 --> 0:20:40.639
<v Speaker 1>This would be the underlying foundation for modern computer networks

0:20:40.640 --> 0:20:44.000
<v Speaker 1>in general and the Internet a k a. The Network

0:20:44.200 --> 0:20:48.880
<v Speaker 1>of networks in particular. Vitten Surf and Robert Klein, who

0:20:48.920 --> 0:20:51.920
<v Speaker 1>both joined the project in the early nineteen seventies, would

0:20:51.920 --> 0:20:55.040
<v Speaker 1>pioneer the work on the basic set of protocols that

0:20:55.040 --> 0:20:58.880
<v Speaker 1>would allow for the network to communications between computers. Now,

0:20:58.920 --> 0:21:00.560
<v Speaker 1>to get them to the nuts and bolts of t

0:21:00.720 --> 0:21:04.200
<v Speaker 1>C P I P would require a full episode, or

0:21:04.240 --> 0:21:07.320
<v Speaker 1>probably more than one, so we're gonna save that for later.

0:21:07.640 --> 0:21:10.200
<v Speaker 1>It's good to know that they represent the basic set

0:21:10.240 --> 0:21:13.800
<v Speaker 1>of rules for computer networking. It's the set of instructions

0:21:13.840 --> 0:21:19.320
<v Speaker 1>that determine how communication between machines happens. Next up, we've

0:21:19.359 --> 0:21:22.760
<v Speaker 1>got UPS, and we are not talking about the delivery

0:21:22.840 --> 0:21:27.880
<v Speaker 1>service here. Instead, we're talking about uninterruptable power supplies. That's

0:21:27.920 --> 0:21:30.840
<v Speaker 1>what UPS stands for in this context, and as the

0:21:30.920 --> 0:21:34.680
<v Speaker 1>name implies, these are technologies that supply power to other

0:21:34.800 --> 0:21:38.960
<v Speaker 1>things even should a normal power source fail. So allow

0:21:39.000 --> 0:21:42.040
<v Speaker 1>me to paint a scenario, as the quister would say,

0:21:42.720 --> 0:21:46.840
<v Speaker 1>this is one that I have maybe personally experienced, possibly

0:21:47.160 --> 0:21:50.359
<v Speaker 1>on numerous occasions. So let us say that you have

0:21:50.480 --> 0:21:54.800
<v Speaker 1>an intrepid writer for a website, and this writer is

0:21:54.880 --> 0:21:58.440
<v Speaker 1>plugging away at an article plug plug plug. And let

0:21:58.520 --> 0:22:03.360
<v Speaker 1>us say that this optimist, naive young writer last saved

0:22:03.440 --> 0:22:06.359
<v Speaker 1>the document that they happened to be working on quite

0:22:06.480 --> 0:22:10.320
<v Speaker 1>some time ago. Maybe they've written a couple of pages

0:22:10.359 --> 0:22:13.200
<v Speaker 1>worth of work since the last time they saved the document.

0:22:13.640 --> 0:22:17.800
<v Speaker 1>And let us say that an inopportune moment, the power

0:22:17.840 --> 0:22:22.320
<v Speaker 1>goes out inside the office building where this brash, handsome

0:22:22.400 --> 0:22:26.520
<v Speaker 1>young writer is working, and because the writer is working

0:22:26.600 --> 0:22:31.520
<v Speaker 1>on a desktop computer without a battery backup, that machine

0:22:31.560 --> 0:22:34.400
<v Speaker 1>crashes and all the work that was created since that

0:22:34.520 --> 0:22:39.480
<v Speaker 1>last save disappears into the ether. And then our unnamed

0:22:39.480 --> 0:22:45.000
<v Speaker 1>but presumably dashingly handsome writer as all get out laments

0:22:45.080 --> 0:22:47.640
<v Speaker 1>the fact that they will now have to start over

0:22:47.800 --> 0:22:50.760
<v Speaker 1>back at their last save point and recreate all the

0:22:50.800 --> 0:22:53.280
<v Speaker 1>work that they had done in order to write about

0:22:53.320 --> 0:22:58.720
<v Speaker 1>how goose neck trailer hitches work. Mm hmm, Yeah, that

0:22:58.800 --> 0:23:02.560
<v Speaker 1>happened to me, and I could have been spared a

0:23:02.560 --> 0:23:05.800
<v Speaker 1>great deal of frustration if I had had my desktop

0:23:05.880 --> 0:23:11.280
<v Speaker 1>computer plugged into an uninterruptable power supply. So these devices

0:23:11.320 --> 0:23:14.520
<v Speaker 1>typically plug into a power source like a wall outlet,

0:23:14.920 --> 0:23:18.320
<v Speaker 1>and then you plug other devices into the UPS itself,

0:23:18.320 --> 0:23:20.919
<v Speaker 1>so the UPS plugs into the wall. You plug your

0:23:20.920 --> 0:23:24.480
<v Speaker 1>stuff into the UPS kind of like a power strip right.

0:23:25.400 --> 0:23:29.040
<v Speaker 1>In fact, some UPS devices look a lot like power strips,

0:23:29.600 --> 0:23:33.600
<v Speaker 1>so it's not just a power strip. The UPS also

0:23:33.680 --> 0:23:38.160
<v Speaker 1>contains a battery backup or some other means of storing electricity.

0:23:38.600 --> 0:23:41.240
<v Speaker 1>You know, maybe it's a supercapacitor or something, but battery

0:23:41.280 --> 0:23:44.920
<v Speaker 1>backup is pretty common. And if the normal power supply

0:23:45.280 --> 0:23:49.160
<v Speaker 1>that is power coming from the wall outlet suffers an outage,

0:23:49.600 --> 0:23:53.399
<v Speaker 1>the backup power supply, the battery or whatever comes on

0:23:53.560 --> 0:23:58.120
<v Speaker 1>practically instantaneously, at least fast enough so that it prevents

0:23:58.160 --> 0:24:01.760
<v Speaker 1>an interruption of power to you or devices. So any

0:24:01.760 --> 0:24:06.120
<v Speaker 1>devices you have plugged into the UPS continue to receive power. Now,

0:24:06.160 --> 0:24:11.199
<v Speaker 1>typically a UPS doesn't have a huge capacity for storing electricity,

0:24:11.240 --> 0:24:14.239
<v Speaker 1>so this isn't meant for you to just keep on

0:24:14.320 --> 0:24:17.320
<v Speaker 1>working away while the power is out. The battery life

0:24:17.359 --> 0:24:20.359
<v Speaker 1>might only allow for a few minutes of continued operation,

0:24:20.800 --> 0:24:22.280
<v Speaker 1>but that can be enough for you to be able

0:24:22.320 --> 0:24:25.040
<v Speaker 1>to save your progress and then shut down your equipment

0:24:25.080 --> 0:24:29.080
<v Speaker 1>through proper methods. This can help prevent damage to your

0:24:29.080 --> 0:24:31.960
<v Speaker 1>work and your equipment, and it can give you time

0:24:32.000 --> 0:24:34.280
<v Speaker 1>to get stuff in a safe mode while you wait

0:24:34.320 --> 0:24:37.800
<v Speaker 1>for the power to come back on. Frequently, a UPS

0:24:37.880 --> 0:24:41.000
<v Speaker 1>can also act as a surge protector, so I can

0:24:41.040 --> 0:24:45.800
<v Speaker 1>prevent voltage spikes from damaging equipment. Some UPS gadgets need

0:24:45.880 --> 0:24:48.880
<v Speaker 1>to be reset after a power outage. Some of them

0:24:48.880 --> 0:24:52.320
<v Speaker 1>will beep at you a lot. Typically they beat when

0:24:52.320 --> 0:24:54.639
<v Speaker 1>they are running low on battery power, and this is

0:24:54.640 --> 0:24:57.840
<v Speaker 1>a message that you really do need to start shutting

0:24:57.880 --> 0:25:00.000
<v Speaker 1>down all of your plugged in devices if you don't

0:25:00.040 --> 0:25:03.359
<v Speaker 1>want them to suddenly lose power. But they can also

0:25:03.480 --> 0:25:06.879
<v Speaker 1>beep as an indication of capacity overload. In that case,

0:25:07.000 --> 0:25:10.080
<v Speaker 1>you have plugged in devices that have too great a

0:25:10.200 --> 0:25:13.439
<v Speaker 1>demand for power for the UPS to accommodate, and you

0:25:13.480 --> 0:25:18.520
<v Speaker 1>need to distribute that load across other devices. Next, we

0:25:18.600 --> 0:25:22.680
<v Speaker 1>have you r L. That stands for Uniform Resource Locator,

0:25:23.040 --> 0:25:26.280
<v Speaker 1>but you could just call it a web address. Essentially,

0:25:26.320 --> 0:25:29.239
<v Speaker 1>this is what tells computers where on a network a

0:25:29.280 --> 0:25:34.680
<v Speaker 1>particular resource resides. It's kind of like your physical address,

0:25:34.720 --> 0:25:37.600
<v Speaker 1>so u r L relates to a specific location on

0:25:37.640 --> 0:25:41.560
<v Speaker 1>a specific server within a specific network. When you type

0:25:41.560 --> 0:25:44.040
<v Speaker 1>out a web address and a browser, you're essentially telling

0:25:44.080 --> 0:25:46.800
<v Speaker 1>the browser I want to see the stuff that is

0:25:46.840 --> 0:25:49.800
<v Speaker 1>stored at this location, and the browser sends out a

0:25:49.840 --> 0:25:53.640
<v Speaker 1>request up through your network to the Internet. Then routers

0:25:53.680 --> 0:25:57.000
<v Speaker 1>direct that request to the proper destination, and thanks to

0:25:57.040 --> 0:25:59.840
<v Speaker 1>that handy dandy u r L that cross references to

0:26:00.200 --> 0:26:04.600
<v Speaker 1>that location, your request arrives there at its proper destination.

0:26:05.200 --> 0:26:07.440
<v Speaker 1>Or if you miss type the web address, you get

0:26:07.480 --> 0:26:13.080
<v Speaker 1>something else, probably an error, but possibly someone's page, especially

0:26:13.119 --> 0:26:17.040
<v Speaker 1>if someone is squatting on commonly made typos. That's still

0:26:17.040 --> 0:26:20.280
<v Speaker 1>a thing. Tim berners Lee, the guy who invented the

0:26:20.280 --> 0:26:23.600
<v Speaker 1>Worldwide Web, defined u r L s in an RFC.

0:26:24.200 --> 0:26:27.520
<v Speaker 1>Do you remember RFCs? That stands for Request for Comments.

0:26:27.520 --> 0:26:32.320
<v Speaker 1>I covered it in the last episode. Next, we have USB.

0:26:32.920 --> 0:26:36.000
<v Speaker 1>This stands for Universal Serial Bus and it is a

0:26:36.040 --> 0:26:40.840
<v Speaker 1>standardized connection for all sorts of stuff. And boy, howdy,

0:26:40.920 --> 0:26:46.160
<v Speaker 1>am I thankful for it because it really made things easy.

0:26:46.480 --> 0:26:49.520
<v Speaker 1>I'm not even being facetious here. USB s are fantastic.

0:26:49.880 --> 0:26:52.720
<v Speaker 1>So in the old old days we would use all

0:26:52.760 --> 0:26:55.639
<v Speaker 1>sorts of different types of connection ports to connect stuff

0:26:55.720 --> 0:26:59.560
<v Speaker 1>to other stuff. And really I'm focusing primarily on computers

0:26:59.600 --> 0:27:01.639
<v Speaker 1>here because I feel that that's what most of us

0:27:01.680 --> 0:27:04.919
<v Speaker 1>associate with this kind of thing, although I will allow

0:27:04.960 --> 0:27:07.639
<v Speaker 1>that people who are really into home entertainment centers or

0:27:07.760 --> 0:27:12.600
<v Speaker 1>or audio setups are also really familiar with the the uh,

0:27:12.640 --> 0:27:15.120
<v Speaker 1>the burdens of having to make lots of different connections

0:27:15.160 --> 0:27:18.639
<v Speaker 1>using different types of cables and ports. Anyway, back in

0:27:18.680 --> 0:27:22.080
<v Speaker 1>the old days, computers had all sorts of different connection

0:27:22.160 --> 0:27:25.600
<v Speaker 1>ports on them, and I'm talking about stuff like parallel ports,

0:27:25.800 --> 0:27:30.199
<v Speaker 1>serial ports, more specific stuff like PS two connectors or

0:27:30.320 --> 0:27:34.480
<v Speaker 1>D I N connectors. Some game controllers required a special

0:27:34.520 --> 0:27:38.399
<v Speaker 1>game port. Typically you would find those on some of

0:27:38.400 --> 0:27:41.760
<v Speaker 1>the more popular sound cards. Back in the day. Sound

0:27:41.760 --> 0:27:44.560
<v Speaker 1>cards were a thing too, because you didn't have uh

0:27:44.640 --> 0:27:49.040
<v Speaker 1>integrated sound chips in computers, so you would have to

0:27:49.160 --> 0:27:51.400
<v Speaker 1>install a sound card in your computer, and on the

0:27:51.480 --> 0:27:53.800
<v Speaker 1>back plate of your PC you would have a new

0:27:53.880 --> 0:27:56.879
<v Speaker 1>port there where you could plug in a controller. It

0:27:56.920 --> 0:27:59.919
<v Speaker 1>was a real mess. Some of these ports required expand

0:28:00.080 --> 0:28:02.040
<v Speaker 1>in cards, and you would have to slot those into

0:28:02.040 --> 0:28:05.120
<v Speaker 1>your motherboard. Just like the sound cards I mentioned, Your

0:28:05.200 --> 0:28:08.000
<v Speaker 1>keyboard might need to go into one specific port, your

0:28:08.040 --> 0:28:11.560
<v Speaker 1>mouse in another. And then in the ninety nineties that

0:28:11.640 --> 0:28:14.439
<v Speaker 1>began to change. That's when we saw the introduction of

0:28:14.520 --> 0:28:18.639
<v Speaker 1>the USB standard. USB allows for the transmission of data

0:28:18.720 --> 0:28:21.720
<v Speaker 1>and power over the same cable, and it did not

0:28:21.840 --> 0:28:25.560
<v Speaker 1>take long for computer accessory manufacturers to start making stuff

0:28:25.600 --> 0:28:30.600
<v Speaker 1>like USB keyboards or USB computer mice. Uh. And later

0:28:30.600 --> 0:28:33.560
<v Speaker 1>on we saw more stuff like computer printers and docking

0:28:33.640 --> 0:28:36.720
<v Speaker 1>stations and stuff like you know, you know, a docking

0:28:36.760 --> 0:28:38.920
<v Speaker 1>station for an MP three player, that kind of thing.

0:28:39.240 --> 0:28:42.719
<v Speaker 1>The USB standard itself also evolved, with more recent versions

0:28:42.760 --> 0:28:47.160
<v Speaker 1>capable of carrying far more data per second than older versions.

0:28:47.640 --> 0:28:49.880
<v Speaker 1>And this meant that now suddenly you had a universal

0:28:50.000 --> 0:28:53.480
<v Speaker 1>kind of connection port and universal cable system where you

0:28:53.520 --> 0:28:56.560
<v Speaker 1>could connect all your different stuff to any of those

0:28:56.600 --> 0:29:00.000
<v Speaker 1>available ports on your computer. You didn't have to remember, oh,

0:29:00.240 --> 0:29:03.880
<v Speaker 1>this one is for the printer, this one is for

0:29:04.000 --> 0:29:08.600
<v Speaker 1>an extra display, Like if it was a USB then

0:29:08.840 --> 0:29:10.920
<v Speaker 1>you can plug it into any port that was USB

0:29:11.200 --> 0:29:14.400
<v Speaker 1>on your machine. With the USB three point oh standard,

0:29:14.440 --> 0:29:17.640
<v Speaker 1>we're looking at transmission speeds of five gigabits per second

0:29:18.120 --> 0:29:21.600
<v Speaker 1>and beyond. USB three point two generation two by two

0:29:21.640 --> 0:29:24.240
<v Speaker 1>has a top speed of ten gigabits per second across

0:29:24.320 --> 0:29:26.840
<v Speaker 1>two lanes of transmission, which gives you a total of

0:29:26.840 --> 0:29:30.320
<v Speaker 1>twenty gigabits per second bandwidth. So now we can use

0:29:30.400 --> 0:29:33.480
<v Speaker 1>USBs for stuff far more demanding than just powering a

0:29:33.560 --> 0:29:38.040
<v Speaker 1>computer mouse. Now, there's still the issue of various connectors

0:29:38.080 --> 0:29:40.720
<v Speaker 1>even with USB. I mean, there's nothing like mixing up

0:29:41.240 --> 0:29:46.320
<v Speaker 1>USB B many with the USB B micro, with USB

0:29:46.640 --> 0:29:49.600
<v Speaker 1>C connectors and all that kind of stuff. But still

0:29:49.840 --> 0:29:52.640
<v Speaker 1>it's leagues better than the old days of the mishmash

0:29:52.720 --> 0:29:57.600
<v Speaker 1>of connectors, and it makes managing that stuff way easier. Next,

0:29:57.720 --> 0:30:00.920
<v Speaker 1>we have v g A, the stands for video graphics Array.

0:30:01.400 --> 0:30:04.280
<v Speaker 1>Speaking of connectors, this was one of them, and some

0:30:04.360 --> 0:30:07.880
<v Speaker 1>computer manufacturers continue to support v g A connections, though

0:30:08.360 --> 0:30:11.160
<v Speaker 1>not nearly as many as they used to. These connectors

0:30:11.240 --> 0:30:14.400
<v Speaker 1>support computer video output, and so this is a port

0:30:14.440 --> 0:30:16.800
<v Speaker 1>that you would use to connect a computer to a

0:30:16.800 --> 0:30:21.280
<v Speaker 1>compatible display or monitor. The connectors have three rows of

0:30:21.360 --> 0:30:23.920
<v Speaker 1>five holes in them, and those line up with the

0:30:24.000 --> 0:30:26.960
<v Speaker 1>fifteen pens that are in the cables. You would use

0:30:27.040 --> 0:30:30.680
<v Speaker 1>to connect your computer to a display. These days, you

0:30:30.720 --> 0:30:35.480
<v Speaker 1>typically see this replaced with more recent technologies like hd M. I. Okay,

0:30:36.120 --> 0:30:39.160
<v Speaker 1>we have one last batch of acronyms and initialisms to

0:30:39.160 --> 0:30:41.040
<v Speaker 1>get through. Let's see if I can do this without

0:30:41.080 --> 0:30:45.120
<v Speaker 1>running super long. But first, let's take a quick break.

0:30:52.640 --> 0:30:56.840
<v Speaker 1>All right, here we go. VM. This stands for virtual machine,

0:30:56.920 --> 0:31:00.320
<v Speaker 1>which I touched on a little bit in this aries.

0:31:00.440 --> 0:31:04.200
<v Speaker 1>A virtual machine is the emulation of a computer system.

0:31:04.560 --> 0:31:08.000
<v Speaker 1>You might use specialized software, some specialized hardware, or a

0:31:08.000 --> 0:31:10.120
<v Speaker 1>combination of the two in order to make this happen.

0:31:10.400 --> 0:31:11.920
<v Speaker 1>And there are a lot of reasons why you would

0:31:11.960 --> 0:31:15.040
<v Speaker 1>want to run a virtual machine on top of actual

0:31:15.120 --> 0:31:19.480
<v Speaker 1>physical hardware. For example, you might have a really powerful

0:31:19.520 --> 0:31:23.760
<v Speaker 1>computer and you want to run separate processes that should

0:31:23.800 --> 0:31:27.600
<v Speaker 1>not intermingle on a single machine. So rather than buy

0:31:27.640 --> 0:31:30.880
<v Speaker 1>a second machine and then divide up the tasks, you

0:31:30.920 --> 0:31:35.440
<v Speaker 1>create virtual machines on your one physical computer, and each

0:31:35.520 --> 0:31:39.960
<v Speaker 1>virtual machine acts like its own standalone computer. They handle

0:31:40.200 --> 0:31:43.400
<v Speaker 1>a specific task, and the two tasks won't come into

0:31:43.400 --> 0:31:46.240
<v Speaker 1>contact with each other. Virtual machines can each have their

0:31:46.280 --> 0:31:51.240
<v Speaker 1>own dedicated computer resources. Or maybe you've got a computer

0:31:51.360 --> 0:31:54.240
<v Speaker 1>like a Mac, but you want to run PC software

0:31:54.240 --> 0:31:58.320
<v Speaker 1>on it, so you create a virtual PC machine running

0:31:58.360 --> 0:32:01.760
<v Speaker 1>on top of the MAC system. The virtual machine emulates

0:32:01.800 --> 0:32:05.840
<v Speaker 1>the physical hardware and architecture of a PC and allows

0:32:05.880 --> 0:32:10.120
<v Speaker 1>you to run PC software on this virtual platform. Virtualization

0:32:10.400 --> 0:32:13.600
<v Speaker 1>is also really important for stuff like data centers, but

0:32:13.680 --> 0:32:17.320
<v Speaker 1>I'll say further discussion for a future episode. Next, we

0:32:17.360 --> 0:32:22.120
<v Speaker 1>have VPN. This stands for virtual private networks. These are

0:32:22.240 --> 0:32:26.240
<v Speaker 1>means of creating a private network connection, particularly when you're

0:32:26.360 --> 0:32:29.880
<v Speaker 1>on a public like WiFi network. The purpose of a

0:32:29.960 --> 0:32:33.800
<v Speaker 1>VPN is to encrypt your Internet activities and disguise your

0:32:33.880 --> 0:32:37.400
<v Speaker 1>online identity, something that can be really important if you

0:32:37.480 --> 0:32:40.600
<v Speaker 1>happen to be working from say a public WiFi hotspot

0:32:41.000 --> 0:32:44.000
<v Speaker 1>like in a coffee shop or something. The way this

0:32:44.040 --> 0:32:47.840
<v Speaker 1>works is that you connect to a VPN directly. Your

0:32:47.880 --> 0:32:53.120
<v Speaker 1>machine essentially makes a connection with the VPN. Then the

0:32:53.200 --> 0:32:57.240
<v Speaker 1>VPN access kind of like your liaison. When you want

0:32:57.280 --> 0:33:00.520
<v Speaker 1>to visit a website, for example, your request for goes

0:33:00.560 --> 0:33:03.040
<v Speaker 1>to the VPN and the vp N kind of acts

0:33:03.080 --> 0:33:06.920
<v Speaker 1>like a proxy to retrieve the website data, then sends

0:33:06.920 --> 0:33:09.800
<v Speaker 1>that data to you and it's all encrypted. To the

0:33:09.840 --> 0:33:12.600
<v Speaker 1>website on the other end, it looks like all the

0:33:12.640 --> 0:33:16.120
<v Speaker 1>requests are coming from the VPN, not from you, So

0:33:16.800 --> 0:33:19.160
<v Speaker 1>you know, if you were to go to how stuff

0:33:19.160 --> 0:33:22.160
<v Speaker 1>works dot com, how stuff works dot Com would see

0:33:22.160 --> 0:33:24.600
<v Speaker 1>the traffic coming from the VPN, but would not see

0:33:24.680 --> 0:33:28.600
<v Speaker 1>that go further back to you. This is handy if

0:33:28.640 --> 0:33:31.480
<v Speaker 1>you want to have some secure connections and not worry

0:33:31.480 --> 0:33:34.280
<v Speaker 1>about someone, whether it's a hacker or an I s

0:33:34.320 --> 0:33:36.880
<v Speaker 1>P or the admin of the hot spot that you're using,

0:33:37.080 --> 0:33:40.160
<v Speaker 1>to know what you're doing. Some companies require employees to

0:33:40.240 --> 0:33:43.920
<v Speaker 1>use a VPN before accessing internal systems to help mitigate

0:33:43.960 --> 0:33:48.400
<v Speaker 1>the risk of hacker intrusions. Another way people use VPNs

0:33:48.480 --> 0:33:51.800
<v Speaker 1>is to bypass region locking. So let's say you want

0:33:51.800 --> 0:33:55.320
<v Speaker 1>to access a service in another country, but you get

0:33:55.320 --> 0:33:58.520
<v Speaker 1>a message saying that you're not within the regional service

0:33:58.600 --> 0:34:01.280
<v Speaker 1>area for that and this happens a lot with media

0:34:01.400 --> 0:34:06.040
<v Speaker 1>based services like streaming video, So you could use a

0:34:06.120 --> 0:34:09.279
<v Speaker 1>VPN to make it appear as though you are in

0:34:09.400 --> 0:34:13.640
<v Speaker 1>that country and while you can access stuff. That is

0:34:13.680 --> 0:34:18.080
<v Speaker 1>assuming that the media company hasn't blacklisted the VPN servers

0:34:18.160 --> 0:34:22.040
<v Speaker 1>IP address and said this is a VPN, we don't

0:34:22.080 --> 0:34:26.080
<v Speaker 1>want to allow traffic to it. I don't advocate for

0:34:26.160 --> 0:34:29.080
<v Speaker 1>this approach. I would rather see region locking just kind

0:34:29.080 --> 0:34:32.799
<v Speaker 1>of go away, rather than suggest you find ways around it.

0:34:33.160 --> 0:34:37.480
<v Speaker 1>But anyway, VPNs are an important component to secure web browsing.

0:34:37.960 --> 0:34:41.080
<v Speaker 1>It's also good to research VPNs before joining one. Some

0:34:41.280 --> 0:34:44.640
<v Speaker 1>vBNS keep a record of users that could potentially become

0:34:44.640 --> 0:34:47.400
<v Speaker 1>a problem if some other entity ever got hold of it.

0:34:48.040 --> 0:34:52.239
<v Speaker 1>Other VPNs make it a practice to never maintain any

0:34:52.320 --> 0:34:54.960
<v Speaker 1>kind of record at all, so your use of the

0:34:55.000 --> 0:34:58.799
<v Speaker 1>service would never become public knowledge, even if, say, law

0:34:58.880 --> 0:35:02.280
<v Speaker 1>enforcement were to go out after it. Next up is VR.

0:35:02.520 --> 0:35:05.839
<v Speaker 1>This one's easy. It's virtual reality basically refers to any

0:35:05.880 --> 0:35:09.400
<v Speaker 1>system in which some, most, or all of your sensory

0:35:09.480 --> 0:35:13.000
<v Speaker 1>input is coming courtesy of a computer system. Typically we

0:35:13.040 --> 0:35:17.080
<v Speaker 1>associated with systems that include head mounted displays. That means

0:35:17.120 --> 0:35:19.640
<v Speaker 1>that everything you see comes from a computer source, and

0:35:19.680 --> 0:35:22.800
<v Speaker 1>it's usually paired with technology that allows for head tracking,

0:35:23.280 --> 0:35:26.400
<v Speaker 1>so that when you turn your head, the computer reflects

0:35:26.440 --> 0:35:29.880
<v Speaker 1>this with a change in your perspective. It's a subtype

0:35:29.920 --> 0:35:33.160
<v Speaker 1>of mixed reality, along with a R or augmented reality,

0:35:33.200 --> 0:35:35.760
<v Speaker 1>which we covered way back at the beginning of this series.

0:35:36.560 --> 0:35:40.319
<v Speaker 1>Next is W three C. The number three so W

0:35:40.560 --> 0:35:44.640
<v Speaker 1>three C. This stands for the Worldwide Web Consortium, which

0:35:44.680 --> 0:35:47.480
<v Speaker 1>is a group that develops standards for use on the

0:35:47.520 --> 0:35:51.239
<v Speaker 1>Worldwide Web. Tim berners Lee pops up again here, as

0:35:51.280 --> 0:35:55.760
<v Speaker 1>he founded and currently leads the organization. The Consortium mainly

0:35:55.800 --> 0:35:58.480
<v Speaker 1>focuses on getting all the various players in the Web

0:35:58.560 --> 0:36:01.280
<v Speaker 1>to work on an agreed upon on set of standards

0:36:01.320 --> 0:36:04.239
<v Speaker 1>so that the experience of accessing the Web remains consistent

0:36:04.320 --> 0:36:07.960
<v Speaker 1>no matter what browser or platforms someone happens to be using.

0:36:08.640 --> 0:36:13.400
<v Speaker 1>Next up, W A N. This is a wide area network.

0:36:13.640 --> 0:36:15.920
<v Speaker 1>So in a previous episode we talked about l a

0:36:16.080 --> 0:36:20.120
<v Speaker 1>N s lands or local area networks. Well, a w

0:36:20.320 --> 0:36:22.879
<v Speaker 1>a N is just a really big network. It's one

0:36:22.920 --> 0:36:26.080
<v Speaker 1>that spans a large geographic region. So we're talking about

0:36:26.080 --> 0:36:29.239
<v Speaker 1>a network that measures at least half a mile across,

0:36:29.480 --> 0:36:33.560
<v Speaker 1>but can be much larger. These networks, like lands, can

0:36:33.640 --> 0:36:37.520
<v Speaker 1>be purely self contained. That means you can have a

0:36:37.680 --> 0:36:40.360
<v Speaker 1>w a N that does not connect out to the Internet,

0:36:41.160 --> 0:36:44.640
<v Speaker 1>or they might have interconnections with other types of networks.

0:36:45.719 --> 0:36:48.319
<v Speaker 1>Next up, we've got w e P. This stands for

0:36:48.480 --> 0:36:52.480
<v Speaker 1>Wired Equivalent Privacy. It's a type of security algorithm for

0:36:52.600 --> 0:36:55.279
<v Speaker 1>use with wireless networks. So the idea is that this

0:36:55.400 --> 0:36:59.719
<v Speaker 1>security algorithm would provide the same sort of privacy that

0:36:59.840 --> 0:37:03.279
<v Speaker 1>you would experience if you had physically connected all the

0:37:03.320 --> 0:37:07.320
<v Speaker 1>computers in your network together with cables. So you're trying

0:37:07.320 --> 0:37:10.200
<v Speaker 1>to prevent the chance for some outside force to snoop

0:37:10.200 --> 0:37:13.560
<v Speaker 1>in on what's going on with the network. And obviously

0:37:13.600 --> 0:37:16.040
<v Speaker 1>this is something to be concerned about when you're dealing

0:37:16.040 --> 0:37:20.000
<v Speaker 1>with wireless networks, right. I mean, all communications are relying

0:37:20.080 --> 0:37:23.319
<v Speaker 1>on radio waves, which can be intercepted by anyone with

0:37:23.360 --> 0:37:28.160
<v Speaker 1>a compatible tuner and antenna. W EP became a security

0:37:28.200 --> 0:37:33.600
<v Speaker 1>standard back in n It uses encryption to protect network communications,

0:37:34.120 --> 0:37:36.720
<v Speaker 1>but w e P has fallen out of favor since

0:37:36.760 --> 0:37:40.400
<v Speaker 1>the mid two thousand's. It's not seen as being particularly secure.

0:37:40.960 --> 0:37:43.439
<v Speaker 1>And our next entry will pick up where w EP

0:37:43.600 --> 0:37:45.879
<v Speaker 1>left off, so let's move on to it. That would

0:37:45.880 --> 0:37:51.000
<v Speaker 1>be w p A. This stands for WiFi Protected Access

0:37:51.040 --> 0:37:54.839
<v Speaker 1>and this family of security systems are the current recommended

0:37:54.880 --> 0:37:58.239
<v Speaker 1>ones to have in use for Wi Fi networks. There

0:37:58.280 --> 0:38:01.120
<v Speaker 1>are three generations of this current LEE. You've got w

0:38:01.280 --> 0:38:04.360
<v Speaker 1>P A, w P A two, and w p A three.

0:38:04.719 --> 0:38:07.040
<v Speaker 1>To get into the full details of this will require

0:38:07.120 --> 0:38:11.120
<v Speaker 1>a separate episode because it gets really technical, but it's

0:38:11.120 --> 0:38:13.600
<v Speaker 1>a good thing to remember that if you have options

0:38:13.640 --> 0:38:16.480
<v Speaker 1>to set your network security to either w e P

0:38:16.760 --> 0:38:20.400
<v Speaker 1>or w P A, you should go with w p A.

0:38:20.480 --> 0:38:23.840
<v Speaker 1>More and more devices infect Almost pretty much every device

0:38:24.239 --> 0:38:27.759
<v Speaker 1>made now is going to be w p A compatible.

0:38:28.239 --> 0:38:30.520
<v Speaker 1>If you're working with really old tech, you might have

0:38:30.560 --> 0:38:34.640
<v Speaker 1>some that aren't, but generally speaking, networks should be w

0:38:34.800 --> 0:38:38.399
<v Speaker 1>p A, preferably w P A three. Next up, we've

0:38:38.440 --> 0:38:43.640
<v Speaker 1>got whizzy wig or w y s I w y

0:38:43.960 --> 0:38:48.319
<v Speaker 1>G whizzy wig. It stands for what you see is

0:38:48.360 --> 0:38:51.520
<v Speaker 1>what you get, and it refers to any type of

0:38:51.680 --> 0:38:55.239
<v Speaker 1>editing software in which what you're seeing as you edit

0:38:55.840 --> 0:38:57.920
<v Speaker 1>is pretty much what you're going to get with the

0:38:57.960 --> 0:39:01.400
<v Speaker 1>final finished product. This is easier for me to explain

0:39:01.520 --> 0:39:04.040
<v Speaker 1>with an old example. So if you've been listening to

0:39:04.080 --> 0:39:06.040
<v Speaker 1>this series, you heard me talk about when I was

0:39:06.080 --> 0:39:10.520
<v Speaker 1>making my first web pages decades ago, using a text

0:39:10.680 --> 0:39:14.400
<v Speaker 1>editor to write out all the HTML code. The text

0:39:14.440 --> 0:39:17.759
<v Speaker 1>document was a collection of markup language tags and then

0:39:17.800 --> 0:39:20.480
<v Speaker 1>the content, and on casual glance it looked like a

0:39:20.520 --> 0:39:23.280
<v Speaker 1>real mess. I mean, you could scan through the document

0:39:23.320 --> 0:39:24.960
<v Speaker 1>and kind of get an idea of what the web

0:39:24.960 --> 0:39:27.799
<v Speaker 1>page was all about. But if you just looked at

0:39:27.800 --> 0:39:30.160
<v Speaker 1>it casually, it looked like a bunch of symbols and

0:39:30.280 --> 0:39:33.080
<v Speaker 1>letters and numbers and didn't have a whole lot of

0:39:33.120 --> 0:39:37.000
<v Speaker 1>meaning to it. Flash forward a few years and companies

0:39:37.040 --> 0:39:40.000
<v Speaker 1>began to develop software that would let people develop a

0:39:40.040 --> 0:39:44.200
<v Speaker 1>web page without having to manage the actual HTML code.

0:39:44.280 --> 0:39:47.120
<v Speaker 1>It was more like a word processor. You could view

0:39:47.160 --> 0:39:50.440
<v Speaker 1>the document as if it were a web page in progress,

0:39:50.840 --> 0:39:53.960
<v Speaker 1>long before you ever uploaded it to a server. So

0:39:54.000 --> 0:39:56.879
<v Speaker 1>what you see is what you get. The view you

0:39:56.920 --> 0:39:59.000
<v Speaker 1>have of your web page in progress is what it

0:39:59.000 --> 0:40:01.279
<v Speaker 1>would look like if some one were to visit it

0:40:01.320 --> 0:40:05.040
<v Speaker 1>through a browser. Now, there tends to be trade offs

0:40:05.080 --> 0:40:08.319
<v Speaker 1>with whizzywig interfaces. You can see right away if something

0:40:08.440 --> 0:40:10.319
<v Speaker 1>is working or not, but you might have to dig

0:40:10.360 --> 0:40:13.360
<v Speaker 1>a bit deeper in the user interface to get to

0:40:13.440 --> 0:40:17.680
<v Speaker 1>some of the more fine tuning controls. If you're coding

0:40:17.760 --> 0:40:21.560
<v Speaker 1>stuff the hard way, you typically have way more precise

0:40:21.600 --> 0:40:24.200
<v Speaker 1>control over things if you know what you're doing, but

0:40:24.280 --> 0:40:26.279
<v Speaker 1>it does require a lot more back and forth to

0:40:26.320 --> 0:40:30.000
<v Speaker 1>make sure that everything's coming out all right. Man, this

0:40:30.080 --> 0:40:31.920
<v Speaker 1>is making me think of the old days when I

0:40:31.960 --> 0:40:34.359
<v Speaker 1>would use word perfect to make documents, and I would

0:40:34.360 --> 0:40:37.600
<v Speaker 1>have reveal codes on all the time, just so I

0:40:37.600 --> 0:40:40.880
<v Speaker 1>could see where stuff was, like an underlying section, or

0:40:41.000 --> 0:40:43.960
<v Speaker 1>where hard returns were, stuff like that. And those were

0:40:44.000 --> 0:40:48.760
<v Speaker 1>the days, man I miss those. Next XML. I touched

0:40:48.760 --> 0:40:50.839
<v Speaker 1>on this in a previous entry, but it stands for

0:40:50.960 --> 0:40:55.200
<v Speaker 1>extensible markup language. This language allows users to create and

0:40:55.239 --> 0:40:58.600
<v Speaker 1>define their own tags, and so this is a meta

0:40:58.640 --> 0:41:01.960
<v Speaker 1>textual markup language. Another way to think of it is

0:41:02.000 --> 0:41:06.160
<v Speaker 1>that x m L is information that is wrapped in tags,

0:41:06.200 --> 0:41:09.280
<v Speaker 1>and xm L doesn't actually do anything on its own.

0:41:09.760 --> 0:41:12.799
<v Speaker 1>You have to write some form of software to interpret

0:41:12.840 --> 0:41:16.600
<v Speaker 1>and act upon those tags. So, for example, if you

0:41:16.640 --> 0:41:19.080
<v Speaker 1>were to create a document and you wanted to use

0:41:19.120 --> 0:41:22.280
<v Speaker 1>some XML tags, you might create a tag that reads,

0:41:22.480 --> 0:41:26.799
<v Speaker 1>you know, open bracket, subheading clothes bracket. Then you might

0:41:26.840 --> 0:41:28.920
<v Speaker 1>type you know a message that you want to have

0:41:29.120 --> 0:41:31.759
<v Speaker 1>as a subheading on your document, and then at the

0:41:31.840 --> 0:41:35.640
<v Speaker 1>end of it you would type open bracket slash subheading,

0:41:35.880 --> 0:41:39.839
<v Speaker 1>close bracket. But that alone doesn't do anything right, that's

0:41:39.920 --> 0:41:42.799
<v Speaker 1>meaningless by itself. But then let's say you create some

0:41:42.880 --> 0:41:47.120
<v Speaker 1>software to handle how this document gets viewed, and in

0:41:47.160 --> 0:41:49.600
<v Speaker 1>the creation of that software, you lay out the rules

0:41:49.760 --> 0:41:53.760
<v Speaker 1>as to how that subheading tag should be displayed within

0:41:53.920 --> 0:41:57.000
<v Speaker 1>a view of the document. That's what x m L does.

0:41:57.320 --> 0:41:59.960
<v Speaker 1>It creates the opportunity to carry data in a specif

0:42:00.000 --> 0:42:03.920
<v Speaker 1>ific way as determined by the tags and the definition

0:42:04.000 --> 0:42:07.400
<v Speaker 1>of those tags. Now this is in contrast with HTML,

0:42:07.560 --> 0:42:13.560
<v Speaker 1>a different markup language which has predefined tags. And finally

0:42:14.160 --> 0:42:18.640
<v Speaker 1>we have HY two K. This was an abbreviation meant

0:42:18.719 --> 0:42:23.000
<v Speaker 1>to indicate a potentially disastrous problem when the calendar switched

0:42:23.040 --> 0:42:27.719
<v Speaker 1>from to two thousand. Some of you listening to this

0:42:28.040 --> 0:42:30.600
<v Speaker 1>might have been born after two thousand or he might

0:42:30.640 --> 0:42:32.840
<v Speaker 1>have been too young to know what this was all about.

0:42:33.600 --> 0:42:37.320
<v Speaker 1>And um I remember, and it was crazy. It mostly

0:42:37.360 --> 0:42:41.640
<v Speaker 1>boils down to people being a little lazy and relying

0:42:41.680 --> 0:42:43.879
<v Speaker 1>on work that was never meant to stand the test

0:42:43.920 --> 0:42:47.239
<v Speaker 1>of time. So let's get to it. Way back in

0:42:47.280 --> 0:42:50.759
<v Speaker 1>the day, computer programmers were facing some pretty big challenges,

0:42:51.160 --> 0:42:53.160
<v Speaker 1>and one of those was finding ways to limit the

0:42:53.239 --> 0:42:56.880
<v Speaker 1>size of programs, both for the sake of simplicity and

0:42:56.960 --> 0:42:59.880
<v Speaker 1>to conserve computer storage space, which was in short supply

0:43:00.120 --> 0:43:02.719
<v Speaker 1>early on in the days of programming. To that end,

0:43:03.040 --> 0:43:06.120
<v Speaker 1>when making programs that need to reference what year it

0:43:06.320 --> 0:43:09.600
<v Speaker 1>was a lot of programmers used a shorthand. They only

0:43:09.719 --> 0:43:12.640
<v Speaker 1>used the last two digits of the year, so for example,

0:43:13.280 --> 0:43:17.520
<v Speaker 1>this year would be twenty one for one. Now, this

0:43:17.640 --> 0:43:21.080
<v Speaker 1>started around the nineteen sixties, so let's be fair to

0:43:21.120 --> 0:43:24.440
<v Speaker 1>those programmers. They probably did not anticipate that the code

0:43:24.640 --> 0:43:28.160
<v Speaker 1>they were building was going to be dependent upon nearly

0:43:28.239 --> 0:43:32.279
<v Speaker 1>half a century later. I'm sure they assumed understandably so

0:43:33.000 --> 0:43:37.680
<v Speaker 1>that someone somewhere, at some point would make a better

0:43:37.880 --> 0:43:41.400
<v Speaker 1>version of the program. And you know, when stuff like

0:43:41.760 --> 0:43:45.640
<v Speaker 1>conserving computer storage space wouldn't be as quite a big concern.

0:43:45.719 --> 0:43:48.480
<v Speaker 1>You could have code with four digits and not have

0:43:48.560 --> 0:43:53.600
<v Speaker 1>to take the shorthand approach. But instead people kept on

0:43:53.800 --> 0:43:58.040
<v Speaker 1>perpetuating that particular form of programming shorthand. At least a

0:43:58.120 --> 0:44:01.120
<v Speaker 1>lot of people did, and a lot of systems, particularly

0:44:01.400 --> 0:44:05.040
<v Speaker 1>systems that would become legacy systems, ones that companies would

0:44:05.080 --> 0:44:08.600
<v Speaker 1>rely upon because it was just too expensive or too

0:44:08.680 --> 0:44:11.560
<v Speaker 1>difficult to upgrade everything, so they would just continue to

0:44:11.600 --> 0:44:15.000
<v Speaker 1>rely on this old infrastructure. A lot of that still

0:44:15.040 --> 0:44:18.440
<v Speaker 1>relied on that two digit format for the year. And

0:44:18.480 --> 0:44:21.239
<v Speaker 1>that works okay until you cross over the end of

0:44:21.239 --> 0:44:28.480
<v Speaker 1>a millennium. Then you potentially have issues. So when was

0:44:28.520 --> 0:44:33.200
<v Speaker 1>to become zero zero, people weren't sure what could happen.

0:44:33.239 --> 0:44:35.840
<v Speaker 1>I mean for systems that use the year to calculate

0:44:35.880 --> 0:44:39.839
<v Speaker 1>stuff like, you know, location data for things like airlines

0:44:40.080 --> 0:44:44.680
<v Speaker 1>or particular financial data. The worry was that the computer

0:44:44.760 --> 0:44:48.279
<v Speaker 1>systems would roll over from zero zero, and that the

0:44:48.280 --> 0:44:51.840
<v Speaker 1>computers would essentially assume the current year would not be

0:44:51.960 --> 0:44:55.680
<v Speaker 1>two thousand, it would instead be nineteen hundred, and that

0:44:55.760 --> 0:44:59.640
<v Speaker 1>could be disastrous. Now, this worry lead to a global

0:44:59.680 --> 0:45:03.839
<v Speaker 1>concer learned bordering on panic. In some instances, there were

0:45:03.880 --> 0:45:08.200
<v Speaker 1>fears that technology ranging from computer systems to airplanes to

0:45:08.400 --> 0:45:13.319
<v Speaker 1>microwaves might fail because of this oversight. Some companies spent

0:45:13.719 --> 0:45:18.160
<v Speaker 1>millions hundreds of millions of dollars to hire programmers to

0:45:18.239 --> 0:45:22.120
<v Speaker 1>go in and update code to reflect a four digit year,

0:45:22.480 --> 0:45:26.160
<v Speaker 1>and in some cases programmers needed to create complicated software

0:45:26.160 --> 0:45:29.160
<v Speaker 1>to adjust for hardware that was hard coded with this

0:45:29.239 --> 0:45:33.120
<v Speaker 1>two digit year approach. In the end, when the clock

0:45:33.160 --> 0:45:36.759
<v Speaker 1>ticked over, there were very few major problems with Y

0:45:36.800 --> 0:45:40.560
<v Speaker 1>two K, particularly here in the United States. Part of

0:45:40.600 --> 0:45:43.080
<v Speaker 1>that reason they have been just that a lot of

0:45:43.120 --> 0:45:46.000
<v Speaker 1>the most necessary work had already happened. A lot of

0:45:46.040 --> 0:45:52.439
<v Speaker 1>companies had spent much of n addressing the issue. There

0:45:52.440 --> 0:45:55.560
<v Speaker 1>were a few exceptions, one of which was a particularly

0:45:56.200 --> 0:45:59.719
<v Speaker 1>scary one. A nuclear energy facility in Japan had some

0:46:00.000 --> 0:46:05.360
<v Speaker 1>creation containment equipment fail, but fortunately backup systems came online immediately,

0:46:05.480 --> 0:46:09.520
<v Speaker 1>so disaster was averted. Some countries did see more problems

0:46:09.520 --> 0:46:13.040
<v Speaker 1>than others. These were typically countries that had not invested

0:46:13.120 --> 0:46:16.120
<v Speaker 1>nearly as much money into preventing the Y two K issue,

0:46:16.160 --> 0:46:19.560
<v Speaker 1>So like South Korea had some issues. I'll probably have

0:46:19.600 --> 0:46:21.640
<v Speaker 1>to do a full episode about Y two K and

0:46:21.680 --> 0:46:25.520
<v Speaker 1>talk about all those related issues with code, including some

0:46:25.640 --> 0:46:30.040
<v Speaker 1>that are similar and had uh you know, relating issues.

0:46:30.960 --> 0:46:34.160
<v Speaker 1>But that is it. We have finally made our way

0:46:34.200 --> 0:46:37.720
<v Speaker 1>through the alphabet. It only took six episodes, and honestly,

0:46:37.760 --> 0:46:40.000
<v Speaker 1>I also skipped over some stuff, like I didn't talk

0:46:40.040 --> 0:46:43.279
<v Speaker 1>about good news very much, but we will save that

0:46:43.320 --> 0:46:46.120
<v Speaker 1>for a catch up episode. If you have suggestions for

0:46:46.200 --> 0:46:48.840
<v Speaker 1>topics I should cover in future episodes of tech Stuff

0:46:49.160 --> 0:46:52.759
<v Speaker 1>alphabetically or otherwise, let me know the best way to

0:46:52.800 --> 0:46:55.360
<v Speaker 1>do that is through Twitter. The handle for the show

0:46:55.480 --> 0:46:59.080
<v Speaker 1>is text Stuff hs W, and I'll talk to you

0:46:59.160 --> 0:47:09.040
<v Speaker 1>again really soon. Tex Stuff is an I Heart Radio production.

0:47:09.280 --> 0:47:12.080
<v Speaker 1>For more podcasts from I heart Radio, visit the i

0:47:12.200 --> 0:47:15.440
<v Speaker 1>heart Radio app, Apple podcasts, or wherever you listen to

0:47:15.480 --> 0:47:16.400
<v Speaker 1>your favorite shows.