The last Stack Exchange Podcast (episode 49) was released one month and eight days ago.

This leads to the following two questions:

  1. When will podcast #50 drop on the streets?
  2. Why the delay?

Update: Link to episode 50.

  • 3
    It's #50, so we had to make sure it was EXTRA AWESOME. Also, I was out for 2 weeks... but mostly the AWESOME part. – David Fullerton Jul 19 '13 at 20:52

We just recorded another episode - the fabled Episode #50. The recent changes to closing are discussed, we argue inconclusively about library recommendation questions, and Joel smashes blinds in the recording room. Will anyone make it out alive? Stay tuned...

It should be live on the blog sometime next week.

  • 2
    Great! I can't wait! – user228741 Jul 19 '13 at 20:51
  • It seems to have been prematurely announced - following that link at the time of writing this leads to "oh no, 404". – Peter Mortensen Jul 26 '13 at 5:12
  • Works for me, @Peter - the link should be blog.stackoverflow.com/2013/07/… - does that work? – Shog9 Jul 26 '13 at 5:17
  • I still get the 404. The link is blog.stackoverflow.com/2013/07/…. I also tried it in Opera with the same result, not being logged into Stack Overflow. – Peter Mortensen Jul 26 '13 at 5:52
  • Not seeing any requests logged for you, @peter - are you behind a caching proxy of any sort? – Shog9 Jul 26 '13 at 6:01
  • Not that I am aware of. Perhaps at my ISP, 3.dk. As far as I know (from a traceroute), there are several NATs between me and the Internet, but I have not encountered this kind of problem before. – Peter Mortensen Jul 26 '13 at 6:05
  • Anyway, the podcast is available from soundcloud.com/stack-exchange/#feeds – Peter Mortensen Jul 26 '13 at 6:05
  • I found the reason. For some reason, on 2009-12-12, I had put in an entry (now deleted) in the hosts file (C:\WINDOWS\system32\Drivers\etc\hosts): " blog.stackoverflow.com" (the new address is One hint was that tracert and nslookup gave different results. – Peter Mortensen Aug 24 '13 at 13:10

You must log in to answer this question.