WEBVTT 00:00:00.000 --> 00:00:03.919 Welcome to today's Deep Dive. We're very glad 00:00:03.919 --> 00:00:06.259 you could join us today. We really are. Yeah, 00:00:06.320 --> 00:00:08.259 because the source material you sent in for this 00:00:08.259 --> 00:00:09.839 one really took us in a completely unexpected 00:00:09.839 --> 00:00:12.240 direction. Oh, totally. I mean, when you submitted 00:00:12.240 --> 00:00:15.400 a file titled Parada Fuente Stadium dash Wikipedia, 00:00:15.880 --> 00:00:18.679 I naturally assumed we were gearing up for a 00:00:18.679 --> 00:00:21.359 sports history deep dive. Right, like an architectural 00:00:21.359 --> 00:00:24.359 review or something. Exactly. I was looking forward 00:00:24.359 --> 00:00:26.719 to reading up on, you know, architectural blueprints, 00:00:26.859 --> 00:00:29.420 maybe some historic football matches, or just 00:00:29.420 --> 00:00:31.940 the cultural impact of a massive sporting arena 00:00:31.940 --> 00:00:34.100 in its local community. You were ready for a 00:00:34.100 --> 00:00:37.299 concrete landmark. I was fully prepared to unpack 00:00:37.299 --> 00:00:40.740 the legacy of a physical building. But then I 00:00:40.740 --> 00:00:43.740 actually opened the document you provided. It 00:00:43.740 --> 00:00:46.560 is such a brilliant bait and switch because the 00:00:46.560 --> 00:00:48.659 source text you sent us isn't an encyclopedia 00:00:48.659 --> 00:00:51.600 article about a stadium at all. Not even close. 00:00:51.659 --> 00:00:54.020 The twist here is that the source is literally 00:00:54.020 --> 00:00:56.759 the text of a Wikipedia page not found screen. 00:00:57.020 --> 00:00:59.520 Yeah. You search for a stadium and you capture 00:00:59.520 --> 00:01:02.439 the exact output of an empty void. Just a blank 00:01:02.439 --> 00:01:05.689 digital wall. Right. So instead of asking you 00:01:05.689 --> 00:01:07.969 to send us a different article, we decided to 00:01:07.969 --> 00:01:10.750 take this blank space seriously. Because it really 00:01:10.750 --> 00:01:13.269 is serious when you look at it. It is. So our 00:01:13.269 --> 00:01:16.069 mission today is treating this digital dead end 00:01:16.069 --> 00:01:20.689 as a profound philosophical document. We are 00:01:20.689 --> 00:01:23.750 going to use this exact source to unpack the 00:01:23.750 --> 00:01:26.510 hidden architecture of the world's biggest encyclopedia. 00:01:26.730 --> 00:01:29.250 Which honestly is often way more revealing than 00:01:29.250 --> 00:01:31.909 a completed article. How so? Well, when you look 00:01:31.909 --> 00:01:35.170 at a polished Wikipedia page, the mechanics of 00:01:35.170 --> 00:01:37.349 how it got there are completely invisible. You 00:01:37.349 --> 00:01:39.890 just see the finished product. But when information 00:01:39.890 --> 00:01:42.909 is missing, the platform is forced to show its 00:01:42.909 --> 00:01:44.969 hand. That makes a lot of sense. Yeah. We're 00:01:44.969 --> 00:01:47.730 going to use this literal non -page to examine 00:01:47.730 --> 00:01:50.409 how this massive platform handles the absence 00:01:50.409 --> 00:01:54.810 of knowledge and the invisible, highly bureaucratic 00:01:54.810 --> 00:01:57.370 mechanisms it uses to govern human curiosity. 00:01:57.670 --> 00:02:00.049 Okay. Let's jump right into the anatomy of this 00:02:00.049 --> 00:02:02.489 missing page. The very first thing that jumps 00:02:02.489 --> 00:02:04.750 out is the bolded message sitting right in the 00:02:04.750 --> 00:02:06.969 middle of the screen. The main error text. Right. 00:02:07.069 --> 00:02:09.770 It says, Wikipedia does not have an article with 00:02:09.770 --> 00:02:13.259 this exact name. That phrasing feels very deliberate 00:02:13.259 --> 00:02:15.819 to me. Oh, it is. Extremely deliberate. Because 00:02:15.819 --> 00:02:18.259 it doesn't say the stadium doesn't exist. And 00:02:18.259 --> 00:02:19.879 it doesn't say the platform lacks information 00:02:19.879 --> 00:02:22.500 on the topic altogether. No. The precision of 00:02:22.500 --> 00:02:25.439 that language is the platform admitting its own 00:02:25.439 --> 00:02:28.719 literalism. It's a necessary disclaimer because 00:02:28.719 --> 00:02:31.479 digital databases don't read context the way 00:02:31.479 --> 00:02:33.719 humans do. They just read the code. Exactly. 00:02:33.780 --> 00:02:37.099 They read code. A human knows that Parada Fuente 00:02:37.099 --> 00:02:40.340 with a capital F and Parada Fuente with a lowercase 00:02:40.340 --> 00:02:43.400 f refer to the exact same physical structure. 00:02:43.560 --> 00:02:46.500 Right. The database, however, sees two entirely 00:02:46.500 --> 00:02:48.740 different strings of characters. Which actually 00:02:48.740 --> 00:02:51.180 leads right into a technical rule listed directly 00:02:51.180 --> 00:02:53.780 under that main message. And I suspect most people 00:02:53.780 --> 00:02:56.060 completely gloss over this when they hit an error 00:02:56.060 --> 00:02:59.159 page. Oh, for sure. The source tells us titles 00:02:59.159 --> 00:03:01.699 on Wikipedia are case sensitive except for the 00:03:01.699 --> 00:03:04.699 first character. Yeah. So if I'm reading this 00:03:04.699 --> 00:03:07.620 right, a single misplaced capital letter in your 00:03:07.620 --> 00:03:10.340 search is enough to hide an entire stadium's 00:03:10.340 --> 00:03:12.240 worth of knowledge from the Internet. That is 00:03:12.240 --> 00:03:15.520 exactly right. But why? Why design a massive 00:03:15.520 --> 00:03:17.840 public encyclopedia with that kind of strict 00:03:17.840 --> 00:03:20.719 case sensitivity? It seems counterintuitive. 00:03:20.919 --> 00:03:22.900 It comes down to how the underlying software 00:03:22.900 --> 00:03:25.680 categorizes variables. The software is called 00:03:25.680 --> 00:03:28.590 MediaWiki. The system automatically capitalizes 00:03:28.590 --> 00:03:31.990 the first letter of any search or URL to standardize 00:03:31.990 --> 00:03:34.210 the formatting of the article titles. Okay, so 00:03:34.210 --> 00:03:36.229 the very first letter is always a capital. Right. 00:03:36.349 --> 00:03:39.689 But after that first character, it strictly enforces 00:03:39.689 --> 00:03:41.909 case sensitivity because it needs to distinguish 00:03:41.909 --> 00:03:44.469 between fundamentally different concepts that 00:03:44.469 --> 00:03:47.069 might share the exact same spelling. Oh, I see. 00:03:47.169 --> 00:03:49.330 For instance, distinguishing between a general 00:03:49.330 --> 00:03:52.349 concept like red meat with a lowercase m and 00:03:52.349 --> 00:03:54.710 a specific proper noun like a band called Red 00:03:54.710 --> 00:03:56.780 Meat with a capital M. Okay, that makes sense. 00:03:56.979 --> 00:03:59.900 The database needs that structural rigidity to 00:03:59.900 --> 00:04:02.599 avoid collapsing distinct unrelated topics into 00:04:02.599 --> 00:04:04.240 one another. It makes you wonder how many times 00:04:04.240 --> 00:04:06.539 people assume information just isn't on the internet 00:04:06.539 --> 00:04:08.900 when in reality they just tripped over a hidden 00:04:08.900 --> 00:04:11.340 database rule. Probably thousands of times a 00:04:11.340 --> 00:04:13.960 day. But the source goes beyond just user error. 00:04:14.180 --> 00:04:16.800 It brings up the possibility that the page might 00:04:16.800 --> 00:04:19.620 have existed once but was actively removed. The 00:04:19.620 --> 00:04:22.259 digital ghosts. Yeah, the digital ghosts. It 00:04:22.259 --> 00:04:25.360 advises, and I'm quoting here, If the page has 00:04:25.360 --> 00:04:27.879 been deleted, check the deletion log and see 00:04:27.879 --> 00:04:31.439 why was the page I created deleted? Which basically 00:04:31.439 --> 00:04:34.300 turns the user into a bit of a digital archaeologist. 00:04:34.420 --> 00:04:36.240 It really does. We tend to view the internet. 00:04:36.620 --> 00:04:39.199 and Wikipedia especially, as this permanent, 00:04:39.360 --> 00:04:42.120 ever -expanding repository where things only 00:04:42.120 --> 00:04:44.579 get added. Right, a permanent library. But this 00:04:44.579 --> 00:04:47.160 error page reminds us that it's actually a heavily 00:04:47.160 --> 00:04:50.220 edited, constantly shifting battleground. What 00:04:50.220 --> 00:04:52.600 exactly is happening in those deletion logs? 00:04:52.720 --> 00:04:55.819 Because asking, why was the page I created deleted, 00:04:56.019 --> 00:04:58.459 implies there is an active force in the background 00:04:58.459 --> 00:05:00.860 scrubbing things out. There is. The deletion 00:05:00.860 --> 00:05:03.639 log is essentially a public record of Wikipedia's 00:05:03.639 --> 00:05:06.399 longstanding internal philosophical war. A war 00:05:06.399 --> 00:05:09.019 between who? Between two main factions of editors, 00:05:09.300 --> 00:05:11.860 the inclusionists and the deletionists. That 00:05:11.860 --> 00:05:15.300 sounds like sci -fi. It kind of is. Inclusionists 00:05:15.300 --> 00:05:17.839 believe the platform should harbor as much information 00:05:17.839 --> 00:05:21.079 as humanly possible, no matter how niche or obscure. 00:05:21.629 --> 00:05:24.889 If a stadium exists, it deserves a page. And 00:05:24.889 --> 00:05:27.589 the deletionists? Deletionists argue that maintaining 00:05:27.589 --> 00:05:30.709 the encyclopedia's high standards requires aggressively 00:05:30.709 --> 00:05:33.410 pruning articles that lack sufficient notability 00:05:33.410 --> 00:05:36.709 or reliable sourcing. So quality over quantity. 00:05:37.050 --> 00:05:39.829 Exactly. So when you see that prompt on the error 00:05:39.829 --> 00:05:42.089 screen, you aren't just looking at a technical 00:05:42.089 --> 00:05:44.750 glitch. You are being invited to look at the 00:05:44.750 --> 00:05:47.079 bureaucratic graveyard. where those editorial 00:05:47.079 --> 00:05:50.120 battles are fought and recorded. Wow. Okay, speaking 00:05:50.120 --> 00:05:52.360 of technical glitches, the text also mentions 00:05:52.360 --> 00:05:56.040 a delay in updating the database. Yes. And it 00:05:56.040 --> 00:05:57.860 advises you to wait a few minutes or try the 00:05:57.860 --> 00:05:59.839 purge function. The purge function. That sounds 00:05:59.839 --> 00:06:01.879 vaguely intense for a public reference site. 00:06:01.939 --> 00:06:03.660 Like we're initiating a self -destruct sequence. 00:06:03.819 --> 00:06:05.959 What actually happens when you hit a purge function? 00:06:06.220 --> 00:06:08.899 It is just a very dramatic term for clearing 00:06:08.899 --> 00:06:11.560 the server's cache. Oh. Because Wikipedia gets 00:06:11.560 --> 00:06:14.639 an astronomical amount of global traffic, it 00:06:14.639 --> 00:06:17.649 would just... completely crash if it tried to 00:06:17.649 --> 00:06:19.670 generate a fresh page from the core database 00:06:19.670 --> 00:06:23.129 every single time a user clicked a link. Just 00:06:23.129 --> 00:06:26.230 too much computing power required. Right. Instead, 00:06:26.370 --> 00:06:29.009 it serves saved snapshots or cast versions of 00:06:29.009 --> 00:06:31.670 the pages. So the purge function is just forcing 00:06:31.670 --> 00:06:34.129 the system to go back to the core database and 00:06:34.129 --> 00:06:37.470 fetch the absolute latest version. Exactly. rather 00:06:37.470 --> 00:06:39.769 than serving you the snapshot it took five minutes 00:06:39.769 --> 00:06:42.670 ago. That is fascinating. The platform is literally 00:06:42.670 --> 00:06:45.089 giving you a glimpse into its own plumbing here. 00:06:45.209 --> 00:06:48.470 It is a living, breathing network of servers 00:06:48.470 --> 00:06:51.680 that sometimes gets congested. and just needs 00:06:51.680 --> 00:06:54.360 a manual reset to catch up with all the edits 00:06:54.360 --> 00:06:56.379 happening in real time. All of these technical 00:06:56.379 --> 00:06:59.160 disclaimers, the case sensitivity, the deletion 00:06:59.160 --> 00:07:01.339 logs, the cache purging, they all eventually 00:07:01.339 --> 00:07:04.220 lead to a very specific call to action. They 00:07:04.220 --> 00:07:06.800 do. The page doesn't just offer excuses for why 00:07:06.800 --> 00:07:09.279 the stadium isn't there. It actively recruits 00:07:09.279 --> 00:07:11.199 you to fill the void. It wants you to build it. 00:07:11.470 --> 00:07:13.709 Right there in the text, it says, you need to 00:07:13.709 --> 00:07:16.389 log in or create an account. But then it dropped 00:07:16.389 --> 00:07:19.009 a hurdle. It says you must be auto -confirmed 00:07:19.009 --> 00:07:21.589 to create new articles. Auto -confirmed. Why 00:07:21.589 --> 00:07:24.709 does Wikipedia force a user to become auto -confirmed 00:07:24.709 --> 00:07:27.110 instead of just letting a team of paid moderators 00:07:27.110 --> 00:07:29.750 handle new Stadium articles? It's entirely an 00:07:29.750 --> 00:07:33.329 issue of scale. Wikipedia is too massive, operating 00:07:33.329 --> 00:07:35.930 in too many languages simultaneously, to ever 00:07:35.930 --> 00:07:38.829 rely on a centralized team of paid moderators. 00:07:38.970 --> 00:07:41.870 It would cost a fortune. A fortune. It relies 00:07:41.870 --> 00:07:45.750 entirely on crowdsourced labor. However, opening 00:07:45.750 --> 00:07:48.290 the floodgates to anonymous users, creating new 00:07:48.290 --> 00:07:50.930 pages, would result in the platform being instantly 00:07:50.930 --> 00:07:55.000 overwhelmed. Overwhelmed by what? Spambots. vandalism 00:07:55.000 --> 00:07:57.300 corporate marketing disguises articles ah so 00:07:57.300 --> 00:07:59.720 auto confirmed is basically an automated trust 00:07:59.720 --> 00:08:02.220 metric it is exactly that it means you can't 00:08:02.220 --> 00:08:04.220 just walk in off the street and break ground 00:08:04.220 --> 00:08:06.399 on a new article you have to earn your status 00:08:06.399 --> 00:08:09.120 first how do you do that usually that involves 00:08:09.120 --> 00:08:10.939 having an account that is a certain number of 00:08:10.939 --> 00:08:14.600 days old and having made a minimum number of 00:08:14.600 --> 00:08:18.060 smaller constructive edits to existing pages 00:08:18.060 --> 00:08:21.060 fixing typos adding citations that sort of thing 00:08:21.060 --> 00:08:23.300 so you prove you're a good citizen right Once 00:08:23.300 --> 00:08:25.779 you cross that threshold, the system trusts you 00:08:25.779 --> 00:08:28.540 enough to let you create something entirely new 00:08:28.540 --> 00:08:31.060 without immediate oversight. But if you haven't 00:08:31.060 --> 00:08:34.110 reached that elite status yet. The source shows 00:08:34.110 --> 00:08:36.730 that the platform does provide alternative paths. 00:08:37.070 --> 00:08:39.090 It doesn't just lock you out completely. Right. 00:08:39.269 --> 00:08:41.990 It says, alternatively, you can use the article 00:08:41.990 --> 00:08:45.330 wizard to submit a draft for review or request 00:08:45.330 --> 00:08:48.090 a new article. Yes. It feels a lot like city 00:08:48.090 --> 00:08:50.750 planning and zoning laws. That's a great way 00:08:50.750 --> 00:08:52.850 to put it. Like if you aren't a licensed contractor, 00:08:53.110 --> 00:08:55.370 you can't just pour concrete. You have to submit 00:08:55.370 --> 00:08:57.269 your blueprints to the zoning board, which is 00:08:57.269 --> 00:08:59.649 the article wizard, or you have to petition the 00:08:59.649 --> 00:09:02.730 city to build it for you. That is a highly accurate. 00:09:13.560 --> 00:09:16.860 So the draft just sits there? A draft submitted 00:09:16.860 --> 00:09:20.299 for review will sit in a queue until an experienced 00:09:20.299 --> 00:09:22.960 editor can vet your sources and ensure the formatting 00:09:22.960 --> 00:09:26.289 meets the encyclopedia's manual of style. You 00:09:26.289 --> 00:09:28.809 know, what's funny about this strict, almost 00:09:28.809 --> 00:09:31.909 governmental hierarchy of editors is that it 00:09:31.909 --> 00:09:34.909 exists on a page that also lets you play with 00:09:34.909 --> 00:09:36.950 visual settings like it's a social media profile 00:09:36.950 --> 00:09:40.610 from 2005. The customization is wild. The source 00:09:40.610 --> 00:09:42.769 lists all these user interface toggles sitting 00:09:42.769 --> 00:09:45.210 on the sidebar. You can change the text size 00:09:45.210 --> 00:09:47.830 from zero small, one standard, to two large. 00:09:48.029 --> 00:09:50.470 You can toggle the width between one standard 00:09:50.470 --> 00:09:52.809 and zero wide. Right. You can even play with 00:09:52.809 --> 00:09:55.659 the color beta settings. Automatic. light mode, 00:09:55.779 --> 00:09:58.120 or dark mode. You can customize the aesthetic 00:09:58.120 --> 00:10:00.779 of a page that contains absolutely zero information. 00:10:01.200 --> 00:10:03.419 That speaks to the decoupling of the user interface 00:10:03.419 --> 00:10:05.720 framework from the content itself. Decoupling. 00:10:05.759 --> 00:10:07.820 Yeah, the platform is designed so that the container 00:10:07.820 --> 00:10:10.620 remains consistent, accessible, and user -friendly, 00:10:10.759 --> 00:10:13.360 regardless of whether the database query is successful 00:10:13.360 --> 00:10:15.820 or not. So the wrapper's always there. Always. 00:10:16.490 --> 00:10:19.049 The overarching design philosophy dictates that 00:10:19.049 --> 00:10:21.490 the tools for accessibility, like high contrast 00:10:21.490 --> 00:10:24.450 dark mode or larger text for visually impaired 00:10:24.450 --> 00:10:27.730 users, must never disappear, even on an error 00:10:27.730 --> 00:10:29.629 page. That's actually really thoughtful design. 00:10:29.929 --> 00:10:32.690 It is. But within that rigid, accessible framework, 00:10:33.009 --> 00:10:35.230 there is a detail in the source that completely 00:10:35.230 --> 00:10:38.490 breaks the serious bureaucratic tone we've been 00:10:38.490 --> 00:10:41.059 talking about. Oh, the Easter egg. Yes. Right 00:10:41.059 --> 00:10:43.379 there in the sidebar navigation mixed in with 00:10:43.379 --> 00:10:45.960 the text and width settings is an option that 00:10:45.960 --> 00:10:49.919 reads birthday mode and in parentheses baby globe. 00:10:50.179 --> 00:10:53.340 Baby globe. And the source shows it toggled to 00:10:53.340 --> 00:10:56.820 one enabled. A baby globe. On a page explaining 00:10:56.820 --> 00:10:59.159 that a massive architectural structure cannot 00:10:59.159 --> 00:11:01.740 be found. It is a great reminder of the human 00:11:01.740 --> 00:11:04.240 element behind all this code. It really is. Open 00:11:04.240 --> 00:11:06.639 source development cultures are famous for burying 00:11:06.639 --> 00:11:09.259 quirky Easter eggs into massive serious projects. 00:11:09.440 --> 00:11:11.480 For all the talk. of cash purging and strict 00:11:11.480 --> 00:11:14.000 hierarchies of auto -confirmed editors, this 00:11:14.000 --> 00:11:16.639 infrastructure was built by programmers. Programmers 00:11:16.639 --> 00:11:18.600 who just want to have a little fun. Exactly. 00:11:19.460 --> 00:11:21.700 Programmers who occasionally decide to celebrate 00:11:21.700 --> 00:11:24.399 the platform's anniversary by swapping out the 00:11:24.399 --> 00:11:27.799 serious Wikipedia logo for a whimsical baby globe. 00:11:28.019 --> 00:11:30.919 But the source immediately grounds that whimsy 00:11:30.919 --> 00:11:33.700 back in reality. Of course it does. Down at the 00:11:33.700 --> 00:11:36.580 very bottom of the page, beneath the search bar 00:11:36.580 --> 00:11:39.940 and the baby globe toggle, we see a list of links 00:11:39.940 --> 00:11:42.720 that form the legal bedrock of the site. The 00:11:42.720 --> 00:11:46.059 fine print. It lists privacy policy about Wikipedia, 00:11:46.460 --> 00:11:49.700 disclaimers, contact Wikipedia, legal and safety 00:11:49.700 --> 00:11:52.620 contacts, code of conduct, developers, statistics, 00:11:53.100 --> 00:11:56.440 cookie statement. Mobile view. Which is a necessary 00:11:56.440 --> 00:11:59.019 buzzkill. Yeah, quite the list. You cannot run 00:11:59.019 --> 00:12:01.720 a top 10 global website that relies on millions 00:12:01.720 --> 00:12:04.120 of anonymous contributors without a massive legal 00:12:04.120 --> 00:12:06.279 safety net. That makes sense. That list of links 00:12:06.279 --> 00:12:08.879 represents international privacy laws, liability 00:12:08.879 --> 00:12:11.200 disclaimers protecting the host foundation from 00:12:11.200 --> 00:12:13.840 the content uploaded by users, and a strict code 00:12:13.840 --> 00:12:15.879 of conduct to govern the behavior of the editors 00:12:15.879 --> 00:12:17.610 we were just talking about. So the whimsical 00:12:17.610 --> 00:12:20.330 baby globe only exists because it is insulated 00:12:20.330 --> 00:12:22.970 by that heavy legal machinery. Precisely. Once 00:12:22.970 --> 00:12:25.549 we understand that machinery, we can look at 00:12:25.549 --> 00:12:27.809 how Wikipedia attempts to salvage your failed 00:12:27.809 --> 00:12:30.690 search. The page doesn't just say, we don't have 00:12:30.690 --> 00:12:33.610 it, go away. It acts as a traffic cop. Yes. It 00:12:33.610 --> 00:12:36.289 explicitly points you toward its extended universe. 00:12:36.370 --> 00:12:39.549 It says, look for Pirata Fuente Stadium on one 00:12:39.549 --> 00:12:42.350 of Wikipedia's sister projects. Right. Now, most 00:12:42.350 --> 00:12:44.350 of us have stumbled onto Wiktionary at some point, 00:12:44.470 --> 00:12:46.929 but what's fascinating here is the triage system 00:12:46.929 --> 00:12:49.929 routing your query to specialized databases. 00:12:50.669 --> 00:12:54.110 It reveals how the platform categorizes all of 00:12:54.110 --> 00:12:58.129 human thought. The main site, Wikipedia, is strictly 00:12:58.129 --> 00:13:00.870 for encyclopedic knowledge. The history, the 00:13:00.870 --> 00:13:03.389 context, the significance of a thing. The big 00:13:03.389 --> 00:13:05.750 picture. Right. But human knowledge is broader 00:13:05.750 --> 00:13:07.610 than that, so they build an entire constellation 00:13:07.610 --> 00:13:10.490 of other databases with entirely different standards 00:13:10.490 --> 00:13:12.950 of inclusion. Let's look at the specific platforms 00:13:12.950 --> 00:13:15.450 it suggests in the source because it gets incredibly 00:13:15.450 --> 00:13:17.450 granular. It tells you to check wiktionary for 00:13:17.450 --> 00:13:19.990 dictionary definitions. It points to wiki books 00:13:19.990 --> 00:13:22.210 for textbooks and wiki quote for quotations. 00:13:22.289 --> 00:13:24.350 Yes. Why go through the effort of separating 00:13:24.350 --> 00:13:26.350 a dictionary from an encyclopedia in the first 00:13:26.350 --> 00:13:28.529 place? Because they serve fundamentally different 00:13:28.529 --> 00:13:31.429 linguistic purposes. An encyclopedia article 00:13:31.429 --> 00:13:34.590 explains the concept or the thing itself. The 00:13:34.590 --> 00:13:36.750 stadium's architecture, its history, its tenant 00:13:36.750 --> 00:13:39.409 teams. Right. A dictionary entry explains the 00:13:39.409 --> 00:13:42.570 word itself. It's etymology, it's pronunciation, 00:13:42.870 --> 00:13:45.470 it's translation into other languages. So if 00:13:45.470 --> 00:13:47.110 it doesn't deserve a history essay, it might 00:13:47.110 --> 00:13:50.149 just need a spelling guide. Exactly. If your 00:13:50.149 --> 00:13:52.210 search doesn't warrant a full historical article, 00:13:52.470 --> 00:13:54.830 the system routes you to Wiktionary just in case 00:13:54.830 --> 00:13:56.450 you were simply trying to find out how to spell 00:13:56.450 --> 00:14:00.789 or translate Paradafuente. It also suggests Wikisource, 00:14:01.049 --> 00:14:03.789 which it labels as the library, and Wikiversity 00:14:03.789 --> 00:14:06.330 for learning resources. It points to Commons 00:14:06.330 --> 00:14:09.610 for media. Commons is huge. So the article about 00:14:09.610 --> 00:14:11.730 the stadium might not exist, but someone might 00:14:11.730 --> 00:14:14.090 have uploaded a photograph of the physical building 00:14:14.090 --> 00:14:16.830 into the Commons database. Right, or an architect 00:14:16.830 --> 00:14:18.710 might have uploaded a public domain blueprint 00:14:18.710 --> 00:14:21.549 to Wikisource. And then it lists the truly niche 00:14:21.549 --> 00:14:25.490 databases, Wikivoyage for a travel guide, Wikinews 00:14:25.490 --> 00:14:28.649 for a news source, Wikidata as a link database. 00:14:28.750 --> 00:14:32.509 And finally, wiki species, defined as a species 00:14:32.509 --> 00:14:34.769 directory. A species directory. Now, obviously, 00:14:34.970 --> 00:14:37.529 a concrete sports stadium isn't going to be found 00:14:37.529 --> 00:14:40.509 in a biological species directory. But the routing 00:14:40.509 --> 00:14:42.789 algorithm doesn't know what a Parada Fuente is. 00:14:42.929 --> 00:14:45.789 It is entirely agnostic. It's just guessing. 00:14:45.990 --> 00:14:49.179 It just knows a query failed? And it is offering 00:14:49.179 --> 00:14:52.980 you every single taxonomic bucket it has. It 00:14:52.980 --> 00:14:55.539 demonstrates an incredibly thorough methodology. 00:14:56.200 --> 00:14:58.340 Before we declare this search a total failure, 00:14:58.539 --> 00:15:00.539 let's check the dictionary, the library, the 00:15:00.539 --> 00:15:03.500 newswire, the photo archive, and yes, even the 00:15:03.500 --> 00:15:06.320 biology files. Just in case Parada Fuente is 00:15:06.320 --> 00:15:09.100 a rare bird. Exactly. So when you look at the 00:15:09.100 --> 00:15:11.870 totality of the source document. What is the 00:15:11.870 --> 00:15:14.629 ultimate takeaway? You sent us a file expecting 00:15:14.629 --> 00:15:17.129 to learn about a stadium in Mexico, and instead, 00:15:17.389 --> 00:15:20.110 we ended up analyzing the structural, legal, 00:15:20.210 --> 00:15:22.490 and philosophical foundations of the Internet's 00:15:22.490 --> 00:15:25.009 largest knowledge base. The takeaway is that 00:15:25.009 --> 00:15:27.629 a digital dead end is rarely just an empty space. 00:15:27.809 --> 00:15:29.830 Right. When we hit a page not found error online, 00:15:30.169 --> 00:15:32.750 our instinct is to simply close the tab and move 00:15:32.750 --> 00:15:34.929 on. But when you actually read the text of the 00:15:34.929 --> 00:15:37.889 void, you find a blueprint. It's a map. The page 00:15:37.889 --> 00:15:40.299 is packed with instructions. insights into database 00:15:40.299 --> 00:15:43.580 management, evidence of editorial history, and 00:15:43.580 --> 00:15:45.940 clear pathways to contribute. And that is something 00:15:45.940 --> 00:15:48.080 I want to point out directly to you, the listener, 00:15:48.240 --> 00:15:50.580 because when you look closely at the language 00:15:50.580 --> 00:15:53.019 in this source, It was a personalized invitation. 00:15:53.440 --> 00:15:55.779 It really was. The page wasn't just rejecting 00:15:55.779 --> 00:15:58.419 your query. It was looking at your specific search 00:15:58.419 --> 00:16:00.740 for this stadium and telling you that if you 00:16:00.740 --> 00:16:02.679 want this place to exist in the digital record, 00:16:02.919 --> 00:16:05.259 you have the tools to put it there. You can build 00:16:05.259 --> 00:16:07.620 it. You can log in, you can learn the zoning 00:16:07.620 --> 00:16:10.240 laws of the article wizard, and you can build 00:16:10.240 --> 00:16:13.659 it. It is a reminder that the internet isn't 00:16:13.659 --> 00:16:16.620 just a product we consume. It is an infrastructure 00:16:16.620 --> 00:16:19.500 we are constantly asked to construct. That is 00:16:19.500 --> 00:16:22.659 a profound way to contextualize it. And if we 00:16:22.659 --> 00:16:25.559 look at one final, very subtle feature in the 00:16:25.559 --> 00:16:28.419 sidebar of this source, it offers a fascinating 00:16:28.419 --> 00:16:30.080 thought experiment about how that construction 00:16:30.080 --> 00:16:32.179 happens. What feature is that? Under the tools 00:16:32.179 --> 00:16:34.620 section, there's an action link that simply reads, 00:16:34.740 --> 00:16:37.019 what links here? What links here? What does that 00:16:37.019 --> 00:16:39.580 actually do on a page that doesn't exist? It 00:16:39.580 --> 00:16:41.820 reveals the invisible architecture of the web. 00:16:42.360 --> 00:16:45.059 Even though the central article for Parada Fuentes 00:16:45.059 --> 00:16:48.679 Stadium has not been written yet, clicking. What 00:16:48.679 --> 00:16:51.179 links here would likely reveal dozens of existing 00:16:51.179 --> 00:16:53.460 articles that are already pointing toward it? 00:16:53.539 --> 00:16:55.820 How is that possible if the page isn't there? 00:16:56.139 --> 00:16:58.379 Because the surrounding context already exists. 00:16:58.840 --> 00:17:01.080 The article for the city where the stadium is 00:17:01.080 --> 00:17:03.840 located likely have a hyperlink ready to go. 00:17:03.940 --> 00:17:06.359 Oh, wow. The biographies of the football players 00:17:06.359 --> 00:17:08.940 who scored goals on that pitch probably have 00:17:08.940 --> 00:17:11.480 hyperlinks pointing to the stadium. The historical 00:17:11.480 --> 00:17:13.759 records of the sports leagues have links waiting 00:17:13.759 --> 00:17:16.500 in their tables. So all of these active, fully 00:17:16.500 --> 00:17:19.640 written pages have coded pathways pointing to 00:17:19.640 --> 00:17:21.859 a destination that hasn't been built yet. Yes. 00:17:22.059 --> 00:17:25.099 A ghost network of hyperlinks. A ghost network. 00:17:25.299 --> 00:17:27.940 That is incredible. The web is essentially full 00:17:27.940 --> 00:17:30.640 of these empty lots. The roads leading to the 00:17:30.640 --> 00:17:32.900 stadium are already paved. The infrastructure 00:17:32.900 --> 00:17:36.019 surrounding it is fully developed. The hyperlinks 00:17:36.019 --> 00:17:38.380 are just sitting there marked in red text, waiting 00:17:38.380 --> 00:17:40.740 patiently in the dark. Just waiting. All it takes 00:17:40.740 --> 00:17:43.740 is for someone... Perhaps the person who initiated 00:17:43.740 --> 00:17:45.940 this search to begin with, to finally lay the 00:17:45.940 --> 00:17:49.119 foundation, write the first sentence, and suddenly, 00:17:49.240 --> 00:17:52.299 that entire ghost network illuminates and connects. 00:17:52.579 --> 00:17:54.960 That completely changes how I view an error page. 00:17:55.319 --> 00:17:57.559 The roads are paved, they're just waiting for 00:17:57.559 --> 00:18:00.140 someone to build the stadium. Exactly. Thank 00:18:00.140 --> 00:18:02.779 you so much for sending this source in. It forced 00:18:02.779 --> 00:18:04.880 us to look at the internet from an entirely new 00:18:04.880 --> 00:18:07.220 perspective, proving that sometimes the absence 00:18:07.220 --> 00:18:09.339 of information is just as fascinating as the 00:18:09.339 --> 00:18:12.680 information itself. Until next time, keep exploring 00:18:12.680 --> 00:18:13.319 the blank spaces.