This little update...actually not so little update you can see in the screenshot below is a powerful update.
Now if you create a playlist to capture your audio goodness, that individual playlist has it's own unique RSS feed. This is outside of the general RSS feed your user profile has in 3Speak.
For example, in the Podcast Index you can see all of the content I've uploaded to 3Speak through my @epodcaster username. https://podcastindex.org/podcast/5312736
It has the recent Daily Voice content and everything else I've ever done on 3Speak.
Now look at the new podcast playlist that is ONLY the Daily Voice playlist: https://podcastindex.org/podcast/8073132
Why This Matters
As a creator, I have lots of things I want to share with the world. Some folks might only be interested in the Daily Voice. Others may be interested in things I do like National Podcast Post Month and could care less about other things.
So now I can share only the playlists that I want to share with specific audiences without overwhelming them with everything.
This is going to come especially handy during November when National Podcast Post Month (NaPodPoMO) is happening. Now I can create a NaPodPoMo 2026 podcast playlist and use that specific RSS feed to the collective NaPodPoMo MEGA Feed ensuring that fellow challengers only get audio related to NaPodPoMo and not anything else.
How and Why Did This Happen?
The origin of this handy feature comes from an ongoing conversation we've been having around 3Speak and audio. At one point @nicklewis recorded a walkthrough of how he uses the SPK network based on a conversation with
@steevc which then became the comment thread between
@tibfox and myself. You can see how it came to be here: @nicklewis/exploring-audio-uploads-in-7
This entire experience is another big example of why Hive is the place for creators. The fact a wish list idea could go from concept to reality in a short time frame is powerful.
I encourage you to take this new 3Speak podcast playlist RSS feature for a spin.
Many thanks to @tibfox,
@nicklewis,
@steevc.