Wikipedia talk:Bots

Active discussions

Requests for the bot flag should be made on this page. This wiki uses the standard bot policy, and allows global bots and automatic approval of certain types of bots. Other bots should apply below. Global bot flag requests are handled at Meta:Steward requests.

If you are requesting bot status, please use the Current requests section. For other matters dealing with bots, please use the "discussion section".

Current requestsEdit

Put new requests at the top. Look here for a form to use to request bot status.


  • Contributions
  • Operator: Brantmeierz
  • Programming language: Java (using a slightly modified version of
  • Function: Redirect management
  • Description: I've been spending a lot of time manually creating and categorizing redirects: many of which follow rules that could be easily identified and performed automatically. In addition, something that I haven't been adding while manually working on redirects is Template:Rcat shell which helps a lot with the clarity of the pages and grouping those with multiple redirect reasons. My bot would perform these behind-the-scenes tasks only on redirect pages.

--Brantmeierz (talk) 03:03, 22 January 2020 (UTC)

  • You will need to list out exactly what edits the bot will be making. Now I understand the Rcat shell one but you imply there are others. What are they? -DJSasso (talk) 10:43, 22 January 2020 (UTC)
Some I had in mind to apply, and their logic, were:
  • Template:R from other capitalization; guaranteed to identify (if the source and destination page titles were different, but equal when both forced lowercase they must differ in capitalization)
  • Template:R to section; guaranteed to identify (check if destination is linked to a section/contains #)
  • Template:R from specific geographic name; fairly easy to identify (look for redirects where destination page is a location and the page title is {Destination}, {Other identifiers})
  • Template:R from acronym; wouldn't identify all of them, but a conservative method would be finding redirect pages where the destination page consists only of words beginning with each consecutive letter of the source page's name
Others like R from other spelling, plurals, etc. would definitely be possible to identify using a dictionary file or APIs but since that has a much greater ability to produce erroneous results it's not something I would attempt with a bot yet. Brantmeierz (talk) 16:02, 22 January 2020 (UTC)
Personally I don't think redirects should be categorized on simple at all, regardless of whether it's by a bot or a human, just doesn't seem the simple way to me. If it is done though, I guess it won't really matter which route is done. Computer Fizz (talk) 08:47, 23 January 2020 (UTC)
Since it’s mostly behind the scenes, more like maintenance categories and not related to page content, I don’t see why the practices should differ much between enwiki and simple (except for some regrouping/renaming; the categorization system here is a lot less technical than enwiki). For the parts where it does affect readers (such as if they happen to stumble across the redirect pages themselves, which will definitely happen sometimes) it helps with readability and navigation to have what’s going on be explained instead of them only being presented with the technical wiki markup for a redirect. Brantmeierz (talk) 16:14, 23 January 2020 (UTC)
@Computer Fizz: From a management side, ignoring the user perspective, it’s nice to have the pages bound to something, since in a lot of cases the only links to them will be found on the “What links here” section of any given page. Having them categorized with similar pages helps make them more searchable than if they were floating around without any page links, and is especially helpful for restructuring or renaming things since they can be identified as a batch with similar properties. Brantmeierz (talk) 16:18, 23 January 2020 (UTC)
Yeah our category system is intended to be a lot more simple than the one on Having a complex category system can end up being unsimple. I do understand where you are coming from so you aren't out in left field or anything. Personally I don't care one way or the other if we categorize redirects. I just know I am not likely to do it myself because I doubt anyone would ever really look at the categories of redirects. -DJSasso (talk) 16:33, 23 January 2020 (UTC)
  •   Approved for trial (100 edits). Ok I will approve a trial for only the 4 tasks above and Rcat shell. I would like to see 100 edits with some edits of each kind. Should you want to add other tasks in the future you would need to come back here for additional approval. -DJSasso (talk) 16:33, 23 January 2020 (UTC)
Isn't there an abuse filter called "redirect page with extra text"? If we're categorizing them now, should that be deleted? Computer Fizz (talk) 17:07, 23 January 2020 (UTC)
Filter 36, but it can easily be changed to include the bot group as well. rollingbarrels (talk) 17:10, 23 January 2020 (UTC)
We have been categorizing them for a long time. Just no one has wanted to do it to the scale he is suggesting. It isn't new. But yes, I will likely add the bot group. (although probably not needed because the bot would be autoconfirmed) -DJSasso (talk) 17:11, 23 January 2020 (UTC)
Abuse filter 36 was designed to tag edits where an unsuspecting user adds content to a redirect, without realising that it would not be visible. If you were to look at the filter rules you will see that all autoconfirmed users will not trip the filter. And as for non-autoconfirmed users causing a false positive if they attempt to categorise redirects, I think the chance of that happening is very low, and it is far more likely that non-autoconfirmed users are (mistakenly) trying to add content in a redirect page. Chenzw  Talk  13:36, 24 January 2020 (UTC)
Yep that is why I said not needed because it would be autoconfirmed. And you are right very unlikely a non-autoconfirmed user would be categorizing articles legitimately. And it only tags an article, doesn't prevent it anyway. -DJSasso (talk) 13:41, 24 January 2020 (UTC)


  • Contributions
  • Programming language: Pywikibot
  • Function: Simplifying / Automating the DYK panel's on the main page, archiving recent ones, and clearing the replaced ones.
  • Description: This bot would making the updating process of the DYK simpler, by running every week when it needs to be replaced — Preceding unsigned comment added by FNAFPUPPETMASTER (talkcontribs)
Two issues here: 1) have you already written the bot code for this task? 2) there is currently no editor activity on DYK. Until activity picks that up, a bot is effectively useless. Chenzw  Talk  07:17, 27 February 2020 (UTC)
Not only that but the DYK system is automatic on its own already with a queue system. -DJSasso (talk) 11:38, 27 February 2020 (UTC)
Then perhaps just moving this into a user script? rollingbarrels (talk) 15:43, 27 February 2020 (UTC)

Policy DiscussionEdit

Request a new botEdit

Return to the project page "Bots".