Quote from: AndyRossy on March 13, 2013, 12:58:42 AM

Quote from: notme on March 13, 2013, 12:54:35 AM

Quote from: the joint on March 12, 2013, 06:53:23 PM

Quote from: zebedee on March 12, 2013, 08:24:01 AM

Quote from: chiropteran on March 12, 2013, 02:39:34 AM

Quote from: the joint on March 12, 2013, 02:37:20 AM

It's not just downtime. It's a clusterfuck due to all transactions that will inevitably be reversed. I guarantee you a bunch of people lose a lot of money from this.

Fortunately for me, I was able to sell some LTC at .0115 BTC Cheesy

No transactions are being reversed at all. Where are you getting this false information from?

He doesn't understand, clearly.

You don't understand what I meant, clearly. I had to resend a transaction that was reversed post-fork.

If you had a little more patience, it would have been reconfirmed in the new chain. There was just a very large backlog that is still being cleared.

- The original problem of TX's building up in mempools still exists - if things get crazy, we can expect out of mem errors, and then dare not think of the consequences for the network.
- A double spend was achieved, some people argue the "mechant" should have ignored the 2nd spend or similar, but it happened.

Whilst, ppl saying all calm down, the fact that the fix did not work is awful long term, and must be addressed asap. And a hard fork happened, is pretty terrible.

Cool story. I have no fucking idea what it had to do with my previous comment though.