Wikipedia:Bots/Requests for approval/Rusabot 2: Difference between revisions
m →Discussion: re |
→Discussion: re |
||
| Line 36: | Line 36: | ||
*:I'd ECP it, but if that's not sufficient I suppose I could full protect it and add people on request from the talk page. Since the scope of potential damage is pretty low (adding a single page to each editor's user space that they wouldn't notice unless they went looking for it) I think that's excessive, though. Theoretically I could add a check for someone adding more than one username at a time or adding usernames other than their own, but that's a lot of extra code for pretty marginal benefit. [[User:Rusalkii|<span style="color:#1C7E85"><b>Rusalkii</b></span>]] ([[User talk:Rusalkii|talk]]) 17:56, 8 September 2026 (UTC) |
*:I'd ECP it, but if that's not sufficient I suppose I could full protect it and add people on request from the talk page. Since the scope of potential damage is pretty low (adding a single page to each editor's user space that they wouldn't notice unless they went looking for it) I think that's excessive, though. Theoretically I could add a check for someone adding more than one username at a time or adding usernames other than their own, but that's a lot of extra code for pretty marginal benefit. [[User:Rusalkii|<span style="color:#1C7E85"><b>Rusalkii</b></span>]] ([[User talk:Rusalkii|talk]]) 17:56, 8 September 2026 (UTC) |
||
*:: Mostly I mention it so it can be taken into account when making the decision. You're right the impact is pretty small, so not worrying about it could be a valid choice. If you decide to worry about it anyway, one strategy might be to have people create a particular .js or .css subpage in their userspace to confirm. [[User:Anomie|Anomie]][[User talk:Anomie|⚔]] 23:43, 8 September 2026 (UTC) |
*:: Mostly I mention it so it can be taken into account when making the decision. You're right the impact is pretty small, so not worrying about it could be a valid choice. If you decide to worry about it anyway, one strategy might be to have people create a particular .js or .css subpage in their userspace to confirm. [[User:Anomie|Anomie]][[User talk:Anomie|⚔]] 23:43, 8 September 2026 (UTC) |
||
*:::I generally don't see any issue with bots editing user space for the purposes of making life easier when the backend software isn't doing the most ideal job, especially if it's opt-in, but there also needs to be a demonstrated need. I'd be fine with a trial (maybe 30 days?) to gauge interest and get feedback from the community. [[User:Primefac|Primefac]] ([[User talk:Primefac|talk]]) 20:40, 13 September 2026 (UTC) |
|||
Revision as of 20:40, 13 September 2026
Operator: Rusalkii (talk · contribs · SUL · edit count · logs · page moves · block log · rights log · ANI search)
Time filed: 09:08, Tuesday, September 8, 2026 (UTC)
Automatic, Supervised, or Manual: automatic
Programming language(s): Python
Source code available: https://github.com/rusamoss/rfd_watch
Function overview: Maintain a manual RfD pseudo-watchlist for users that have opted in, to work around the fact that there's no way to watchlist individual RfD discussions.
Links to relevant discussions (where appropriate): N/A
Edit period(s): Continuous (every 15 minutes)
Estimated number of pages affected: Single userspace page for each user who opts in
Exclusion compliant (Yes/No): No
Already has a bot flag (Yes/No): Yes
Function details: For every user that opts in at User:Rusabot/RfD subscribers, maintain a list at User:Username/RfD subscriptions, which is updated whenever that nomination has any changes. Any RfD nominations from your Twinkle log is added automatically, and you can manually add entries as well.
It's been running at User:Rusalkii/RfD subscriptions without any issues. Not entirely sure I need a BRFA for an opt-in userspace-only bot, but filing just in case; I'll unprotect the subscribers page once the bot is approved for other users. Possibly the subscribers page should be permanently ECPed since it controls a bot and non-EC users are pretty unlikely to need it.
Accompanying userscript User:Rusalkii/subscribeToRfDs.js adds some convenience buttons.
Discussion
Not entirely sure I need a BRFA for an opt-in userspace-only bot
To write anyone else's userspace besides your own and the bot's, you do. WP:BOTUSERSPACE doesn't cover userspace in general, even with opt-in. BTW, I note that an unprotected subscription page may not be completely opt-in, if there's no guard against someone adding other names to the list. Anomie⚔ 11:31, 8 September 2026 (UTC)- I'd ECP it, but if that's not sufficient I suppose I could full protect it and add people on request from the talk page. Since the scope of potential damage is pretty low (adding a single page to each editor's user space that they wouldn't notice unless they went looking for it) I think that's excessive, though. Theoretically I could add a check for someone adding more than one username at a time or adding usernames other than their own, but that's a lot of extra code for pretty marginal benefit. Rusalkii (talk) 17:56, 8 September 2026 (UTC)
- Mostly I mention it so it can be taken into account when making the decision. You're right the impact is pretty small, so not worrying about it could be a valid choice. If you decide to worry about it anyway, one strategy might be to have people create a particular .js or .css subpage in their userspace to confirm. Anomie⚔ 23:43, 8 September 2026 (UTC)
- I generally don't see any issue with bots editing user space for the purposes of making life easier when the backend software isn't doing the most ideal job, especially if it's opt-in, but there also needs to be a demonstrated need. I'd be fine with a trial (maybe 30 days?) to gauge interest and get feedback from the community. Primefac (talk) 20:40, 13 September 2026 (UTC)
- Mostly I mention it so it can be taken into account when making the decision. You're right the impact is pretty small, so not worrying about it could be a valid choice. If you decide to worry about it anyway, one strategy might be to have people create a particular .js or .css subpage in their userspace to confirm. Anomie⚔ 23:43, 8 September 2026 (UTC)
- I'd ECP it, but if that's not sufficient I suppose I could full protect it and add people on request from the talk page. Since the scope of potential damage is pretty low (adding a single page to each editor's user space that they wouldn't notice unless they went looking for it) I think that's excessive, though. Theoretically I could add a check for someone adding more than one username at a time or adding usernames other than their own, but that's a lot of extra code for pretty marginal benefit. Rusalkii (talk) 17:56, 8 September 2026 (UTC)
