"There's finally an Indy on my desk instead of a Sun4. This means that I also have an IndyCam, so I hacked up a script to grab and save a frame of me sitting there every five minutes." (http://www.jwz.org/gruntle/nscpdorm.html)
I tried doing timed snapshots, but it frequently caught an empty chair. So I have it take a picture whenever I deactivate the screen saver, so I'm pretty much guaranteed to be in front of the machine. I also have hooks for other activities/events, like while I'm playing QuakeLive.
Ok, sorta tangent on this. It would be a very interesting study to take photos of a large sampling of drivers during a morning commute into a city. I wonder if you could get some information on what parts of the road really stress out the drivers and cause those grey hairs?
Plus lolcommits includes the commit message. Great for when some of our less technical folks work on the UI and regularly submit "SDF" as the commit message...
That should provide some entertainment later on. I look pretty ragged sometimes when I finally stumble across the line and commit something I've been at war with.
#!/usr/bin/env ruby
num_snaps = 5
time_int = Time.now.to_i
num_snaps.times do |i|
file="~/.gitshots/#{time_int}__#{i+1}_of_#{num_snaps}.jpg"
system "imagesnap -q #{file}"
end
exit 0
The problem with this code is it makes the camera go on and off successively, which creates a minimum delay between shots. It would be nicer to have finer control over the interval.
Picturesnap somehow supports sequences but there's no control to how long they should last (would require firing a background task), and snapshots get saved in the running directory (instead of based on the passed filename/path) which would require mving each file. Pull request could be a short and sweet free time project...
You're quite right. But we're still left with many problems stemmed from not having control on the sequence length and file names. I've tried it with a background task and the results are super flimsy. The time that the camera takes to be ready varies which then makes the number of files generated vary, sometimes the process is killed before imagesnap finished saving current file resulting in a corrupted image. And the file names outputted are really begging for some post-processing renaming.
This little hack takes a picture every hour (webcam and screenshot) and gives visualization of your online work habits: http://wanderingstan.com/lifeslice
I had a script that took a picture of my every half hour. This ran for about six months and gave me a brilliant insight into the ins and outs of my laptop usage.
I do something similar now and then with a script that takes a photo and a screen grab every minute throughout the day. The resulting 1-2 min movies can be quite fascinating to watch (for me at least).
I know this makes me a terrible person and I feel bad about what my brain is saying because someone went to the effort to create this and it's kind of cool if you're the kind of person who isn't creeped out by their own pictures, but my brain instinctually just keeps repeating, "Dang, that's coquetastic!"