Warning: ftp_nlist() expects parameter 1 to be resource, null given in /home/maykdev/public_html/icsr/wp-admin/includes/class-wp-filesystem-ftpext.php on line 420

Warning: ftp_pwd() expects parameter 1 to be resource, null given in /home/maykdev/public_html/icsr/wp-admin/includes/class-wp-filesystem-ftpext.php on line 230

Warning: ftp_pwd() expects parameter 1 to be resource, null given in /home/maykdev/public_html/icsr/wp-admin/includes/class-wp-filesystem-ftpext.php on line 230

Warning: ftp_pwd() expects parameter 1 to be resource, null given in /home/maykdev/public_html/icsr/wp-admin/includes/class-wp-filesystem-ftpext.php on line 230

Warning: ftp_nlist() expects parameter 1 to be resource, null given in /home/maykdev/public_html/icsr/wp-admin/includes/class-wp-filesystem-ftpext.php on line 420

Warning: ftp_pwd() expects parameter 1 to be resource, null given in /home/maykdev/public_html/icsr/wp-admin/includes/class-wp-filesystem-ftpext.php on line 230

Warning: ftp_pwd() expects parameter 1 to be resource, null given in /home/maykdev/public_html/icsr/wp-admin/includes/class-wp-filesystem-ftpext.php on line 230

Warning: ftp_pwd() expects parameter 1 to be resource, null given in /home/maykdev/public_html/icsr/wp-admin/includes/class-wp-filesystem-ftpext.php on line 717

Warning: ftp_nlist() expects parameter 1 to be resource, null given in /home/maykdev/public_html/icsr/wp-admin/includes/class-wp-filesystem-ftpext.php on line 420

Warning: ftp_pwd() expects parameter 1 to be resource, null given in /home/maykdev/public_html/icsr/wp-admin/includes/class-wp-filesystem-ftpext.php on line 230

Warning: ftp_pwd() expects parameter 1 to be resource, null given in /home/maykdev/public_html/icsr/wp-admin/includes/class-wp-filesystem-ftpext.php on line 230

Warning: ftp_pwd() expects parameter 1 to be resource, null given in /home/maykdev/public_html/icsr/wp-admin/includes/class-wp-filesystem-ftpext.php on line 230

Warning: ftp_nlist() expects parameter 1 to be resource, null given in /home/maykdev/public_html/icsr/wp-admin/includes/class-wp-filesystem-ftpext.php on line 420

Warning: ftp_pwd() expects parameter 1 to be resource, null given in /home/maykdev/public_html/icsr/wp-admin/includes/class-wp-filesystem-ftpext.php on line 230

Warning: ftp_pwd() expects parameter 1 to be resource, null given in /home/maykdev/public_html/icsr/wp-admin/includes/class-wp-filesystem-ftpext.php on line 230

Warning: ftp_pwd() expects parameter 1 to be resource, null given in /home/maykdev/public_html/icsr/wp-admin/includes/class-wp-filesystem-ftpext.php on line 717

Why ISIS Is So Good at Branding Its Failures as Successes

Why ISIS Is So Good at Branding Its Failures as Successes
21st September 2017 ICSR Team
In ICSR's News, Insights, Publications

By Charlie Winter, Senior Research Fellow, ICSR and Haroro Ingram, Research Associate with the International Centre for Counterterrorism

When you think about terrorist attacks the way the Islamic State does, even blatant technical failure can become strategic success. It’s all about how shrewdly you brand an attack after the fact—and how willing the media is to buy into your narrative.

Consider what happened in the U.K. on Friday. During morning rush hour, the London Underground’s District Line was brought to a standstill after a fireball erupted on a train at Parsons Green Station. Minutes after the Metropolitan Police arrived, news broke that the incident had been caused by a bomb—crudely concealed in a bucket and placed in a supermarket shopping bag—that had failed to detonate properly. Within a couple of hours, British Prime Minister Theresa May declared the incident an attempted terrorist attack.

Read the full article published by The Atlantic here.

Want to stay updated about ICSR’s work? Sign up to our mailing list here.


Warning: fopen(/home/maykdev/public_html/icsr/wp-content/comet-cache-214517197.lock): failed to open stream: No space left on device in /home/maykdev/public_html/icsr/wp-content/plugins/comet-cache-pro/src/includes/traits/Shared/CacheLockUtils.php on line 52

Fatal error: Uncaught Exception: Unable to obtain an exclusive lock. in /home/maykdev/public_html/icsr/wp-content/plugins/comet-cache-pro/src/includes/traits/Shared/CacheLockUtils.php:53 Stack trace: #0 /home/maykdev/public_html/icsr/wp-content/plugins/comet-cache-pro/src/includes/traits/Ac/ObUtils.php(372): WebSharks\CometCache\Pro\Classes\AbsBaseAp->cacheLock() #1 [internal function]: WebSharks\CometCache\Pro\Classes\AdvancedCache->outputBufferCallbackHandler('<!DOCTYPE html>...', 9) #2 /home/maykdev/public_html/icsr/wp-includes/functions.php(5277): ob_end_flush() #3 /home/maykdev/public_html/icsr/wp-includes/class-wp-hook.php(307): wp_ob_end_flush_all('') #4 /home/maykdev/public_html/icsr/wp-includes/class-wp-hook.php(331): WP_Hook->apply_filters('', Array) #5 /home/maykdev/public_html/icsr/wp-includes/plugin.php(476): WP_Hook->do_action(Array) #6 /home/maykdev/public_html/icsr/wp-includes/load.php(1102): do_action('shutdown') #7 [internal function]: shutdown_action_hook() #8 {main} thrown in /home/maykdev/public_html/icsr/wp-content/plugins/comet-cache-pro/src/includes/traits/Shared/CacheLockUtils.php on line 53