Quote from: Phoenix1969 on July 09, 2014, 06:19:03 PM

Everyone saying they planned to screw us ahead of time is like saying they knew about Gox in 1976 imho.

Rubbish.
It was totally predictable (and predicted) that:
a) They would deliver absolutely as late as they could while being able to claim they didn't technically violate their promises
b) They would weasel out of their refund promises of 'at any point up to shipping'

Here is my prediction, from February:
https://bitcointalk.org/index.php?topic=170332.msg4950745#msg4950745

Quote from: murraypaul on February 05, 2014, 12:32:18 PM

Quote from: de_ixie on February 05, 2014, 10:21:01 AM

Quote from: Tigggger on February 05, 2014, 09:50:33 AM

You need to read between the lines, the wording is carefully chosen.
Look at the underlined part, as they only said Q1/Q2 delivery they won't be late until July 1st.

I have to contradict here in terms of Batch 1 (CA Batch) & Batch 2 -

Batch 1 ToS state: Q1/Q2 but delivery 3-4 weeks before batch 2 which equals delay = 1st July -3/4 weeks
Batch 2 ToS state: Delivery one month before batch 3 which equals delay= 1st July - roughly 2 month (for batch 1)
Batch 3 ToS state: Delivery Q 2

Not much space for interpretation here. Batch 1 hashing has to start latest around early May to satisfy the ToS of all batches 1-3.

My interpretation:
Batch 1 delivered 1st July.
Batch 2 delivered 3-4 weeks later, but with compensatory cloud hashing from 1st July.
Batch 3 delivered 1 month later, but with compensatory cloud hashing from 1st July.

Batch 1 customers are delivered on time.
They just say to batch 2 and 3 customers "Yes, we were late, but it didn't affect you, because we gave you free hashing to match"

From middle to end of June, your machines will be 'in production', and unable to be refunded.

I'm not posting this to claim I'm some sort of genius, it was really obvious at the time.
Why was it obvious? Because it what they did last time.
Fool me once, shame on you, fool me twice, shame on me.