Comment 1 for bug 1302033

After poring over the changelog and diff and talking about it with Michael a few times, I think the risk-versus shiny here is worth it, and he's already got a few fixes queued up in a 1.0.1 that will follow this upload immediately after (or replace it). Approving, and leaving the blame fully in mvo's court when it all explodes. :P