THOUGHTS in resque_stuck_queue-0.0.11 vs THOUGHTS in resque_stuck_queue-0.0.13

@@ -12,5 +12,12 @@
 ensure the logging gets flushed into log file correctly? (integration with god?)
 add a trap{} to force_stop. ok for overwriting process's trap handlers? use config for that?
 
 fix skeleton recipe https://github.com/shaiguitar/resque_stuck_queue/blame/master/README.md#L103
   raise appname, => :environment, log path
+
+set a redis key instead of doing a manual refresh and have a recover handler. also pass the lag time into the handlers/procs (same semantics)
+investigate: why is temple getting triggered? how often? is the enqueing/checking taking too much time?
+also, if one queue is bad, does it trigger other queue's handlers? write some tests, asshole.
+woes of redis namespace, in regards to Awsm.redis != Resque.redis etc. (which is important for setting the key through @redis)
+
+with lag time, it will continue to trigger, for every heartbeat time it's supposed to tick, find some way to do that, and then maybe add some resolved handler/proc?