WEBVTT 00:00:00.000 --> 00:00:02.759 Imagine you walk into, like, the biggest, most 00:00:02.759 --> 00:00:05.200 comprehensive library in human history. Okay, 00:00:05.419 --> 00:00:07.759 set in the scene, I like it. Right. And you march 00:00:07.759 --> 00:00:10.539 straight up to the central index, you pull out 00:00:10.539 --> 00:00:12.919 the card for the exact obscure topic you want 00:00:12.919 --> 00:00:15.660 to learn about, and you follow the map deep into 00:00:15.660 --> 00:00:17.699 the winding stacks. But let me guess, the book 00:00:17.699 --> 00:00:20.219 isn't there. It's not there. When you finally 00:00:20.219 --> 00:00:22.879 arrive at the specific shelf, it's entirely empty. 00:00:23.039 --> 00:00:26.000 Just a completely blank physical space where, 00:00:26.000 --> 00:00:28.480 you know, the sum total of that knowledge was 00:00:28.480 --> 00:00:31.839 supposed to be... resting. Exactly. But instead 00:00:31.839 --> 00:00:34.020 of just leaving you staring at the dust, there 00:00:34.020 --> 00:00:37.600 is this highly detailed, incredibly complex set 00:00:37.600 --> 00:00:40.679 of instructions taped right to that empty shelf. 00:00:40.719 --> 00:00:44.280 Oh wow! And those instructions tell you precisely 00:00:44.280 --> 00:00:47.060 why the book isn't there, where else in the universe 00:00:47.060 --> 00:00:50.320 it might be hiding, and the bureaucratic steps 00:00:50.320 --> 00:00:52.420 required for you to actually write the book yourself. 00:00:52.679 --> 00:00:54.640 I mean, it's basically the architecture of a 00:00:54.640 --> 00:00:57.119 void. And honestly, the shape of that empty space 00:00:57.119 --> 00:00:59.320 tells us so much more about how the library functions 00:00:59.320 --> 00:01:01.689 than the book itself probably would have. That 00:01:01.689 --> 00:01:04.329 is exactly the journey we are taking today. So 00:01:04.329 --> 00:01:06.390 when you sent us your source document for this 00:01:06.390 --> 00:01:08.569 deep dive, you asked us to look into someone 00:01:08.569 --> 00:01:11.090 named Steady Ed Hedrick. Right. But there is 00:01:11.090 --> 00:01:14.909 a massive twist to the text you provided. The 00:01:14.909 --> 00:01:18.170 document you sent us contains absolutely zero 00:01:18.170 --> 00:01:20.409 biographical information about the man. Like 00:01:20.409 --> 00:01:24.170 none at all. None. Instead, you sent us the exact 00:01:24.170 --> 00:01:27.730 raw text of a Wikipedia article not found page. 00:01:28.109 --> 00:01:30.989 Which honestly is such a brilliant pivot for 00:01:30.989 --> 00:01:33.950 us to explore? You think so? Oh, totally. Because 00:01:33.950 --> 00:01:35.829 instead of hitting a frustrating dead end, we 00:01:35.829 --> 00:01:38.849 are getting a really rare behind the scenes look 00:01:38.849 --> 00:01:41.269 at the scaffolding of the internet's biggest 00:01:41.269 --> 00:01:43.049 encyclopedia. Yeah, that makes sense. Like when 00:01:43.049 --> 00:01:45.049 you look closely at an error page, you aren't 00:01:45.049 --> 00:01:47.909 just seeing a mistake. You are seeing the rigid 00:01:47.909 --> 00:01:51.510 rules of the system temporarily exposed. It's 00:01:51.510 --> 00:01:55.430 like seeing the underlying matrix of how we categorize 00:01:55.430 --> 00:01:57.969 human knowledge. I love that. So our mission 00:01:57.969 --> 00:02:00.439 for this deep dive is to explore. the anatomy 00:02:00.439 --> 00:02:03.540 of this digital empty space. Let's do it. We 00:02:03.540 --> 00:02:06.859 are going to examine what this platform's specific 00:02:06.859 --> 00:02:10.340 UI, its error messages, and its navigation menus 00:02:10.340 --> 00:02:13.520 actually reveal about how crowdsourced knowledge 00:02:13.520 --> 00:02:16.699 is structured, maintained, and sometimes incredibly 00:02:16.699 --> 00:02:18.539 delayed. It's a lot more complex than people 00:02:18.539 --> 00:02:20.860 think. It really is. So let's start with the 00:02:20.860 --> 00:02:22.439 blunt reality right at the top of the document 00:02:22.439 --> 00:02:25.680 you sent. The primary message the platform delivers 00:02:25.680 --> 00:02:29.039 is, quote, Wikipedia does not have an article 00:02:29.039 --> 00:02:31.479 with this exact name. Notice the phrasing there. 00:02:31.659 --> 00:02:34.039 Right. It doesn't say, this person doesn't exist. 00:02:34.379 --> 00:02:36.699 It just says, we don't have this specific string 00:02:36.699 --> 00:02:40.020 of text. Exactly. And then it gives you, the 00:02:40.020 --> 00:02:42.319 user, this fascinating piece of advice about 00:02:42.319 --> 00:02:45.219 its search mechanics. It warns that titles are 00:02:45.219 --> 00:02:47.259 case sensitive except for the first character. 00:02:47.479 --> 00:02:50.319 Yeah. And that specific detail reveals the rigid 00:02:50.319 --> 00:02:52.780 mathematical nature of digital filing systems. 00:02:52.840 --> 00:02:56.159 How so? Well, to a human brain, steady ed with 00:02:56.159 --> 00:02:58.979 a lowercase e and steady ed with an uppercase 00:02:58.979 --> 00:03:01.139 e mean the exact same thing, right? We parse 00:03:01.139 --> 00:03:03.699 the semantic meaning effortlessly. Right. If 00:03:03.699 --> 00:03:06.060 you pass me a note with bad capitalization, I 00:03:06.060 --> 00:03:07.699 still know exactly who you were talking about. 00:03:07.960 --> 00:03:11.439 Totally. But to a massive database architecture, 00:03:11.639 --> 00:03:14.439 those are entirely different entities. Oh, wow. 00:03:14.580 --> 00:03:17.180 Really? Yeah. Under the hood, Computers don't 00:03:17.180 --> 00:03:19.400 read letters. They read characters as binary 00:03:19.400 --> 00:03:22.520 numbers, specifically ASCII codes. OK, I remember 00:03:22.520 --> 00:03:25.060 hearing about ASCII. Right. So an uppercase E 00:03:25.060 --> 00:03:27.919 and a lowercase E are literally different numerical 00:03:27.919 --> 00:03:31.560 values. So if a database is strictly case sensitive, 00:03:32.139 --> 00:03:34.199 searching for the wrong capitalization isn't 00:03:34.199 --> 00:03:36.520 just a typo. It's a totally different search. 00:03:36.740 --> 00:03:39.419 Exactly. To the machine, it is like searching 00:03:39.419 --> 00:03:41.900 for a completely different species of animal. 00:03:42.400 --> 00:03:45.180 That feels incredibly unforgiving. I mean, let's 00:03:45.180 --> 00:03:48.199 unpack this. It's like looking up a name in a 00:03:48.199 --> 00:03:51.400 massive ancient phone book. But the librarian 00:03:51.400 --> 00:03:53.520 tells you that capitalizing the wrong letter 00:03:53.520 --> 00:03:56.360 halfway through the name effectively banishes 00:03:56.360 --> 00:03:58.460 that person to a parallel universe. That's a 00:03:58.460 --> 00:04:00.240 great way to put it. They just cease to exist 00:04:00.240 --> 00:04:02.439 in your search. But wait, if it's so strict, 00:04:02.620 --> 00:04:04.819 why does the page say, except for the first character? 00:04:05.039 --> 00:04:08.379 Oh, that exception is a brilliant necessary compromise 00:04:08.379 --> 00:04:11.139 between messy human behavior and strict machine 00:04:11.139 --> 00:04:14.680 logic. OK, how so? Well, humans almost instinctively 00:04:14.680 --> 00:04:16.860 capitalize the first letter of a search term, 00:04:17.199 --> 00:04:19.290 whether they mean to or not. It's just how we 00:04:19.290 --> 00:04:22.449 type. True, yeah. And more importantly, web browsers 00:04:22.449 --> 00:04:25.029 automatically capitalize the first letter of 00:04:25.029 --> 00:04:28.209 a URL pathway for structural consistency. Oh, 00:04:28.209 --> 00:04:30.790 I didn't know that. Yeah. So by making only that 00:04:30.790 --> 00:04:33.810 very first character case insensitive, the system 00:04:33.810 --> 00:04:36.910 forgives our single most common formatting habit. 00:04:37.009 --> 00:04:39.689 Oh, that's smart. Right. While still maintaining 00:04:39.689 --> 00:04:42.269 the lightning fast sorting capability that a 00:04:42.269 --> 00:04:44.949 database of millions of articles actually requires. 00:04:45.089 --> 00:04:47.509 I have to wonder, though, does this strict case 00:04:47.509 --> 00:04:50.829 sensitive actually make knowledge more precise? 00:04:51.470 --> 00:04:53.410 Or does it just make it significantly harder 00:04:53.410 --> 00:04:55.230 for you and me to find what we're looking for? 00:04:55.329 --> 00:04:57.389 That's the big question. Like, if the database 00:04:57.389 --> 00:04:59.870 is so powerful, why can't it just guess our intent? 00:05:00.170 --> 00:05:03.370 It is a deliberate trade -off, really. It prioritizes 00:05:03.370 --> 00:05:06.230 precision over intuition. Think about it. If 00:05:06.230 --> 00:05:08.410 you are trying to distinguish between the iconic 00:05:08.410 --> 00:05:11.209 80s band, the... Yeah, great band. Right. If 00:05:11.209 --> 00:05:13.329 you're distinguishing them and the standard English 00:05:13.329 --> 00:05:17.029 word, the... Case sensitivity is the only reliable 00:05:17.029 --> 00:05:19.410 way a machine can tell them apart without reading 00:05:19.410 --> 00:05:21.569 the entire context of the article. Oh, that makes 00:05:21.569 --> 00:05:24.110 total sense. It forces the user to speak the 00:05:24.110 --> 00:05:26.009 database's language rather than the database 00:05:26.009 --> 00:05:28.329 burning vastly more computational power trying 00:05:28.329 --> 00:05:31.889 to guess human nuance. Okay, so we failed the 00:05:31.889 --> 00:05:35.509 primary search because we didn't speak the machine's 00:05:35.509 --> 00:05:38.589 language perfectly or the page just plain doesn't 00:05:38.589 --> 00:05:41.089 exist. We hit the wall. Yeah. But the document 00:05:41.089 --> 00:05:43.819 you sent shows the page doesn't just stop and 00:05:43.819 --> 00:05:46.060 leave you hanging there. It immediately pivots. 00:05:46.300 --> 00:05:48.759 It really does. It offers this massive constellation 00:05:48.759 --> 00:05:52.420 of alternative databases. It lists like a dozen 00:05:52.420 --> 00:05:54.639 sister projects you can check on a debt. This 00:05:54.639 --> 00:05:57.620 list is an absolute masterclass in how we have 00:05:57.620 --> 00:06:00.000 decided to compartmentalize knowledge in the 00:06:00.000 --> 00:06:02.500 digital age. I want to read this list to you 00:06:02.500 --> 00:06:04.879 because seeing it all laid out is just staggering. 00:06:05.079 --> 00:06:07.980 Go for it. So it tells you to go look for steady 00:06:07.980 --> 00:06:10.600 Ed Hedrick on Wiktionary, which is the dictionary. 00:06:10.879 --> 00:06:14.980 Wiki books. for textbooks, WikiQuote for quotations, 00:06:15.519 --> 00:06:18.040 Wikisource, the library of primary texts. Which 00:06:18.040 --> 00:06:21.399 is huge on its own. Yeah. Then Wikiversity for 00:06:21.399 --> 00:06:24.639 learning resources, Commons for media and images, 00:06:25.360 --> 00:06:28.420 Wikivoyage, the travel guide, Wikinews, the news 00:06:28.420 --> 00:06:32.360 source, Wikidida, the linked database, and finally 00:06:32.360 --> 00:06:35.699 Wikispecies, the biological directory. It's exhausting 00:06:35.699 --> 00:06:37.839 just hearing it, but what's fascinating here 00:06:37.839 --> 00:06:40.939 is how it reveals the platform's underlying philosophy. 00:06:41.040 --> 00:06:43.060 Which is what? That not all information is created 00:06:43.060 --> 00:06:45.439 equal, and more importantly, not all information 00:06:45.439 --> 00:06:48.339 belongs in the same container. An encyclopedia 00:06:48.339 --> 00:06:51.779 article is fundamentally prose. It is a synthesized 00:06:51.779 --> 00:06:54.220 narrative summary of historical facts. That is 00:06:54.220 --> 00:06:56.139 a completely different format than Wikidata, 00:06:56.199 --> 00:06:58.040 for instance. I'm really glad you brought up 00:06:58.040 --> 00:06:59.680 Wikidata, because that one always confuses people. 00:07:00.000 --> 00:07:02.860 How is a linked database different from an encyclopedia? 00:07:03.290 --> 00:07:05.430 Think about the last time you asked your phone's 00:07:05.430 --> 00:07:07.949 voice assistant a trivia question, like, when 00:07:07.949 --> 00:07:10.610 was Ed Hedrick born? OK. Your phone doesn't want 00:07:10.610 --> 00:07:12.689 to read a five paragraph biographical narrative 00:07:12.689 --> 00:07:15.430 to find the answer. It wants a raw machine readable 00:07:15.430 --> 00:07:17.889 data point. Oh, right. It just needs the date. 00:07:18.350 --> 00:07:21.589 Exactly. Wikidata strips away all the pros and 00:07:21.589 --> 00:07:25.310 just stores the raw relationships. Name? Ed Hedrick. 00:07:25.490 --> 00:07:29.410 Birthdate. June 28, 1924. It is knowledge formatted 00:07:29.410 --> 00:07:32.439 exclusively for other machines to read. Here's 00:07:32.439 --> 00:07:37.000 where it gets really interesting to me. fracture 00:07:37.000 --> 00:07:39.800 human knowledge into so many highly specialized 00:07:39.800 --> 00:07:42.600 buckets. It's like going to a massive department 00:07:42.600 --> 00:07:45.259 store looking for a simple biography, and the 00:07:45.259 --> 00:07:47.060 greeter tells you to go check the hardware section, 00:07:47.259 --> 00:07:49.639 the travel agency, and the garden center, just 00:07:49.639 --> 00:07:52.360 in case. That's a funny visual. Right. Why not 00:07:52.360 --> 00:07:55.139 just put everything about a single topic on one 00:07:55.139 --> 00:07:57.319 massive scrolling page? Well, because mixing 00:07:57.319 --> 00:08:00.339 data types creates absolute editorial chaos. 00:08:00.459 --> 00:08:03.040 How so? If we connect this to the bigger picture 00:08:03.040 --> 00:08:05.120 of how information is maintained, you quickly 00:08:05.120 --> 00:08:07.410 realize that that a dictionary requires entirely 00:08:07.410 --> 00:08:10.410 different editorial rules than, say, a travel 00:08:10.410 --> 00:08:12.709 guide. OK, that's fair. A travel guide, like 00:08:12.709 --> 00:08:15.889 WikiVoyage, needs constant, almost daily updates. 00:08:16.350 --> 00:08:18.610 If a restaurant closes or a train route changes, 00:08:19.170 --> 00:08:21.069 you need users to update that instantly. Yeah, 00:08:21.110 --> 00:08:23.310 it has to be immediate. But an encyclopedia, 00:08:23.509 --> 00:08:26.870 however, needs deep... peer -reviewed historical 00:08:26.870 --> 00:08:30.870 consensus. It moves slowly by design. I see. 00:08:31.110 --> 00:08:33.230 You can't use the same yardstick to measure a 00:08:33.230 --> 00:08:36.090 quick travel tip and a nuanced historical biography. 00:08:36.370 --> 00:08:38.389 Precisely. If you put them all in one bucket, 00:08:38.590 --> 00:08:41.190 the editorial standards would just collapse under 00:08:41.190 --> 00:08:43.610 the weight of trying to govern completely different 00:08:43.610 --> 00:08:46.769 types of truth. Wow. By siloing them, the platform 00:08:46.769 --> 00:08:49.649 protects the integrity of each specific type 00:08:49.649 --> 00:08:52.690 of knowledge. OK, so we see how strict the database 00:08:52.690 --> 00:08:55.730 is with text and how aggressive it categorizes 00:08:55.730 --> 00:08:58.360 different types of facts. But what blew my mind 00:08:58.360 --> 00:09:01.240 in the document you sent us is that this rigid 00:09:01.240 --> 00:09:04.519 control bleeds directly into the visual design 00:09:04.519 --> 00:09:07.179 of the page itself. Oh, this part is fascinating. 00:09:07.340 --> 00:09:09.159 It actually hijacks your screen's appearance. 00:09:09.559 --> 00:09:11.779 The source material details some highly specific 00:09:11.779 --> 00:09:13.919 visual parameters for this error page. Yeah, 00:09:13.940 --> 00:09:16.259 the UI toggles. Exactly. You have this appearance 00:09:16.259 --> 00:09:18.679 menu on the sidebar. It offers a width toggle, 00:09:18.980 --> 00:09:21.279 standard or wide. It offers text size options, 00:09:21.659 --> 00:09:24.379 small, standard, large. It even offers a color 00:09:24.379 --> 00:09:26.490 beta. letting you choose automatic, light, or 00:09:26.490 --> 00:09:29.549 dark mode. Which, on the surface, implies a highly 00:09:29.549 --> 00:09:31.909 customizable, user -friendly environment. It 00:09:31.909 --> 00:09:35.750 does. And it even has this incredibly mysterious 00:09:35.750 --> 00:09:39.110 feature listed as birthday mode, baby globe, 00:09:39.690 --> 00:09:42.289 which is currently marked as disabled. I absolutely 00:09:42.289 --> 00:09:45.049 love that detail. It's so weird. It is such a 00:09:45.049 --> 00:09:48.110 wonderfully strange artifact of the platform's 00:09:48.110 --> 00:09:51.149 underlying code. Like, a birthday mode implies 00:09:51.149 --> 00:09:54.490 some sort of celebratory user interface overlay. 00:09:54.759 --> 00:09:57.220 perhaps for an anniversary of the platform itself. 00:09:57.259 --> 00:09:59.639 Yeah, like digital confetti or something. Exactly. 00:10:00.080 --> 00:10:02.379 But here it is, sitting disabled on a sterile 00:10:02.379 --> 00:10:04.820 error page, like a crumpled party favor left 00:10:04.820 --> 00:10:07.460 behind in a drab filing cabinet. It's hilarious. 00:10:08.000 --> 00:10:10.379 But here is the truly crazy part. Lay it on me. 00:10:10.720 --> 00:10:13.159 Right under these customizable options for text 00:10:13.159 --> 00:10:16.000 size and color, the document explicitly notes 00:10:16.000 --> 00:10:18.779 two force limitations. Oh, right. It says, this 00:10:18.779 --> 00:10:21.879 page always uses small font size, and this page 00:10:21.879 --> 00:10:24.450 is always in light mode. It's white. It literally 00:10:24.450 --> 00:10:26.669 provides you with a menu to change the look of 00:10:26.669 --> 00:10:29.230 the site and then completely overrides your choice. 00:10:29.429 --> 00:10:30.970 This raises a really important question about 00:10:30.970 --> 00:10:33.169 the psychology of user interface design. Yeah, 00:10:33.169 --> 00:10:35.990 why do that? Why would an error page deliberately 00:10:35.990 --> 00:10:39.370 lock you into specific visual constraints despite 00:10:39.370 --> 00:10:42.649 having the architecture built in for user customization? 00:10:43.149 --> 00:10:45.789 It feels like a total contradiction. Yeah. Is 00:10:45.789 --> 00:10:48.210 this intentional psychological design? I think 00:10:48.210 --> 00:10:50.779 it has to be. Because when you were reading a 00:10:50.779 --> 00:10:54.139 normal article, you might want dark mode to reduce 00:10:54.139 --> 00:10:56.580 eye strain so you can read comfortably for an 00:10:56.580 --> 00:11:00.019 hour. Exactly. But locking this error page in 00:11:00.019 --> 00:11:03.340 a sterile, bright light mode feels like flipping 00:11:03.340 --> 00:11:05.379 on the fluorescent lights in a hospital waiting 00:11:05.379 --> 00:11:08.659 room. That is the perfect analogy. Right. It 00:11:08.659 --> 00:11:10.919 subtly urges you to stop getting comfortable 00:11:10.919 --> 00:11:13.299 and either leave the room or fix the problem. 00:11:13.460 --> 00:11:15.100 I think you've hit on something crucial about 00:11:15.100 --> 00:11:17.879 how digital spaces manage our behavior. Yeah. 00:11:18.179 --> 00:11:20.240 When you are looking at an article, you are a 00:11:20.240 --> 00:11:23.019 consumer. You are meant to be relaxed. But an 00:11:23.019 --> 00:11:26.779 error page is not content. It is a system diagnostic. 00:11:26.899 --> 00:11:29.340 Oh, I like that distinction. It is the machine 00:11:29.340 --> 00:11:32.190 speaking directly to you, the user. By stripping 00:11:32.190 --> 00:11:34.230 away those comfort features and forcing small 00:11:34.230 --> 00:11:37.210 text in a bright light mode, the system is visually 00:11:37.210 --> 00:11:39.350 communicating. This is a sterile administrative 00:11:39.350 --> 00:11:42.809 space. Pay attention. It totally breaks the illusion. 00:11:43.190 --> 00:11:45.690 It snaps you out of your cozy reading environment 00:11:45.690 --> 00:11:48.669 and puts you in the harsh, brightly lit engine 00:11:48.669 --> 00:11:51.159 room of the website. It wants you alert. It needs 00:11:51.159 --> 00:11:53.639 you to read the technical instructions rather 00:11:53.639 --> 00:11:56.100 than just passively scrolling. And those technical 00:11:56.100 --> 00:11:58.620 instructions are incredibly demanding. Very much 00:11:58.620 --> 00:12:00.759 so. Which brings us to the contribute section 00:12:00.759 --> 00:12:03.659 of the page. You aren't just allowed to passively 00:12:03.659 --> 00:12:06.139 stare at the void. The page actively tells you 00:12:06.139 --> 00:12:08.799 how to fill it. Right. But the gatekeeping here 00:12:08.799 --> 00:12:12.320 is intense. To create the missing steady Ed Hedrick 00:12:12.320 --> 00:12:16.919 article, the text lays out very specific bureaucratic 00:12:16.919 --> 00:12:18.860 hurdles. Yep, the hoops you have to jump through. 00:12:19.080 --> 00:12:21.059 First, you have to log in or create an account. 00:12:21.559 --> 00:12:24.559 And then, crucially, it says you must be auto 00:12:24.559 --> 00:12:27.309 -confirmed. to create new articles. Which is 00:12:27.309 --> 00:12:30.470 a huge barrier for a casual user. Totally. Otherwise 00:12:30.470 --> 00:12:31.789 you have to use something called the article 00:12:31.789 --> 00:12:35.210 wizard to submit a draft for review or formally 00:12:35.210 --> 00:12:36.769 request that someone else write the article. 00:12:36.950 --> 00:12:39.009 This is where we see the ultimate tension in 00:12:39.009 --> 00:12:41.990 crowdsource knowledge. How so? The platform famously 00:12:41.990 --> 00:12:44.870 brands itself as the free encyclopedia that anyone 00:12:44.870 --> 00:12:47.029 can edit. Right, that's their whole thing. But 00:12:47.029 --> 00:12:49.950 the reality of maintaining that freedom requires 00:12:49.950 --> 00:12:53.259 hidden robust layers of bureaucracy. So what 00:12:53.259 --> 00:12:55.299 does this all mean for the average person? I 00:12:55.299 --> 00:12:57.720 mean, it's like being handed a hammer and told 00:12:57.720 --> 00:12:59.779 you can help build a massive community center. 00:12:59.879 --> 00:13:01.860 But first you have to sit in the contractor's 00:13:01.860 --> 00:13:04.460 office until they decide you're trustworthy enough 00:13:04.460 --> 00:13:06.679 to actually swing it. That's exactly what it's 00:13:06.679 --> 00:13:09.600 like. What exactly is this auto -confirmed status 00:13:09.600 --> 00:13:12.200 anyway? Well, auto -confirmed is essentially 00:13:12.200 --> 00:13:15.679 a digital trust metric. In the very early days 00:13:15.679 --> 00:13:17.980 of the internet, anyone could create a webpage 00:13:17.980 --> 00:13:21.179 instantly, completely anonymously. The Wild West 00:13:21.179 --> 00:13:24.360 days. Exactly. But as the platform grew, that 00:13:24.360 --> 00:13:27.279 open door policy led to massive waves of spam, 00:13:27.559 --> 00:13:30.200 malicious vandalism, and the creation of millions 00:13:30.200 --> 00:13:33.299 of junk pages by automated bots. Oh, right. The 00:13:33.299 --> 00:13:36.240 bots ruin everything. They really do. So to protect 00:13:36.240 --> 00:13:38.100 the database from collapsing under the weight 00:13:38.100 --> 00:13:41.700 of digital garbage, the system instituted this 00:13:41.700 --> 00:13:43.840 invisible threshold. And what is the threshold? 00:13:44.309 --> 00:13:46.149 Generally, you have to have an account for a 00:13:46.149 --> 00:13:48.350 certain number of days and have made a certain 00:13:48.350 --> 00:13:51.610 number of minor non -destructive edits before 00:13:51.610 --> 00:13:53.809 the system automatically upgrades your status 00:13:53.809 --> 00:13:56.730 to honored and firmed. Oh, I see. It is a test 00:13:56.730 --> 00:13:59.129 to prove you are a human being who is acting 00:13:59.129 --> 00:14:01.789 in good faith. I understand the defense mechanism, 00:14:01.870 --> 00:14:03.789 but let me push back on the reality of this. 00:14:03.889 --> 00:14:06.090 Sure, go ahead. Think about the friction of having 00:14:06.090 --> 00:14:09.250 to prove you're human online. We all hate doing 00:14:09.250 --> 00:14:11.690 those TCHA tests where you have to click on all 00:14:11.690 --> 00:14:13.769 the traffic lights. Oh, they're the worst. Wasn't 00:14:13.769 --> 00:14:16.070 this heavy requirement to use an article wizard 00:14:16.070 --> 00:14:19.889 or wait days to become auto -confirmed? Intimidate? 00:14:20.110 --> 00:14:23.029 the very people who might actually hold the missing 00:14:23.029 --> 00:14:25.350 knowledge? That's a very valid concern. Like 00:14:25.350 --> 00:14:28.230 what if the world's leading 80 -year -old expert 00:14:28.230 --> 00:14:30.970 on steady Ed Hedrick finally decides to share 00:14:30.970 --> 00:14:34.049 their life's work but they hit this wall of technical 00:14:34.049 --> 00:14:37.169 bureaucracy and just give up? It is a profound 00:14:37.169 --> 00:14:40.029 risk and it is the central dilemma of open source 00:14:40.029 --> 00:14:43.250 architecture. Every single hurdle you add to 00:14:43.250 --> 00:14:45.990 prevent a bad actor simultaneously discourages 00:14:45.990 --> 00:14:48.690 a good actor. The article wizard is meant to 00:14:48.690 --> 00:14:51.289 be the compromise here. How does that work? It 00:14:51.289 --> 00:14:54.690 guides unconfirmed users through a heavily structured 00:14:54.690 --> 00:14:57.830 form to ensure they provide citations and maintain 00:14:57.830 --> 00:15:00.629 a neutral tone. Oh, so it holds their hand a 00:15:00.629 --> 00:15:03.769 bit. Yes, but it still puts their draft in a 00:15:03.769 --> 00:15:06.450 slow moving queue to be manually reviewed by 00:15:06.450 --> 00:15:08.490 experienced editors. So they still have to wait. 00:15:08.600 --> 00:15:11.600 They do. Ultimately, the platform has decided 00:15:11.600 --> 00:15:14.500 that a slower, more frustrating creation process 00:15:14.500 --> 00:15:17.559 is a worthwhile price to pay to ensure the repository 00:15:17.559 --> 00:15:20.519 remains accurate and reliable. It's prioritizing 00:15:20.519 --> 00:15:23.600 defense over speed. It assumes the human user 00:15:23.600 --> 00:15:26.340 is the risky variable. Precisely. Which brings 00:15:26.340 --> 00:15:29.519 us perfectly to a section of your source document 00:15:29.519 --> 00:15:32.399 that assumes the human isn't the problem at all. 00:15:32.639 --> 00:15:35.480 Oh yes, the technical side. Sometimes the machine 00:15:35.480 --> 00:15:37.759 itself struggles to keep up. The final section 00:15:37.759 --> 00:15:40.690 is titled Other reasons this message may be displayed, 00:15:41.350 --> 00:15:44.009 and it outlines the hidden mechanical realities 00:15:44.009 --> 00:15:46.309 of the servers. This is where we finally confront 00:15:46.309 --> 00:15:49.210 the illusion of the instantaneous internet. Yes. 00:15:49.750 --> 00:15:52.909 The page explicitly warns that if a new article 00:15:52.909 --> 00:15:55.789 was recently created, it might not be visible 00:15:55.789 --> 00:15:58.870 yet because of a delay in updating the database. 00:15:59.169 --> 00:16:01.610 It's just a slight hiccup in the matrix. It literally 00:16:01.610 --> 00:16:04.269 tells you, the user, to wait a few minutes or 00:16:04.269 --> 00:16:07.090 try the purge function. And if that doesn't work, 00:16:07.240 --> 00:16:10.159 It suggests checking the deletion log to see 00:16:10.159 --> 00:16:12.399 why the page might have been erased. We are so 00:16:12.399 --> 00:16:14.740 accustomed to thinking of the digital world as 00:16:14.740 --> 00:16:17.519 a permanent, real -time reflection of reality. 00:16:17.659 --> 00:16:19.960 We really are. You click a button and you expect 00:16:19.960 --> 00:16:22.440 the universe to... instantly reorganize itself. 00:16:23.100 --> 00:16:25.899 Exactly. But terms like database delay and purge 00:16:25.899 --> 00:16:28.100 function peel back the curtain. They remind us 00:16:28.100 --> 00:16:30.759 that the internet is a physical thing. It is 00:16:30.759 --> 00:16:32.940 composed of thousands of spinning hard drives, 00:16:33.299 --> 00:16:36.500 miles of fiber optic cables, and massive server 00:16:36.500 --> 00:16:38.980 farms syncing data across continents. I just 00:16:38.980 --> 00:16:40.940 love the dramatic terminology here. It is pretty 00:16:40.940 --> 00:16:43.240 intense. The purge function. It sounds like something 00:16:43.240 --> 00:16:44.840 out of a sci -fi movie where you had to vent 00:16:44.840 --> 00:16:47.419 the reactor core before the ship explodes. Right, 00:16:47.419 --> 00:16:49.159 it does. What is the purge function actually 00:16:49.159 --> 00:16:52.600 doing in this context? text. When you view a 00:16:52.600 --> 00:16:55.600 heavily trafficked web page, you usually aren't 00:16:55.600 --> 00:16:58.840 pulling data directly from the live master database. 00:16:59.039 --> 00:17:01.139 OK, why not? Because that would overwhelm the 00:17:01.139 --> 00:17:04.599 system. Instead, you are seeing a cached version, 00:17:04.940 --> 00:17:08.599 a temporary static snapshot saved by a server 00:17:08.599 --> 00:17:11.319 physically closer to your geographic location 00:17:11.319 --> 00:17:13.920 to make the page load faster on your screen. 00:17:14.099 --> 00:17:15.980 Oh, that makes sense. It's like a photocopy of 00:17:15.980 --> 00:17:18.000 the real thing. Exactly. If an article was just 00:17:18.000 --> 00:17:20.680 created seconds ago, that local snapshot has 00:17:20.650 --> 00:17:23.809 updated yet to reflect the change. So the purge 00:17:23.809 --> 00:17:26.569 function is a manual command that forces the 00:17:26.569 --> 00:17:29.109 server to throw away its old snapshot and fetch 00:17:29.109 --> 00:17:32.089 the absolute latest live version from the master 00:17:32.089 --> 00:17:34.190 database. That implies something really wild. 00:17:34.309 --> 00:17:36.710 What's that? We expect the internet to be perfectly 00:17:36.710 --> 00:17:38.970 in sync with the present moment, but the very 00:17:38.970 --> 00:17:42.450 existence of a purge function means the platform 00:17:42.450 --> 00:17:44.930 sometimes gets stuck in the past. It totally 00:17:44.930 --> 00:17:47.170 does. Are we ever really seeing the most current 00:17:47.170 --> 00:17:49.619 version of digital history? Or are we always 00:17:49.619 --> 00:17:52.980 looking at a cached ghost? Wow. That is a beautiful 00:17:52.980 --> 00:17:56.369 way to frame it. A cached ghost. And if we connect 00:17:56.369 --> 00:18:00.470 this idea of ghosts to the deletion log mentioned 00:18:00.470 --> 00:18:03.109 in the text, it becomes even more literal. How 00:18:03.109 --> 00:18:06.109 so? Well, the deletion log proves that the void 00:18:06.109 --> 00:18:09.809 we are looking at might not be empty simply because 00:18:09.809 --> 00:18:12.589 no one ever cared about Steady Ed Hedrick. Right. 00:18:12.930 --> 00:18:14.930 It might be empty because someone did write the 00:18:14.930 --> 00:18:17.809 article, but a community of editors argued over 00:18:17.809 --> 00:18:20.450 it, decided it didn't meet their notability standards, 00:18:20.630 --> 00:18:22.990 and effectively erased it from the public eye. 00:18:23.069 --> 00:18:27.220 Oh, wow. isn't always virgin territory waiting 00:18:27.220 --> 00:18:29.259 to be discovered. Sometimes it's an excavated 00:18:29.259 --> 00:18:32.319 site. Exactly. The Deletion Log is a record of 00:18:32.319 --> 00:18:34.880 the invisible battles fought over what deserves 00:18:34.880 --> 00:18:37.200 to be remembered and what gets left behind. An 00:18:37.200 --> 00:18:39.900 excavated site. that totally reframes its entire 00:18:39.900 --> 00:18:41.960 document for me. It really changes your perspective, 00:18:42.000 --> 00:18:44.460 doesn't it? It does. We started this DeepDog 00:18:44.460 --> 00:18:46.539 trying to figure out who SteadyEdHedrick was, 00:18:47.160 --> 00:18:49.700 and while your source material left us with absolutely 00:18:49.700 --> 00:18:52.140 no idea about the man himself... None whatsoever. 00:18:52.359 --> 00:18:54.519 This missing search result offered us something 00:18:54.519 --> 00:18:57.420 arguably more profound. It gave us a complete 00:18:57.420 --> 00:18:59.779 naked blueprint of the Internet's most vital 00:18:59.779 --> 00:19:02.660 knowledge engine. We saw how the rigid mathematical 00:19:02.660 --> 00:19:05.720 rules of case sensitivity and ASCII codes dictate 00:19:05.720 --> 00:19:08.380 what the machine can even understand. We saw 00:19:08.380 --> 00:19:10.680 how human knowledge is fractured into highly 00:19:10.680 --> 00:19:13.180 specific sister projects, like the difference 00:19:13.180 --> 00:19:16.440 between an encyclopedia and the raw data of Wikidata, 00:19:16.720 --> 00:19:19.579 just to protect the integrity of the facts. And 00:19:19.579 --> 00:19:22.259 we looked at the rigid, sterile aesthetics of 00:19:22.259 --> 00:19:25.059 the error page itself. The way it offers you 00:19:25.059 --> 00:19:27.779 customizable dark mode, and then forces you into 00:19:27.779 --> 00:19:30.980 a bright light mode with small text, acting exactly 00:19:30.980 --> 00:19:33.380 like the harsh fluorescent lights of an interrogation 00:19:33.380 --> 00:19:36.279 room. We explored the necessary, sometimes frustrating, 00:19:36.420 --> 00:19:39.880 gatekeeping of being auto -concerned or using 00:19:39.880 --> 00:19:42.279 the article wizard just to swing the hammer of 00:19:42.279 --> 00:19:44.400 creation. And finally, we found those cached 00:19:44.400 --> 00:19:46.559 ghosts in the machine. Yeah, we did. The server 00:19:46.559 --> 00:19:49.059 delays, the dramatic purge functions, and the 00:19:49.059 --> 00:19:50.900 hidden deletion logs that prove the internet 00:19:50.900 --> 00:19:53.720 is a physical churning machine subject to traffic 00:19:53.720 --> 00:19:56.819 jams and editorial erasure. It turns out an empty 00:19:56.819 --> 00:19:58.819 shelf in the Library of Human Knowledge is one 00:19:58.819 --> 00:20:01.000 of the most structurally complex and heavily 00:20:01.000 --> 00:20:03.880 guarded places you can visit. It really is. And 00:20:03.880 --> 00:20:05.740 I want to leave you with one final thought to 00:20:05.740 --> 00:20:08.640 mull over after sending us this fascinating document. 00:20:08.740 --> 00:20:12.369 Let's hear it. Every single article on Wikipedia, 00:20:13.349 --> 00:20:16.029 every massive, heavily cited, sprawling page 00:20:16.029 --> 00:20:18.710 detailing the entirety of human history, every 00:20:18.710 --> 00:20:21.569 war, every scientific breakthrough, every biography 00:20:21.569 --> 00:20:25.210 of every world leader, started as the exact same 00:20:25.210 --> 00:20:27.710 blank lockdown, sterile void we just explored 00:20:27.710 --> 00:20:29.970 today. That's an incredible point. So the next 00:20:29.970 --> 00:20:32.309 time you encounter a digital error page, a 404 00:20:32.309 --> 00:20:34.549 or a not found message, ask yourself... Yeah. 00:20:34.720 --> 00:20:37.460 Is this just a frustrating dead end, or is it 00:20:37.460 --> 00:20:39.599 an invitation to become the architect of a space 00:20:39.599 --> 00:20:40.539 that doesn't yet exist?