responds_to?(:chris)

Various places in the Google Voice help docs say that they can only handle voicemail for mobile phones. That's not entirely correct. I think what they mean to say is that your phone/phone service must support "Conditional Call Forwarding". U-verse supports this, and others I'm sure do as well. The steps below are for the U-verse land line I just setup, but I suspect others will work similarly.

1. Add your U-verse land line to Google Voice via the web interface, when you are prompted for Phone Type select "Mobile"
2. Verify the phone you just added by letting Google call you and entering the code displayed on the screen.
3. Login to your U-verse account https://www.att.com/olam/loginAction.olamexecute
4. Go to your Voice Homepage (https://uversecentral3.att.com/uvp/myhome/uverse_voice/messages)
5. Select "Phone Features"
6. Expand and turn on the "No Answer Call Forwarding" section
7. Enter your Google Voice number with area code, and click save

That's it! Now try it out. Using a phone number that isn't on your Google Voice account, call your U-verse home phone, and let it ring, it should forward to your Google Voice account and you'll hear whatever message you have setup.

Ah, it's nice to have all my voicemail in one place

Loading mentions Retweet

This slick little tool allows you to run a command in the background and get notified of its success or failure via the Growl notification framework in OSX. This would be great for deployment scripts that take a little bit of time to run, and you don't really care to watch all the logs as you wait. Or even for annoying data processing/importing scripts that take a long time. Can't wait to try it out!

http://github.com/robey/growlme

Loading mentions Retweet

Google's stock pile of dark fiber (maybe not so dark any more) has been used to communicate between it's data centers across the world for sometime now. I have always hoped they would consider turning this high speed private network into the backbone of an ISP that could be managed by Google. This would hopefully apply significant pressure to US based ISPs who are seemingly un-motivated to improve their own aging networks. Looks like that day might be on the horizon

http://googleblog.blogspot.com/2010/02/think-big-with-gig-our-experimental.html

Loading mentions Retweet

Maybe I would be more likely to blog if it was integrated with email?
We shall see!

Loading mentions Retweet

I'm getting pretty frustrated seeing all the negativity about the Rails community explode out of one event at the GoGaRuCo conference. It's an unnecessary overreaction, and calling out people's personal styles, views, and choices is as equally unprofessional and offensive as any other potentially "offensive" action.

That said I'd like to point out some posts I've seen that are some of the most constructive so far.

http://www.quirkey.com/blog/2009/04/27/the-ghetto-of-the-mind/
http://www.rubyinside.com/be-professional-or-be-edgy-how-context-can-keep-everyone-happy-1709.html

Thank you RubyInside and Aaron Quint.

Loading mentions Retweet

We've all read about the great benefits of loading your JS libraries from Google. But one that isn't terribly obvious is IP Geocoding. When you include "http://www.google.com/jsapi" on your page, Google has automatically done its best to locate the client's machine for you (to the 'metro' level). Isn't that nice of them? It's called google.loader.ClientLocation.

Loading mentions Retweet

Pretty interesting visualization of Rails commit history. And a great example of how the move to Github has spawned community involvement and contribution to Rails. Shamless plug: I make an appearance at 5:22 and 5:53, keep an eye out for the red avatar! Anyone else see themselves?

Loading mentions Retweet