Some work done towards this in merge request https://forge-allura.apache.org/p/allura/git/merge-requests/173/ to store the data in mongo, so at least it can be queried/reported.
A page to list the recent results would still be good to have. And when deleting a project or disabling a user, it would be nice to show the spam results, so individual items can be marked off and sent back to the spam filter for better training. That'd be more involved though to get all the submission params to match correctly. --- ** [tickets:#8021] Surface to spammy users to site admins** **Status:** open **Milestone:** unreleased **Created:** Tue Nov 10, 2015 06:44 PM UTC by Dave Brondsema **Last Updated:** Sun Dec 13, 2015 03:04 PM UTC **Owner:** nobody If a user's submissions is being frequently flagged as spam, either automatically or manually, that user should be listed for site admins to review (and likely disable). Content should include posts, or any other artifact (although not all artifacts go through the spam filtered checks yet). Not sure exactly how we should define "frequently". In the list of users for review, it would be nice to include their name, registration date, which projects they admin (in case the whole project is spam), number of spam items, total number of submitted items (via activitystream)?, small preview of spam items - or maybe just preview or link to all activity. So that site admins can easily judge if the user is generating mostly spam, or if it was a false positive report. --- Sent from forge-allura.apache.org because dev@allura.apache.org is subscribed to https://forge-allura.apache.org/p/allura/tickets/ To unsubscribe from further messages, a project admin can change settings at https://forge-allura.apache.org/p/allura/admin/tickets/options. Or, if this is a mailing list, you can unsubscribe from the mailing list.
