Yeah... how to boolean logic.
I'll edit that out. [E] Or... it won't let me. Apparently there's a 24-hour limit or something. That's nice, guess I won't be using this platform anymore...
The rest still kind of holds true, though.
As far as using .call over .send... That explanation doesn't really make a whole lot of sense to me. It was .send before, and was changed to .call. .send works with contracts, so I don't see why it's necessary, even to support generic contracts as recipients.
The only difference between a .send and a .call with no data is that there's much less gas provided, preventing things like this from happening (when the gas amount is correct, that is).
So again... why did .send need to be changed to .call? There are only places in the contract where .send and .call are used appropriately... But this one was specifically changed to be used inappropriately.
Still doesn't answer the issue of the backdoor in the refund method, if the fueling goal isn't met.
RE: The DAO: A contract engineered for failure.