What a troll. BFL coming up empty making your ass hurt?
I think Luke-Jr might be worrying about the same thing I'm looking at for some time: there's a huge backlog of dust and low/no-fee transactions waiting to be confirmed (see: http://blockchain.info/fr/unconfirmed-transactions). Unless some miner gives priority to the ASICMINER share confirmation dust it will have a hard time coming through (the dividends should be fine as Luke-Jr corrected later).
These unconfirmed transactions are still growing and slow down some bitcoind operations unless you upgrade to 0.8.2rc3 or later. It seems 0.8.2rc3 can handle these transactions given that you have enough memory and its default setting will ignore a sizable part of it.
I didn't study these transactions but I wonder if someone wants us to strengthen the network against this kind of DoS attack by doing the attack (generating huge amounts of dust) in a progressive and controlled way to force devs to solve the problem (done pending stable release) and miners to upgrade (in progress even without stable release) without disturbing the network too much. In the current situation, it seems to me that some individual with Bitcoins to spare and a modified client can slow <=0.8.1 nodes to a crawl at will by generating dust in very large quantities. If I'm right the people/individual behind the "benign DoS attack" are/is actually doing us a huge service.