Geek Dads @ Home #5: Looking Ahead

by Daniel M. Clark on January 31, 2009

Play

The Geek Dads @ Home (Scott Jangro, Daniel M. Clark, Joe Magennis and Sam Harrelson) circle the changing table for another episode.

Clearly, the big news of the week had to do with the inauguration of Barack H. Obama as the 44th President of the United States. First, the gang discussed how this inauguration differed from inaugurations of the past with the use of social media, Facebook integrations, Twitter survival, mobile phones and mainstream geekery (like Microsoft’s awesome Photosynth debut).

Along those lines, the conversation morphs into a discussion of the possibilities that come with this national attention on politics and if/how future generations will view politics differently than the current crop of parent and adults.

And, Twitter stayed up!

Next, the group discusses some of the more interesting and geek-notable functions of the new WhiteHouse.gov site and how technologies such as comments, RSS, podcasts and blogs will be second nature to our children as they grow up digital.

After a conversation about how parents should be great role models and demonstrate reading and listening to good music, the group starts their new weekly segment entitled “I Can’t Believe I Did That To My Kid.” This week’s segment is a sad and bloody tale.

The show runs a hope-filled 50 minutes.

Enjoy!

  • http://intensedebate.com/people/affiliatetip Shawn Collins

    I sent a question to Comments@whitehouse.gov (I guess they added the form since them) on January 20 to ask if they would be opening comments on the blog based on their proclamation of communication, transparency, and participation in a post that day:
    http://www.whitehouse.gov/blog/change_has_come_to

    I got a notice of temporary failure from Gmail the next evening that "The recipient server did not accept our requests to connect." and they provided a link to http://mail.google.com/support/bin/answer.py?answ… and they instructed me not to resend the message.

    Google indicated that the reason for the issue was:

    - The other domain doesn't have up-to-date MX records or is otherwise misconfigured.
    - The other domain is blacklisting or graylisting messages from Gmail.
    - The other domain is experiencing temporary networking problems.

    Not sure if the message ever did make it through. If so, there was no autoresponse or real response.

Previous post:

Next post: