"Potential. That's the single reason I would recommend Drupal over wordpress (or movable type, etc).
Of course, there are all the other reasons mentioned in this thread: crappy wordpress community support, centralization of third-party modules, active development, cutting edge tech... those are all good reasons too."
A major downside of the proliferation of major blog sites (Windows Live Spaces, livejournal, blogger, blogspot, wordpress.com, etc etc) is that many of them require you to be logged in to comment. This creates the problem of needing to keep so many accounts that are only to comment, and while blogger is the notable exception, I'll never use them for anything else. Gods, the 'net needs more people to support OpenID (and a functional openid server for wordpress would be handy too).
If you've downloaded the release version of 2.1.1 (e.g. the .zip or .tar.gz version of the files) in the past few days, your software may have a security hole added by a malicious user. You should upgrade to the new release pronto.
As the linked article states, subversion was not compromised, so it's safe to patch your 2.1.1 install to 2.1.2 using the public repository access
This is for those of you that haven't upgraded to wordpress 2.1 yet, and are comfortable following instructions using a command line.
It also assumes you have command-line access to your server. But that's a story for another day
Rather than go through the traditional rigamarole with updating wordpress (2.0.9 was released very recently) I decided to try a different approach. What made this possible was that there were no database changes so no upgrade script was needed.
at last I've upgraded to wordpress 1.5, and have fixed that blasted problem where ' and " characters in the comments would be prefixed with slashes. Enough about that problem... I'll be upgrading/changing this template from the default in a few days, when I can get more time. Comments are welcome