Wikipedia:Bots/Requests for approval/DatBot 3


 * The following discussion is an archived debate. Please do not modify it. To request review of this BRFA, please start a new section at WT:BRFA. The result of the discussion was Symbol keep vote.svg Approved

DatBot 43
Operator:

Time filed: 11:45, Friday, November 4, 2019 (UTC)

Automatic, Supervised, or Manual: automatic

Programming language(s): Python

Source code available: My GitHub (outdated)

Function overview: Reports users who have either tripped 15 filters quickly in a list, a filter that is in an "immediate report" list, or a very suspicious username-related filter.

Links to relevant discussions (where appropriate):

Edit period(s): Continuous

Estimated number of pages affected: 2

Exclusion compliant (Yes/No): No

Already has a bot flag (Yes/No): Your

Function details: This task was previously done by. However, Z-bot and Z-man are currently inactive. I have used the previous code, but added a section for username-related filters that should be reported to UAA. If/once this task is approved (for trial), I will create User:DatBot/filters.js. It will contain immediate= vandalism= UAAreport= When the bot will report, it will contain the filter in the "reason for reporting" box. More details can be found at this BRFA.

Discussion

 * Wonder if using a in some way protected page that isn't a userjs page is also an option. Jo-Jo Eumerus (talk, contributions) 16:15, 4 November 2016 (UTC)
 * I believe that will also be fine. Extended-protected page that contains mostly only immediate =, vandalism = , UAAreport = and some comments starting with # should do the trick. Dat GuyTalkContribs 16:22, 4 November 2016 (UTC)
 * This is normally OK'd as it will let the operator and admins update it, but not others. —  xaosflux  Talk 02:33, 6 November 2016 (UTC)


 * Will which filters are in your scope, which are "immediate", be part of the onwiki config? If so, can you build this out? —  xaosflux  Talk 03:39, 6 November 2016 (UTC)
 * ✅ at a js per your comments and the fact that there are barely any non-admin EFMs. The non-admin EFMs I do know I'm sure can email an administrator. Also, I believe that Mr.Z-man thought of a hacky workaround, so that even if the filter is private it will still be able to access it? Either that or the filters haven't always been private. Dat GuyTalkContribs 11:01, 6 November 2016 (UTC)
 * Almost half of these filters (including all of the 'immediate' ones are private filters - do you expect to actually be able to have your bot use these? — xaosflux  Talk 16:23, 6 November 2016 (UTC)
 * I believe so. Z-bot never had EFM, but it was still able to perform. See also . I have no idea if in August the filter was private, but I believe that the code uses a workaround. There is also a library called "wikitools," so perhaps that was used as a workaround. Dat GuyTalkContribs 16:42, 6 November 2016 (UTC)
 * Can you by start making some private-trials (report to a bot subpage), verify if you are able to do what you expect - try configuring it for only the private filters and see if it actual works. — xaosflux  Talk 17:15, 6 November 2016 (UTC)
 * Going a bit out of your request. I've jsub'd it on Tool Labs. I want to see if everything works properly first, as I'm not sure if 1. The import modules still work and 2. If I configured the import modules properly. If it works for the night then I will change it so that it will be only private filters. Cheers, Dat GuyTalkContribs 19:15, 6 November 2016 (UTC)
 * One thing I want to see out of an eventual trial is you actually posting the reports, but to user space for review. — xaosflux  Talk 02:31, 7 November 2016 (UTC)
 * What do you mean? What I am trying to do now is post everything to the DatGuy sandbox. I've encountered a mystery error over the night, but restarted the job now. It was the only error, so if it is fixed it should work. Dat GuyTalkContribs 06:45, 7 November 2016 (UTC)
 * Fix didn't work, I'll try to debug it and ask for help. Dat GuyTalkContribs 14:54, 7 November 2016 (UTC) Christ, that was a stupid error. Probably fixed now, pending restarting of the task and hits. Dat GuyTalkContribs 15:14, 7 November 2016 (UTC)


 * , I have some great news. With the help of and some from  (with collaboration from ), we managed to get the bot working. It should start writing to my sandbox any second now. The only issue we encountered is that while debugging, for private filters, it does not find the filter. It just prints the user and the time. However, since administrators will check the filter log, I believe this won't be much of an issue if once we print to Wikipedia, it still does not work. It also prints to, as Mr.Z-bot did. If/when the task gets approved, I'll request to send an email to the EFM mailing list. Dat GuyTalkContribs 19:28, 8 November 2016 (UTC)
 * DatBot knows when private filters are tripped and on what page, but not which filter they are tripped on. I request approval of this bot, and hopefully later on I would be able to debug the reason why Mr.Z-bot was able to know what filter is hit. Dat GuyTalkContribs 19:19, 15 November 2016 (UTC)
 * The next step would be to move you to a trial for reporting to a live page - do you plan on sending to WP:AIV/AVB or somewhere else? — xaosflux  Talk 01:54, 17 November 2016 (UTC)
 * Administrator intervention against vandalism/TB2 and Usernames for administrator attention/Bot. The UAA currently doesn't work since the only filter there is private. Dat GuyTalkContribs 06:34, 17 November 2016 (UTC)
 * The bot also managed to find an annoying duckmaster, see Suix and co. Dat GuyTalkContribs 16:18, 18 November 2016 (UTC)


 * -, you are OK to start reporting to the noticeboards. Please be very responsive to any issues brought up and stop reporting if you are causing any problems.  Please report any presented and resolved problems here; please provide an update in a week after you start as to the status. —  xaosflux  Talk 16:34, 18 November 2016 (UTC)


 * 1) Private filters weren't found/used -
 * 2) Usernames were reported twice -
 * 3) Edit conflict (?) Results in page protected error

I'll keep updating this. Dat GuyTalkContribs 18:29, 19 November 2016 (UTC)
 * 1) Log became too big - Scheduled a crontab
 * May I add one thing for the code? I modified some of DeltaQuadBot's code (with permission and attribution for ) and now I have some notes. For example, at User:DatBot/testing, for filter 808, which is targeted against a specific sockmaster, it'll say:


 * - Tripped filter 808 (Dead rat/Woomoo vandal) ([ details]). DatBot
 * See Sockpuppet investigations/The Suix. [[User:DatBot|DatBot]

I could also make it single-line if requested. Dat GuyTalkContribs 19:18, 24 November 2016 (UTC)
 * Those seem fine, I don't think you need to clerk report on your own report though - single line notes that would be helpful. — xaosflux  Talk 20:14, 24 November 2016 (UTC)
 * Coded. However, bot is going to be down today while I sleep. Sorry. Dat GuyTalkContribs 21:15, 24 November 2016 (UTC)
 * Note system isn't going to be working for now while I attempt to fix an issue. For the summary, DatBot probably has around a 95% report-to-block ratio. The probable 2% has now been moved to vandalism (most of them were from immediate, such as Special:AbuseFilter/31), 1% is an issue with Special:AbuseFilter/168 that I'll try to nag some edit filters to change something, and the other 2% is users not being warned. Dat GuyTalkContribs 22:21, 25 November 2016 (UTC)


 * As it is not a specific amount of edits, I'll let it run until the day passes. Bot has received support at User talk:DatGuy/Archives/2016/December. Dat GuyTalkContribs 15:02, 2 December 2016 (UTC)
 * Can you put a short line on User:DatBot about what this (now basically primary task) is? — xaosflux  Talk 20:12, 2 December 2016 (UTC)
 * ✅ as best I can. Dat GuyTalkContribs 20:16, 2 December 2016 (UTC)


 * — xaosflux  Talk 20:19, 2 December 2016 (UTC)


 * The above discussion is preserved as an archive of the debate. Please do not modify it. To request review of this BRFA, please start a new section at WT:BRFA.