WEBVTT 00:00:00.000 --> 00:00:02.200 Welcome to this custom -tailored deep dives. 00:00:02.580 --> 00:00:06.320 Today, we are looking at the sources you sent 00:00:06.320 --> 00:00:08.660 us, and I have to admit, you threw us a massive 00:00:08.660 --> 00:00:10.640 curveball this time. Yeah, we definitely weren't 00:00:10.640 --> 00:00:12.580 expecting this one. Right, because usually we're 00:00:12.580 --> 00:00:15.820 unpacking, you know, a dense scientific paper 00:00:15.820 --> 00:00:17.760 or a historical treatise or some breaking news 00:00:17.760 --> 00:00:22.370 report. But today, you handed us... blank page 00:00:22.370 --> 00:00:25.390 literally a blank page literally specifically 00:00:25.390 --> 00:00:28.269 we are looking at a Wikipedia page not found 00:00:28.269 --> 00:00:31.449 error for the name Mary Frances yeah spelled 00:00:31.449 --> 00:00:34.149 as one single word it is definitely not our usual 00:00:34.149 --> 00:00:35.689 source material when you first sent this over 00:00:35.689 --> 00:00:39.070 I think the initial reaction was to think Maybe 00:00:39.070 --> 00:00:41.450 there was a mistake, like maybe a broken link. 00:00:41.570 --> 00:00:43.270 Yeah, I thought the file was corrupted or something. 00:00:43.429 --> 00:00:45.710 Right, because we're looking at the literal absence 00:00:45.710 --> 00:00:48.609 of information. But then when you start to really 00:00:48.609 --> 00:00:52.590 analyze the text on this specific 404 page, you 00:00:52.590 --> 00:00:55.229 realize it's, well, it is essentially a blueprint. 00:00:55.509 --> 00:00:57.509 Okay, let's unpack this. Because at first glance, 00:00:57.590 --> 00:00:59.450 you see a missing page and you think, well, there's 00:00:59.450 --> 00:01:01.149 nothing here. It's a dead end, right? Let's just 00:01:01.149 --> 00:01:03.509 move to the next topic. Exactly, yeah. But the 00:01:03.509 --> 00:01:05.890 mission of this deep dive isn't to figure out 00:01:05.890 --> 00:01:09.090 who Mary Frances is. The mission is to explore 00:01:09.090 --> 00:01:12.030 the invisible machinery around this missing cage. 00:01:12.109 --> 00:01:15.189 Be the context. It's like looking at the negative 00:01:15.189 --> 00:01:17.609 space in a painting to understand the whole picture. 00:01:17.790 --> 00:01:20.709 I love that analogy because if we connect this 00:01:20.709 --> 00:01:23.549 to the bigger picture of how digital repositories 00:01:23.549 --> 00:01:27.359 actually work. This single, seemingly empty page 00:01:27.359 --> 00:01:30.500 reveals the incredibly complex infrastructure 00:01:30.500 --> 00:01:33.060 of the world's biggest encyclopedia. It really 00:01:33.060 --> 00:01:35.480 does. When you strip away the actual article 00:01:35.480 --> 00:01:38.140 content, you are left staring directly at the 00:01:38.140 --> 00:01:41.540 framework. You see how this massive entity categorizes 00:01:41.540 --> 00:01:43.859 human knowledge, how it attempts to troubleshoot 00:01:43.859 --> 00:01:46.819 errors in real time, and how it governs a global 00:01:46.819 --> 00:01:50.099 community of editors. Yeah. It is a master class 00:01:50.099 --> 00:01:52.780 in digital architecture hiding right there in 00:01:52.780 --> 00:01:55.439 plain sight. So let's jump right into the architecture 00:01:55.439 --> 00:01:58.159 of this void. I want to look at the exact wording 00:01:58.159 --> 00:02:00.239 you encounter when you search for Mary Frances. 00:02:00.480 --> 00:02:04.200 The phrasing is so specific. It really is. The 00:02:04.200 --> 00:02:06.060 site doesn't just give you a blank white screen. 00:02:06.439 --> 00:02:09.219 It gives you a very carefully constructed message. 00:02:09.460 --> 00:02:13.039 It says, Wikipedia does not have an article with 00:02:13.039 --> 00:02:15.840 this exact name. Right. It doesn't say Mary Frances 00:02:15.840 --> 00:02:18.199 doesn't exist or that the topic isn't important 00:02:18.199 --> 00:02:21.580 enough. It specifically says, we don't have it 00:02:21.580 --> 00:02:23.919 with this exact name. That phrasing is crucial. 00:02:24.280 --> 00:02:26.659 It instantly pivots from a statement of absence 00:02:26.659 --> 00:02:29.860 into a troubleshooting guide. And if we look 00:02:29.860 --> 00:02:31.939 at the system's own advice for the user, for 00:02:31.939 --> 00:02:34.759 you the listener who searched this, we uncover 00:02:34.759 --> 00:02:37.800 some really specific database quirks. Okay, like 00:02:37.800 --> 00:02:40.099 what? Well, for instance, the system notes that 00:02:40.099 --> 00:02:42.280 titles on the platform are, and I quote from 00:02:42.280 --> 00:02:44.139 the source here, case sensitive, except for the 00:02:44.139 --> 00:02:46.560 first character. Wait, wait, just the first character? 00:02:46.699 --> 00:02:48.819 It seems random, right? And did a programmer 00:02:48.819 --> 00:02:51.219 just get lazy early on? Or is there an actual 00:02:51.219 --> 00:02:54.080 functional reason for that highly specific rule? 00:02:54.340 --> 00:02:56.400 There is a very functional reason, and it comes 00:02:56.400 --> 00:02:58.860 down to how human beings actually search for 00:02:58.860 --> 00:03:01.259 information online. Think about how you type 00:03:01.259 --> 00:03:04.580 on your phone. Often, your phone's keyboard will 00:03:04.580 --> 00:03:07.000 automatically capitalize the first letter of 00:03:07.000 --> 00:03:09.819 a search term. Oh, right. It always does that. 00:03:10.020 --> 00:03:12.939 Or, conversely, you might be typing quickly on 00:03:12.939 --> 00:03:15.280 a laptop and just keep everything lowercase because 00:03:15.280 --> 00:03:18.099 you are in a rush. Sure. The system needs Mary 00:03:18.099 --> 00:03:21.120 Frances with a lowercase m and Mary Frances with 00:03:21.120 --> 00:03:24.240 an uppercase m to lead to the exact same destination. 00:03:24.620 --> 00:03:27.259 If it didn't do that, the database would be flooded 00:03:27.259 --> 00:03:30.240 with endless duplicate pages just because someone 00:03:30.240 --> 00:03:33.300 hit the shift key. Wow. That actually makes perfect 00:03:33.300 --> 00:03:35.840 sense. Yeah. But the source text points out that 00:03:35.840 --> 00:03:39.080 beyond that first letter, the database is incredibly 00:03:39.080 --> 00:03:42.740 rigid. Extremely rigid. Every subsequent capital 00:03:42.740 --> 00:03:45.000 letter matters. That's why the page prompts you 00:03:45.000 --> 00:03:47.060 to check alternative capitalizations. Right. 00:03:47.159 --> 00:03:49.379 It even suggests that if you do find the correct 00:03:49.379 --> 00:03:51.939 page under a distant capitalization, you should 00:03:51.939 --> 00:03:54.219 consider adding a redirect to the correct title. 00:03:54.379 --> 00:03:57.520 A redirect. So it's essentially asking you. the 00:03:57.520 --> 00:03:59.919 reader, to help wire the electrical system of 00:03:59.919 --> 00:04:02.139 the encyclopedia so the next person doesn't hit 00:04:02.139 --> 00:04:04.900 the same dead end. Exactly. It's crowdsourcing 00:04:04.900 --> 00:04:06.919 the maintenance. It's treating you like a potential 00:04:06.919 --> 00:04:08.939 maintenance worker. Yeah. And then we get to 00:04:08.939 --> 00:04:10.599 what I like to call the ghosts in the machine. 00:04:10.740 --> 00:04:13.039 The ghosts in the machine, yes. The page offers 00:04:13.039 --> 00:04:15.719 some slightly eerie possibilities for why Mary 00:04:15.719 --> 00:04:18.939 Frances isn't showing up. The text says, if a 00:04:18.939 --> 00:04:21.100 page was recently created here, it may not be 00:04:21.100 --> 00:04:24.000 visible yet because of a delay in updating the 00:04:24.000 --> 00:04:26.680 database. Right. And it asks you to wait a few 00:04:26.680 --> 00:04:29.500 minutes or, and this sounds like something out 00:04:29.500 --> 00:04:32.220 of a sci -fi movie, try the purge function. The 00:04:32.220 --> 00:04:34.500 purge function. I know it does sound incredibly 00:04:34.500 --> 00:04:37.040 dramatic, like you are initiating a self -destruct 00:04:37.040 --> 00:04:39.040 sequence. Right. But it's actually referring 00:04:39.040 --> 00:04:42.040 to a very real technical process regarding server 00:04:42.040 --> 00:04:44.420 caches. A cache is one of those words we hear 00:04:44.420 --> 00:04:46.899 all the time, but we rarely define it. How does 00:04:46.899 --> 00:04:48.860 the purge function actually interact with the 00:04:48.860 --> 00:04:51.759 cache here? Think of a cache like a restaurant's 00:04:51.759 --> 00:04:54.959 pre -printed daily menu. Okay. To save time, 00:04:55.079 --> 00:04:57.579 the restaurant prints 100 menus in the morning. 00:04:58.079 --> 00:05:00.360 If you walk in at noon, they hand you that menu. 00:05:00.579 --> 00:05:02.720 But let's say they just ran out of the soup of 00:05:02.720 --> 00:05:05.399 the day, or conversely, the chef just whipped 00:05:05.399 --> 00:05:07.600 up a brand new special. So the menu is wrong 00:05:07.600 --> 00:05:10.240 now. Right. That pre -printed menu, the cache, 00:05:10.540 --> 00:05:12.860 is now outdated. So it's a snapshot of the past. 00:05:13.339 --> 00:05:15.980 Precisely. It's a snapshot. So to get the server 00:05:15.980 --> 00:05:18.620 to clear its cache, to essentially throw away 00:05:18.620 --> 00:05:21.240 those outdated pre -printed menus and go ask 00:05:21.240 --> 00:05:24.300 the chef what is actively cooking right the second 00:05:24.300 --> 00:05:26.720 you use the purge function. Oh, wow. It forces 00:05:26.720 --> 00:05:29.480 the system to fetch the absolute most recent 00:05:29.480 --> 00:05:32.139 version of a page. And this raises an important 00:05:32.139 --> 00:05:34.500 point about the nature of digital information. 00:05:34.879 --> 00:05:37.660 We tend to think of the Internet as this instantaneous 00:05:37.660 --> 00:05:41.339 magic. Just floating in the cloud. Exactly. But 00:05:41.339 --> 00:05:44.250 this text reminds us. that even the largest encyclopedia 00:05:44.250 --> 00:05:47.170 in human history is still a physical database 00:05:47.170 --> 00:05:50.430 sitting on actual servers subject to traffic 00:05:50.430 --> 00:05:53.389 jams and processing delays your page might actually 00:05:53.389 --> 00:05:55.750 exist but it might just be stuck in digital traffic 00:05:55.750 --> 00:05:58.149 that is wild and if it's not stuck in traffic 00:05:58.149 --> 00:06:00.230 the text suggests it might have been completely 00:06:00.230 --> 00:06:03.029 erased yes the other possibility the page gives 00:06:03.029 --> 00:06:05.540 you is that the article was deleted and it prompts 00:06:05.540 --> 00:06:07.720 you to check the deletion log the deletion log 00:06:07.720 --> 00:06:10.540 it even links to a specific help page titled 00:06:10.540 --> 00:06:13.540 why was the page i created deleted like a digital 00:06:13.540 --> 00:06:17.000 graveyard it is a digital graveyard and it's 00:06:17.000 --> 00:06:19.379 a stark reminder that information doesn't just 00:06:19.379 --> 00:06:22.920 organically grow wild on this platform it is 00:06:22.920 --> 00:06:26.579 actively and sometimes ruthlessly pruned ruthlessly 00:06:26.579 --> 00:06:29.500 pruned i like that Not everything survives the 00:06:29.500 --> 00:06:31.779 editorial process, which brings up the really 00:06:31.779 --> 00:06:33.899 interesting aspect of the source material regarding 00:06:33.899 --> 00:06:36.139 who actually gets to create these pages in the 00:06:36.139 --> 00:06:37.819 first place. OK, yeah, let's talk about that. 00:06:38.100 --> 00:06:40.540 So if the page is missing and I want to fix that, 00:06:40.600 --> 00:06:42.420 can I just start typing? Because you always hear 00:06:42.420 --> 00:06:44.620 it's the free encyclopedia that anyone can edit. 00:06:44.740 --> 00:06:46.560 So I should just be able to write the Mary Frances 00:06:46.560 --> 00:06:48.560 page right now, right? You would think so based 00:06:48.560 --> 00:06:51.540 on that reputation. But the source text outlines 00:06:51.540 --> 00:06:54.279 a very clear barrier to entry. What does it say? 00:06:54.399 --> 00:06:58.529 It states. You need to log in or create an account 00:06:58.529 --> 00:07:01.290 and be auto -confirmed to create new articles. 00:07:01.649 --> 00:07:04.589 Auto -confirmed. That sounds like corporate jargon. 00:07:04.610 --> 00:07:06.290 What does that actually mean for the average 00:07:06.290 --> 00:07:09.170 user who's just trying to contribute? It reveals 00:07:09.170 --> 00:07:11.970 a distinct hierarchy within the community. You 00:07:11.970 --> 00:07:14.149 aren't just a full -fledged editor the moment 00:07:14.149 --> 00:07:16.750 you show up. You have to undergo a probationary 00:07:16.750 --> 00:07:19.569 period. Think of it like starting a new job in 00:07:19.569 --> 00:07:22.540 retail. On your first day, they don't hand you 00:07:22.540 --> 00:07:24.660 the keys to the store and let you manage the 00:07:24.660 --> 00:07:27.019 cash register alone. No, definitely not. You 00:07:27.019 --> 00:07:29.339 have to shadow someone, learn the ropes, and 00:07:29.339 --> 00:07:30.959 prove you aren't going to accidentally delete 00:07:30.959 --> 00:07:34.160 the inventory. In this digital ecosystem, being 00:07:34.160 --> 00:07:36.399 auto -confirmed generally means your account 00:07:36.399 --> 00:07:38.639 has to be a certain number of days old and you 00:07:38.639 --> 00:07:41.180 have to have made a certain number of minor acceptable 00:07:41.180 --> 00:07:43.920 edits elsewhere before you are trusted with the 00:07:43.920 --> 00:07:46.180 power to create a brand new entry from scratch. 00:07:46.779 --> 00:07:49.540 So it's a velvet rope. Exactly. It's not the 00:07:49.540 --> 00:07:52.600 Wild West anymore. There is a very rigorous bureaucracy 00:07:52.600 --> 00:07:56.180 in place. But let's say I'm not auto -confirmed. 00:07:56.220 --> 00:07:58.600 I'm just a passionate person who knows there 00:07:58.600 --> 00:08:01.459 needs to be a page for Mary Frances. The site 00:08:01.459 --> 00:08:03.379 doesn't just tell me to go away, does it? No, 00:08:03.379 --> 00:08:05.399 it doesn't just shut you out. The text provides 00:08:05.399 --> 00:08:09.079 a fallback option. It says, alternatively, you 00:08:09.079 --> 00:08:11.500 can use the article wizard to submit a draft 00:08:11.500 --> 00:08:15.100 for review or request a new article. Notice the 00:08:15.100 --> 00:08:17.339 specific language there. I'm not publishing an 00:08:17.339 --> 00:08:19.779 article. I'm using a wizard to submit a draft 00:08:19.779 --> 00:08:22.959 for review. Yes, the wording implies a structured 00:08:22.959 --> 00:08:25.600 gauntlet. You are submitting your work to be 00:08:25.600 --> 00:08:27.620 checked by those invisible guards standing at 00:08:27.620 --> 00:08:30.199 the door. They are checking your citations, your 00:08:30.199 --> 00:08:32.360 formatting, and whether the topic meets their 00:08:32.360 --> 00:08:35.519 specific criteria for notability. This highlights 00:08:35.519 --> 00:08:38.179 the intense vetting process required to add new 00:08:38.179 --> 00:08:40.950 information to this database today. It is no 00:08:40.950 --> 00:08:43.509 longer a blank wall where anyone can spray paint 00:08:43.509 --> 00:08:46.730 a fun fact. That era is over. Completely over. 00:08:46.850 --> 00:08:49.649 It is a highly structured editorial environment 00:08:49.649 --> 00:08:52.629 with strict checkpoints. So what does this all 00:08:52.629 --> 00:08:55.429 mean for the user? It means the site is actively 00:08:55.429 --> 00:08:58.230 protecting itself from spam, from vandalism, 00:08:58.250 --> 00:09:01.269 from bad actors trying to manipulate information. 00:09:02.300 --> 00:09:04.860 We implicitly trust this platform for a quick 00:09:04.860 --> 00:09:07.159 summary of a historical event or a scientific 00:09:07.159 --> 00:09:09.779 concept, but we rarely think about the complex 00:09:09.779 --> 00:09:12.139 security systems operating behind the scenes 00:09:12.139 --> 00:09:14.600 to keep that information reliable. We take it 00:09:14.600 --> 00:09:16.799 for granted. And if your submission can't get 00:09:16.799 --> 00:09:19.039 through that door, if it doesn't meet the encyclopedic 00:09:19.039 --> 00:09:21.639 criteria the system points you outward, it suggests 00:09:21.639 --> 00:09:24.059 that if Mary Frances is in an encyclopedia article, 00:09:24.340 --> 00:09:26.580 maybe it belongs somewhere else within their 00:09:26.580 --> 00:09:29.139 broader network. Oh, here is where it gets really 00:09:29.139 --> 00:09:31.899 interesting, because the page says, look for 00:09:31.899 --> 00:09:34.879 Mary Frances on one of Wikipedia's sister projects. 00:09:35.159 --> 00:09:37.000 The sister project. I think most people know 00:09:37.000 --> 00:09:39.100 the main site, obviously. But the list provided 00:09:39.100 --> 00:09:43.340 on this page reveals an entire sprawling extended 00:09:43.340 --> 00:09:46.320 universe. We have to look at these because it 00:09:46.320 --> 00:09:49.399 shows how ridiculously human knowledge is being 00:09:49.399 --> 00:09:52.240 categorized by these volunteers. It really is 00:09:52.240 --> 00:09:55.360 a taxonomy of information. The source lists 10 00:09:55.360 --> 00:09:58.019 distinct sister. projects. Let's group them to 00:09:58.019 --> 00:10:00.399 understand what they are actually trying to achieve 00:10:00.399 --> 00:10:03.419 here. First, we have witchinary, which is categorized 00:10:03.419 --> 00:10:05.779 as the dictionary. Right. So if Mary Frances 00:10:05.779 --> 00:10:08.500 isn't a full encyclopedic topic with a rich history, 00:10:08.659 --> 00:10:11.000 maybe it's just a name that needs an etymological 00:10:11.000 --> 00:10:13.519 definition. Or maybe it translates to something 00:10:13.519 --> 00:10:16.019 specific in another language. Exactly. And then 00:10:16.019 --> 00:10:18.580 you have the educational tier. The source lists 00:10:18.580 --> 00:10:21.659 Wikibooks, which it describes as textbooks, and 00:10:21.659 --> 00:10:24.200 Wikiversity for learning resources. Imagine a 00:10:24.200 --> 00:10:26.480 whole open source textbook just on the subject 00:10:26.480 --> 00:10:29.580 of Mary Frances. Or a full university level curriculum. 00:10:30.019 --> 00:10:34.159 Then there is Wikiquote for quotations and Wikisource, 00:10:34.399 --> 00:10:36.899 which is described as a library. So maybe Mary 00:10:36.899 --> 00:10:39.120 Frances is the author of a public domain text 00:10:39.120 --> 00:10:42.059 or the source of a feminist historical quote. 00:10:42.399 --> 00:10:45.139 Now let's look at the data and media layer. The 00:10:45.139 --> 00:10:48.899 page lists Commons. for media and Wikidata, the 00:10:48.899 --> 00:10:51.620 linked database. Wikidata is fascinating because 00:10:51.620 --> 00:10:53.679 it's so different from a traditional article. 00:10:53.860 --> 00:10:56.519 It operates on an entirely different level. While 00:10:56.519 --> 00:10:58.720 an encyclopedia article is written in paragraphs 00:10:58.720 --> 00:11:01.759 for human beings to read, Wikidata is structured 00:11:01.759 --> 00:11:04.460 information designed to be read by machines and 00:11:04.460 --> 00:11:07.259 search engines. Oh, right. It's the raw data, 00:11:07.440 --> 00:11:09.960 birth dates, geographical coordinates, statistical 00:11:09.960 --> 00:11:13.080 relationships. It is the invisible web of facts 00:11:13.080 --> 00:11:15.379 that feeds artificial intelligence and search 00:11:15.379 --> 00:11:17.639 algorithms globally. And then we round out the 00:11:17.639 --> 00:11:20.480 list with Wikivoyage, The Travel Guide, Wikinews, 00:11:20.600 --> 00:11:22.980 The News Source, and finally, Wikispecies, The 00:11:22.980 --> 00:11:26.539 Species Directory. Wikispecies. Unless Mary Frances 00:11:26.539 --> 00:11:29.279 is a newly discovered type of beetle or a rare 00:11:29.279 --> 00:11:31.940 fungus, she probably isn't in there. But I want 00:11:31.940 --> 00:11:34.620 you, the listener, to really consider the scope 00:11:34.620 --> 00:11:36.779 of this network for a moment. It's staggering 00:11:36.779 --> 00:11:39.019 when you see it all laid out like this. We are 00:11:39.019 --> 00:11:41.600 so used to typing a query into a search engine 00:11:41.600 --> 00:11:44.700 and expecting one synthesized answer. We completely 00:11:44.700 --> 00:11:47.779 forget that there are global volunteer led efforts 00:11:47.779 --> 00:11:51.159 systematically mapping every single type of human 00:11:51.159 --> 00:11:53.940 knowledge into distinct buckets. They aren't 00:11:53.940 --> 00:11:56.080 just hoarding facts in one giant pile. Right. 00:11:56.220 --> 00:11:58.659 They're actively separating them into definitions, 00:11:59.039 --> 00:12:02.080 curriculums, historical texts, machine readable 00:12:02.080 --> 00:12:05.200 data points, media libraries and biological directories. 00:12:05.240 --> 00:12:07.980 It is a monumental, highly categorized under. 00:12:08.009 --> 00:12:10.789 It's like walking into a massive infinite library 00:12:10.789 --> 00:12:13.870 asking for a specific biography and the librarian 00:12:13.870 --> 00:12:16.070 says, we don't have a biography on that person. 00:12:16.190 --> 00:12:18.750 Yeah. But have you checked the linguistics wing, 00:12:18.889 --> 00:12:22.269 the photography archives, the zoology department? 00:12:22.529 --> 00:12:24.090 That's a great way to put it. It's mind blowing. 00:12:24.250 --> 00:12:26.730 And what proves that this digital library isn't 00:12:26.730 --> 00:12:28.830 just a dusty archive of old facts is right at 00:12:28.830 --> 00:12:31.590 the top of the source page. It is a living. breathing 00:12:31.590 --> 00:12:33.730 interface. You were referring to the campaign 00:12:33.730 --> 00:12:36.409 banner that appeared on the page. Yes. The text 00:12:36.409 --> 00:12:39.129 you provided explicitly shows a banner for a 00:12:39.129 --> 00:12:41.690 global campaign. It says, Wiki loves Ramadan 00:12:41.690 --> 00:12:44.870 2026. Tell the world about Ramadan traditions. 00:12:45.500 --> 00:12:48.600 This is a crucial piece of the puzzle. The stated 00:12:48.600 --> 00:12:50.820 goal of this campaign, right there in the text, 00:12:51.000 --> 00:12:53.779 is to bridge knowledge gaps about Islamic history 00:12:53.779 --> 00:12:56.620 and culture, and it actively invites the user 00:12:56.620 --> 00:12:59.460 to participate now. It's a direct call to action. 00:12:59.580 --> 00:13:02.419 Exactly. This proves the platform isn't just 00:13:02.419 --> 00:13:04.899 a static database passively waiting for people 00:13:04.899 --> 00:13:07.600 to stumble in and add things. It is a proactive 00:13:07.600 --> 00:13:11.019 community. The editors recognize they have blind 00:13:11.019 --> 00:13:13.360 spots based on who is writing the articles and 00:13:13.360 --> 00:13:16.240 where they live. counter that, they are actively 00:13:16.240 --> 00:13:18.759 running targeted campaigns to fill those global 00:13:18.759 --> 00:13:21.519 voids. It reminds you that the encyclopedia is 00:13:21.519 --> 00:13:24.139 written by real people, and sometimes those people 00:13:24.139 --> 00:13:26.519 need to be rallied together to focus on a specific 00:13:26.519 --> 00:13:29.600 area of human history. Absolutely. And speaking 00:13:29.600 --> 00:13:31.960 of the interface, we have to talk about the quirky 00:13:31.960 --> 00:13:34.659 customizations available to the user, because 00:13:34.659 --> 00:13:37.200 this error page gives you immense control over 00:13:37.200 --> 00:13:39.580 how you view the void. The customization options 00:13:39.580 --> 00:13:42.000 listed in the source are surprisingly granular 00:13:42.000 --> 00:13:44.559 for a page that technically doesn't even exist. 00:13:45.019 --> 00:13:47.720 You have standard interface mechanics. You can 00:13:47.720 --> 00:13:50.139 control the text size, choosing between small, 00:13:50.379 --> 00:13:53.399 standard, or large, though the text notes a technical 00:13:53.399 --> 00:13:56.080 limitation saying, this page always uses small 00:13:56.080 --> 00:13:59.080 font size. You can also control the width, choosing 00:13:59.080 --> 00:14:01.139 between standard or wide, where the content is 00:14:01.139 --> 00:14:03.019 as wide as possible for your browser window. 00:14:03.200 --> 00:14:05.620 And you can control the color beta, toggling 00:14:05.620 --> 00:14:07.759 between automatic, light mode, or dark mode. 00:14:08.169 --> 00:14:10.230 But there's one setting in the source material 00:14:10.230 --> 00:14:12.549 that stands out from all the rest. My absolute 00:14:12.549 --> 00:14:14.629 favorite part of the source material, the thing 00:14:14.629 --> 00:14:16.509 that made me genuinely laugh out loud when I 00:14:16.509 --> 00:14:19.649 read it, the setting called birthday mode. And 00:14:19.649 --> 00:14:22.769 in parentheses, it says baby globe. Right now, 00:14:22.789 --> 00:14:24.970 according to the text, it is set to zero, which 00:14:24.970 --> 00:14:28.360 means disabled. Birthday mode baby globe. It 00:14:28.360 --> 00:14:30.539 is a fascinating inclusion in the code. I can't 00:14:30.539 --> 00:14:32.399 stop picturing what a baby globe birthday mode 00:14:32.399 --> 00:14:34.500 actually looks like. Is it the standard puzzle 00:14:34.500 --> 00:14:36.860 piece globe logo, but it's wearing a tiny party 00:14:36.860 --> 00:14:39.779 hat? That would be amazing. Does it have a pacifier? 00:14:40.059 --> 00:14:42.440 Are there digital balloons floating across the 00:14:42.440 --> 00:14:45.830 404 page? What is happening? While the source 00:14:45.830 --> 00:14:48.429 doesn't explicitly describe what happens visually 00:14:48.429 --> 00:14:50.529 when you toggle that setting from zero to one, 00:14:50.710 --> 00:14:53.049 the sheer fact that it exists tells you something 00:14:53.049 --> 00:14:55.590 vital about the culture of the developers. Yeah, 00:14:55.649 --> 00:14:58.870 it does. This is an open source, highly bureaucratic, 00:14:58.909 --> 00:15:02.070 rigorously academic database with strict deletion 00:15:02.070 --> 00:15:04.649 logs and auto -confirmed hierarchies. And yet, 00:15:04.809 --> 00:15:08.169 there is a toggle switch for a baby globe. There 00:15:08.169 --> 00:15:11.549 is whimsy embedded directly into the code. It 00:15:11.549 --> 00:15:14.070 completely humanizes the platform. You're dealing 00:15:14.070 --> 00:15:16.590 with strict rules and database purges, and then 00:15:16.590 --> 00:15:19.230 suddenly, baby globe. It reminds you that coders 00:15:19.230 --> 00:15:21.389 have a sense of humor. But right beneath that 00:15:21.389 --> 00:15:24.009 whimsy, at the very bottom of the page, we hit 00:15:24.009 --> 00:15:26.009 the ground again. We hit the fine print. The 00:15:26.009 --> 00:15:28.419 hidden scaffolding. Every single page on this 00:15:28.419 --> 00:15:30.720 platform, even a page that results in an error, 00:15:30.840 --> 00:15:33.460 is propped up by a massive legal and ethical 00:15:33.460 --> 00:15:36.120 framework. The source lists them out at the footer. 00:15:36.179 --> 00:15:40.059 You've got privacy policy, about Wikipedia, disclaimers, 00:15:40.159 --> 00:15:42.480 contact Wikipedia, legal and safety contacts, 00:15:42.720 --> 00:15:45.399 code of conduct, developers, statistics, cookie 00:15:45.399 --> 00:15:48.019 statement, and mobile view. Think about what 00:15:48.019 --> 00:15:51.100 this list represents. It is the invisible constitution 00:15:51.100 --> 00:15:54.500 of the site. You cannot have a crowdsourced open 00:15:54.500 --> 00:15:57.580 access ecosystem without a strict code of conduct 00:15:57.580 --> 00:16:00.480 and dedicated legal contacts. It's the gravity 00:16:00.480 --> 00:16:03.019 keeping the whole Sister Project universe from 00:16:03.019 --> 00:16:05.799 flying apart into absolute chaos. Precisely. 00:16:05.799 --> 00:16:08.460 A collaborative utopia requires traditional legal 00:16:08.460 --> 00:16:10.879 boundaries to function in the real world. And 00:16:10.879 --> 00:16:13.460 there's one final, slightly melancholic detail 00:16:13.460 --> 00:16:16.460 about this specific missing page. Under the add 00:16:16.460 --> 00:16:19.080 languages section, the source states, page content's 00:16:19.080 --> 00:16:21.480 not supported in other languages. Wow. It's not 00:16:21.480 --> 00:16:23.340 just... missing in English. It's unsupported 00:16:23.340 --> 00:16:26.299 globally. It's a universal void. Which brings 00:16:26.299 --> 00:16:28.480 us to the end of our journey today. Let's do 00:16:28.480 --> 00:16:30.799 a quick recap of what we've unpacked here. What 00:16:30.799 --> 00:16:33.240 started as a simple assumed dead end, a missing 00:16:33.240 --> 00:16:35.639 entry for the name Mary Frances, turned into 00:16:35.639 --> 00:16:38.019 a masterclass on the internet's largest repository 00:16:38.019 --> 00:16:40.600 of knowledge. We looked at the exact wording 00:16:40.600 --> 00:16:42.980 of the absence and how it instantly pivots to 00:16:42.980 --> 00:16:45.840 troubleshooting. We explored database quirks 00:16:45.840 --> 00:16:48.340 like case sensitivity and the mysterious purge 00:16:48.340 --> 00:16:50.600 function, realizing that the internet is still 00:16:50.600 --> 00:16:52.860 just a series of physical servers subject to 00:16:52.860 --> 00:16:55.179 delays. We uncovered the hidden bureaucracy, 00:16:55.519 --> 00:16:58.519 the auto -confirmed gatekeepers, the probationary 00:16:58.519 --> 00:17:01.320 periods, and the article wizard standing between 00:17:01.320 --> 00:17:23.849 a user and a published page. It fundamentally 00:17:23.849 --> 00:17:30.769 changes how you look at an error page. It is 00:17:30.769 --> 00:17:32.930 not a closed door. It is a map of the entire 00:17:32.930 --> 00:17:35.920 building. And that leaves us with a final lingering 00:17:35.920 --> 00:17:37.880 question based purely on the text we've read 00:17:37.880 --> 00:17:39.819 today. The site tells us that the page might 00:17:39.819 --> 00:17:42.319 be missing simply due to case sensitivity. It 00:17:42.319 --> 00:17:44.480 tells us there might just be a database delay 00:17:44.480 --> 00:17:47.440 requiring a cache purge. It tells us it might 00:17:47.440 --> 00:17:49.900 just be lacking an autoconfirmed user to write 00:17:49.900 --> 00:17:52.339 it. So what's the ultimate question here? This 00:17:52.339 --> 00:17:54.519 raises an important question for you, the listener. 00:17:54.720 --> 00:17:57.420 Does the absence of Mary Frances represent a 00:17:57.420 --> 00:18:01.039 true, actual void in human knowledge? Or is it 00:18:01.039 --> 00:18:03.319 simply a draft waiting for you to open the article 00:18:03.319 --> 00:18:06.019 wizard and submit it for review? Now that is 00:18:06.019 --> 00:18:08.220 something to mull over next time you hit a 4014 00:18:08.220 --> 00:18:10.700 page. Thank you for joining us on this deep dive. 00:18:10.839 --> 00:18:13.359 Keep asking questions. Keep looking at the negative 00:18:13.359 --> 00:18:15.519 space. And we will see you next time.