Page MenuHomePhabricator

Sockpuppet detection through text mining & machine learning
Open, LowestPublic

Description

This card tracks a proposal from the 2015 Community Wishlist Survey: https://meta.wikimedia.org/wiki/2015_Community_Wishlist_Survey

This proposal received 6 support votes, and was ranked #82 out of 107 proposals. https://meta.wikimedia.org/wiki/2015_Community_Wishlist_Survey/Moderation_and_admin_tools#Machine_learning_to_identify_sockpuppets

Event Timeline

ToAruShiroiNeko claimed this task.
ToAruShiroiNeko raised the priority of this task from to Needs Triage.
ToAruShiroiNeko updated the task description. (Show Details)
ToAruShiroiNeko added a subscriber: ToAruShiroiNeko.
Restricted Application added a subscriber: Aklapper. · View Herald TranscriptJul 31 2015, 4:59 PM
He7d3r added a subscriber: He7d3r.Jul 31 2015, 5:07 PM
Aklapper renamed this task from Sockpupet detection through text mining & machine learning to Sockpuppet detection through text mining & machine learning.Jul 31 2015, 6:09 PM
Aklapper set Security to None.
ToAruShiroiNeko triaged this task as Lowest priority.Aug 3 2015, 2:08 AM
IMPORTANT: If you are a community developer interested in working on this task: The Wikimedia Hackathon 2016 (Jerusalem, March 31 - April 3) focuses on #Community-Wishlist-Survey projects. There is some budget for sponsoring volunteer developers. THE DEADLINE TO REQUEST TRAVEL SPONSORSHIP IS TODAY, JANUARY 21. Exceptions can be made for developers focusing on Community Wishlist projects until the end of Sunday 24, but not beyond. If you or someone you know is interested, please REGISTER NOW.
DannyH updated the task description. (Show Details)Feb 6 2016, 12:27 AM
jrbs moved this task from Backlog to Security/Abuse on the Trust-and-Safety board.May 3 2017, 11:48 PM
Harej moved this task from Ideas to Epic on the Machine Learning Platform board.Apr 3 2019, 5:01 AM
Aklapper removed ToAruShiroiNeko as the assignee of this task.Jun 19 2020, 4:31 PM

This task has been assigned to the same task owner for more than two years. Resetting task assignee due to inactivity, to decrease task cookie-licking and to get a slightly more realistic overview of plans. Please feel free to assign this task to yourself again if you still realistically work or plan to work on this task - it would be welcome!

For tips how to manage individual work in Phabricator (noisy notifications, lists of task, etc.), see https://phabricator.wikimedia.org/T228575#6237124 for available options.
(For the records, two emails were sent to assignee addresses before resetting assignees. See T228575 for more info and for potential feedback. Thanks!)