{"action":"created","issue":{"url":"https://api.github.com/repos/willemarcel/osmcha-django/issues/14","labels_url":"https://api.github.com/repos/willemarcel/osmcha-django/issues/14/labels{/name}","comments_url":"https://api.github.com/repos/willemarcel/osmcha-django/issues/14/comments","events_url":"https://api.github.com/repos/willemarcel/osmcha-django/issues/14/events","html_url":"https://github.com/willemarcel/osmcha-django/issues/14","id":126673727,"number":14,"title":"Using osmcha to detect vandals","user":{"login":"planemad","id":126868,"avatar_url":"https://avatars.githubusercontent.com/u/126868?v=3","gravatar_id":"","url":"https://api.github.com/users/planemad","html_url":"https://github.com/planemad","followers_url":"https://api.github.com/users/planemad/followers","following_url":"https://api.github.com/users/planemad/following{/other_user}","gists_url":"https://api.github.com/users/planemad/gists{/gist_id}","starred_url":"https://api.github.com/users/planemad/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/planemad/subscriptions","organizations_url":"https://api.github.com/users/planemad/orgs","repos_url":"https://api.github.com/users/planemad/repos","events_url":"https://api.github.com/users/planemad/events{/privacy}","received_events_url":"https://api.github.com/users/planemad/received_events","type":"User","site_admin":false},"labels":[],"state":"open","locked":false,"assignee":null,"milestone":null,"comments":6,"created_at":"2016-01-14T15:09:27Z","updated_at":"2016-01-18T10:42:25Z","closed_at":null,"body":"@willemarcel first off, love your work in making osmcha, its one of the most promising monitoring tools I have come across for mappers to keep a track of changes to their area. My colleage @batpad just setup [a global instance](http://ec2-52-90-240-32.compute-1.amazonaws.com/) that I have been poking around with to see if it can be used to catch map vandals :skull: , a technically challenging problem that nobody has successfully solved.\r\n\r\nI'm interested in spending some more time exploring osmcha to review the flagged changesets and provide feedback to improve the detection rules, but it has been hard to keep up with the growing volume of data everyday. Is there any mechanism to quickly filter the data to a smaller subset that would make it easier to review? "},"comment":{"url":"https://api.github.com/repos/willemarcel/osmcha-django/issues/comments/172494350","html_url":"https://github.com/willemarcel/osmcha-django/issues/14#issuecomment-172494350","issue_url":"https://api.github.com/repos/willemarcel/osmcha-django/issues/14","id":172494350,"user":{"login":"batpad","id":72280,"avatar_url":"https://avatars.githubusercontent.com/u/72280?v=3","gravatar_id":"","url":"https://api.github.com/users/batpad","html_url":"https://github.com/batpad","followers_url":"https://api.github.com/users/batpad/followers","following_url":"https://api.github.com/users/batpad/following{/other_user}","gists_url":"https://api.github.com/users/batpad/gists{/gist_id}","starred_url":"https://api.github.com/users/batpad/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/batpad/subscriptions","organizations_url":"https://api.github.com/users/batpad/orgs","repos_url":"https://api.github.com/users/batpad/repos","events_url":"https://api.github.com/users/batpad/events{/privacy}","received_events_url":"https://api.github.com/users/batpad/received_events","type":"User","site_admin":false},"created_at":"2016-01-18T10:42:25Z","updated_at":"2016-01-18T10:42:25Z","body":"To summarize points above and add some of my own thoughts about the users question:\r\n\r\n - When importing changesets, fetch additional metadata about the user. We would need to either find an existing API that allows us to query it, or build our own for this. Would be something like this: http://hdyc.neis-one.org/user/PlaneMad (we would need to ask permission if we want to use this, but am giving it as an example here). We then store those extended attributes in a `users` table or so in osmcha-django. We can then users the user attributes to filter changesets - for eg. if we don't want to see changesets by a user who has more than 10,000 edits to their name, etc.\r\n\r\n - Give instances the option to have something like USERS_WHITELIST defined in project `settings`. I am not very happy with this idea for the same reason you mention, @willemarcel - it will not be suitable for a community instance.\r\n\r\n - Track the number of changesets of each user that has been marked \"verified good\" and \"verified bad\". Display this number on the changesets list and allow people to filter by this. So, for eg. I can say \"do not show me changesets for users that have more than 5 changesets already verified as good\". Or, the reverse, \"filter to show me all changesets of users that have had at least 1 changeset marked as bad\".\r\n\r\n - Maintain a \"per reviewer\" white-list and black-list. So I can white-list a user and their changesets will never show up as suspicious for me, but will still show up for other users.\r\n\r\n@willemarcel if any / all of these seem interesting to implement, let me know and I'll open separate tickets for each and we can see how best to implement. Thanks :)\r\n\r\n"}}