WEBVTT 00:00:00.000 --> 00:00:03.480 Imagine you're packing your bags for Poland. 00:00:03.899 --> 00:00:05.980 Right? Oh, exciting. Yeah, you're flying into 00:00:05.980 --> 00:00:08.060 a regional hub, so you type your destination 00:00:08.060 --> 00:00:10.679 into the world's largest online encyclopedia. 00:00:11.099 --> 00:00:13.580 You know, you look up Solidarity, Cheston -Golenio 00:00:13.580 --> 00:00:15.460 Airport. And you're probably expecting, like, 00:00:15.460 --> 00:00:17.940 a map or maybe some runway lengths. Exactly. 00:00:18.300 --> 00:00:20.199 You want the local weather or, I don't know, 00:00:20.260 --> 00:00:22.719 a photograph of the terminal, but instead you 00:00:22.719 --> 00:00:26.179 just hit a brick wall, a total digital dead end. 00:00:26.219 --> 00:00:29.019 It's the worst feeling. It really is. The screen 00:00:29.019 --> 00:00:32.939 just... dares back at you with this bold, completely 00:00:32.939 --> 00:00:36.420 uncompromising message. It says, Wikipedia does 00:00:36.420 --> 00:00:39.079 not have an article with this exact name. Right, 00:00:39.079 --> 00:00:41.140 because we've basically been conditioned to expect 00:00:41.140 --> 00:00:43.859 the internet to act like a vending machine. You 00:00:43.859 --> 00:00:46.439 put in a search query, and a neatly packaged 00:00:46.439 --> 00:00:48.679 informational product just drops out. So when 00:00:48.679 --> 00:00:52.179 that transaction fails, it feels almost like 00:00:52.179 --> 00:00:54.960 a glitch in reality. A glitch in reality. I love 00:00:54.960 --> 00:00:57.179 that. And that is exactly what makes today's 00:00:57.179 --> 00:01:00.200 source material So highly unusual. It really 00:01:00.200 --> 00:01:03.899 is a strange one. Right. So a listener submitted 00:01:03.899 --> 00:01:07.480 a request for a deep dive on this specific Polish 00:01:07.480 --> 00:01:10.579 airport. But rather than handing us a, you know, 00:01:10.920 --> 00:01:14.180 a brochure on aviation infrastructure, the source 00:01:14.180 --> 00:01:17.459 they sent is a literal page not found screen. 00:01:17.640 --> 00:01:20.359 Which completely pivots the entire mission for 00:01:20.359 --> 00:01:23.299 today. Yes. We are not packing our bags for Poland 00:01:23.299 --> 00:01:27.049 anymore. Today, we are going to explore the anatomy 00:01:27.049 --> 00:01:30.489 of a digital void. A deep dive into nothingness. 00:01:30.709 --> 00:01:32.599 Pretty much. We're going to look at exactly what 00:01:32.599 --> 00:01:34.799 the machinery of the internet tells you when 00:01:34.799 --> 00:01:37.060 a piece of knowledge just isn't there. Because, 00:01:37.099 --> 00:01:39.799 I mean, a blank page on a massive platform like 00:01:39.799 --> 00:01:42.799 that is never actually empty. Right. It's brimming 00:01:42.799 --> 00:01:45.560 with systemic clues. Yeah. It outlines the underlying 00:01:45.560 --> 00:01:48.340 rules, the alternative pathways, all the specific 00:01:48.340 --> 00:01:50.780 hurdles required to even bring information into 00:01:50.780 --> 00:01:53.159 existence. It's essentially a negative space 00:01:53.159 --> 00:01:55.420 that perfectly defines the shape of the entire 00:01:55.420 --> 00:01:58.079 structure. Exactly. OK, let's unpack this because 00:01:58.079 --> 00:02:00.859 we have a really fascinating document here. a 00:02:00.859 --> 00:02:03.239 blueprint of the background infrastructure. Yeah, 00:02:03.239 --> 00:02:06.280 it doesn't just leave you hanging. No. When you 00:02:06.280 --> 00:02:09.039 hit this dead end, the system doesn't just shrug 00:02:09.039 --> 00:02:11.460 and walk away. It actually gives you a highly 00:02:11.460 --> 00:02:14.120 specific, very technical set of instructions 00:02:14.120 --> 00:02:16.680 and explanations for why you are staring at nothing. 00:02:17.360 --> 00:02:21.419 And those reasons are incredibly revealing about 00:02:21.419 --> 00:02:23.879 how knowledge is actually manufactured, verified, 00:02:23.979 --> 00:02:26.819 and controlled in the digital age. So the very 00:02:26.819 --> 00:02:28.780 first clue the source gives us is about the creation 00:02:28.780 --> 00:02:31.900 process itself. It tells the user, you need to 00:02:31.900 --> 00:02:35.419 log in or create an account and be auto -confirmed 00:02:35.419 --> 00:02:37.840 to create new articles. Auto -concerned? Yeah. 00:02:38.300 --> 00:02:41.599 Or alternatively, it suggests using an article 00:02:41.599 --> 00:02:44.680 wizard to submit a draft. Now I have to ask you 00:02:44.680 --> 00:02:46.539 about this terminology. Go for it. We always 00:02:46.539 --> 00:02:48.280 hear the famous slogan that this is the free 00:02:48.280 --> 00:02:50.360 encyclopedia that anyone can edit. Right. That's 00:02:50.360 --> 00:02:52.800 the pitch. So why would an open platform require 00:02:52.800 --> 00:02:55.219 a user to log in jump through all these hoops, 00:02:55.479 --> 00:02:57.439 and achieve this very bureaucratic -sounding 00:02:57.439 --> 00:03:00.159 status of being auto -confirmed just to add a 00:03:00.159 --> 00:03:02.199 regional airport to the map. Well, what's fascinating 00:03:02.199 --> 00:03:04.680 here is the inherent tension between the philosophy 00:03:04.680 --> 00:03:08.080 of open knowledge and the actual practical reality 00:03:08.080 --> 00:03:11.180 of maintaining a massive database. Right. The 00:03:11.180 --> 00:03:13.419 reality is probably a lot messier. Oh, absolutely. 00:03:13.520 --> 00:03:16.439 You have this utopian ideal from the early days 00:03:16.439 --> 00:03:20.219 of the web, you know, open access. Zero barriers 00:03:20.219 --> 00:03:23.819 the Wild West exactly, but if literally anyone 00:03:23.819 --> 00:03:27.280 could create a page instantly Totally anonymously 00:03:27.280 --> 00:03:30.319 and with zero friction the entire system would 00:03:30.319 --> 00:03:32.599 just collapse overnight under a ways of spam 00:03:32.599 --> 00:03:36.659 I imagine spam commercial advertising Vandalism 00:03:36.659 --> 00:03:40.199 and just pure duplication. It would just be millions 00:03:40.199 --> 00:03:44.129 of pages about like people's pets or inside jokes. 00:03:44.409 --> 00:03:46.469 Yeah, or advertisements for cryptocurrency. Oh, 00:03:46.550 --> 00:03:49.129 absolutely. Precisely. Yeah. So this auto -confirmed 00:03:49.129 --> 00:03:51.930 status, it acts as an invisible gatekeeper. It's 00:03:51.930 --> 00:03:54.310 a system designed to measure friction. To measure 00:03:54.310 --> 00:03:56.409 friction. Yeah. The platform requires a minor 00:03:56.409 --> 00:03:59.370 but really crucial demonstration of commitment. 00:03:59.530 --> 00:04:01.710 Oh, OK. Kind of like getting a library card. 00:04:02.030 --> 00:04:04.009 How do you mean? Well, you can walk into a public 00:04:04.009 --> 00:04:05.750 library and read anything you want completely 00:04:05.750 --> 00:04:08.150 anonymously. Right. But the moment you want to 00:04:08.150 --> 00:04:10.490 check a book out, or in this case, put a new 00:04:10.490 --> 00:04:12.789 book on the shelf, the librarian actually needs 00:04:12.789 --> 00:04:15.150 to know you live in the neighborhood. They need 00:04:15.150 --> 00:04:17.829 to know you aren't going to set the periodical 00:04:17.829 --> 00:04:19.889 section on fire. That is a perfect way to look 00:04:19.889 --> 00:04:22.660 at it. You have to exist in their system. long 00:04:22.660 --> 00:04:25.920 enough or interact enough to prove you are a 00:04:25.920 --> 00:04:28.300 human being acting in good faith. Right. And 00:04:28.300 --> 00:04:30.620 if you aren't auto -confirmed, they point you 00:04:30.620 --> 00:04:33.740 to the article wizard. That sounds so formal. 00:04:34.000 --> 00:04:37.319 It is. That phrasing implies a guided, highly 00:04:37.319 --> 00:04:39.839 structured process. You aren't just throwing 00:04:39.839 --> 00:04:42.459 text onto a blank canvas anymore. You're submitting 00:04:42.459 --> 00:04:45.839 a formatted draft. Exactly. For review by editors 00:04:45.839 --> 00:04:48.360 who already understand the complex matrix of 00:04:48.360 --> 00:04:50.620 the community's rules. It really changes the 00:04:50.620 --> 00:04:53.720 perception of the site. It's way less of a digital 00:04:53.720 --> 00:04:56.560 Wild West and much more of a heavily curated 00:04:56.560 --> 00:04:58.779 almost bureaucratic institution. Oh, definitely. 00:04:59.040 --> 00:05:00.759 But there is another reason the source gives 00:05:00.759 --> 00:05:02.779 for the missing page. And honestly, this one 00:05:02.779 --> 00:05:04.360 sounds straight out of a science fiction novel. 00:05:04.519 --> 00:05:07.800 Oh, the database delay. Yes. It says the page 00:05:07.800 --> 00:05:09.819 might have been recently created, but it's not 00:05:09.819 --> 00:05:12.660 visible yet because of a delay in updating the 00:05:12.660 --> 00:05:17.040 database. Right. And then it advises you to wait 00:05:17.040 --> 00:05:19.339 a few minutes or try the purge function. Try 00:05:19.339 --> 00:05:21.180 the purge function. I mean, are we looking for 00:05:21.180 --> 00:05:23.360 an airport or are we operating a nuclear submarine? 00:05:23.699 --> 00:05:26.019 Right. It sounds incredibly intense. What does 00:05:26.019 --> 00:05:28.699 purging even mean in this context? It's a very 00:05:28.699 --> 00:05:32.939 dramatic term for a very mundane but essential 00:05:32.939 --> 00:05:36.000 piece of computer science. It basically all comes 00:05:36.000 --> 00:05:38.899 down to how servers handle massive amounts of 00:05:38.899 --> 00:05:41.480 traffic. Think of a database like a massive, 00:05:41.660 --> 00:05:44.519 incredibly busy restaurant kitchen. If thousands 00:05:44.519 --> 00:05:46.680 of people are asking for the exact same menu 00:05:46.680 --> 00:05:49.660 item every single second, The kitchen doesn't 00:05:49.660 --> 00:05:51.839 cook it from scratch every time. No. That would 00:05:51.839 --> 00:05:54.019 take way too long. The servers would just crash. 00:05:54.180 --> 00:05:56.420 Right. Instead, they use a cache. The cache is 00:05:56.420 --> 00:05:58.319 kind of like a display case at the front of the 00:05:58.319 --> 00:06:03.079 restaurant. Oh, OK. I follow. They put them in 00:06:03.079 --> 00:06:05.500 the display case so they can hand them out to 00:06:05.500 --> 00:06:08.959 users instantly. But because of this, the display 00:06:08.959 --> 00:06:11.259 case isn't always perfectly synchronized with 00:06:11.259 --> 00:06:13.620 what's happening back in the kitchen. Ah, I see. 00:06:13.680 --> 00:06:15.660 So the airport article might have actually been 00:06:15.660 --> 00:06:18.620 written. The kitchen has cooked the meal. It 00:06:18.620 --> 00:06:20.720 exists somewhere in the server's deep memory. 00:06:21.230 --> 00:06:24.209 But the public -facing display case, the cache, 00:06:24.670 --> 00:06:26.930 it just hasn't been updated yet. You nailed it. 00:06:27.009 --> 00:06:30.430 There is a literal temporal gap between the creation 00:06:30.430 --> 00:06:32.910 of knowledge and its visibility to the public. 00:06:32.910 --> 00:06:35.629 And that purge function the source mentions, 00:06:36.209 --> 00:06:39.170 that is a manual command to force the system 00:06:39.170 --> 00:06:42.389 to throw out the old display case and pull the 00:06:42.389 --> 00:06:45.069 absolute freshest data straight from the kitchen. 00:06:45.290 --> 00:06:47.449 That is wild. It's essentially a ghost page. 00:06:47.660 --> 00:06:50.300 Yeah, pretty much. It is there, but you can't 00:06:50.300 --> 00:06:52.019 see it until you literally force the machine 00:06:52.019 --> 00:06:54.300 to acknowledge the present reality instead of 00:06:54.300 --> 00:06:56.439 the reality from five minutes ago. It's a great 00:06:56.439 --> 00:06:58.819 reminder of how things actually work under the 00:06:58.819 --> 00:07:01.420 hood. I love this detail because it completely 00:07:01.420 --> 00:07:03.459 shatters the illusion we have of the internet 00:07:03.459 --> 00:07:06.139 being instantaneous. We really do take that for 00:07:06.139 --> 00:07:08.620 granted. We forget that the digital world has 00:07:08.620 --> 00:07:11.620 physical constraints. Servers take time to sync. 00:07:11.959 --> 00:07:14.040 Data actually takes time to travel through fiber 00:07:14.040 --> 00:07:17.319 optic cables. It reminds us that knowledge dissemination 00:07:17.319 --> 00:07:19.920 is still a mechanical process, even when it's 00:07:19.920 --> 00:07:21.519 happening at the speed of light. But what if 00:07:21.519 --> 00:07:24.560 it's not a mechanical delay? What if we push 00:07:24.560 --> 00:07:27.500 the purge button, we wait, we are fully auto 00:07:27.500 --> 00:07:30.360 -confirmed, and the page just still isn't there? 00:07:30.480 --> 00:07:32.540 Then we get into the human element. Right, that 00:07:32.540 --> 00:07:34.959 brings us to the microscopic human errors, or 00:07:34.959 --> 00:07:37.370 even... purposeful erasure, and here's where 00:07:37.370 --> 00:07:39.470 it gets really interesting. The naming rules. 00:07:39.990 --> 00:07:42.910 Yes. The source outlines a bizarrely specific 00:07:42.910 --> 00:07:45.069 rule about how things are named in this database. 00:07:45.870 --> 00:07:48.970 It warns the user, titles on Wikipedia are case 00:07:48.970 --> 00:07:51.589 sensitive, except for the first character. It 00:07:51.589 --> 00:07:53.709 really is one of the most peculiar technical 00:07:53.709 --> 00:07:56.509 artifacts on the entire platform. I mean, I have 00:07:56.509 --> 00:07:58.970 to push back on this logic, because... Honestly, 00:07:59.149 --> 00:08:01.230 it makes absolutely zero sense to me as a user. 00:08:01.329 --> 00:08:03.709 It's definitely counterintuitive. Why would it 00:08:03.709 --> 00:08:05.990 be case sensitive except for the first character? 00:08:06.250 --> 00:08:08.550 Why wouldn't the system just force everything 00:08:08.550 --> 00:08:10.930 to be completely case -sensitive or, you know, 00:08:11.290 --> 00:08:13.329 completely ignore capitalization altogether like 00:08:13.329 --> 00:08:15.769 Google does? It seems totally nonsensical to 00:08:15.769 --> 00:08:17.750 a human, but it actually makes perfect sense 00:08:17.750 --> 00:08:20.189 if you look at the archaeology of the software. 00:08:20.410 --> 00:08:23.529 The archaeology? Yeah. When the underlying code 00:08:23.529 --> 00:08:27.009 for this platform was written decades ago, URLs, 00:08:27.329 --> 00:08:29.970 the actual web addresses, they often couldn't 00:08:29.970 --> 00:08:32.779 handle spaces. Oh, right. Early internet days. 00:08:33.100 --> 00:08:35.419 So developers use something called camel case, 00:08:35.580 --> 00:08:37.759 where you capitalize the first letter of each 00:08:37.759 --> 00:08:41.100 word to string them together. Furthermore, early 00:08:41.100 --> 00:08:43.740 database indexing scripts automatically capitalize 00:08:43.740 --> 00:08:46.399 the first letter of any new entry just to keep 00:08:46.399 --> 00:08:49.039 alphabetical lists looking neat. Oh. So it's 00:08:49.039 --> 00:08:51.799 a fossil. Yes. It's a leftover piece of code 00:08:51.799 --> 00:08:54.940 from the 1990s that is still dictating how we 00:08:54.940 --> 00:08:57.279 search for things today. It is a pure legacy 00:08:57.279 --> 00:09:00.039 constraint. The software architecture bubbled 00:09:00.039 --> 00:09:02.740 up and basically created a strict rule for human 00:09:02.740 --> 00:09:06.000 users. It's like a bouncer at a club who only 00:09:06.000 --> 00:09:08.620 cares if the first letter of your name is capitalized 00:09:08.620 --> 00:09:11.620 on your ID, but just completely ignores the rest 00:09:11.620 --> 00:09:13.659 of it. That's exactly what it's like. So if our 00:09:13.659 --> 00:09:16.720 listener typed a lowercase s for solidarity instead 00:09:16.720 --> 00:09:18.899 of a capital S at the very beginning of the search, 00:09:19.419 --> 00:09:22.120 the system forgives it. Right. But if they capitalize 00:09:22.120 --> 00:09:24.840 the wrong letter later in the title, like maybe 00:09:24.840 --> 00:09:28.080 they write schessen with lowercase s in the middle 00:09:28.080 --> 00:09:31.039 of the string, The entire search completely breaks. 00:09:31.279 --> 00:09:33.759 The machine forces you to think with its own 00:09:33.759 --> 00:09:36.919 rigid, unnatural logic. Please check alternative 00:09:36.919 --> 00:09:39.419 capitalizations, it politely suggests, while 00:09:39.419 --> 00:09:41.639 silently judging your keystrokes. It's very passive, 00:09:41.679 --> 00:09:44.220 aggressive code. But then the source pivots from 00:09:44.220 --> 00:09:47.039 a simple typo to something much more ominous. 00:09:47.220 --> 00:09:50.059 A deletion log. Yeah. It says, if the page has 00:09:50.059 --> 00:09:53.080 been deleted, check the deletion log. And it 00:09:53.080 --> 00:09:55.559 directs the user to a highly specific help section 00:09:55.559 --> 00:09:59.149 titled, why was the page I created deleted? I 00:09:59.149 --> 00:10:00.970 really want to focus on that phrasing for a moment. 00:10:01.350 --> 00:10:03.470 Why was the page I created deleted? Yeah, it 00:10:03.470 --> 00:10:05.830 gets personal. The system switches to the first 00:10:05.830 --> 00:10:09.230 -person pronoun. It directly anticipates the 00:10:09.230 --> 00:10:12.230 user's emotional reaction. It anticipates the 00:10:12.230 --> 00:10:14.990 frustration, the confusion, and honestly, a real 00:10:14.990 --> 00:10:18.090 sense of loss. It is almost defensive. Like, 00:10:18.090 --> 00:10:20.450 the machine knows you poured your time into writing 00:10:20.450 --> 00:10:22.690 an article about this regional Polish airport, 00:10:22.690 --> 00:10:25.210 and it knows you are going to be mad that it 00:10:25.210 --> 00:10:27.649 vanished. And it points to a reality we rarely 00:10:27.649 --> 00:10:31.320 consider. It implies a massive hidden graveyard 00:10:31.320 --> 00:10:34.279 of articles. The graveyard? When you and I browse 00:10:34.279 --> 00:10:36.799 the web, we only see the surviving texts. We 00:10:36.799 --> 00:10:39.159 see the winners of the editorial battles. Right. 00:10:39.159 --> 00:10:41.679 We just assume the encyclopedia steadily grows, 00:10:41.860 --> 00:10:44.220 adding one brick after another. But this error 00:10:44.220 --> 00:10:46.379 page points us toward the deletion log, which 00:10:46.379 --> 00:10:49.059 is essentially a ledger of everything that was 00:10:49.059 --> 00:10:52.379 deemed unworthy, unverified, or just unnecessary. 00:10:52.539 --> 00:10:55.220 It reminds us that knowledge curation is not 00:10:55.220 --> 00:10:58.080 just an additive process. No, not at all. It 00:10:58.080 --> 00:11:01.080 is a highly active, sometimes highly destructive 00:11:01.080 --> 00:11:03.879 process of erasure. It's a constant pruning of 00:11:03.879 --> 00:11:06.340 the tree. Exactly. The airport might have been 00:11:06.340 --> 00:11:08.980 there yesterday, but an editor decided it didn't 00:11:08.980 --> 00:11:12.240 have enough independent citations. Or maybe it 00:11:12.240 --> 00:11:15.399 wasn't notable enough for a global audience, 00:11:15.659 --> 00:11:17.580 and so it was sent straight to the graveyard. 00:11:18.000 --> 00:11:20.759 Which brings up the next logical problem. If 00:11:20.759 --> 00:11:22.879 an article is deleted because it doesn't fit 00:11:22.879 --> 00:11:27.090 the strict formal rules of an encyclopedia, Where 00:11:27.090 --> 00:11:29.590 does that information go? Does it just disappear 00:11:29.590 --> 00:11:32.070 from the internet entirely? Well, according to 00:11:32.070 --> 00:11:33.809 our source document, it actually doesn't have 00:11:33.809 --> 00:11:36.110 to. If the article isn't there and it hasn't 00:11:36.110 --> 00:11:39.230 been miscapitalized, the text gives us a roadmap 00:11:39.230 --> 00:11:42.090 of exactly where else we should look within its 00:11:42.090 --> 00:11:45.029 vast ecosystem. The sister projects. Yeah, it 00:11:45.029 --> 00:11:47.789 literally provides a menu of what it calls sister 00:11:47.789 --> 00:11:49.809 projects. And this is where we start to see the 00:11:49.809 --> 00:11:52.970 true scale of this informational endeavor. It 00:11:52.970 --> 00:11:54.950 really is staggering. It treats you like you're 00:11:54.950 --> 00:11:57.690 standing in the main lobby of a massive academic 00:11:57.690 --> 00:11:59.649 institution. That's a great way to picture it. 00:11:59.750 --> 00:12:01.529 The encyclopedia didn't. have what you wanted, 00:12:01.730 --> 00:12:03.850 so the receptionist is essentially pointing you 00:12:03.850 --> 00:12:06.110 to different wings of the campus. Saying, you 00:12:06.110 --> 00:12:08.590 know, look elsewhere. Exactly. It explicitly 00:12:08.590 --> 00:12:12.070 says, look for Solidarity Schuson -Golenio Airport 00:12:12.070 --> 00:12:15.450 on one of Wikipedia's sister projects. And the 00:12:15.450 --> 00:12:18.549 list covers almost every conceivable way to categorize 00:12:18.549 --> 00:12:21.309 human thought. Let's break down what those alternative 00:12:21.309 --> 00:12:23.450 wings actually are, because they're fascinating. 00:12:23.590 --> 00:12:26.490 OK, looking at the source here, it offers Wiktionary, 00:12:26.690 --> 00:12:29.450 which it defines as a dictionary. Right. Wikibooks 00:12:29.450 --> 00:12:33.120 for textbooks. WikiQuote for quotations. WikiSource 00:12:33.120 --> 00:12:35.860 for a free library. WikiVersity for learning 00:12:35.860 --> 00:12:38.580 resources. Commons for free media. Keep going, 00:12:38.600 --> 00:12:41.779 there's more. WikiVoyage, a travel guide. WikiNews, 00:12:42.159 --> 00:12:46.000 a news source. WikiData, a linked database. And 00:12:46.000 --> 00:12:48.679 WikiSpecies, a species directory. Okay, so if 00:12:48.679 --> 00:12:51.059 we connect this to the bigger picture, that list 00:12:51.059 --> 00:12:54.000 is essentially a modern taxonomy of human information 00:12:54.000 --> 00:12:56.159 gathering. It covers everything. Every single 00:12:56.159 --> 00:12:58.840 one of those sister projects represents a fundamentally 00:12:58.840 --> 00:13:01.559 different philosophy of how data should be consumed. 00:13:01.700 --> 00:13:03.960 Okay, take Wiktionary, for example. What is the 00:13:03.960 --> 00:13:06.320 actual difference between looking up our Polish 00:13:06.320 --> 00:13:09.100 airport in a dictionary versus an encyclopedia? 00:13:09.600 --> 00:13:13.039 Scope and intent. A dictionary simply defines 00:13:13.039 --> 00:13:16.120 the word. It tells you how to pronounce Schusson. 00:13:16.320 --> 00:13:18.840 It's etymology. It's part of speech. It doesn't 00:13:18.840 --> 00:13:21.139 care about the runway length. Exactly. It doesn't 00:13:21.139 --> 00:13:23.639 care about the history of the runway or the passenger 00:13:23.639 --> 00:13:27.059 volume in 2023. An encyclopedia cares about the 00:13:27.059 --> 00:13:29.600 narrative, the context, and the historical weight 00:13:29.600 --> 00:13:31.539 of the subject. And then you have something like 00:13:31.539 --> 00:13:34.000 Wikidata, which the source describes as a linked 00:13:34.000 --> 00:13:36.659 database. Now, for the average person hitting 00:13:36.659 --> 00:13:39.320 an error page, that sounds incredibly abstract. 00:13:39.379 --> 00:13:41.399 It does. What does a linked database actually 00:13:41.399 --> 00:13:44.620 do for us? Think of Wikidata as the matrix code 00:13:44.620 --> 00:13:47.740 behind the simulation. A regular article is written 00:13:47.740 --> 00:13:49.700 in paragraphs for human eyes to read, right? 00:13:50.019 --> 00:13:52.220 Yeah. Wikidata strips all the narrative away. 00:13:52.360 --> 00:13:55.580 It is just raw, Schmin readable data tags. It 00:13:55.580 --> 00:13:58.759 links the concept of solidarity airport to coordinates, 00:13:59.000 --> 00:14:01.419 to an IATA code, to a country. Okay, but why? 00:14:01.500 --> 00:14:03.980 It's designed so that when you ask your smartphone's 00:14:03.980 --> 00:14:06.279 virtual assistant, where is the closest airport 00:14:06.279 --> 00:14:09.600 in Poland? The AI doesn't have to read a paragraph 00:14:09.600 --> 00:14:12.720 of text. It just pulls the raw data points instantly 00:14:12.720 --> 00:14:16.059 from Wikidata. That is fascinating. So the platform 00:14:16.059 --> 00:14:18.840 is simultaneously catering to human readers and 00:14:18.840 --> 00:14:20.860 artificial intelligence algorithms. Exactly. 00:14:21.019 --> 00:14:22.679 But if you're the one sitting at your computer 00:14:22.679 --> 00:14:24.659 packing for your trip and you just want to know 00:14:24.659 --> 00:14:27.460 how to get a taxi from this terminal, which of 00:14:27.460 --> 00:14:29.460 these sister projects is actually going to help 00:14:29.460 --> 00:14:31.980 you? Good question. Because searching for an 00:14:31.980 --> 00:14:35.460 airport in wiki species, you know, a biological 00:14:35.460 --> 00:14:38.679 directory is obviously ridiculous unless there's 00:14:38.679 --> 00:14:41.559 some newly discovered species of pigeon. living 00:14:41.559 --> 00:14:45.299 exclusively in Terminal B, that wing of the campus 00:14:45.299 --> 00:14:48.519 is completely useless to you. Very true. But 00:14:48.519 --> 00:14:52.100 look at Wikivoyage or Commons. Yes. Wikivoyage 00:14:52.100 --> 00:14:54.860 is a travel guide. It's entirely about practical, 00:14:55.240 --> 00:14:57.299 boots -on -the -ground utility. Where do I eat? 00:14:57.340 --> 00:14:59.980 What is the bus schedule? Right. That serves 00:14:59.980 --> 00:15:02.179 a completely different intellectual purpose than 00:15:02.179 --> 00:15:04.899 an encyclopedia. The main site might have deleted 00:15:04.899 --> 00:15:07.159 the airport article because it wasn't historically 00:15:07.159 --> 00:15:09.740 notable, but the travel guide gladly accepts 00:15:09.740 --> 00:15:12.059 it. because tourists need to know where the baggage 00:15:12.059 --> 00:15:15.360 claim is. Or consider Commons, the media repository. 00:15:15.759 --> 00:15:18.299 You might not find a 5 ,000 -word essay on the 00:15:18.299 --> 00:15:20.440 airport's construction there. But you might find 00:15:20.440 --> 00:15:24.500 photos. Exactly. 50 high -resolution photographs 00:15:24.500 --> 00:15:27.419 of the runway, the signage, the surrounding geography. 00:15:28.139 --> 00:15:30.940 The platform is basically decentralizing the 00:15:30.940 --> 00:15:32.960 idea of what an answer looks like. Yeah, that's 00:15:32.960 --> 00:15:34.980 a great way to put it. It's saying, we don't 00:15:34.980 --> 00:15:37.379 have the abstract summary you asked for, but 00:15:37.379 --> 00:15:39.860 we might have the raw photos. or the practical 00:15:39.860 --> 00:15:42.419 travel directions, or the exact translation of 00:15:42.419 --> 00:15:44.899 the name. It's remarkably helpful for an error 00:15:44.899 --> 00:15:47.840 page, honestly. It really is. But beyond just 00:15:47.840 --> 00:15:51.059 where to look, the source document also reveals 00:15:51.059 --> 00:15:53.860 some highly specific ways to customize how we 00:15:53.860 --> 00:15:55.700 look at this dead end. And I think this might 00:15:55.700 --> 00:15:57.720 be my favorite part of the entire document. Oh, 00:15:57.720 --> 00:15:59.740 you mean the interface settings hidden in the 00:15:59.740 --> 00:16:02.399 sidebar? Yes. The user environment settings. 00:16:02.519 --> 00:16:05.879 We are staring at a blank page. a literal void, 00:16:06.519 --> 00:16:08.399 an error message telling us that what we want 00:16:08.399 --> 00:16:10.980 does not exist. Right. And yet right there on 00:16:10.980 --> 00:16:13.200 the side of the screen, the system is offering 00:16:13.200 --> 00:16:16.299 us a highly customizable waiting room. It gives 00:16:16.299 --> 00:16:19.759 us toggles for text size, you know, small, standard, 00:16:20.139 --> 00:16:22.919 large. It has a width toggle too. Yes. So you 00:16:22.919 --> 00:16:25.299 can view your failure in standard or wide format. 00:16:25.799 --> 00:16:28.220 It even has color modes in beta, automatic, light 00:16:28.220 --> 00:16:30.519 and dark. It insists on giving you aesthetic 00:16:30.519 --> 00:16:33.539 control over your own dead end. Customize your 00:16:33.539 --> 00:16:37.629 void. It is so funny to me that the system cares 00:16:37.629 --> 00:16:39.850 whether I want to read my error message in a 00:16:39.850 --> 00:16:43.330 large font or a small font. But then there is 00:16:43.330 --> 00:16:45.690 a detail in this appearance menu that completely 00:16:45.690 --> 00:16:47.090 threw me. I think I know what you're going to 00:16:47.090 --> 00:16:49.870 say. It is the most unexpected, almost surreal 00:16:49.870 --> 00:16:53.029 detail in the entire source text. Right under 00:16:53.029 --> 00:16:55.090 the appearance header, there is a toggle for 00:16:55.090 --> 00:16:57.870 something called birthday mode. And in parentheses, 00:16:57.970 --> 00:17:00.990 it says baby globe. Baby globe. Currently, the 00:17:00.990 --> 00:17:03.889 toggle is set to disabled. Birthday mode. It's 00:17:03.889 --> 00:17:06.950 so weird. Yes. I have to challenge this because 00:17:06.950 --> 00:17:08.890 it feels so completely out of place. It really 00:17:08.890 --> 00:17:11.329 does. We are looking for Polish aviation infrastructure. 00:17:11.529 --> 00:17:14.569 We hit a wall. We have spent this entire time 00:17:14.569 --> 00:17:17.829 navigating bureaucratic auto confirmations, legacy 00:17:17.829 --> 00:17:21.569 database purges, and the cold harsh realities 00:17:21.569 --> 00:17:24.509 of the deletion logs. Very serious stuff. And 00:17:24.509 --> 00:17:27.069 suddenly, right in the middle of this sterile 00:17:27.069 --> 00:17:30.009 environment, the system offers us a baby globe 00:17:30.009 --> 00:17:34.119 birthday mode. What does it say about a platform 00:17:34.119 --> 00:17:37.839 that it builds a whimsical Easter egg like this 00:17:37.839 --> 00:17:40.740 directly into its error pages? Well, it's a brilliant 00:17:40.740 --> 00:17:43.460 juxtaposition and it actually reveals the most 00:17:43.460 --> 00:17:45.859 important thing about the platform's architecture. 00:17:46.059 --> 00:17:49.079 Which is? Think about it. If you hit a page not 00:17:49.079 --> 00:17:52.359 found error on a corporate monolith, say an Apple 00:17:52.359 --> 00:17:55.460 service or a Google product, you get a sterile 00:17:55.609 --> 00:17:58.829 heavily branded, legally approved graphics. Oh, 00:17:58.829 --> 00:18:01.349 totally. A corporate entity would never put a 00:18:01.349 --> 00:18:04.390 Baby Globe birthday mode toggle in a global user 00:18:04.390 --> 00:18:06.710 interface menu. Never. It would be considered 00:18:06.710 --> 00:18:08.750 unprofessional. It would be scrubbed by the UI 00:18:08.750 --> 00:18:11.670 design team immediately. Exactly. But this platform 00:18:11.670 --> 00:18:14.009 is not a corporate monolith. It's open source. 00:18:14.190 --> 00:18:16.730 It's built, maintained, and coded by tens of 00:18:16.730 --> 00:18:19.369 thousands of individual volunteers. Real people. 00:18:19.470 --> 00:18:21.950 Yes. Real people who have anniversaries, who 00:18:21.950 --> 00:18:24.009 celebrate milestones, and who occasionally want 00:18:24.009 --> 00:18:25.930 to leave their own human fingerprints on the 00:18:25.930 --> 00:18:28.430 code. That makes a lot of sense. A birthday mode 00:18:28.430 --> 00:18:30.990 toggle proves that this massive intimidating 00:18:30.990 --> 00:18:34.490 database is actually a decentralized community 00:18:34.490 --> 00:18:37.470 -built project. It's a reminder that developers 00:18:37.470 --> 00:18:40.369 are people with a sense of humor. The fact that 00:18:40.369 --> 00:18:42.509 the toggle is sitting right there next to the 00:18:42.509 --> 00:18:44.609 text with settings on a page about a missing 00:18:44.609 --> 00:18:47.970 Polish airport shows how deeply intertwined human 00:18:47.970 --> 00:18:50.849 quirks are with the cold hard code. It really 00:18:50.849 --> 00:18:53.529 humanizes the void. Even in the graveyard of 00:18:53.529 --> 00:18:55.849 missing pages, there's the birthday party waiting 00:18:55.849 --> 00:18:58.470 to be enabled. Exactly. So what does this all 00:18:58.470 --> 00:19:01.460 mean? When we started, you, the listener, asked 00:19:01.460 --> 00:19:04.779 for a deep dive on Solidarity Chess in Gilenyo 00:19:04.779 --> 00:19:06.839 Airport. And we definitely didn't get that. No, 00:19:06.960 --> 00:19:09.000 we couldn't board that specific flight today. 00:19:09.400 --> 00:19:11.660 We didn't learn how many terminals it has or 00:19:11.660 --> 00:19:13.839 what the weather is like on the runway. But what 00:19:13.839 --> 00:19:16.700 we got instead was an incredible, exclusive, 00:19:16.859 --> 00:19:19.099 behind -the -scenes tour of the airport terminal 00:19:19.099 --> 00:19:22.019 itself. The hidden infrastructure of the Internet's 00:19:22.019 --> 00:19:25.299 largest knowledge base. Exactly. We met the auto 00:19:25.299 --> 00:19:27.779 -confirmed gatekeepers holding the library cards. 00:19:28.200 --> 00:19:30.279 We saw the mechanical delays of the database 00:19:30.279 --> 00:19:33.339 caches and the purge functions. We explored the 00:19:33.339 --> 00:19:36.039 vast alternative wings of the sister projects. 00:19:36.180 --> 00:19:38.980 And we even found a disabled baby globe hidden 00:19:38.980 --> 00:19:41.519 in the maintenance closet. You know, this raises 00:19:41.519 --> 00:19:44.220 an important question though. What's that? It 00:19:44.220 --> 00:19:46.880 forces us to realize that a lack of information 00:19:46.880 --> 00:19:50.980 is in itself a profoundly detailed form of information. 00:19:51.059 --> 00:19:53.839 I like that. A blank page does not mean nothing 00:19:53.839 --> 00:19:57.599 is there. It means there are rigorous, invisible, 00:19:58.059 --> 00:20:00.619 and sometimes highly subjective rules governing 00:20:00.619 --> 00:20:03.019 what is allowed to exist in that space. Right. 00:20:03.400 --> 00:20:05.960 The rules holding the empty space tell us everything 00:20:05.960 --> 00:20:07.960 we need to know about the values, the history, 00:20:08.039 --> 00:20:10.559 and the mechanics of the system as a whole. The 00:20:10.559 --> 00:20:14.019 negative space defines the shape. I love that. 00:20:14.359 --> 00:20:16.000 And it leaves me with one final thing for you 00:20:16.000 --> 00:20:18.500 to ponder long after we wrap up today. Think 00:20:18.500 --> 00:20:20.980 back to that deletion log we discussed earlier. 00:20:21.119 --> 00:20:23.220 The hidden graveyard. Yeah, the hidden graveyards 00:20:23.220 --> 00:20:26.180 of rejected articles. How much digital history, 00:20:26.400 --> 00:20:29.380 how many early drafts of reality, how many mundane 00:20:29.380 --> 00:20:32.039 details about regional airports and local histories 00:20:32.039 --> 00:20:34.759 are sitting just out of sight in those hidden 00:20:34.759 --> 00:20:37.220 logs on the websites you rely on every single 00:20:37.220 --> 00:20:39.539 day? It's probably more than anyone realizes. 00:20:39.779 --> 00:20:42.440 We take the visible internet for granted. We 00:20:42.440 --> 00:20:45.160 assume what we see is all there is. But the next 00:20:45.160 --> 00:20:47.819 time you hit a page not found, don't just immediately 00:20:47.819 --> 00:20:50.299 click away. Take a look around. Take a second 00:20:50.299 --> 00:20:53.160 and ask yourself, what invisible rules, what 00:20:53.160 --> 00:20:55.980 gatekeepers, and what pastilations are keeping 00:20:55.980 --> 00:20:58.779 that page hidden in the dark? Because as we learned 00:20:58.779 --> 00:21:01.799 today, even the void always has a story to tell.