Silicon Investor (SI) -- The First Internet Community

STOCKTALK

We've detected that you're using an ad content blocking browser plug-in or feature. Ads provide a critical source of revenue to the continued operation of Silicon Investor. We ask that you disable ad blocking while on Silicon Investor in the best interests of our community. If you are not using an ad blocker but are still receiving this message, make sure your browser's tracking protection is set to the 'standard' level.

Strategies & Market Trends : The Residential Real Estate Crash Index -- Ignore unavailable to you. Want to Upgrade?

To: DebtBomb who wrote (261029)	7/15/2010 10:03:11 AM
From: Secret_Agent_Man	Read Replies (2) \| Respond to of 306849

so when they try and cap disshit before the relief wells are in place, regardless, she's gonna blow- game over- but if in fact the casing is already compromised, it's all bulshitt n e wayz- unless they go below the compromised casing-

To: DebtBomb who wrote (261029)	7/15/2010 10:11:21 AM
From: Smiling Bob	Read Replies (1) \| Respond to of 306849

KKR not as deft as Blackrock was

To: DebtBomb who wrote (261029)	7/15/2010 10:41:57 AM
From: Les H	Read Replies (2) \| Respond to of 306849

BP suspended the "top kill" operation for 16 hours - because, according to numerous experts, it was creating more damage to the well bore - without even telling the media, local officials or the public that it had delayed the effort until long afterwards. BP also admitted - many days after it stopped the top kill attempt - (1) that BP had to stop because mud was leaking out below the seafloor, and (2) that capping the well from the top could blow out the whole well. Similarly, it took more than 5 hours for BP to publicly announce the delay of the "well integrity test" after the decision to delay was made. So BP doesn't have a great track record of promptly informing us of what is happening. But now that the well integrity test (background here and here) is underway, can we somehow tell if it's working or not? georgewashington2.blogspot.com