#4 actions specified by users

[Gerard Vignes]

currently actions are hard-coded into three categories:
1. exclude
2. include
3. skip
and the user specified the location of 4 report files:
1. index
2. excluded
3. included
4. skipped

the user should be able to spedify actions like:

* file://mypath/myfile.xml to save to local file

* mailto:mylogin@mydomain.com

* http://mydomain/mypath.php?action=post

there should be only one hardcoded action, the default which skips a post and logs it to the local file skipped

[Gerard Vignes]

this requires changes to the current way of reporting filter results; since reports contain so much redundant code, this is a good excuse to re-architect that part of the code and significantly increase the options available to the user; it should be easy for the user to accept a default reporting configuration that makes sense, but they should also be able to extend that configuration to report results in interesting and useful ways; the changes needed for this feature are architectural and not trivial, but they are necessary and worth the effort; this should be done once more serious outstanding issues are resolved;

[Gerard Vignes]

system actions are llimited to: exclude, include and skip;
user actions will be applied to these system actions (probably only to include);
initially, user actions will provide email and micro/blog post; i can test these, since i don't have a cell phone in greenville; when i get back to seattle i will get another cell phone;