This episode currently has no reviews.
Submit ReviewDeplatforming has become a buzzword that often sparks debates about censorship. The recent case of Glenn Beck, a popular conservative radio and podcast host, being removed from Apple Podcasts raised questions about the extent of free speech and the role of centralized platforms. However "deplatforming" incidents are not always rooted in censorship. In this episode, we delve into the complexities behind podcast removals, exploring the Glenn Beck Program case, communication issues with Apple Podcasts, and the need for improved strategies within the podcasting community.
The Glenn Beck Program Removed from Apple Podcasts:
Glenn Beck's removal from Apple Podcasts garnered significant attention due to its knee-jerk association with censorship concerns. However, it is important to differentiate between removal due to potential violations and outright censorship. While the details of the violation were not uncovered until later, it highlights the complexity surrounding podcast removals and the need to respect trademark and copyright laws.
Was it a Technical Issue?
Initially, it was speculated that the removal of the Glenn Beck Program was a technical glitch because there were certainly technical problems with his podcast RSS feed. These included the size (11.5 MB, which led to stability issues), redundant data, and a large cover art file size. We were surprised it actually wasn't a technical issue after all and that his show even worked before this takedown!
A Trademark Violation was to Blame
In the case of the Glenn Beck Program, it was the trademark rights holder who complained to Apple (after not getting the demanded action from Glenn Beck's team), prompting the removal. While this action can be seen as an appropriate response to a trademark violation, it also raises questions about whether podcast hosting providers should be the central point for addressing trademark issues rather than relying solely on the platforms, like Apple Podcasts.
Apple Doesn't Always Communicate Well
One recurring issue surrounding podcast removals, in general, is the lack of effective communication from Apple Podcasts. The lack of specific details regarding technical issues or policy violations has led to confusion and panic within the podcasting community. Improved communication channels and transparency would be beneficial in addressing concerns and avoiding the spread of fear, accusations, and misunderstandings.
Deplatforming: Centralized versus Decentralized
The Beck incident highlights the debate between centralized and decentralized podcasting platforms. While centralized platforms like Apple Podcasts and Spotify offer the benefit of potential notifications for issues, they also hold the power to remove content without clear guidelines or explanations. This raises concerns about potential censorship when the content is the least bit controversial (no matter which political direction it leans). On the other hand, decentralized catalogs like Podcast Index offer more freedom and less likelihood of corporate- or government-driven censorship.
Podcast-Hosting Providers Need to Handle Problems Better
To mitigate the risks of sudden removals, podcast-hosting providers should play a more proactive role in addressing issues. They should be monitoring feeds for potential problems or even disallowing problematic stuff to be uploaded in the first place, such as large images or invalid HTML or RSS. Any of these, and more technical errors, can lead to removals or performance problems on major podcast apps and directories. Additionally, hosting providers should take the lead in resolving trademark or copyright concerns and ensure ample communication with podcasters to avoid unnecessary panic.
Make Yourself Easy to Contact!
Podcasters need to be easily reachable when issues arise. Including contact information within podcast feeds and ensuring...
Deplatforming has become a buzzword that often sparks debates about censorship. The recent case of Glenn Beck, a popular conservative radio and podcast host, being removed from Apple Podcasts raised questions about the extent of free speech and the role of centralized platforms. However "deplatforming" incidents are not always rooted in censorship. In this episode, we delve into the complexities behind podcast removals, exploring the Glenn Beck Program case, communication issues with Apple Podcasts, and the need for improved strategies within the podcasting community.
The Glenn Beck Program Removed from Apple Podcasts:
Glenn Beck's removal from Apple Podcasts garnered significant attention due to its knee-jerk association with censorship concerns. However, it is important to differentiate between removal due to potential violations and outright censorship. While the details of the violation were not uncovered until later, it highlights the complexity surrounding podcast removals and the need to respect trademark and copyright laws.
Was it a Technical Issue?
Initially, it was speculated that the removal of the Glenn Beck Program was a technical glitch because there were certainly technical problems with his podcast RSS feed. These included the size (11.5 MB, which led to stability issues), redundant data, and a large cover art file size. We were surprised it actually wasn't a technical issue after all and that his show even worked before this takedown!
A Trademark Violation was to Blame
In the case of the Glenn Beck Program, it was the trademark rights holder who complained to Apple (after not getting the demanded action from Glenn Beck's team), prompting the removal. While this action can be seen as an appropriate response to a trademark violation, it also raises questions about whether podcast hosting providers should be the central point for addressing trademark issues rather than relying solely on the platforms, like Apple Podcasts.
Apple Doesn't Always Communicate Well
One recurring issue surrounding podcast removals, in general, is the lack of effective communication from Apple Podcasts. The lack of specific details regarding technical issues or policy violations has led to confusion and panic within the podcasting community. Improved communication channels and transparency would be beneficial in addressing concerns and avoiding the spread of fear, accusations, and misunderstandings.
Deplatforming: Centralized versus Decentralized
The Beck incident highlights the debate between centralized and decentralized podcasting platforms. While centralized platforms like Apple Podcasts and Spotify offer the benefit of potential notifications for issues, they also hold the power to remove content without clear guidelines or explanations. This raises concerns about potential censorship when the content is the least bit controversial (no matter which political direction it leans). On the other hand, decentralized catalogs like Podcast Index offer more freedom and less likelihood of corporate- or government-driven censorship.
Podcast-Hosting Providers Need to Handle Problems Better
To mitigate the risks of sudden removals, podcast-hosting providers should play a more proactive role in addressing issues. They should be monitoring feeds for potential problems or even disallowing problematic stuff to be uploaded in the first place, such as large images or invalid HTML or RSS. Any of these, and more technical errors, can lead to removals or performance problems on major podcast apps and directories. Additionally, hosting providers should take the lead in resolving trademark or copyright concerns and ensure ample communication with podcasters to avoid unnecessary panic.
Make Yourself Easy to Contact!
Podcasters need to be easily reachable when issues arise. Including contact information within podcast feeds and ensuring that email addresses are not removed can facilitate communication with hosting providers and mitigate the risk of immediate removal without proper dialogue. But removing email addresses from feeds helps protect podcasters' privacy. So no matter what, have a clearly labeled contact page on your website!
Ensure Your Feed Is Working!
Technical issues lead to most podcast removals. We advise podcasters to maintain separate feeds for their podcasts, especially if they use the same publishing tool for blogging. This practice can help mitigate the risk of feed issues, including offline feeds or missing episodes.
An Environment of Oversensitivity
This incident also reflects a growing climate of oversensitivity, where legal concerns or even technical issues are misinterpreted as censorship. While there are legitimate cases of censorship, it is crucial to separate these instances from other challenges podcasters face.
Never Let a Good Catastrophe Go to Waste:
The podcasting community can learn valuable lessons from incidents like the Glenn Beck removal. Along with other negative events like a DDOS attack, a negative review, or something else, even deplatforming can provide opportunities for stronger calls to action in other areas.
Boostagrams
Adam Curry sent 25,000§ and said: "Advertising induces self-censorship, which I consider to be a mental illness."
Your hosts
Find Dave at schoolofpodcasting.com
Find Daniel at theaudacitytopodcast.com
Mentioned in this episode
Details on the trademark issue from Podnews
Test your podcast feed with Cast Feed Validator or Podbase Podcast Validator
Chapters
00:00:47 - The Glenn Beck Program removed from Apple Podcasts 00:06:12 - Was it a technical issue? 00:11:20 - A trademark violation was to blame 00:14:57 - Apple doesn't always communicate well 00:21:35 - Deplatforming: centralized versus decentralized 00:24:36 - Podcast-hosting providers need to handle problems better 00:29:31 - Make yourself easy to contact! 00:34:21 - Ensure your feed is working! 00:35:20 - An environment of oversensitivity 00:36:57 - Never let a good catastrophe go to waste 00:40:41 - Boostagrams
Mentioned in this episode:
If You've Received Value From This Episode
This podcast supports podcasting 2.0 boosts and streaming of sats. You can boost the show using a new podcast app at www.newpodcastapps.com
of-podcasting.captivate.fm/new-podcast-apps">Podcasting 2.0 Apps
This episode currently has no reviews.
Submit ReviewThis episode could use a review! Have anything to say about it? Share your thoughts using the button below.
Submit Review