I built a tool that maps every GitHub user’s followers and followings onto a world map. Sounds simple, right? But the first time I saw the result, I felt a strange mix of fascination and unease.
There it was: a cluster of dots in San Francisco, another in Bangalore, a dense patch in Berlin, and a lonely spark in my own hometown. The internet promised a borderless world. But the code we write still has a zip code.
That’s the hidden truth this project exposes. I call it Audience Atlas. It’s a client-side React app that uses GitHub’s GraphQL API to fetch all followers and followings, then cross-references the missing data with the REST API (because GitHub’s API has a bug that drops some records). A custom geocoder parses each user’s location into a country. Imperfect, yes—but the success rate is high enough to reveal something profound.
Type in your username. Suddenly you see that your audience isn’t a flat list of avatars. It’s a geography of influence. Your open-source project isn’t global. It’s a network of regional hubs and diaspora highways.
Take a typical developer in the Bay Area. Their following map looks like a family reunion in Silicon Valley, with a few cousins in London and Sydney. A developer in Nairobi? Their followers cluster around East Africa, plus a straggler in Amsterdam. The pattern is unmistakable: where you are shapes who follows you.
This challenges the founding myth of open source—that code is a meritocracy, that talent and ideas cross borders frictionlessly. The data says otherwise. Open source isn’t global. It’s a collection of localized tribes connected by weak ties.
I saw this firsthand when I started mapping my own network. I’m based in Madagascar, a country not famous for its tech scene. Yet my followers include a surprising number from France and India—legacies of old colonial ties and diaspora networks. The map didn’t just show me who cares about my work. It showed me why they care. And that changed how I think about collaboration.
So what do you do with this information? If you’re building a project, stop assuming “everyone” will see it. Target your outreach to the regions where you already have a foothold. If you’re a maintainer, look at your following map: are you missing a continent? That’s a signal. Geography isn’t destiny, but ignoring it is a mistake.
This isn’t about surveillance or gatekeeping. It’s about seeing the hidden structure of our digital lives. Code is abstract, but coders are not. They live in cities, eat local food, and work in time zones. The map makes that reality impossible to ignore.
I’ve open-sourced the entire tool. Go ahead, enter your own username. You might be surprised by what you find. The internet is a place. Your code is a map of that place. And you’re standing in the middle of it.
FAQ
Q: What question would a skeptic ask?
A: Isn't this just a fancy way to display location data that's already public? The real insight is in the aggregation: seeing the density and patterns reveals biases and clusters that individual profiles hide. It's not about data, it's about the shape of the network.
Q: What's the practical implication?
A: If you're an open-source maintainer, use this map to decide where to focus your documentation translations, conference talks, or community outreach. Your project's adoption is not random—it follows geographic trails. Double down on your clusters, or deliberately build bridges to regions you're missing.
Q: What's the contrarian take?
A: The map may actually reinforce the myth of global meritocracy by making regional disparities visible. Some will use it to justify hiring from 'hotspots' only, or to assume that code from a certain country is better. That's a dangerous misinterpretation. The tool reveals a pattern, not a value judgment.