tracking

I use this to functions as a base of my tracking algorithm. //1. detect the features cv::goodFeaturesToTrack(gray_prev, // the image features, // the output detected features max_count, // the maximum number of features qlevel, // quality level minDist); // min distance between two features // 2. track features cv::calcOpticalFlowPyrLK( gray_prev, gray, // 2 consecutive images points_prev, // input point positions in first im points_cur, // output point positions in the 2nd status, // tracking success err); // tracking error cv::calcOpticalFlowPyrLK takes vector of points from the previous

Litmus released an email analytics service last month (may 2010). See here: http://litmusapp.com/email-analytics They boast a very cool "read rate" tracking: they can track normal reads, Skims, and Glanced/Deleted. How can they track skims and glanced/deleted? This to me seems impossible :) They also track forwards and prints. Prints are easy (they include a css @media print query with a bg image). But forwards? I think this might be a combo between subsequent opens and different IPs/reffering URLs. However, this means that if I open my mail and re-read it from another computer, it counts as a

Since Facebook introduced hashtags, I've been interested in finding out more about them. Can someone point me in the direction of possibly tracking the hashtags similar to how twitter allows us access to pull hashtag data via their API. I can count mentions, get usernames, and the tweets. Has Facebook launched anything similar? I can't find any documentation online. Igy There is currently no API for the hashtags feature on Facebook edit : there was however a public posts search function which will return some public posts with a certain hashtag if you use that hashtag as the search string in

Normally, the referrer is traceable through: JavaScript's document.referrer The request headers, e.g. PHP's $_SERVER['HTTP_REFERER'] I have set up a Codepad demo which shows these properties, for testing purposes. Requirements: The original referrer should effectively be hidden, at least for all mouse events. Cross-browser support (at least Chrome and Firefox). Stand-alone, without any external content (plugins, libraries, redirection pages, ...). No side-effects: Links should not be rewritten, history entries should be preserved . The solution will be used to hide the referrer when following

I am in charge of about 100+ documents (word document, not source code) that needs revision by different people in my department. Currently all the documents are in a shared folder where they will retrieve, revise and save back into the folder. What I am doing now is looking up the "date modified" in the shared folder, opened up recent modified documents and use the "Track Change" function in MS Word to apply the changes. I find this a bit tedious. So will it be better and easier if I commit this in a version control database? Basically I want to keep different version of a file. What have I