WEBVTT 00:00:00.000 --> 00:00:02.960 Welcome to another deep dive. Today, we're looking 00:00:02.960 --> 00:00:06.719 at something you've probably encountered a hundred 00:00:06.719 --> 00:00:09.199 times. Oh, at least a hundred. Right? You've 00:00:09.199 --> 00:00:11.339 clicked away from it in annoyance, and I guarantee 00:00:11.339 --> 00:00:12.960 you've never actually stopped to read it. No 00:00:12.960 --> 00:00:16.219 one does. No. Because today, we are looking at 00:00:16.219 --> 00:00:19.320 a digital void. Specifically, we're looking at 00:00:19.320 --> 00:00:21.739 the page not found error screen on Wikipedia. 00:00:21.879 --> 00:00:25.399 Yeah. And the exact source material we are examining 00:00:25.399 --> 00:00:28.440 today is the screen that generates when you search 00:00:28.440 --> 00:00:31.280 for the list of NHL award winners. And the database 00:00:31.280 --> 00:00:34.679 just comes up completely empty. Exactly. Nothing 00:00:34.679 --> 00:00:36.439 there. Now, you might be wondering why we're 00:00:36.439 --> 00:00:38.479 dedicating our time to an empty screen. Right. 00:00:38.560 --> 00:00:42.200 Instead of a dense research paper or a new book 00:00:42.200 --> 00:00:44.880 or something. Exactly. But our mission today 00:00:44.880 --> 00:00:47.939 is not to learn a single thing about hockey history. 00:00:48.200 --> 00:00:50.520 Not a single thing. Instead, we're using the 00:00:50.520 --> 00:00:53.539 exact... text, the menus, the fine print of this 00:00:53.539 --> 00:00:56.340 missing page to understand the invisible architecture 00:00:56.340 --> 00:00:58.619 of the internet. It's fascinating because when 00:00:58.619 --> 00:01:02.659 you hit a dead end online, you are actually looking 00:01:02.659 --> 00:01:05.079 at a master class in how digital knowledge is 00:01:05.079 --> 00:01:07.879 constructed. Constructed, curated, maintained, 00:01:08.060 --> 00:01:11.180 all of it. Think of this error page as an x -ray. 00:01:11.519 --> 00:01:14.500 An x -ray. I like that. Yeah, because when a 00:01:14.500 --> 00:01:17.439 digital platform is working perfectly and handing 00:01:17.439 --> 00:01:20.280 you exactly what you asked for, the interface 00:01:20.280 --> 00:01:23.579 completely disappears. You just read the content. 00:01:23.620 --> 00:01:25.700 You don't think about the website itself. Right. 00:01:25.819 --> 00:01:28.359 The only time the underlying scaffolding of a 00:01:28.359 --> 00:01:30.939 website becomes visible to the user is when the 00:01:30.939 --> 00:01:33.260 system breaks. Or when it hits a wall. Exactly. 00:01:33.480 --> 00:01:35.879 So by carefully reading the troubleshooting text 00:01:35.879 --> 00:01:38.379 and the structural menus surrounding this void, 00:01:38.599 --> 00:01:41.120 we get a clear view of the platform's skeleton. 00:01:41.359 --> 00:01:43.200 So let's just start with the central error text 00:01:43.200 --> 00:01:45.879 itself. Okay. The very first thing the page tells 00:01:45.879 --> 00:01:48.879 you, in bold lettering, is Wikipedia does not 00:01:48.879 --> 00:01:51.099 have an article with this exact name. This exact 00:01:51.099 --> 00:01:53.140 name. Notice the phrasing there. It's so specific. 00:01:53.260 --> 00:01:55.939 The system never claims the topic itself doesn't 00:01:55.939 --> 00:01:58.540 exist out in the real world. No. It just states 00:01:58.540 --> 00:02:01.219 that this exact string of characters does not 00:02:01.219 --> 00:02:03.599 match an existing title in its filing cabinet. 00:02:03.980 --> 00:02:06.200 And that distinction really highlights the fundamental 00:02:06.200 --> 00:02:09.060 difference between human communication and database 00:02:09.060 --> 00:02:11.759 architecture. It really does. I mean, if you 00:02:11.759 --> 00:02:14.139 ask a friend about hockey awards, their brain 00:02:14.139 --> 00:02:17.539 uses context. Intuition. Assumption. Right. They 00:02:17.539 --> 00:02:19.580 figure out what you mean, even if you say it 00:02:19.580 --> 00:02:22.240 wrong. Yeah. A database has none of those things. 00:02:22.439 --> 00:02:25.580 It's entirely literal. Completely. If your search 00:02:25.580 --> 00:02:29.379 query is off by a single keystroke, the database 00:02:29.379 --> 00:02:32.229 simply returns a null value. It's a striking 00:02:32.229 --> 00:02:35.590 reminder that we are interacting with cold, rigid 00:02:35.590 --> 00:02:39.509 arrays of stored data. Not an omniscient intelligence 00:02:39.509 --> 00:02:41.889 that just knows what you want. Right. And the 00:02:41.889 --> 00:02:44.590 rigidity of that system leads directly into the 00:02:44.590 --> 00:02:46.949 first troubleshooting tip provided on the page. 00:02:47.090 --> 00:02:49.689 Which is such a funny little detail. It is. The 00:02:49.689 --> 00:02:53.030 text reads, titles on Wikipedia are case sensitive 00:02:53.030 --> 00:02:55.349 except for the first character. Except for the 00:02:55.349 --> 00:02:57.629 first character. Consider the compromise that 00:02:57.629 --> 00:03:00.030 rule represents. It's a very specific exception. 00:03:00.370 --> 00:03:02.210 The architects of the platform know that human 00:03:02.210 --> 00:03:05.090 beings are sloppy typists. We naturally capitalize 00:03:05.090 --> 00:03:07.650 the first letter of a search query. Or our smartphones 00:03:07.650 --> 00:03:09.590 just automatically do it for us. Oh yeah, the 00:03:09.590 --> 00:03:12.710 AutoCap. Right, so the database is intentionally 00:03:12.710 --> 00:03:16.009 programmed with a tiny bit of flexibility to 00:03:16.009 --> 00:03:19.210 forgive that specific human habit. It lets the 00:03:19.210 --> 00:03:22.110 first letter slide. It allows it to pass through 00:03:22.110 --> 00:03:25.560 without strict scrutiny. but after that initial 00:03:25.560 --> 00:03:28.360 character, the machine logic takes over completely. 00:03:28.889 --> 00:03:32.090 Meaning a single errant capital letter in the 00:03:32.090 --> 00:03:34.210 middle of a word will just... It'll hide the 00:03:34.210 --> 00:03:36.150 entire article from you. Just completely block 00:03:36.150 --> 00:03:39.030 it. It is essentially a bridge between human 00:03:39.030 --> 00:03:41.990 fallibility and machine precision. It's a great 00:03:41.990 --> 00:03:43.949 way to put it. Moving down the troubleshooting 00:03:43.949 --> 00:03:46.229 list, there's another technical warning that 00:03:46.229 --> 00:03:48.870 really stands out. Oh, the delay warning. Yes. 00:03:49.110 --> 00:03:52.009 The text advises if a page was recently created 00:03:52.009 --> 00:03:54.250 here, it may not be visible yet because of a 00:03:54.250 --> 00:03:56.830 delay in updating the database. Then it tells 00:03:56.830 --> 00:03:58.919 you to wait a few minutes or... try the purge 00:03:58.919 --> 00:04:01.240 function. Right. Wait a few minutes. That single 00:04:01.240 --> 00:04:03.819 sentence shatters the illusion of the real -time 00:04:03.819 --> 00:04:06.599 internet. We are so heavily conditioned to view 00:04:06.599 --> 00:04:09.259 the digital world as instantaneous. You click 00:04:09.259 --> 00:04:12.219 a button and the result just materializes. But 00:04:12.219 --> 00:04:14.960 this warning explicitly acknowledges a physical 00:04:14.960 --> 00:04:18.769 lag. It reminds you, the user, that the internet 00:04:18.769 --> 00:04:21.250 is actually made of tangible infrastructure. 00:04:21.689 --> 00:04:24.209 Servers are physical machines. They're sitting 00:04:24.209 --> 00:04:26.870 in massive climate -controlled warehouses somewhere. 00:04:27.189 --> 00:04:30.689 Data actually has to be written to drives. Processed, 00:04:30.689 --> 00:04:33.230 propagated across global fiber optic networks. 00:04:33.610 --> 00:04:36.829 It takes time. But the wording here, the purge 00:04:36.829 --> 00:04:39.149 function part, sounds almost aggressive. It does 00:04:39.149 --> 00:04:42.189 sound intense. What exactly is a user purging 00:04:42.189 --> 00:04:44.430 in this context? They're purging the cache. The 00:04:44.430 --> 00:04:47.829 cache. Okay, explain that a bit. So to handle 00:04:47.829 --> 00:04:50.970 millions of visitors a second, massive websites 00:04:50.970 --> 00:04:53.850 don't build a fresh page every single time someone 00:04:53.850 --> 00:04:56.329 clicks a link. That would just melt the servers. 00:04:56.589 --> 00:04:58.329 It would require way too much computing power. 00:04:58.779 --> 00:05:01.120 Instead, they take a snapshot of the page and 00:05:01.120 --> 00:05:03.819 serve that saved copy to everyone. Like a photograph 00:05:03.819 --> 00:05:06.139 of the page. Think of it like a massive bakery. 00:05:06.319 --> 00:05:08.339 They don't bake a new loaf of bread the second 00:05:08.339 --> 00:05:10.379 you order a sandwich. Right. They use the bread 00:05:10.379 --> 00:05:13.079 they baked an hour ago. Exactly. So the system 00:05:13.079 --> 00:05:14.939 is telling you that the hockey article might 00:05:14.939 --> 00:05:17.800 actually exist, but you are looking at an old 00:05:17.800 --> 00:05:20.759 snapshot of the database from before it was written. 00:05:21.279 --> 00:05:24.279 Precisely. Hitting the perch function is the 00:05:24.279 --> 00:05:26.740 digital equivalent of demanding the chef cook 00:05:26.740 --> 00:05:29.240 your meal from scratch. Right in front of you. 00:05:29.279 --> 00:05:32.000 Just throw out the old bread. Yes. It forces 00:05:32.000 --> 00:05:35.100 the server to throw away the save snapshot, query 00:05:35.100 --> 00:05:37.300 the database anew, and show you the absolute 00:05:37.300 --> 00:05:40.519 newest version of reality. Wow. Okay, so that 00:05:40.519 --> 00:05:43.000 covers the technical reasons a page might be 00:05:43.000 --> 00:05:45.519 missing. Physical limitations. Right. But the 00:05:45.519 --> 00:05:47.980 text doesn't just offer technical excuses. It 00:05:47.980 --> 00:05:50.459 actually offers you a job. It invites you to 00:05:50.459 --> 00:05:52.680 fix the problem. It provides instructions on 00:05:52.680 --> 00:05:55.040 how to create the missing NHL page yourself. 00:05:55.949 --> 00:05:58.269 But there is a catch. Pretty significant one. 00:05:58.370 --> 00:06:01.569 The text specifies you need to log in or create 00:06:01.569 --> 00:06:04.149 an account and be autoconfirmed to create new 00:06:04.149 --> 00:06:07.110 articles. Autoconfirmed. It's a very heavy bureaucratic 00:06:07.110 --> 00:06:09.629 term. Autoconfirmed. Honestly, it is the single 00:06:09.629 --> 00:06:11.750 most critical word on the entire page. Really? 00:06:11.829 --> 00:06:14.870 The most critical? Yes. It represents the platform's 00:06:14.870 --> 00:06:16.889 primary defense mechanism. Well, wait. Doesn't 00:06:16.889 --> 00:06:19.350 an autoconfirmer requirement completely contradict 00:06:19.350 --> 00:06:22.089 the famous premise of an encyclopedia that anyone 00:06:22.089 --> 00:06:24.420 can edit? I know it seems contradictory at first 00:06:24.420 --> 00:06:27.259 glance, but it's really a matter of pure scale. 00:06:27.420 --> 00:06:30.220 How so? Well, in the very early days of the Internet, 00:06:30.399 --> 00:06:32.959 platforms were largely frictionless. You could 00:06:32.959 --> 00:06:35.120 walk right in and change things. Just type and 00:06:35.120 --> 00:06:38.439 publish. Right. But digital communities quickly 00:06:38.439 --> 00:06:42.060 learned that a totally open door allows automated 00:06:42.060 --> 00:06:45.699 spam bots and bad actors to completely overwhelm 00:06:45.699 --> 00:06:48.069 the system. It just turns into garbage immediately. 00:06:48.569 --> 00:06:52.089 Exactly. So auto -confirmed is the minimum viable 00:06:52.089 --> 00:06:54.230 friction required to keep the project alive. 00:06:54.629 --> 00:06:57.089 Minimum viable friction. You have to prove you 00:06:57.089 --> 00:06:59.350 are a human. And you have to prove you have a 00:06:59.350 --> 00:07:01.089 basic track record of not destroying things. 00:07:01.509 --> 00:07:03.970 How do you do that? Usually by having an account 00:07:03.970 --> 00:07:06.589 active for a few days and making a handful of 00:07:06.589 --> 00:07:09.300 minor edits first. Okay, so it's an immune system 00:07:09.300 --> 00:07:12.060 response. Very much so. If you don't have that 00:07:12.060 --> 00:07:14.399 trust built up yet, the page actually offers 00:07:14.399 --> 00:07:16.959 alternative paths. It doesn't just shut you out. 00:07:17.100 --> 00:07:20.079 No, it suggests you use the article wizard to 00:07:20.079 --> 00:07:22.699 submit a draft for review or that you request 00:07:22.699 --> 00:07:25.480 a new article. Which is a really revealing look 00:07:25.480 --> 00:07:28.360 at the layered ecosystem of crowdsourcing. Yeah, 00:07:28.420 --> 00:07:30.540 because information isn't simply dumped onto 00:07:30.540 --> 00:07:33.439 a server. Right. If you lack the auto -confirm 00:07:33.439 --> 00:07:36.019 status, your contribution goes into a holding 00:07:36.019 --> 00:07:38.379 pin. The article wizard forces you to format 00:07:38.379 --> 00:07:40.680 your text properly. And then it sits in a queue, 00:07:40.860 --> 00:07:42.699 waiting for a trusted member of the community 00:07:42.699 --> 00:07:45.449 to evaluate it. And requesting an article is 00:07:45.449 --> 00:07:47.529 even more removed. Oh, yeah. You're essentially 00:07:47.529 --> 00:07:50.629 tossing a flare into the digital sky, hoping 00:07:50.629 --> 00:07:52.910 someone with the proper credentials decides your 00:07:52.910 --> 00:07:55.189 topic is worth their time. It really reframes 00:07:55.189 --> 00:07:57.870 the whole concept of crowdsourcing. It goes from 00:07:57.870 --> 00:08:01.170 a chaotic free -for -all into a highly structured 00:08:01.170 --> 00:08:04.170 tiered bureaucracy. It has to be or it wouldn't 00:08:04.170 --> 00:08:06.610 work. And the final troubleshooting step shows 00:08:06.610 --> 00:08:09.709 just how ruthless that bureaucracy can be. The 00:08:09.709 --> 00:08:12.149 deletion log. Yeah. It tells the user if the 00:08:12.149 --> 00:08:14.500 page has been deleted. check the deletion log, 00:08:14.680 --> 00:08:17.319 and see why was the page I created deleted. The 00:08:17.319 --> 00:08:20.199 deletion log is a monumental concept. It sounds 00:08:20.199 --> 00:08:22.800 kind of sad, honestly. Well, we naturally focus 00:08:22.800 --> 00:08:25.420 our attention on the millions of articles that 00:08:25.420 --> 00:08:28.279 successfully exist on the platform. We rarely 00:08:28.279 --> 00:08:30.980 think about the sheer volume of text that is 00:08:30.980 --> 00:08:33.299 actively rejected. The stuff that doesn't make 00:08:33.299 --> 00:08:36.500 the cut. The community utilizes strict notability 00:08:36.500 --> 00:08:39.460 guidelines to determine what deserves a permanent 00:08:39.460 --> 00:08:42.039 record and what doesn't. So what is the deletion 00:08:42.039 --> 00:08:45.000 log exactly? It is essentially a massive digital 00:08:45.000 --> 00:08:48.389 graveyard. a graveyard of vanity projects hyper 00:08:48.389 --> 00:08:51.690 niche interests and spam that simply did not 00:08:51.690 --> 00:08:54.090 meet the editorial threshold so it's an ongoing 00:08:54.090 --> 00:08:57.610 daily curation of human knowledge constant curation 00:08:57.610 --> 00:08:59.929 okay i want to pull our focus away from the text 00:08:59.929 --> 00:09:02.549 of the error itself and look at the structural 00:09:02.549 --> 00:09:04.990 frames surrounding it the margins of the page 00:09:04.990 --> 00:09:08.529 exactly because this empty space is flanked by 00:09:08.529 --> 00:09:11.570 highly detailed appearance and tools menus right 00:09:11.570 --> 00:09:13.990 the interface gives you an incredible amount 00:09:13.990 --> 00:09:16.389 of control over a room with absolutely nothing 00:09:16.389 --> 00:09:18.789 in it. The level of customization is striking. 00:09:18.990 --> 00:09:21.230 What specific settings are available on the source 00:09:21.230 --> 00:09:24.049 page? Well, you can adjust the text sizes to 00:09:24.049 --> 00:09:26.950 small, standard, or large. Okay. You can change 00:09:26.950 --> 00:09:29.809 the width of the page to standard or wide. You 00:09:29.809 --> 00:09:31.710 can toggle the color mode between automatic, 00:09:32.029 --> 00:09:34.690 light, and dark. Standard stuff. But there is 00:09:34.690 --> 00:09:37.629 even a quirky experimental feature listed as 00:09:37.629 --> 00:09:41.110 disabled called birthday mode or baby globe. 00:09:41.330 --> 00:09:44.250 Baby globe mode. I love that. Right. But beyond 00:09:44.250 --> 00:09:46.690 the amusement of a baby globe mode, offering 00:09:46.690 --> 00:09:49.190 all of those settings on an error page demonstrates 00:09:49.190 --> 00:09:52.230 a core principle of modern web architecture. 00:09:52.649 --> 00:09:55.110 The strict separation of content and presentation. 00:09:55.470 --> 00:09:57.429 Expand on that. The database might have failed 00:09:57.429 --> 00:09:59.470 to find the hockey article you wanted, but the 00:09:59.470 --> 00:10:01.970 presentation layer of the website does not care. 00:10:02.110 --> 00:10:04.809 It's totally separate. Its only job is to ensure 00:10:04.809 --> 00:10:07.419 the interface... respects your viewing preferences 00:10:07.419 --> 00:10:10.440 so the system honors your visual needs even when 00:10:10.440 --> 00:10:13.480 it has nothing to show you it is a profound commitment 00:10:13.480 --> 00:10:16.340 to universal design because if you need it you 00:10:16.340 --> 00:10:19.419 need it exactly if a user requires large text 00:10:19.419 --> 00:10:22.279 and a high contrast dark mode to read comfortably 00:10:22.279 --> 00:10:24.740 abandoning those settings just because the user 00:10:24.740 --> 00:10:27.960 hit a 404 error would be incredibly jarring it 00:10:27.960 --> 00:10:30.120 would break the whole experience the platform 00:10:30.120 --> 00:10:32.240 ensures that the environment remains consistent 00:10:32.240 --> 00:10:34.779 and accessible proving that how information is 00:10:34.779 --> 00:10:36.879 delivered is treated with the exact same importance 00:10:36.879 --> 00:10:39.500 as the information itself. That makes a lot of 00:10:39.500 --> 00:10:41.379 sense. And that architectural consistency extends 00:10:41.379 --> 00:10:43.860 to the Tools menu as well. What's in the Tools 00:10:43.860 --> 00:10:46.419 menu? Well, this completely empty page allows 00:10:46.419 --> 00:10:49.960 you to get shortened URL, download QR code, and 00:10:49.960 --> 00:10:52.200 generate a printable version. A printable version 00:10:52.200 --> 00:10:54.799 of an error page. Right. At first glance, the 00:10:54.799 --> 00:10:57.120 idea of downloading a QR code that leads to a 00:10:57.120 --> 00:11:00.200 page not found error seems totally absurd. Why 00:11:00.200 --> 00:11:03.059 would anyone want to print a void? It seems crazy, 00:11:03.159 --> 00:11:05.919 but it makes perfect sense when you realize that 00:11:05.919 --> 00:11:08.879 the Internet treats URLs as geographic coordinates. 00:11:09.019 --> 00:11:11.620 Geographic coordinates. Yeah. Latitude and longitude 00:11:11.620 --> 00:11:13.700 exist perfectly well in the middle of the empty 00:11:13.700 --> 00:11:16.440 ocean. Oh, wow. Okay. The specific web address 00:11:16.440 --> 00:11:19.399 for the list of NHL award winners is a distinct 00:11:19.399 --> 00:11:22.500 digital location, regardless of whether a structural 00:11:22.500 --> 00:11:25.480 article currently occupies that lot. So a user 00:11:25.480 --> 00:11:27.480 might actually need to point someone to that 00:11:27.480 --> 00:11:30.779 exact empty lot. Exactly. In academic research, 00:11:31.039 --> 00:11:33.440 journalism or system administration, proving 00:11:33.440 --> 00:11:35.679 a negative is often necessary. You have to prove 00:11:35.679 --> 00:11:38.080 it's not there. Right. You might need to link 00:11:38.080 --> 00:11:40.700 to the empty page to demonstrate to a colleague 00:11:40.700 --> 00:11:43.419 that a specific data set has not been compiled 00:11:43.419 --> 00:11:45.860 yet. Or you might print it to document that an 00:11:45.860 --> 00:11:48.460 article was definitively removed by a certain 00:11:48.460 --> 00:11:51.759 date. Exactly. The utility tools are blind to 00:11:51.759 --> 00:11:54.139 the content. They exist solely to manipulate 00:11:54.139 --> 00:11:56.419 the coordinate. So we have this highly structured, 00:11:56.639 --> 00:11:59.899 customizable, empty room. And the page makes 00:11:59.899 --> 00:12:02.220 it clear that this room is just one small part 00:12:02.220 --> 00:12:04.659 of a sprawling complex. The sister projects. 00:12:04.860 --> 00:12:07.659 Yes. The text prompts you to search for your 00:12:07.659 --> 00:12:10.100 hockey topic on Wikipedia's sister projects. 00:12:10.399 --> 00:12:13.440 And it provides a massive list. It's a huge list. 00:12:13.720 --> 00:12:16.539 Wiktionary, Wikibooks, Wikiquote, Wikisource, 00:12:16.720 --> 00:12:19.840 Wikiversity, Commons, Wikivoyage, Wikinews, Wikidata, 00:12:19.980 --> 00:12:22.580 and Wikispecies. That list represents a really 00:12:22.580 --> 00:12:25.360 compelling exercise in epistemology. Epistemology. 00:12:25.500 --> 00:12:28.399 The study of knowledge. Yes. The study of knowledge 00:12:28.399 --> 00:12:31.019 and how we classify it. We tend to use the word 00:12:31.019 --> 00:12:33.690 information as a catch -all term for... everything 00:12:33.690 --> 00:12:35.190 on the internet. Sure, it's all just information. 00:12:35.529 --> 00:12:38.269 But this platform forces the user to categorize 00:12:38.269 --> 00:12:41.850 reality into highly specialized buckets. So how 00:12:41.850 --> 00:12:44.070 does that categorization play out for someone 00:12:44.070 --> 00:12:46.730 who is just looking for a hockey list? Well, 00:12:46.789 --> 00:12:50.169 if the information you possess doesn't fit the 00:12:50.169 --> 00:12:52.370 strict prose requirements of an encyclopedia 00:12:52.370 --> 00:12:55.600 article, It doesn't mean the information is useless. 00:12:55.860 --> 00:12:58.240 It just means it belongs somewhere else. It belongs 00:12:58.240 --> 00:13:00.440 in a different structure. If you only have raw, 00:13:00.539 --> 00:13:02.899 unformatted statistics about the hockey awards, 00:13:03.159 --> 00:13:06.240 that belongs in Wikidata. Ah, okay. If you have 00:13:06.240 --> 00:13:09.200 a scanned copy of the original 1920s NHL charter, 00:13:09.419 --> 00:13:12.379 that belongs in Wikisource. So they're all different 00:13:12.379 --> 00:13:14.500 types of knowledge. The platform is essentially 00:13:14.500 --> 00:13:17.759 telling the user, your data has value, but you 00:13:17.759 --> 00:13:19.440 are knocking on the wrong door of the library. 00:13:19.740 --> 00:13:22.200 That's a great analogy. It forces the contributor 00:13:22.200 --> 00:13:24.080 to understand the difference between raw data, 00:13:24.240 --> 00:13:27.519 historical source material, and synthesized knowledge. 00:13:27.740 --> 00:13:30.100 It's a brilliant way to organize human output. 00:13:30.419 --> 00:13:32.460 It really is. And speaking of the humans involved, 00:13:32.720 --> 00:13:35.539 if we scroll down to the absolute bottom of our 00:13:35.539 --> 00:13:38.000 source page, we hit the true foundation of this 00:13:38.000 --> 00:13:40.919 entire enterprise. The footer. The footer. The 00:13:40.919 --> 00:13:44.220 very bottom of the page links to legal and safety 00:13:44.220 --> 00:13:47.690 contacts and a code of conduct. Which brings 00:13:47.690 --> 00:13:50.289 us back to the reality that a digital ecosystem 00:13:50.289 --> 00:13:54.610 is, at its core, a human project. It's all just 00:13:54.610 --> 00:13:56.590 people at the end of the day. You can engineer 00:13:56.590 --> 00:13:59.190 the most elegant database rules and cash purging 00:13:59.190 --> 00:14:01.570 systems in the world, but eventually you have 00:14:01.570 --> 00:14:03.870 to manage human behavior. The technology is easy. 00:14:03.990 --> 00:14:06.909 The people are hard. Very hard. You need a code 00:14:06.909 --> 00:14:09.169 of conduct because thousands of anonymous editors 00:14:09.169 --> 00:14:11.990 will inevitably argue over syntax and facts. 00:14:12.210 --> 00:14:14.549 They will fight over commas. And you need legal 00:14:14.549 --> 00:14:17.539 and safety contacts. Because actions taken in 00:14:17.539 --> 00:14:19.700 the digital realm have real -world consequences 00:14:19.700 --> 00:14:22.480 that require oversight. And perhaps most importantly, 00:14:22.659 --> 00:14:24.840 you need a way to keep these servers powered 00:14:24.840 --> 00:14:27.139 on. Which is reflected right at the top of the 00:14:27.139 --> 00:14:30.600 page, baked into the personal tools menu. The 00:14:30.600 --> 00:14:33.139 donation prompt. Yep. There's a prominent prompt 00:14:33.139 --> 00:14:35.360 to donate. Along with the message, donors like 00:14:35.360 --> 00:14:38.159 you keep Wikipedia thriving. And a link to learn 00:14:38.159 --> 00:14:40.799 about legacy giving. That financial plea really 00:14:40.799 --> 00:14:43.399 synthesizes our entire deep dive today. How so? 00:14:43.850 --> 00:14:46.769 Because behind the strict auto -confirmed hierarchies, 00:14:46.809 --> 00:14:49.970 the machine logic arrays, and the vast network 00:14:49.970 --> 00:14:52.789 of sister projects, there is a harsh economic 00:14:52.789 --> 00:14:55.909 reality. It costs money. This massive utopian 00:14:55.909 --> 00:14:59.230 project of cataloging human knowledge does not 00:14:59.230 --> 00:15:01.970 exist in a vacuum. It requires immense resources. 00:15:02.409 --> 00:15:05.210 It relies on community rules to manage human 00:15:05.210 --> 00:15:07.570 nature. And it relies on financial donations 00:15:07.570 --> 00:15:09.990 to literally pay for the electricity and the 00:15:09.990 --> 00:15:12.409 warehouse space for those physical servers we 00:15:12.409 --> 00:15:14.250 talked about earlier. The infrastructure of free 00:15:14.250 --> 00:15:16.429 knowledge is incredibly expensive to maintain 00:15:16.429 --> 00:15:19.289 Extremely expensive We started today looking 00:15:19.289 --> 00:15:21.529 for a simple list of hockey awards and hit a 00:15:21.529 --> 00:15:24.409 dead end But by analyzing the exact text and 00:15:24.409 --> 00:15:27.049 structure of that dead end, we uncovered the 00:15:27.049 --> 00:15:29.049 hidden mechanics of the Internet. We saw how 00:15:29.049 --> 00:15:31.429 databases interact with human typing. How digital 00:15:31.429 --> 00:15:34.850 platforms scale trust through friction. How presentation 00:15:34.850 --> 00:15:37.269 is completely separated from content. And how 00:15:37.269 --> 00:15:40.409 raw data is categorized into distinct epistemological 00:15:40.409 --> 00:15:43.230 buckets. It is a powerful reminder for you, the 00:15:43.230 --> 00:15:45.970 listener. The next time you hit an error page, 00:15:46.190 --> 00:15:49.070 a 404 screen, or a missing link anywhere on the 00:15:49.070 --> 00:15:51.779 Internet, Do not just immediately click away. 00:15:51.960 --> 00:15:54.240 Take a breath. Take a breath and look at the 00:15:54.240 --> 00:15:56.759 scaffolding around the air. Look at the menus, 00:15:56.840 --> 00:15:59.460 the troubleshooting text, and the footers. Because 00:15:59.460 --> 00:16:03.100 that supposedly empty page will tell you exactly 00:16:03.100 --> 00:16:05.320 how the platform functions. How it organizes 00:16:05.320 --> 00:16:08.480 reality and how it views you as a user. The void 00:16:08.480 --> 00:16:11.259 is never truly empty. It is just waiting to be 00:16:11.259 --> 00:16:14.179 read. Now, to wrap up today's deep dive, we want 00:16:14.179 --> 00:16:16.980 to leave you with one final lingering thought 00:16:16.980 --> 00:16:19.480 to ponder on your own. Something to mull over. 00:16:20.090 --> 00:16:22.210 We've spent this time analyzing the specific 00:16:22.210 --> 00:16:24.870 architecture of a missing page and the friction 00:16:24.870 --> 00:16:27.570 required to create new information. But consider 00:16:27.570 --> 00:16:29.909 the current trajectory of technology. The rapid 00:16:29.909 --> 00:16:32.190 rise of generative artificial intelligence. Right. 00:16:32.509 --> 00:16:35.210 Generative AI models don't generally return page 00:16:35.210 --> 00:16:37.169 not found errors. Yeah, they don't like dead 00:16:37.169 --> 00:16:40.049 ends. If you ask an AI for a list of hockey awards 00:16:40.049 --> 00:16:42.629 that doesn't exist in its training data, it doesn't 00:16:42.629 --> 00:16:44.570 show you the structural scaffolding. It often 00:16:44.570 --> 00:16:47.440 just synthesizes an answer on the fly. Or hallucinates 00:16:47.440 --> 00:16:50.659 a response just to fulfill your prompt. It smooths 00:16:50.659 --> 00:16:53.120 over the void entirely. So the question to mull 00:16:53.120 --> 00:16:56.019 over is this. As the internet transitions from 00:16:56.019 --> 00:16:59.220 rigid databases to generative AI, will the missing 00:16:59.220 --> 00:17:01.759 page error eventually go completely extinct? 00:17:02.120 --> 00:17:04.380 That's a wild thought. And if future generations 00:17:04.380 --> 00:17:06.900 never experience the friction of hitting a digital 00:17:06.900 --> 00:17:09.720 dead end, what happens to our collective curiosity 00:17:09.720 --> 00:17:12.200 when we can no longer clearly see the boundaries 00:17:12.200 --> 00:17:14.700 of recorded human knowledge? Something to think 00:17:14.700 --> 00:17:16.480 about the next time you ask a machine for an 00:17:16.480 --> 00:17:18.980 answer. Definitely. Thanks for joining us for 00:17:18.980 --> 00:17:21.119 this deep dive. We will catch you next time.