Terminators or appliances? Some thoughts on the new robots

There’s been alot of buzz around the work being done at Boston Dynamics on robots. Previously there was their video of BigDog

And recently this clip has been getting alot of attention, of PETMAN:

I was alarmed when I first saw this video. I don’t imagine the scientists at Boston Dynamics are blind, and they can likely see a lot of uses for PETMAN besides testing clothing. (Watch the way the man pushes the robot to show stability, for example.) If anything, I wouldn’t be surprised to see it doing a similar support role that BigDog with the U.S. military. The first “man” into a fire fight would be PETMAN.

After being alarmed, my second thought was to think of the funders of this, namely DARPA. DARPA also was instrumental in the creation of the Internet, and needless to say, the first purpose of the Internet as DARPA saw it was not to be able to exchange cute pictures of cats on Facebook. But that is where we ended up. Likewise, I could see a similar thing happening with robots, and they could end up being domesticated, just like the Internet is. The robots will become appliances, just like all the other smart devices will be in our homes. (And very soon everything will be “smart”, be it your fridge, oven, washer, etc.) They will be an appliance that moves. They’ll carry in groceries. They’ll paint things. They’ll even vacuum. (Wait, we have that.).  We’ll end up complaining that our robots are too old and can’t do the cleaning tasks that the brand new robots can.

Will robots be used in war? Of course. But if one soldier is accompanied by a PETMAN and his enemy is accompanied by heavy artillery, my money is on the enemy. They will still be effective in many ways, but like any weaponry, armies will adapt to meet the challenge.

Before I close, I want to add that this is a really under-reported story. There are lots of stories out about the latest mobile device or the latest laptop, but the rapid advancement of robotics in the 21st century is going to be a big deal.

How to use cURL and the Twitter API, November 2011 edition

I used to use cURL to interface with the Twitter API, but after they changed/restricted it, that became harder. However, with a bit of investigation, I can show you how to use them together still, at least for queries. (If anyone knows a simple way of doing updates, please comment below).

For example, if you want to get my timeline, you can use

curl http://twitter.com/statuses/user_timeline/blm849.rss

If you want to get 200 entries, you can use:

curl http://twitter.com/statuses/user_timeline/blm849.rss?count=200

If you want to get 200 entries and use JSON instead of RSS, you can use:

curl http://twitter.com/statuses/user_timeline/blm849.json?count=200

If you want to play around, replace “blm849” with your twitter handle or someone else’s that isn’t protected.

For more on various formats and parameters, see GET statuses/user_timeline | Twitter Developers. Also make sure you check it for limits.

Here’s another option. If you want to get the statuses for the entries in my FAVS lists, you can use:

curl http://api.twitter.com/1/blm849/lists/favs/statuses.atom

If you go to the REST API Resources for Twitter Developers page, you can see other options.

Essentially you need to play around to take a command you send to the REST API (e.g. GET lists/statuses) and learn how to turn it around to a commend you can pass to twitter.com/api.twitter.com.

If you say: hmmmm, some of this is inconsistent, etc., I confess I have just started experimenting. But I wanted to get something down before I forgot about it, and I will build on it later.

Good luck!