Wikipedia:Bots/Requests for approval/SDZeroBot 5
Appearance
Blocked
[edit]- but the approved task is having unfortunate side effects in destroying data from the critical page used by several of the most active AFC reviewers, Category:AfC G13 eligible soon submissions . I'm blocking the bot pending further discussion. DGG ( talk ) 05:20, 26 October 2020 (UTC) �
- the destruction caused this bot task. can apparently not be undone; I will unblock when I am assured that future operations will be as they should be.
- {{Primefac}},[1] when you approved the task, you apparently were relying upon SD0001 statement that they "don't really see this task as being much relevant to either NPR or AFC." When he said "There is a small set of people who review bad draftications, G13 nominations etc but there isn't any organized project", that's not a reason for not notifying the people who do use it, such as me or Liz and making sure we understood. The jump from a test of 50 to a production run of 3000 can be too large a jump to see problems . AFCH is problematic enough when it works as it is supposed to. DGG ( talk ) 18:44, 26 October 2020 (UTC) �
- Assuming you meant to ping @Primefac:. Sidenote, do you have diffs of the faulty edits? Or a link to contribs with a list of them? I don't see them in recent contribs, assuming it will make it easier for people to review. ProcrastinatingReader (talk) 22:09, 26 October 2020 (UTC)
- Followup, with the caveat I know minimal about AfC, if the issue is that a bot made an edit, thus it's not going to go into the category, it feels like a category issue for not checking for human (excl bot) editors? At the same time, this bot only works on past draftifications (JJMC89 bot is for future), and this bot's one-time run is already done, whatever harm it may or may not have done, so keeping it blocked doesn't seem to be resolving anything. It may be appropriate to unblock it to allow its regular tasks to keep running. ProcrastinatingReader (talk) 22:14, 26 October 2020 (UTC)
- Followup #2: Is the only check we have to populate Category:G13 eligible AfC submissions based off the REVISIONTIMESTAMP code in Template:AFC submission/draft? If that's the issue here, then yes, can't be fixed in this way, and also seems like a weak way to do G13 given it won't work on draftspace articles without the template. Is there not a bot that goes around tagging upcoming-G13-deletions? If so, that bot should be able to filter out bot edits, and so this bot task shouldn't affect it. If not, a bot could always be coded up to do just that. ProcrastinatingReader (talk) 22:20, 26 October 2020 (UTC)
- DGG, I'll give you the opportunity to unblock the bot before I do so myself, but as has been mentioned in multiple places now, the bot run is long over, damage done; the bot has other (more important and less "disruptive") tasks that it needs to be doing. It's something to keep in mind for future draft-space edits, that's for sure, but that's about all to be done here. Primefac (talk) 00:49, 27 October 2020 (UTC)
- Followup #2: Is the only check we have to populate Category:G13 eligible AfC submissions based off the REVISIONTIMESTAMP code in Template:AFC submission/draft? If that's the issue here, then yes, can't be fixed in this way, and also seems like a weak way to do G13 given it won't work on draftspace articles without the template. Is there not a bot that goes around tagging upcoming-G13-deletions? If so, that bot should be able to filter out bot edits, and so this bot task shouldn't affect it. If not, a bot could always be coded up to do just that. ProcrastinatingReader (talk) 22:20, 26 October 2020 (UTC)
- Followup, with the caveat I know minimal about AfC, if the issue is that a bot made an edit, thus it's not going to go into the category, it feels like a category issue for not checking for human (excl bot) editors? At the same time, this bot only works on past draftifications (JJMC89 bot is for future), and this bot's one-time run is already done, whatever harm it may or may not have done, so keeping it blocked doesn't seem to be resolving anything. It may be appropriate to unblock it to allow its regular tasks to keep running. ProcrastinatingReader (talk) 22:14, 26 October 2020 (UTC)
- you are right, and I unblocked. I would have done so a few hours earlier, but I needed to have dinner. DGG ( talk ) 04:40, 27 October 2020 (UTC)
- @DGG and Liz: Here you go. Not a perfect list, and needs to exclude all the "Missing encyclopaedic articles" entries, but filters out likely bot / totally routine maintenance edits. Some on the list don't qualify, but at a flick the majority do. ProcrastinatingReader (talk) 14:46, 27 October 2020 (UTC)
- Assuming you meant to ping @Primefac:. Sidenote, do you have diffs of the faulty edits? Or a link to contribs with a list of them? I don't see them in recent contribs, assuming it will make it easier for people to review. ProcrastinatingReader (talk) 22:09, 26 October 2020 (UTC)
- I appreciate this, but it is not really a satisfactory replacement in the logner run. For every item, I need to paste the title into a WP search box. With what we had before, I could hover over the titles, which is at least twice as fast, and, as about 9/10 of them aren't worth working on further once they been looked at by hovering, this now give me 20 times the work. . It's difficult enough to keep up , using what we had 2 weeks ago, as there are just 2 or 3 people responsible for checking the hundreds of articles a day. It's impossible with this if this is the way it will continue.
I hope this is intended just as a temporary fix for this months problem, and everything in the future will still return to the old way of listing. for everything reaching 5 months from today onwards. DGG ( talk ) 18:58, 27 October 2020 (UTC)