WEBVTT - Rerun: Data Preservation and Destruction

0:00:04.480 --> 0:00:12.559
<v Speaker 1>Welcome to tech Stuff, a production from iHeartRadio. Hey there,

0:00:12.600 --> 0:00:15.760
<v Speaker 1>and welcome to tech Stuff. I'm your host Jonathan Strickland

0:00:15.760 --> 0:00:19.440
<v Speaker 1>di'mond executive producer with iHeartRadio. And how the tech are yet.

0:00:20.320 --> 0:00:22.439
<v Speaker 1>You know, I thought it might be interesting to talk

0:00:22.480 --> 0:00:26.600
<v Speaker 1>about how data can both be easy to lose and

0:00:27.120 --> 0:00:30.720
<v Speaker 1>hard to lose. It's a paradise, but really this is

0:00:30.720 --> 0:00:35.840
<v Speaker 1>all about the media upon which we store data and

0:00:36.200 --> 0:00:40.720
<v Speaker 1>how that media can pose various challenges. Now, first up,

0:00:41.159 --> 0:00:46.240
<v Speaker 1>let's just talk about the concept of obsolescence. So as

0:00:46.520 --> 0:00:50.080
<v Speaker 1>our technology, our language, our culture, as all these things

0:00:50.120 --> 0:00:54.360
<v Speaker 1>evolve and we discover new ways to commit information to

0:00:55.000 --> 0:00:59.360
<v Speaker 1>different types of media, we often leave the older methods behind.

0:01:00.400 --> 0:01:03.280
<v Speaker 1>And for example, very few people are recording audio to

0:01:03.400 --> 0:01:07.360
<v Speaker 1>wax cylinders today. For example, you know Thomas Edison did it,

0:01:07.880 --> 0:01:09.800
<v Speaker 1>but you don't see people doing it now, at least

0:01:09.800 --> 0:01:12.920
<v Speaker 1>not outside of you know, historical demonstrations and that sort

0:01:12.959 --> 0:01:17.479
<v Speaker 1>of thing. The days of storing info magnetically onto strips

0:01:17.520 --> 0:01:20.240
<v Speaker 1>of metal, like we saw at the end of the

0:01:20.319 --> 0:01:23.680
<v Speaker 1>nineteenth century, that's pretty far behind us too, although magnetic

0:01:23.720 --> 0:01:26.440
<v Speaker 1>tape is built on the same principle. But before we

0:01:26.560 --> 0:01:31.440
<v Speaker 1>use tape, we used wire, not that frequently, but it

0:01:31.480 --> 0:01:33.080
<v Speaker 1>was one of those things that kind of paved the

0:01:33.120 --> 0:01:38.319
<v Speaker 1>way toward magnetic tape. Now, over time, all media will

0:01:38.400 --> 0:01:42.240
<v Speaker 1>ultimately go obsolete, either because the stuff we recorded upon

0:01:42.840 --> 0:01:47.400
<v Speaker 1>has worn out, the actual physical stuff has broken, or

0:01:47.480 --> 0:01:51.320
<v Speaker 1>because we've lost the ability to retrieve information from that

0:01:51.440 --> 0:01:55.320
<v Speaker 1>type of media. And that inability to retrieve can range

0:01:55.400 --> 0:01:59.000
<v Speaker 1>from the technical to just our knowledge of how to

0:01:59.040 --> 0:02:02.120
<v Speaker 1>do it. So let's take a moment to consider something

0:02:02.200 --> 0:02:05.800
<v Speaker 1>that is pretty far removed from modern technology unless you

0:02:05.840 --> 0:02:12.320
<v Speaker 1>watch stargate, and that is hieroglyphs. So thousands of years ago,

0:02:12.720 --> 0:02:16.080
<v Speaker 1>the people of ancient Egypt developed a writing system that

0:02:16.320 --> 0:02:20.560
<v Speaker 1>was complicated, to say the least. So our Latin alphabet,

0:02:21.000 --> 0:02:23.520
<v Speaker 1>the one that we use in English, for example, has

0:02:23.560 --> 0:02:27.000
<v Speaker 1>twenty six characters write twenty six letters in the alphabet,

0:02:27.880 --> 0:02:35.480
<v Speaker 1>and hieroglyphs had hundreds of characters, like a thousand or more. Now,

0:02:35.520 --> 0:02:40.480
<v Speaker 1>some of the characters in ancient Egypt represented basic phonemes.

0:02:41.400 --> 0:02:45.440
<v Speaker 1>Phonemes are sounds within a language, right, like would be

0:02:45.560 --> 0:02:50.680
<v Speaker 1>a phoneeme or like these are basic sounds. But other

0:02:51.080 --> 0:02:55.280
<v Speaker 1>characters in ancient Egyptian hieroglyphs, they represented entire words, or

0:02:55.320 --> 0:03:01.880
<v Speaker 1>at least parts of words. Some represented stills, so not

0:03:02.280 --> 0:03:06.200
<v Speaker 1>necessarily parts of words like you would think, but a

0:03:06.240 --> 0:03:10.360
<v Speaker 1>syllable that was common in ancient Egypt. But over the millennia,

0:03:10.919 --> 0:03:15.440
<v Speaker 1>the knowledge of how to read hieroglyphs faded from Egyptian culture.

0:03:16.280 --> 0:03:17.919
<v Speaker 1>There were a lot of reasons for this. I mean,

0:03:17.960 --> 0:03:23.760
<v Speaker 1>the style of writing down information changed from hieroglyphs to

0:03:23.800 --> 0:03:27.920
<v Speaker 1>like demonic writing, and beyond Also, you had folks like

0:03:28.680 --> 0:03:32.120
<v Speaker 1>you know, Europeans, like Greeks and Romans, who were invading

0:03:32.160 --> 0:03:37.280
<v Speaker 1>Egypt and changing things and disrupting Egyptian culture significantly. By

0:03:37.320 --> 0:03:40.360
<v Speaker 1>the time we got a few centuries into the common era,

0:03:40.720 --> 0:03:44.200
<v Speaker 1>pretty much no one knew how to read the hieroglyphs

0:03:44.280 --> 0:03:48.000
<v Speaker 1>of ancient Egypt anymore. So we had all this knowledge

0:03:48.080 --> 0:03:52.840
<v Speaker 1>stored in various places and no way to retrieve that knowledge.

0:03:53.040 --> 0:03:55.240
<v Speaker 1>It appeared as though we had lost all of it,

0:03:55.440 --> 0:04:00.160
<v Speaker 1>or that we had, due to some misconceptions, completely miss

0:04:00.200 --> 0:04:03.560
<v Speaker 1>interpreted that knowledge. So by the time we got into

0:04:03.560 --> 0:04:08.120
<v Speaker 1>the medieval era, there was this prevailing hypothesis that the

0:04:08.160 --> 0:04:13.280
<v Speaker 1>Egyptian hieroglyphs were symbolic in meaning, And by that I

0:04:13.320 --> 0:04:15.840
<v Speaker 1>mean that the images that the Egyptians used were thought

0:04:15.880 --> 0:04:18.680
<v Speaker 1>of to be direct symbols of whatever the message was.

0:04:19.360 --> 0:04:22.800
<v Speaker 1>So let's say you had images of a boat and

0:04:22.880 --> 0:04:25.359
<v Speaker 1>a snake, then you might be led to think that

0:04:25.400 --> 0:04:29.320
<v Speaker 1>what you're looking at must be an allegorical story about

0:04:29.360 --> 0:04:34.240
<v Speaker 1>snakes on a boat, possibly starring Samuel L. Jackson. But no,

0:04:35.400 --> 0:04:39.600
<v Speaker 1>the symbols used weren't meant to represent exactly what they

0:04:39.640 --> 0:04:44.000
<v Speaker 1>looked like. They represented elements of a language. So, for example,

0:04:44.000 --> 0:04:46.880
<v Speaker 1>if you want to understand what I'm saying, our letter

0:04:47.120 --> 0:04:50.080
<v Speaker 1>S looks kind of like a snake, right, but it

0:04:50.120 --> 0:04:52.880
<v Speaker 1>doesn't mean snake. When you see the letter S, that

0:04:52.960 --> 0:04:57.120
<v Speaker 1>doesn't mean snake. It could be the beginning of the

0:04:57.120 --> 0:04:59.719
<v Speaker 1>word snake. Obviously that begins with S, but it could

0:04:59.720 --> 0:05:03.640
<v Speaker 1>mean anything. It represents the S sound, which is found

0:05:03.680 --> 0:05:06.919
<v Speaker 1>in lots of words, not just snake. And the hieroglyphs

0:05:06.920 --> 0:05:09.560
<v Speaker 1>were similar, but no one had a document that matched

0:05:09.640 --> 0:05:14.360
<v Speaker 1>hieroglyphs to some other known language so that someone could

0:05:14.360 --> 0:05:17.240
<v Speaker 1>actually decipher the symbols. So it just seemed to be,

0:05:18.000 --> 0:05:21.640
<v Speaker 1>you know, all these icons that the meaning had been

0:05:21.680 --> 0:05:27.200
<v Speaker 1>completely lost. But then came Napoleon Ponaparte and his armies

0:05:27.320 --> 0:05:30.680
<v Speaker 1>invaded Egypt toward the end of the eighteenth century, and

0:05:30.760 --> 0:05:35.599
<v Speaker 1>in the process the armies happened across something incredibly important,

0:05:36.120 --> 0:05:39.440
<v Speaker 1>and it would later be called the Rosetta Stone. Now,

0:05:39.480 --> 0:05:43.880
<v Speaker 1>the Rosetta Stone itself is a type of monument, and

0:05:43.960 --> 0:05:47.760
<v Speaker 1>there are carvings on the monument that represent an official

0:05:48.000 --> 0:05:53.040
<v Speaker 1>dynastic decree. The carvings are in three different written languages.

0:05:53.440 --> 0:05:56.279
<v Speaker 1>So at the base of the monument you have the

0:05:56.360 --> 0:06:00.719
<v Speaker 1>carving in ancient Greek, above that is Demotic that is

0:06:00.760 --> 0:06:04.480
<v Speaker 1>an Egyptian language that followed the High language, and at

0:06:04.480 --> 0:06:07.880
<v Speaker 1>the top are hieroglyphs. And since all three carvings represented

0:06:07.920 --> 0:06:11.919
<v Speaker 1>the same decree, this gave experts the opportunity to finally

0:06:11.960 --> 0:06:17.400
<v Speaker 1>begin deciphering Egyptian hieroglyphs, and so began the long process

0:06:17.440 --> 0:06:22.120
<v Speaker 1>of uncovering lost knowledge. And this was helped by subsequent

0:06:22.160 --> 0:06:27.800
<v Speaker 1>discoveries of similar decrees, so that we, over time were

0:06:27.839 --> 0:06:32.560
<v Speaker 1>able to understand what these hieroglyphs actually stood for. We

0:06:32.640 --> 0:06:36.080
<v Speaker 1>understood that it was a written language that wasn't just

0:06:36.160 --> 0:06:40.520
<v Speaker 1>purely symbolic. Now, my point in telling the story is

0:06:40.520 --> 0:06:42.880
<v Speaker 1>that we have to remind ourselves that while we have

0:06:43.080 --> 0:06:46.520
<v Speaker 1>ways to record knowledge. It would be foolish for us

0:06:46.600 --> 0:06:49.600
<v Speaker 1>to assume that any way that we use is permanent,

0:06:50.600 --> 0:06:53.920
<v Speaker 1>because we've got plenty of examples of knowledge being lost

0:06:53.960 --> 0:06:57.039
<v Speaker 1>in the past, whether it's because people forgot how to

0:06:57.279 --> 0:07:01.800
<v Speaker 1>access that knowledge, or maybe the knowledge was based in

0:07:01.920 --> 0:07:05.680
<v Speaker 1>folklore and the people that were the stewards of that

0:07:05.800 --> 0:07:09.800
<v Speaker 1>knowledge were wiped out or assimilated and the knowledge was lost,

0:07:10.280 --> 0:07:13.720
<v Speaker 1>or maybe the physical copies, if it was like a

0:07:13.760 --> 0:07:16.840
<v Speaker 1>written language, maybe the physical copies were lost. And a

0:07:16.880 --> 0:07:20.760
<v Speaker 1>shout out to the late great Library of Alexandria, which

0:07:20.760 --> 0:07:23.360
<v Speaker 1>I should add kind of faded away, not just because

0:07:23.400 --> 0:07:26.480
<v Speaker 1>the famous fire set by Julius Caesar's forces, though that

0:07:26.640 --> 0:07:31.480
<v Speaker 1>clearly was a catastrophic event, but also there was a

0:07:31.560 --> 0:07:34.880
<v Speaker 1>long period in which leaders were cracking down on scholars

0:07:34.920 --> 0:07:38.480
<v Speaker 1>because well, a little knowledge is a dangerous thing, so

0:07:38.520 --> 0:07:41.040
<v Speaker 1>a lot of knowledge has got to be absolutely deadly, right.

0:07:41.480 --> 0:07:45.280
<v Speaker 1>But anyway, let's skip ahead to the modern era. So

0:07:45.520 --> 0:07:48.760
<v Speaker 1>even today we run the risk of losing access to

0:07:48.800 --> 0:07:53.080
<v Speaker 1>information because we no longer make the stuff, what plays

0:07:53.200 --> 0:07:55.920
<v Speaker 1>the media that we used in the old days, or

0:07:55.920 --> 0:07:58.480
<v Speaker 1>at least in many cases, it is getting really tricky

0:07:58.520 --> 0:08:02.320
<v Speaker 1>to track down the components that can retrieve data from

0:08:02.440 --> 0:08:05.040
<v Speaker 1>those types of media. Right, you might be able to

0:08:05.080 --> 0:08:10.040
<v Speaker 1>find old working equipment that can access certain types of

0:08:10.160 --> 0:08:14.280
<v Speaker 1>stuff that otherwise we no longer can access. But it's

0:08:14.400 --> 0:08:17.120
<v Speaker 1>rare that you're gonna find someone make a new version

0:08:17.160 --> 0:08:19.880
<v Speaker 1>of that. It's not impossible. It's not like we've lost

0:08:20.280 --> 0:08:23.840
<v Speaker 1>all ability to It's just that unless there is a

0:08:24.560 --> 0:08:29.720
<v Speaker 1>pressing financial benefit to creating that kind of stuff, no

0:08:29.760 --> 0:08:32.040
<v Speaker 1>one's going to bother to do it. Because you know,

0:08:32.240 --> 0:08:39.360
<v Speaker 1>it's expensive to produce older types of technologies, and unless

0:08:39.360 --> 0:08:42.920
<v Speaker 1>there's a financial incentive, no one's going to do it.

0:08:42.920 --> 0:08:45.840
<v Speaker 1>It's had to say so. There's also the danger that

0:08:45.880 --> 0:08:49.559
<v Speaker 1>the media we rely upon could wear out and deteriorate

0:08:49.679 --> 0:08:54.320
<v Speaker 1>over time. So, for example, let's consider celluloid or film.

0:08:55.080 --> 0:08:59.560
<v Speaker 1>Cinematic film degrades over time, particularly if it's in a

0:08:59.720 --> 0:09:03.600
<v Speaker 1>hot and moist environment. And you might have heard about

0:09:03.880 --> 0:09:07.880
<v Speaker 1>some filmmakers storing prints of their movies or masters of

0:09:07.920 --> 0:09:11.360
<v Speaker 1>their movies in old salt mines such as the one

0:09:11.360 --> 0:09:16.000
<v Speaker 1>that's below Hutchinson, Kansas in the United States. These subterranean

0:09:16.080 --> 0:09:20.640
<v Speaker 1>spaces maintain a constant temperature of around sixty eight fahrenheit

0:09:20.840 --> 0:09:24.880
<v Speaker 1>or twenty celsius, and they have a low humidity somewhere

0:09:24.960 --> 0:09:28.319
<v Speaker 1>between like forty to forty five percent humidity. Of course,

0:09:28.320 --> 0:09:30.440
<v Speaker 1>movies are not the only things stored in those minds.

0:09:30.840 --> 0:09:33.760
<v Speaker 1>That in fact, we got the idea because of the

0:09:34.200 --> 0:09:38.360
<v Speaker 1>story of the monument men who ended up finding lots

0:09:38.360 --> 0:09:43.120
<v Speaker 1>of stolen art from various parts of Europe that the

0:09:43.200 --> 0:09:46.280
<v Speaker 1>Nazis had collected and stored in salt mines. We ended

0:09:46.320 --> 0:09:49.800
<v Speaker 1>up kind of using the same idea because it's a

0:09:49.840 --> 0:09:53.880
<v Speaker 1>great way to preserve stuff. If you otherwise, it's in

0:09:53.960 --> 0:09:57.880
<v Speaker 1>danger of deterioration. Also, we have to acknowledge that while

0:09:57.920 --> 0:09:59.960
<v Speaker 1>it's a great way to preserve stuff, there's a tragedy

0:10:00.080 --> 0:10:04.480
<v Speaker 1>here because we're also removing it right from us. You know,

0:10:04.520 --> 0:10:07.080
<v Speaker 1>we're storing it and we're preserving it, But to what

0:10:07.280 --> 0:10:12.400
<v Speaker 1>end if you can't access it, then it doesn't really

0:10:12.800 --> 0:10:15.560
<v Speaker 1>like there's a lot of questions. There are philosophical questions.

0:10:15.880 --> 0:10:18.760
<v Speaker 1>If you have a priceless work of art stored in

0:10:18.800 --> 0:10:21.280
<v Speaker 1>assault mind and no one can go there, is it

0:10:21.360 --> 0:10:24.360
<v Speaker 1>the same as not having it at all. Now, in

0:10:24.400 --> 0:10:26.880
<v Speaker 1>the case of film, a lot of studios will actually

0:10:27.000 --> 0:10:30.120
<v Speaker 1>use those master recordings. When they want to do a

0:10:30.200 --> 0:10:33.080
<v Speaker 1>remastered version of the film they want to release it

0:10:33.120 --> 0:10:36.240
<v Speaker 1>on say like Blu ray or something, they'll go to

0:10:36.440 --> 0:10:39.800
<v Speaker 1>the original print that's stored in as salt mine and

0:10:39.840 --> 0:10:42.480
<v Speaker 1>they'll pull from that. But yeah, there's lots of other

0:10:42.480 --> 0:10:45.480
<v Speaker 1>stuff besides just film down there, anything that needs a

0:10:45.480 --> 0:10:50.319
<v Speaker 1>controlled environment in order to stop or at least slow deterioration. Now,

0:10:50.360 --> 0:10:54.760
<v Speaker 1>magnetic tape is another important storage method, and we've been

0:10:54.840 --> 0:10:58.200
<v Speaker 1>using magnetic tape as storage since the mid twentieth century,

0:10:58.240 --> 0:11:01.240
<v Speaker 1>around nineteen fifty one or so, and again the basic

0:11:01.360 --> 0:11:04.559
<v Speaker 1>principle behind it dates back to the late nineteenth century.

0:11:04.559 --> 0:11:09.880
<v Speaker 1>That was when we were using magnetic wire. But whether

0:11:10.000 --> 0:11:14.280
<v Speaker 1>it's real to real tape, or cassettes or VHS tapes,

0:11:14.679 --> 0:11:18.079
<v Speaker 1>we've relied on this methodology to store all sorts of information,

0:11:18.320 --> 0:11:23.200
<v Speaker 1>from computer information to music in the case of like

0:11:23.280 --> 0:11:28.520
<v Speaker 1>the cassette tapes of the eighties nineties or the VHS videotapes,

0:11:29.520 --> 0:11:32.960
<v Speaker 1>all sorts of info we have committed to magnetic tape,

0:11:33.760 --> 0:11:35.959
<v Speaker 1>and a lot of companies still rely on magnetic tape

0:11:36.000 --> 0:11:39.640
<v Speaker 1>for long term storage and backups. When I use long

0:11:39.720 --> 0:11:43.720
<v Speaker 1>term storage, i'm speaking relatively as we will see now

0:11:43.840 --> 0:11:48.000
<v Speaker 1>some older forms of magnetic tape are largely obsolete because

0:11:48.040 --> 0:11:50.640
<v Speaker 1>the devices we'd use to read the data from them

0:11:51.200 --> 0:11:55.120
<v Speaker 1>are out of production. You might find a working device

0:11:55.160 --> 0:11:57.640
<v Speaker 1>here or there, but they can be pretty rare, and

0:11:58.000 --> 0:12:01.839
<v Speaker 1>being mechanical in nature, they will eventually require maintenance or

0:12:01.960 --> 0:12:05.120
<v Speaker 1>they'll stop working. And when you're talking about this kind

0:12:05.160 --> 0:12:08.720
<v Speaker 1>of stuff, often you're talking about things that have parts

0:12:08.760 --> 0:12:11.840
<v Speaker 1>that no one's making anymore, so it becomes very challenging

0:12:11.840 --> 0:12:14.480
<v Speaker 1>to keep them in good working order because there's a

0:12:14.559 --> 0:12:18.120
<v Speaker 1>limited supply of components you can use to make replacements

0:12:18.120 --> 0:12:21.160
<v Speaker 1>when something breaks down. On top of all that, magnetic

0:12:21.240 --> 0:12:25.720
<v Speaker 1>information itself can degrade over time, actually can degrade really

0:12:25.800 --> 0:12:28.560
<v Speaker 1>quickly if it's in the presence of a strong magnetic field,

0:12:28.640 --> 0:12:30.679
<v Speaker 1>which is why as a kid I was told never

0:12:30.720 --> 0:12:33.120
<v Speaker 1>to bring a magnet close to a computer or computer

0:12:33.240 --> 0:12:39.360
<v Speaker 1>discs because you could actually corrupt information that's stored on

0:12:39.400 --> 0:12:44.320
<v Speaker 1>those devices because the magnet would realign the magnetic components

0:12:44.320 --> 0:12:47.560
<v Speaker 1>that were on this plastic film, or in the case

0:12:47.559 --> 0:12:52.200
<v Speaker 1>of a computer, a raid on a platter inside the

0:12:52.200 --> 0:12:57.439
<v Speaker 1>hard disk drive. Now, on average, if stored in decent conditions,

0:12:57.920 --> 0:13:02.120
<v Speaker 1>magnetic tape typically will retain data from anywhere between ten

0:13:02.160 --> 0:13:06.400
<v Speaker 1>to twenty years. When stored in prime conditions like in

0:13:06.440 --> 0:13:09.160
<v Speaker 1>that salt mine, for example, you might stretch it to

0:13:09.240 --> 0:13:12.439
<v Speaker 1>around thirty years. So magnetic tape can hold on to

0:13:12.559 --> 0:13:17.240
<v Speaker 1>data for a while, but certainly not indefinitely. It will

0:13:17.960 --> 0:13:22.360
<v Speaker 1>sooner or later degrade to a point where the information

0:13:22.400 --> 0:13:26.760
<v Speaker 1>will be corrupted or irretrievable. Now, on a similar note,

0:13:27.200 --> 0:13:29.720
<v Speaker 1>let's talk floppy disks. So when I was a kid,

0:13:29.760 --> 0:13:32.040
<v Speaker 1>our Apple two E computer had a five and a

0:13:32.120 --> 0:13:36.000
<v Speaker 1>quarter inch floppy disk drive. These were not the first

0:13:36.040 --> 0:13:38.520
<v Speaker 1>floppy disks. There were older ones. There were larger ones.

0:13:38.559 --> 0:13:43.000
<v Speaker 1>IBM created eight inch floppy disks for example. And the

0:13:43.320 --> 0:13:45.839
<v Speaker 1>discs that I was familiar with back when I was

0:13:45.920 --> 0:13:49.439
<v Speaker 1>using the Apple to E were these plastic envelopes, and

0:13:49.520 --> 0:13:53.320
<v Speaker 1>the envelopes were covering a disc of magnetic film on

0:13:53.400 --> 0:13:58.520
<v Speaker 1>the inside, and it was on this magnetic disc that

0:13:58.600 --> 0:14:02.000
<v Speaker 1>you could save and retreat data. And I actually had

0:14:02.040 --> 0:14:04.320
<v Speaker 1>to look this up because I could not remember it myself.

0:14:04.320 --> 0:14:07.000
<v Speaker 1>But the original five and a quarter inch floppy disks

0:14:07.520 --> 0:14:10.120
<v Speaker 1>could hold up to ninety kilobytes of data. That's when

0:14:10.120 --> 0:14:15.200
<v Speaker 1>they were first created. So that's just ninety kilobytes. But

0:14:15.520 --> 0:14:20.720
<v Speaker 1>over time, you know, engineers improved the technology. They increased

0:14:20.760 --> 0:14:24.160
<v Speaker 1>the capacity of floppy discs. Typically, they did this by

0:14:24.200 --> 0:14:27.280
<v Speaker 1>creating more precise read write heads so they could store

0:14:27.920 --> 0:14:33.120
<v Speaker 1>data in smaller physical sizes, which meant you could cram

0:14:33.200 --> 0:14:35.640
<v Speaker 1>more of it onto the same sized disc. They also

0:14:35.840 --> 0:14:39.800
<v Speaker 1>figured out how to multilayer discs, so that increased storage

0:14:39.840 --> 0:14:44.480
<v Speaker 1>as well. I think, you know, some discs maxed out

0:14:44.480 --> 0:14:47.720
<v Speaker 1>at around seven hundred and twenty kilobytes, so significantly more

0:14:47.760 --> 0:14:50.360
<v Speaker 1>than ninety, but still way less than what we use today.

0:14:51.800 --> 0:14:54.600
<v Speaker 1>Now I'm going to talk more about floppy disks and

0:14:54.680 --> 0:14:59.920
<v Speaker 1>other forms of storage and why all these different types

0:15:00.080 --> 0:15:02.760
<v Speaker 1>have kind of a limited shelf life of one span

0:15:03.000 --> 0:15:05.240
<v Speaker 1>or another. But before we get to that, let's take

0:15:05.480 --> 0:15:16.200
<v Speaker 1>a quick break. Okay, we're back, and we were talking

0:15:16.200 --> 0:15:20.080
<v Speaker 1>about floppy discs. Well, my parents write novels, and so

0:15:20.240 --> 0:15:23.400
<v Speaker 1>my dad's first books, which were written in the early eighties,

0:15:23.400 --> 0:15:25.880
<v Speaker 1>they were written on that old Apple two E computer,

0:15:26.440 --> 0:15:29.960
<v Speaker 1>and he would save chapters of his books to floppy discs.

0:15:30.440 --> 0:15:33.520
<v Speaker 1>Each novel would take up several discs, like I don't know,

0:15:33.600 --> 0:15:36.680
<v Speaker 1>around a dozen or so, I can't quite remember. I

0:15:36.720 --> 0:15:41.240
<v Speaker 1>remember we had disk holders that would hold like maybe

0:15:41.280 --> 0:15:44.600
<v Speaker 1>three of his novels, because that's how many discs would

0:15:44.600 --> 0:15:49.440
<v Speaker 1>be taken up just by storing chapters onto them. I'm

0:15:49.440 --> 0:15:52.680
<v Speaker 1>not sure if he actually still owns those floppy discs,

0:15:53.000 --> 0:15:54.880
<v Speaker 1>but I imagine that even if he does, he doesn't

0:15:54.920 --> 0:15:56.720
<v Speaker 1>have any way to check and see if the data

0:15:56.840 --> 0:15:59.560
<v Speaker 1>is still there or not. He would need an Apple

0:15:59.600 --> 0:16:03.720
<v Speaker 1>to E or an emulator to simulate an Apple to

0:16:03.840 --> 0:16:06.200
<v Speaker 1>E on another machine. Plus he would have to have

0:16:06.240 --> 0:16:09.680
<v Speaker 1>a floppy disk drive connected to whatever computer he was

0:16:09.760 --> 0:16:13.040
<v Speaker 1>using in order to try and read those disks. And

0:16:13.240 --> 0:16:17.120
<v Speaker 1>floppy disk drives are not completely gone. You can still

0:16:17.200 --> 0:16:22.280
<v Speaker 1>find them. They are increasingly rare, however, so it's easy

0:16:22.320 --> 0:16:25.320
<v Speaker 1>to imagine that a day will come when anything stored

0:16:25.360 --> 0:16:28.400
<v Speaker 1>on discs like that, like my dad's books, will just

0:16:28.440 --> 0:16:31.600
<v Speaker 1>become lost simply because no one makes the stuff capable

0:16:31.640 --> 0:16:34.800
<v Speaker 1>of reading it anymore. And the stuff that already exists

0:16:34.840 --> 0:16:43.880
<v Speaker 1>will eventually break down, and you know, the actual magnetic

0:16:43.880 --> 0:16:46.640
<v Speaker 1>information on the discs will degrade over time too, just

0:16:46.680 --> 0:16:51.520
<v Speaker 1>like with magnetic tape. Eventually you'll have some of those

0:16:51.600 --> 0:16:55.160
<v Speaker 1>magnetic particles move out of alignment. That's going to corrupt

0:16:55.200 --> 0:16:57.880
<v Speaker 1>your data. I know I keep saying data and data.

0:16:57.920 --> 0:17:00.160
<v Speaker 1>I know I do that. I don't know why I

0:17:00.200 --> 0:17:02.160
<v Speaker 1>do that, and I can't predict when it happens. It

0:17:02.320 --> 0:17:04.320
<v Speaker 1>just does. I apologize for it, though, because I know

0:17:04.359 --> 0:17:08.119
<v Speaker 1>it drives some of you crazy, and my apologies. It

0:17:08.240 --> 0:17:12.000
<v Speaker 1>just happens anyway. Those particles will move out of alignment,

0:17:12.280 --> 0:17:15.720
<v Speaker 1>the information gets corrupted, So yeah, switch to information there,

0:17:16.240 --> 0:17:18.359
<v Speaker 1>and then you can't retrieve it anymore. So that can

0:17:18.400 --> 0:17:21.560
<v Speaker 1>happen too. Even if you have a working computer system

0:17:21.960 --> 0:17:25.200
<v Speaker 1>that could theoretically pull that information off the disc, sometimes

0:17:25.200 --> 0:17:28.520
<v Speaker 1>the information on the disc itself will become corrupt. Now,

0:17:28.560 --> 0:17:31.199
<v Speaker 1>we also have to keep in mind that media that

0:17:31.240 --> 0:17:34.000
<v Speaker 1>we still use today because hardly. I mean, people do

0:17:34.040 --> 0:17:36.959
<v Speaker 1>still use floppy disks depending on the situation, but it's

0:17:37.000 --> 0:17:39.560
<v Speaker 1>pretty rare. But even the stuff that we do use today,

0:17:39.640 --> 0:17:43.440
<v Speaker 1>eventually that's going to become obsolete too. Just a few

0:17:43.520 --> 0:17:46.959
<v Speaker 1>years ago, compact discs were the go to for data storage,

0:17:47.119 --> 0:17:49.800
<v Speaker 1>at least for personal computers, though a lot of enterprises

0:17:49.840 --> 0:17:52.879
<v Speaker 1>would continue to rely on magnetic tape for more long

0:17:53.000 --> 0:17:57.920
<v Speaker 1>term backups, and compact discs are a type of optical storage,

0:17:57.920 --> 0:18:01.879
<v Speaker 1>meaning that Rather than using magnetism to align tiny particles

0:18:01.960 --> 0:18:07.639
<v Speaker 1>on a physical surface, we're using lasers to write and

0:18:07.720 --> 0:18:12.159
<v Speaker 1>to read from these discs. The information is stored in

0:18:12.240 --> 0:18:17.120
<v Speaker 1>water called pits and lands, pits being a designated pit

0:18:17.400 --> 0:18:20.280
<v Speaker 1>in the surface, and lands being the spaces between pits.

0:18:21.040 --> 0:18:24.359
<v Speaker 1>Though rewriteable CDs actually kind of use foggy and clear

0:18:25.680 --> 0:18:28.439
<v Speaker 1>sections that are very very tiny, you wouldn't be able

0:18:28.480 --> 0:18:31.400
<v Speaker 1>to see them with the naked eye. Now, compact discs

0:18:32.000 --> 0:18:34.520
<v Speaker 1>allow us to create a more dense storage system, so

0:18:34.560 --> 0:18:37.800
<v Speaker 1>we could put way more information on a single CD

0:18:38.840 --> 0:18:42.159
<v Speaker 1>than we could with stuff like floppy discs. Now, Unlike

0:18:42.200 --> 0:18:46.400
<v Speaker 1>cassettes and floppy disks, optical discs are not affected by magnetism.

0:18:46.600 --> 0:18:49.520
<v Speaker 1>So if you did bring a powerful magnet close to

0:18:49.560 --> 0:18:51.760
<v Speaker 1>a bunch of floppy disks or cassette tapes or anything

0:18:51.760 --> 0:18:55.840
<v Speaker 1>that uses magnetic storage, you would scramble the information on

0:18:55.960 --> 0:18:59.600
<v Speaker 1>there because the powerful magnet would realign the magnetic particles

0:18:59.680 --> 0:19:03.000
<v Speaker 1>that are on the tape. But optical discs don't have

0:19:03.119 --> 0:19:06.440
<v Speaker 1>magnetic particles, so they would be immune to that kind

0:19:06.480 --> 0:19:11.080
<v Speaker 1>of interference. However, this does not mean that optical discs

0:19:11.160 --> 0:19:17.399
<v Speaker 1>last forever, so there are many layers on a compact disc.

0:19:17.720 --> 0:19:19.760
<v Speaker 1>Same thing with DVDs and blue rays. By the way,

0:19:20.280 --> 0:19:24.560
<v Speaker 1>there are several layers involved, and these layers can have

0:19:24.640 --> 0:19:28.720
<v Speaker 1>chemical reactions in them, and those chemical reactions can cause

0:19:28.760 --> 0:19:32.879
<v Speaker 1>those layers to degrade over time. So like a CD

0:19:33.000 --> 0:19:35.679
<v Speaker 1>that's stored in a very humid and warm place, like

0:19:36.119 --> 0:19:40.240
<v Speaker 1>if people had stored their CDs, their music CDs inside

0:19:40.280 --> 0:19:43.119
<v Speaker 1>their car and the summer in Georgia, they might find

0:19:43.119 --> 0:19:45.520
<v Speaker 1>that those CDs don't last that long, like they might

0:19:45.640 --> 0:19:50.720
<v Speaker 1>last a few seasons, but eventually they degrade, and they will.

0:19:50.840 --> 0:19:52.920
<v Speaker 1>You know, if you're in a hot and humid environment,

0:19:53.000 --> 0:19:57.840
<v Speaker 1>then a disc is going to degrade faster, not like instantaneously,

0:19:58.119 --> 0:20:01.000
<v Speaker 1>but it will start to degrade faster than it would

0:20:01.040 --> 0:20:05.520
<v Speaker 1>if you stored it in a cooler, dry place. And

0:20:06.240 --> 0:20:09.919
<v Speaker 1>that outer layer on a CD, that's the clear layer, right,

0:20:09.960 --> 0:20:12.920
<v Speaker 1>It's protective and it's clear so that a laser can

0:20:12.960 --> 0:20:16.160
<v Speaker 1>go through it. But sometimes that clear layer can start

0:20:16.160 --> 0:20:18.879
<v Speaker 1>to rot away and it can leave the reflective layer

0:20:18.920 --> 0:20:23.639
<v Speaker 1>that's underneath it exposed. And with some CDs, that reflective

0:20:23.680 --> 0:20:29.280
<v Speaker 1>layer is made up of silver or sometimes a silver compound,

0:20:29.320 --> 0:20:33.960
<v Speaker 1>and silver when exposed to air will tarnish. The tarnished

0:20:34.000 --> 0:20:37.000
<v Speaker 1>silver won't reflect a laser properly, and so you start

0:20:37.040 --> 0:20:39.800
<v Speaker 1>to get errors when you're trying to read information off

0:20:39.840 --> 0:20:43.120
<v Speaker 1>of that kind of CD. Now, not all CDs were

0:20:43.160 --> 0:20:46.600
<v Speaker 1>made that way, right, so only some CDs have this

0:20:46.640 --> 0:20:50.760
<v Speaker 1>particular bronzing issue. In fact, our research group determined that

0:20:50.880 --> 0:20:54.840
<v Speaker 1>the CDs that really have this specific problem we're all

0:20:54.880 --> 0:20:59.000
<v Speaker 1>pressed in Blackburn, Lancashire, England, between the years nineteen eighty

0:20:59.040 --> 0:21:04.800
<v Speaker 1>eight and nineteen nine. That's pretty darn specific. Now. The

0:21:05.440 --> 0:21:08.240
<v Speaker 1>issue here, though, is that there's really no way to

0:21:08.280 --> 0:21:12.040
<v Speaker 1>give an average lifespan for a compact disc because there's

0:21:12.040 --> 0:21:14.960
<v Speaker 1>no such thing as an average compact discs there were

0:21:15.000 --> 0:21:18.639
<v Speaker 1>there were so many different manufacturing and pressing processes and

0:21:18.720 --> 0:21:25.560
<v Speaker 1>recording processes that different ones could last a different you know,

0:21:26.320 --> 0:21:29.639
<v Speaker 1>theoretical maximum amount of time. So we can't really answer

0:21:29.720 --> 0:21:33.040
<v Speaker 1>the question how long on average will as CD last.

0:21:33.680 --> 0:21:36.639
<v Speaker 1>I've seen a lot of people suggest five to ten years,

0:21:36.640 --> 0:21:38.800
<v Speaker 1>some people saying ten to twenty, some people going as

0:21:38.800 --> 0:21:41.679
<v Speaker 1>far as fifty. I think it really depends on the

0:21:41.720 --> 0:21:46.240
<v Speaker 1>way the CD was made and what storage facility it's in, Like,

0:21:46.480 --> 0:21:49.439
<v Speaker 1>is it in a house where it's kept out of

0:21:49.600 --> 0:21:54.520
<v Speaker 1>sunlight because UV radiation can affect CDs. Is it kept

0:21:54.640 --> 0:21:57.200
<v Speaker 1>cool and dry, then it's gonna last longer. Is it

0:21:57.240 --> 0:22:00.760
<v Speaker 1>not handled a lot? Like if it's it's your favorite

0:22:01.200 --> 0:22:04.720
<v Speaker 1>music CD, and you handle it a lot, then it's

0:22:04.760 --> 0:22:08.360
<v Speaker 1>going to degrade faster. Again, not instantaneously, and it may

0:22:08.400 --> 0:22:11.560
<v Speaker 1>not even be noticeable at first, but eventually you might

0:22:11.560 --> 0:22:14.280
<v Speaker 1>get the things where it starts to skip on a

0:22:14.280 --> 0:22:17.960
<v Speaker 1>certain track, or it won't even play certain tracks. That

0:22:18.040 --> 0:22:21.399
<v Speaker 1>will happen over time. And it's a similar story for

0:22:21.440 --> 0:22:24.440
<v Speaker 1>other optical formats, which include you know, DVDs and Blu

0:22:24.560 --> 0:22:28.240
<v Speaker 1>ray discs. These two have a limited lifespan, though that

0:22:28.280 --> 0:22:31.639
<v Speaker 1>lifespan may stretch to as long as a century under

0:22:31.680 --> 0:22:34.879
<v Speaker 1>ideal conditions. And a century is a long time for

0:22:34.920 --> 0:22:37.960
<v Speaker 1>a single person, right, I mean, that's that's a significant

0:22:37.960 --> 0:22:42.679
<v Speaker 1>amount of time. However, if we step outside of a

0:22:42.760 --> 0:22:46.280
<v Speaker 1>human's lifespan and we look at it from the perspective

0:22:46.520 --> 0:22:51.320
<v Speaker 1>of a historical account, then one hundred years is not

0:22:51.440 --> 0:22:54.600
<v Speaker 1>long at all. I mean, imagine for a moment, if

0:22:54.720 --> 0:22:58.800
<v Speaker 1>you had no access to any information that was recorded

0:22:58.880 --> 0:23:02.719
<v Speaker 1>before nineteen twenty ten, because all the media that we

0:23:02.760 --> 0:23:06.399
<v Speaker 1>had used to record info on had fallen apart or

0:23:06.560 --> 0:23:11.960
<v Speaker 1>was otherwise unusable or inaccessible. That nothing before nineteen twenty

0:23:12.040 --> 0:23:16.159
<v Speaker 1>two would be knowable apart from what people wrote about

0:23:16.200 --> 0:23:21.000
<v Speaker 1>those times post nineteen twenty two. That would be crazy, right,

0:23:21.880 --> 0:23:25.240
<v Speaker 1>But that's the kind of situation we're in when we

0:23:25.280 --> 0:23:29.320
<v Speaker 1>start looking at digital information. All right, Well, what about

0:23:29.480 --> 0:23:31.960
<v Speaker 1>we look at like hard drives, hard disk drives and

0:23:32.040 --> 0:23:34.680
<v Speaker 1>solid state drives, you know, the stuff that's in your

0:23:34.680 --> 0:23:38.080
<v Speaker 1>computer systems, your smartphones, that kind of thing. What do

0:23:38.320 --> 0:23:43.760
<v Speaker 1>they have? You know, how long will information last in those? Well,

0:23:43.920 --> 0:23:47.520
<v Speaker 1>they stored information in different ways. Hard disk drives have

0:23:47.760 --> 0:23:52.160
<v Speaker 1>one or more platters in them, and each platter has

0:23:52.200 --> 0:23:56.199
<v Speaker 1>a magnetic coding on it upon which information can be stored. So,

0:23:56.680 --> 0:24:01.000
<v Speaker 1>just like cassettes and floppy disks and other magnetic storage methods,

0:24:01.160 --> 0:24:04.120
<v Speaker 1>hard disk drives can be affected by powerful magnetic fields

0:24:04.160 --> 0:24:10.719
<v Speaker 1>because they too, store information magnetically. Hardness drives have moving parts,

0:24:11.240 --> 0:24:16.440
<v Speaker 1>so the platters spin quite quickly in fact, and an

0:24:16.480 --> 0:24:20.159
<v Speaker 1>actuator mechanical arm with a read write quote unquote head

0:24:20.280 --> 0:24:23.919
<v Speaker 1>on it. This is the bit that either can read

0:24:24.280 --> 0:24:27.600
<v Speaker 1>the magnetic particles that are stored on a platter, or

0:24:27.840 --> 0:24:33.119
<v Speaker 1>it can actually exert a magnetic field that aligns the particles.

0:24:33.280 --> 0:24:36.959
<v Speaker 1>When you're writing information on the platter, it moves across

0:24:37.000 --> 0:24:40.240
<v Speaker 1>the platter and it starts to retrieve or write information

0:24:40.320 --> 0:24:43.919
<v Speaker 1>to the disc itself. And because we're talking about moving

0:24:44.000 --> 0:24:48.760
<v Speaker 1>parts here, stuff can and does wear down over time

0:24:48.880 --> 0:24:51.480
<v Speaker 1>and use. If it gets a lot of use, it

0:24:51.520 --> 0:24:54.840
<v Speaker 1>wears out more quickly. Also, it means that you should

0:24:54.840 --> 0:24:57.240
<v Speaker 1>be gentle when you're moving anything that happens to have

0:24:57.280 --> 0:24:59.600
<v Speaker 1>a hard disk drive inside of it, because a good

0:24:59.600 --> 0:25:03.040
<v Speaker 1>whack can damage the delicate parts. If you knock that

0:25:03.160 --> 0:25:06.600
<v Speaker 1>actuator arm out of alignment, that's a big problem. It's

0:25:07.040 --> 0:25:12.080
<v Speaker 1>going to be impossible to read or write stuff reliably

0:25:12.280 --> 0:25:16.480
<v Speaker 1>to that hard disk drive. Now, hard drives don't tend

0:25:16.520 --> 0:25:19.720
<v Speaker 1>to last very long because of those mechanical parts. I've

0:25:19.720 --> 0:25:23.000
<v Speaker 1>seen estimates of the life span for hard disk drives

0:25:23.080 --> 0:25:27.359
<v Speaker 1>lasting somewhere between three to maybe six and a half years,

0:25:27.400 --> 0:25:30.840
<v Speaker 1>seven years. Some give it a little bit longer, some

0:25:30.920 --> 0:25:33.280
<v Speaker 1>a little bit shorter. Of course, a hard disk drive

0:25:33.320 --> 0:25:37.760
<v Speaker 1>can last longer than a decade. But that's you know,

0:25:38.560 --> 0:25:41.280
<v Speaker 1>if we're looking at typical use and we're looking at

0:25:41.320 --> 0:25:44.080
<v Speaker 1>the average life span of hard disk drives, we tend

0:25:44.160 --> 0:25:47.359
<v Speaker 1>to fall in that three to seven year range, So

0:25:47.640 --> 0:25:50.639
<v Speaker 1>your mileage may vary. It may depend upon how you

0:25:51.240 --> 0:25:54.880
<v Speaker 1>use your hard disk drive and the setting that you're in.

0:25:55.560 --> 0:25:59.800
<v Speaker 1>So they will eventually break down. Also, even if they

0:25:59.800 --> 0:26:04.280
<v Speaker 1>don't break down sooner or later, really later, that magnetic

0:26:04.320 --> 0:26:08.600
<v Speaker 1>information will start to move out of alignment just naturally.

0:26:09.040 --> 0:26:12.639
<v Speaker 1>And so even if you were to preserve a hard

0:26:12.680 --> 0:26:17.240
<v Speaker 1>disk drive perfectly and come back to it in a century,

0:26:17.640 --> 0:26:19.600
<v Speaker 1>chances are a lot of the information would no longer

0:26:19.640 --> 0:26:23.359
<v Speaker 1>be accessible because the actual magnetic particles would no longer

0:26:23.359 --> 0:26:27.879
<v Speaker 1>be in the proper alignment. Solid state drives store information

0:26:28.000 --> 0:26:32.000
<v Speaker 1>in a totally different way from hard disk drives, So

0:26:32.040 --> 0:26:37.120
<v Speaker 1>instead of aligning magnetic particles, and SSD stores information through

0:26:37.280 --> 0:26:40.680
<v Speaker 1>flash memory similar to USB sticks and other types of

0:26:40.720 --> 0:26:45.640
<v Speaker 1>flash drives. These drives store information using nand flash that's

0:26:45.720 --> 0:26:49.280
<v Speaker 1>in a n D and that in turn is composed

0:26:49.640 --> 0:26:52.879
<v Speaker 1>of what are called floating gate transistors. And all of

0:26:52.920 --> 0:26:55.600
<v Speaker 1>this gets super technical, but let's just kind of imagine

0:26:55.600 --> 0:26:59.520
<v Speaker 1>it this way. Each floating gate can be either charged,

0:27:00.000 --> 0:27:02.760
<v Speaker 1>which means it's a zero, or it could be non charged,

0:27:02.800 --> 0:27:05.200
<v Speaker 1>which means it's a one. So it gets a little

0:27:05.200 --> 0:27:08.760
<v Speaker 1>bit confusing because we often think of binary with zero

0:27:08.880 --> 0:27:12.119
<v Speaker 1>being off and one being on. But in this case,

0:27:12.359 --> 0:27:15.200
<v Speaker 1>zero means that there is a charge in a cell

0:27:15.280 --> 0:27:18.040
<v Speaker 1>and one means there is no charge in that cell,

0:27:18.520 --> 0:27:20.679
<v Speaker 1>And a drive is made up of a grid of

0:27:20.720 --> 0:27:25.359
<v Speaker 1>these cells. So USB flash drives and SSDs are non

0:27:25.480 --> 0:27:29.200
<v Speaker 1>volatile memory. That means that they retain information even if

0:27:29.240 --> 0:27:32.160
<v Speaker 1>they are not receiving power. Right, So, if you were

0:27:32.200 --> 0:27:35.200
<v Speaker 1>to turn off your computer and it has an SSD

0:27:35.320 --> 0:27:38.520
<v Speaker 1>drive in it, you didn't just wipe out everything that

0:27:38.600 --> 0:27:42.480
<v Speaker 1>was stored on that SSD. It remains there. However, if

0:27:42.520 --> 0:27:46.879
<v Speaker 1>an SSD goes without power for an extended period, so

0:27:46.920 --> 0:27:50.280
<v Speaker 1>we're talking like five to ten years here, it can

0:27:50.359 --> 0:27:54.159
<v Speaker 1>experience what is called bit rot That is, some of

0:27:54.200 --> 0:27:58.760
<v Speaker 1>those charged gates might lose their charge without access to power,

0:27:59.080 --> 0:28:03.520
<v Speaker 1>and over time the information degrades. So SSDs are not

0:28:03.680 --> 0:28:09.199
<v Speaker 1>immune to deterioration either. Given enough time, the information on

0:28:09.280 --> 0:28:12.280
<v Speaker 1>those will be corrupted as well, without any other external

0:28:12.320 --> 0:28:18.400
<v Speaker 1>forces being applied to the SSDs. Well, what about cloud storage,

0:28:18.440 --> 0:28:21.800
<v Speaker 1>because that's changed everything, right, I mean, there's so much

0:28:22.040 --> 0:28:24.560
<v Speaker 1>of the information that we use day to day that

0:28:24.680 --> 0:28:28.400
<v Speaker 1>isn't even stored on our native device at all, or

0:28:29.400 --> 0:28:31.840
<v Speaker 1>what is stored on our native device is a temporary

0:28:33.040 --> 0:28:38.480
<v Speaker 1>representation of that file. The actual file lives in the cloud. Well,

0:28:38.800 --> 0:28:42.440
<v Speaker 1>assuming that the company that's providing the storage remains strong,

0:28:42.680 --> 0:28:46.280
<v Speaker 1>data stored in the cloud tends to be pretty darn resilient.

0:28:46.880 --> 0:28:50.160
<v Speaker 1>And that's because in order to provide a reputable cloud

0:28:50.440 --> 0:28:54.680
<v Speaker 1>storage service, or really any cloud service, companies have to

0:28:54.880 --> 0:29:00.000
<v Speaker 1>ensure redundancy. Now, that just means that any information that's

0:29:00.120 --> 0:29:02.720
<v Speaker 1>stored to the cloud system has to be stored on

0:29:02.840 --> 0:29:07.480
<v Speaker 1>multiple machines, because remember, cloud just means someone else's computer.

0:29:07.800 --> 0:29:10.480
<v Speaker 1>That's really what the cloud is. When you're storing stuff

0:29:10.480 --> 0:29:13.800
<v Speaker 1>in the cloud, it's not just floating around in the Internet.

0:29:13.880 --> 0:29:18.160
<v Speaker 1>It's being stored on servers that are part of some

0:29:18.520 --> 0:29:24.120
<v Speaker 1>massive data server farm that are owned by some even

0:29:24.160 --> 0:29:29.800
<v Speaker 1>more massive company like Amazon or Microsoft or Google. Now,

0:29:29.880 --> 0:29:33.960
<v Speaker 1>the reason why these companies store the information on multiple

0:29:33.960 --> 0:29:40.040
<v Speaker 1>machines is that should a single machine holding information malfunctions

0:29:40.160 --> 0:29:44.080
<v Speaker 1>or I don't know, goes on fire or something, there

0:29:44.080 --> 0:29:48.840
<v Speaker 1>are backups on other machines. So the customer ideally never

0:29:48.920 --> 0:29:52.840
<v Speaker 1>even notices that there's any problem. There's no interruption of service,

0:29:52.880 --> 0:29:56.920
<v Speaker 1>there's no delay. Their information is still on quote unquote

0:29:57.040 --> 0:30:01.080
<v Speaker 1>the cloud, when really it's on multiple machines. So this

0:30:01.200 --> 0:30:05.000
<v Speaker 1>is important because most of these data server farm places,

0:30:05.600 --> 0:30:09.960
<v Speaker 1>they're using really cheap components, like lots of them, but

0:30:10.000 --> 0:30:12.200
<v Speaker 1>they're inexpensive and it's you know, it's just off the

0:30:12.240 --> 0:30:16.920
<v Speaker 1>shelf inexpensive components to store all this information or to

0:30:17.000 --> 0:30:20.800
<v Speaker 1>run processes. That's what allows them to have this kind

0:30:20.840 --> 0:30:24.840
<v Speaker 1>of redundancy because they're not spending ridiculous amounts of money

0:30:24.840 --> 0:30:27.600
<v Speaker 1>to get state of the art machines in there. They

0:30:27.640 --> 0:30:31.080
<v Speaker 1>don't need that. They just need machines that are you know,

0:30:31.400 --> 0:30:34.880
<v Speaker 1>more or less reliable and more importantly inexpensive, so that

0:30:34.960 --> 0:30:37.200
<v Speaker 1>you can have lots of them so that you have backup.

0:30:38.160 --> 0:30:41.320
<v Speaker 1>So in the background, these companies can replace broken or

0:30:41.400 --> 0:30:44.560
<v Speaker 1>damage systems with newer ones. They can migrate copies of

0:30:44.640 --> 0:30:49.040
<v Speaker 1>information onto new machines or existing machines, keep things going

0:30:49.080 --> 0:30:53.160
<v Speaker 1>smoothly and the customers never notice an issue. Now, there

0:30:53.200 --> 0:30:55.960
<v Speaker 1>is a caveat there, which I will get to after

0:30:56.040 --> 0:31:05.800
<v Speaker 1>we come back from this break. So before the break,

0:31:05.840 --> 0:31:11.920
<v Speaker 1>I alluded to a caveat about having these indefinitely resilient

0:31:12.800 --> 0:31:16.760
<v Speaker 1>data storage systems using the cloud, and that is I

0:31:16.800 --> 0:31:20.080
<v Speaker 1>said at the beginning, assuming the company providing the storage

0:31:20.160 --> 0:31:24.040
<v Speaker 1>remains strong. So we have to remember that much of

0:31:24.160 --> 0:31:28.120
<v Speaker 1>cloud storage out there is resting in these few big companies,

0:31:28.160 --> 0:31:31.640
<v Speaker 1>and they are really big and thus pretty resilient to

0:31:32.200 --> 0:31:35.480
<v Speaker 1>change and to going out of business, but they're not

0:31:35.800 --> 0:31:40.400
<v Speaker 1>immune to it. Even companies like Amazon, Microsoft and Google

0:31:40.680 --> 0:31:45.280
<v Speaker 1>have their vulnerabilities, and in fact, we're seeing increased pressure

0:31:45.320 --> 0:31:48.120
<v Speaker 1>from around the world to break some of these companies

0:31:48.200 --> 0:31:51.600
<v Speaker 1>up because they are so dominant in their respective spaces.

0:31:52.400 --> 0:31:54.680
<v Speaker 1>So the odds of these companies going out of business

0:31:54.680 --> 0:31:59.200
<v Speaker 1>are really really low, but they're not zero, or at

0:31:59.280 --> 0:32:02.160
<v Speaker 1>least it's not zero that they won't be split up,

0:32:02.360 --> 0:32:07.760
<v Speaker 1>and that ultimately that could lead to discontinuation of services

0:32:07.800 --> 0:32:11.600
<v Speaker 1>in some areas. So we have to remember that the

0:32:12.000 --> 0:32:16.280
<v Speaker 1>access to this information remains dependent upon these various companies

0:32:16.720 --> 0:32:19.840
<v Speaker 1>staying in business and being capable of providing that service,

0:32:19.880 --> 0:32:22.720
<v Speaker 1>So it's never a guarantee. So even the stuff that's

0:32:22.760 --> 0:32:28.120
<v Speaker 1>saved in the cloud isn't necessarily permanent, it's probably it's

0:32:28.160 --> 0:32:30.840
<v Speaker 1>probably in better shape than say something that's saved on

0:32:30.880 --> 0:32:35.120
<v Speaker 1>a magnet or magnetized tape that you keep in your

0:32:36.080 --> 0:32:39.280
<v Speaker 1>neodyne magnet room. It's going to be better than that,

0:32:40.480 --> 0:32:44.960
<v Speaker 1>but it's not bulletproof. There are several other methods for

0:32:45.000 --> 0:32:48.400
<v Speaker 1>storing information as well, including some that are fairly new.

0:32:48.920 --> 0:32:51.640
<v Speaker 1>But the point remains our ability to hold on to

0:32:51.800 --> 0:32:56.480
<v Speaker 1>knowledge depends upon the media we use and the machinery

0:32:56.520 --> 0:32:59.040
<v Speaker 1>we use to access that media, and if we do

0:32:59.080 --> 0:33:03.520
<v Speaker 1>not consistently move information to new storage methods, we run

0:33:03.560 --> 0:33:08.960
<v Speaker 1>the risk of losing the older information. And I'll come

0:33:09.000 --> 0:33:11.400
<v Speaker 1>back to that at the very end, but let's switch

0:33:11.440 --> 0:33:15.120
<v Speaker 1>gears for a second, because sometimes we want to get

0:33:15.200 --> 0:33:19.040
<v Speaker 1>rid of information. Sometimes we need to wipe some storage,

0:33:19.240 --> 0:33:21.360
<v Speaker 1>you know, maybe we need to make room for something new.

0:33:21.600 --> 0:33:24.960
<v Speaker 1>Anyone who's had a gaming PC, you've probably at some

0:33:25.040 --> 0:33:27.160
<v Speaker 1>point said, all right, well, I got to uninstall a

0:33:27.160 --> 0:33:29.200
<v Speaker 1>couple of these titles so that I can install the

0:33:29.240 --> 0:33:33.280
<v Speaker 1>newest game I want to play. Or maybe we want

0:33:33.320 --> 0:33:35.200
<v Speaker 1>to just get rid of something we no longer need

0:33:35.320 --> 0:33:37.760
<v Speaker 1>or use, or maybe we need to get rid of

0:33:37.800 --> 0:33:40.040
<v Speaker 1>something because we don't want someone else to see it.

0:33:40.560 --> 0:33:43.240
<v Speaker 1>For example, let's say that you've upgraded to a brand

0:33:43.280 --> 0:33:46.560
<v Speaker 1>new computer and you want to sell your old computer,

0:33:46.720 --> 0:33:48.680
<v Speaker 1>or you're going to donate it to like a school

0:33:48.760 --> 0:33:51.480
<v Speaker 1>or something, or maybe you just want to recycle it. Well,

0:33:51.600 --> 0:33:54.320
<v Speaker 1>chances are before you do that, you're going to want

0:33:54.360 --> 0:33:58.440
<v Speaker 1>to wipe that computer clear of information first. If there's

0:33:58.600 --> 0:34:02.240
<v Speaker 1>anything personal on computer, you probably don't want it falling

0:34:02.280 --> 0:34:05.240
<v Speaker 1>into someone else's hands. Like, let's say you get some

0:34:05.280 --> 0:34:09.240
<v Speaker 1>financial or medical information that was stored somewhere on that machine,

0:34:09.600 --> 0:34:12.960
<v Speaker 1>you definitely want to get that wiped off before you

0:34:13.040 --> 0:34:16.040
<v Speaker 1>hand it over to someone else. Well, what happens when

0:34:16.040 --> 0:34:19.640
<v Speaker 1>you delete data, Well, if you're using a computer and

0:34:19.680 --> 0:34:23.360
<v Speaker 1>you're moving files to the recycle bin, that doesn't actually

0:34:23.360 --> 0:34:25.920
<v Speaker 1>mean that the files are gone. Even emptying the recycle

0:34:26.000 --> 0:34:29.000
<v Speaker 1>bin doesn't necessarily mean the files are gone. What it

0:34:29.080 --> 0:34:33.080
<v Speaker 1>means is that the computer has essentially designated the respective

0:34:33.160 --> 0:34:37.600
<v Speaker 1>parts on the storage system holding those files as being

0:34:37.840 --> 0:34:43.080
<v Speaker 1>available for new information. So like the markers that would

0:34:43.160 --> 0:34:45.759
<v Speaker 1>designate that as being a file or gone, but the

0:34:45.760 --> 0:34:48.840
<v Speaker 1>file itself, the information of the file itself is still there.

0:34:49.760 --> 0:34:52.399
<v Speaker 1>But then when it's time for you to save new

0:34:52.440 --> 0:34:55.560
<v Speaker 1>information to your computer, some of that new information might

0:34:55.600 --> 0:34:59.080
<v Speaker 1>be overwritten on top of the older files that you

0:34:59.200 --> 0:35:04.400
<v Speaker 1>quote unquote, So over time, you will slowly eradicate the

0:35:04.400 --> 0:35:08.239
<v Speaker 1>information of that deleted file as your computer writes new

0:35:08.280 --> 0:35:13.440
<v Speaker 1>information to those segments. But it's not instantaneous. And the

0:35:13.480 --> 0:35:16.720
<v Speaker 1>important thing to remember is that deleting a file doesn't

0:35:16.800 --> 0:35:19.400
<v Speaker 1>mean the file is gone. It's not enough to just

0:35:19.680 --> 0:35:23.440
<v Speaker 1>delete a file. Many operating systems include options to let

0:35:23.480 --> 0:35:27.880
<v Speaker 1>you permanently delete files, and this option typically just involves

0:35:28.000 --> 0:35:33.920
<v Speaker 1>overwriting the selected deleted files with information, usually garbage data

0:35:34.080 --> 0:35:37.040
<v Speaker 1>that doesn't actually mean anything. The original file is gone

0:35:37.280 --> 0:35:40.480
<v Speaker 1>and it's replaced with gibberish. But let's say you have

0:35:40.520 --> 0:35:44.000
<v Speaker 1>to be absolutely certain that no one will ever retrieve

0:35:44.080 --> 0:35:48.680
<v Speaker 1>information from your hard drive. Maybe this computer held crucial

0:35:48.719 --> 0:35:52.920
<v Speaker 1>financial information for an important company, or maybe it held

0:35:53.239 --> 0:35:55.880
<v Speaker 1>medical information for lots of people, and say like a hospital,

0:35:55.920 --> 0:35:58.520
<v Speaker 1>and it's time for you to downgrade the system and

0:35:58.560 --> 0:36:01.120
<v Speaker 1>get rid of it. Well, you're gonna really want to

0:36:01.120 --> 0:36:04.920
<v Speaker 1>make sure that that machine is wiped clear. So then

0:36:04.960 --> 0:36:07.759
<v Speaker 1>you might want to engage in what I would like

0:36:07.800 --> 0:36:09.719
<v Speaker 1>to think of as the nuclear option. It's called the

0:36:09.840 --> 0:36:13.600
<v Speaker 1>Gutman method. So Peter Gutman and Colin Plum came up

0:36:13.600 --> 0:36:18.719
<v Speaker 1>with this process in the nineties. It involves overwriting a

0:36:18.800 --> 0:36:24.360
<v Speaker 1>disk drive with gibberish thirty five times, using different patterns,

0:36:24.360 --> 0:36:28.160
<v Speaker 1>including some that are not patterns but random passes. So

0:36:28.160 --> 0:36:30.520
<v Speaker 1>there's no pattern at all. It's just a random overright

0:36:30.600 --> 0:36:33.960
<v Speaker 1>pass followed by a whole bunch of patterned overwrites followed

0:36:33.960 --> 0:36:37.360
<v Speaker 1>by more random passes. And this is because even with

0:36:37.440 --> 0:36:41.080
<v Speaker 1>your standard gibberish overwright, it can still be possible for

0:36:41.160 --> 0:36:44.239
<v Speaker 1>a determined person with the right tools to retrieve at

0:36:44.320 --> 0:36:48.560
<v Speaker 1>least some information off of a hard drive. This is

0:36:48.600 --> 0:36:52.600
<v Speaker 1>because of that magnetic storage. We're talking about the hard

0:36:52.640 --> 0:36:55.760
<v Speaker 1>disk drive era here, so we're really talking about looking

0:36:55.800 --> 0:37:02.120
<v Speaker 1>for faint traces of magnetic imprints that could suggest what

0:37:02.160 --> 0:37:05.400
<v Speaker 1>the original data saved on that hard disk drive was.

0:37:06.000 --> 0:37:10.480
<v Speaker 1>Even by overwriting, those faint traces might remain. So this

0:37:10.680 --> 0:37:15.360
<v Speaker 1>was Gutman's way of just obliterating any trace of what

0:37:15.560 --> 0:37:19.480
<v Speaker 1>was there originally. So you really got to go to extremes,

0:37:19.800 --> 0:37:22.359
<v Speaker 1>or at least you used to, because Gutman and Plum

0:37:22.600 --> 0:37:27.120
<v Speaker 1>were really concerned about that magnetic issue. These days, most

0:37:27.160 --> 0:37:30.760
<v Speaker 1>experts suggest that the Gutman method is really overkill, especially

0:37:30.840 --> 0:37:33.400
<v Speaker 1>if you're using a solid state drive and that after

0:37:33.480 --> 0:37:37.200
<v Speaker 1>three passes, you're usually in pretty reliable shape and you

0:37:37.239 --> 0:37:39.800
<v Speaker 1>don't have to worry about someone getting access to your information.

0:37:40.600 --> 0:37:43.319
<v Speaker 1>There are also several software packages on the market that

0:37:43.400 --> 0:37:47.000
<v Speaker 1>can go through the process of deleting files permanently, usually

0:37:47.080 --> 0:37:52.400
<v Speaker 1>using some form of multipass overwrite patterns. Multipass meaning going

0:37:52.440 --> 0:37:58.239
<v Speaker 1>over the entire storage drive, not like Leelu Dallas multipass.

0:37:59.200 --> 0:38:03.200
<v Speaker 1>Sometimes folks go to even further extremes, such as using

0:38:03.239 --> 0:38:07.880
<v Speaker 1>powerful magnets to destroy you know, magnetic storage that happens

0:38:08.040 --> 0:38:11.840
<v Speaker 1>where you know you're that'll be part of the process.

0:38:12.640 --> 0:38:16.479
<v Speaker 1>Some will even use shredders to destroy like hard disk

0:38:16.520 --> 0:38:19.240
<v Speaker 1>platters and such, so that not only have the files

0:38:19.239 --> 0:38:22.880
<v Speaker 1>been thoroughly deleted and overwritten, but the physical media itself

0:38:22.960 --> 0:38:28.239
<v Speaker 1>has been physically destroyed. That's probably overkill for most of us,

0:38:28.719 --> 0:38:31.200
<v Speaker 1>unless you go by a three number designation like double

0:38:31.200 --> 0:38:34.400
<v Speaker 1>oh nine or something. But it really is interesting to

0:38:34.440 --> 0:38:39.560
<v Speaker 1>me that information can simultaneously be challenging to preserve and

0:38:40.520 --> 0:38:43.719
<v Speaker 1>difficult to get rid of. But we're also talking about

0:38:43.719 --> 0:38:46.680
<v Speaker 1>different time skills here, right, It's not apples to apples

0:38:46.840 --> 0:38:50.399
<v Speaker 1>for preservation. We're really concerned about the long haul, how

0:38:50.440 --> 0:38:54.920
<v Speaker 1>can we keep information accessible even as the way we generate, store,

0:38:55.000 --> 0:38:59.920
<v Speaker 1>and retrieve information changes. How can we ensure that future

0:39:00.080 --> 0:39:03.200
<v Speaker 1>generations will have access to the information that's at our

0:39:03.200 --> 0:39:08.479
<v Speaker 1>disposal today. There are so many offshoots of this as well.

0:39:08.520 --> 0:39:13.520
<v Speaker 1>For example, the desire to preserve old information is what

0:39:13.640 --> 0:39:18.000
<v Speaker 1>drove the creators of the multi Arcade Machine Emulator software

0:39:18.120 --> 0:39:21.040
<v Speaker 1>or MAIM to do what they do. They wanted to

0:39:21.080 --> 0:39:24.600
<v Speaker 1>create a way to preserve code that otherwise could fade

0:39:24.640 --> 0:39:29.560
<v Speaker 1>into obscurity because these old arcade machines were physically coded

0:39:29.680 --> 0:39:33.520
<v Speaker 1>onto chips that were part of these arcade cabinets, and

0:39:34.239 --> 0:39:37.560
<v Speaker 1>over time more of those cabinets ended up being destroyed

0:39:37.880 --> 0:39:41.759
<v Speaker 1>or they become inoperable, and so this was an attempt

0:39:41.760 --> 0:39:44.400
<v Speaker 1>to create a system that would preserve that code, to

0:39:44.480 --> 0:39:48.400
<v Speaker 1>make it playable, not necessarily for people to play, but

0:39:48.520 --> 0:39:51.880
<v Speaker 1>again to preserve the code itself, otherwise it would be lost.

0:39:53.040 --> 0:39:55.880
<v Speaker 1>And as for destroying information, well that tends to be

0:39:56.000 --> 0:39:59.880
<v Speaker 1>for short term requirements, right, if there's nothing that's threatening

0:40:00.120 --> 0:40:04.160
<v Speaker 1>us or our information, well we could just play the

0:40:04.160 --> 0:40:07.960
<v Speaker 1>waiting game, depending on how we've stored the information in

0:40:07.960 --> 0:40:11.200
<v Speaker 1>the first place, because sooner or later the medium that

0:40:11.239 --> 0:40:14.839
<v Speaker 1>the information is on will deteriorate or it'll go obsolete,

0:40:15.080 --> 0:40:17.400
<v Speaker 1>and no one will be able to get the information anyway,

0:40:17.440 --> 0:40:20.600
<v Speaker 1>including you. So if you don't, if you're not in

0:40:20.680 --> 0:40:23.759
<v Speaker 1>a rush, you could just wait and the information will

0:40:23.760 --> 0:40:28.400
<v Speaker 1>eventually no longer be accessible. Now related to these concepts,

0:40:28.480 --> 0:40:31.080
<v Speaker 1>by the way, is the challenge of figuring out how

0:40:31.120 --> 0:40:35.319
<v Speaker 1>to future proof messaging so that people far into the

0:40:35.320 --> 0:40:39.160
<v Speaker 1>future will understand what those messages mean. Let's think back

0:40:39.200 --> 0:40:42.600
<v Speaker 1>to the Egyptian example. Without the Rosetta stone, we would

0:40:42.640 --> 0:40:44.759
<v Speaker 1>have no way of knowing what the hieroglyphs mean. Not

0:40:44.840 --> 0:40:48.200
<v Speaker 1>for sure. We could have a lot of hypotheses, but

0:40:48.280 --> 0:40:50.800
<v Speaker 1>we wouldn't be able to really test them and prove

0:40:51.280 --> 0:40:56.120
<v Speaker 1>that our hypothesis is accurate. So let's take an example.

0:40:56.920 --> 0:41:02.000
<v Speaker 1>Let's take the problem of nuclear waste from nuclear power facilities.

0:41:02.480 --> 0:41:06.720
<v Speaker 1>So some nuclear waste remains dangerous for thousands of years

0:41:07.760 --> 0:41:09.480
<v Speaker 1>and we have to store it. We have to put

0:41:09.480 --> 0:41:12.560
<v Speaker 1>it someplace where it's out of the way and safe.

0:41:12.640 --> 0:41:15.080
<v Speaker 1>And it also means that any warnings that we put

0:41:15.160 --> 0:41:18.759
<v Speaker 1>up at nuclear waste storage facilities really needs to be

0:41:18.840 --> 0:41:22.319
<v Speaker 1>easy for future generations to interpret, even if they have

0:41:22.520 --> 0:41:27.319
<v Speaker 1>lost all other records of what that site is, so

0:41:27.400 --> 0:41:31.719
<v Speaker 1>the signage needs to convey displace is dangerous. But then,

0:41:31.840 --> 0:41:35.520
<v Speaker 1>as that hieroglyphs example showed us, this is easier said

0:41:35.560 --> 0:41:38.120
<v Speaker 1>than done. We might do something that to us seems

0:41:38.160 --> 0:41:42.880
<v Speaker 1>completely obvious, but there's no way of knowing that people

0:41:43.239 --> 0:41:47.040
<v Speaker 1>ten thousand years from now will still understand it. There

0:41:47.040 --> 0:41:50.920
<v Speaker 1>are experts who work hard to create iconography and messaging

0:41:50.960 --> 0:41:54.359
<v Speaker 1>that someone unfamiliar with our current alphabet and language and

0:41:55.080 --> 0:41:59.520
<v Speaker 1>symbols might understand. So for a really awesome treatment of

0:41:59.560 --> 0:42:04.239
<v Speaker 1>this topic, I highly recommend a classic episode of ninety

0:42:04.320 --> 0:42:07.520
<v Speaker 1>nine percent Invisible, a phenomenal show. If you've never listened

0:42:07.560 --> 0:42:11.200
<v Speaker 1>to it, you definitely need to is It is one

0:42:11.239 --> 0:42:14.000
<v Speaker 1>of the best podcasts I've ever listened to. But this

0:42:14.040 --> 0:42:16.440
<v Speaker 1>particular one comes from way back when it was like

0:42:16.480 --> 0:42:20.280
<v Speaker 1>twenty fourteen when it published, and it is titled ten

0:42:20.520 --> 0:42:25.359
<v Speaker 1>thousand Years. Really a great, great episode. You should check

0:42:25.400 --> 0:42:28.400
<v Speaker 1>that out. It's an incredible treatment of the challenge of

0:42:28.480 --> 0:42:33.719
<v Speaker 1>how do you convey information to people that there's no

0:42:33.760 --> 0:42:36.360
<v Speaker 1>way for us to know anything about them, and keeping

0:42:36.360 --> 0:42:38.880
<v Speaker 1>in mind, like we're talking ten thousand years, because nuclear

0:42:38.920 --> 0:42:43.120
<v Speaker 1>waste can stay dangerous that long. You go back ten

0:42:43.160 --> 0:42:46.480
<v Speaker 1>thousand years and you suddenly think, wow, yeah, creating a

0:42:46.480 --> 0:42:49.160
<v Speaker 1>message that would be readable ten thousand years from now

0:42:49.239 --> 0:42:54.040
<v Speaker 1>that is going to be super challenging to do so. Yeah.

0:42:54.320 --> 0:42:58.360
<v Speaker 1>Storing data, retrieving data, destroying data, all of these things

0:42:58.680 --> 0:43:02.439
<v Speaker 1>have their own challenges and obstacles in front of them.

0:43:02.719 --> 0:43:05.919
<v Speaker 1>It's important for us to think about because it's also

0:43:05.960 --> 0:43:09.080
<v Speaker 1>important for us to take steps to preserve things when

0:43:09.120 --> 0:43:12.719
<v Speaker 1>we can. There are other great examples we can use.

0:43:13.080 --> 0:43:16.800
<v Speaker 1>One I would point out is that a lot of people,

0:43:16.880 --> 0:43:21.279
<v Speaker 1>particularly in my generation, we used stuff like Facebook to

0:43:21.360 --> 0:43:26.719
<v Speaker 1>become kind of the storage center for photographs, right, Like,

0:43:27.920 --> 0:43:32.000
<v Speaker 1>I have hundreds of photos stored on Facebook. But then

0:43:32.040 --> 0:43:35.080
<v Speaker 1>I decided to peace out a Facebook. So I needed

0:43:35.080 --> 0:43:39.160
<v Speaker 1>to download my Facebook information because otherwise I was going

0:43:39.200 --> 0:43:42.880
<v Speaker 1>to lose access to all those pictures that I had stored.

0:43:43.520 --> 0:43:45.400
<v Speaker 1>And it was just a kind of thing I had

0:43:45.440 --> 0:43:48.440
<v Speaker 1>taken for granted that I would always be on Facebook

0:43:48.880 --> 0:43:51.759
<v Speaker 1>and I would always have access to those images, and

0:43:51.920 --> 0:43:56.200
<v Speaker 1>now I don't. And so it's again an example of

0:43:56.280 --> 0:43:58.839
<v Speaker 1>things that we have to keep in mind when we

0:43:59.320 --> 0:44:04.680
<v Speaker 1>choose a storage method, is that we should also occasionally

0:44:05.200 --> 0:44:08.360
<v Speaker 1>think of ways to migrate information to a new storage

0:44:08.520 --> 0:44:12.400
<v Speaker 1>method to make certain that we don't lose what came before.

0:44:13.360 --> 0:44:18.160
<v Speaker 1>All right, I hope you enjoyed this episode about the

0:44:18.200 --> 0:44:22.239
<v Speaker 1>paradoxical nature of information in the digital age. If you

0:44:22.280 --> 0:44:24.840
<v Speaker 1>have suggestions for topics I should cover in future episodes

0:44:24.880 --> 0:44:27.439
<v Speaker 1>of tech Stuff, please reach out to me. The best

0:44:27.440 --> 0:44:30.000
<v Speaker 1>way to do that is on Twitter. The handle for

0:44:30.080 --> 0:44:33.960
<v Speaker 1>the show is tech Stuff HSW and I'll talk to

0:44:34.000 --> 0:44:44.320
<v Speaker 1>you again really soon. Tech Stuff is an iHeartRadio production.

0:44:44.640 --> 0:44:49.640
<v Speaker 1>For more podcasts from iHeartRadio, visit the iHeartRadio app, Apple Podcasts,

0:44:49.760 --> 0:44:55.680
<v Speaker 1>or wherever you listen to your favorite shows.