How the Cloud became the new colony

 The infrastructure of extraction has moved from railways to data centres, but the logic remains the same.

This is the second piece in Empire of Code, a series that looks at how the digital world is quietly rewriting the story of power and dependence. The first empire ran on cotton and coal. The new one runs on clicks and code. When we understand this, we don’t just scroll smarter, we decide better.

In 1853, India’s first passenger train ran from Bombay to Thane. The British called it progress; history calls it extraction. Those gleaming locomotives weren’t laid to connect Indians to each other but to move India’s cotton, tea, and minerals to British ports. The infrastructure stayed; the wealth left.

Fast-forward to today. Our fiber-optic cables, data centres, and cloud servers promise connectivity and convenience. But once again, the direction of value is outward. The infrastructure stays; the wealth travels.

https://hackmd.io/@alexaa34/SkhmFPLOMe

https://medium.com/@alexharris59600/how-the-cloud-became-the-new-colony-5e70aeae06b2

The new railways


Sunita runs a small store in Bengaluru’s Shivajinagar. She accepts payments through Google Pay, manages inventory on WhatsApp Business, and advertises on Instagram. Her business hums on digital rails that feel empowering, efficient, modern.

But each transaction, each customer query, each inventory update flows to servers in Virginia and Oregon. There, her data trains algorithms that will serve businesses globally, while Sunita pays for the privilege with her behavioural information. The system improves with her labour; the profits accumulate elsewhere.

That’s data colonialism in motion: the empire of the cloud extracting value from everyday life while calling it service.


The invisible plantations


Behind every “smart” system is a hidden class of workers making it function. In Nairobi, content moderators earning less than $2 an hour watch beheadings and child abuse so Facebook’s algorithm can learn to filter them. In Manila, data annotators label images for pennies per thousand. In Hyderabad, customer-service agents soothe global consumers for platforms they’ll never own stock in.

The celebrated ChatGPT relied partly on Kenyan workers who spent months wading through humanity’s worst output, violence, abuse, hate, to teach the AI what to avoid. Many reported lasting psychological trauma. Their names appear in no credits. Their suffering is laundered into “artificial intelligence.”

These invisible labourers are the digital age’s plantation workers: essential but disposable. The pattern hasn’t changed; the periphery provides the raw labour while the centre reaps the reward.

We’re told the internet has made the world flat, a “global village.” But it’s a village where a handful of landlords Tenant Farmers on Digital Estates own all the land.

A Nigerian creator building a YouTube channel is, in effect, a tenant farmer on Google’s estate. She can plant (create content), harvest (earn views), even make a living. But she doesn’t own the platform, can’t negotiate her rent (platform fees), can’t appeal to a human when evicted, and wakes each day to find the landlord has rearranged the village overnight, new algorithms, new rules, no consultation.

Access feels equal; control is not.


The civilising mission, redux


Colonial powers justified conquest with noble intentions: progress, civilisation, education. Tech empires do it with connectivity and convenience.

Facebook says it wants to “connect the world.” Google vows to “organize the world’s information.” Amazon calls itself “Earth’s most customer-centric company.”


But whose world, whose information, whose customers?


When Facebook launched Free Basics in India, it promised free internet for the poor, but only within Facebook’s walled garden. The government rightly called it “digital colonialism in the garb of digital equality.” The script was old; only the medium had changed.

Comments

Popular posts from this blog

How to Activate Your Menards Card Online

Microsoft adds Windows protections for malicious Remote Desktop files

How to write technical blog posts that people actually read?