Orange County Disasters on Twitter

by Kristi on March 15, 2010



I have a lot of friends who just don’t ‘get’ the Twitter thing.

“Isn’t Facebook the same?” “I don’t understand Twitter.”

I love both. I keep Facebook for my more immediate friends and sharing kiddo pictures and video while Twitter is more of my daily news addiction from far and wide.  Facebook is slowly becoming more news oriented for me because of all the Fan Pages being created that update on my wall but I’m still a Twitter girl.

For me, Twitter shines during disasters.  “Did you feel that earthquake?” Yep, that’s gonna be me. Instead of calling my Mom and BFF on the phone I can just put it out to Twitter and be reassured that I’m not just tipsy at 11am. Alright, I probably do call them anyway but if it is an earthquake, I am deathly afraid of them and want to talk or connect with someone in case of a bigger and badder quake striking in the next ten minutes. I need time for my heart rate to slow down.

Last month we had three huge storms coming in one after another that affected my travel plans up to Big Bear.  It was hard to find good information on what roads were open yet searching for ‘Big Bear’ on Twitter connected me to hundreds of people talking about the major traffic and road closures on their way up the mountain.  From Twitter I found the BigBearRoads account which will now keep me updated on what roads are open or closed. It was also during the OC Tornado Watch 2010 that I could find out when the ‘vortex’ of the storm would be coming through Yorba Linda.  Valuable info, my friends. 😉

Suzanne Broughton had an awesome post on Disaster Planning that I’ve been keeping in my browser for the past month. I love her style of disaster planning because it resembles mine. Luckily, I now have my girl’s school phone number in my cell so I can contact them! She lists some great Orange County Twitter handles though and OCReggie (the Orange County Register) and QuakeOC are two of my favorites.

Comments on this entry are closed.

Previous post:

Next post: