WEBVTT 00:00:00.000 --> 00:00:03.540 Imagine walking into like the world's largest 00:00:03.540 --> 00:00:06.280 most prestigious library You walk right up to 00:00:06.280 --> 00:00:09.539 the front desk and ask the librarian for a very 00:00:09.539 --> 00:00:14.019 specific book, okay? Let's say it's a book about 00:00:14.019 --> 00:00:17.019 Squirt the whale right a very specific whale 00:00:17.019 --> 00:00:19.600 Yeah, so the librarian taps on their computer 00:00:19.600 --> 00:00:22.120 looks up and instead of just saying, you know, 00:00:22.120 --> 00:00:24.859 we don't have it They hand you a blank blueprint. 00:00:25.160 --> 00:00:28.699 Oh wow and a hammer and this massive technical 00:00:28.699 --> 00:00:31.660 manual, plus a 500 -page legal rule book. That 00:00:31.660 --> 00:00:33.799 is quite the response. Right. And then they look 00:00:33.799 --> 00:00:36.060 you dead in the eye and ask, do you want to build 00:00:36.060 --> 00:00:37.979 the shelf and write the book yourself? I mean, 00:00:37.979 --> 00:00:40.560 it is a uniquely modern experience. We're so 00:00:40.560 --> 00:00:42.219 used to search engines either just giving us 00:00:42.219 --> 00:00:44.979 the exact answer or giving us a polite little 00:00:44.979 --> 00:00:47.159 error message. Exactly. But this system doesn't 00:00:47.159 --> 00:00:50.299 do that at all. It completely exposes its entire 00:00:50.299 --> 00:00:52.920 foundation. It totally does. And that is exactly 00:00:52.920 --> 00:00:54.820 what happened with the source document you, our 00:00:54.820 --> 00:00:57.689 listener, handed us today. You asked us to do 00:00:57.689 --> 00:01:00.250 a deep dive into a digital encyclopedia page 00:01:00.250 --> 00:01:02.630 for Squirt the Whale. Which is a great prompt, 00:01:02.909 --> 00:01:06.010 honestly. It is. We were totally ready for marine 00:01:06.010 --> 00:01:09.769 biology facts or maybe like a local legend about 00:01:09.769 --> 00:01:12.689 a captive animal. But we just hit a dead end. 00:01:12.890 --> 00:01:14.890 A very detailed dead end. Yeah, the page simply 00:01:14.890 --> 00:01:17.930 does not exist. However, the document you shared 00:01:17.930 --> 00:01:20.890 didn't just give us a standard 404 error. It 00:01:20.890 --> 00:01:22.930 gave us that exact blueprint I just talked about. 00:01:23.120 --> 00:01:25.420 So, okay, let's unpack this, because instead 00:01:25.420 --> 00:01:27.859 of a whale, we found the invisible scaffolding 00:01:27.859 --> 00:01:30.120 of how crowdsourced knowledge actually works. 00:01:30.359 --> 00:01:32.560 And I really invite you, listening right now, 00:01:32.640 --> 00:01:35.319 to just forget about Squirt the Whale for a moment. 00:01:35.659 --> 00:01:37.879 Sorry, Squirt. Right, sorry, Squirt. But look 00:01:37.879 --> 00:01:40.700 past the missing information, because what we 00:01:40.700 --> 00:01:43.579 are really exploring today is the architecture, 00:01:44.140 --> 00:01:46.560 the rigid rules, and the hidden mechanisms that 00:01:46.560 --> 00:01:48.900 govern what happens when human curiosity hits 00:01:48.900 --> 00:01:50.760 a digital wall. So let's start right at that 00:01:50.760 --> 00:01:52.579 wall, right at the top of the search result. 00:01:52.719 --> 00:01:55.540 the system delivers this incredibly specific, 00:01:55.739 --> 00:01:58.519 really rigid message. It says, in bold letters, 00:01:59.040 --> 00:02:00.939 Wikipedia does not have an article with this 00:02:00.939 --> 00:02:03.400 exact name. It's very blunt. It is. And I have 00:02:03.400 --> 00:02:05.299 to be honest, my first reaction was, wait, it 00:02:05.299 --> 00:02:07.780 has to be this exact name. That feels incredibly 00:02:07.780 --> 00:02:10.560 archaic for a modern search bar. How so? Well, 00:02:10.560 --> 00:02:13.379 usually if I misspell something or use a slightly 00:02:13.379 --> 00:02:15.900 wrong name, an algorithm just guesses what I 00:02:15.900 --> 00:02:17.879 meant, right? Just quietly fixes it and shows 00:02:17.879 --> 00:02:20.500 me the results. Right, it autocorrects. But what's 00:02:20.500 --> 00:02:22.979 fascinating here is that the system is deliberately 00:02:22.979 --> 00:02:26.580 choosing not to guess. Really? Yeah. It's admitting 00:02:26.580 --> 00:02:30.300 a failure based only on the exact literal parameters 00:02:30.300 --> 00:02:32.879 you provided. But it doesn't leave you hanging. 00:02:33.340 --> 00:02:36.039 It immediately pivots and starts coaching you 00:02:36.039 --> 00:02:38.400 on how to be a better digital detective. Oh, 00:02:38.400 --> 00:02:40.969 I see. It isn't just a dead end, it's a redirection. 00:02:41.449 --> 00:02:43.669 The very first thing it tells you to do is search 00:02:43.669 --> 00:02:47.389 for squirt the whale in existing articles. Which, 00:02:47.509 --> 00:02:49.150 you know, makes total sense. It's essentially 00:02:49.150 --> 00:02:51.210 saying, hey, maybe this whale isn't famous enough 00:02:51.210 --> 00:02:53.849 to get his own dedicated biography page, but 00:02:53.849 --> 00:02:56.090 maybe he's a footnote. Exactly. Like maybe he's 00:02:56.090 --> 00:02:57.889 mentioned in a broader article about a specific 00:02:57.889 --> 00:03:01.990 aquarium down in California or a historical marine 00:03:01.990 --> 00:03:04.969 rescue event. Precisely. It pushes you to think 00:03:04.969 --> 00:03:07.949 about the hierarchy of information. But the most 00:03:07.949 --> 00:03:10.590 revealing work around it offers is the prompt 00:03:10.590 --> 00:03:13.810 to look for pages that link to this title, the 00:03:13.810 --> 00:03:16.259 What Links Here tool. See, that part completely 00:03:16.259 --> 00:03:19.879 tripped me up. How on earth can a page link to 00:03:19.879 --> 00:03:22.180 a title that doesn't even exist yet? It's a bit 00:03:22.180 --> 00:03:24.759 counterintuitive, yeah. Right. If the Squirt 00:03:24.759 --> 00:03:27.159 the Whale page is just a phantom, how are there 00:03:27.159 --> 00:03:30.560 bridges pointing to it? Think of it as digital 00:03:30.560 --> 00:03:33.900 real estate speculation. OK. Speculation. Yeah. 00:03:34.139 --> 00:03:36.740 It happens constantly in these crowdsourced environments. 00:03:37.280 --> 00:03:39.719 An author of a completely different article. 00:03:40.280 --> 00:03:43.740 Maybe an article about a specific species of 00:03:43.740 --> 00:03:47.080 beluga whale might type the words, squirt the 00:03:47.080 --> 00:03:48.939 whale. Even though they know the page isn't there. 00:03:49.180 --> 00:03:51.379 Exactly. They know that page doesn't exist today, 00:03:51.719 --> 00:03:54.419 but they create a hyperlink for it anyway, anticipating 00:03:54.419 --> 00:03:57.719 that someone, someday, will write it. Oh wow. 00:03:57.960 --> 00:04:00.539 It creates what the community calls a red link. 00:04:00.729 --> 00:04:03.469 It's basically a bridge to nowhere, just waiting 00:04:03.469 --> 00:04:05.449 for the land to be built on the other side. So 00:04:05.449 --> 00:04:08.129 by suggesting you check what links here, the 00:04:08.129 --> 00:04:10.389 system is actually teaching you how to hunt for 00:04:10.389 --> 00:04:13.069 fragmented, anticipated knowledge. That is wild. 00:04:13.110 --> 00:04:15.969 It's essentially a map of human intentions. And 00:04:15.969 --> 00:04:18.430 the system treats this empty space as a physical 00:04:18.430 --> 00:04:20.709 object, too. It really does. If you look at the 00:04:20.709 --> 00:04:23.069 tools menu hidden over in the sidebar of this 00:04:23.069 --> 00:04:26.110 missing page, it gives you all these options 00:04:26.110 --> 00:04:29.149 for a void. Like what? Well, you have upload 00:04:29.149 --> 00:04:32.480 file, sure. But you also have printable version, 00:04:33.120 --> 00:04:36.420 page information, and get shortened URL. I mean, 00:04:36.639 --> 00:04:38.699 why would anyone need a shortened URL for a blank 00:04:38.699 --> 00:04:41.350 page? Because it tells you something vital about 00:04:41.350 --> 00:04:43.790 how this entire database is constructed. The 00:04:43.790 --> 00:04:45.870 interface isn't reacting to the content of the 00:04:45.870 --> 00:04:48.089 page, it's reacting to the container. The container. 00:04:48.269 --> 00:04:50.769 Right. The container exists in the database architecture. 00:04:51.129 --> 00:04:53.589 Even if the content inside it is literally zero, 00:04:53.970 --> 00:04:56.350 you can print the empty container. You can generate 00:04:56.350 --> 00:04:58.870 a link to the empty container. That's, yeah, 00:04:59.029 --> 00:05:00.930 that's fascinating. The structure of the library 00:05:00.930 --> 00:05:02.889 is absolute, regardless of whether there's actually 00:05:02.889 --> 00:05:05.769 a book on the shelf. So we have this empty, printable, 00:05:05.990 --> 00:05:08.720 linkable container. And the very next logical 00:05:08.720 --> 00:05:11.560 step the interface suggests is, hey, the container's 00:05:11.560 --> 00:05:13.860 empty. Why don't you fill it? Create the page. 00:05:14.240 --> 00:05:16.860 Seems simple enough. But when we actually look 00:05:16.860 --> 00:05:19.360 at the source material, it's really not that 00:05:19.360 --> 00:05:22.040 simple. I want to push back a little on the whole 00:05:22.040 --> 00:05:25.240 free encyclopedia that anyone can edit reputation 00:05:25.240 --> 00:05:28.959 because this document reveals some incredibly 00:05:28.959 --> 00:05:31.779 strict gatekeeping. It definitely does. It explicitly 00:05:31.779 --> 00:05:33.860 states that to create a new article, you need 00:05:33.860 --> 00:05:36.860 to log in or create an account. Right. But simply 00:05:36.860 --> 00:05:39.519 having an account isn't enough to just start 00:05:39.519 --> 00:05:41.620 publishing whatever you want. It specifically 00:05:41.620 --> 00:05:44.800 says you must be auto -confirmed. Auto -confirmed. 00:05:45.180 --> 00:05:47.800 So what does this all mean? It's a big hurdle. 00:05:48.220 --> 00:05:49.959 It sounds like you're getting a top secret security 00:05:49.959 --> 00:05:51.980 clearance just to talk about a marine mammal. 00:05:52.540 --> 00:05:55.740 It totally shatters the utopian illusion that 00:05:55.740 --> 00:05:57.860 anyone can just walk in off the virtual street 00:05:57.860 --> 00:06:00.560 and take their own page into the book. And that 00:06:00.560 --> 00:06:02.779 illusion really has to be shattered for the platform 00:06:02.779 --> 00:06:06.819 to survive. Auto -confirmed is a vital load -bearing 00:06:06.819 --> 00:06:09.319 design choice to prevent the site from devolving 00:06:09.319 --> 00:06:12.220 into absolute chaos. Because of trolls and spam? 00:06:12.620 --> 00:06:14.800 Exactly. It's a status threshold. It generally 00:06:14.800 --> 00:06:16.699 means an account has to be a certain number of 00:06:16.699 --> 00:06:18.899 days old and have made a certain number of minor 00:06:18.899 --> 00:06:21.759 acceptable edits to existing pages. You have 00:06:21.759 --> 00:06:24.540 to prove yourself. Yes. It's a mechanism to prove 00:06:24.540 --> 00:06:27.379 you aren't a spam bot, a corporate PR firm, or 00:06:27.379 --> 00:06:30.389 just a vandal. You have to prove your citizenship 00:06:30.389 --> 00:06:33.089 in this digital community before you get the 00:06:33.089 --> 00:06:35.730 keys to the printing press. But they don't completely 00:06:35.730 --> 00:06:38.990 lock the doors on newcomers, right? The text 00:06:38.990 --> 00:06:42.509 does offer an alternative. It says, alternatively, 00:06:42.689 --> 00:06:45.129 you can use the article wizard to submit a draft 00:06:45.129 --> 00:06:47.430 for review. Notice the shift in language there, 00:06:47.769 --> 00:06:50.889 though. Submit a draft for review. Right. If 00:06:50.889 --> 00:06:53.529 we look at the contribute sidebar, it uses this 00:06:53.529 --> 00:06:56.560 really warm, welcoming language, help. learn 00:06:56.560 --> 00:06:59.060 to edit, and a community portal. Sounds very 00:06:59.060 --> 00:07:01.220 inviting. Sounds incredibly democratic. Everyone 00:07:01.220 --> 00:07:02.839 sitting around a campfire sharing knowledge. 00:07:03.379 --> 00:07:05.500 But the second you actually try to push a brand 00:07:05.500 --> 00:07:08.720 new unverified topic into the public eye without 00:07:08.720 --> 00:07:11.500 that auto -confirmed status, the campfire just 00:07:11.500 --> 00:07:14.750 vanishes. Yep. You are funneled into the... Article 00:07:14.750 --> 00:07:17.810 Wizard, which sounds magical, but is actually 00:07:17.810 --> 00:07:20.490 just an editorial triage desk. That's a great 00:07:20.490 --> 00:07:23.329 way to put it. It perfectly illustrates the evolution 00:07:23.329 --> 00:07:25.649 of how we manage crowdsourced information at 00:07:25.649 --> 00:07:28.449 a massive scale. Like growing pains. Exactly. 00:07:28.910 --> 00:07:31.209 Twenty years ago, the Wild West approach worked 00:07:31.209 --> 00:07:33.209 because the volume was lower and the stakes were 00:07:33.209 --> 00:07:36.370 lower. Today, reality dictates that to maintain 00:07:36.370 --> 00:07:39.069 even a baseline of quality and trust, you need 00:07:39.069 --> 00:07:41.170 these layered permission systems. Yeah, that 00:07:41.170 --> 00:07:43.920 makes sense. The community portal is open to 00:07:43.920 --> 00:07:46.819 everyone, sure, but the actual publication of 00:07:46.819 --> 00:07:49.660 new truth requires passing through a hierarchy 00:07:49.660 --> 00:07:52.199 of trust. Okay, but let's imagine a scenario 00:07:52.199 --> 00:07:54.899 where someone did pass that test. Maybe they 00:07:54.899 --> 00:07:56.759 used the article wizard and waited for approval, 00:07:57.060 --> 00:07:59.540 or maybe they already had that coveted auto -confirmed 00:07:59.540 --> 00:08:02.160 status. Okay, they're in. Right. They hit publish 00:08:02.160 --> 00:08:05.000 on Squirt the Whale, but the page is still missing. 00:08:05.259 --> 00:08:08.100 Gah! This brings us to the troubleshooting section 00:08:08.100 --> 00:08:10.579 of our source document, which explains why a 00:08:10.579 --> 00:08:13.079 page might be entirely invisible even after it's 00:08:13.079 --> 00:08:15.779 been written. Here's where it gets really interesting. 00:08:15.980 --> 00:08:18.000 It talks about the physical limitations of the 00:08:18.000 --> 00:08:20.120 technology itself. The actual hardware. Yeah. 00:08:20.420 --> 00:08:22.860 It says, if a page was recently created here, 00:08:23.160 --> 00:08:25.019 it may not be visible yet because of a delay 00:08:25.019 --> 00:08:27.439 in updating the database. Wait a few minutes 00:08:27.439 --> 00:08:30.060 or try the purge function. The purge function. 00:08:30.300 --> 00:08:33.419 I mean, it sounds incredibly dramatic. The whale 00:08:33.419 --> 00:08:35.980 isn't on our scanners. Initialize the purge function. 00:08:36.399 --> 00:08:38.620 But what is actually happening there? Think of 00:08:38.620 --> 00:08:41.320 the database like a massive global restaurant 00:08:41.320 --> 00:08:44.200 chain. OK, I'm with you. The kitchen just updated 00:08:44.200 --> 00:08:47.620 the menu to include a new dish, Squirt the Whale. 00:08:48.000 --> 00:08:50.220 But the thousands of waiters out on the floor 00:08:50.220 --> 00:08:52.960 are still handing out the old printed menus they 00:08:52.960 --> 00:08:55.440 have in their pockets to save time. Because printing 00:08:55.440 --> 00:08:57.879 new ones constantly would be too slow. Right. 00:08:58.159 --> 00:09:00.960 In computing, that's called caching. storing 00:09:00.960 --> 00:09:03.200 a snapshot of the page so it loads instantly 00:09:03.200 --> 00:09:05.740 for the next user. But it means the waiters don't 00:09:05.740 --> 00:09:08.039 know the new dish exists yet. So they're basically 00:09:08.039 --> 00:09:10.200 serving an outdated reality to the customers. 00:09:10.519 --> 00:09:13.960 Exactly. This platform is so massive with so 00:09:13.960 --> 00:09:16.759 many interconnected server farms caching information 00:09:16.759 --> 00:09:19.419 globally that it actually takes time for a new 00:09:19.419 --> 00:09:22.059 reality to ripple across the network. So clicking 00:09:22.059 --> 00:09:24.220 the Perch function is essentially the manager 00:09:24.220 --> 00:09:26.620 yelling at every waiter to throw away their old 00:09:26.620 --> 00:09:29.620 menus, run back to the kitchen, and look at the 00:09:29.620 --> 00:09:32.460 most current up to the second chalkboard. It 00:09:32.460 --> 00:09:35.220 forces the server to clear its memory and fetch 00:09:35.220 --> 00:09:37.759 the absolute latest version of the database. 00:09:38.320 --> 00:09:41.090 That makes so much sense. We expect the internet 00:09:41.090 --> 00:09:44.269 to be this instantaneous fluid thing, but it's 00:09:44.269 --> 00:09:46.769 actually bound by the physical laws of updating 00:09:46.769 --> 00:09:49.169 servers. It really is. But then the document 00:09:49.169 --> 00:09:51.409 gives us another entirely different reason for 00:09:51.409 --> 00:09:54.570 a missing page. It says, titles on Wikipedia 00:09:54.570 --> 00:09:56.990 are case sensitive except for the first character. 00:09:57.450 --> 00:10:00.450 Ah, yes. And it tells the user to check alternative 00:10:00.450 --> 00:10:02.889 capitalizations and consider adding a redirect. 00:10:03.470 --> 00:10:05.289 I have to admit, I read that and thought, really? 00:10:05.580 --> 00:10:08.500 Why does the capital W in whale matter so much? 00:10:08.799 --> 00:10:10.419 Well, this raises an important question about 00:10:10.419 --> 00:10:12.639 the fundamental friction between human language 00:10:12.639 --> 00:10:14.919 and machine logic. OK. How so? You and I can 00:10:14.919 --> 00:10:17.639 look at squirt the whale with a lowercase w and 00:10:17.639 --> 00:10:20.279 scrape the whale with an uppercase w, and our 00:10:20.279 --> 00:10:22.919 brains instantly process them as the exact same 00:10:22.919 --> 00:10:25.360 concept. Right. We just use context clues. But 00:10:25.360 --> 00:10:27.740 to a literal database, they are not the same 00:10:27.740 --> 00:10:30.700 concept at all. A lowercase w and an uppercase 00:10:30.700 --> 00:10:33.480 w have entirely different binary codes. Oh, right. 00:10:33.860 --> 00:10:35.919 They are fundamentally different. different entities 00:10:35.919 --> 00:10:38.940 to the machine. And in an encyclopedia containing 00:10:38.940 --> 00:10:41.879 millions of entries, capitalization drastically 00:10:41.879 --> 00:10:44.840 changes meaning. Like what? Well, are you talking 00:10:44.840 --> 00:10:47.820 about the chemical polish with a capital P used 00:10:47.820 --> 00:10:50.059 to shine your shoe? Wait, no, lowercase p for 00:10:50.059 --> 00:10:52.750 shoe polish? Or the nationality? Polish with 00:10:52.750 --> 00:10:55.649 a capital P. Polish and polish, yes. The system 00:10:55.649 --> 00:10:58.669 demands rigid mathematical precision because 00:10:58.669 --> 00:11:01.769 human language is incredibly messy. Which brings 00:11:01.769 --> 00:11:03.730 us back to that redirect the source mentions. 00:11:03.889 --> 00:11:06.370 It says, consider adding a redirect here to the 00:11:06.370 --> 00:11:08.950 correct title. Redirects are basically the invisible 00:11:08.950 --> 00:11:11.570 glue of the internet. They act as translators 00:11:11.570 --> 00:11:14.470 between our messy human typing and the database's 00:11:14.470 --> 00:11:16.649 rigid rules. So they fix the binary problem. 00:11:16.809 --> 00:11:19.950 Exactly. If the official auto -confirmed page 00:11:19.950 --> 00:11:22.789 is squirt the whale with a capital W, a redirect 00:11:22.789 --> 00:11:25.470 is a tiny hidden script that catches anyone who 00:11:25.470 --> 00:11:28.110 typed it with a lowercase w or maybe even misspelled 00:11:28.110 --> 00:11:30.909 squirt and seamlessly teleports them to the right 00:11:30.909 --> 00:11:33.429 place. That's brilliant. It's the infrastructure 00:11:33.429 --> 00:11:36.269 that makes a rigid database feel intuitive to 00:11:36.269 --> 00:11:39.129 a human being. But what if it's not a caching 00:11:39.129 --> 00:11:42.629 delay and it's not a typo? The source document 00:11:42.629 --> 00:11:45.250 forces us to confront the darkest possibility. 00:11:45.559 --> 00:11:48.620 The graveyard. Yes, the graveyard. The final 00:11:48.620 --> 00:11:50.740 reason it gives for a missing page is, quote, 00:11:51.279 --> 00:11:53.879 if the page has been deleted, check the deletion 00:11:53.879 --> 00:11:56.860 log and see why was the page I created deleted? 00:11:57.279 --> 00:12:01.279 The deletion log. It is a permanent public record 00:12:01.279 --> 00:12:03.879 of everything the community decided did not belong. 00:12:04.220 --> 00:12:06.039 I mean, think about the human element of that 00:12:06.039 --> 00:12:07.860 for a second. Someone out there might have spent 00:12:07.860 --> 00:12:10.570 hours writing about this whale. Very true. They 00:12:10.570 --> 00:12:12.190 researched it, they formatted the text, they 00:12:12.190 --> 00:12:14.129 cited their sources, and then an auto -confirmed 00:12:14.129 --> 00:12:16.710 editor or a panel of reviewers comes along, looks 00:12:16.710 --> 00:12:19.149 at it, and decides it simply doesn't meet the 00:12:19.149 --> 00:12:21.809 criteria for notability. Yep. And with a few 00:12:21.809 --> 00:12:24.309 clicks, it's erased. Into the deletion log it 00:12:24.309 --> 00:12:27.470 goes. That's just devastating. It can be. But 00:12:27.470 --> 00:12:30.429 it highlights a crucial philosophical point about 00:12:30.429 --> 00:12:33.389 curating knowledge. Crowdsourcing isn't just 00:12:33.389 --> 00:12:35.450 about the frantic accumulation of information. 00:12:35.730 --> 00:12:38.190 It's equally about the aggressive pruning of 00:12:38.190 --> 00:12:42.100 it. Pruning. Like a garden. Exactly. A library 00:12:42.100 --> 00:12:44.500 that accepts every single scrap of paper handed 00:12:44.500 --> 00:12:46.639 to it isn't a library at all. It's a landfill. 00:12:46.940 --> 00:12:49.840 Yes, it's a landfill. The community has to constantly 00:12:49.840 --> 00:12:53.500 decide what isn't knowledge, or at least what 00:12:53.500 --> 00:12:55.899 isn't suitable for this specific format. Which 00:12:55.899 --> 00:12:58.639 is actually the perfect bridge to the next section 00:12:58.639 --> 00:13:00.960 of our source material. Because if Squirt the 00:13:00.960 --> 00:13:03.320 Whale gets tossed into this deletion log because 00:13:03.320 --> 00:13:05.679 he doesn't meet the stripped encyclopedia criteria, 00:13:06.200 --> 00:13:08.740 Does that mean his digital existence is completely 00:13:08.740 --> 00:13:11.220 erased? Not necessarily. Right, the interface 00:13:11.220 --> 00:13:14.419 actually offers a safety net. It reveals a massive 00:13:14.419 --> 00:13:17.220 parallel universe of other databases. To sister 00:13:17.220 --> 00:13:19.360 projects? Exactly. The prompt right in the middle 00:13:19.360 --> 00:13:22.039 of this dead end page says, look for squirt the 00:13:22.039 --> 00:13:24.179 whale on one of Wikipedia's sister projects. 00:13:24.720 --> 00:13:27.200 and it lists 10 distinct platforms. That's a 00:13:27.200 --> 00:13:29.860 lot of platforms. It is. It lists Wiktionary, 00:13:30.120 --> 00:13:33.059 Wikibooks, Wikiquote, Wikisource, Wikiversity, 00:13:33.559 --> 00:13:36.759 Commons, Wikivoyage, Wikinews, Wikidata, and 00:13:36.759 --> 00:13:38.840 Wikispecies. If we connect this to the bigger 00:13:38.840 --> 00:13:41.059 picture, this list is profound. It proves that 00:13:41.059 --> 00:13:43.620 what we casually call knowledge is not a monolith. 00:13:43.980 --> 00:13:46.460 It is highly decentralized. Break that down for 00:13:46.460 --> 00:13:50.240 me. Why separate them? Why not just have one 00:13:50.240 --> 00:13:53.019 massive website with absolutely everything on 00:13:53.019 --> 00:13:55.580 it? Because... Different types of knowledge require 00:13:55.580 --> 00:13:57.580 entirely different architectural structures. 00:13:57.679 --> 00:14:00.159 OK. Take Wiktionary, for example. That's for 00:14:00.159 --> 00:14:03.440 lexical data. It defines what a word means. It's 00:14:03.440 --> 00:14:06.379 etymology. It's pronunciation. It doesn't care 00:14:06.379 --> 00:14:08.179 about the history of the thing, just the word 00:14:08.179 --> 00:14:10.710 itself. That's a dictionary. Wikidata, on the 00:14:10.710 --> 00:14:13.970 other hand, is ontological. It's pure structured 00:14:13.970 --> 00:14:16.490 data meant to be read by machines and algorithms, 00:14:16.730 --> 00:14:20.409 not humans. And commons is strictly for media 00:14:20.409 --> 00:14:22.909 files, photographs, audio clips. So if squirt 00:14:22.909 --> 00:14:25.629 is just a funny slang term someone made up for 00:14:25.629 --> 00:14:29.009 a water gun, he goes to wiktionary. Yes. If squirt 00:14:29.009 --> 00:14:31.769 the whale is an actual documented biological 00:14:31.769 --> 00:14:34.740 specimen, he belongs in wiki species. or maybe 00:14:34.740 --> 00:14:36.919 there's no article at all, and Squirt is just 00:14:36.919 --> 00:14:39.259 a really fantastic photograph of a beluga whale 00:14:39.259 --> 00:14:41.419 blowing bubbles. In that case, he belongs in 00:14:41.419 --> 00:14:43.899 commons. That makes total sense. Exactly. If 00:14:43.899 --> 00:14:46.539 you tried to force dictionary definitions, raw 00:14:46.539 --> 00:14:48.899 machine data, travel guides, and photographs 00:14:48.899 --> 00:14:52.539 all into one single encyclopedic format, the 00:14:52.539 --> 00:14:55.100 entire system would collapse under its own contradictory 00:14:55.100 --> 00:14:57.139 rules. It would be a mess. An absolute mess. 00:14:57.740 --> 00:15:00.440 By pushing you toward the sister projects, the 00:15:00.440 --> 00:15:03.220 system is forcing you to define the nature of 00:15:03.220 --> 00:15:05.899 the information you are seeking. It's asking 00:15:05.899 --> 00:15:09.320 the user, are you looking for a definition, a 00:15:09.320 --> 00:15:13.220 data point, a picture? Wow. It is stealth media 00:15:13.220 --> 00:15:15.779 literacy training, basically disguised as a 4 00:15:15.779 --> 00:15:17.899 -4 error page. That's a brilliant way to look 00:15:17.899 --> 00:15:20.330 at it. Now, we've spent all this time dissecting 00:15:20.330 --> 00:15:22.330 the center of this page, the search results, 00:15:22.490 --> 00:15:24.830 the rules, the sister projects. The core mechanics. 00:15:25.110 --> 00:15:27.289 Right. But if we zoom out and look at the wrapper 00:15:27.289 --> 00:15:29.750 around all of this, the source document gives 00:15:29.750 --> 00:15:32.250 us a very clear picture of the user environment 00:15:32.250 --> 00:15:34.509 itself, the physical interface where all of this 00:15:34.509 --> 00:15:36.470 governance is actually happening. The menus and 00:15:36.470 --> 00:15:38.350 settings. Yeah. Up at the top, you have your 00:15:38.350 --> 00:15:41.289 standard main menu navigation, main page, contents, 00:15:41.590 --> 00:15:43.309 current events, random article. But right next 00:15:43.309 --> 00:15:45.669 to that, you have appearance settings. And this 00:15:45.669 --> 00:15:47.789 is where the platform suddenly shifts from being 00:15:47.789 --> 00:15:50.409 a rigid gatekeeper to a very accommodating host. 00:15:50.809 --> 00:15:52.889 It really does. It hands a surprising amount 00:15:52.889 --> 00:15:55.210 of control back to the user's local browser. 00:15:55.610 --> 00:15:58.450 What kind of control? Well, you can change the 00:15:58.450 --> 00:16:01.929 text size to small, standard, or large. You can 00:16:01.929 --> 00:16:05.409 change the width to standard or wide, basically 00:16:05.409 --> 00:16:08.129 stretching the content to fit your specific screen. 00:16:08.669 --> 00:16:10.730 You can even change the color scheme. It offers 00:16:10.730 --> 00:16:13.690 automatic, light mode, or dark mode. which really 00:16:13.690 --> 00:16:16.429 reflects a modern vital understanding of accessibility. 00:16:17.110 --> 00:16:19.370 Absolutely. The architects of this system recognize 00:16:19.370 --> 00:16:21.389 that reading an encyclopedia shouldn't be a one 00:16:21.389 --> 00:16:24.309 -size -fits -all physical experience. If you 00:16:24.309 --> 00:16:27.009 have visual impairments and need large text, 00:16:27.529 --> 00:16:29.850 or if you are researching in a dark room and 00:16:29.850 --> 00:16:32.750 need dark mode to avoid eye strain, the environment 00:16:32.750 --> 00:16:35.509 adapts to your physical reality. It's super practical. 00:16:35.610 --> 00:16:37.850 But then, nestled right in the middle of these 00:16:37.850 --> 00:16:40.789 incredibly practical accessibility -focused settings, 00:16:41.190 --> 00:16:43.779 there's this bizarre quirky option. Oh, I know 00:16:43.779 --> 00:16:45.299 what you're going to say. It's called birthday 00:16:45.299 --> 00:16:48.600 mode in parentheses baby globe. And it just has 00:16:48.600 --> 00:16:51.519 a simple binary toggle, zero for disabled or 00:16:51.519 --> 00:16:54.539 one for enabled. It's a delightful Easter egg, 00:16:54.779 --> 00:16:57.580 a reminder that for all its rigid rules and database 00:16:57.580 --> 00:17:00.200 caching, this system was built by human beings 00:17:00.200 --> 00:17:03.779 with a sense of humor. It is hilarious, but the 00:17:03.779 --> 00:17:06.740 humor creates this incredible whiplash when you 00:17:06.740 --> 00:17:08.799 scroll down to the absolute bottom of the page. 00:17:09.000 --> 00:17:11.519 and hit the footer. The fine print. Yes, the 00:17:11.519 --> 00:17:14.160 fine print. You go from birthday mode, baby globe, 00:17:14.759 --> 00:17:17.759 straight into the heavy, unyielding legal bedrock 00:17:17.759 --> 00:17:20.119 of the platform. You get the privacy policy, 00:17:20.440 --> 00:17:23.460 disclaimers, contact Wikipedia, legal and safety 00:17:23.460 --> 00:17:26.720 contacts, code of conduct, developers, statistics, 00:17:27.519 --> 00:17:30.519 and the cookie statement. It is a stark juxtaposition. 00:17:30.829 --> 00:17:33.109 But it perfectly encapsulates the dual nature 00:17:33.109 --> 00:17:36.109 of this entire digital ecosystem. How so? On 00:17:36.109 --> 00:17:39.349 the surface, the user interface is highly customizable, 00:17:39.650 --> 00:17:41.890 user -friendly, and occasionally playful. It 00:17:41.890 --> 00:17:43.869 wants you to feel comfortable. But underneath 00:17:43.869 --> 00:17:46.250 that customizable surface, rigidly enforcing 00:17:46.250 --> 00:17:49.150 the rules of the road, are the legal and ethical 00:17:49.150 --> 00:17:50.970 constraints. It's like painting the walls of 00:17:50.970 --> 00:17:53.089 a house. You can turn the background black. You 00:17:53.089 --> 00:17:54.849 can make the font massive. You can turn on the 00:17:54.849 --> 00:17:57.230 baby globe. But you cannot touch the load -bearing 00:17:57.230 --> 00:18:00.109 pillars. Exactly. You are still bound by the 00:18:00.109 --> 00:18:02.650 code. of conduct. You are still operating under 00:18:02.650 --> 00:18:05.690 their privacy policy and disclaimers. Precisely. 00:18:05.960 --> 00:18:08.359 The platform grants you total autonomy over the 00:18:08.359 --> 00:18:10.940 visual rendering of the information, but it never 00:18:10.940 --> 00:18:14.059 lets you escape the legal and communal framework 00:18:14.059 --> 00:18:16.319 that makes the information possible in the first 00:18:16.319 --> 00:18:19.220 place. Right. The legal and safety contacts and 00:18:19.220 --> 00:18:22.059 the code of conduct in that footer are just as 00:18:22.059 --> 00:18:24.400 foundational to the encyclopedia as the server 00:18:24.400 --> 00:18:27.299 farms we talked about earlier. Without that legal 00:18:27.299 --> 00:18:30.339 and ethical bedrock, the trust that makes the 00:18:30.339 --> 00:18:32.640 community portal and the article wizard function 00:18:32.640 --> 00:18:35.839 would completely evaporate. That is so true. 00:18:36.240 --> 00:18:38.380 So when you submitted this source document about 00:18:38.380 --> 00:18:40.539 a missing whale, you probably just wanted to 00:18:40.539 --> 00:18:42.579 know if Scroot was a real animal. You probably 00:18:42.579 --> 00:18:44.819 didn't expect us to go this deep into the digital 00:18:44.819 --> 00:18:46.799 weeds. Probably not. But look at the journey 00:18:46.799 --> 00:18:49.319 this one dead link took us on. By hitting that 00:18:49.319 --> 00:18:52.299 wall, we got a master class in how human knowledge 00:18:52.299 --> 00:18:54.599 is structured, filtered, and governed in the 00:18:54.599 --> 00:18:57.700 modern age. We didn't find the whale, but we 00:18:57.700 --> 00:19:00.440 unpacked the article wizard. We did. We learned 00:19:00.440 --> 00:19:02.519 how to clear the cache with the purge function. 00:19:02.700 --> 00:19:06.200 We stared into the emotional abyss of the deletion 00:19:06.200 --> 00:19:09.740 log and we mapped out a sprawling decentralized 00:19:09.740 --> 00:19:12.380 universe of sister projects. It really serves 00:19:12.380 --> 00:19:14.579 as a powerful reminder that the internet isn't 00:19:14.579 --> 00:19:16.720 just a magical vending machine where you type 00:19:16.720 --> 00:19:19.680 a query and receive. a guaranteed fact. No, it's 00:19:19.680 --> 00:19:23.400 not. It is a constructed, curated and heavily 00:19:23.400 --> 00:19:26.980 regulated space. Every single piece of knowledge 00:19:26.980 --> 00:19:29.259 you consume on a platform like this has survived 00:19:29.259 --> 00:19:32.400 a rigorous, invisible gauntlet of human consensus 00:19:32.400 --> 00:19:35.099 and machine logic. It really makes you appreciate 00:19:35.099 --> 00:19:37.819 the pages that do exist, knowing the sheer amount 00:19:37.819 --> 00:19:40.269 of friction they had to overcome. just to render 00:19:40.269 --> 00:19:42.670 on your screen. It does. And if we can leave 00:19:42.670 --> 00:19:44.789 you with one final thought to mull over today, 00:19:44.990 --> 00:19:46.509 I want you to think back to that deletion log 00:19:46.509 --> 00:19:49.069 we discussed and those strict barriers of the 00:19:49.069 --> 00:19:51.670 auto -confirmed status. OK. If these are the 00:19:51.670 --> 00:19:53.829 necessary unyielding filters through which a 00:19:53.829 --> 00:19:56.170 topic must pass to become officially recognized 00:19:56.170 --> 00:19:58.809 digital knowledge, how much of human history, 00:19:58.990 --> 00:20:02.170 how much hyper -local culture, and how many fascinating 00:20:02.170 --> 00:20:04.349 niche interests are currently floating out there 00:20:04.349 --> 00:20:07.119 in the digital void? It's lost. lost forever 00:20:07.119 --> 00:20:09.680 simply because someone didn't survive the article 00:20:09.680 --> 00:20:12.140 wizard or because they capitalized at the wrong 00:20:12.140 --> 00:20:14.579 letter and no one was there to build a redirect. 00:20:14.880 --> 00:20:17.960 Wow. Think about that the next time you are searching 00:20:17.960 --> 00:20:20.099 for something and you get a page not found error. 00:20:20.839 --> 00:20:23.259 What history was almost there. It's a heavy thought. 00:20:23.619 --> 00:20:26.390 It really is. Thank you so much for providing 00:20:26.390 --> 00:20:28.670 such a uniquely revealing source document for 00:20:28.670 --> 00:20:31.710 us to explore today. Who knew an empty container 00:20:31.710 --> 00:20:34.210 could teach us so much about how we build the 00:20:34.210 --> 00:20:36.769 world? Truly fascinating. Remember to keep questioning, 00:20:37.210 --> 00:20:39.930 keep exploring, and keep looking for the invisible 00:20:39.930 --> 00:20:42.109 architecture hiding behind your favorite websites. 00:20:42.910 --> 00:20:44.369 We'll see you on the next Deep Dive.