Just received official email from BFL, my Jale's are on the way...

[Crypt_Current]

FINALLY.  Only been waiting since 9/2012.

Speculate.

[Crypt_Current]

http://us6.campaign-archive1.com/?u=5015fc3486176144c53751877&id=3af5f83481&e=07b9e37e2a

[Rampion]

They just ask you to confirm you accept whatever they ship you whenever they ship.

[Crypt_Current]

[BitcoinAshley]

Does this mean Smoothie gets to change his sig? 

[smoothie]

Does this mean Smoothie gets to change his sig? 

What you mean? My sig is still legit 

[Frizz23]

FINALLY.  Only been waiting since 9/2012.

No, your Jalapeno is not on it's way.

BFL just sent you a nice letter with lots of yadda yadda. The interesting part is this here:

"Please be advised that [1]due to the adjustments described above, we need your confirmation prior to release of your order into the final build queue and on to final delivery.  It may also be a good time to [2]review your purchase altogether relative to the bitcoin market as this is the last opportunity to do so.  If your order is not confirmed, it will be canceled and your money will be refunded. "

They did this because of legal reasons - to be on the save side:
[1] They screwed up power and performance, so they want to get your OK.
[2] They screwed up shipment dates - and know that it will take a long, long time before your units will be shipped - and difficulty will have sky rocketed and you only make a fraction of the Bitcoins that you would have made had BFL shipped on time. They want to get your OK for that too.

Basically it's like a blank check for BFL: "OK we screwed up big time but you have to sign here XXX and confirm that this is still OK with you".

Not that some of you guys come up with the idea of suing them ...  


Wake up, people!
They're doing this not because they are such a customer-friendly company - they are doing this for a reason.

[PuertoLibre]

FINALLY.  Only been waiting since 9/2012.

No, your Jalapeno is not on it's way.

BFL just sent you a nice letter with lots of yadda yadda. The interesting part is this here:

"Please be advised that [1]due to the adjustments described above, we need your confirmation prior to release of your order into the final build queue and on to final delivery.  It may also be a good time to [2]review your purchase altogether relative to the bitcoin market as this is the last opportunity to do so.  If your order is not confirmed, it will be canceled and your money will be refunded. "

They did this because of legal reasons - to be on the save side:
[1] They screwed up power and performance, so they want to get your OK.
[2] They screwed up shipment dates - and know that it will take a long, long time before your units will be shipped - and difficulty will have sky rocketed and you only make a fraction of the Bitcoins that you would have made had BFL shipped on time. They want to get your OK for that too.

Basically it's like a blank check for BFL: "OK we screwed up big time but you have to sign here XXX and confirm that this is still OK with you".

Not that some of you guys come up with the idea of suing them ...  


Wake up, people!
They're doing this not because they are such a customer-friendly company - they are doing this for a reason.

Bingo,

It appears Frizz is astute (and logical) enough to figure that out instantly.

[smoothie]

FINALLY.  Only been waiting since 9/2012.

No, your Jalapeno is not on it's way.

BFL just sent you a nice letter with lots of yadda yadda. The interesting part is this here:

"Please be advised that [1]due to the adjustments described above, we need your confirmation prior to release of your order into the final build queue and on to final delivery.  It may also be a good time to [2]review your purchase altogether relative to the bitcoin market as this is the last opportunity to do so.  If your order is not confirmed, it will be canceled and your money will be refunded. "

They did this because of legal reasons - to be on the save side:
[1] They screwed up power and performance, so they want to get your OK.
[2] They screwed up shipment dates - and know that it will take a long, long time before your units will be shipped - and difficulty will have sky rocketed and you only make a fraction of the Bitcoins that you would have made had BFL shipped on time. They want to get your OK for that too.

Basically it's like a blank check for BFL: "OK we screwed up big time but you have to sign here XXX and confirm that this is still OK with you".

Not that some of you guys come up with the idea of suing them ...  


Wake up, people!
They're doing this not because they are such a customer-friendly company - they are doing this for a reason.

+1 well said. Hopefully someone is saved from any more grief

[DPoS]

Fatal error: Uncaught exception 'PDOException' with message 'SQLSTATE[08004] [1040] Too many connections' in /var/web/bflweb/library/Zend/Db/Adapter/Pdo/Abstract.php:129 Stack trace: #0 /var/web/bflweb/library/Zend/Db/Adapter/Pdo/Abstract.php(129): PDO->__construct('mysql:host=loca...', 'zend_admin', '3ErK5wqJ6bTUgxk', Array) #1 /var/web/bflweb/library/Zend/Db/Adapter/Pdo/Mysql.php(109): Zend_Db_Adapter_Pdo_Abstract->_connect() #2 /var/web/bflweb/library/Zend/Db/Adapter/Abstract.php(315): Zend_Db_Adapter_Pdo_Mysql->_connect() #3 /var/web/bflweb/application/Bootstrap.php(203): Zend_Db_Adapter_Abstract->getConnection() #4 /var/web/bflweb/library/Zend/Application/Bootstrap/BootstrapAbstract.php(667): Bootstrap->_initCharsetDB() #5 /var/web/bflweb/library/Zend/Application/Bootstrap/BootstrapAbstract.php(620): Zend_Application_Bootstrap_BootstrapAbstract->_executeResource('charsetdb') #6 /var/web/bflweb/library/Zend/Application/Bootstrap/BootstrapAbstract.php(584): Zend_Application_Bootstrap_BootstrapAbstract->_bootstrap(NULL) in /var/web/bflweb/library/Zend/Db/Adapter/Pdo/Abstract.php on line 144

[Crypt_Current]

lol trollz

[shapemaker]

PDO->__construct('mysql:host=loca...', 'zend_admin', '3ErK5wqJ6bTUgxk', Array)

Fer chrissakes, the incompetency...

[Tamerz]

Fer chrissakes, the incompetency...

I'm just hoping that password is only for that account, and only allowed to log in locally.

EDIT: They just said in the shoutbox it has been changed already.

[shapemaker]

EDIT: They just said in the shoutbox it has been changed already.

Aaaand the next error will throw the next password out until they change the debug output too...

[erk]

These database driven sites just don't seem to be able to handle a moderate number of hits without some elaborate server setup.

[centove]

These database driven sites just don't seem to be able to handle a moderate number of hits without some elaborate server setup.

They do okay if you have dedicated hardware to handle the DB load. (IE a web server & a DB server as two separate physical machines)

[Quix]

PHP isn't very good for scaling, every request is a totally separate action and it doesn't look like they're using caching. What PHP is good for is small stuff because it's quick and easy to understand.

BTW, disabling diagnostic errors on public-facing sites is COMPSCI101 stuff. If this happened on a webapp I'd worked on I would be fired on the spot.

[DPoS]

they are learning..


There has been an error processing your request Exception printing is disabled by default for security reasons.

Error log record number: 604414173345
..

[DPoS]

good that they had people around while they sent out that email to clean things up

this shows now on the other error:


"Unable to connect to database"

[Inaba]

PHP isn't very good for scaling, every request is a totally separate action and it doesn't look like they're using caching. What PHP is good for is small stuff because it's quick and easy to understand.

BTW, disabling diagnostic errors on public-facing sites is COMPSCI101 stuff. If this happened on a webapp I'd worked on I would be fired on the spot.

I agree... someone is going to get ... schooled ... tomorrow.  I'm very displeased at the moment.