Skip to main content
THE WAY WE TELL THE STORIES

Whose river? Whose history?

A dam may appear in one archive as an engineering triumph, in another as a field lost, a village moved, or a river no longer open to fishing. We begin with those who lived with these changes.

History from the riverbank

We follow the lives of people who worked rivers, built water systems, resisted dispossession and preserved knowledge. Their testimony and local histories are not illustrations of somebody else's theory. They are part of the evidence itself.

Decisions have names

We identify the governments, armies, firms, treaties, financial institutions and policies behind the events. Colonial legacies and external intervention matter. So do decisions made by governments and movements after independence. Responsibility is traced from records, not assigned in advance.

Documents are not neutral

Official maps and administrative reports often record what rulers measured and omitted what communities knew. We read them critically beside local knowledge, oral history, Indigenous research and witnesses. No community exists only as a casualty count.

Freedom, not the appearance of calm

A ceasefire may stop gunfire without returning a well, a home or political authority. The stories examine who gains security, what remains unsettled, and how people have pursued land, dignity and control over water.

Our starting point is the essay Decolonising Water Diplomacy: From Tintin’s Gaze Back to Molana’s River and earlier research, including Nagheeby and Amezaga (2023) on equity and identity ↗, developed further in Nagheeby, Mason, Dajani and Hussein (2025) ↗

Begin with Palestine →

WHO GETS NAMED?

A water system does not destroy itself.

A passive sentence can turn a political decision into a natural disaster. Our stories name the authorities who ordered attacks, imposed restrictions, approved concessions or withheld permits whenever the documents allow it. We also check which communities were able to speak in the record and whose accounts were overlooked.

WITHOUT RESPONSIBILITY“Water supplies were disrupted in Raqqa.”
WITH A DOCUMENTED ACTOR“US-led coalition strikes damaged Raqqa’s urban infrastructure during the 2017 offensive.”Read the investigation ↗

Historian Assal Rad has documented how headlines can obscure who carried out violence. Her work on Palestine offers a way to scrutinise the language of conflict reporting; it does not replace checking original sources for every other country.

IN CONVERSATION · SEPTEMBER 2026

Assal Rad: who is missing from the headline?

In The Listening Post, Rad examines how journalistic word choices shape public understanding of violence in Palestine.

Read her published analysis ↗
THE PERSON BEHIND THE PROJECT

Created and edited by Mohsen Nagheeby.

Water Never Dies is an independent public-history and research project initiated by Dr Mohsen Nagheeby, a researcher and water-diplomacy practitioner. His work brings international water law, decolonising water diplomacy, environmental politics and the political economy of water into conversation with histories of colonial rule, resistance and people's knowledge of their rivers.

This website is his independent editorial project. It does not represent the official position of any university, employer or organisation, and it does not claim to speak on behalf of the communities whose histories and testimony it documents. Where possible, their accounts are attributed and linked in their own right.

Research enquiries, archive contributions and collaboration: Contact Mohsen Nagheeby via LinkedIn ↗.

EDITORIAL ACCOUNTABILITY

Living history. Checkable evidence. Open to correction.

Every historical reconstruction has limits. Archives can omit people and events; witnesses may remember differently; casualty figures and investigations can change as evidence develops. This project distinguishes archival record, attributed testimony, documented findings and editorial interpretation. Where figures differ, we try to identify who counted, when and how.

If you find an incorrect date, an unsupported attribution, a broken source, an image shown out of context or an important missing perspective, please send the passage and supporting evidence ↗. Material corrections will be reviewed and documented in the public editorial record. Serious errors will be corrected, not quietly defended.