You are probably aware of the shameful display of hooliganism that has ravaged several British cities including London, just a year before it is due to host the Olympics. According to reports, BlackBerry Messenger (BBM) was the primary tool used to spread and organize the riots.
The riots started on August 6, in response to the Police shooting of Mark Duggan in Tottenham. A protest march by a couple of hundred people turned violent, and resorted to rioting, vandalism, and looting. Over the next few days, the disturbance spread to several other cities including Birmingham, Liverpool, and Nottingham. As mentioned earlier, the vandals, who were mostly youths, resorted to using BBM as the primary means of communication. UrbanMashup has dug up evidence that illustrates how BBM was used to spread information about areas that were being attacked and were vulnerable.
Reacting to the widespread allegations of misuse of BBM during the riots, the official BlackBerry UK Twitter account promised to co-operate with the police during the investigation. It issued the following brief statement on the aforementioned micro-blogging platform:
We feel for those impacted by the riots in London. We have engaged with the authorities to assist in any way we can.
Although RIM has declined to reveal the extent of its co-operation with the police, according to The Inquirer, The Regulation of Investigatory Powers Act could be used to force Research in Motion (RIM) – the Canadian manufacturer of BlackBerry, to hand over data from its encrypted BBM network.
This announcement obviously didn’t sit well with some people. A group called Team Poison defaced the official BlackBerry blog in retaliation. Team Poison has urged RIM to not cooperate with the UK police, as it believes that handing over BBM data will lead to innocent bystanders, who were at the wrong place at the wrong time, getting implicated. It also threatened to release RIM’s UK employee database to the angry rioters, if the Canadian company didn’t back down. The offending blog post has already been removed by RIM, but a screenshot provided by an HN user is embedded below.