acf domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the init action or later. Please see Debugging in WordPress for more information. (This message was added in version 6.7.0.) in /home2/offthebe/podbiblemag.com/wp-includes/functions.php on line 6131ga-google-analytics domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the init action or later. Please see Debugging in WordPress for more information. (This message was added in version 6.7.0.) in /home2/offthebe/podbiblemag.com/wp-includes/functions.php on line 6131woocommerce domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the init action or later. Please see Debugging in WordPress for more information. (This message was added in version 6.7.0.) in /home2/offthebe/podbiblemag.com/wp-includes/functions.php on line 6131wp-user-avatar domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the init action or later. Please see Debugging in WordPress for more information. (This message was added in version 6.7.0.) in /home2/offthebe/podbiblemag.com/wp-includes/functions.php on line 6131loginizer domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the init action or later. Please see Debugging in WordPress for more information. (This message was added in version 6.7.0.) in /home2/offthebe/podbiblemag.com/wp-includes/functions.php on line 6131wordpress-seo domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the init action or later. Please see Debugging in WordPress for more information. (This message was added in version 6.7.0.) in /home2/offthebe/podbiblemag.com/wp-includes/functions.php on line 6131The post Rivalry hits boiling point between Acast podcasts Firecrotch & Normcore and Previously On… Succession appeared first on POD BIBLE.
]]>On the Acast Creator Network, two of them, Firecrotch & Normcore and Previously On… Succession, are currently tied up in a fearsome rivalry to dominate the market.
The podcasts both launched on Acast in October to mark the highly anticipated return of season three of the Succession TV series, each offering listeners an in-depth commentary on the plotline and character, allowing listeners to get even more of the Roy family, discuss fan theories and shocking plot twists.
However, as the series continues to unfold, so does the podcaster’s discord. This week, Firecrotch & Normcore released a public statement in response to Previously On… Succession’s press conference discussing “the other podcast’s” attempt at a hostile takeover. There have been talks of plans for the podcasting giants to sit down for a shareholder meeting – which is rumoured to take place on a crossover episode at the end of the season…
Whilst is may seem cut-throat, the tongue-in-cheek animosity from both podcasts is in line with the tone of the show. And this is also a good example of how cross-promotion can work on podcasting, perhaps one of the few platforms where ‘rival’ shows can feel confident to share an audience.
And it just goes to show how we can’t get enough of TV companion podcasts!
The post Rivalry hits boiling point between Acast podcasts Firecrotch & Normcore and Previously On… Succession appeared first on POD BIBLE.
]]>