Wikipedia:Bots/Requests for approval/TenshiBot

TenshiBot

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

Time filed: 22:26, Sunday, April 20, 2025 (UTC)

Automatic, Supervised, or Manual: automatic

Programming language(s): Pywikibot

Source code available: [1]

Function overview: Clerk RM/TR requests and notify users when their contested request has been removed from the page.

Links to relevant discussions (where appropriate): Wikipedia_talk:Requested_moves/Archive_35#Bot_to_clerk_RM/TR, Wikipedia_talk:Requested_moves/Archive_36#Re_the_clerking_bot_at_RMTR, Wikipedia:Bot requests#Clerk_Requested_Moves/Technical

Edit period(s): Twice per day (12 hour interval)

Estimated number of pages affected: ~5 a day

Exclusion compliant (Yes/No): Yes

Already has a bot flag (Yes/No): No

Function details:

Removes already completed requests from RM/TR.
Removes contested requests that have been inactive for longer than 72 hours, and notifies the requester how they can start a requested move discussion (only if one hasn't been started on the article's talk page).
Moves requests to the Administrator needed section if the request contains create-protected or move-protected pages.

Discussion

Tenshi Hinanawi Thank you for doing this. I have some comments/feedback on the proposed setup:
- For User:TenshiBot/RMTR_contested_notification, is it possible to add a parameter to revision id to point to them what request that was left hanging? i.e. Special:Permalink/1287442441#BOW? There may be someone who have requested multiple moves in batches and it is common to see that some of them gets processed and the others don't for whatever reason.
- For notify_requesters function, maybe improve it to group multiple requests if any. otherwise, the bot may spam one user's talk page in a single go if they had made multiple requests.
- For the frequency of the runs, I suggest a lower frequency, like once or twice a day. RM/TR, despite the backlog, isn't as bad as RFPP/I.

That's all from me for now from me. – robertsky (talk) 01:43, 27 April 2025 (UTC)[reply]

Partly done Requests are now grouped for notifications. Working on if requests can be permalinked in the template or similar. — Tenshi! (Talk page) 14:21, 27 April 2025 (UTC)[reply]

@Tenshi Hinanawi, Thanks! From {{RMassist/core}}, it seems that permalink generation for the specific request is: [[Special:Permalink/{{Wikipedia:Requested moves/Technical requests/Permalink}}#{{#invoke:String|sub|{{#invoke:BaseConvert|16to36|{{#invoke:Hash function|main|adler32|{{#invoke:string|replace|plain=false|{{{1|}}}{{{2|}}}|%W|}}}}}}|-3}}. That should help you with the replicating the permalink(s). – robertsky (talk) 15:56, 27 April 2025 (UTC)[reply]

Is this intended to get their specific request from when they made it or their request before it would be removed by the bot from the page? — Tenshi! (Talk page) 20:55, 27 April 2025 (UTC)[reply]

@Tenshi Hinanawi By before the bot removes the request from the page. In this manner, the requestor can tell if there had been discussions that may have occurred. Wikipedia:Requested moves/Technical requests/Permalink is a bot updated of the latest revision id of the RM/TR page. Of course you may not want to rely on this in case the bot update fails, and instead use the latest revision id of the page from the API. – robertsky (talk) 01:32, 28 April 2025 (UTC)[reply]

Done Added to template, code updated. — Tenshi! (Talk page) 18:24, 28 April 2025 (UTC)[reply]

Thanks~ I have no further inputs here. Let's wait for a BAG member to do their stuff here. :) – robertsky (talk) 00:41, 29 April 2025 (UTC)[reply]