WEBVTT - Data Preservation and Destruction

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:14.680
<v Speaker 1>Hey there, and welcome to tech Stuff. I'm your host,

0:00:14.760 --> 0:00:18.159
<v Speaker 1>Jonathan Strickland, Diamond executive producer with I Heart Radio and

0:00:18.200 --> 0:00:20.960
<v Speaker 1>how the tech are yet. You know, I thought it

0:00:21.040 --> 0:00:24.320
<v Speaker 1>might be interesting to talk about how data can both

0:00:24.400 --> 0:00:29.560
<v Speaker 1>be easy to lose and hard to lose. It's a paradox,

0:00:29.920 --> 0:00:33.240
<v Speaker 1>but really this is all about the media upon which

0:00:33.720 --> 0:00:40.000
<v Speaker 1>we store data and how that media can pose various challenges. Now,

0:00:40.080 --> 0:00:44.760
<v Speaker 1>first up, let's just talk about the concept of obsolescence.

0:00:45.400 --> 0:00:49.519
<v Speaker 1>So as our technology, our language, our culture, as all

0:00:49.560 --> 0:00:53.080
<v Speaker 1>these things evolve and we discover new ways to commit

0:00:53.400 --> 0:00:58.000
<v Speaker 1>information to different types of media, we often leave the

0:00:58.080 --> 0:01:02.640
<v Speaker 1>older methods behind. For example, very few people are recording

0:01:02.640 --> 0:01:06.600
<v Speaker 1>audio to wax cylinders today. For example, you know, Thomas

0:01:06.720 --> 0:01:09.240
<v Speaker 1>Edison did it, but you don't see people doing it now,

0:01:09.319 --> 0:01:12.319
<v Speaker 1>at least not outside of you know, historical demonstrations and

0:01:12.360 --> 0:01:16.440
<v Speaker 1>that sort of thing. The days of storing info magnetically

0:01:16.520 --> 0:01:20.039
<v Speaker 1>onto strips of metal, like we saw at the end

0:01:20.080 --> 0:01:22.640
<v Speaker 1>of the nineteenth century, that's pretty far behind us too,

0:01:22.640 --> 0:01:25.840
<v Speaker 1>although magnetic tape is built on the same principle. But

0:01:25.959 --> 0:01:31.120
<v Speaker 1>before we use tape, we used wire um, not that frequently,

0:01:31.160 --> 0:01:32.480
<v Speaker 1>but it was one of those things that kind of

0:01:32.520 --> 0:01:37.360
<v Speaker 1>paved the way toward magnetic tape. Now, over time, all

0:01:37.440 --> 0:01:41.280
<v Speaker 1>media will ultimately go obsolete, either because the stuff we

0:01:41.360 --> 0:01:46.560
<v Speaker 1>recorded upon has worn out, the actual physical stuff has broken,

0:01:47.240 --> 0:01:51.120
<v Speaker 1>or because we've lost the ability to retrieve information from

0:01:51.160 --> 0:01:54.880
<v Speaker 1>that type of media. And that inability to retrieve can

0:01:55.000 --> 0:01:58.840
<v Speaker 1>range from the technical to just our knowledge of how

0:01:58.840 --> 0:02:00.800
<v Speaker 1>to do it. So let's take a moment to consider

0:02:01.600 --> 0:02:05.639
<v Speaker 1>something that is pretty far removed from modern technology unless

0:02:05.680 --> 0:02:11.280
<v Speaker 1>you watch stargate, and that is hieroglyphs. So thousands of

0:02:11.400 --> 0:02:15.320
<v Speaker 1>years ago, the people of ancient Egypt developed a writing

0:02:15.360 --> 0:02:19.520
<v Speaker 1>system that was complicated, to say the least. So our

0:02:19.639 --> 0:02:22.760
<v Speaker 1>Latin alphabet, the one that we use in in English,

0:02:22.800 --> 0:02:26.079
<v Speaker 1>for example, has twenty six characters, right, twenty six letters

0:02:26.120 --> 0:02:32.720
<v Speaker 1>in the alphabet, and hieroglyphs had hundreds of characters, like

0:02:33.040 --> 0:02:37.040
<v Speaker 1>a thousand or more. Now, some of the characters in

0:02:37.200 --> 0:02:44.200
<v Speaker 1>ancient Egypt represented basic phonemes. Phonemes are sounds within a language, right,

0:02:44.280 --> 0:02:49.360
<v Speaker 1>like would be a phoneme or like these are basic sounds.

0:02:50.160 --> 0:02:55.080
<v Speaker 1>But other characters in ancient Egyptian hieroglyphs they represented entire words,

0:02:55.200 --> 0:03:00.440
<v Speaker 1>or at least parts of words. Uh. Some represented still bles,

0:03:01.000 --> 0:03:05.399
<v Speaker 1>so not necessarily parts of words like you would think,

0:03:05.400 --> 0:03:09.040
<v Speaker 1>but a syllable that was common in ancient Egypt. But

0:03:09.120 --> 0:03:13.519
<v Speaker 1>over the millennia, the knowledge of how to read hieroglyphs

0:03:13.600 --> 0:03:17.200
<v Speaker 1>faded from Egyptian culture. There were a lot of reasons

0:03:17.240 --> 0:03:21.320
<v Speaker 1>for this, I mean, the the style of writing down

0:03:21.360 --> 0:03:26.840
<v Speaker 1>information changed from hieroglyphs to like demonic writing, and beyond also,

0:03:26.880 --> 0:03:30.600
<v Speaker 1>you had folks like you know, Europeans, like Greeks and

0:03:30.720 --> 0:03:34.480
<v Speaker 1>Romans who were invading Egypt and changing things and disrupting

0:03:34.720 --> 0:03:38.400
<v Speaker 1>Egyptian culture significantly. By the time we got a few

0:03:38.440 --> 0:03:42.160
<v Speaker 1>centuries into the common era, pretty much no one knew

0:03:42.160 --> 0:03:46.360
<v Speaker 1>how to read the hieroglyphs of ancient Egypt anymore. So

0:03:46.400 --> 0:03:50.480
<v Speaker 1>we had all this knowledge stored in various places and

0:03:50.720 --> 0:03:54.000
<v Speaker 1>no way to retrieve that knowledge. It appeared as though

0:03:54.040 --> 0:03:56.240
<v Speaker 1>we had lost all of it, or that we had,

0:03:56.840 --> 0:04:02.240
<v Speaker 1>due to some misconceptions, completely miss interpreted that knowledge. So

0:04:02.320 --> 0:04:05.119
<v Speaker 1>by the time we got into the medieval era, there

0:04:05.160 --> 0:04:11.000
<v Speaker 1>was this prevailing hypothesis that the Egyptian hieroglyphs were symbolic

0:04:11.560 --> 0:04:14.200
<v Speaker 1>in meaning and by that I mean that the images

0:04:14.240 --> 0:04:16.800
<v Speaker 1>that the Egyptians used were thought of to be direct

0:04:16.880 --> 0:04:20.400
<v Speaker 1>symbols of whatever the message was. So let's say you

0:04:20.520 --> 0:04:24.279
<v Speaker 1>had images of a boat and a snake, then you

0:04:24.360 --> 0:04:26.120
<v Speaker 1>might be led to think that what you're looking at

0:04:26.480 --> 0:04:30.200
<v Speaker 1>must be an allegorical story about snakes on a boat,

0:04:30.440 --> 0:04:36.559
<v Speaker 1>possibly starring Samuel L. Jackson. But no, the symbols used

0:04:36.560 --> 0:04:40.400
<v Speaker 1>weren't meant to represent exactly what they looked like. They

0:04:40.480 --> 0:04:44.159
<v Speaker 1>represented elements of a language. So for example, if you

0:04:44.200 --> 0:04:48.320
<v Speaker 1>want to understand what I'm saying, our letter S looks

0:04:48.440 --> 0:04:51.400
<v Speaker 1>kind of like a snake, right, but it doesn't mean snake.

0:04:51.480 --> 0:04:55.240
<v Speaker 1>When you see the letter S, that doesn't mean snake. Uh.

0:04:55.320 --> 0:04:58.200
<v Speaker 1>It could be the beginning of the word snake. Obviously

0:04:58.240 --> 0:05:00.640
<v Speaker 1>that begins with S, but it could mean anything. It

0:05:00.680 --> 0:05:04.560
<v Speaker 1>represents the S sound, which is found in lots of words,

0:05:04.560 --> 0:05:07.880
<v Speaker 1>not just snake. And the hieroglyphs were similar, but no

0:05:07.920 --> 0:05:11.200
<v Speaker 1>one had a document that matched hieroglyphs to some other

0:05:11.480 --> 0:05:15.920
<v Speaker 1>known language so that someone could actually decipher the symbols.

0:05:16.000 --> 0:05:19.560
<v Speaker 1>So it just seemed to be, you know, all these

0:05:19.839 --> 0:05:23.800
<v Speaker 1>icons that the meaning had been completely lost. But then

0:05:23.920 --> 0:05:28.880
<v Speaker 1>came Napoleon Bonaparte and his armies invaded Egypt toward the

0:05:29.000 --> 0:05:32.200
<v Speaker 1>end of the eighteenth century, and in the process the

0:05:32.400 --> 0:05:36.880
<v Speaker 1>armies happened across something incredibly important, and it would later

0:05:36.920 --> 0:05:40.760
<v Speaker 1>be called the Rosetta Stone. Now, the Rosetta Stone itself

0:05:41.320 --> 0:05:45.120
<v Speaker 1>is a type of monument, and there are carvings on

0:05:45.200 --> 0:05:50.480
<v Speaker 1>the monument that represent an official dynastic decree. The carvings

0:05:50.520 --> 0:05:54.360
<v Speaker 1>are in three different written languages. So at the base

0:05:54.560 --> 0:05:57.599
<v Speaker 1>of the monument you have the carving in ancient Greek,

0:05:58.320 --> 0:06:01.800
<v Speaker 1>above that is Demotic, that is an Egyptian language that

0:06:01.880 --> 0:06:05.800
<v Speaker 1>followed the hieroglyphic language, and at the top are hieroglyphs.

0:06:05.839 --> 0:06:09.640
<v Speaker 1>And since all three carvings represented the same decree, this

0:06:09.720 --> 0:06:14.960
<v Speaker 1>gave experts the opportunity to finally begin deciphering Egyptian hieroglyphs,

0:06:15.000 --> 0:06:20.320
<v Speaker 1>and so began the long process of uncovering lost knowledge.

0:06:20.640 --> 0:06:24.400
<v Speaker 1>And this was helped by subsequent discoveries of similar decrees,

0:06:25.120 --> 0:06:29.960
<v Speaker 1>so that we over time we're able to understand what

0:06:30.240 --> 0:06:33.360
<v Speaker 1>these these hieroglyphs actually stood for. We understood that it

0:06:33.480 --> 0:06:38.360
<v Speaker 1>was a written language that wasn't just purely symbolic. Now,

0:06:38.480 --> 0:06:40.920
<v Speaker 1>my point in telling the story is that we have

0:06:40.960 --> 0:06:44.440
<v Speaker 1>to remind ourselves that while we have ways to record knowledge,

0:06:45.200 --> 0:06:47.719
<v Speaker 1>it would be foolish for us to assume that any

0:06:47.760 --> 0:06:51.960
<v Speaker 1>way that we use is permanent, because we've got plenty

0:06:51.960 --> 0:06:55.080
<v Speaker 1>of examples of knowledge being lost in the past, whether

0:06:55.120 --> 0:06:59.240
<v Speaker 1>it's because people forgot how to access that knowledge, or

0:06:59.800 --> 0:07:03.159
<v Speaker 1>maybe the knowledge was based in folklore and the people

0:07:03.720 --> 0:07:07.159
<v Speaker 1>that were the stewards of that knowledge were wiped out

0:07:07.240 --> 0:07:11.600
<v Speaker 1>or assimilated and the knowledge was lost, or maybe the

0:07:11.640 --> 0:07:14.600
<v Speaker 1>physical copies, if it was like a written language, maybe

0:07:14.600 --> 0:07:17.560
<v Speaker 1>the physical copies were lost. And shout out to the

0:07:17.680 --> 0:07:21.640
<v Speaker 1>late Great Library of Alexandria, which I should add kind

0:07:21.640 --> 0:07:24.080
<v Speaker 1>of faded away, not just because of the famous fire

0:07:24.080 --> 0:07:28.600
<v Speaker 1>set by Julius Caesar's forces, though that clearly was a

0:07:28.680 --> 0:07:32.240
<v Speaker 1>catastrophic event, but also there was a long period in

0:07:32.280 --> 0:07:36.640
<v Speaker 1>which leaders were cracking down on scholars because well, a

0:07:36.640 --> 0:07:38.800
<v Speaker 1>little knowledge is a dangerous thing, so a lot of

0:07:38.800 --> 0:07:42.280
<v Speaker 1>knowledge has got to be absolutely deadly right. But anyway,

0:07:42.760 --> 0:07:46.120
<v Speaker 1>let's skip ahead to the modern era. So even today

0:07:46.400 --> 0:07:50.280
<v Speaker 1>we run the risk of losing access to information because

0:07:50.320 --> 0:07:53.800
<v Speaker 1>we no longer make the stuff, what plays the media

0:07:54.000 --> 0:07:56.160
<v Speaker 1>that we used in the old days, or at least

0:07:56.200 --> 0:07:58.800
<v Speaker 1>in many cases, it is getting really tricky to track

0:07:58.880 --> 0:08:02.920
<v Speaker 1>down the components that can retrieve data from those types

0:08:02.960 --> 0:08:05.680
<v Speaker 1>of media. Right, you might be able to find old

0:08:05.760 --> 0:08:10.600
<v Speaker 1>working equipment that can access certain types of stuff that

0:08:10.640 --> 0:08:14.560
<v Speaker 1>otherwise we no longer can access, but it's it's rare

0:08:14.600 --> 0:08:17.440
<v Speaker 1>that you're gonna find someone make a new version of that.

0:08:17.800 --> 0:08:20.920
<v Speaker 1>It's not impossible. It's not like we've lost all ability

0:08:21.000 --> 0:08:25.880
<v Speaker 1>to It's just that unless there is a pressing financial

0:08:26.760 --> 0:08:30.160
<v Speaker 1>benefit to creating that kind of stuff, no one's gonna

0:08:30.160 --> 0:08:33.280
<v Speaker 1>bother to do it. Because you know, it's expensive to

0:08:33.400 --> 0:08:39.559
<v Speaker 1>produce older types of of technologies, and unless there's a

0:08:39.600 --> 0:08:43.200
<v Speaker 1>financial incentive, no one's gonna do it. Um, it's sad

0:08:43.280 --> 0:08:46.240
<v Speaker 1>to say so. There's also the danger that the media

0:08:46.320 --> 0:08:51.000
<v Speaker 1>we rely upon could wear out and deteriorate over time. So,

0:08:51.120 --> 0:08:56.719
<v Speaker 1>for example, let's consider celluloid or film. Cinematic film degrades

0:08:56.960 --> 0:09:01.720
<v Speaker 1>over time, particularly if it's in a hot and moist environment.

0:09:02.160 --> 0:09:06.080
<v Speaker 1>And you might have heard about some filmmakers storing prints

0:09:06.120 --> 0:09:09.360
<v Speaker 1>of their movies or masters of their movies in old

0:09:09.400 --> 0:09:13.120
<v Speaker 1>salt mines such as the one that's below Hutchinson, Kansas

0:09:13.160 --> 0:09:18.000
<v Speaker 1>in the United States. These subterranean spaces maintain a constant

0:09:18.040 --> 0:09:22.600
<v Speaker 1>temperature of around sixty eight fahrenheit or twenty celsius, and

0:09:22.679 --> 0:09:27.800
<v Speaker 1>they have a low humidity somewhere between like forty humidity.

0:09:27.840 --> 0:09:29.760
<v Speaker 1>Of course, movies are not the only thing stored in

0:09:29.800 --> 0:09:33.520
<v Speaker 1>those minds that in fact, we got the idea because

0:09:33.520 --> 0:09:36.600
<v Speaker 1>of the story of the monument men who ended up

0:09:36.640 --> 0:09:42.840
<v Speaker 1>finding lots of stolen art from various parts of Europe

0:09:42.840 --> 0:09:45.679
<v Speaker 1>that the Nazis had collected and stored in salt mines.

0:09:45.760 --> 0:09:48.839
<v Speaker 1>We ended up kind of using the same idea. So,

0:09:49.000 --> 0:09:52.079
<v Speaker 1>because it's a great way to preserve stuff, if you

0:09:53.080 --> 0:09:56.800
<v Speaker 1>otherwise it's in danger of deterioration. Also, we have to

0:09:57.000 --> 0:09:59.079
<v Speaker 1>acknowledge that while it's a great way to preserve stuff,

0:09:59.120 --> 0:10:02.120
<v Speaker 1>there's a tragedy year because we're also removing it right

0:10:02.280 --> 0:10:06.600
<v Speaker 1>from us. You know, we're storing it and we're preserving it,

0:10:06.640 --> 0:10:11.160
<v Speaker 1>but to what end if you can't access it, then

0:10:11.280 --> 0:10:14.160
<v Speaker 1>it doesn't really like there's a lot of questions. There

0:10:14.160 --> 0:10:17.640
<v Speaker 1>are philosophical questions. If you have a priceless work of

0:10:17.760 --> 0:10:20.400
<v Speaker 1>art stored an assault mine and no one can go there,

0:10:21.000 --> 0:10:23.280
<v Speaker 1>is it the same as not having it at all?

0:10:24.080 --> 0:10:26.280
<v Speaker 1>Now in the case of film. A lot of studios

0:10:26.280 --> 0:10:29.680
<v Speaker 1>will actually use those master recordings when they want to

0:10:29.720 --> 0:10:32.560
<v Speaker 1>do a remastered version of the film they want to

0:10:32.559 --> 0:10:35.800
<v Speaker 1>release it on, say like Blu ray or something, they'll

0:10:35.800 --> 0:10:38.959
<v Speaker 1>go to the the original print that's stored in a

0:10:39.080 --> 0:10:41.960
<v Speaker 1>salt mine and they'll pull from that. But yeah, there's

0:10:42.000 --> 0:10:44.959
<v Speaker 1>lots of other stuff besides just film down there, anything

0:10:45.000 --> 0:10:47.319
<v Speaker 1>that needs a controlled environment in order to stop or

0:10:47.360 --> 0:10:52.719
<v Speaker 1>at least slow deterioration. Now, magnetic tape is another important

0:10:52.840 --> 0:10:56.520
<v Speaker 1>storage method, and we've been using magnetic tape as storage

0:10:56.600 --> 0:11:00.400
<v Speaker 1>since the mid twenty century, around nine or so, and

0:11:00.440 --> 0:11:03.240
<v Speaker 1>again the basic principle behind it dates back to the

0:11:03.320 --> 0:11:08.360
<v Speaker 1>late nineteenth century. That was when we were using magnetic wire.

0:11:09.360 --> 0:11:13.040
<v Speaker 1>But whether it's real to real tape, or cassettes or

0:11:13.280 --> 0:11:17.040
<v Speaker 1>VHS tapes, we've relied on this methodology to store all

0:11:17.080 --> 0:11:22.160
<v Speaker 1>sorts of information, from you know, computer information to music

0:11:22.200 --> 0:11:24.439
<v Speaker 1>in the case of like the cassette tapes of the

0:11:24.520 --> 0:11:30.040
<v Speaker 1>eighties nineties or the VHS video tapes, all sorts of

0:11:30.040 --> 0:11:34.040
<v Speaker 1>info we have committed to magnetic tape, and a lot

0:11:34.080 --> 0:11:36.680
<v Speaker 1>of companies still rely on magnetic tape for long term

0:11:36.720 --> 0:11:40.720
<v Speaker 1>storage and backups. When I use long term storage. I'm

0:11:40.760 --> 0:11:44.800
<v Speaker 1>speaking relatively, as we will see now, some older forms

0:11:44.800 --> 0:11:48.760
<v Speaker 1>of magnetic tape are largely obsolete because the devices we'd

0:11:48.840 --> 0:11:52.719
<v Speaker 1>use to read the data from them are out of production.

0:11:53.200 --> 0:11:56.000
<v Speaker 1>You might find a working device here or there, but

0:11:56.200 --> 0:11:59.160
<v Speaker 1>they can be pretty rare, and being mechanical in nature,

0:11:59.679 --> 0:12:03.800
<v Speaker 1>they will eventually require maintenance or they'll stop working. And

0:12:03.880 --> 0:12:06.199
<v Speaker 1>when you're talking about this kind of stuff, often you're

0:12:06.240 --> 0:12:09.960
<v Speaker 1>talking about things that have parts that no one's making anymore.

0:12:10.120 --> 0:12:12.640
<v Speaker 1>So it becomes very challenging to keep them in good

0:12:12.679 --> 0:12:16.200
<v Speaker 1>working order because there's a limited supply of components you

0:12:16.200 --> 0:12:19.760
<v Speaker 1>can use to make replacements when something breaks down. On

0:12:19.840 --> 0:12:23.520
<v Speaker 1>top of all that, magnetic information itself can degrade over time,

0:12:24.360 --> 0:12:27.040
<v Speaker 1>actually can degrade really quickly if it's in the presence

0:12:27.040 --> 0:12:29.640
<v Speaker 1>of a strong magnetic field, which is why as a

0:12:29.720 --> 0:12:31.720
<v Speaker 1>kid I was told never to bring a magnet close

0:12:31.720 --> 0:12:35.400
<v Speaker 1>to a computer or computer disks because you could actually

0:12:35.920 --> 0:12:41.280
<v Speaker 1>uh corrupt information that's stored on those those devices, because

0:12:41.400 --> 0:12:45.240
<v Speaker 1>the magnet would realign the magnetic components that were on

0:12:45.360 --> 0:12:48.160
<v Speaker 1>this plastic film or in the case of a computer,

0:12:48.840 --> 0:12:53.559
<v Speaker 1>uh arraid on a platter inside the hard disk drive. Now,

0:12:53.600 --> 0:12:59.720
<v Speaker 1>on average if stored in decent conditions, magnetic tape typically

0:12:59.720 --> 0:13:02.960
<v Speaker 1>will retained data from anywhere between ten to twenty years.

0:13:03.600 --> 0:13:07.080
<v Speaker 1>When stored in prime conditions like in that salt mine,

0:13:07.120 --> 0:13:10.520
<v Speaker 1>for example, you might stretch it to around thirty years.

0:13:10.840 --> 0:13:13.360
<v Speaker 1>So magnetic tape can hold onto data for a while,

0:13:14.000 --> 0:13:19.760
<v Speaker 1>but certainly not indefinitely. It will sooner or later degrade

0:13:19.800 --> 0:13:23.040
<v Speaker 1>to a point where the the information will be corrupted

0:13:23.480 --> 0:13:28.480
<v Speaker 1>or irretrievable. Now, on a similar note, let's talk floppy disks.

0:13:28.760 --> 0:13:30.559
<v Speaker 1>So when I was a kid, our Apple to E

0:13:30.800 --> 0:13:34.360
<v Speaker 1>computer had a five and a quarter inch floppy disk drive.

0:13:35.200 --> 0:13:37.520
<v Speaker 1>These were not the first floppy discs. There were older ones.

0:13:37.559 --> 0:13:40.640
<v Speaker 1>There were larger ones. IBM created eight inch floppy disks

0:13:40.679 --> 0:13:45.080
<v Speaker 1>for example, And the disks that I was familiar with

0:13:45.240 --> 0:13:47.520
<v Speaker 1>back when I was using the Apple to E were

0:13:47.559 --> 0:13:51.760
<v Speaker 1>these plastic envelopes, and the envelopes were covering a disc

0:13:51.880 --> 0:13:56.559
<v Speaker 1>of magnetic film on the inside, and it was on

0:13:56.640 --> 0:14:00.839
<v Speaker 1>this magnetic disc that you could save and retreat data.

0:14:01.240 --> 0:14:02.839
<v Speaker 1>And I actually had to look this up because I

0:14:02.880 --> 0:14:05.400
<v Speaker 1>could not remember it myself, but the original five and

0:14:05.480 --> 0:14:08.439
<v Speaker 1>a quarter inch floppy disks could hold up to nine

0:14:09.040 --> 0:14:12.040
<v Speaker 1>bytes of data. That's when they were first created, so

0:14:12.120 --> 0:14:18.160
<v Speaker 1>that's just ninety kilobytes. But over time, you know, engineers

0:14:18.240 --> 0:14:23.280
<v Speaker 1>improved the technology. They increased the capacity of floppy disks. Typically,

0:14:23.360 --> 0:14:26.240
<v Speaker 1>they did this by creating more precise read write heads

0:14:26.360 --> 0:14:31.600
<v Speaker 1>so they could store data in smaller physical sizes, which

0:14:31.680 --> 0:14:34.120
<v Speaker 1>meant you could cram more of it onto the same

0:14:34.200 --> 0:14:37.640
<v Speaker 1>sized disc. They also figured out how to multilayer discs,

0:14:37.760 --> 0:14:42.440
<v Speaker 1>so that increased storage as well. I think, you know,

0:14:42.840 --> 0:14:47.760
<v Speaker 1>some disks maxed out at around so significantly more than

0:14:47.880 --> 0:14:50.240
<v Speaker 1>ninety but still weigh less than what we use today.

0:14:51.720 --> 0:14:54.760
<v Speaker 1>Now I'm gonna talk more about floppy disks and other

0:14:54.840 --> 0:15:00.280
<v Speaker 1>forms of storage and why all these different types kind

0:15:00.280 --> 0:15:03.320
<v Speaker 1>of a limited shelf life of one span or another.

0:15:03.480 --> 0:15:14.160
<v Speaker 1>But before we get to that, let's take a quick break. Okay,

0:15:14.560 --> 0:15:17.320
<v Speaker 1>we're back, and we were talking about floppy discs. Well,

0:15:17.560 --> 0:15:21.320
<v Speaker 1>my parents write novels, and so my dad's first books,

0:15:21.840 --> 0:15:23.880
<v Speaker 1>which were written in the early eighties, they were written

0:15:23.960 --> 0:15:26.920
<v Speaker 1>on that old Apple to E computer, and he would

0:15:27.000 --> 0:15:30.960
<v Speaker 1>save chapters of his books too floppy disks. Each novel

0:15:31.040 --> 0:15:33.840
<v Speaker 1>would take up several discs, like I don't know, around

0:15:34.200 --> 0:15:36.920
<v Speaker 1>a dozen or so. I can't quite remember I remember

0:15:36.960 --> 0:15:41.400
<v Speaker 1>we had disc holders that would hold like maybe three

0:15:41.520 --> 0:15:44.560
<v Speaker 1>of his novels, because that's how many discs would be

0:15:45.400 --> 0:15:48.320
<v Speaker 1>taken up just by you know, storing chapters onto them.

0:15:49.160 --> 0:15:52.560
<v Speaker 1>I'm not sure if he actually still owns those floppy discs,

0:15:52.920 --> 0:15:54.800
<v Speaker 1>but I imagine that even if he does, he doesn't

0:15:54.840 --> 0:15:56.640
<v Speaker 1>have any way to check and see if the data

0:15:56.760 --> 0:15:59.520
<v Speaker 1>is still there or not. He would need an Apple

0:15:59.560 --> 0:16:03.640
<v Speaker 1>to E or an emulator to simulate an Apple to

0:16:03.760 --> 0:16:06.040
<v Speaker 1>E on another machine. Plus he would have to have

0:16:06.160 --> 0:16:09.560
<v Speaker 1>a floppy disk drive connected to whatever computer he was

0:16:09.680 --> 0:16:12.880
<v Speaker 1>using in order to try and read those disks. And

0:16:13.120 --> 0:16:16.680
<v Speaker 1>floppy disk drives are not completely gone. They you can

0:16:16.760 --> 0:16:21.880
<v Speaker 1>still find them. They are increasingly rare, however, so it's

0:16:21.880 --> 0:16:24.840
<v Speaker 1>easy to imagine that a day will come when anything

0:16:24.920 --> 0:16:28.120
<v Speaker 1>stored on disks like that, like my dad's books, will

0:16:28.200 --> 0:16:31.040
<v Speaker 1>just become lost simply because no one makes the stuff

0:16:31.080 --> 0:16:34.200
<v Speaker 1>capable of reading it anymore. And the stuff that already

0:16:34.240 --> 0:16:39.960
<v Speaker 1>exists will eventually break down. Um and you know, the

0:16:40.920 --> 0:16:45.680
<v Speaker 1>the actual magnetic information on the discs will degrade over

0:16:45.760 --> 0:16:50.400
<v Speaker 1>time to just like with magnetic tape. The eventually you'll

0:16:50.480 --> 0:16:53.720
<v Speaker 1>you'll have some of those magnetic particles move out of alignment.

0:16:54.320 --> 0:16:56.840
<v Speaker 1>That's going to corrupt your data. I know, I keep

0:16:56.840 --> 0:16:58.960
<v Speaker 1>saying data and data. I know I do that. I

0:16:59.160 --> 0:17:01.440
<v Speaker 1>don't know why do that, and I can't predict when

0:17:01.480 --> 0:17:03.760
<v Speaker 1>it happens. It just does. I apologize for it though,

0:17:03.800 --> 0:17:06.280
<v Speaker 1>because I know it drives some of you crazy, and

0:17:06.600 --> 0:17:11.239
<v Speaker 1>my apologies. It just happens anyway, Those particles will move

0:17:11.280 --> 0:17:14.879
<v Speaker 1>out of alignment, the information gets corrupted. So yeah, switch

0:17:14.920 --> 0:17:17.640
<v Speaker 1>to information there, and then you can't retrieve it anymore.

0:17:17.840 --> 0:17:19.680
<v Speaker 1>So that can happen to even if you have a

0:17:19.800 --> 0:17:23.919
<v Speaker 1>working computer system that could theoretically pull that information off

0:17:23.960 --> 0:17:26.640
<v Speaker 1>the disk. Sometimes the information on the disc itself will

0:17:26.680 --> 0:17:29.520
<v Speaker 1>become corrupt. Now, we also have to keep in mind

0:17:30.320 --> 0:17:33.280
<v Speaker 1>that media that we still use today because hardly. I mean,

0:17:33.400 --> 0:17:36.400
<v Speaker 1>people do still use floppy disks depending on the situation,

0:17:36.600 --> 0:17:38.720
<v Speaker 1>but it's pretty rare. But even the stuff that we

0:17:38.800 --> 0:17:42.960
<v Speaker 1>do use today, eventually that's gonna become obsolete too. Just

0:17:43.119 --> 0:17:45.600
<v Speaker 1>a few years ago, compact discs were the go to

0:17:45.800 --> 0:17:48.840
<v Speaker 1>for data storage, at least for personal computers, though a

0:17:48.920 --> 0:17:51.840
<v Speaker 1>lot of enterprises would continue to rely on magnetic tape

0:17:51.880 --> 0:17:56.000
<v Speaker 1>for more long term backups, and compact discs are a

0:17:56.119 --> 0:17:59.880
<v Speaker 1>type of optical storage, meaning that rather than using magnetism

0:18:00.240 --> 0:18:06.040
<v Speaker 1>to align tiny particles on a physical surface, we're using

0:18:06.280 --> 0:18:10.119
<v Speaker 1>lasers to write and to read from these disks. UH,

0:18:10.560 --> 0:18:13.679
<v Speaker 1>the information is stored in water called pits and lands,

0:18:14.080 --> 0:18:18.960
<v Speaker 1>pits being designated pit in the surface, and lands being

0:18:19.000 --> 0:18:22.560
<v Speaker 1>the spaces between PITSU. The rewriteable CD is actually kind

0:18:22.560 --> 0:18:27.199
<v Speaker 1>of use foggy and clear UH sections that are very

0:18:27.320 --> 0:18:28.840
<v Speaker 1>very tiny. You wouldn't be able to see them with

0:18:28.840 --> 0:18:32.680
<v Speaker 1>the naked eye. Now, compact discs allow us to create

0:18:32.720 --> 0:18:35.360
<v Speaker 1>a more dense storage system, so we could put way

0:18:35.520 --> 0:18:39.480
<v Speaker 1>more information on a single CD than we could with

0:18:39.560 --> 0:18:43.560
<v Speaker 1>stuff like floppy disks. Now, unlike cassettes and floppy disks,

0:18:43.640 --> 0:18:47.119
<v Speaker 1>optical discs are not affected by magnetism. So if you

0:18:47.240 --> 0:18:49.800
<v Speaker 1>did bring a powerful magnet close to a bunch of

0:18:49.840 --> 0:18:53.120
<v Speaker 1>floppy disks or cassette tapes or anything that uses magnetic storage,

0:18:53.920 --> 0:18:57.119
<v Speaker 1>you would scramble the information on there because the powerful

0:18:57.160 --> 0:19:00.760
<v Speaker 1>magnet would realign the magnetic particles that are on the tape.

0:19:01.320 --> 0:19:04.879
<v Speaker 1>But optical discs don't have magnetic particles, so they would

0:19:05.000 --> 0:19:09.560
<v Speaker 1>be immune to that kind of interference. However, this does

0:19:09.600 --> 0:19:14.840
<v Speaker 1>not mean that optical discs last forever, so the there

0:19:14.920 --> 0:19:18.119
<v Speaker 1>are many layers on a compact disc. Same thing with

0:19:18.240 --> 0:19:20.960
<v Speaker 1>DVDs and blue race, by the way, there are several

0:19:21.080 --> 0:19:26.400
<v Speaker 1>layers involved, and these layers can have chemical reactions in them,

0:19:26.920 --> 0:19:29.800
<v Speaker 1>and those chemical reactions can cause those layers to degrade

0:19:29.880 --> 0:19:33.680
<v Speaker 1>over time. So like a CD that's stored in a

0:19:33.840 --> 0:19:37.639
<v Speaker 1>very humid and warm place, like if people had stored

0:19:37.760 --> 0:19:40.879
<v Speaker 1>their CDs, their music CDs inside their car in the

0:19:40.960 --> 0:19:43.960
<v Speaker 1>summer and Georgia, they might find that those CDs don't

0:19:44.040 --> 0:19:46.560
<v Speaker 1>last that long, like they might last a few seasons,

0:19:46.640 --> 0:19:51.320
<v Speaker 1>but eventually they degrade and they you know, if you're

0:19:51.359 --> 0:19:54.080
<v Speaker 1>in a hot and humid environment, then disc is going

0:19:54.119 --> 0:19:58.960
<v Speaker 1>to degrade faster, not like instantaneously, but it will start

0:19:59.040 --> 0:20:01.639
<v Speaker 1>to degrade faster than it would if you stored it

0:20:01.760 --> 0:20:07.600
<v Speaker 1>in a cooler, dry place. And that outer layer on

0:20:07.720 --> 0:20:11.159
<v Speaker 1>a CD, that's the clear layer, right, it's protective and

0:20:11.280 --> 0:20:13.399
<v Speaker 1>it's clear so that a laser can go through it.

0:20:14.160 --> 0:20:16.760
<v Speaker 1>But sometimes that clear layer can start to rot away

0:20:17.080 --> 0:20:21.120
<v Speaker 1>and it can leave the reflective layer that's underneath it exposed.

0:20:21.480 --> 0:20:24.600
<v Speaker 1>And with some CDs, that reflective layer is made up

0:20:24.800 --> 0:20:29.680
<v Speaker 1>of a silver or sometimes a silver compound and silver

0:20:29.800 --> 0:20:34.560
<v Speaker 1>when exposed to air will tarnish. The tarnished silver won't

0:20:34.600 --> 0:20:37.280
<v Speaker 1>reflect a laser properly, and so you start to get

0:20:37.560 --> 0:20:39.920
<v Speaker 1>errors when you're trying to read information off of that

0:20:40.359 --> 0:20:43.320
<v Speaker 1>kind of c D. Now, not all CDs were made

0:20:43.680 --> 0:20:47.040
<v Speaker 1>that way, right, so only some CDs have this particular

0:20:47.160 --> 0:20:50.800
<v Speaker 1>bronzing issue. In fact, our research group determined that the

0:20:50.920 --> 0:20:54.679
<v Speaker 1>c ds that really have this specific problem we're all

0:20:54.800 --> 0:20:58.840
<v Speaker 1>pressed in Blackburn, Lancashire, England, between the year's nineteen eight

0:20:59.200 --> 0:21:03.560
<v Speaker 1>and nineteen nine D three. That's pretty darn specific. Now.

0:21:04.680 --> 0:21:07.640
<v Speaker 1>The issue here, though, is that there's really no way

0:21:07.720 --> 0:21:11.720
<v Speaker 1>to give an average lifespan for a compact disc because

0:21:11.760 --> 0:21:14.679
<v Speaker 1>there's no such thing as an average compact discs. There

0:21:14.720 --> 0:21:18.440
<v Speaker 1>were there were so many different manufacturing and pressing processes

0:21:18.480 --> 0:21:24.760
<v Speaker 1>and recording processes that different ones could last a different

0:21:25.240 --> 0:21:28.640
<v Speaker 1>you know, theoretical maximum amount of time. So we can't

0:21:28.840 --> 0:21:31.879
<v Speaker 1>really answer the question how long on average will a

0:21:31.920 --> 0:21:34.520
<v Speaker 1>s c D last. I've seen a lot of people

0:21:34.560 --> 0:21:37.840
<v Speaker 1>suggest five to ten years, some people saying ten to twenty,

0:21:37.960 --> 0:21:40.440
<v Speaker 1>some people going as far as fifty. I think it

0:21:40.520 --> 0:21:43.080
<v Speaker 1>really depends on the way the CD was made and

0:21:43.359 --> 0:21:47.399
<v Speaker 1>what storage facility it's in, Like, is it in a

0:21:47.520 --> 0:21:51.120
<v Speaker 1>house where it's kept out of sunlight because UV radiation

0:21:51.200 --> 0:21:55.240
<v Speaker 1>can affect c D suh. Is it kept cool and dry,

0:21:55.440 --> 0:21:58.280
<v Speaker 1>then it's gonna last longer. Is it not handled a lot?

0:21:58.760 --> 0:22:03.000
<v Speaker 1>Like if it's your favorite music CD and you handle

0:22:03.080 --> 0:22:07.640
<v Speaker 1>it a lot, then it's gonna degrade faster. Again, not instantaneously,

0:22:07.880 --> 0:22:10.520
<v Speaker 1>and it may not even be noticeable at first, but

0:22:10.800 --> 0:22:13.560
<v Speaker 1>eventually you might get the things where it starts to

0:22:13.640 --> 0:22:16.280
<v Speaker 1>skip on a certain track, or it won't even play

0:22:16.440 --> 0:22:20.879
<v Speaker 1>certain tracks. That will happen over time. It's a similar

0:22:20.960 --> 0:22:24.040
<v Speaker 1>story for other optical formats, which include you know, DVDs

0:22:24.080 --> 0:22:27.560
<v Speaker 1>and Blu ray discs. These two have a limited lifespan,

0:22:27.720 --> 0:22:30.399
<v Speaker 1>though that lifespan may stretch to as long as a

0:22:30.480 --> 0:22:34.440
<v Speaker 1>century under ideal conditions. In a century is a long

0:22:34.520 --> 0:22:36.840
<v Speaker 1>time for a single person, right, I mean, that's that's

0:22:37.040 --> 0:22:41.320
<v Speaker 1>a significant amount of time. However, if we step outside

0:22:41.640 --> 0:22:45.360
<v Speaker 1>of a humans lifespan and we look at it from

0:22:45.440 --> 0:22:50.280
<v Speaker 1>the perspective of, you know, a historical account, then a

0:22:50.359 --> 0:22:53.240
<v Speaker 1>hundred years is not long at all. I mean, imagine

0:22:53.280 --> 0:22:57.240
<v Speaker 1>for a moment, if you had no access to any

0:22:57.359 --> 0:23:01.520
<v Speaker 1>information that was recorded before nineteen twenty because all the

0:23:01.680 --> 0:23:05.400
<v Speaker 1>media that we had used to record info on had

0:23:05.440 --> 0:23:10.840
<v Speaker 1>fallen apart or was otherwise unusable or inaccessible, that nothing

0:23:10.920 --> 0:23:14.280
<v Speaker 1>before nineteen twenty two would be knowable apart from what

0:23:14.440 --> 0:23:19.760
<v Speaker 1>people wrote about those times post nineteen two. That would

0:23:19.800 --> 0:23:24.240
<v Speaker 1>be crazy, right, But that's the kind of situation we're

0:23:24.320 --> 0:23:28.760
<v Speaker 1>in when we start looking at digital information. All right, Well,

0:23:28.800 --> 0:23:31.440
<v Speaker 1>what about we look at like hard drives, hard disk

0:23:31.520 --> 0:23:34.040
<v Speaker 1>drives and solid state drives, you know, the stuff that's

0:23:34.119 --> 0:23:37.080
<v Speaker 1>in your computer systems, your smartphones, that kind of thing.

0:23:37.320 --> 0:23:41.000
<v Speaker 1>What what do they have? You know, how long will

0:23:41.080 --> 0:23:45.920
<v Speaker 1>information last in those? Well, they stored information in different ways.

0:23:46.240 --> 0:23:50.120
<v Speaker 1>Hard disk drives have one or more platters in them,

0:23:50.720 --> 0:23:53.840
<v Speaker 1>and each platter has a magnetic coding on it upon

0:23:53.920 --> 0:23:57.840
<v Speaker 1>which information can be stored. So, just like cassettes and

0:23:57.960 --> 0:24:01.800
<v Speaker 1>floppy disks and other magnetic storage methods, hard disk drives

0:24:01.880 --> 0:24:05.160
<v Speaker 1>can be affected by powerful magnetic fields because they too,

0:24:05.440 --> 0:24:11.200
<v Speaker 1>store information magnetically. Hard disk drives have moving parts, so

0:24:11.400 --> 0:24:16.280
<v Speaker 1>the platters spin quite quite quickly in fact, and an

0:24:16.359 --> 0:24:20.480
<v Speaker 1>actuator mechanical arm with a ReadWrite quote unquote head on it.

0:24:20.640 --> 0:24:24.920
<v Speaker 1>This is the bit that either can read the magnetic

0:24:25.040 --> 0:24:28.120
<v Speaker 1>particles that are stored on a platter, or it can

0:24:28.240 --> 0:24:33.360
<v Speaker 1>actually exert a magnetic field that aligns the particles. When

0:24:33.400 --> 0:24:36.960
<v Speaker 1>you're writing information on the platter, it moves across the

0:24:37.000 --> 0:24:40.280
<v Speaker 1>platter and it starts to retrieve or right information to

0:24:40.359 --> 0:24:44.720
<v Speaker 1>the disc itself. And because we're talking about moving parts here,

0:24:45.160 --> 0:24:49.280
<v Speaker 1>stuff can and does wear down over time and use.

0:24:49.760 --> 0:24:51.960
<v Speaker 1>If it gets a lot of use, it wears out

0:24:52.040 --> 0:24:55.240
<v Speaker 1>more quickly. Also, it means that you should be gentle

0:24:55.359 --> 0:24:57.560
<v Speaker 1>when you're moving anything that happens to have a hard

0:24:57.640 --> 0:25:00.040
<v Speaker 1>disk drive inside of it, because a good whack and

0:25:00.200 --> 0:25:03.920
<v Speaker 1>damage the delicate parts. If you knock that actuator arm

0:25:03.960 --> 0:25:07.120
<v Speaker 1>out of alignment, that's a big problem. It's it's going

0:25:07.200 --> 0:25:12.240
<v Speaker 1>to be impossible to read or write stuff reliably to

0:25:12.400 --> 0:25:16.440
<v Speaker 1>that hard disk drive. Now, hard drives don't tend to

0:25:16.600 --> 0:25:19.840
<v Speaker 1>last very long because of those mechanical parts. I've seen

0:25:20.040 --> 0:25:23.760
<v Speaker 1>estimates of the lifespan for hard disk drives lasting somewhere

0:25:23.800 --> 0:25:27.920
<v Speaker 1>between three two maybe six and a half years, seven years.

0:25:28.560 --> 0:25:31.120
<v Speaker 1>Some give it a little bit longer, some a little

0:25:31.119 --> 0:25:33.720
<v Speaker 1>bit shorter. Of course, a hard disk drive can last

0:25:34.040 --> 0:25:38.800
<v Speaker 1>longer than a decade, but that's you know, if we're

0:25:38.840 --> 0:25:41.960
<v Speaker 1>looking at typical use and we're looking at the average

0:25:42.000 --> 0:25:44.440
<v Speaker 1>lifespan of hard disk drives, we tend to fall on

0:25:44.520 --> 0:25:48.720
<v Speaker 1>that three to seven year range. So your mileage may vary.

0:25:49.119 --> 0:25:52.080
<v Speaker 1>It may depend upon how you use your hard disk

0:25:52.119 --> 0:25:57.280
<v Speaker 1>drive and the setting that you're in. So they will

0:25:57.359 --> 0:26:01.200
<v Speaker 1>eventually break down. Also, even if they don't down sooner

0:26:01.359 --> 0:26:05.399
<v Speaker 1>or later, really later, that magnetic information will start to

0:26:05.480 --> 0:26:10.520
<v Speaker 1>move out of alignment just naturally. And so even if

0:26:10.960 --> 0:26:15.119
<v Speaker 1>you were to preserve a hard disk drive perfectly and

0:26:15.680 --> 0:26:18.119
<v Speaker 1>come back to it in a century, chances are a

0:26:18.160 --> 0:26:20.520
<v Speaker 1>lot of the information would no longer be accessible because

0:26:20.640 --> 0:26:23.560
<v Speaker 1>the actual magnetic particles would no longer be in the

0:26:23.600 --> 0:26:28.760
<v Speaker 1>proper alignment. Solid state drives store information in a totally

0:26:28.960 --> 0:26:32.880
<v Speaker 1>different way from hard disk drives, So instead of aligning

0:26:32.960 --> 0:26:37.960
<v Speaker 1>magnetic particles, and ss D stores information through flash memory

0:26:38.040 --> 0:26:41.320
<v Speaker 1>similar to USB sticks and other types of flash drives.

0:26:41.920 --> 0:26:45.920
<v Speaker 1>These drives store information using nanned flash that's in a

0:26:46.240 --> 0:26:49.800
<v Speaker 1>n D and that in turn is composed of what

0:26:49.880 --> 0:26:53.200
<v Speaker 1>are called floating gate transistors. And all of this gets

0:26:53.240 --> 0:26:56.120
<v Speaker 1>super technical, but let's just kind of imagine it this way.

0:26:56.720 --> 0:27:00.400
<v Speaker 1>Each floating gate can be either charged, which means it's

0:27:00.400 --> 0:27:03.160
<v Speaker 1>a zero, or it could be non charged, which means

0:27:03.200 --> 0:27:05.680
<v Speaker 1>it's a one. So it gets a little bit confusing

0:27:05.880 --> 0:27:09.400
<v Speaker 1>because we often think of binary with zero being off

0:27:10.040 --> 0:27:12.920
<v Speaker 1>and one being on. But in this case, zero means

0:27:13.040 --> 0:27:15.520
<v Speaker 1>that there is a charge in a cell and one

0:27:15.600 --> 0:27:18.600
<v Speaker 1>means there is no charge in that cell, and a

0:27:18.760 --> 0:27:21.280
<v Speaker 1>drive is made up of a grid of these cells.

0:27:22.480 --> 0:27:24.919
<v Speaker 1>So USB flash drives and s s d s are

0:27:25.040 --> 0:27:28.880
<v Speaker 1>non volatile memory. That means that they retain information even

0:27:28.960 --> 0:27:31.840
<v Speaker 1>if they are not receiving power. Right, So, if you

0:27:31.920 --> 0:27:34.639
<v Speaker 1>were to turn off your computer and it has an

0:27:34.760 --> 0:27:38.280
<v Speaker 1>SSD drive in it, you didn't just wipe out everything

0:27:38.359 --> 0:27:41.600
<v Speaker 1>that was stored on that SSD. It remains there. However,

0:27:42.200 --> 0:27:45.040
<v Speaker 1>if an S s D goes without power for an

0:27:45.119 --> 0:27:49.400
<v Speaker 1>extended period, so we're talking like five to ten years here,

0:27:49.920 --> 0:27:53.280
<v Speaker 1>it can experience what is called bit rot That is,

0:27:53.560 --> 0:27:57.760
<v Speaker 1>some of those charged gates might lose their charge without

0:27:57.800 --> 0:28:02.240
<v Speaker 1>access to power, and over time the information degrades. So

0:28:02.520 --> 0:28:05.440
<v Speaker 1>s s d s are not immune to deterioration either.

0:28:06.119 --> 0:28:09.640
<v Speaker 1>You know, given enough time, the information on those will

0:28:09.680 --> 0:28:13.280
<v Speaker 1>be corrupted as well. Without any other external forces being

0:28:13.320 --> 0:28:17.359
<v Speaker 1>applied to the S s D s well, what about

0:28:17.480 --> 0:28:21.160
<v Speaker 1>cloud storage, because that's changed everything, right. I mean, there's

0:28:21.200 --> 0:28:23.600
<v Speaker 1>so much of the information that we use day to

0:28:23.720 --> 0:28:27.399
<v Speaker 1>day that isn't even stored on our our native device

0:28:27.560 --> 0:28:31.000
<v Speaker 1>at all, or what is stored in our native devices

0:28:31.040 --> 0:28:36.639
<v Speaker 1>a temporary representation of that file. The actual file lives

0:28:36.800 --> 0:28:40.560
<v Speaker 1>in the cloud. Well, assuming that the company that's providing

0:28:40.600 --> 0:28:44.440
<v Speaker 1>the storage remains strong, data stored in the cloud tends

0:28:44.480 --> 0:28:48.040
<v Speaker 1>to be pretty darn resilient. And that's because in order

0:28:48.120 --> 0:28:52.080
<v Speaker 1>to provide a reputable cloud storage service, or really any

0:28:52.160 --> 0:28:57.840
<v Speaker 1>cloud service, companies have to ensure redundancy. Now, that just

0:28:58.000 --> 0:29:01.520
<v Speaker 1>means that any information that's stored to the cloud system

0:29:01.640 --> 0:29:04.960
<v Speaker 1>has to be stored on multiple machines, because remember, cloud

0:29:05.080 --> 0:29:09.000
<v Speaker 1>just means someone else's computer. That's really what the cloud is.

0:29:09.400 --> 0:29:11.800
<v Speaker 1>When you're storing stuff in the cloud, it's not like

0:29:12.080 --> 0:29:14.760
<v Speaker 1>just floating around in the Internet. It's being stored on

0:29:15.600 --> 0:29:21.120
<v Speaker 1>servers that are part of some massive data server farm

0:29:21.760 --> 0:29:25.440
<v Speaker 1>that are owned by some even more massive company like

0:29:25.800 --> 0:29:31.720
<v Speaker 1>Amazon or Microsoft or Google. Now, the reason why these

0:29:31.800 --> 0:29:36.320
<v Speaker 1>companies store the information on multiple machines is that should

0:29:36.400 --> 0:29:41.520
<v Speaker 1>a single machine holding information malfunctions or I don't know,

0:29:41.560 --> 0:29:45.040
<v Speaker 1>it goes on fire, or something. There are backups on

0:29:45.200 --> 0:29:49.840
<v Speaker 1>other machines, so the customer ideally never even notices that

0:29:50.000 --> 0:29:53.560
<v Speaker 1>there's any problem. There's no interruption of service, there's no delay,

0:29:54.400 --> 0:29:58.040
<v Speaker 1>their information is still on quote unquote the cloud, when

0:29:58.080 --> 0:30:01.920
<v Speaker 1>really it's on multiple machines. So this is important because

0:30:02.040 --> 0:30:06.760
<v Speaker 1>most of these data server farm places, they're using really

0:30:06.960 --> 0:30:10.880
<v Speaker 1>cheap components, like lots of them, but they're inexpensive and

0:30:10.960 --> 0:30:13.920
<v Speaker 1>it's you know, it's just off the shelf inexpensive components

0:30:14.080 --> 0:30:18.719
<v Speaker 1>to store all this information or to run processes. Uh.

0:30:19.000 --> 0:30:21.400
<v Speaker 1>That's what allows them to have this kind of redundancy

0:30:21.480 --> 0:30:25.040
<v Speaker 1>because they're not spending ridiculous amounts of money to get

0:30:25.600 --> 0:30:28.120
<v Speaker 1>state of the art machines in there. They don't need that.

0:30:28.800 --> 0:30:31.560
<v Speaker 1>They just need machines that are you know, more or

0:30:31.640 --> 0:30:35.080
<v Speaker 1>less reliable and more importantly inexpensive, so that you can

0:30:35.120 --> 0:30:38.160
<v Speaker 1>have lots of them so that you have backup. So

0:30:38.240 --> 0:30:41.680
<v Speaker 1>in the background, these companies can replace broken or damage

0:30:41.720 --> 0:30:45.120
<v Speaker 1>systems with newer ones. They can migrate copies of information

0:30:45.640 --> 0:30:49.440
<v Speaker 1>onto new machines or existing machines, keep things going smoothly,

0:30:49.600 --> 0:30:53.200
<v Speaker 1>and the customers never noticed an issue. Now there is

0:30:53.240 --> 0:30:56.000
<v Speaker 1>a caveat there which I will get to after we

0:30:56.120 --> 0:31:05.760
<v Speaker 1>come back from this break. So before the break, I

0:31:05.880 --> 0:31:10.440
<v Speaker 1>alluded to a caveat about you know, having these indefinitely

0:31:11.240 --> 0:31:16.360
<v Speaker 1>resilient data storage systems using the cloud, and that is

0:31:16.560 --> 0:31:19.520
<v Speaker 1>I said at the beginning, assuming the company providing the

0:31:19.600 --> 0:31:23.840
<v Speaker 1>storage remains strong. So we have to remember that much

0:31:23.920 --> 0:31:26.560
<v Speaker 1>of cloud storage out there is resting in these few

0:31:27.040 --> 0:31:30.480
<v Speaker 1>big companies, and they are really big and thus pretty

0:31:30.640 --> 0:31:35.280
<v Speaker 1>resilient to change into going out of business, but they're

0:31:35.320 --> 0:31:39.840
<v Speaker 1>not immune to it. Even companies like Amazon, Microsoft and

0:31:39.920 --> 0:31:44.320
<v Speaker 1>Google have their vulnerabilities, and in fact, we're seeing increased

0:31:44.760 --> 0:31:47.520
<v Speaker 1>pressure from around the world to break some of these

0:31:47.600 --> 0:31:51.480
<v Speaker 1>companies up because they are so dominant in their respective spaces.

0:31:52.320 --> 0:31:54.560
<v Speaker 1>So the odds of these companies going out of business

0:31:54.600 --> 0:31:59.160
<v Speaker 1>are really really low, but they're not zero, or at

0:31:59.240 --> 0:32:02.040
<v Speaker 1>least it's not zero that they won't be split up,

0:32:02.280 --> 0:32:07.680
<v Speaker 1>and that ultimately that could lead to discontinuation of services

0:32:07.720 --> 0:32:11.480
<v Speaker 1>in some areas. So we have to remember that the

0:32:11.880 --> 0:32:16.160
<v Speaker 1>access to this information remains dependent upon these various companies

0:32:16.640 --> 0:32:19.719
<v Speaker 1>staying in business and being capable of providing that service,

0:32:19.800 --> 0:32:22.640
<v Speaker 1>so it's never a guarantee. So even the stuff that's

0:32:22.680 --> 0:32:28.040
<v Speaker 1>saved in the cloud isn't necessarily permanent. It's probably it's

0:32:28.080 --> 0:32:30.680
<v Speaker 1>probably in better shape than say, something that's saved on

0:32:30.800 --> 0:32:35.120
<v Speaker 1>a magnet are magnetized tape that you keep in your

0:32:35.480 --> 0:32:39.200
<v Speaker 1>your neodyne magnet room. It's going to be better than that,

0:32:40.400 --> 0:32:44.880
<v Speaker 1>but it's not bulletproof. There are several other methods for

0:32:44.920 --> 0:32:47.480
<v Speaker 1>storing information as well, including some that are, you know,

0:32:47.680 --> 0:32:51.240
<v Speaker 1>fairly new. But the point remains our ability to hold

0:32:51.320 --> 0:32:55.600
<v Speaker 1>onto knowledge depends upon the media we use uh and

0:32:55.760 --> 0:32:58.640
<v Speaker 1>the machinery we used to access that media. And if

0:32:58.680 --> 0:33:03.000
<v Speaker 1>we do not consistently information to new storage methods, we

0:33:03.200 --> 0:33:07.880
<v Speaker 1>run the risk of losing the older information. UH. And

0:33:08.480 --> 0:33:10.520
<v Speaker 1>I'll come back to that at the very end, But

0:33:10.720 --> 0:33:14.400
<v Speaker 1>let's switch gears for a second, because sometimes we want

0:33:14.680 --> 0:33:17.840
<v Speaker 1>to get rid of information. Sometimes we need to wipe

0:33:18.160 --> 0:33:20.520
<v Speaker 1>some storage, you know, maybe we need to make room

0:33:20.600 --> 0:33:24.120
<v Speaker 1>for something new. Anyone who's had a gaming PC, you've

0:33:24.160 --> 0:33:26.320
<v Speaker 1>probably at some point said, all right, well, I gotta

0:33:26.600 --> 0:33:28.600
<v Speaker 1>install a couple of these titles so that I can

0:33:28.680 --> 0:33:32.440
<v Speaker 1>install the newest game I want to play. Or maybe

0:33:32.880 --> 0:33:34.440
<v Speaker 1>we want to just get rid of something we no

0:33:34.560 --> 0:33:37.320
<v Speaker 1>longer need or use, or maybe we need to get

0:33:37.440 --> 0:33:39.480
<v Speaker 1>rid of something because we don't want someone else to

0:33:39.560 --> 0:33:42.360
<v Speaker 1>see it. For example, let's say that you've upgraded to

0:33:42.640 --> 0:33:45.800
<v Speaker 1>a brand new computer and you want to sell your

0:33:45.840 --> 0:33:48.200
<v Speaker 1>old computer, or you're gonna donate it to like a

0:33:48.280 --> 0:33:51.400
<v Speaker 1>school or something, or maybe you just want to recycle it. Well,

0:33:51.520 --> 0:33:54.240
<v Speaker 1>chances are before you do that, you're going to want

0:33:54.280 --> 0:33:58.360
<v Speaker 1>to wipe that computer clear of information first. If there's

0:33:58.520 --> 0:34:02.160
<v Speaker 1>anything personal on computer, you probably don't want it falling

0:34:02.200 --> 0:34:05.160
<v Speaker 1>into someone else's hands. Like let's say you get some

0:34:05.240 --> 0:34:09.040
<v Speaker 1>financial or medical information that was stored somewhere on that machine,

0:34:09.520 --> 0:34:12.840
<v Speaker 1>you definitely want to get that wiped off before you

0:34:13.000 --> 0:34:15.920
<v Speaker 1>hand it over to someone else. Well, what happens when

0:34:15.960 --> 0:34:19.520
<v Speaker 1>you delete data, Well, if you're using a computer and

0:34:19.600 --> 0:34:23.240
<v Speaker 1>you're moving files to the recycled bin, that doesn't actually

0:34:23.280 --> 0:34:25.920
<v Speaker 1>mean that the files are gone. Even emptying the recycled

0:34:25.920 --> 0:34:28.880
<v Speaker 1>bin doesn't necessarily mean the files are gone. What it

0:34:29.000 --> 0:34:33.000
<v Speaker 1>means is that the computer has essentially designated the respective

0:34:33.080 --> 0:34:37.479
<v Speaker 1>parts on the storage system holding those files as being

0:34:37.760 --> 0:34:43.040
<v Speaker 1>available for new information. So like the markers that would

0:34:43.080 --> 0:34:45.640
<v Speaker 1>designate that as being a file or gone, but the

0:34:45.719 --> 0:34:48.760
<v Speaker 1>file itself, the information of the file itself is still there.

0:34:49.680 --> 0:34:52.279
<v Speaker 1>But then When it's time for you to save new

0:34:52.360 --> 0:34:55.440
<v Speaker 1>information to your computer, some of that new information might

0:34:55.480 --> 0:34:58.960
<v Speaker 1>be overwritten on top of the older files that you

0:34:59.120 --> 0:35:03.400
<v Speaker 1>quote unquote de eated. So over time you will slowly

0:35:03.480 --> 0:35:07.400
<v Speaker 1>eradicate the information of that deleted file as your computer

0:35:07.600 --> 0:35:12.200
<v Speaker 1>rights new information to those segments. But it's not instantaneous.

0:35:13.160 --> 0:35:15.120
<v Speaker 1>And the important thing to remember is that deleting a

0:35:15.200 --> 0:35:18.799
<v Speaker 1>file doesn't mean the file is gone. It's not enough

0:35:18.920 --> 0:35:23.040
<v Speaker 1>to just delete a file. Many operating systems include options

0:35:23.120 --> 0:35:26.680
<v Speaker 1>to let you permanently delete files, and this option typically

0:35:26.800 --> 0:35:32.920
<v Speaker 1>just involves overwriting the selected deleted files with information, usually

0:35:33.040 --> 0:35:36.319
<v Speaker 1>garbage data that doesn't actually mean anything. The original file

0:35:36.440 --> 0:35:40.120
<v Speaker 1>is gone and it's replaced with gibberish. But let's say

0:35:40.160 --> 0:35:43.160
<v Speaker 1>you have to be absolutely certain that no one will

0:35:43.200 --> 0:35:47.840
<v Speaker 1>ever retrieve information from your hard drive. Maybe this computer

0:35:48.000 --> 0:35:52.319
<v Speaker 1>held crucial financial information for an important company, or maybe

0:35:52.400 --> 0:35:55.000
<v Speaker 1>it held medical information for lots of people, and say

0:35:55.080 --> 0:35:57.960
<v Speaker 1>like a hospital, and it's time for you to downgrade

0:35:58.000 --> 0:36:00.439
<v Speaker 1>the system and get rid of it. Well, you're gonna

0:36:00.560 --> 0:36:03.480
<v Speaker 1>really want to make sure that that machine is wiped clear.

0:36:04.160 --> 0:36:07.320
<v Speaker 1>So then you might want to engage in what I

0:36:07.360 --> 0:36:09.279
<v Speaker 1>would like to think of as the nuclear option. It's

0:36:09.320 --> 0:36:13.040
<v Speaker 1>called the Gutman method, so Peter Gutman and Colin Plum

0:36:13.200 --> 0:36:16.840
<v Speaker 1>came up with this process in the nineties. It involves

0:36:16.960 --> 0:36:23.319
<v Speaker 1>overwriting a disk drive with gibberish thirty five times, using

0:36:23.400 --> 0:36:27.600
<v Speaker 1>different patterns, including some that are not patterns but random passes.

0:36:27.960 --> 0:36:29.920
<v Speaker 1>So there's no pattern at all. It's just a random

0:36:30.000 --> 0:36:33.400
<v Speaker 1>overright pass followed by a whole bunch of patterned overrites

0:36:33.520 --> 0:36:36.840
<v Speaker 1>followed by more random passes. Uh. And this is because

0:36:36.960 --> 0:36:40.320
<v Speaker 1>even with your standard gibberish overwrite, it can still be

0:36:40.440 --> 0:36:43.520
<v Speaker 1>possible for a determined person with the right tools to

0:36:43.640 --> 0:36:47.759
<v Speaker 1>retrieve at least some information off of a hard drive. UM.

0:36:48.160 --> 0:36:51.560
<v Speaker 1>This is because of that magnetic storage. We're talking about

0:36:51.640 --> 0:36:55.040
<v Speaker 1>the hard disk drive era here, so we're really talking

0:36:55.040 --> 0:37:01.480
<v Speaker 1>about looking for faint traces of magnetic imprints that could

0:37:01.520 --> 0:37:04.759
<v Speaker 1>suggest what the original data saved on that hard disk

0:37:04.840 --> 0:37:09.560
<v Speaker 1>drive was. Even by overwriting, those faint traces might remain.

0:37:10.120 --> 0:37:14.920
<v Speaker 1>So this was Gutman's way of just obliterating any trace

0:37:15.040 --> 0:37:18.600
<v Speaker 1>of what was there originally. So you really got to

0:37:18.600 --> 0:37:21.520
<v Speaker 1>go to extremes, or at least you used to, because

0:37:21.560 --> 0:37:25.440
<v Speaker 1>Gutman and Plumb were really concerned about that magnetic issue.

0:37:25.840 --> 0:37:29.000
<v Speaker 1>These days, most experts suggest that the Gutman method is

0:37:29.040 --> 0:37:32.560
<v Speaker 1>really overkill, especially if you're using a solid state drive,

0:37:32.719 --> 0:37:36.640
<v Speaker 1>and that after three passes you're usually in pretty reliable

0:37:36.680 --> 0:37:38.640
<v Speaker 1>shape and you don't have to worry about someone getting

0:37:38.640 --> 0:37:42.400
<v Speaker 1>access to your information. There are also several software packages

0:37:42.440 --> 0:37:44.759
<v Speaker 1>on the market that can go through the process of

0:37:44.840 --> 0:37:48.760
<v Speaker 1>deleting files permanently, usually using some form of multi pass

0:37:49.080 --> 0:37:55.200
<v Speaker 1>overwrite patterns multi pass meaning going over the entire storage drive,

0:37:55.560 --> 0:38:00.719
<v Speaker 1>not like Lulu Dallas multi pass. Sometimes folks go to

0:38:00.920 --> 0:38:04.600
<v Speaker 1>even further extremes, such as using powerful magnets to destroy

0:38:05.200 --> 0:38:09.279
<v Speaker 1>you know, magnetic storage that happens where you know you're

0:38:10.000 --> 0:38:13.279
<v Speaker 1>that will be part of the process. Some will even

0:38:13.480 --> 0:38:17.279
<v Speaker 1>use shredders to destroy like hard disc platters and such,

0:38:17.600 --> 0:38:20.120
<v Speaker 1>so that not only have the files been thoroughly deleted

0:38:20.160 --> 0:38:25.239
<v Speaker 1>and overwritten, but the physical media itself has been physically destroyed.

0:38:26.239 --> 0:38:28.960
<v Speaker 1>That's probably over a kill for most of us, unless

0:38:29.000 --> 0:38:31.239
<v Speaker 1>you go by a three number designation like double oh

0:38:31.360 --> 0:38:34.400
<v Speaker 1>nine or something. But it really is interesting to me

0:38:34.560 --> 0:38:40.960
<v Speaker 1>that information can simultaneously be challenging to preserve and difficult

0:38:41.000 --> 0:38:43.920
<v Speaker 1>to get rid of. But we're also talking about different

0:38:43.960 --> 0:38:47.520
<v Speaker 1>time scales here, right, it's not apples to apples for preservation,

0:38:47.760 --> 0:38:50.600
<v Speaker 1>We're really concerned about the long haul. How can we

0:38:50.760 --> 0:38:54.800
<v Speaker 1>keep information accessible even as the way we generate, store,

0:38:54.920 --> 0:38:59.800
<v Speaker 1>and retrieve information changes. How can we ensure that future

0:39:00.000 --> 0:39:03.080
<v Speaker 1>generations will have access to the information that's at our

0:39:03.120 --> 0:39:08.319
<v Speaker 1>disposal today. There are so many offshoots of this as well.

0:39:08.440 --> 0:39:13.360
<v Speaker 1>For example, the desire to preserve old information is what

0:39:13.560 --> 0:39:17.920
<v Speaker 1>drove the creators of the Multi Arcade Machine Emulator software

0:39:18.080 --> 0:39:20.920
<v Speaker 1>or MAIM to do what they do. They wanted to

0:39:21.000 --> 0:39:24.520
<v Speaker 1>create a way to preserve code that otherwise could fade

0:39:24.560 --> 0:39:29.440
<v Speaker 1>into obscurity because these old arcade machines were physically coded

0:39:29.600 --> 0:39:33.400
<v Speaker 1>onto chips that were part of these arcade cabinets, and

0:39:34.200 --> 0:39:37.440
<v Speaker 1>over time more of those cabinets end up being destroyed

0:39:37.800 --> 0:39:41.560
<v Speaker 1>or they become inoperable, and so this was an attempt

0:39:41.680 --> 0:39:44.279
<v Speaker 1>to create a system that would preserve that code, to

0:39:44.400 --> 0:39:48.239
<v Speaker 1>make it playable, not necessarily for people to play, but

0:39:48.400 --> 0:39:51.760
<v Speaker 1>again to preserve the code itself, otherwise it would be lost.

0:39:52.960 --> 0:39:55.759
<v Speaker 1>And as for destroying information, well that tends to be

0:39:55.920 --> 0:39:59.399
<v Speaker 1>for short term requirements, right, Uh, if there's nothing that's

0:39:59.440 --> 0:40:03.960
<v Speaker 1>threatening us or our information, Well, we could just play

0:40:04.000 --> 0:40:07.760
<v Speaker 1>the waiting game, depending on how we've stored the information

0:40:07.800 --> 0:40:10.800
<v Speaker 1>in the first place, because sooner or later the medium

0:40:11.040 --> 0:40:14.719
<v Speaker 1>that the information is on will deteriorate or it'll go obsolete,

0:40:15.040 --> 0:40:17.240
<v Speaker 1>and no one will be able to get the information anyway,

0:40:17.360 --> 0:40:20.520
<v Speaker 1>including you. So if you don't, if you're not in

0:40:20.600 --> 0:40:23.640
<v Speaker 1>a rush, you could just wait and the information will

0:40:23.680 --> 0:40:28.320
<v Speaker 1>eventually no longer be accessible. Now related to these concepts,

0:40:28.400 --> 0:40:30.879
<v Speaker 1>by the way, is the challenge of figuring out how

0:40:31.000 --> 0:40:35.200
<v Speaker 1>to future proof messaging so that people far into the

0:40:35.280 --> 0:40:39.080
<v Speaker 1>future will understand what those messages mean. Let's think back

0:40:39.120 --> 0:40:42.520
<v Speaker 1>to the Egyptian example. Without the Rosetta stone, we would

0:40:42.520 --> 0:40:44.520
<v Speaker 1>have no way of knowing what the higher glyphs mean.

0:40:44.560 --> 0:40:47.000
<v Speaker 1>Not for sure, we could have a lot of hypotheses,

0:40:48.040 --> 0:40:50.680
<v Speaker 1>but we wouldn't be able to really test them improve

0:40:51.200 --> 0:40:56.000
<v Speaker 1>that our hypothesis is accurate. So let's take an example.

0:40:56.880 --> 0:41:01.880
<v Speaker 1>Let's take the problem of nuclear waste from nuclear power facilities.

0:41:02.400 --> 0:41:06.640
<v Speaker 1>So some nuclear waste remains dangerous for thousands of years,

0:41:07.719 --> 0:41:09.359
<v Speaker 1>and we have to store it. We have to put

0:41:09.400 --> 0:41:11.760
<v Speaker 1>it someplace where it's out of the way and safe.

0:41:12.560 --> 0:41:15.000
<v Speaker 1>And it also means that any warnings that we put

0:41:15.080 --> 0:41:18.640
<v Speaker 1>up at nuclear waste storage facilities really needs to be

0:41:18.760 --> 0:41:22.200
<v Speaker 1>easy for future generations to interpret, even if they have

0:41:22.440 --> 0:41:27.120
<v Speaker 1>lost all other records of what that site is. So

0:41:27.320 --> 0:41:31.640
<v Speaker 1>the signage needs to convey displace is dangerous. But then,

0:41:31.760 --> 0:41:35.439
<v Speaker 1>as that hieroglyphs example showed us, this is easier said

0:41:35.480 --> 0:41:38.000
<v Speaker 1>than done. We might do something that to us seems

0:41:38.080 --> 0:41:42.760
<v Speaker 1>completely obvious, but there's no way of knowing that people

0:41:43.160 --> 0:41:46.960
<v Speaker 1>ten thousand years from now will still understand it. There

0:41:46.960 --> 0:41:50.800
<v Speaker 1>are experts who work hard to create iconography and messaging

0:41:50.880 --> 0:41:54.200
<v Speaker 1>that someone unfamiliar with our current alphabet and language and

0:41:55.000 --> 0:41:59.400
<v Speaker 1>symbols might understand. So for a really awesome treatment of

0:41:59.520 --> 0:42:05.400
<v Speaker 1>this top I highly recommend a classic episode of Invisible,

0:42:05.719 --> 0:42:08.320
<v Speaker 1>a phenomenal show. If you've never listened to it, you

0:42:08.520 --> 0:42:11.279
<v Speaker 1>definitely need to. It is It is one of the

0:42:11.360 --> 0:42:14.640
<v Speaker 1>best podcasts I've ever listened to. But this particular one

0:42:14.719 --> 0:42:16.920
<v Speaker 1>comes from way back when it was like two thousand

0:42:17.000 --> 0:42:21.520
<v Speaker 1>fourteen when it published, and it is titled ten thousand Years.

0:42:22.280 --> 0:42:25.640
<v Speaker 1>Really a great, great episode, You should check that out.

0:42:25.840 --> 0:42:28.719
<v Speaker 1>It's an incredible treatment of the challenge of how do

0:42:28.880 --> 0:42:33.600
<v Speaker 1>you convey information to people that you you there's no

0:42:33.680 --> 0:42:36.239
<v Speaker 1>way for us to know anything about them, and keeping

0:42:36.280 --> 0:42:38.800
<v Speaker 1>in mind, like we're talking ten thousand years, because nuclear

0:42:38.840 --> 0:42:43.000
<v Speaker 1>waste can stay dangerous that long. You go back ten

0:42:43.080 --> 0:42:46.360
<v Speaker 1>thousand years and you suddenly think, wow, Yeah, creating a

0:42:46.440 --> 0:42:49.000
<v Speaker 1>message that would be readable ten tho years from now

0:42:49.200 --> 0:42:53.799
<v Speaker 1>that is going to be super challenging to do so. Yeah.

0:42:54.239 --> 0:42:58.160
<v Speaker 1>Storing data, retrieving data, destroying data, all of these things

0:42:58.560 --> 0:43:02.319
<v Speaker 1>have their own challenges and obstacles in front of them.

0:43:02.640 --> 0:43:05.839
<v Speaker 1>It's important for us to think about because it's also

0:43:05.920 --> 0:43:09.000
<v Speaker 1>important for us to take steps to preserve things when

0:43:09.040 --> 0:43:12.600
<v Speaker 1>we can. Um there are other great examples we can use.

0:43:13.040 --> 0:43:16.680
<v Speaker 1>One I would point out is that a lot of people,

0:43:16.800 --> 0:43:21.160
<v Speaker 1>particularly in my generation, we used stuff like Facebook to

0:43:21.320 --> 0:43:26.560
<v Speaker 1>become kind of the storage center for photographs, right, Like,

0:43:27.800 --> 0:43:31.880
<v Speaker 1>I have hundreds of photos stored on Facebook. But then

0:43:31.960 --> 0:43:34.960
<v Speaker 1>I decided to piece out of Facebook. So I needed

0:43:35.000 --> 0:43:39.000
<v Speaker 1>to download my Facebook information because otherwise I was going

0:43:39.080 --> 0:43:42.800
<v Speaker 1>to lose access to all those pictures that I had stored.

0:43:43.480 --> 0:43:45.319
<v Speaker 1>And it was just a kind of thing I had

0:43:45.360 --> 0:43:48.320
<v Speaker 1>taken for granted that I would always be on Facebook

0:43:48.800 --> 0:43:51.560
<v Speaker 1>and I would always have access to those images, and

0:43:51.840 --> 0:43:55.520
<v Speaker 1>now I don't, And so it's it's it's again. An

0:43:55.600 --> 0:43:57.600
<v Speaker 1>example of things that we have to keep in mind

0:43:57.719 --> 0:44:02.600
<v Speaker 1>when we choose a orange method is that we should

0:44:02.640 --> 0:44:07.120
<v Speaker 1>also occasionally think of ways to my great information to

0:44:07.320 --> 0:44:10.560
<v Speaker 1>a new storage method to make certain that we don't

0:44:10.640 --> 0:44:15.120
<v Speaker 1>lose what came before. All right, I hope you enjoyed

0:44:15.440 --> 0:44:20.600
<v Speaker 1>this episode about the paradoxical nature of information in the

0:44:20.680 --> 0:44:23.680
<v Speaker 1>digital age. If you have suggestions for topics I should

0:44:23.680 --> 0:44:26.520
<v Speaker 1>cover in future episodes of tech Stuff, please reach out

0:44:26.560 --> 0:44:28.880
<v Speaker 1>to me. The best way to do that is on Twitter.

0:44:29.360 --> 0:44:32.239
<v Speaker 1>The handle for the show is tech Stuff H s

0:44:32.440 --> 0:44:42.080
<v Speaker 1>W and I'll talk to you again really soon. Tech

0:44:42.160 --> 0:44:45.560
<v Speaker 1>Stuff is an I Heart Radio production. For more podcasts

0:44:45.640 --> 0:44:48.400
<v Speaker 1>from my Heart Radio, visit the i Heart Radio app,

0:44:48.520 --> 0:44:51.640
<v Speaker 1>Apple Podcasts, or wherever you listen to your favorite shows.