Starting tomorrow, we're upgrading our servers to match the growth of Wikidot. We plan to make the upgrade on-line, without any noticeable service outage, keeping 100% uptime. However, if we encounter problems, Wikidot (or parts of the service) might go off-line for a while, but we will try to make it as smooth as possible — and we know how to do this.

If you try to use a wiki for issue tracking, you'll find that it works well in some ways, and badly in others. Now, issue tracking may seem esoteric, but most projects end up needing it. Today I'll explain why that is, why it does not scale, and how to do this properly using Wikidot.

Over the last days we've been seeing too-frequent "500 Internal Server Errors" and other random JavaScript failures. These now seem to be mostly resolved, though not entirely.

We're seeing quite a rash of "500 Internal Error" or "JavaScript failed" errors when trying to post comments, edit pages, and sometimes read sites. This is annoying but not fatal, just redo the same action. I'll explain what's happening and what we plan to do about it.

You'll see a new section on this site, "Top needs" (at left). It's not so much Yet Another Wishlist but a kind of instant poll about what today's most active Wikidot users want and need.

Wikidot often makes life such fun, when we discover how add sophisticated functionality to a site in literally a few minutes. Today, I dealt with a spam entry (or at least, a very confused new user) on the wiki section of this site.

After deliberation, here are the results of the first Wikidot Theme Contest. Our decisions were based on the quality, originality and utility of the themes.