The china firewall is complex. In this case, github.com isn't actually blocked in the strict sense. Its just that the DNS for some or all of China's DNS servers doesn't have the correct records. If it were truly blocked, even using the correct IP won't get you there.
This could have happened if github.com changed its DNS records and the China DNSs didn't pick it up. This happens sometimes. The only solution I have found is to re-trigger the DNS change so that next time the China DNSs might pick it up. Otherwise, its anyone's guess when the China DNSs might get corrected. How do you re-trigger the change notification from your primary DNS? I'm not expert enough to know how to do this non-destructively. When I've had these problems in the past, I've had to drop the records and re-add them.
Congrats on Merb 1.0!!! I'm looking forward to a somewhat stable 1.0RC.
Nanite does look interesting.
I did quite a bit a of erlang work a few years ago. Loved it. It was a tough call to go with ruby for building my http://shellshadow.com webapp instead of moving along with erlang. In the end, I went with mindshare.
Hey ez, Can you explain why github is down quite a bit lately? Is it only because all the caretakers are hanging ou in San Diego right now? ;)
nanite is for individual application where you know every part of the system is allowed to talk to one another. Vertebra is for wide area networking and assumes hostility so does a lot more security isolation.
Vertebra is for controlling clusters and clouds at large while nanite is for building scalable backends for individual apps.
Great talk - thanks! I've mirrored the file (and changed the extension to .wmv). On mac I had to use VLC to play it and change the audio to Track 2 to hear it. It was definitely worth the effort though to get it downloaded and playing.
The file streaming works by chunking up a file and broadcasting the chunks to an exchange. Any agents subscribed to the exchange will get a copy of the file. There is a small state machine for re-assembling files and each set of file packets is tagged with a token for easy re-assembly even on a multiplexed channel where multiple files are streaming at once.
Nanite, looks cool we have built a similar system for requesting and completing jobs, but it would be nice to work on top of a well built and maintained framework.