This is an archive of past discussions with User:DatGuy. Do not edit the contents of this page. If you wish to start a new discussion or revive an old one, please do so on the current talk page.

DatBot does a good job at reporting vandals to AIV. However, I noticed they sometimes add reports even if another report is present in the user section. This 2nd report is redundant and often not needed. I feel it would be better to have DatBot check if there is already a report in the user section and not add the report if one is already there, similar to Twinkle's function of reminding you that a bot report is present if you try to report someone when there is already a report for them by a bot. interstatefive  (talk) - just another roadgeek 01:35, 3 April 2022 (UTC)__DTREPLYBUTTONSCONTENT__-->__DTELLIPSISBUTTON__{"threadItem":{"timestamp":"2022-04-03T01:35:00.000Z","author":"InterstateFive","type":"comment","level":1,"id":"c-InterstateFive-2022-04-03T01:35:00.000Z-Suggestion_for_DatBot","replies":["c-DatGuy-2022-04-04T17:38:00.000Z-InterstateFive-2022-04-03T01:35:00.000Z"]}}-->

@InterstateFive: I have thought about this, but where ClueBot and other user reports apply to user edits and vandalism through warnings, DatBot may trigger twice on different filters, one of which could prevent an edit much more harmful than certain edits caught by other filters. There also already is a small mechanism to make sure reports aren't spammed. [1] for example was triggered for edits four hours apart, rather than minutes. Dat Guy^Talk_Contribs 17:38, 4 April 2022 (UTC)__DTREPLYBUTTONSCONTENT__-->__DTELLIPSISBUTTON__{"threadItem":{"timestamp":"2022-04-04T17:38:00.000Z","author":"DatGuy","type":"comment","level":2,"id":"c-DatGuy-2022-04-04T17:38:00.000Z-InterstateFive-2022-04-03T01:35:00.000Z","replies":[],"displayName":"Dat Guy"}}-->

Not sure if I'm missing something here, but DatBot reported 96.248.121.106 for filter 793 (Common spam/scam phone numbers), except nothing appears in this IP's filter log. Wanted to send it your way for a second look. Best, Spencer^T•C 00:57, 12 April 2022 (UTC)__DTREPLYBUTTONSCONTENT__-->__DTELLIPSISBUTTON__{"threadItem":{"timestamp":"2022-04-12T00:57:00.000Z","author":"Spencer","type":"comment","level":1,"id":"c-Spencer-2022-04-12T00:57:00.000Z-DatBot_AIV_report_without_any_logged_edits","replies":["c-DatGuy-2022-04-12T14:54:00.000Z-Spencer-2022-04-12T00:57:00.000Z"]}}-->

@Spencer: this happened once before, also on filter 793, and I'm still not sure what causes the mismatch. Suffusion of Yellow said the edits were oversighted, but since it's a spam filter perhaps it was instead caught by a global blacklist? On an irrelevant note, could you do me a favour and delete the User talk:DatGuy/sandbox0-22 pages found here? Thanks. Dat Guy^Talk_Contribs 14:54, 12 April 2022 (UTC)__DTREPLYBUTTONSCONTENT__-->__DTELLIPSISBUTTON__{"threadItem":{"timestamp":"2022-04-12T14:54:00.000Z","author":"DatGuy","type":"comment","level":2,"id":"c-DatGuy-2022-04-12T14:54:00.000Z-Spencer-2022-04-12T00:57:00.000Z","replies":["c-Suffusion_of_Yellow-2022-04-12T18:14:00.000Z-DatGuy-2022-04-12T14:54:00.000Z"],"displayName":"Dat Guy"}}-->

@Spencer: Yep, this was probably Special:AbuseLog/32359531 which was oversighted. DatGuy, you may want to add a FAQ... Suffusion of Yellow (talk) 18:14, 12 April 2022 (UTC)__DTREPLYBUTTONSCONTENT__-->__DTELLIPSISBUTTON__{"threadItem":{"timestamp":"2022-04-12T18:14:00.000Z","author":"Suffusion of Yellow","type":"comment","level":3,"id":"c-Suffusion_of_Yellow-2022-04-12T18:14:00.000Z-DatGuy-2022-04-12T14:54:00.000Z","replies":["c-Spencer-2022-04-13T03:35:00.000Z-Suffusion_of_Yellow-2022-04-12T18:14:00.000Z"]}}-->

Thank you for the clarification; DatGuy, 0-22 are deleted. Best, Spencer^T•C 03:35, 13 April 2022 (UTC)__DTREPLYBUTTONSCONTENT__-->__DTELLIPSISBUTTON__{"threadItem":{"timestamp":"2022-04-13T03:35:00.000Z","author":"Spencer","type":"comment","level":4,"id":"c-Spencer-2022-04-13T03:35:00.000Z-Suffusion_of_Yellow-2022-04-12T18:14:00.000Z","replies":[]}}-->

Last file-space edit is March 31, and the backlog of images needing resizing is building up. * Pppery * _{it has begun...} 01:27, 17 April 2022 (UTC)__DTREPLYBUTTONSCONTENT__-->__DTELLIPSISBUTTON__{"threadItem":{"timestamp":"2022-04-17T01:27:00.000Z","author":"Pppery","type":"comment","level":1,"id":"c-Pppery-2022-04-17T01:27:00.000Z-DatBot_seems_to_have_stopped_resizing_images","replies":["c-DatGuy-2022-04-17T16:19:00.000Z-Pppery-2022-04-17T01:27:00.000Z"],"displayName":"* Pppery *"}}-->

Should be fixed, along with wikiwork. Dat Guy^Talk_Contribs 16:19, 17 April 2022 (UTC)__DTREPLYBUTTONSCONTENT__-->__DTELLIPSISBUTTON__{"threadItem":{"timestamp":"2022-04-17T16:19:00.000Z","author":"DatGuy","type":"comment","level":2,"id":"c-DatGuy-2022-04-17T16:19:00.000Z-Pppery-2022-04-17T01:27:00.000Z","replies":[],"displayName":"Dat Guy"}}-->