After spending about 30 minutes at the UPS transfer point, located some 16 miles from where I wanted the Chumby delivered, I now have it in my hands. The device itself is not particularly spectacular in appearance, but it is functional. Last night, I was on the Chumby site at http://www.chumby.com and was able to set up the Chumby to download some apps from the main site. The way that they have the Chumby set up is that it will always connect with the main site. The main site for chumby.com is located in San Diego, CA 92130. That does not mean that the main server for the chumby is located in the same place, but bets are, this is the location. I only say that because the device is made in China and could potentially have a backdoor to a server in China. See how trusting I really am? I am not afraid since I don't have anything at my house worth stealing and most of my network is closed off anyway. But back to the story. My hands are off to the Chumby people in terms of their ease of setup on the device. You have to have a computer nearby to finish the setup since it does interact with the Chumby site. There is an ID number that is exchanged with the Chumby site that authenticates your new Chumby so that you can make changes to the app structure. I still have a lot of exploration to make prior to hacking the box, but it is nice to see that they have put a lot of thought into what the device is capable of doing.
My gameplan is to hack the Chumby and use it as a robotics controller. the Chumby itself weighs very little, which is a great advantage. It has a wifi capability which enhances its communication power with my laptop. I have not bee successful at hooking the Chumby into our guest wireless at work due to the capture page issue. I haven't figured out what completely is needed to do that yet. The debugchumby file that I created does not hook into our Cisco system. One thing, I do not have a real good sense of the IP address of the proxy and the fact that the form is not named from the proxy may have something to do with it. More later.
Tuesday, July 27, 2010
The Chumby is in ...
After spending about 30 minutes at the UPS transfer point, located some 16 miles from where I wanted the Chumby delivered, I now have it in my hands. The device itself is not particularly spectacular in appearance, but it is functional. Last night, I was on the Chumby site at http://www.chumby.com and was able to set up the Chumby to download some apps from the main site. The way that they have the Chumby set up is that it will always connect with the main site. The main site for chumby.com is located in San Diego, CA 92130. That does not mean that the main server for the chumby is located in the same place, but bets are, this is the location. I only say that because the device is made in China and could potentially have a backdoor to a server in China. See how trusting I really am? I am not afraid since I don't have anything at my house worth stealing and most of my network is closed off anyway. But back to the story. My hands are off to the Chumby people in terms of their ease of setup on the device. You have to have a computer nearby to finish the setup since it does interact with the Chumby site. There is an ID number that is exchanged with the Chumby site that authenticates your new Chumby so that you can make changes to the app structure. I still have a lot of exploration to make prior to hacking the box, but it is nice to see that they have put a lot of thought into what the device is capable of doing.
My gameplan is to hack the Chumby and use it as a robotics controller. the Chumby itself weighs very little, which is a great advantage. It has a wifi capability which enhances its communication power with my laptop. I have not bee successful at hooking the Chumby into our guest wireless at work due to the capture page issue. I haven't figured out what completely is needed to do that yet. The debugchumby file that I created does not hook into our Cisco system. One thing, I do not have a real good sense of the IP address of the proxy and the fact that the form is not named from the proxy may have something to do with it. More later.
Subscribe to:
Post Comments (Atom)
No comments:
Post a Comment