WEBVTT 00:00:00.000 --> 00:00:04.299 Imagine walking into the world's largest, most 00:00:04.299 --> 00:00:06.639 comprehensive library. OK, I'm picturing it. 00:00:06.759 --> 00:00:09.099 Right. And you stride right up to the front desk, 00:00:09.859 --> 00:00:12.820 clear your throat, and ask for a very specific 00:00:12.820 --> 00:00:15.279 single file that you need for a project. And 00:00:15.279 --> 00:00:17.660 you expect them to just hand it over. Exactly. 00:00:18.179 --> 00:00:20.859 But the librarian looks at you, doesn't say a 00:00:20.859 --> 00:00:23.239 word, and instead hands you a completely blank 00:00:23.239 --> 00:00:27.000 sheet of paper. Oh, wow. Just blank. Just blank. 00:00:27.399 --> 00:00:30.079 But. And this is the crazy part. It's wrapped 00:00:30.079 --> 00:00:33.500 in a dense, highly technical instruction manual 00:00:33.500 --> 00:00:36.880 on how the library's entire filing system works. 00:00:37.079 --> 00:00:38.799 I mean, that would be incredibly jarring. You 00:00:38.799 --> 00:00:40.979 walked in expecting an answer, and you were handed 00:00:40.979 --> 00:00:43.939 a schematic of the building. Right, exactly. 00:00:44.500 --> 00:00:46.700 And for you listening, you're probably used to 00:00:46.700 --> 00:00:49.520 us dissecting massive, dense reports on this 00:00:49.520 --> 00:00:51.539 show. Yeah, usually we have hundreds of pages 00:00:51.539 --> 00:00:53.679 to go through. We do. So you might be looking 00:00:53.679 --> 00:00:56.259 at today's topic and thinking, wait. There's 00:00:56.259 --> 00:00:58.579 nothing here. Because there literally isn't. 00:00:58.600 --> 00:01:01.399 Right. We are doing a custom -tailored deep dive 00:01:01.399 --> 00:01:04.260 into a very specific subject for you today. The 00:01:04.260 --> 00:01:06.920 subject is the Solidarity Szczedek -Gulunio Airport 00:01:06.920 --> 00:01:10.140 in Poland. But the twist is we don't have an 00:01:10.140 --> 00:01:12.700 article detailing, you know, runway links or 00:01:12.700 --> 00:01:15.340 the history of Polish aviation. Or like passenger 00:01:15.340 --> 00:01:17.120 statistics or anything like that. Right. What 00:01:17.120 --> 00:01:19.959 we have is a digital dead end. It is the literal 00:01:19.959 --> 00:01:23.120 Wikipedia error page that appears when you search 00:01:23.120 --> 00:01:25.359 for that exact term. Yeah. The screen staring 00:01:25.359 --> 00:01:28.459 back at us simply says Wikipedia does not have 00:01:28.459 --> 00:01:31.340 an article with this exact name. That's it. Just 00:01:31.340 --> 00:01:34.760 a void. Just a void. But rather than just like 00:01:34.760 --> 00:01:37.219 closing the tab and giving up. we are going to 00:01:37.219 --> 00:01:40.659 extract the hidden architecture from this empty 00:01:40.659 --> 00:01:43.140 space. I love that, because as a learner, you 00:01:43.140 --> 00:01:45.200 know, you often learn so much more about the 00:01:45.200 --> 00:01:47.280 shape and limits of a system by looking at what 00:01:47.280 --> 00:01:49.799 it refuses to hold. Exactly. Rather than what 00:01:49.799 --> 00:01:52.379 it successfully contains, we're going to explore 00:01:52.379 --> 00:01:55.560 the invisible, rigid rules of the internet's 00:01:55.560 --> 00:01:58.099 biggest encyclopedia. Rules that really only 00:01:58.099 --> 00:02:00.040 reveal themselves when you go looking for something 00:02:00.040 --> 00:02:02.939 that just isn't there. Right. Okay, let's unpack 00:02:02.939 --> 00:02:04.599 this. We'll start with the rejection itself. 00:02:05.069 --> 00:02:07.829 The search query was solidarity, Sheech, and 00:02:07.829 --> 00:02:11.430 Galenio. And then in parentheses, the word airport. 00:02:11.750 --> 00:02:14.550 Notice those parentheses, yeah. Yeah. And the 00:02:14.550 --> 00:02:16.969 database responds with a very specific caveat. 00:02:17.430 --> 00:02:20.389 It doesn't just say, you know. Not found. No, 00:02:20.530 --> 00:02:22.210 it says it doesn't have an article with this 00:02:22.210 --> 00:02:25.289 exact name. Exact name. But wait, I mean, in 00:02:25.289 --> 00:02:29.310 an era of AI and autocorrect, isn't it kind of 00:02:29.310 --> 00:02:31.469 ridiculous that the world's biggest repository 00:02:31.469 --> 00:02:34.810 of human knowledge gets confused by like a stray 00:02:34.810 --> 00:02:37.729 parentheses or a hyphen? It seems that way, yeah. 00:02:37.909 --> 00:02:39.990 I mean, why is it so stubbornly rigid? Well, 00:02:40.069 --> 00:02:42.810 it's crucial to remember that a database isn't 00:02:42.810 --> 00:02:45.189 a sentient brain, right? It doesn't use context 00:02:45.189 --> 00:02:47.659 clues the way you or I do. Oh, right. Because 00:02:47.659 --> 00:02:49.199 we see the parentheses and think, oh, they're 00:02:49.199 --> 00:02:51.259 just clarifying what it is. Exactly. When we 00:02:51.259 --> 00:02:53.979 see the word airport inside parentheses, our 00:02:53.979 --> 00:02:56.539 human brain says, ah, they're clarifying the 00:02:56.539 --> 00:02:58.759 type of facility. Like, it's an airport, not 00:02:58.759 --> 00:03:01.219 a train station. Right. But to a database, you 00:03:01.219 --> 00:03:03.219 aren't providing context. You are submitting 00:03:03.219 --> 00:03:05.259 a mathematical string of characters. So it's 00:03:05.259 --> 00:03:07.479 taking me completely literally. Absolutely literal. 00:03:07.580 --> 00:03:10.099 It's binary. If you search for that airport, 00:03:10.199 --> 00:03:13.750 but you use say, a dash instead of a hyphen. 00:03:13.969 --> 00:03:16.330 Or if you forget the accent over the O in Golanio. 00:03:16.629 --> 00:03:19.289 Exactly. The database doesn't think you're asking 00:03:19.289 --> 00:03:21.330 for a slightly different version of the same 00:03:21.330 --> 00:03:23.669 thing. It just flat out rejects it. Yeah. To 00:03:23.669 --> 00:03:25.830 the machine, you are asking for something that 00:03:25.830 --> 00:03:27.969 fundamentally does not exist in its universe. 00:03:28.289 --> 00:03:31.650 Man, so it's forcing the human user to adapt 00:03:31.650 --> 00:03:35.150 to the machine's strict syntax rather than the 00:03:35.150 --> 00:03:37.759 machine adapting to my you know, sloppy typing. 00:03:37.979 --> 00:03:40.979 Which exposes the seam of the digital world, 00:03:41.120 --> 00:03:44.400 really. We are so used to modern search algorithms 00:03:44.400 --> 00:03:46.539 predicting our thoughts. Oh yeah, covering up 00:03:46.539 --> 00:03:49.780 our typos, spoon feeding us the most likely answer. 00:03:50.159 --> 00:03:53.099 Right, this specific error page strips away that 00:03:53.099 --> 00:03:55.400 comforting illusion of artificial intelligence. 00:03:55.819 --> 00:03:57.479 It reminds you that you are talking to a filing 00:03:57.479 --> 00:03:59.699 cabinet. And if you don't have the exact label 00:03:59.699 --> 00:04:02.599 on the folder, the drawer stays shut. the drawer 00:04:02.599 --> 00:04:04.879 stays completely shut. Okay, but the page doesn't 00:04:04.879 --> 00:04:06.840 just leave us stranded in that closed drawer 00:04:06.840 --> 00:04:08.939 reality, which is nice. It actually gives us 00:04:08.939 --> 00:04:11.800 a diagnostic toolkit. Yeah, right below the rejection 00:04:11.800 --> 00:04:14.759 there's a menu labeled, other reasons this message 00:04:14.759 --> 00:04:17.920 may be displayed. We essentially get a troubleshooting 00:04:17.920 --> 00:04:21.100 guide for the internet. And looking at the first 00:04:21.100 --> 00:04:24.600 step, I have to admit I am fascinated. It says 00:04:24.600 --> 00:04:29.019 the page might exist, but there could be a delay. 00:04:29.370 --> 00:04:31.689 in updating the database. Right, the database 00:04:31.689 --> 00:04:33.990 lag. It tells you to wait a few minutes or, and 00:04:33.990 --> 00:04:36.589 this is my favorite part, try the purge function. 00:04:37.209 --> 00:04:39.910 Ah, the purge function. Here's where it gets 00:04:39.910 --> 00:04:42.810 really interesting. It sounds incredibly dramatic. 00:04:43.149 --> 00:04:46.689 Like, Captain, the database is lagging. Initiate 00:04:46.689 --> 00:04:48.810 the purge function. It does sound like a sci 00:04:48.810 --> 00:04:50.709 -fi movie. What are we actually purging here? 00:04:50.750 --> 00:04:53.310 I mean, why would a digital encyclopedia have 00:04:53.310 --> 00:04:56.689 a lag? I type something, I hit enter, it should 00:04:56.689 --> 00:04:59.120 be there. Well, if we connect this to the bigger 00:04:59.120 --> 00:05:01.360 picture, you're bumping up against the physical 00:05:01.360 --> 00:05:03.879 reality of the internet. OK, the physical reality. 00:05:03.920 --> 00:05:06.279 Yeah, we treat the web like it's a magical weightless 00:05:06.279 --> 00:05:08.639 cloud, but it's not. Right. There are actual 00:05:08.639 --> 00:05:11.139 machines involved. Exactly. It's physical servers, 00:05:11.579 --> 00:05:14.319 miles of fiber optic cables, hard drives spinning 00:05:14.319 --> 00:05:16.319 in air -conditioned rooms all over the world. 00:05:16.579 --> 00:05:19.339 So when a new article is created, that data has 00:05:19.339 --> 00:05:22.420 to be propagated across a massive global network 00:05:22.420 --> 00:05:26.160 of servers. Oh, wow. So a delay in updating means 00:05:26.160 --> 00:05:29.279 the article on the Shichin Gilenyo Airport might 00:05:29.279 --> 00:05:32.060 literally be sitting in a digital waiting room 00:05:32.060 --> 00:05:34.540 somewhere. Pretty much. It might be written to 00:05:34.540 --> 00:05:37.019 the main database, but the server that is talking 00:05:37.019 --> 00:05:39.680 to your specific computer just hasn't caught 00:05:39.680 --> 00:05:41.560 up yet. And that's where the purge function comes 00:05:41.560 --> 00:05:44.139 in. Exactly. To understand the purge function, 00:05:44.199 --> 00:05:46.420 we have to talk about how caching works. Please 00:05:46.420 --> 00:05:48.259 do, because caching always sounds like something 00:05:48.259 --> 00:05:50.660 a squirrel does with nuts before winter. That's 00:05:50.660 --> 00:05:52.819 a great way to picture it, honestly. Think of 00:05:52.819 --> 00:05:55.939 it like a massive library. OK. The deep underground 00:05:55.939 --> 00:05:59.019 archives are the main database. But fetching 00:05:59.019 --> 00:06:01.240 books from the basement takes time. Nobody wants 00:06:01.240 --> 00:06:03.720 to wait for that. Right. So the librarian keeps 00:06:03.720 --> 00:06:06.699 the most popular recently requested books right 00:06:06.699 --> 00:06:09.959 on the front desk. That front desk is the cache. 00:06:10.279 --> 00:06:12.500 Oh, I see. It's temporary memory designed for 00:06:12.500 --> 00:06:16.500 speed. OK, that makes sense. Like, if... Millions 00:06:16.500 --> 00:06:18.279 of people are checking the page for a celebrity. 00:06:18.800 --> 00:06:20.360 The system doesn't want to go to the basement 00:06:20.360 --> 00:06:22.879 every single time. No, it just hands them the 00:06:22.879 --> 00:06:26.060 copy on the desk. Precisely. But what happens 00:06:26.060 --> 00:06:28.139 if the actual book in the basement gets updated? 00:06:28.680 --> 00:06:30.500 Like someone adds a new piece of information. 00:06:30.860 --> 00:06:33.120 Yeah. But the librarian is still handing out 00:06:33.120 --> 00:06:35.100 the old copy from the desk. Well, then the person 00:06:35.100 --> 00:06:38.100 gets outdated information. Right. So clicking 00:06:38.100 --> 00:06:40.600 the purge function is essentially you walking 00:06:40.600 --> 00:06:42.860 up to the librarian and saying, clear your desk. 00:06:43.050 --> 00:06:44.990 Throw away all the temporary copies. Throw them 00:06:44.990 --> 00:06:47.089 away. Go down in the basement and bring me the 00:06:47.089 --> 00:06:50.129 raw, absolute most recent truth from the main 00:06:50.129 --> 00:06:53.149 database. You are purging the cache. Man, that 00:06:53.149 --> 00:06:55.910 is deeply satisfying. It's a mechanical override 00:06:55.910 --> 00:06:59.310 for a digital bottleneck. It really is. But let's 00:06:59.310 --> 00:07:01.449 move down to the next troubleshooting step on 00:07:01.449 --> 00:07:04.009 this page because it introduces a rule that seems 00:07:04.009 --> 00:07:06.509 completely contradictory. The capitalization 00:07:06.509 --> 00:07:10.220 rule. Yes. It explicitly states... Titles on 00:07:10.220 --> 00:07:13.019 Wikipedia are case sensitive, except for the 00:07:13.019 --> 00:07:15.769 first character. It is a beautifully specific 00:07:15.769 --> 00:07:18.490 compromise. But why only the first character? 00:07:18.889 --> 00:07:21.069 Well... Like, looking at this rule, it means 00:07:21.069 --> 00:07:23.449 if I search for solidarity with the lowercase 00:07:23.449 --> 00:07:26.610 s, the database automatically bumps it up to 00:07:26.610 --> 00:07:28.930 a capital S. Right. It forgives you for that 00:07:28.930 --> 00:07:31.350 one single keystroke. But if I capitalize the 00:07:31.350 --> 00:07:34.129 G in Golenio differently, or lowercase the A 00:07:34.129 --> 00:07:37.009 in Airport, the whole search shatters. Completely 00:07:37.009 --> 00:07:39.610 falls apart. Why build a system that is, you 00:07:39.610 --> 00:07:43.470 know, 99 % rigid and 1 % forgiving? To understand 00:07:43.470 --> 00:07:45.870 that, you have to look at the programmer's dilemma. 00:07:46.110 --> 00:07:49.230 You have to understand how a computer reads letters. 00:07:49.329 --> 00:07:52.730 OK, lay it on me. To a human, a lowercase a and 00:07:52.730 --> 00:07:55.810 an uppercase a are the exact same concept, just 00:07:55.810 --> 00:07:58.230 with a different visual emphasis. Sure, a big 00:07:58.230 --> 00:07:59.850 A at the start of the sentence, a little one 00:07:59.850 --> 00:08:02.269 in the middle, same letter. But to a computer 00:08:02.269 --> 00:08:06.689 reading binary code, A lowercase a and an uppercase 00:08:06.689 --> 00:08:09.490 a are entirely different entities. Wait, really? 00:08:09.750 --> 00:08:11.730 Entirely different? Completely. They have completely 00:08:11.730 --> 00:08:14.129 different numerical values in the system's underlying 00:08:14.129 --> 00:08:16.769 code. They are as different to the computer as 00:08:16.769 --> 00:08:19.410 the number 4 and the symbol for a dollar sign. 00:08:19.670 --> 00:08:22.810 Oh, wow. Okay, so if a system is case -sensitive, 00:08:23.029 --> 00:08:25.889 it's not being stubborn. No, it's literally reading 00:08:25.889 --> 00:08:28.189 two completely different languages. That is wild. 00:08:28.250 --> 00:08:31.449 Exactly. But the architects of this database 00:08:31.449 --> 00:08:34.639 knew that humans are sloppy. We are very sloppy. 00:08:35.000 --> 00:08:36.960 We start sentences with capital letters out of 00:08:36.960 --> 00:08:39.600 habit, but we often type search queries in all 00:08:39.600 --> 00:08:42.379 lowercase because we are in a hurry. Right. Nobody 00:08:42.379 --> 00:08:45.340 uses the shift key when they're furiously googling 00:08:45.340 --> 00:08:47.940 something. Right. So if the database strictly 00:08:47.940 --> 00:08:50.720 enforced case sensitivity on the very first letter, 00:08:51.360 --> 00:08:53.820 millions of searches would fail every single 00:08:53.820 --> 00:08:55.840 day. Just because someone didn't hit the shift 00:08:55.840 --> 00:08:58.460 key. Yep. So they programmed a grid. So you programmed 00:08:58.460 --> 00:09:01.120 a grid. They did. That, except for the first 00:09:01.120 --> 00:09:04.139 character rule, is a massive, deliberate piece 00:09:04.139 --> 00:09:07.100 of programming labor. Like, they forced the machine 00:09:07.100 --> 00:09:09.519 to adapt, just a little bit. They forced the 00:09:09.519 --> 00:09:11.779 machine to say, OK, whatever binary con they 00:09:11.779 --> 00:09:14.480 put in the first slot, treat the uppercase and 00:09:14.480 --> 00:09:17.100 lowercase versions as identical. But why not 00:09:17.100 --> 00:09:18.860 do that for all the letters? Because to do that 00:09:18.860 --> 00:09:21.340 for every single letter in a 10 -word title would 00:09:21.340 --> 00:09:24.080 require massive computational power. Oh, and 00:09:24.080 --> 00:09:26.080 it would slow the whole system down. Exactly. 00:09:26.580 --> 00:09:29.879 So they give you grace on the first letter. After 00:09:29.879 --> 00:09:32.620 that, you are back in the rigid, unforgiving 00:09:32.620 --> 00:09:35.330 world of the machine. It's the exact boundary 00:09:35.330 --> 00:09:38.730 line where human intuition ends and database 00:09:38.730 --> 00:09:40.850 logic begins. That's a great way to put it. Okay, 00:09:40.870 --> 00:09:43.250 so we've purged the cache, we've meticulously 00:09:43.250 --> 00:09:45.429 checked our capitalization to appease the binary 00:09:45.429 --> 00:09:47.629 code, and the Solidarity, Schissing, and Gellinier 00:09:47.629 --> 00:09:50.750 airport page truly just doesn't exist. We've 00:09:50.750 --> 00:09:53.009 exhausted the diagnostics. Right. Now the text 00:09:53.009 --> 00:09:56.470 on our screen shifts from troubleshooting a failure 00:09:56.470 --> 00:09:59.360 to explaining the rules of creation. It tells 00:09:59.360 --> 00:10:01.720 us how to fill the void. This is where we run 00:10:01.720 --> 00:10:03.860 into the gatekeepers of knowledge. And it sounds 00:10:03.860 --> 00:10:06.100 surprisingly bureaucratic. It really does. It 00:10:06.100 --> 00:10:08.240 says you need to log in or create an account 00:10:08.240 --> 00:10:11.080 and be auto -confirmed to create new articles. 00:10:11.299 --> 00:10:13.539 Auto -confirmed? Yeah, auto -confirmed. And if 00:10:13.539 --> 00:10:15.700 you aren't, it says you have to go use the article 00:10:15.700 --> 00:10:18.580 wizard to submit a draft. Right, the wizard. 00:10:18.820 --> 00:10:21.200 I mean, I'm sorry, but doesn't this totally contradict 00:10:21.200 --> 00:10:24.000 the whole free encyclopedia that anyone can edit 00:10:24.000 --> 00:10:26.440 slogan? It feels like a contradiction, for sure. 00:10:26.620 --> 00:10:29.000 Why do I need a special auto -confirm status 00:10:29.000 --> 00:10:31.720 or have to consult a wizard just to write about 00:10:31.720 --> 00:10:35.240 a regional airport in Poland? It feels, I don't 00:10:35.240 --> 00:10:37.419 know, it feels kind of elitist. Well, this raises 00:10:37.419 --> 00:10:39.080 an important question about quality control. 00:10:39.159 --> 00:10:42.039 It's not elitism. It's a filtration system. Okay, 00:10:42.179 --> 00:10:44.200 a filtration system. Yeah, this touches on the 00:10:44.200 --> 00:10:46.220 fundamental tension at the heart of the open 00:10:46.220 --> 00:10:49.360 source internet. Right. The ideal is beautiful, 00:10:49.539 --> 00:10:53.019 right? Completely open access where human knowledge 00:10:53.019 --> 00:10:56.970 is freely shared by anyone instantly. But the 00:10:56.970 --> 00:10:59.590 reality... The reality is that a completely open, 00:10:59.889 --> 00:11:03.090 frictionless system is instantly destroyed. Destroyed 00:11:03.090 --> 00:11:06.610 by what? By vandalism, spam bots, and malicious 00:11:06.610 --> 00:11:09.570 actors. No, of course. Trolls. Exactly. If you 00:11:09.570 --> 00:11:11.850 could just arrive at this error page, click a 00:11:11.850 --> 00:11:13.389 button, and write whatever you wanted without 00:11:13.389 --> 00:11:15.830 logging in or proving who you are. I mean, within 00:11:15.830 --> 00:11:17.690 five minutes, someone would rewrite it to say 00:11:17.690 --> 00:11:19.649 the airport was built by aliens. Or it would 00:11:19.649 --> 00:11:21.889 be filled with links selling counterfeit sneakers. 00:11:22.009 --> 00:11:24.909 Right. It would be chaos. Precisely. So what 00:11:24.909 --> 00:11:27.360 you were seeing... This requirement to be auto 00:11:27.360 --> 00:11:30.320 -confirmed is the necessary friction built into 00:11:30.320 --> 00:11:33.080 the ecosystem to prevent that. It's a structured 00:11:33.080 --> 00:11:35.480 hierarchy of trust. Exactly. It protects the 00:11:35.480 --> 00:11:38.159 knowledge. So how does someone actually get that 00:11:38.159 --> 00:11:41.320 trust? I mean, is auto -confirm just some secret 00:11:41.320 --> 00:11:44.440 VIP club for internet nerds? Not at all. It's 00:11:44.440 --> 00:11:47.240 a meritocracy of patience. A meritocracy of patience. 00:11:47.240 --> 00:11:49.299 I like that. Usually it just means you've created 00:11:49.299 --> 00:11:51.419 an account, your account is at least a few days 00:11:51.419 --> 00:11:54.240 old, and you've made a small handful of basic, 00:11:54.519 --> 00:11:57.340 non -destructive edits to existing pages. Like 00:11:57.340 --> 00:11:59.899 fixing a typo somewhere else. Right. The system 00:11:59.899 --> 00:12:02.600 watches you, it verifies that you are a human 00:12:02.600 --> 00:12:04.860 being, and more importantly, a human being who 00:12:04.860 --> 00:12:06.980 isn't trying to bur - the library down? Okay, 00:12:07.059 --> 00:12:10.200 so once you clear that low bar, the system automatically 00:12:10.200 --> 00:12:13.059 elevates your status. You become auto -confirmed. 00:12:13.159 --> 00:12:15.659 And you unlock the ability to pour new concrete 00:12:15.659 --> 00:12:18.840 and build a completely new page. Exactly. But 00:12:18.840 --> 00:12:21.480 wait, what if I don't want to wait? Like if I 00:12:21.480 --> 00:12:23.440 have breaking news about this airport right now? 00:12:23.580 --> 00:12:26.240 That's why the article wizard exists. Oh, the 00:12:26.240 --> 00:12:29.330 wizards. Yes. You can write the draft, but it 00:12:29.330 --> 00:12:32.549 acts as a bottleneck. It forces your work into 00:12:32.549 --> 00:12:36.129 a queue where an actual experienced human editor 00:12:36.129 --> 00:12:38.529 has to review it before it goes live to the public. 00:12:39.549 --> 00:12:42.070 Ah. So even the void is heavily guarded. Very 00:12:42.070 --> 00:12:44.710 much so. You don't get to just walk in off the 00:12:44.710 --> 00:12:46.149 street and start putting up drywall. You have 00:12:46.149 --> 00:12:49.070 to earn the right to contribute. Right. But let's 00:12:49.070 --> 00:12:50.970 say I don't want to jump through those hoops. 00:12:51.009 --> 00:12:52.570 I don't want to make an account. I don't want 00:12:52.570 --> 00:12:55.269 to use the wizard. I'm just a user looking for 00:12:55.269 --> 00:12:57.879 an airport. OK. If we zoom out from the error 00:12:57.879 --> 00:13:00.779 message itself, the margins of this page are 00:13:00.779 --> 00:13:03.460 absolutely full of alternative options. Yes, 00:13:03.740 --> 00:13:05.919 the safety net of the platform. Yes, because 00:13:05.919 --> 00:13:07.899 the page doesn't just end with, sorry, try again. 00:13:08.000 --> 00:13:11.000 Yeah. It actively tries to redirect your curiosity. 00:13:11.159 --> 00:13:13.799 It offers so many other paths. It really does. 00:13:14.009 --> 00:13:17.029 It says, look for Solidarity Chesson -Golenio 00:13:17.029 --> 00:13:19.570 Airport on one of Wikipedia's sister projects. 00:13:19.590 --> 00:13:22.070 Sister projects, yeah. And it lists an entire 00:13:22.070 --> 00:13:24.149 universe of categorization. Let's really look 00:13:24.149 --> 00:13:26.610 at this list because it is wild. It's extensive. 00:13:26.950 --> 00:13:30.710 It suggests checking Wiktionary, Wikibooks, Wikiquote, 00:13:30.870 --> 00:13:34.370 Wikisource, Wikiversity, Commons, Wikivoyage, 00:13:34.730 --> 00:13:38.639 Wikinews, Wikidata. and even wiki species. It's 00:13:38.639 --> 00:13:41.740 a comprehensive attempt to index every facet 00:13:41.740 --> 00:13:44.600 of human existence. But think about the absurdity 00:13:44.600 --> 00:13:47.240 of this safety net catching our specific query. 00:13:47.379 --> 00:13:49.379 Right, because of what you searched for. Yeah, 00:13:49.440 --> 00:13:51.720 it's suggesting I look for a Polish airport in 00:13:51.720 --> 00:13:54.740 a textbook library or a directory of biological 00:13:54.740 --> 00:13:56.820 species. Which makes no sense. What am I going 00:13:56.820 --> 00:13:59.679 to find in wiki species? Did someone classify 00:13:59.679 --> 00:14:03.759 a Boeing 737 as a rare metal bird native to Galenio? 00:14:04.200 --> 00:14:06.909 Probably not. Or wiki quote. Am I going to find 00:14:06.909 --> 00:14:08.809 a curated list of things people yelled at the 00:14:08.809 --> 00:14:11.669 baggage claim in Chesson? I mean, while it seems 00:14:11.669 --> 00:14:13.850 absurd for this specific search, you have to 00:14:13.850 --> 00:14:15.789 look at what the infrastructure represents. What 00:14:15.789 --> 00:14:18.149 do you mean? The platform doesn't know why you 00:14:18.149 --> 00:14:20.289 are searching for that term. It just knows its 00:14:20.289 --> 00:14:22.789 primary encyclopedia failed you. OK, so it's 00:14:22.789 --> 00:14:25.269 just guessing. So it offers every other possible 00:14:25.269 --> 00:14:27.620 lens. Maybe you weren't looking for the history 00:14:27.620 --> 00:14:29.899 of the airport, but you are a linguistic student 00:14:29.899 --> 00:14:32.360 looking for the etymology of the word golenio 00:14:32.360 --> 00:14:35.299 in Wiktionary. Oh, I see. Or maybe you are a 00:14:35.299 --> 00:14:38.440 pilot looking for raw, unfiltered aeronautical 00:14:38.440 --> 00:14:40.620 data coordinates in Wikidata. Or maybe I just 00:14:40.620 --> 00:14:42.600 need the travel guide in Wikivoyage to figure 00:14:42.600 --> 00:14:45.100 out where to park. Exactly. It's an incredible 00:14:45.100 --> 00:14:47.620 framework of alternative resources. It's throwing 00:14:47.620 --> 00:14:49.460 everything at the wall so you don't leave empty 00:14:49.460 --> 00:14:52.519 -handed. It's an incredibly ambitious piece of 00:14:52.519 --> 00:14:54.899 architecture. It is. But speaking of the architecture, 00:14:54.940 --> 00:14:56.559 I want to talk about the appearance settings. 00:14:57.059 --> 00:15:00.120 Ah, the visual interface. Right. On this page 00:15:00.120 --> 00:15:02.580 that is explicitly telling us it has absolutely 00:15:02.580 --> 00:15:05.919 nothing to show us, we still have incredibly 00:15:05.919 --> 00:15:09.679 granular control over how we view that nothingness. 00:15:10.019 --> 00:15:12.940 You can customize the void. You really can. The 00:15:12.940 --> 00:15:15.340 sidebar lets us adjust the text size to small, 00:15:15.419 --> 00:15:18.059 standard, or large. we can set the width of the 00:15:18.059 --> 00:15:20.379 blank page. The light and dark mode toggles, 00:15:20.620 --> 00:15:22.679 too. Yes, toggle between light mode and dark 00:15:22.679 --> 00:15:25.820 mode. But right there in that menu is an option 00:15:25.820 --> 00:15:28.059 that completely stopped me in my tracks. I know 00:15:28.059 --> 00:15:29.700 exactly what you're going to say. It's an option 00:15:29.700 --> 00:15:33.559 for birthday mode, and in parentheses, baby globe. 00:15:34.059 --> 00:15:37.580 Yes, birthday mode, baby globe. Currently listed 00:15:37.580 --> 00:15:41.000 as disabled, but present in the code. What is 00:15:41.000 --> 00:15:44.600 happening there? We are staring at this sterile... 00:15:44.700 --> 00:15:48.720 highly technical diagnostic screen talking about 00:15:48.720 --> 00:15:51.860 server purges and case -sensitive binary strings. 00:15:52.179 --> 00:15:55.399 And gatekeeping wizards. Yes, and wizards. And 00:15:55.399 --> 00:15:57.519 right next to it is a toggle to put the whole 00:15:57.519 --> 00:15:59.720 system into birthday mode and look at a baby 00:15:59.720 --> 00:16:03.059 globe. It's amazing. It is such a bizarre, jarring 00:16:03.059 --> 00:16:05.519 Easter egg. It's jarring, but honestly, it might 00:16:05.519 --> 00:16:07.639 be the most important philosophical takeaway 00:16:07.639 --> 00:16:10.389 on the entire page. Wait, really? How so? because 00:16:10.389 --> 00:16:12.649 it perfectly encapsulates the central paradox 00:16:12.649 --> 00:16:14.669 of the open source internet. Okay, elaborate 00:16:14.669 --> 00:16:18.029 on that. On one hand, you have this terrifyingly 00:16:18.029 --> 00:16:21.289 strict, rigid bureaucracy, databases that fail 00:16:21.289 --> 00:16:23.570 over a lowercase letter, hierarchical user, ranks 00:16:23.570 --> 00:16:25.789 like auto -confirmed, strict codes of conduct 00:16:25.789 --> 00:16:27.490 in the footer. Right, it has to be strict to 00:16:27.490 --> 00:16:29.970 survive. Exactly. It operates with the cold, 00:16:30.309 --> 00:16:32.769 unfeeling logic of a machine. But on the other 00:16:32.769 --> 00:16:36.230 hand, the machine is entirely built, maintained, 00:16:36.490 --> 00:16:39.830 and driven by human volunteers. And humans are 00:16:39.830 --> 00:16:43.110 whimsical. The developers who spend their nights 00:16:43.110 --> 00:16:46.090 writing complex caching algorithms and vandalism 00:16:46.090 --> 00:16:49.090 filters are the same people who occasionally 00:16:49.090 --> 00:16:51.470 just want to put a party hat on the site's globe 00:16:51.470 --> 00:16:55.090 logo to celebrate an anniversary. A baby globe. 00:16:55.289 --> 00:16:58.649 Right. The birthday mode reminds you that behind 00:16:58.649 --> 00:17:01.730 the intimidating, monolithic facade of the database, 00:17:02.409 --> 00:17:04.509 there are real people with a sense of humor. 00:17:05.410 --> 00:17:08.289 That is wow. The strictness of the machine relies 00:17:08.289 --> 00:17:11.289 entirely on the whimsy of humans. That is a brilliant 00:17:11.289 --> 00:17:14.250 way to look at it. The humanity is hiding right 00:17:14.250 --> 00:17:16.630 there in the appearance menu. It really is. Okay, 00:17:16.630 --> 00:17:18.769 well, let's pull all of this together. We started 00:17:18.769 --> 00:17:21.309 today's deep dive looking for a straightforward 00:17:21.309 --> 00:17:24.130 article on the Solidarity Chesson -Golenio Airport. 00:17:24.230 --> 00:17:27.460 And we hit a wall. A complete blank. But by lingering 00:17:27.460 --> 00:17:30.200 in that void and reading the manual the librarian 00:17:30.200 --> 00:17:32.880 handed us, we learned so much more than if the 00:17:32.880 --> 00:17:35.640 page had just loaded normally. We dissected the 00:17:35.640 --> 00:17:38.000 absolute literalism of digital search. Right. 00:17:38.160 --> 00:17:40.859 Realizing that a machine doesn't see words, it 00:17:40.859 --> 00:17:43.660 sees strings of binary code. We uncovered the 00:17:43.660 --> 00:17:46.039 physical infrastructure of the internet. The 00:17:46.039 --> 00:17:49.240 reality of servers and caches that require mechanical 00:17:49.240 --> 00:17:52.059 purge function to catch up to the present moment. 00:17:52.180 --> 00:17:54.480 And we debated the programmers' dilemma. Yes, 00:17:54.599 --> 00:17:57.240 understanding why case sensitivity forgives you 00:17:57.240 --> 00:17:59.819 on the first letter but punishes you on the second. 00:17:59.920 --> 00:18:01.980 We challenged the gatekeepers of knowledge, too, 00:18:02.400 --> 00:18:04.920 realizing that the bureaucratic friction of wizards 00:18:04.920 --> 00:18:08.539 in auto -confirmed ranks isn't elitism. No, it's 00:18:08.539 --> 00:18:11.400 the necessary armor that protects a free resource 00:18:11.400 --> 00:18:13.839 from collapsing under the weight of human malice. 00:18:13.920 --> 00:18:17.009 Exactly. And we explored the immense safety net 00:18:17.009 --> 00:18:19.890 of the platform, the sprawling ambition of sister 00:18:19.890 --> 00:18:23.230 projects ready to catch a failed query. And the 00:18:23.230 --> 00:18:25.730 delightful human crooks, like a hidden birthday 00:18:25.730 --> 00:18:28.410 mode, that keep the rigid structure grounded 00:18:28.410 --> 00:18:31.269 in volunteer culture. It totally reframes how 00:18:31.269 --> 00:18:33.849 we should experience a digital dead end. It does. 00:18:34.029 --> 00:18:36.170 And for you listening, I think this is the ultimate 00:18:36.170 --> 00:18:38.509 lesson for the curious mind. Oh, absolutely. 00:18:38.890 --> 00:18:41.349 When you're trying to understand how a massive 00:18:41.349 --> 00:18:44.369 complex system works, whether it's an organization, 00:18:44.869 --> 00:18:48.349 a piece of software, or a community, you usually 00:18:48.349 --> 00:18:51.230 don't learn the truth by reading its successful 00:18:51.230 --> 00:18:54.609 polished outputs. No, the polish hides the mechanisms. 00:18:54.869 --> 00:18:57.930 Exactly. You learn how the machine works by bumping 00:18:57.930 --> 00:18:59.930 hard into its boundaries. By hitting the errors. 00:19:00.089 --> 00:19:02.349 You learn by triggering its error messages, reading 00:19:02.349 --> 00:19:05.109 its diagnostic manuals, and asking why it broke. 00:19:05.349 --> 00:19:08.450 The errors are where the true blueprint of the 00:19:08.450 --> 00:19:11.069 system becomes visible. But before we wrap up, 00:19:11.210 --> 00:19:13.230 there is one final piece of the blueprint on 00:19:13.230 --> 00:19:15.150 this page that we haven't resolved. Oh, right. 00:19:15.630 --> 00:19:18.410 A lingering mystery buried at the very bottom 00:19:18.410 --> 00:19:20.829 of the troubleshooting list. The final explanation 00:19:20.829 --> 00:19:23.349 for why our airport article might be missing. 00:19:23.690 --> 00:19:26.150 The text says, if the page has been deleted, 00:19:26.250 --> 00:19:28.920 check the deletion log. and see, why was the 00:19:28.920 --> 00:19:31.539 page I created deleted? It opens up an entirely 00:19:31.539 --> 00:19:33.859 new dimension to the void. It really does. It 00:19:33.859 --> 00:19:35.700 leaves you wondering about the history of this 00:19:35.700 --> 00:19:38.200 specific blank space. Yeah, was the Solidarity 00:19:38.200 --> 00:19:40.900 Chessin' Galenio airport page truly never created? 00:19:41.259 --> 00:19:43.839 Did no one in the entire history of the internet 00:19:43.839 --> 00:19:47.559 ever bother to type it up? Or was it built? Did 00:19:47.559 --> 00:19:50.299 someone go through the trouble of making an account, 00:19:50.740 --> 00:19:53.420 becoming auto -confirmed, drafting the history 00:19:53.420 --> 00:19:56.380 of the runways? submitting it to the article 00:19:56.380 --> 00:19:59.200 wizard was it published live for the world to 00:19:59.200 --> 00:20:02.019 see and then deliberately systematically wiped 00:20:02.019 --> 00:20:05.480 from the digital record a digital graveyard what 00:20:05.480 --> 00:20:08.000 other digital ghosts are hiding right now just 00:20:08.000 --> 00:20:11.589 at a site in the deletion log Were they removed 00:20:11.589 --> 00:20:15.269 for inaccuracy, for lack of citations, or for 00:20:15.269 --> 00:20:17.529 something else? It's a fascinating thought to 00:20:17.529 --> 00:20:19.450 leave you with. It really is. The next time you 00:20:19.450 --> 00:20:21.630 hit a dead end on the web, remember, you might 00:20:21.630 --> 00:20:23.309 not be looking at an empty lot. You might be 00:20:23.309 --> 00:20:25.789 looking at a demolished building. Well! Something 00:20:25.789 --> 00:20:27.589 to mull over. Until next time.