---
title: "Warning - Don’t touch MindTouch Deki Wiki"
url: "https://osherove.com/blog/2010/5/29/warning-dont-touch-mindtouch-deki-wiki.md"
canonical: "https://osherove.com/blog/2010/5/29/warning-dont-touch-mindtouch-deki-wiki.html"
published: "2010-05-29T01:53:20"
updated: "2010-05-29T01:53:20"
tags: []
author: "Roy Osherove"
description: "I made the big mistake of hosting my book’s website wiki on MindTouch’s Deki Wiki ( http://*.wik.is ) Why was it a mistake? I started getting lots of SPAM in the wiki. That in itself isn’t really a MindTouch problem,…"
usage: "Licensed under CC BY 4.0 — reuse, quote and adapt with attribution (Roy Osherove, link to the original page)."
license: "https://creativecommons.org/licenses/by/4.0/"
---

# Warning - Don’t touch MindTouch Deki Wiki

By Roy Osherove May 29, 2010

**Historical article** · Originally published May 29, 2010; technical details may be outdated.

I made the big mistake of hosting [my book’s website wiki](http://artofunittesting.com/) on [MindTouch’s](http://www.mindtouch.com/) Deki Wiki ( [http://\*.wik.is](http://*.wik.is/))

Why was it a mistake?

I started getting lots of SPAM in the wiki. That in itself isn’t really a MindTouch problem, but how one handles spam in a Deki Wiki _is_.

- There’s no way to bulk delete comments
- There’s no spam-aware way to moderate comments
- No easy way to get notification whenever my pages were changed (that should have been the default)
- There’s no easy way to bulk ban or delete users
- there’s no way to see or remove all comments by a specific user

So, a wiki owner discovers one day his wiki has been turned in a spam heaven – and they have almost nothing to do but go one by one and delete comments and pages. Bad.

I had to literally recreate the site from scratch (using [SquareSpace](http://squarespace.com/)).


---

## About the author

**Roy Osherove**: Senior Solutions Architect at AWS working on AI for production and AI-driven development; author of The Art of Unit Testing and Elastic Leadership, with about 20 years of consulting and training on unit testing, TDD, team leadership and continuous delivery.

### Sites

- [RobotPaper](https://robotpaper.ai/): This blog: AI patterns and anti-patterns, AI and coding agents, and engineering leadership.
- [osherove.com](https://osherove.com): Roy's personal site. Author of The Art of Unit Testing and Elastic Leadership; consulting and training on unit testing, TDD, team leadership and continuous delivery, plus about 20 years of blog posts.
- [The Art of Unit Testing](https://www.artofunittesting.com): The Art of Unit Testing, 3rd Edition (Manning): readable, maintainable, trustworthy unit tests, plus TDD workshops in C#, JavaScript, Java and Kotlin.
- [5whys.com](https://www.5whys.com): Roy's writing on software team leadership: self-organizing teams, surviving chaos, learning mode and the Elastic Leadership model.
- [Pipeline Driven](https://pipelinedriven.org): Continuous delivery and DevOps practices: build patterns, pipeline-friendly testing, DevOps metrics and enterprise DevOps.
- [Elastic Leadership](https://www.elasticleadership.com): Elastic Leadership, Roy's framework for software team leaders (survival, learning and self-organizing modes).

### Social

- X: https://x.com/royosherove
- LinkedIn: https://www.linkedin.com/in/osherove/

### Contact

- Contact form: https://forms.gle/jQSx5KoXvrVA1JCK7

### License

Licensed under CC BY 4.0 — reuse, quote and adapt with attribution (Roy Osherove, link to the original page). License: https://creativecommons.org/licenses/by/4.0/