Time for a Digital Resistance

This is in response to the Trump administration’s censorship of the EPA, National Park Service, etc.

Mission: make every government attempt at knowledge suppression backfire.

* identify and expose every attempt at government knowledge suppression and propaganda (e.g. removal of climate science data from the EPA’s website)

* rescue the data (copy it to places outside the reach of the U.S. government — maybe archive.org already does this, maybe it needs help)

* provide easy access to the secure rescued copies of the data

* highlight before and after versions of the government’s position (e.g. a diff of the EPA website before Trump and after Trump)

The goal is to make censorship as counterproductive as possible.


The focus of this effort is against censorship, specifically censorship of scientific information (that is the immediate threat), and to expose propaganda against science in general. I think it needs to be narrowly focused to be effective, and shouldn’t spread out into a generalized anti-Trump political movement as there are plenty of those already.

Products: reference and editorial components

I see two main component artefacts (digital products) to this.

One is a reference section, possibly in wiki format, that acts as the clearinghouse or knowledge base. Every censorship or propaganda act captured here, with links to the rescued data, before and after comparisons, etc. Relatively free from editorial.

An editorial website to complement the reference. More easily accessible and with a conventional news or magazine website format. Used to highlight the more recent and/or egregious acts and provide analysis and explanation.

Branding and names

“Digital resistance” was just my initial thought in response to the Trump censorship. It’s kind of an broad name and it appears there’s a band of that name. The name could be more focused (against government censorship). In anycase, a domain name is needed.


Static websites make it easier to leverage CDNs and would be more resistant to DDOS type attacks. Any reason to not go static? What’s a good wiki static generator?

Needless to say the whole thing needs to be outside the grasp of the U.S. government (maybe outside the grasp of any government, if possible). Or do we need a trusted host nation for any reason?


This are just my initial, day one thoughts. Nothing is cast in stone. I don’t want to lead this effort, just contribute. If there’s an existing effort along these lines please point me to it.

For the immediate future communicate by responding to this medium post or email me at mediaobelia@gmail.com.


Like what you read? Give Mike Anderson a round of applause.

From a quick cheer to a standing ovation, clap to show how much you enjoyed this story.