WEBVTT 00:00:00.000 --> 00:00:04.719 So imagine walking into the world's largest library, 00:00:05.059 --> 00:00:08.039 right? You go up to the front desk and you ask 00:00:08.039 --> 00:00:12.820 for a very specific, maybe slightly obscure book. 00:00:12.980 --> 00:00:16.519 OK, I'm picturing it. Let's say you want a comprehensive 00:00:16.519 --> 00:00:20.100 history of a comedy musician's discography. Like 00:00:20.100 --> 00:00:22.199 Weird Al or something. Yeah, exactly. Let's say 00:00:22.199 --> 00:00:25.120 Weird Al. And instead of the librarian just saying, 00:00:25.120 --> 00:00:28.010 you know, Sorry, we don't have that. They hand 00:00:28.010 --> 00:00:31.129 you a set of binding glue, a stack of blank paper, 00:00:31.370 --> 00:00:34.509 and a diagnostic manual. Oh, wow. And they essentially 00:00:34.509 --> 00:00:36.590 just tell you to write the book yourself. But, 00:00:36.909 --> 00:00:39.270 and here's the catch, you can only start writing 00:00:39.270 --> 00:00:41.530 if you pass the secret invisible background check 00:00:41.530 --> 00:00:44.030 first. Which completely flips the dynamic of 00:00:44.030 --> 00:00:46.270 how we usually interact with information online. 00:00:46.609 --> 00:00:48.609 I mean, we are so used to the internet being 00:00:48.609 --> 00:00:50.530 this seamless vending machine. Right, exactly. 00:00:50.670 --> 00:00:52.909 You press a button, the coil turns, and your 00:00:52.909 --> 00:00:55.119 snack just drops down. And when it doesn't, You 00:00:55.119 --> 00:00:56.679 know, we usually just walk away. Yeah, you hit 00:00:56.679 --> 00:00:59.380 that page not found screen, that digital dead 00:00:59.380 --> 00:01:01.479 end, and your immediate instinct is just to close 00:01:01.479 --> 00:01:03.399 the tab. Yep, just move on to the next search. 00:01:03.700 --> 00:01:05.680 But we are actually not going to do that today. 00:01:05.920 --> 00:01:08.620 Welcome to today's deep dive. Our mission today 00:01:08.620 --> 00:01:11.560 is highly unusual because our source material 00:01:11.560 --> 00:01:15.280 is just a single web page. Just one page. Just 00:01:15.280 --> 00:01:17.859 one. And ironically, it is a page that technically 00:01:17.859 --> 00:01:20.219 does not even exist. Which is such a brilliant 00:01:20.219 --> 00:01:22.000 contradiction to start with, really. I mean, 00:01:22.000 --> 00:01:24.400 we are literally analyzing the architecture of 00:01:24.400 --> 00:01:27.519 a void. Right. So specifically, we have the Wikipedia 00:01:27.519 --> 00:01:29.900 search result and the error page for Weird Al 00:01:29.900 --> 00:01:32.980 Yankovitch's greatest hits. And just to be perfectly 00:01:32.980 --> 00:01:34.819 clear right out of the gate for everyone listening, 00:01:35.239 --> 00:01:37.480 The goal of this deep dive isn't to actually 00:01:37.480 --> 00:01:40.579 talk about Weird Al. No, definitely not. Or his 00:01:40.579 --> 00:01:45.180 music. We aren't analyzing accordion solos today. 00:01:45.420 --> 00:01:47.260 Though that would be a fun deep dive. But no, 00:01:47.359 --> 00:01:49.620 we are using this specific missing page as a 00:01:49.620 --> 00:01:52.180 sort of magnifying glass. Exactly. We're going 00:01:52.180 --> 00:01:54.700 to analyze this digital blank space to try and 00:01:54.700 --> 00:01:57.019 understand the hidden mechanics, the really strict 00:01:57.019 --> 00:02:00.120 rules, and the sheer architectural scale of the 00:02:00.120 --> 00:02:02.719 world's largest crowd -sourced encyclopedia. 00:02:02.920 --> 00:02:06.400 Because you, listening right now, have absolutely 00:02:06.400 --> 00:02:09.919 hit a Wikipedia does not have an article with 00:02:09.919 --> 00:02:12.659 this exact name page before. I mean, it happens 00:02:12.659 --> 00:02:15.780 to all of us. Oh, constantly. But you've probably 00:02:15.780 --> 00:02:17.860 never actually stopped to read the fine print 00:02:17.860 --> 00:02:21.000 on that screen. So, OK, let's unpack this. Do 00:02:21.000 --> 00:02:23.719 it. Because right off the bat, Wikipedia gives 00:02:23.719 --> 00:02:26.939 you this big, bold message stating the article 00:02:26.939 --> 00:02:29.439 just isn't there. But instead of leaving you 00:02:29.439 --> 00:02:32.539 hanging, it immediately pivots into this massive 00:02:32.539 --> 00:02:35.460 diagnostic toolkit. It's giving you the exact 00:02:35.460 --> 00:02:37.560 reasons why you might be staring at a blank page. 00:02:37.740 --> 00:02:40.240 Yeah. What's fascinating here is that the platform 00:02:40.240 --> 00:02:43.300 exposes its own backend infrastructure directly 00:02:43.300 --> 00:02:45.939 to the everyday reader. I mean, most tech companies 00:02:45.939 --> 00:02:47.939 completely hide their errors. Right, if Twitter 00:02:47.939 --> 00:02:50.000 breaks, you get a cute graphic of a fail whale 00:02:50.000 --> 00:02:52.460 or something. Exactly. Or if a website is down, 00:02:52.599 --> 00:02:55.379 you get, like, a funny cartoon dog holding an 00:02:55.379 --> 00:02:57.500 unplugged cord. But Wikipedia doesn't do that 00:02:57.500 --> 00:03:00.900 at all. They treat you, the casual reader, as 00:03:00.900 --> 00:03:04.300 a potential system administrator. Yes. And the 00:03:04.300 --> 00:03:06.680 first bullet point they offer really caught my 00:03:06.680 --> 00:03:10.139 eye because it suggests that the page might have 00:03:10.139 --> 00:03:12.719 actually been created recently, but it's just 00:03:12.719 --> 00:03:16.409 not visible yet because of a, quote, delay in 00:03:16.409 --> 00:03:19.150 updating the database. I have the database delay. 00:03:19.330 --> 00:03:21.650 It literally tells you to wait a few minutes 00:03:21.650 --> 00:03:24.490 or try something called the purge function. Now 00:03:24.490 --> 00:03:27.229 I have to be honest here, try the purge function 00:03:27.229 --> 00:03:29.729 sounds highly technical. It does sound a bit 00:03:29.729 --> 00:03:31.770 intense. It sounds like a command you yell in 00:03:31.770 --> 00:03:34.250 a sci -fi movie to vent the work core or something. 00:03:34.710 --> 00:03:36.610 Why are they telling a regular person looking 00:03:36.610 --> 00:03:39.129 up a comedy album to purge the system? I mean, 00:03:39.129 --> 00:03:41.189 it does sound intimidating, but it is actually 00:03:41.189 --> 00:03:43.870 this beautiful peek behind the curtain of how 00:03:43.870 --> 00:03:47.969 the modern Okay, how so? Well, it shatters the 00:03:47.969 --> 00:03:51.449 illusion that Wikipedia is just this magic instant 00:03:51.449 --> 00:03:54.770 ether. It reminds you that it is a physical database 00:03:54.770 --> 00:03:57.930 residing on massive servers globally. And to 00:03:57.930 --> 00:04:00.490 survive the billions of hits it gets every single 00:04:00.490 --> 00:04:04.129 day, Wikipedia relies heavily on caching. Caching. 00:04:04.289 --> 00:04:05.889 Okay, break that down for us in this context. 00:04:06.009 --> 00:04:08.270 Sure. So, think of a massive restaurant kitchen 00:04:08.270 --> 00:04:10.370 during the dinner rush. If a thousand people 00:04:10.370 --> 00:04:13.569 are all ordering the exact same soup, The chef 00:04:13.569 --> 00:04:16.610 isn't going to cook a thousand individual tiny 00:04:16.610 --> 00:04:18.829 pots of soup from scratch every single time an 00:04:18.829 --> 00:04:20.449 order comes in. Right, that would be totally 00:04:20.449 --> 00:04:23.230 inefficient. Exactly. They make a massive batch, 00:04:23.410 --> 00:04:25.689 keep it warm, and just ladle it out instantly. 00:04:26.009 --> 00:04:28.509 That is a cache. Oh, I see. The server takes 00:04:28.509 --> 00:04:31.310 a snapshot of a highly trafficked page and just 00:04:31.310 --> 00:04:33.629 hands out that saved copy because it's computationally 00:04:33.629 --> 00:04:36.610 cheap and incredibly fast. Okay, so the system 00:04:36.610 --> 00:04:39.230 is essentially saying we might actually have 00:04:39.230 --> 00:04:41.449 the soup, but the waiter is holding an outdated 00:04:41.449 --> 00:04:43.829 menu. That's a great way to put it, yes. And 00:04:43.829 --> 00:04:47.490 so what exactly is the purge function doing then? 00:04:47.790 --> 00:04:50.149 To take your library analogy from earlier a step 00:04:50.149 --> 00:04:52.709 further. Oh please do. The purge function is 00:04:52.709 --> 00:04:55.050 like forcing the librarian to get out of their 00:04:55.050 --> 00:04:57.470 chair, walk all the way down to the basement 00:04:57.470 --> 00:05:00.129 archives, and physically check the actual shelf. 00:05:00.310 --> 00:05:02.550 Just to see if the book was dropped off like 00:05:02.550 --> 00:05:05.230 five minutes ago. Exactly. Rather than just glancing 00:05:05.230 --> 00:05:07.600 at the outdated card catalog on their desk. It 00:05:07.600 --> 00:05:11.060 is a manual override. It forces the server to 00:05:11.060 --> 00:05:14.240 completely bypass the saved snapshot and build 00:05:14.240 --> 00:05:17.480 a fresh version of the page from the raw underlying 00:05:17.480 --> 00:05:20.579 database. They are literally giving you the button 00:05:20.579 --> 00:05:22.819 to kick the vending machine. That is incredible. 00:05:22.899 --> 00:05:24.899 They just hand you the keys to kick the machine 00:05:24.899 --> 00:05:27.300 and then right below that it gets even more granular. 00:05:27.459 --> 00:05:30.180 It really does. The next diagnostic step warns 00:05:30.180 --> 00:05:33.920 you that titles on Wikipedia are case sensitive 00:05:33.920 --> 00:05:36.699 except for the first character. So it prompts 00:05:36.699 --> 00:05:39.660 you to check your capitalizations. The case sensitivity 00:05:39.660 --> 00:05:42.379 warning, right? Like if I capitalized weird but 00:05:42.379 --> 00:05:45.160 accidentally left greatest with a lowercase g. 00:05:45.449 --> 00:05:47.730 The system treats that as a complete failure. 00:05:47.790 --> 00:05:50.310 It just breaks. Which perfectly illustrates the 00:05:50.310 --> 00:05:53.329 friction between human language and machine logic. 00:05:53.529 --> 00:05:55.769 What do you mean by that? Well, as humans, we 00:05:55.769 --> 00:05:58.449 read semantics, right? Yeah. We look at a lowercase 00:05:58.449 --> 00:06:01.629 G and a capital G, and our brains automatically 00:06:01.629 --> 00:06:04.709 group them as the exact same underlying concept. 00:06:04.889 --> 00:06:07.149 Right. It's just a G. It means the same thing. 00:06:07.329 --> 00:06:10.089 But to a computer database at its most fundamental 00:06:10.089 --> 00:06:12.629 level, those are completely different entities. 00:06:12.790 --> 00:06:14.829 Because it's just reading the raw code behind 00:06:14.829 --> 00:06:18.060 the letter. Exactly. In the AXI standard, which 00:06:18.060 --> 00:06:20.339 is the numerical code computers use to represent 00:06:20.339 --> 00:06:25.120 text, a capital G is the number 71. Okay. A lowercase 00:06:25.120 --> 00:06:28.540 g is the number 103. Wait, really? They're that 00:06:28.540 --> 00:06:31.959 far apart? Yep. So to a database searching for 00:06:31.959 --> 00:06:35.279 a string of text, asking for 71 when the file's 00:06:35.279 --> 00:06:38.560 name 103 is just as wrong as asking for the number 00:06:38.560 --> 00:06:42.509 900. Wow. So by warning you about case sensitivity, 00:06:43.009 --> 00:06:45.290 Wikipedia is basically teaching the user how 00:06:45.290 --> 00:06:48.649 strict a database query actually is. Yes. The 00:06:48.649 --> 00:06:50.709 system is forgiving enough on the very first 00:06:50.709 --> 00:06:53.230 letter of an article. Mostly just to be helpful, 00:06:53.610 --> 00:06:55.529 but after that you have to speak the machine's 00:06:55.529 --> 00:06:57.990 exact dialect. It's so painfully literal. But 00:06:57.990 --> 00:06:59.589 then we get to the third reason the page might 00:06:59.589 --> 00:07:02.149 be missing, which is honestly my absolute favorite 00:07:02.149 --> 00:07:03.870 part of this whole page. Oh, I know what you're 00:07:03.870 --> 00:07:05.610 going with this. It says, if the page has been 00:07:05.610 --> 00:07:08.269 deleted, check the deletion log and see why was 00:07:08.269 --> 00:07:11.870 the page I created deleted? Ah, yes. The infamous 00:07:11.870 --> 00:07:14.089 deletion log. They actually link you to a guide 00:07:14.089 --> 00:07:16.509 explaining why they might have actively destroyed 00:07:16.509 --> 00:07:18.449 the very thing you're looking for. It's quite 00:07:18.449 --> 00:07:20.740 blunt. It's like the librarian saying, yeah, 00:07:20.800 --> 00:07:23.459 we had that book, but the library committee decided 00:07:23.459 --> 00:07:26.120 it wasn't worthy so we shredded it. They give 00:07:26.120 --> 00:07:28.800 you the literal autopsy report of your search 00:07:28.800 --> 00:07:32.290 query. And again, it's about this radical transparency. 00:07:32.490 --> 00:07:35.009 You came looking for a musician's compilation 00:07:35.009 --> 00:07:37.829 album, and you leave with a basic understanding 00:07:37.829 --> 00:07:41.709 of server caching, ASCII case sensitivity, and 00:07:41.709 --> 00:07:44.170 administrative deletion policies. It's wild. 00:07:44.850 --> 00:07:47.670 So let's say we've run the diagnostics, we've 00:07:47.670 --> 00:07:50.149 purged the cache, we've triple -checked our capital 00:07:50.149 --> 00:07:52.709 letters, and we check the deletion log. The machine 00:07:52.709 --> 00:07:54.759 is working fine. Right. The machine is fine. 00:07:55.000 --> 00:07:57.759 The information just truly isn't there. The natural 00:07:57.759 --> 00:07:59.980 thought is, well, I'll just make the page myself. 00:08:00.319 --> 00:08:01.860 Because that's the whole premise of the site. 00:08:02.120 --> 00:08:04.680 Exactly. But when you actually read the instructions 00:08:04.680 --> 00:08:07.240 on how to do that, it is not what you expect 00:08:07.240 --> 00:08:10.000 at all. Right. The transition from passive reader 00:08:10.000 --> 00:08:12.500 to active creator is a big leap. It is. And I 00:08:12.500 --> 00:08:14.480 have to push back here on something. Yeah. Because 00:08:14.480 --> 00:08:17.199 the entire cultural brand of Wikipedia, their 00:08:17.199 --> 00:08:20.339 actual slogan is, the free encyclopedia that 00:08:20.339 --> 00:08:22.920 anyone can edit. Right. Anyone can edit. But 00:08:22.920 --> 00:08:25.399 this error page proves that is a bit of a myth. 00:08:26.019 --> 00:08:29.019 To create a new article for Weird Al Yankovitch's 00:08:29.019 --> 00:08:32.100 Greatest Hits, the text clearly states you cannot 00:08:32.100 --> 00:08:35.519 just start typing. First, you have to log in. 00:08:35.820 --> 00:08:38.820 Which makes sense. Sure. But then, and this is 00:08:38.820 --> 00:08:40.399 the word that really stopped me in my tracks, 00:08:40.519 --> 00:08:43.470 you must be Auto -confirmed. Auto -confirmed 00:08:43.470 --> 00:08:46.909 is a highly specific, very bureaucratic term. 00:08:47.049 --> 00:08:49.450 It sounds like a digital caste system. I mean, 00:08:49.590 --> 00:08:52.590 doesn't this auto -confirmation barrier completely 00:08:52.590 --> 00:08:54.990 contradict their core mission statement? It does 00:08:54.990 --> 00:08:56.850 feel like a bit of a contradiction, yes. It feels 00:08:56.850 --> 00:08:59.269 like a bait and switch. You can't just show up 00:08:59.269 --> 00:09:01.970 and contribute to human knowledge. You have to 00:09:01.970 --> 00:09:05.090 pass this invisible probationary period to achieve 00:09:05.090 --> 00:09:07.210 this special status. Well, this raises an important 00:09:07.210 --> 00:09:09.450 question about how open platforms survive at 00:09:09.450 --> 00:09:12.750 scale. The balance between, you know, utopian 00:09:12.750 --> 00:09:16.190 open source ideation and strict, ruthless quality 00:09:16.190 --> 00:09:19.409 control is basically the central tension of Wikipedia's 00:09:19.409 --> 00:09:21.669 entire existence. Okay, so it wasn't always like 00:09:21.669 --> 00:09:24.210 this. No. In the early days, it was much more 00:09:24.210 --> 00:09:27.009 of a free -for -all. But if you allow anonymous, 00:09:27.409 --> 00:09:30.090 brand -new users to mint new pages instantly 00:09:30.090 --> 00:09:33.009 today, the site would be crushed within hours. 00:09:33.250 --> 00:09:38.049 Crushed by what? Like traffic? By spambots. Vandalism. 00:09:38.200 --> 00:09:40.720 corporate marketing teams trying to make pages 00:09:40.720 --> 00:09:43.580 for their new brand of sneakers, political operatives 00:09:43.580 --> 00:09:46.259 trying to spin narratives. Oh, right. Humans 00:09:46.259 --> 00:09:49.720 ruin everything? Pretty much. The auto -confirmed 00:09:49.720 --> 00:09:52.200 requirement, which generally means an account 00:09:52.200 --> 00:09:53.919 has to be at least four days old and have made 00:09:53.919 --> 00:09:57.159 a minimum of 10 edits to existing pages, is a 00:09:57.159 --> 00:09:59.500 vital self -defense mechanism. So it's essentially 00:09:59.500 --> 00:10:02.399 a test of human latency. Exactly. You have to 00:10:02.399 --> 00:10:04.940 prove you can exist in the ecosystem responsibly 00:10:04.940 --> 00:10:07.899 over a period of time before you are handed the 00:10:07.899 --> 00:10:10.460 keys to the heavy machinery of creating brand 00:10:10.460 --> 00:10:12.519 new topics. Okay, that makes sense. It's proof 00:10:12.519 --> 00:10:14.919 of good faith. Yes. But looking closer at this 00:10:14.919 --> 00:10:17.059 page, if you scroll past that initial rejection, 00:10:17.440 --> 00:10:19.879 there's this weird backdoor option. The text 00:10:19.879 --> 00:10:22.460 says, alternatively, you can use the Article 00:10:22.460 --> 00:10:25.220 Wizard to submit a draft for review or request 00:10:25.220 --> 00:10:27.789 a new article. The Article Wizard. What exactly 00:10:27.789 --> 00:10:29.909 is an article wizard? It sounds like a character 00:10:29.909 --> 00:10:32.590 in a video game. The article wizard is essentially 00:10:32.590 --> 00:10:36.049 a digital chaperone. It's a guided process for 00:10:36.049 --> 00:10:38.509 users who haven't earned their stripes yet. So 00:10:38.509 --> 00:10:41.690 it's like getting a learner's permit for knowledge 00:10:41.690 --> 00:10:43.750 creation. That's a perfect way to describe it. 00:10:43.889 --> 00:10:46.190 You can't publish directly to the live site. 00:10:46.230 --> 00:10:48.610 You have to submit a draft, and then someone 00:10:48.610 --> 00:10:51.490 else, someone higher up in that hierarchy, has 00:10:51.490 --> 00:10:54.350 to review it. and approve it. Right, the auto 00:10:54.350 --> 00:10:57.490 -confirmed users. Exactly. Or if you don't even 00:10:57.490 --> 00:10:58.830 want to write it, you can just put your hand 00:10:58.830 --> 00:11:01.470 up and submit a request for someone else to do 00:11:01.470 --> 00:11:04.750 the heavy lifting. It is a highly structured, 00:11:05.309 --> 00:11:08.110 tiered bureaucracy. It really is. And notice 00:11:08.110 --> 00:11:10.129 the other suggestions they give you before you 00:11:10.129 --> 00:11:12.110 even try to create the page. What do you mean? 00:11:12.309 --> 00:11:15.029 Well, they explicitly tell you to search for 00:11:15.029 --> 00:11:17.570 weird Al Yankovich's greatest hits in existing 00:11:17.570 --> 00:11:21.090 articles and to look for pages within Wikipedia 00:11:21.090 --> 00:11:23.299 that link to this title. Like they're saying, 00:11:23.460 --> 00:11:25.419 are you absolutely sure you need to make this? 00:11:25.600 --> 00:11:28.100 Did you look everywhere else first? Exactly. 00:11:28.639 --> 00:11:32.000 It is a strict anti -redundancy measure. The 00:11:32.000 --> 00:11:34.240 system desperately wants to ensure that knowledge 00:11:34.240 --> 00:11:37.600 is consolidated, not fragmented. Because fragments 00:11:37.600 --> 00:11:40.419 are harder to manage. Right. Every new page is 00:11:40.419 --> 00:11:42.899 a new node in the database that has to be maintained, 00:11:43.299 --> 00:11:45.740 monitored for vandalism, and updated. That makes 00:11:45.740 --> 00:11:48.940 a lot of sense. If Weird Al's greatest hits are 00:11:48.940 --> 00:11:50.860 already discussed thoroughly in a subsection 00:11:50.860 --> 00:11:53.899 of his main biography page, the platform would 00:11:53.899 --> 00:11:56.220 much rather you just create a redirect to that 00:11:56.220 --> 00:11:59.539 existing section than create a messy, duplicate 00:11:59.539 --> 00:12:02.279 stub of an article. Oh, so if I search the album, 00:12:02.440 --> 00:12:04.440 it just seamlessly jumps me to his main page. 00:12:04.639 --> 00:12:06.519 Exactly. They're actively trying to keep the 00:12:06.519 --> 00:12:09.240 database clean, lean, and interconnected. OK, 00:12:09.320 --> 00:12:11.860 so we've looked at the mechanical void, the server 00:12:11.860 --> 00:12:14.659 lag, and the case sensitivity stuff. And we've 00:12:14.659 --> 00:12:17.360 explored the bureaucratic hurdles, the learner's 00:12:17.360 --> 00:12:19.659 permit of the article wizard, and the auto -confirmed 00:12:19.659 --> 00:12:22.600 gatekeeping. But now I want to look at the actual 00:12:22.600 --> 00:12:25.340 visual real estate of this page. Because the 00:12:25.340 --> 00:12:27.639 center of the page is just a blank void regarding 00:12:27.639 --> 00:12:30.870 the specific album. the margins of the page. 00:12:31.029 --> 00:12:33.509 Margins are busy. They're absolutely packed. 00:12:33.649 --> 00:12:36.470 The periphery of the error. Exactly. The source 00:12:36.470 --> 00:12:38.929 material outlines all these menus and sidebars 00:12:38.929 --> 00:12:41.409 that frame this empty space. First off, there 00:12:41.409 --> 00:12:43.710 is this whole section called In Other Projects. 00:12:43.710 --> 00:12:46.610 OK. And it says, look for weird Al Yankovich's 00:12:46.610 --> 00:12:49.330 greatest hits on one of Wikipedia's sister projects. 00:12:49.350 --> 00:12:52.649 And then it drops a massive list. What's on the 00:12:52.649 --> 00:12:55.710 list? Remind me. Listen to this scale. Wiktionary. 00:12:56.629 --> 00:13:00.649 Wikibooks. Wikiquote. Wikisource, Wikiversity, 00:13:01.350 --> 00:13:05.769 Commons, Wikivoyage, Wikinews, Wikidata, and 00:13:05.769 --> 00:13:08.860 my absolute personal favorite, WikiSpecies. It 00:13:08.860 --> 00:13:12.279 is an entire parallel universe of information. 00:13:12.539 --> 00:13:15.320 My analogy for this is, well, imagine you walk 00:13:15.320 --> 00:13:17.159 into a room looking for a specific painting and 00:13:17.159 --> 00:13:18.940 the room is completely empty. Right. But then 00:13:18.940 --> 00:13:20.759 you look around and you realize the empty room 00:13:20.759 --> 00:13:23.700 is just the lobby of a massive 10 -wing university 00:13:23.700 --> 00:13:25.840 campus. I love that. And the signs on the doors 00:13:25.840 --> 00:13:28.799 are pointing to the travel agency wing, the newsroom 00:13:28.799 --> 00:13:31.340 wing, and the biological classification wing. 00:13:31.700 --> 00:13:34.179 Why do all of these separate projects even exist? 00:13:34.240 --> 00:13:37.809 Why isn't it just one giant Wikipedia? If we 00:13:37.809 --> 00:13:39.990 connect this to the bigger picture, this list 00:13:39.990 --> 00:13:42.750 actually reveals a really profound insight into 00:13:42.750 --> 00:13:45.350 how humans categorize knowledge. Okay, later 00:13:45.350 --> 00:13:48.789 on me. Epistemologically speaking, different 00:13:48.789 --> 00:13:51.470 types of data require fundamentally different 00:13:51.470 --> 00:13:54.279 architectures. How so? Give me an example. Think 00:13:54.279 --> 00:13:56.659 about the boundary between a dictionary and an 00:13:56.659 --> 00:14:00.080 encyclopedia. An encyclopedia, like Wikipedia, 00:14:00.720 --> 00:14:03.259 is designed to explain the history, context, 00:14:03.360 --> 00:14:06.679 and significance of a concept, like the concept 00:14:06.679 --> 00:14:08.879 of an apple. Right, where apples come from, Johnny 00:14:08.879 --> 00:14:11.620 Appleseed, all that. Exactly. But a dictionary, 00:14:12.120 --> 00:14:15.080 like Wiktionary, is designed to explain the etymology, 00:14:15.519 --> 00:14:18.039 the pronunciation, and the part of speech of 00:14:18.039 --> 00:14:21.120 the word apple. Oh, I see. Those require totally 00:14:21.120 --> 00:14:23.720 different database fields. Right, and WikiSpecies. 00:14:23.940 --> 00:14:26.659 A database for biological taxonomy requires strict, 00:14:26.720 --> 00:14:30.580 hierarchical fields for genus, family, kingdom, 00:14:30.759 --> 00:14:32.679 and phylum. You can't just write a free -form 00:14:32.679 --> 00:14:35.580 paragraph. Oh, wow, yeah. That's a totally different 00:14:35.580 --> 00:14:38.000 structure. And a travel guide like WikiVoyage 00:14:38.000 --> 00:14:41.299 needs fields for interactive maps, hotel coordinates, 00:14:41.860 --> 00:14:45.009 and currency exchange info. If you tried to cram 00:14:45.009 --> 00:14:47.950 biological taxonomy, dictionary pronunciations, 00:14:48.049 --> 00:14:51.370 and hotel reviews into one single software architecture, 00:14:51.750 --> 00:14:54.049 the code would literally collapse under its own 00:14:54.049 --> 00:14:56.350 weight. It would be a nightmare to search. A 00:14:56.350 --> 00:14:58.750 complete mess. By presenting all these sister 00:14:58.750 --> 00:15:01.570 projects on an error page, the platform is reminding 00:15:01.570 --> 00:15:04.190 you of its sheer scale. It's basically saying, 00:15:04.399 --> 00:15:06.779 We might not have what you want here, but look 00:15:06.779 --> 00:15:09.240 at the entirety of human knowledge we are attempting 00:15:09.240 --> 00:15:11.960 to organize. It's a flex. It's a total flex. 00:15:12.179 --> 00:15:14.600 And the customization options are just as expansive. 00:15:14.620 --> 00:15:17.059 Right. The appearance settings. The source outlines 00:15:17.059 --> 00:15:19.600 these incredible appearance toggles right there 00:15:19.600 --> 00:15:22.279 on the sidebar. You can adjust the text size 00:15:22.279 --> 00:15:25.399 to small, standard, or large. You can adjust 00:15:25.399 --> 00:15:28.659 the width of the page to standard or wide. Which 00:15:28.659 --> 00:15:30.899 is kind of hilarious, by the way. It is, because 00:15:30.899 --> 00:15:33.320 it explicitly notes the content is as wide as 00:15:33.320 --> 00:15:35.500 possible for your browser window when there is 00:15:35.500 --> 00:15:37.600 essentially absolutely no content on the page 00:15:37.600 --> 00:15:41.330 to widen. It is delightfully ironic. The frame 00:15:41.330 --> 00:15:43.409 stretches perfectly to accommodate the missing 00:15:43.409 --> 00:15:45.629 picture. But the absolute best detail, the thing 00:15:45.629 --> 00:15:47.710 that I genuinely laughed at when reading the 00:15:47.710 --> 00:15:50.450 source, is a toggle in the appearance menu called 00:15:50.450 --> 00:15:54.769 birthday mode. OK. And in parentheses, it specifies 00:15:54.769 --> 00:15:57.990 baby globe. You can have it disabled or enabled. 00:15:58.210 --> 00:16:00.490 The baby globe. I mean, we've just spent the 00:16:00.490 --> 00:16:02.750 last 10 minutes talking about strict bureaucratic 00:16:02.750 --> 00:16:06.110 deletion logs, database server purging and auto 00:16:06.110 --> 00:16:09.450 confirmed status. Very serious stuff. Exactly. 00:16:09.789 --> 00:16:12.129 And right next to all of that rigid governance 00:16:12.129 --> 00:16:16.129 is a whimsical toggle for a baby globe birthday 00:16:16.129 --> 00:16:19.909 mode. It's so unexpectedly human. It really highlights 00:16:19.909 --> 00:16:22.789 the open source, community driven nature of the 00:16:22.789 --> 00:16:25.110 code itself. Right. Someone had to program that. 00:16:25.200 --> 00:16:27.919 Our volunteer developers build these little Easter 00:16:27.919 --> 00:16:30.299 eggs or quality of life features into the user 00:16:30.299 --> 00:16:33.259 interface. It shows a platform that is actively 00:16:33.259 --> 00:16:35.840 trying to optimize your reading environment and 00:16:35.840 --> 00:16:38.200 personalize your experience, even when there 00:16:38.200 --> 00:16:40.220 is absolutely nothing for you to read. They just 00:16:40.220 --> 00:16:42.340 want you to be comfortable in the void. Exactly. 00:16:42.679 --> 00:16:44.980 They care deeply about the experience of the 00:16:44.980 --> 00:16:47.379 interface. But then you scroll down to the very 00:16:47.379 --> 00:16:49.639 bottom, down to the tiny text in the footer of 00:16:49.639 --> 00:16:53.860 the page, and the whimsical baby globe vibe vanishes 00:16:53.860 --> 00:16:58.019 completely. We are right back to serious institutional 00:16:58.019 --> 00:17:00.519 grounding. The fine print at the bottom of the 00:17:00.519 --> 00:17:02.460 internet. Yep. What is the source list down there? 00:17:02.720 --> 00:17:05.779 It's a heavy list. Let me read it. Privacy policy, 00:17:06.359 --> 00:17:09.500 disclaimers, contact Wikipedia, legal and safety 00:17:09.500 --> 00:17:13.500 contacts, code of conduct, developers, statistics. 00:17:13.950 --> 00:17:17.250 Cookie statement. What stands out to you about 00:17:17.250 --> 00:17:20.490 that specific grouping of links? For me, honestly, 00:17:20.750 --> 00:17:23.150 it's seeing the phrase code of conduct sitting 00:17:23.150 --> 00:17:25.890 right next to legal and safety contacts. Yeah, 00:17:26.069 --> 00:17:28.440 that's a big shift in tone. It is a stark reminder 00:17:28.440 --> 00:17:30.660 that this isn't just a fun little passion project 00:17:30.660 --> 00:17:32.519 being run out of someone's garage anymore. It's 00:17:32.519 --> 00:17:35.000 a massive legal entity. It absolutely is. It 00:17:35.000 --> 00:17:37.220 has to worry about international privacy laws, 00:17:37.619 --> 00:17:39.980 cookie tracking regulations in Europe, and maintaining 00:17:39.980 --> 00:17:42.799 a safe working environment for thousands of volunteer 00:17:42.799 --> 00:17:45.279 editors working across the globe. That is the 00:17:45.279 --> 00:17:48.039 crux of it right there. Those footer links anchor 00:17:48.039 --> 00:17:50.940 what seems like a wild west of crowd -sourced 00:17:50.940 --> 00:17:54.819 information into a rigid, real -world legal and 00:17:54.819 --> 00:17:57.200 statistical framework. Right. It grounds it. 00:17:57.400 --> 00:18:00.000 The code of conduct is essentially the HR department 00:18:00.000 --> 00:18:02.059 for those auto -confirmed users we talked about 00:18:02.059 --> 00:18:05.440 earlier. Without a code of conduct, that collaboration 00:18:05.440 --> 00:18:08.920 breaks down into toxicity. Of course. Put thousands 00:18:08.920 --> 00:18:11.319 of people in a room to argue over facts, you 00:18:11.319 --> 00:18:14.720 need rules. Exactly. And the statistics link 00:18:14.720 --> 00:18:17.420 implies a constant algorithmic monitoring of 00:18:17.420 --> 00:18:19.960 the database's health, the server load, and the 00:18:19.960 --> 00:18:22.900 overall growth. This totally empty error page 00:18:22.900 --> 00:18:25.720 is actually being supported by a massive, invisible 00:18:25.720 --> 00:18:28.519 scaffolding of rules, metrics, and lawyers. So 00:18:28.519 --> 00:18:30.579 what does this all mean? We started out today 00:18:30.579 --> 00:18:33.359 looking at a digital dead end, an error page 00:18:33.359 --> 00:18:35.940 for a compilation comedy album that literally 00:18:35.940 --> 00:18:38.339 tells you it has zero content. Zero content on 00:18:38.339 --> 00:18:40.460 the subject you wanted anyway. Right. But by 00:18:40.460 --> 00:18:42.420 taking the time to read the fine print to not 00:18:42.420 --> 00:18:45.000 just close the tab, we've essentially uncovered 00:18:45.000 --> 00:18:47.759 a comprehensive blueprint of the internet's most 00:18:47.759 --> 00:18:50.299 important website. We found the structural foundation. 00:18:50.119 --> 00:18:53.400 Exactly. It reveals the mechanical realities, 00:18:53.539 --> 00:18:56.160 the fact that a database has to cache to survive, 00:18:56.359 --> 00:18:58.819 and that it cares deeply about the mathematical 00:18:58.819 --> 00:19:01.099 difference between a capital and a lowercase 00:19:01.099 --> 00:19:04.140 letter. The ASCII codes. Yep. And it reveals 00:19:04.140 --> 00:19:07.339 the human gatekeeping, the reality that you have 00:19:07.339 --> 00:19:09.579 to prove your worth as an auto -confirmed user 00:19:09.579 --> 00:19:12.579 to create, or you have to subject yourself to 00:19:12.579 --> 00:19:15.160 the bureaucracy of an article wizard. The learner's 00:19:15.160 --> 00:19:17.680 permit. And it reveals the staggering ecosystem 00:19:17.680 --> 00:19:20.259 from the biological directories of of wiki species 00:19:20.259 --> 00:19:23.039 to the legal disclaimers holding the whole thing 00:19:23.039 --> 00:19:26.380 together. You, as a listener, should care about 00:19:26.380 --> 00:19:28.680 this because these invisible rules dictate the 00:19:28.680 --> 00:19:30.980 information you consume every single day. They 00:19:30.980 --> 00:19:33.500 shape your reality. Exactly. The shape of the 00:19:33.500 --> 00:19:35.279 container dictates the shape of the knowledge 00:19:35.279 --> 00:19:38.059 we receive. That is exactly right. The architecture 00:19:38.059 --> 00:19:40.079 of the platform dictates what survives, what 00:19:40.079 --> 00:19:43.240 gets merged, and what gets destroyed. And actually, 00:19:43.299 --> 00:19:45.279 that leads me to a final thought for you to mull 00:19:45.279 --> 00:19:47.759 over. Oh, go for it. Next time you search for 00:19:47.759 --> 00:19:51.039 something online. a person, an event, a piece 00:19:51.039 --> 00:19:54.000 of art, and you hit that wall and you find absolute 00:19:54.000 --> 00:19:57.200 silence. I want you to think about Wikipedia's 00:19:57.200 --> 00:20:01.359 deletion log. We implicitly trust these platforms 00:20:01.359 --> 00:20:04.519 to be the ultimate objective repositories of 00:20:04.519 --> 00:20:07.839 human history. But what invisible histories, 00:20:08.160 --> 00:20:10.920 what controversial ideas or forgotten cultural 00:20:10.920 --> 00:20:14.240 artifacts are actively being erased, rejected 00:20:14.240 --> 00:20:17.440 or deemed not notable enough right now by the 00:20:17.440 --> 00:20:19.839 auto -confirmed gatekeepers of our digital age. 00:20:19.880 --> 00:20:22.240 Wow. When you go to that digital vending machine 00:20:22.240 --> 00:20:24.420 and nothing comes out, it isn't always because 00:20:24.420 --> 00:20:26.500 the snack was never made. Sometimes the void 00:20:26.500 --> 00:20:28.720 isn't really empty. Sometimes it is a highly 00:20:28.720 --> 00:20:32.059 curated silence. A curated silence. Wow. I will 00:20:32.059 --> 00:20:34.000 say this next time I hit a page not found, I'm 00:20:34.000 --> 00:20:36.240 definitely not just closing. the tab. You'll 00:20:36.240 --> 00:20:37.779 be checking the return shoot in the base. I'll 00:20:37.779 --> 00:20:39.660 be checking the return shoot and I will definitely 00:20:39.660 --> 00:20:41.759 be keeping a close eye out for the library committee.