WEBVTT 00:00:00.000 --> 00:00:03.620 Today, we are going to reconstruct two centuries 00:00:03.620 --> 00:00:07.919 of, well, a pretty bloody complex history using 00:00:07.919 --> 00:00:10.320 basically nothing. Right. Almost nothing at all. 00:00:10.480 --> 00:00:13.300 Welcome to today's Deep Dive. You, our listener, 00:00:13.539 --> 00:00:16.500 have handed us an incredibly wild source document 00:00:16.500 --> 00:00:18.920 to look at today. It really is. It looks like 00:00:18.920 --> 00:00:21.539 a mistake at first glance. Exactly. It is a single 00:00:21.539 --> 00:00:25.320 Wikipedia disambiguation page for the name Wang 00:00:25.320 --> 00:00:28.550 Yang. just three bullet points, a typo, and a 00:00:28.550 --> 00:00:30.829 website toggle switch for a baby globe. Which 00:00:30.829 --> 00:00:35.369 sounds completely absurd. It does. But our mission 00:00:35.369 --> 00:00:38.210 today is to look past that bare bones formatting, 00:00:38.329 --> 00:00:41.450 you know, and extract this sweeping 200 -year 00:00:41.450 --> 00:00:43.509 historical narrative that is just hiding right 00:00:43.509 --> 00:00:45.630 there in the metadata. And it is such an incredible 00:00:45.630 --> 00:00:48.289 exercise in reading the negative space of history 00:00:48.289 --> 00:00:50.710 because, I mean, a page like this functions as 00:00:50.710 --> 00:00:53.179 a kind of digital graveyard. I know. A digital 00:00:53.179 --> 00:00:55.600 graveyard. Yeah, or maybe more accurately, a 00:00:55.600 --> 00:00:58.299 historical waiting room. You have these individuals 00:00:58.299 --> 00:01:00.820 who have been stripped of all their worldly context. 00:01:00.840 --> 00:01:03.100 Right. They are reduced to just a name, a couple 00:01:03.100 --> 00:01:05.219 of dates, and a title, and they're just sitting 00:01:05.219 --> 00:01:08.120 in this blank digital void. I kept thinking of 00:01:08.120 --> 00:01:12.379 it kind of like a bizarre algorithmically enforced 00:01:12.379 --> 00:01:15.840 dinner party. A dinner party? I love that. Yeah, 00:01:15.840 --> 00:01:17.959 you have time travelers from completely different 00:01:17.959 --> 00:01:20.560 centuries forced to sit at the same table for 00:01:20.560 --> 00:01:22.930 eternity. simply because they are wearing the 00:01:22.930 --> 00:01:25.250 exact same name tag. Right. The algorithm just 00:01:25.250 --> 00:01:27.450 shoves them together. Exactly. They might have 00:01:27.450 --> 00:01:29.980 absolutely nothing else in common. But the architecture 00:01:29.980 --> 00:01:31.560 of the internet has trapped them in the same 00:01:31.560 --> 00:01:33.859 room. And the overarching theme we see when we 00:01:33.859 --> 00:01:36.400 really look closely at this room is the absolute 00:01:36.400 --> 00:01:38.939 flattening of human legacy. Flattening is the 00:01:38.939 --> 00:01:41.159 perfect word for it. It really is the defining 00:01:41.159 --> 00:01:44.540 feature of how the digital age catalogs the past. 00:01:45.140 --> 00:01:48.420 To understand how a sweeping, multi -generational 00:01:48.420 --> 00:01:52.680 legacy gets compressed into a few lines of open 00:01:52.680 --> 00:01:55.340 source text, we need to look at the physical 00:01:55.340 --> 00:01:59.170 realities of the people behind the name. chronological 00:01:59.170 --> 00:02:01.109 progression here through the Goryeo dynasty, 00:02:01.370 --> 00:02:03.870 right? Yes. Starting in the 11th century, the 00:02:03.870 --> 00:02:07.230 name Wang Yang tracks a very specific trajectory 00:02:07.230 --> 00:02:09.629 of power. And the first figure anchoring this 00:02:09.629 --> 00:02:13.629 legacy is Duke Nakrang. He lived from 1043 to 00:02:13.629 --> 00:02:16.650 1112. Which is a remarkable span for that era. 00:02:16.770 --> 00:02:19.210 Right, but his entire existence on this page 00:02:19.210 --> 00:02:23.889 is summarized by two words, just two words, Goryeo 00:02:23.889 --> 00:02:26.800 royalty. Which is wild, but if we look at the 00:02:26.800 --> 00:02:29.560 biological reality of those dates, surviving 00:02:29.560 --> 00:02:34.259 from 1043 to 1112 means Duke Nacrang lived for 00:02:34.259 --> 00:02:38.620 69 years. Which, back then, is huge. Huge. In 00:02:38.620 --> 00:02:41.360 the 11th century, reaching your late 60s is not 00:02:41.360 --> 00:02:43.379 just, you know, a matter of good genetics. It 00:02:43.379 --> 00:02:45.620 is a structural achievement. Right. It requires 00:02:45.620 --> 00:02:48.800 this insulated bubble of extreme privilege. Exactly. 00:02:48.879 --> 00:02:51.360 You need a dedicated apparatus for food security, 00:02:51.939 --> 00:02:53.939 constant protection from court violence. Court 00:02:53.939 --> 00:02:56.060 violence was no joke. Oh, absolutely. And you 00:02:56.060 --> 00:02:57.860 need the highest level of medical care available 00:02:57.860 --> 00:03:00.439 at the time. So that lifespan mechanically proves 00:03:00.439 --> 00:03:02.680 that royalty tag. Yeah, that makes sense. His 00:03:02.680 --> 00:03:05.900 title, Duke, establishes the base for the political 00:03:05.900 --> 00:03:08.639 capital of the Wang -Yang name in this era. He 00:03:08.639 --> 00:03:11.039 is an integral component of the ruling infrastructure. 00:03:11.319 --> 00:03:13.599 Right. He possesses immense institutional protection. 00:03:14.060 --> 00:03:16.560 But as I was looking at this, the timeline immediately 00:03:16.560 --> 00:03:19.219 presents us with this weird structural puzzle. 00:03:19.340 --> 00:03:23.020 The gap in the dates. Yes. Duke Nakrang dies 00:03:23.020 --> 00:03:26.539 in the year 1112. The very next person on this 00:03:26.539 --> 00:03:29.900 list, the second Wang Young, is born in 1126. 00:03:30.080 --> 00:03:33.259 14 years later. Exactly. A 14 -year gap between 00:03:33.259 --> 00:03:35.580 the death of the first Wang Young and the birth 00:03:35.580 --> 00:03:38.719 of the second. And I have to push back on the 00:03:38.719 --> 00:03:40.819 idea that this is just some random coincidence 00:03:40.819 --> 00:03:43.759 of birth. It rarely is with royalty. Right. When 00:03:43.759 --> 00:03:46.979 you are dealing with royal lineages, naming conventions 00:03:46.979 --> 00:03:50.349 are highly strategic. A 14 year gap feels like 00:03:50.349 --> 00:03:53.650 the precise operational timeline required for 00:03:53.650 --> 00:03:56.590 a name to transition from mourning to, like, 00:03:56.909 --> 00:03:59.189 historical reverence. And the mechanics of lineage 00:03:59.189 --> 00:04:02.229 management absolutely support that theory. In 00:04:02.229 --> 00:04:04.750 highly stratified royal families, a name carries 00:04:04.750 --> 00:04:06.729 immense political weight. You can't just throw 00:04:06.729 --> 00:04:09.090 it around. No, you really can't. Reusing the 00:04:09.090 --> 00:04:11.030 name of a prominent duke immediately after his 00:04:11.030 --> 00:04:12.930 death is often viewed as politically presumptuous. 00:04:12.969 --> 00:04:14.949 Oh, interesting. Or even a direct challenge to 00:04:14.949 --> 00:04:17.360 the immediate successor's authority. It can also 00:04:17.360 --> 00:04:19.879 be deemed spiritually unlucky. So it functions 00:04:19.879 --> 00:04:22.399 almost like retiring a jersey number in a sports 00:04:22.399 --> 00:04:25.100 franchise. That's a great analogy. But only temporarily. 00:04:25.779 --> 00:04:27.939 You pull the name Wang Young out of circulation. 00:04:28.439 --> 00:04:31.500 You let the immediate grief fade. The courtiers 00:04:31.500 --> 00:04:34.699 who serve the Duke, well, they age out of the 00:04:34.699 --> 00:04:37.259 system. Exactly. They retire or die off. And 00:04:37.259 --> 00:04:39.199 a decade and a half later, when a new child is 00:04:39.199 --> 00:04:42.199 born in 1126, the name has had enough time to 00:04:42.199 --> 00:04:45.379 cool off. The new Wang Yong isn't competing with 00:04:45.379 --> 00:04:47.680 the living, breathing memory of the Duke. Right. 00:04:47.680 --> 00:04:50.699 He is being positioned to embody a revered historical 00:04:50.699 --> 00:04:53.920 legacy instead. Precisely. It is a deliberate 00:04:53.920 --> 00:04:57.000 reactivation of political capital. And that reactivation 00:04:57.000 --> 00:04:58.959 brings us to the second figure in our timeline, 00:04:59.439 --> 00:05:02.259 who picks up the mantle in 1126. Count Gonghua? 00:05:02.459 --> 00:05:05.800 Yep. He lives from 1126 to 1186. And just like 00:05:05.800 --> 00:05:08.600 his predecessor, the database categorizes him 00:05:08.600 --> 00:05:12.170 identically as quote, Goryeo royalty. And here 00:05:12.170 --> 00:05:14.110 is where the digital flattening effect really 00:05:14.110 --> 00:05:16.670 starts to distort the history. How so? Well, 00:05:16.790 --> 00:05:19.290 we go from Duke Nakrang to Count Gangwa, to a 00:05:19.290 --> 00:05:21.329 modern English -speaking listener, moving from 00:05:21.329 --> 00:05:24.529 a duke to a count signals a demotion. Yeah, that 00:05:24.529 --> 00:05:27.350 was my first thought, too. Right, because in 00:05:27.350 --> 00:05:29.910 standard Western nobility frameworks, a duke 00:05:29.910 --> 00:05:33.269 holds way more territorial and political authority 00:05:33.269 --> 00:05:36.089 than a count. So the immediate assumption is 00:05:36.089 --> 00:05:38.810 that the Wang -Young brand lost some of its prestige 00:05:38.810 --> 00:05:41.720 over that 14 -year gap. But we are looking at 00:05:41.720 --> 00:05:44.300 this through a highly distorted translation lens, 00:05:44.360 --> 00:05:47.199 aren't we? We are hitting the ontological limits 00:05:47.199 --> 00:05:50.750 of modern databases. The Goryeo dynasty was a 00:05:50.750 --> 00:05:53.670 medieval Korean kingdom. Their socio -political 00:05:53.670 --> 00:05:55.970 structure just did not feature dukes and counts 00:05:55.970 --> 00:05:57.689 in the way the French or the English did. They 00:05:57.689 --> 00:05:59.889 didn't have a Western feudal system. Exactly. 00:05:59.970 --> 00:06:02.470 They operated on a highly nuanced indigenous 00:06:02.470 --> 00:06:05.509 system of aristocratic ranks, royal family branches, 00:06:05.910 --> 00:06:08.610 and bureaucratic titles. So when modern historians 00:06:08.610 --> 00:06:10.509 and database architects attempt to make this 00:06:10.509 --> 00:06:12.810 history legible to an English reading Wikipedia 00:06:12.810 --> 00:06:15.970 user, they are forced to map complex Eastern 00:06:15.970 --> 00:06:18.800 hierarchies onto Western equivalents. Yes. They 00:06:18.800 --> 00:06:21.259 shoehorn an entirely different cultural reality 00:06:21.259 --> 00:06:23.920 into a pre -existing European schema. So we actually 00:06:23.920 --> 00:06:26.240 have no way of knowing from this page whether 00:06:26.240 --> 00:06:29.079 Count Gangwa wielded less actual power than Duke 00:06:29.079 --> 00:06:32.319 Necrang. No way at all. or if the internal ranking 00:06:32.319 --> 00:06:34.740 architecture of the royal court simply evolved 00:06:34.740 --> 00:06:37.360 over the intervening century. But to the database, 00:06:37.740 --> 00:06:39.980 the distinction is entirely irrelevant. They 00:06:39.980 --> 00:06:42.199 are both just tossed into the generic bucket 00:06:42.199 --> 00:06:45.420 of Goryeo royalty. And that generic categorization 00:06:45.420 --> 00:06:47.980 strips away the entire lived experience of the 00:06:47.980 --> 00:06:51.620 individual. I mean, a 60 -year life of political 00:06:51.620 --> 00:06:55.100 maneuvering, shifting alliances, and court administration 00:06:55.100 --> 00:06:58.509 all reduced to a homogenized tag. But the raw 00:06:58.509 --> 00:07:01.370 chronological data manages to preserve a fascinating 00:07:01.370 --> 00:07:04.009 structural anomaly. Because while Count Gwanghwa 00:07:04.009 --> 00:07:06.670 is navigating the final years of his six -decade 00:07:06.670 --> 00:07:09.389 life, the timeline presents us with a physical 00:07:09.389 --> 00:07:11.870 collision. I love this part. The legacy of the 00:07:11.870 --> 00:07:14.329 name actually overlaps. It does. The logistical 00:07:14.329 --> 00:07:16.569 implications of this overlap are so fascinating. 00:07:16.870 --> 00:07:19.050 Right, because our third figure on the page is 00:07:19.050 --> 00:07:21.439 Wijong of Goryeo. And his title is The Ultimate 00:07:21.439 --> 00:07:23.860 Promotion. He is not a duke. He is not a count. 00:07:24.060 --> 00:07:26.660 He's categorized as Goryeo King, the big boss. 00:07:26.699 --> 00:07:30.759 He lives from 1181 to 1237. But and here's the 00:07:30.759 --> 00:07:34.000 twist, Count Gonwo doesn't die until 1186, which 00:07:34.000 --> 00:07:37.819 creates a documented five year window from 1181 00:07:37.819 --> 00:07:42.120 to 1186, where two royal Wang Youngs are physically 00:07:42.120 --> 00:07:44.699 alive and operating within the Goryeo dynasty 00:07:44.699 --> 00:07:47.240 simultaneously. Consider the practical reality 00:07:47.240 --> 00:07:49.420 of the royal court during that five year window. 00:07:49.680 --> 00:07:52.279 It plays out like a high -spakes historical sitcom 00:07:52.279 --> 00:07:55.180 scenario. It really does. You have Count Gangwa, 00:07:55.459 --> 00:07:58.319 this senior, esteemed royal in his late 50s. 00:07:58.500 --> 00:08:00.879 He's a respected elder statesman of the dynasty. 00:08:01.079 --> 00:08:03.220 An absolute pillar of the court. And somewhere 00:08:03.220 --> 00:08:05.639 else in the palace complex, there is a literal 00:08:05.639 --> 00:08:10.040 infant. A baby who is also named Wang Yong and 00:08:10.040 --> 00:08:12.180 who is structurally destined to become the supreme 00:08:12.180 --> 00:08:14.360 ruler of the nation. Yes, crawling around somewhere. 00:08:14.500 --> 00:08:17.439 Right. When court bureaucrats are drafting decrees 00:08:17.439 --> 00:08:19.759 or palace staff are delivering messages for Wang 00:08:19.759 --> 00:08:22.439 Yong, the royal infrastructure has to physically 00:08:22.439 --> 00:08:24.720 navigate the shared name. Between a senior count 00:08:24.720 --> 00:08:27.699 and a toggler future king. It is hilarious to 00:08:27.699 --> 00:08:30.439 picture, but it also highlights how a single 00:08:30.439 --> 00:08:33.259 name serves as a bridge across entirely different 00:08:33.259 --> 00:08:36.200 phases of the dynasty. For Kel Gangwa, those 00:08:36.200 --> 00:08:38.679 five years represent the twilight of his influence. 00:08:39.200 --> 00:08:42.039 But for the infant Huizhong, the name Wangyang 00:08:42.039 --> 00:08:44.779 is just beginning its ascent. So during this 00:08:44.779 --> 00:08:47.519 overlap, the name itself is essentially occupying 00:08:47.519 --> 00:08:49.620 two different spaces in the hierarchy at once. 00:08:49.940 --> 00:08:52.620 It tracks a clear trajectory. The name was established 00:08:52.620 --> 00:08:55.440 by a duke, maintained by a count, and ultimately 00:08:55.440 --> 00:08:58.139 achieves the crown. It reaches the absolute apex 00:08:58.139 --> 00:09:00.799 of sovereign power. And Huizhong holds on to 00:09:00.799 --> 00:09:03.519 that sovereign power until his death in 1237. 00:09:04.019 --> 00:09:06.039 So when you map it all out, we aren't just looking 00:09:06.039 --> 00:09:08.529 at three isolated bullet points anymore. No, 00:09:08.570 --> 00:09:11.730 the source document actually charts a 194 -year 00:09:11.730 --> 00:09:14.350 unbroken span of history. From the birth of Duke 00:09:14.350 --> 00:09:17.629 Necrang in 1043 to the death of King Huizhong 00:09:17.629 --> 00:09:21.470 in 1237. That is nearly two centuries of complex 00:09:21.470 --> 00:09:24.409 Goryeo statecraft, neatly packaged in about 30 00:09:24.409 --> 00:09:27.009 words. And that packaging brings us to the most 00:09:27.009 --> 00:09:29.570 conceptually jarring part of the source material. 00:09:29.730 --> 00:09:32.549 The metadata. Yeah. Because after we reconstruct 00:09:32.549 --> 00:09:35.710 this 194 -year physical history, we must examine 00:09:35.710 --> 00:09:38.110 the modern vessel that contains it. the digital 00:09:38.110 --> 00:09:40.830 skeleton of the disambiguation page itself. The 00:09:40.830 --> 00:09:43.169 architecture of the Internet, wrapping its code 00:09:43.169 --> 00:09:45.789 around 11th century Korean sovereignty. Exactly. 00:09:45.909 --> 00:09:49.350 The metadata is where the reality of our historical 00:09:49.350 --> 00:09:52.870 fragility becomes glaringly obvious. Right below 00:09:52.870 --> 00:09:55.950 the kings and counts, the page includes a C also 00:09:55.950 --> 00:09:58.230 section. Right. And the only entry it offers 00:09:58.230 --> 00:10:03.549 is a link to Wang Yong disambiguation. That is 00:10:03.549 --> 00:10:05.830 Wang Yong spelled with an O instead of an EO. 00:10:06.009 --> 00:10:08.259 It functions essentially as a digital traffic 00:10:08.259 --> 00:10:11.019 cop. The page is explicitly warning the user 00:10:11.019 --> 00:10:13.159 that an internal link might have incorrectly 00:10:13.159 --> 00:10:16.019 routed them to this specific waiting room. But 00:10:16.019 --> 00:10:18.279 the underlying mechanism of that warning is deeply 00:10:18.279 --> 00:10:21.419 profound. It demonstrates how utterly precarious 00:10:21.419 --> 00:10:23.840 historical memory is in a digitized world. Oh, 00:10:23.840 --> 00:10:26.000 it really is. I mean, you could be Duke Necrang. 00:10:26.120 --> 00:10:28.059 You could survive the brutal realities of the 00:10:28.059 --> 00:10:31.179 11th century for 69 years. You could be King 00:10:31.179 --> 00:10:34.279 Huanjong and rule an entire dynasty through divine 00:10:34.279 --> 00:10:36.360 right. Like the Meijiun armies. Yes. And yet, 00:10:36.559 --> 00:10:38.340 a modern researcher trying to study your legacy 00:10:38.340 --> 00:10:40.960 might miss your existence entirely, simply because 00:10:40.960 --> 00:10:43.500 their thumb slipped on a keyboard. Centuries 00:10:43.500 --> 00:10:47.320 of royal bloodlines, armies, and political maneuvering 00:10:47.320 --> 00:10:50.519 are entirely dependent on a single vowel keystroke. 00:10:50.700 --> 00:10:53.980 It is terrifying. The human legacy is entirely 00:10:53.980 --> 00:10:56.639 at the mercy of the search algorithm. And that 00:10:56.639 --> 00:10:58.899 algorithmic tension is visible in the hidden 00:10:58.899 --> 00:11:00.919 categories listed at the bottom of the source 00:11:00.919 --> 00:11:03.779 document too. Specifically, the category that 00:11:03.779 --> 00:11:06.500 flags, quote, short description is different 00:11:06.500 --> 00:11:08.600 from Wikidata. Right. I looked into the mechanics 00:11:08.600 --> 00:11:11.480 of that Wikidata discrepancy and it reveals this 00:11:11.480 --> 00:11:14.139 fascinating structural conflict. Yeah. Wikidata 00:11:14.139 --> 00:11:16.700 is the central storage system for the machine 00:11:16.700 --> 00:11:19.299 readable structured data used across Wikimedia 00:11:19.299 --> 00:11:22.039 projects. So when the short description on the 00:11:22.039 --> 00:11:24.139 English human readable page doesn't match the 00:11:24.139 --> 00:11:26.659 central Wikidata item, it essentially means the 00:11:26.659 --> 00:11:28.779 human archive is arguing with the machine archive. 00:11:28.879 --> 00:11:31.250 That is the perfect way to describe it. The algorithm 00:11:31.250 --> 00:11:33.950 is struggling to align the messy, nuanced reality 00:11:33.950 --> 00:11:37.129 of Goryeo royalty with a rigid, standardized 00:11:37.129 --> 00:11:40.190 queue identifier in the database. It is a fundamental 00:11:40.190 --> 00:11:42.389 misalignment between human history and machine 00:11:42.389 --> 00:11:45.750 logic. The database requires absolute categorization. 00:11:46.049 --> 00:11:48.929 Is this person a politician, a monarch, a military 00:11:48.929 --> 00:11:52.070 leader? But medieval Korean royalty rarely fits 00:11:52.070 --> 00:11:54.669 neatly into those binary modern data fields. 00:11:54.909 --> 00:11:57.669 Right. Even now, eight centuries later, the digital 00:11:57.669 --> 00:12:00.070 architecture is actively struggling to process 00:12:00.070 --> 00:12:02.769 who these people were. The curators of our metaphorical 00:12:02.769 --> 00:12:05.629 dinner party are arguing in the kitchen about 00:12:05.629 --> 00:12:08.190 how to properly format the menus for the time 00:12:08.190 --> 00:12:10.750 travelers. Exactly. And speaking of formatting, 00:12:11.049 --> 00:12:13.730 the absolute whiplash of the user interface options 00:12:13.730 --> 00:12:16.389 provided in this source document is incredible. 00:12:16.490 --> 00:12:19.169 Oh, it is so jarring. Right alongside. the birth 00:12:19.169 --> 00:12:22.149 and death dates of a 12th century king, the page 00:12:22.149 --> 00:12:25.149 presents the site appearance settings. The user 00:12:25.149 --> 00:12:29.750 is offered choices. Text, small, standard, large, 00:12:30.610 --> 00:12:33.360 color. automatic, light mode, dark mode. The 00:12:33.360 --> 00:12:35.620 interface completely democratizes the history. 00:12:35.960 --> 00:12:38.340 The user is granted total control over the visual 00:12:38.340 --> 00:12:41.360 presentation of the Goryeo dynasty. But the detail 00:12:41.360 --> 00:12:43.559 that truly underscores the absurdity of this 00:12:43.559 --> 00:12:46.200 digitization is the setting labeled birthday 00:12:46.200 --> 00:12:49.179 mode, baby globe. Yes. The source listed as a 00:12:49.179 --> 00:12:51.559 toggle switch, disabled or enabled. Think about 00:12:51.559 --> 00:12:53.580 the sheer cognitive dissonance of that interface. 00:12:53.759 --> 00:12:55.429 It's hard to wrap your head around. You have 00:12:55.429 --> 00:12:58.649 the majestic, heavily politicized, sovereign 00:12:58.649 --> 00:13:02.149 legacy of an ancient kingdom resting right next 00:13:02.149 --> 00:13:05.190 to a toggle switch for a baby globe. It proves 00:13:05.190 --> 00:13:07.450 that this history has been entirely divorced 00:13:07.450 --> 00:13:10.409 from its original context. The weight of human 00:13:10.409 --> 00:13:12.909 existence has been dropped into a standardized 00:13:12.909 --> 00:13:15.590 open source template. And the mechanics of that 00:13:15.590 --> 00:13:17.970 open source template? are legally codified at 00:13:17.970 --> 00:13:21.269 the very bottom of the page. The text explicitly 00:13:21.269 --> 00:13:23.990 states that all of this information is available 00:13:23.990 --> 00:13:26.730 under the Creative Commons Attribution Share 00:13:26.730 --> 00:13:29.570 Like 4 .0 license. Which is wild when you consider 00:13:29.570 --> 00:13:31.990 the philosophical implications of that licensing 00:13:31.990 --> 00:13:34.590 agreement. It is a massive paradigm shift in 00:13:34.590 --> 00:13:37.230 how we handle power, right? Absolutely. The lives 00:13:37.230 --> 00:13:40.009 of a duke, a count, and a king were defined by 00:13:40.009 --> 00:13:43.409 exclusivity. They wielded unshared power justified 00:13:43.409 --> 00:13:46.129 by divine right and enforced by military might. 00:13:46.250 --> 00:13:48.070 Their names were practically untouchable. But 00:13:48.070 --> 00:13:50.470 now, under a Creative Commons license, their 00:13:50.470 --> 00:13:53.649 entire legacy is freely licensable, shareable, 00:13:53.750 --> 00:13:55.889 and legally adaptable by anyone on earth with 00:13:55.889 --> 00:13:58.289 a Wi -Fi connection. That is crazy to think about. 00:13:58.490 --> 00:14:01.029 The structural exclusivity of their royalty has 00:14:01.029 --> 00:14:03.730 been completely neutralized by modern copyright 00:14:03.730 --> 00:14:05.870 law. They ruled through absolute divine right, 00:14:06.009 --> 00:14:08.210 and today their legacy is legally governed by 00:14:08.210 --> 00:14:11.370 the terms of use and privacy policy of a nonprofit 00:14:11.370 --> 00:14:13.610 tech organization based in San Francisco. It 00:14:13.610 --> 00:14:17.320 is the ultimate reduction of power. Yet, despite 00:14:17.320 --> 00:14:20.159 being reduced to open source data, the document 00:14:20.159 --> 00:14:22.700 proves that they haven't been abandoned. The 00:14:22.700 --> 00:14:25.299 source notes the exact time stamp when this digital 00:14:25.299 --> 00:14:29.799 monument was last touched. June 25, 2025 at 13 00:14:29.799 --> 00:14:33.379 .48 UTC. That time stamp is so vital. It means 00:14:33.379 --> 00:14:35.600 that on a specific afternoon in the summer of 00:14:35.600 --> 00:14:39.289 2025, A human, editor, or, you know, an automated 00:14:39.289 --> 00:14:41.549 maintenance bot cared enough about the formatting 00:14:41.549 --> 00:14:43.970 of these three names to execute an update. So 00:14:43.970 --> 00:14:45.909 the historical waiting room is not a derelict 00:14:45.909 --> 00:14:48.370 building? No, the floor is being swept, the digital 00:14:48.370 --> 00:14:50.690 lights are being kept on, the legacy, however 00:14:50.690 --> 00:14:53.289 flattened, is actively maintained. When we step 00:14:53.289 --> 00:14:55.049 back and review the mission we started with, 00:14:55.250 --> 00:14:56.950 the transformation of the source material is 00:14:56.950 --> 00:14:59.330 remarkable. We began with what appeared to be 00:14:59.330 --> 00:15:02.330 the driest document imaginable. A utilitarian 00:15:02.330 --> 00:15:04.990 navigational webpage featuring three bullet points. 00:15:05.309 --> 00:15:08.559 Right. But by examining the biological realities, 00:15:08.980 --> 00:15:10.960 the naming mechanics, and the digital infrastructure, 00:15:11.740 --> 00:15:15.799 we reconstructed a 194 -year physical journey. 00:15:16.200 --> 00:15:18.600 We watched the political capital of the name 00:15:18.600 --> 00:15:21.580 Wang -Yung incubate with the Duke, rest for a 00:15:21.580 --> 00:15:24.080 strategic 14 -year period, transition through 00:15:24.080 --> 00:15:26.919 account. and ultimately bridge a logistical overlap 00:15:26.919 --> 00:15:29.539 to crown a king. We trace nearly two centuries 00:15:29.539 --> 00:15:32.080 of complex hierarchy. And then we analyze the 00:15:32.080 --> 00:15:34.860 mechanics of how that sprawling history was eventually 00:15:34.860 --> 00:15:37.659 compressed, translated, and legally flattened 00:15:37.659 --> 00:15:40.179 into a few bytes of open source text governed 00:15:40.179 --> 00:15:43.179 by a toggle switch. It serves as a powerful reminder 00:15:43.179 --> 00:15:45.600 that there is no such thing as boring source 00:15:45.600 --> 00:15:48.840 material. A bare -bones disambiguation page isn't 00:15:48.840 --> 00:15:51.740 a dead end. It is a structural doorway. It really 00:15:51.740 --> 00:15:54.139 is. If you look closely at the gaps, the overlaps, 00:15:54.179 --> 00:15:56.659 and the metadata, the most mundane digital spaces 00:15:56.659 --> 00:15:58.899 are hiding centuries of interconnected human 00:15:58.899 --> 00:16:01.500 lifespans. It is a sobering realization regarding 00:16:01.500 --> 00:16:03.899 how history processes human existence, because 00:16:03.899 --> 00:16:05.919 ultimately time and technology will flatten all 00:16:05.919 --> 00:16:08.000 of us into data points. Which brings us to a 00:16:08.000 --> 00:16:10.419 final thought for you, our listener, to ponder 00:16:10.419 --> 00:16:13.500 as we close out this deep dive. We've spent this 00:16:13.500 --> 00:16:15.519 time analyzing the digital waiting room of the 00:16:15.519 --> 00:16:18.620 Wang Youngs, but consider the inevitable mechanics 00:16:18.620 --> 00:16:21.019 of your own legacy. That is a chilling thought. 00:16:21.379 --> 00:16:24.019 If historians or database algorithms 800 years 00:16:24.019 --> 00:16:27.139 from now were to generate a digital disambiguation 00:16:27.139 --> 00:16:30.080 page for you and all the diverse people across 00:16:30.080 --> 00:16:32.159 history who happen to share your exact name, 00:16:32.519 --> 00:16:35.379 What single standardized title and what brief 00:16:35.379 --> 00:16:37.840 date range would the algorithm use to summarize 00:16:37.840 --> 00:16:40.559 your entire complex existence? What a question. 00:16:40.779 --> 00:16:43.279 And as you picture that endless blank digital 00:16:43.279 --> 00:16:45.320 waiting room, who are the historical strangers 00:16:45.320 --> 00:16:47.299 you would be forced to sit next to for the rest 00:16:47.299 --> 00:16:47.779 of eternity?