Ghost Names: The Infrastructure of Empire That Refuses to Die
Official renaming cannot erase colonial place names because they exist as cognitive and navigational infrastructure, not merely ideas to be replaced.
When South Africa renamed Port Elizabeth Gqeberha in 2021, the old name persisted in shipping charts and maritime habits—a phenomenon the author terms the Rename Paradox. Naming is not a declarative act but an infrastructural one: it embeds identity into cognitive territory through repetition across systems. Colonial toponyms persist long after the political conditions that created them dissolve, governing how millions think about belonging. The quiet violence of toponymy lies not in the original act of naming, but in its maintenance through sheer repetition.
The Hidden Names That Claimed the World Before You
In February 2021, South Africa did something that looked, on paper, like a corrective. Port Elizabeth became Gqeberha. The change was official, gazetted, announced with ceremony. Indigenous names restored to a landscape that had been labeled by strangers. A small act of historical justice, or so the press releases suggested. Four years later, international shipping charts still list Port Elizabeth. Sailors who trained on British Admiralty maps do not consult South African government publications. The name persists in the cognitive infrastructure of global navigation, a ghost name that no amount of official decree has been able to exorcise. The port's old name now exists in two registers simultaneously: the one that appears on government letterhead, and the one that appears in the logbooks of ships that actually move through those waters. This is the Rename Paradox, and it reveals something uncomfortable about how we talk about decolonizing geography. We treat naming as an act of declaration—when a place gets a new name, we assume the old one loses its power. But names are not ideas. They are infrastructure. And infrastructure does not yield to ceremony. The psychology of toponymic ownership runs deeper than policy. When you name a place, you do not merely describe it. You project yourself into it. You assert presence. The explorer who names an island after his ship or himself is not making a neutral notation—he is planting a flag in the cognitive territory of everyone who will ever encounter that name. The British whalers who blanketed South Georgia with names like Grytviken, Stromness, and Leith Harbour were not lost in the naming. They were claiming. Every toponym was a small act of possession that required no treaty, no army, no vote. Just the willingness to write something down and let others repeat it. South Georgia's naming history is instructive precisely because it was so thorough. By the early twentieth century, the island had been mapped, renamed, and charted by Norwegian and British whaling interests with such consistency that the indigenous names—if any existed—had been thoroughly overwritten. The UK Antarctic Place-Names Committee now maintains these records with administrative precision, but the names themselves are artifacts of a specific historical moment: the moment when industrial whaling operations needed to locate themselves in space, and lacked any interest in what the space had been called before they arrived. What interests me about this process is not the original sin—explorers and colonizers have always named things—but the persistence. The political conditions that produced these names dissolved long ago. The whaling industry collapsed. The empires retreated. Yet the names remain, governing how millions of people think about who belongs in a place. This is the quiet violence of toponymy: the original act of naming requires power, but the maintenance of that name requires only repetition. Which brings us back to the Rename Paradox. When South Africa changed Port Elizabeth to Gqeberha, it performed an act of resistance against that repetition. But resistance to repetition is not the same as replacing it. The old name had been repeated for generations—in textbooks, in shipping logs, in the habits of millions of people who had grown up knowing that particular arrangement of letters. The new name had to fight against not just inertia but against the sheer cognitive weight of everything that had already been written. Renaming a place is not a naming act. It is an infrastructure act. And infrastructure, by its nature, is distributed across thousands of systems that do not communicate with each other. Maps are made by private companies, by governments, by hobbyists. Charts are maintained by naval authorities with their own protocols. GPS databases are updated on commercial timelines that have nothing to do with national policy. Textbooks are written by authors who may never learn that a change has occurred. Each of these systems must be individually updated, and each update requires someone, somewhere, to care enough to make it happen. This is why renaming efforts so frequently produce the opposite of their intended effect. The contested period—during which both names circulate—doubles the cognitive presence of the place. People must now learn two names instead of one. The old name does not disappear; it becomes the name that older people use, the name that appears in older documents, the name that sailors who trained before 2021 continue to use because their habits were formed before the change. The new name exists alongside the old one, and the old one persists in every context where the new one has not yet arrived. I find this genuinely fascinating from a scientific standpoint. It is a system-level failure that looks, at first glance, like a problem of will. Governments announce changes; people do not comply. But the non-compliance is not defiance. It is the natural behavior of distributed systems. No single authority controls the entire network of names. No single decree can reach every chart, every database, every mental habit. The renaming happens at the level of policy, but the names live at the level of practice, and practice changes slowly, locally, and without coordination. None of this means renaming is pointless. The alternative—that we leave names in place forever, that we accept the cognitive ownership of whoever arrived first—is worse. But we should be honest about what renaming can and cannot do. It can signal intention. It can begin the long process of shifting habits. It can give a new generation a name that reflects their own history rather than someone else's. What it cannot do, on its own, is change the infrastructure. That requires sustained effort across dozens of systems, none of which are under any single body's control. The deeper point is this: the power of names is not in their origin but in their adoption. A name means nothing until people repeat it. The explorer who named South Georgia's harbors understood this instinctively—he was not describing the landscape, he was colonizing the mental space that others would occupy when they thought about it. To rename is to attempt a counter-colonization of that mental space. But it is harder than the original colonization, because the original colonization has a head start measured in generations. The names we inherit are not neutral descriptions. They are the fingerprints of whoever possessed the power to project presence onto a landscape. The question is not whether we can rename things—the question is whether we understand that renaming requires rebuilding the entire system that sustains the old name. Until we treat toponymic change as infrastructure change, we will keep producing gestures rather than outcomes. And the ghost names will keep sailing on, long after the ceremonies have ended.