This places the responsibility on theme authors to support the new classes. They are:

• alignleft
• alignright
• aligncenter

I'm not convinced of the need for the align prefix, but it's great progress nonetheless. If your theme doesn't support those classes, here's the code you can insert at the end to handle them:

.alignleft,.left {
	float:left;
	margin: 0.5em;
}
.alignright,.right {
	float:right;
	margin: 0.5em;
}
.aligncenter, .center {
	display: block;
	text-align: center;
	margin: 0 auto;
}

Disconnected 1.3 is out. It includes support for WordPress 2.3's native tagging, and preliminary support for WordPress 2.5's get_avatar() function. I know I said I'd never support gravatars1, but since they're going native in 2.5, there's no point in fighting anymore. At least once 2.5 is released, I can write a plugin to use MyBlogLog Avatars instead.

There's a new theme for habari, I think it's the first fully original theme. It's a beauty, evoking the sleek monochromatic habari dashboard, and including a bunch of custom plugins. It's called Charcoal, and it's hosted on google code, although the code isn't up there, so there's no SVN updating.

1. Since they provide identity without authentication, a sure recipe for abuse

h/t Alex King

I think I'm missing something -
so I make this "killer" GPL, CSS only theme. you sell it for $50, on the premise that it's not a generic XXL poncho (I know you said pink, but what you meant was gray with a blue hood). Immediately on release, any self-hosted blog can download it and install it themselves. Since it's CSS-only, anyone on wordpress.com can pay for the CSS Upgrade and start using it. Suddenly it seems like my theme is another XXL poncho, and the guy who bought it trying to get a unique design is seriously screwed.
I must be thinking about this wrong.

It's not that there aren't perfectly valid revenue models based on the GPL. It's just that this is the only one that isn't.  Once a GPL slice of code is released1 , it can be redistributed by everyone. There are (very few) projects that actually sell GPL-ed code.  X-chat for windows is the one that comes to mind. It works because compiling source code on windows is such a pain.  The more viable methods of making money from GPL software include selling support2, and selling proprietary add-ons.

The way the latter option works with wordpress themes is that the underlying PHP has to be GPL, but the CSS can be any license.  Matt, instead is looking for CSS-only, GPL themes.  This gets extra bizarre in that any CSS-only theme can be implemented by anyone with the CSS upgrade.  Since the themes are GPL, automattic can't even legally suggest that they shouldn't do that.

Designing premium themes is already a tough market. At least designers willing to handle the storefront themselves aren't further hampered by having to open-source their graphics. Arpit is right to question the sensibility of such a marketplace, and Michael Martin reaches a similar conclusion.

1. Meaning, once it's been bought, but in this context, Matt is saying that it will also be made available to self-hosted users
2. CSS support on wordpress.com is currently volunteer-only, staff refuse to touch it