Social Networks Help Filipinos Deal with Manila Floods

Article excerpt

Manila is still at risk for more flooding, but recovery efforts are underway, and many are turning to social networking sites to update and get updates on the situation.

The sprawling Philippines capital of Manila is edging into recovery mode after monsoon rains killed at least 19 people and left much of the city of 15 million under waist and chest high water.

The Philippine government today said people should return to work as soon as possible, as rains eased off early Wednesday. But more rain later hit the city, 60 percent of which is under water, according to national disaster agency head Benito Ramos.

Many are turning to social networking sites to update and get updates on the situation. But even as recovery work kicks into gear, the capital remains vulnerable.

"If we have more rains we will really be in serious trouble," says Mon Casiple, director of the Institute for Political and Electoral Reform (IPER).

Manila Mayor Alfredo Lim declared a state of calamity in the capital earlier Wednesday. Aurela Calica, journalist with the Philippine Star, says that she is stuck inside the Malacanang Palace Compound in Manila this evening local time. "When I came here the roads were still passable but when I was about to leave before 7 p.m. the streets were already flooded," she says.

Ms. Calica was corresponding with fellow journalists via Twitter and Twitter's direct message system, highlighting how social networking and cellphones have become a vital link in the rescue and relief chain. People stranded on rooftops have been SMSing for help, while many Filipinos have taken to Facebook and Twitter to post updates and supplement government and media coverage of the floods and rescue work.

According to a July World Bank report titled "Information and Communications for Development: Maximizing Mobile," there were 101 mobile cellular subscriptions for every 100 people in the Philippines in 2011, up from 41 subscriptions for every 100 people 6 years previously. …


An unknown error has occurred. Please click the button below to reload the page. If the problem persists, please try again in a little while.