Iditablog Podcast ‘10 – Episode 1

Iditablog Podcast ‘10 – Episode 1

In the first official podcast for the Iditarod 2010 Season, we break in the new “studio” setup and it has a noticeable impact  on the dynamic of our show – we have a lot of fun and have some great conversations about what’s going on in the mushing world leading up to the start of the Iditarod this next weekend.  We also cover:

  • Yukon Quest and other race recap
  • Who Will Win?” Contest
  • The Checkpoint Guessing Game
  • Mushing Vocabulary Word of the Day
  • What’s going on with all these retirements?
  • Iditarod Schedule this week
  • Our plans for  Iditablog Coverage of the race start?
  • Lots more!

Thanks SO much to all those who tuned in for the live webcast, we’re excited to grow that interaction in the days to come.  Sorry to everyone about the audio levels in the podcast and on the live stream, there were a few kinks in the new system that we’ll have worked out before we broadcast next time.

Feel free to email us with topics or questions you’d like to hear us discuss on the next episode… the email address is: josh@radioalaska.org, send us a twitter/facebook message or call the voicemail box at 253-773-MUSH.

Subscribe to the Podcast in iTunesBrowse the Podcast Archives

Twitter Digg Delicious Stumbleupon Technorati Facebook

3 Responses to “Iditablog Podcast ‘10 – Episode 1”

  1. Help! The podcast is not available for download on iTunes! I would love to listen to it…

  2. Great idea,… really great idea.
    Just make it sound like you don’t have to look for mikes for 3 minutes and keep your facts flowing.
    Congratulations !

  3. The podcast episodes not updating in the iTunes Store is an issue Apple is experiencing with *many* podcast producers. I’m working with their support team and hope to get things fixed before the race really kicks off. HOWEVER, the good news is that if you subscribe to the Iditablog Podcast in iTunes, you *will* get new episodes regardless if they show up in the Store listing or not.

    Sorry for the trouble, I’m hoping we can get it resolved soon.

UA-1454641-1