Leo's Twitter Updates for 2008-09-20

• @RickMacMerc Don't make me cry, Rick. #
• Burn After Reading and steak tacos at The Alamo on 6th St in Austin. If it had been after 5p I might have had a gin and tonic, too. #
• @RickMacMerc Yeah the TWiT and Leoville sites are down. I've put in a ticket with Softlayer. This machine has been a lil flaky lately. #
• Erggh. The RAID 5 array died on the server for TWiT.tv and Leoville.com - sites will be down for a while. #
• @alansebastian I enjoyed Burn After Reading - but I'm a Coen Brothers fan. Frances, Brad, and George were a little broad I thought. #
• @alienspaces If you're gonna buy a Drobo use our promo code not Cali's! But seriously the RAID 5 card died - data is not recoverable. -sigh- #
• @PhantomJoe Yeah - the hardware in that server has been troubled for a while. It was a 3Ware 9550-SX RAID card that died. #
• @rogermcguinn Yeah it's a little disappointing. We have three Raptors in the array. No data is recoverable. My backups are a little old too. #
• Rebuilding twit.tv, army.twit.tv, live.twit.tv, twit.tv/forums, and leoville.com, munchcast.com is not going to be fun. #
• @mollywood Is that code? #

Leo's Twitter Updates for 2008-09-18

• Off to Austin for NAB. Too early. in Oakland, CA http://tinyurl.com/3rbo88 #
• It's kind of quiet here. Smells like a recession. in Austin, TX http://tinyurl.com/3g3ahx #

Leo's Twitter Updates for 2008-09-14

• @submooringtone I think that's definitely going on for some. When you get hundreds of people in a chat there are all sorts of undercurrents. #

Leo's Twitter Updates for 2008-09-12

• TWiT Army has its own Twhirl now: http://is.gd/2wPH - ok it works with any Laconica site, too. Thanks Loic and Marco! #
• @bradarsenault UGM is off being painted at ALSA. Today, all day, on TWiT Live, coverage of Bearhug Camp on the future of open microblogging. #
• jack payne, biz stone, and jack dorsey just walked into the bearhug. http://twitlive.tv #

Leo's Twitter Updates for 2008-09-10

• Heading home. in Los Angeles, CA http://tinyurl.com/5lu8s5 #
• @steverubel It's definitely related to over-the-air iPhone app installs or updates. Use iTunes only. Maybe 2.1 will fix this - maybe not. #