Change Details

Recently we should manually write down Extension:AbuseFilter's pattern (string match, regex, etc). It is a very hard for non-technical user (just a admin of a wiki) and consumes technical user's time. I propose a machine suggestion for AbuseFiliter's pattern to reduce such difficulties and cost. For example, when I put marks on some revisions or users, I can get the suggested pattern generated by machine learning which extracts points in common among the specified revisions or user's contributions. I don't have any concrete methods or implementations because I'm specialized in neither the machine learning or natural language processing. But I heard it's not impossible. --aokomoriuta (talk) 23:56, 9 November 2015 (UTC) This card tracks a proposal from the 2015 Community Wishlist Survey: https://meta.wikimedia.org/wiki/2015_Community_Wishlist_Survey This proposal received 0 support votes, and was ranked last out of 107 proposals. https://meta.wikimedia.org/wiki/2015_Community_Wishlist_Survey/Moderation_and_admin_tools#Suggesting_AbuseFilter_by_machine_learning

Currently, we should manually write down Extension:AbuseFilter's pattern (string match, regex, etc). It is a very hard task for non-technical users and consumes technical user's time. I propose a machine learning approach that would suggest patterns to be used for AbuseFiliter; this would reduce difficulties and development time. For example, when I put marks on some revisions or users, I can get the suggested pattern generated by machine learning which extracts points in common among the specified revisions or user's contributions. I don't have any concrete methods or implementations because I'm specialized in neither the machine learning or natural language processing. But I heard it's not impossible. --aokomoriuta (talk) 23:56, 9 November 2015 (UTC) This card tracks a proposal from the 2015 Community Wishlist Survey: https://meta.wikimedia.org/wiki/2015_Community_Wishlist_Survey This proposal received 0 support votes, and was ranked last out of 107 proposals. https://meta.wikimedia.org/wiki/2015_Community_Wishlist_Survey/Moderation_and_admin_tools#Suggesting_AbuseFilter_by_machine_learning

RecCurrently, we should manually write down Extension:AbuseFilter's pattern (string match, regex, etc). It is a very hard task for non-technical user (just a admin of a wiki)s and consumes technical user's time. I propose a machine learning approach that would suggestiont patterns to be used for AbuseFiliter's pattern to reduce such; this would reduce difficulties and costdevelopment time. For example, when I put marks on some revisions or users, I can get the suggested pattern generated by machine learning which extracts points in common among the specified revisions or user's contributions. I don't have any concrete methods or implementations because I'm specialized in neither the machine learning or natural language processing. But I heard it's not impossible. --aokomoriuta (talk) 23:56, 9 November 2015 (UTC) This card tracks a proposal from the 2015 Community Wishlist Survey: https://meta.wikimedia.org/wiki/2015_Community_Wishlist_Survey This proposal received 0 support votes, and was ranked last out of 107 proposals. https://meta.wikimedia.org/wiki/2015_Community_Wishlist_Survey/Moderation_and_admin_tools#Suggesting_AbuseFilter_by_machine_learning