Wikipedia:Bots/Requests for approval/Leaderbot

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.

Leaderbot

New to bots on Wikipedia? Read these primers!

Approval process – How this discussion works
Overview/Policy – What bots are/What they can (or can't) do
Dictionary – Explains bot-related jargon

Operator: Leaderboard (talk · contribs · SUL · edit count · logs · page moves · block log · rights log · ANI search)

Time filed: 12:32, Saturday, August 10, 2024 (UTC)

Function overview: phab:T370842 - I want to see if this is something English Wikipedia wants for their local rights. I could not find evidence of this already being done or discussion about this on any other bot.

Automatic, Supervised, or Manual: Automatic

Programming language(s): Python

Source code available: https://github.com/Leader-board/userrights-reminder-bot, though this is under development

Links to relevant discussions (where appropriate): Wikipedia:Administrators'_noticeboard/Archive364#Bot_to_inform_temp_users_of_expiry ~~I do not believe that this is required, but should it be considered necessary, I can file one explicitly.~~

Edit period(s): Daily.

Estimated number of pages affected: 2-3 per day approximately.

Namespace(s): User talk only.

Exclusion compliant (Yes/No): No, as it is not applicable. However, a mechanism to allow users to exclude the bot from running on their talk page is expected to be provided before the bot is formally run. This is otherwise opt-out.

Function details: As explained above. For users whose temporary rights are expected to expire in a week, the bot will simply remind the user on their talk page that their right will expire within that time. That's it - while I eventually expect this to run on multiple wikis, this request pertains only en.wikipedia. This request will not require the bot flag. Please ping me when needed.

Discussion

{{BotOnHold}} You do not have a working bot, you do not have consensus for this task, and you do not seem to understand that all bots need a bot flag. If you can come around to those three things, then re-open this task and we'll discuss whether it is feasible. Primefac (talk) 13:09, 10 August 2024 (UTC)[reply]

@Primefac:, I was under the impression that the rules said that "Bot accounts will be marked by a bureaucrat as being in the "bot" user group upon BAG request", which implied that it was optional. Did I mis-read the rules? Regarding point 2: should I be doing it at Village Pump (Proposals) - I believed that my bot was not "controversial" enough but no issues taking the consensus route if needed? Regarding point 1: I'm requesting permission in advance, and did not know that was in error. Leaderboard (talk) 15:46, 10 August 2024 (UTC)[reply]

I think it's fine to get some kind of indication a task will be approved before doing the development effort.

I'd suggest asking in some community venue to see if people want this task, though. I'd probably opt for WP:VPP or WP:AN (posting at either and cross-notifying the other) ProcrastinatingReader (talk) 02:36, 15 August 2024 (UTC)[reply]

Thanks, I'll do that. Leaderboard (talk) 14:21, 15 August 2024 (UTC)[reply]

Many of our rights assignments are temporary on purpose and that is communicated during request/granting, so "reminding" someone of this seems like it could be more annoying then anything else. Specifically confirmed and event coordinator are almost always granted for a fixed term. Especially confirmed, as it is often granted for 1-10 days for event attendees. As such, these groups probably shouldn't be "reminded". Reminding bot is fairly useless, and potentially IPBE as well (another group that is often granted for a fixed term). — xaosflux ^Talk 15:42, 15 August 2024 (UTC)[reply]
@Xaosflux: I thought IPBE was something where reminding was useful - what about the temp rights often granted at WP:PERM? Another option if the community prefers it that way is to make this opt-in instead of opt-out for this wiki. Leaderboard (talk) 16:23, 15 August 2024 (UTC)[reply]
I'm not super sure on that one, could be useful. Perhaps an additional "don't notify someone that has been inactive for xxx" (like 3 months maybe)? Most of the other temp grants we do at PERM are "granted for a trial, come back and renew" - so those could be useful. — xaosflux ^Talk 16:25, 15 August 2024 (UTC)[reply]

@Primefac and Xaosflux: the bot is ready for en.wiki testing: meta:Global reminder bot. The consensus seems to be mostly positive (at WP:AN), with one concern about IPBE that I'm not sure how to interpret (this is assuming AN discussions do not need to be closed - I'm not sure). A test edit is testwiki:User_talk:Leaderbot_demo. Leaderboard (talk) 09:14, 22 August 2024 (UTC)[reply]

What is your format for multiple entries in "always_excluded_local" ? (e.g. "x","y" ; "x,y" ; etc) ? Please create a local (or at least a global) userpage for this bot account, where such documentation could be linked. — xaosflux ^Talk 09:45, 22 August 2024 (UTC)[reply]

Are local and global config entries merged, or overwritten? — xaosflux ^Talk 09:46, 22 August 2024 (UTC)[reply]

Hi @Xaosflux:,

the global userpage does link to the Meta-Wiki documentation page? You should be able to see it by forcibly creating a local account for Leaderbot.
It's a JSON array, so currently it has ["confirmed"] in it. To add entries, just update the array, so for example, ["confirmed", "bot"]
"Are local and global config entries merged, or overwritten" - I don't understand what you mean. For exclusion purposes, they are merged. For message purposes, it's local, with global used only if local does not exist.

Leaderboard (talk) 10:09, 22 August 2024 (UTC)[reply]

@Leaderboard ok it seems to be because that account is not present on this project (Special:CentralAuth/Leaderbot) - would you attach it please? — xaosflux ^Talk 12:30, 22 August 2024 (UTC)[reply]

Thanks, so yes if global exclusion is "confirmed" and local is "bot" - then locally the exclusion is to confirmed, bot - correct? (Similarly, local can not un-exclude something in global). — xaosflux ^Talk 12:32, 22 August 2024 (UTC)[reply]

@Xaosflux: Done, and yes to both. Leaderboard (talk) 12:48, 22 August 2024 (UTC)[reply]

@Primefac: just want to check with you on whether I can "re-open" this task by formally disabling the BotOnHold template (you said to do that when all three things have been done, which I think is now the case but could be wrong). Leaderboard (talk) 13:49, 24 August 2024 (UTC)[reply]

If you feel that you have what you need, then by all means go for it. I know it feels like a snarky answer, but it's more because I have not had (or taken) the time to do an evaluation of the situation, so I'll leave that to your discretion. Primefac (talk) 20:07, 25 August 2024 (UTC)[reply]

Please link the AN discussion above under "Links to relevant discussions". – SD0001 (talk) 07:22, 1 September 2024 (UTC)[reply]

@SD0001

Done Leaderboard (talk) 07:25, 1 September 2024 (UTC)[reply]

{{BAG assistance needed}} If this was premature, I apologise. Leaderboard (talk) 05:32, 31 August 2024 (UTC)[reply]

Sounds useful. Editors are often confused why they can no longer patrol pages and such, not realizing their temporary access has expired. I don't think this really requires a community discussion, as long as opt-out options are clearly available. Would suggest not reminding if the original access was very short (< 2 weeks?) as then the user is likely to remember it as Xaosflux mentions.

Approved for trial (2 weeks or 10 edits). Please provide a link to the relevant contributions and/or diffs when the trial is complete. – SD0001 (talk) 12:24, 31 August 2024 (UTC)[reply]

As for the code, I'd suggest using a bot framework like mwclient or pywikibot for simplicity and so that error cases are handled. – SD0001 (talk) 12:25, 31 August 2024 (UTC)[reply]

Trial complete. Special:Contributions/Leaderbot @SD0001: Three things: (i) the bot had to be run a couple of times since it hit ratelimit a few times, and (ii) some accounts for which the bot sent messages didn't contribute at all (but indeed had IPBE) - I don't think there's an issue with that in my opinion, and (iii) all 10 messages it sent were for IPBE, as the 10 edits limit was hit before it could go to the users with other rights. (The reason it made these many edits in one day is because as the bot was never run before, it also captured users whose rights were expiring the next day, for instance) Leaderboard (talk) 13:18, 31 August 2024 (UTC)[reply]

The language of the message could use some work.

Hi, As part of Global reminder bot, this is an automated reminder –> Hi, this is an automated reminder
to let you know that your WP:IPBE right will expire on 2024-09-06 11:56:03, which gave you the right to bypass IP-address blocks –> to let you know that your WP:IPBE right which gave you the ability to bypass IP address blocks will expire on 11:56, 6 September 2024 (UTC) It's good to match the signature timestamp format so that it'll be converted to user's time zone if they have the gadget enabled.
At the end, consider adding To opt out of user right expiry notifications, add yourself to m:Global reminder bot/Exclusion.

– SD0001 (talk) 20:03, 31 August 2024 (UTC)[reply]

@SD0001: First and third one done (feel free to improve the message at metawiki:Global_reminder_bot/enwiki - the bot directly pulls the message from that page). The second one I will need to look further, since this format (i.e, $3 on the above page) is common for all wikis and would rather consider that for the future if possible. P.S: it's likely the "Global reminder bot" subpages on metawiki will be protected soon using an abuse filter - noting if you're concerned about unauthorised modification. Leaderboard (talk) 04:37, 1 September 2024 (UTC)[reply]

$3 can be replaced with a wiki-specific date format. – SD0001 (talk) 07:20, 1 September 2024 (UTC)[reply]

@SD0001 This is something I can look into for the future (and wonder if there's an easy way to do this?), but for now I would prefer retaining the current date/time style if that is something you're OK with. Leaderboard (talk) 07:35, 1 September 2024 (UTC)[reply]

Easy way would be to include the date format accepted by python strftime in the per-wiki configuation, eg. for enwiki it would be %H:%M, %-d %B %Y (UTC). Then while posting, substitute $3 with the formatted timestamp. – SD0001 (talk) 08:01, 1 September 2024 (UTC)[reply]

@SD0001: Got it; can the bot be approved before that? Another reason I'm inclined to delay this one for now is that I'm working on getting the bot approved on other wikis, and want to see if other wikis prefer a different date/time format. This will help when developing (for instance, in case I need to do something similar for another language). Leaderboard (talk) 11:17, 1 September 2024 (UTC)[reply]

{{BAG assistance needed}} Leaderboard (talk) 16:00, 7 September 2024 (UTC)[reply]

Approved for extended trial (1 month). Please provide a link to the relevant contributions and/or diffs when the trial is complete. As the first trial only covered a single user group. Please use localised name of groups (eg. page mover) instead of the technical names (eg. extendedmover). The header ("Notice of expiration of ...") makes it sound like it already expired. "Upcoming expiry of ..." would sound more correct. And make the bot talk page not be a red link. – SD0001 (talk) 10:35, 8 September 2024 (UTC)[reply]

@SD0001, regarding the usage of localised names, is User_talk:CharlieMehta#Upcoming_expiry_of_your_patroller_right OK, or would you prefer using only the localised name where applicable? Just want to check if I need to change something. Leaderboard (talk) 11:47, 8 September 2024 (UTC)[reply]

Trial complete. - see bot contributions. Feel free to tweak the title/text on the meta page.

Notice that the bot now prints the date/time of expiry in text form (i.e, with month names) - this can be configured on meta:Global reminder bot/enwiki. Another behind-the-scene improvement: the bot now supports renamed users (previously if the user was renamed between the first notification and the actual expiry of the right, it would send a duplicate notification - though this hasn't actually happened before I fixed it).
One thing I plan to work on is redirects - currently the bot does not recognise cases where the user has redirected their talk page to something else (either on the same wiki or a cross-wiki redirect). I do not think this is urgent though.

Leaderboard (talk) 18:58, 8 October 2024 (UTC)[reply]

{{BAG assistance needed}} Leaderboard (talk) 16:07, 13 October 2024 (UTC)[reply]

Approved. Primefac (talk) 16:56, 13 October 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.