Good cop, bad cop

Identity in era of social media proliferation was something I brought up in last week’s post. Since then, my office has shifted, and I have to travel a little more to get to the new place. Instead of going below the elevated highway, I take a shorter route that gives me elevated views every 5 minutes thanks to ‘amateur’ humps. But the traffic is better. Traffic and violations – that’s the connection.

A few months back, a video on the Facebook page of the Bangalore Traffic Police made headlines. The cops asked for help in finding the errant car driver. (I’m not sure if they did nab him) Since then, I’ve seen increased participation on the page, with users adding photos of traffic violations, ad campaigns on safety and questions being answered by the cops themselves, though that’s occasional. In many cases, numbers of vehicles are clearly visible and I’ve seen one in which the cops have noted a violation by a fellow officer, uploaded by a user. This, and the brouhaha over the London cops naming and shaming those involved in the UK riots last year made me think about individual identities beyond virtual social and in to real social.

Though we are still at a stage where even a person’s social, let alone all online activities cannot be comprehensively tracked and measured, technology on that front is rapidly catching up. In the near future, real world tracking technologies will probably catch up too. We’re already seeing signs of the worlds colliding. It is then possible that the social identity of a person would include his real-life actions too and a ‘Klout’ would probably have a holistic ranking of an individual, one that includes traffic violations and philanthropy and so on. 🙂

This is probably one area where brands will then have a head start, because naming and shaming them is something many of us already do via social platforms. I wonder if we will be more lenient towards them after we get a dose of identity warfare.

until next time, coping with cops

Leave a Reply

Your email address will not be published. Required fields are marked *