Wow, that was still a really stupid patch. There was an #ifndef PURIFY there for a reason. It's because the openssl authors knew that line would cause trouble in a memory debuger like Purify or Valgrind. http://en.wikipedia.org/wiki/IBM_Rational_Purify
Seriously guys, take a few minutes to understand the code before hacking on it. If it was written by a n00b, you need to understand it to make sure they didn't do other stuff wrong. If it was written by someone competent (which is probably the case for openssl), then you need to make sure you're not the one making the mistake. In this case, to make it work with valgrind, the patch should have been to debian/rules, simply changing the way Configure was called.
No, they are not all tethered any more. They've had an untethered one for about a year now. I could go down and ask them how long exactly if anyone's really interested.
They are pretty lound however, especially the untethered one I saw, as it needed a high speed fan on it to keep stuff cool. I don't remember exactly why they needed the fan, but I think it might have been because they didn't want huge heatsinks on the voltage regulators. The other source of noise of course is the sound of dozens of servos with cheap gearboxes. Each joint is controlled by a separate servo.
Sorry, I don't really know much about the current status, as I haven't been keeping up much after I leaving that lab. I still work at CMU, so I still see them now and then.
Cute, so they did release at least some of the bits. Do you happen to know what audio codec gtalk uses? XEP-0167 says, "Support for the Speex codec is RECOMMENDED.", so I guess Speex is a fair guess. I guess it's reasonably unlikely they would have chosen one of the patented codecs.
So... Anyone want to go slap SIP on a free Jabber client?
Only if you trust Fred... If Fred sends you a cool screensaver (and you know it's actually from Fred) would you run it? Do you trust Fred to not have opened any Word document you wouldn't have opened? If he did, it could have modified all the ones he wrote himself, or the ones receieved expectedly from a trusted source.
Basically, if you don't trust Fred enough to give him your password, he isn't a trusted source.
Slashdot Mirror
The standard operation is carefully designed to avoid increasing the count to more than the total number of voters in a given district.
Seriously guys, take a few minutes to understand the code before hacking on it. If it was written by a n00b, you need to understand it to make sure they didn't do other stuff wrong. If it was written by someone competent (which is probably the case for openssl), then you need to make sure you're not the one making the mistake. In this case, to make it work with valgrind, the patch should have been to debian/rules, simply changing the way Configure was called.
No, they are not all tethered any more. They've had an untethered one for about a year now. I could go down and ask them how long exactly if anyone's really interested.
They are pretty lound however, especially the untethered one I saw, as it needed a high speed fan on it to keep stuff cool. I don't remember exactly why they needed the fan, but I think it might have been because they didn't want huge heatsinks on the voltage regulators. The other source of noise of course is the sound of dozens of servos with cheap gearboxes. Each joint is controlled by a separate servo.
Sorry, I don't really know much about the current status, as I haven't been keeping up much after I leaving that lab. I still work at CMU, so I still see them now and then.
Cute, so they did release at least some of the bits. Do you happen to know what audio codec gtalk uses? XEP-0167 says, "Support for the Speex codec is RECOMMENDED.", so I guess Speex is a fair guess. I guess it's reasonably unlikely they would have chosen one of the patented codecs.
So... Anyone want to go slap SIP on a free Jabber client?
Clearly whoever wrote that article hasn't looked at http://www.google.com/talk/otherclients.html. Specifically the "Voice calls to other Google Talk users" column.
Honestly, I'm not sure they haven't documented the protocol recently.
Last I checked, Apple had switched to Intel. They don't even have a PowerPC option any more.
Only if you trust Fred... If Fred sends you a cool screensaver (and you know it's actually from Fred) would you run it? Do you trust Fred to not have opened any Word document you wouldn't have opened? If he did, it could have modified all the ones he wrote himself, or the ones receieved expectedly from a trusted source.
Basically, if you don't trust Fred enough to give him your password, he isn't a trusted source.