We've been alpha testing sensr.net for a few months now. I got an email from one of our early users that his camera caught a thief in action. See the shots below.
Unfortunately they haven't caught the guy, yet. At least the neighbors have been warned and they know what the guy looks like so they can keep an eye out for him in the future.
Wednesday, December 23, 2009
Wreath Thief Caught on sensr.net
Posted by
adam
at
7:43 AM
0
comments
Labels: network cameras, security, sensr.net
Love is all you need
A touching video from Starbucks.
My favorites are the wacky folks from Japan and Denmark.
Click here to view on YouTube.
Posted by
adam
at
7:08 AM
0
comments
Monday, November 23, 2009
Tuesday, November 10, 2009
sensr.net live
About a year ago I started playing around with the idea of monitoring various things around the house. We travel a lot and I wanted to be able to check on the house while I was out of town. I started playing with network cameras and found that it was cool to have remote access to a camera back home, but setting it up and monitoring it was a pain. I tried Linux, PC, and Mac software but I didn't like the idea of having a dedicated computer inside my house to do the monitoring. My PhD is in distributed computing, so it's only fitting that my home to be monitored in the cloud.
I started building a website for monitoring my cameras and realized that this could be a useful service for others and might even be a nice business. In the course of the last year I've been lucky enough to hook up with some incredibly talented folks who have joined me in this effort. We're now ready to start opening up the site for others to try. It's not perfect and it's not for everyone, but sensr.net is at least ready for the hacker class to try.
How does it work?
Basically we'll provision an FTP account for each of your cameras and process all the images it sends to us. We keep images where we've detected motion and organize them by time and date. Want to know what time the plumber left? Check the front door camera, archived on sensr.net.
We'll also send you alerts (email or text) if you want. This works great on indoor cameras when you're away from home. Of course you may get notified about motion that you don't care about. Here's one alert I got a while back that would have been annoying had it come at 3 am.
Moth caught mid-flight.
Why the cloud?
Nobody runs their own email server anymore, why should you run a home server?
- Infinite disk space: You don't have to worry that the PC in your basement is going to run out of disk just before your house gets robbed.
- Elastic compute infrastructure: We can build all kinds of interesting computer vision algorithms to process your images. Right now we're starting with simple motion detection, but once the pipeline is setup, we can add other kinds of processing. Face detection should be easy. Face recognition is doable. Tagging your images with text could be next. Having our infrastructure in the cloud allows us to be creative and try new kinds of processing without requiring you to install anything.
- Nothing to manage: Our users don't have to worry about the care and feeding of a PC. We'll deal with all those hassles for them.
- Disaster recovery: If your house is robbed, we'll still have pictures of the thieves, even if they steal the camera. If your house burns down, all the images we've stored for you will still be there.
Why FTP?
FTP may seem like an anachronism, but in this case I think it makes a lot of sense. The issue is the home firewall. These days everyone has a firewall, so our servers can't reach into your network and pull images from your cameras. With FTP your camera will push images to our servers. Users don't need to configure confusing port forwarding options on their firewall.
Why Facebook Connect?
Do your really want another user name and password to remember? I didn't think so. That's one reason we use Facebook Connect for authentication. Besides, this makes it easy for you to share access to your cameras with your friends. BTW, you don't have to share whole cameras. You can mark a camera as private, then only share interesting images by uploading them to Facebook in a single click.
Not on Facebook yet? (Really?) Well, you can still peruse the public cameras. If you want to add your own camera or see cameras that your friends have added, you'll have to sign up for a Facebook account. Facebook accounts are free you know.
Give it a try!
So if you have a network camera that supports FTP, head over to sensr.net and give it a try. If you want to use the camera built into your PC or a USB camera you can make that work too. See the sensr.net FAQ for details.
Posted by
adam
at
5:27 PM
1 comments
Labels: cameras, monitoring, network camera, sensr.net, webcam
Saturday, October 31, 2009
Big Island Damage
even get up. The kite ended up in the waves and suffered a big rip.
It seems that 9 times out of 10 I need a bigger kite. I guess it's
time to look into a 12 because this 10 isn't doing it for me.
Posted by
adam
at
12:10 PM
0
comments
Tuesday, October 20, 2009
Tesla Model S Infotainment Center
Cool video on the design of the Model S. Can't wait for this.
For the UI geeks, skip to minute 28 or so to get to the juicy bits.
Towards the end of the talk in the Q&A they mention the possibility of a Tesla App store. Basically the idea is to keep it flexible and customizable. Sweet!
Posted by
adam
at
10:08 AM
0
comments
Sunday, October 4, 2009
Salted Chrome
According to CNet there is now a NaCL (Native Client) version of Chrome. Since the early days of the web, computer scientists have tried to come up with ways to programmaticly extended the browser. It started with slow Java Applets and led to scary ActiveX implementations. Today most developers stick with Javascript or Flash.
This latest effort from Google might actually have a chance at success. It seems to strike a nice balance between performance and security. Of course a huge obstacle will be adoption. Including NaCL in Chrome is a significant step forward, but Chrome is has a very small percentage of the browser market. Perhaps if the Chrome experiment goes well, Google can get Firefox to include NaCL. I still don't see Microsoft supporting NaCL in IE, so compared to Javascript and Flash, it's going to be a long uphill battle for widespread adoption. I suppose NaCL browser plugins/extensions for Firefox and IE might be one way to gain further adoption. Maybe they could deliver it as an iPhone App as a way to finally get Google Voice on the iPhone. :-)
I'll be interested to see how it goes. I'll give it a try when the Mac version comes out.
Posted by
adam
at
9:40 PM
1 comments

