Operator: Anomie ( talk · contribs · SUL · edit count · logs · page moves · block log · rights log · ANI search)
Time filed: 13:35, Thursday, April 29, 2021 ( UTC)
Function overview: Apply pending changes protection to TFAs while they are on the Main Page.
Automatic, Supervised, or Manual: Automatic
Programming language(s): Perl
Source code available: User:AnomieBOT/source/tasks/TFAProtector.pm
Links to relevant discussions (where appropriate): Wikipedia talk:Today's featured article#Pending changes TFA trial, Special:PermanentLink/1017460384#Pending-changes protection of Today's featured article
Edit period(s): Hourly, but typically will only apply protection once per day.
Estimated number of pages affected: 1 per day
Namespace(s): Article
Exclusion compliant (Yes/No): N/A, does not edit
Adminbot (Yes/No): Yes
Function details: The bot will apply pending changes protection to a TFA about an hour before it begins to be featured on the main page, set to expire an hour after the featuring ends. The day's TFA is identified using the date's subtemplate of Template:TFA title.
It will also re-check each hour to ensure that someone has not removed the protection. If an existing PC protection would end before the bot's protection would, the bot will extend it. It will not shorten any existing PC protection that lasts longer than the protection it would apply.
Note this task is itself a trial, per the RFC. The code at present will refuse to run beyond May 31, 2021 at 22:00 UTC (i.e. it will protect TFAs through the end of May, but will stop before it would protect June 1's TFA). After that it will be up to interested people to hold another RFC to determine whether consensus exists to continue the task. If that consensus exists, I'll remove the relevant code to allow the bot to continue running (without a subsequent BRFA).
I ran the task once already with a hack to point it at Wikipedia:Pending changes/Testing/9 instead of the actual TFA (and with the reason hacked too), to validate that the stabilize API call worked as expected. I'd have used a userspace page, but PC protection can't be used in userspace. Anomie ⚔ 13:35, 29 April 2021 (UTC) reply
Trial complete.
Here are all the log entries. Of note:
As noted above, even if this is approved now I won't run the task until a followup RFC determines that the task should proceed. As far as this BRFA goes, I'd personally go ahead and approve it with that understanding since there's nothing left for BAG to do here other than rubber-stamping that RFC. Anomie ⚔ 22:27, 31 May 2021 (UTC) reply
Operator: Anomie ( talk · contribs · SUL · edit count · logs · page moves · block log · rights log · ANI search)
Time filed: 13:35, Thursday, April 29, 2021 ( UTC)
Function overview: Apply pending changes protection to TFAs while they are on the Main Page.
Automatic, Supervised, or Manual: Automatic
Programming language(s): Perl
Source code available: User:AnomieBOT/source/tasks/TFAProtector.pm
Links to relevant discussions (where appropriate): Wikipedia talk:Today's featured article#Pending changes TFA trial, Special:PermanentLink/1017460384#Pending-changes protection of Today's featured article
Edit period(s): Hourly, but typically will only apply protection once per day.
Estimated number of pages affected: 1 per day
Namespace(s): Article
Exclusion compliant (Yes/No): N/A, does not edit
Adminbot (Yes/No): Yes
Function details: The bot will apply pending changes protection to a TFA about an hour before it begins to be featured on the main page, set to expire an hour after the featuring ends. The day's TFA is identified using the date's subtemplate of Template:TFA title.
It will also re-check each hour to ensure that someone has not removed the protection. If an existing PC protection would end before the bot's protection would, the bot will extend it. It will not shorten any existing PC protection that lasts longer than the protection it would apply.
Note this task is itself a trial, per the RFC. The code at present will refuse to run beyond May 31, 2021 at 22:00 UTC (i.e. it will protect TFAs through the end of May, but will stop before it would protect June 1's TFA). After that it will be up to interested people to hold another RFC to determine whether consensus exists to continue the task. If that consensus exists, I'll remove the relevant code to allow the bot to continue running (without a subsequent BRFA).
I ran the task once already with a hack to point it at Wikipedia:Pending changes/Testing/9 instead of the actual TFA (and with the reason hacked too), to validate that the stabilize API call worked as expected. I'd have used a userspace page, but PC protection can't be used in userspace. Anomie ⚔ 13:35, 29 April 2021 (UTC) reply
Trial complete.
Here are all the log entries. Of note:
As noted above, even if this is approved now I won't run the task until a followup RFC determines that the task should proceed. As far as this BRFA goes, I'd personally go ahead and approve it with that understanding since there's nothing left for BAG to do here other than rubber-stamping that RFC. Anomie ⚔ 22:27, 31 May 2021 (UTC) reply