Wikipedia:Bots/Requests for approval/BaranBOT 7
- The following discussion is an archived debate. Please do not modify it. To request review of this BRFA, please start a new section at Wikipedia:Bots/Noticeboard. The result of the discussion was Approved.
Operator: DreamRimmer (talk · contribs · SUL · edit count · logs · page moves · block log · rights log · ANI search)
Time filed: 04:43, Wednesday, September 18, 2024 (UTC)
Automatic, Supervised, or Manual: automatic
Programming language(s): Python
Source code available:
Function overview: Notify creators of drafts that the page hasn't been edited in at least 5 months, and therefore the page may be deleted soon. Backup for FireflyBot Task 11.
Links to relevant discussions (where appropriate): Wikipedia:Bots/Noticeboard#User:FireflyBot
Edit period(s): Every 4 hours
Estimated number of pages affected: ~100 per day
Exclusion compliant (Yes/No): Yes
Already has a bot flag (Yes/No): Yes
Function details: This bot will notify the creators of drafts that the page hasn't been edited in at least 5 months and may therefore be deleted soon. It is a backup for FireflyBot Task 11. Firefly has not edited since 29 July 2024, and their bot task, which notifies creators of drafts that the page hasn't been edited in at least 5 months, stopped on 3 September 2024. Liz left them a message on their talk page and sent an email but has not received any response. I also noticed that Firefly's activity has been very low over the past year, so I want to use my bot, BaranBOT, as a backup until Firefly restarts their bot task. I will use the same script with the same functionality. I will stop this bot once Firefly restarts theirs and will use it only when their bot is down.
Discussion
edit- I think this will be useful to run as a permanent backup, as the task is critical and the existing bots have had a poor track record over the years. FireflyBot also doesn't filter out bot edits while considering the last edit dates (bot edits don't affect G13 eligibility).Assuming FireflyBot sends the notification 5 months after the last edit, this bot could run at 5 months + 3 days (say), and send the notification if FireflyBot didn't already do it. – SD0001 (talk) 17:37, 18 September 2024 (UTC)[reply]
- Firefly bot seems to be back up; can we still test this while it is running? Primefac (talk) 13:31, 25 September 2024 (UTC)[reply]
- Primefac: There are some database permission-related issues, but they will not affect anything for now, and I will take care of them when Firefly comes online. For now, we can test this bot without any problems if you can approve a trial. The FireflyBot runs at the 1st minute of each UTC hour, so for the trial, I can run my bot between the 5th to the 55th minutes of a UTC hour. – DreamRimmer (talk) 18:05, 13 October 2024 (UTC)[reply]
- Approved for trial. Please provide a link to the relevant contributions and/or diffs when the trial is complete. Will probably be worth coordinating with Firefly to avoid duplicate posts being made on user talk pages. Primefac (talk) 18:28, 13 October 2024 (UTC)[reply]
- Primefac: Can we make this trial time-based, maybe for just one hour/day? When the bot runs, it goes through a full cycle and sends notifications for all drafts that meet the criteria at that time. This makes it tough to stop after just five edits. For instance, if there are 10 drafts that qualify in the first run, it will notify for all of them, and we can't just stop after notifying five. If we do stop it (using Ctrl + C), it will only make edits but won't record anything in the database. The first run probably won't have many pages since the FireflyBot is running continuously. Also, I won't be posting any duplicate notifications, and I am already in touch with Firefly. – DreamRimmer (talk) 18:59, 13 October 2024 (UTC)[reply]
- That's fine, makes sense. Primefac (talk) 19:10, 13 October 2024 (UTC)[reply]
- Trial complete. Notified 9 users. Everything worked as intended. I would like to improve its functionality in the future. For example, the current bot only notifies about a draft once, and if that draft becomes eligible for a notification again in the future, it will not send another notification. I plan to fix this so that the bot can notify again if the same draft meets the notification criteria in the future. I am not going to make any changes for now and will post on the relevant talk pages before making any modifications, and will file a new BRFA if needed. For now, I will work on filtering out bot edits and run it as SD0001 suggested. – DreamRimmer (talk) 03:27, 14 October 2024 (UTC)[reply]
- Approved. Minor changes such as the ones you described will not necessarily require a new BRFA (as they are not changing the actual functionality), though if you feel they might be breaking changes by all means ping BAG on the talk page and we can talk expansion. Primefac (talk) 11:50, 20 October 2024 (UTC)[reply]
- Trial complete. Notified 9 users. Everything worked as intended. I would like to improve its functionality in the future. For example, the current bot only notifies about a draft once, and if that draft becomes eligible for a notification again in the future, it will not send another notification. I plan to fix this so that the bot can notify again if the same draft meets the notification criteria in the future. I am not going to make any changes for now and will post on the relevant talk pages before making any modifications, and will file a new BRFA if needed. For now, I will work on filtering out bot edits and run it as SD0001 suggested. – DreamRimmer (talk) 03:27, 14 October 2024 (UTC)[reply]
- That's fine, makes sense. Primefac (talk) 19:10, 13 October 2024 (UTC)[reply]
- Primefac: Can we make this trial time-based, maybe for just one hour/day? When the bot runs, it goes through a full cycle and sends notifications for all drafts that meet the criteria at that time. This makes it tough to stop after just five edits. For instance, if there are 10 drafts that qualify in the first run, it will notify for all of them, and we can't just stop after notifying five. If we do stop it (using Ctrl + C), it will only make edits but won't record anything in the database. The first run probably won't have many pages since the FireflyBot is running continuously. Also, I won't be posting any duplicate notifications, and I am already in touch with Firefly. – DreamRimmer (talk) 18:59, 13 October 2024 (UTC)[reply]
- Approved for trial. Please provide a link to the relevant contributions and/or diffs when the trial is complete. Will probably be worth coordinating with Firefly to avoid duplicate posts being made on user talk pages. Primefac (talk) 18:28, 13 October 2024 (UTC)[reply]
- Primefac: There are some database permission-related issues, but they will not affect anything for now, and I will take care of them when Firefly comes online. For now, we can test this bot without any problems if you can approve a trial. The FireflyBot runs at the 1st minute of each UTC hour, so for the trial, I can run my bot between the 5th to the 55th minutes of a UTC hour. – DreamRimmer (talk) 18:05, 13 October 2024 (UTC)[reply]
- Firefly bot seems to be back up; can we still test this while it is running? Primefac (talk) 13:31, 25 September 2024 (UTC)[reply]
- 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 Wikipedia:Bots/Noticeboard.