☑ Password-protected accounts. Using an account to make changes could be optional, but reporting who made a change should happen only with a protected account. Spammers are now signing with my name (David Owen).

☑ Enhance versioning to display diffs to/from other versions

☑ How about a preview button on the "edit" page. -- Peter

☑ Convenient way of adding a link to an entry in the Hyperspec glossary.

☑ When displaying times e.g., on the "Recent Changes" pages, also display a time zone. FWIW, all times should be UTC

☑ Add support for code syntax highlighting. Maybe it can be borrowed from bknr or from lisppaste? -- 2004-07-28 Ivan Toshkov

Things that aren't planned to get done

An easier list/header/formatting system than html, like e.g MoinMoin has.
I think HTML is ok. Andrey and I tried Markdown when writing CLiki2. It didn't cover all use cases and there were a lot of problems. --Vladimir Sedach

Automatic link checker to annotate external links when they go 404.
There are a lot of third-party link validation tools. Checking links on every page load is too slow. Batch-checking them means false positives for whoever has to check the logs. And the important thing is you still need to decide what to do about the broken links (find a working one, archive.org, declare software dead, etc.). --Vladimir Sedach

Email integration: (a) Edit-by-email service, (b) notification when page changes.
Edit-by-email is an interesting project; I'm not sure how much precedent there is. Email notifications can be obtained by connecting the ATOM change feeds to a feed-to-email gateway. --Vladimir Sedach