 |
|
The Delhi Police is investigating a potential link between a Telegram post and a recent bomb blast in the city. The post, shared in a group called 'Justice League Indian,' contained CCTV footage of the blast, which had been altered to include a 'Khalistan Zindabad' watermark. This act of digital manipulation suggests a deliberate attempt to associate the blast with the pro-Khalistan movement, raising concerns about the motives behind the post and its potential impact on public perception. The police are requesting details about the creator of the Telegram group to further understand the circumstances surrounding the post's creation and dissemination.
The Telegram post itself contains threatening language, with the writer stating that 'filthy goons' were hired to target group members and that they are 'capable to strike anytime.' This aggressive rhetoric, coupled with the altered CCTV footage, paints a picture of a group actively seeking to incite fear and possibly violence. While the authenticity of the post and the extent of its connection to the actual bomb blast remain unclear, the police are treating this investigation with utmost seriousness, recognizing the potential for such messaging to escalate tensions and contribute to a climate of fear and unrest.
The incident highlights the growing concern about the use of online platforms like Telegram for spreading misinformation and promoting extremist ideologies. The ease of anonymity and the lack of robust content moderation mechanisms on such platforms make them susceptible to manipulation and abuse by individuals and groups seeking to propagate their agendas. This case underscores the need for collaboration between law enforcement agencies and social media platforms to effectively identify and combat online threats to public safety and national security. It also raises questions about the responsibility of social media companies in policing their platforms and preventing the spread of harmful content.
Source: Delhi Bomb Blast: Delhi Police writes to Telegram, here's why