Archives
Up to June 2011 (archive 1) July 2011-February 2012 (archive 2) March 2012-September 2013 (archive 3) October 2013-June 2014 (archive 4)

Yes, I get the Signpost delivered right to my discussion doorstep!

There are some archives of this page. See the orange box at right.

Saw this bug report over the signature button appearing in namespaces that editor's would rather it didn't and figured I should mention the "obvious"

Just add

		'filters': [ 'body.ns-talk, body.ns-4' ],

to the signature button's entry in jquery.wikiEditor.toolbar.config.js and your done. The same approach is used for the references button (see that same .js file if you don't believe me)

If you want to allow the signature button's generation in more namespaces, just add their numeric designation(s) to the filter using body.ns-4 in the above as your example (no comma after the last entry btw).

You can also exclude button generation for certain namespaces this way....

		'filters': [ 'body:not(.ns-2, .ns-8, .ns-828)' ],

Hope that helps -- George Orwell III (talk) 22:54, 27 July 2014 (UTC)[reply]

That implementation method was not something I was aware of, so thanks for enlightening me :) However I don't think it is necessarily appropriate for this situation. It wouldn't be right to hard-code the list of namespaces in this JavaScript code, and it also seems a bit wasteful to be stringing together a 'body.ns-' + namespaceId type thing when we can just delete the entry from the JavaScript object.

The main issue surrounding this bug is that no-one can agree on how we should decide which namespaces get the sig button. I would appreciate it if you could contribute, based on the three options I outlined in comment 19 of the bug. — This, that and the other (talk) 07:31, 28 July 2014 (UTC)[reply]

Same old, same old. No-one agrees because each has their own embedded bias/perspective by now if they've been a regualar for any noteworthy amount of time by now. I dare say even your poo-poo'ing of the existing filter settings has some trace degree of that too.

Look, it seems like all the wiki-projects at least share the same ~17(I forget what the right # is) core namespaces - that's all you folks should be discussing a default setting for. Period.

Half of those are talk-pages so body.ns-talk or some similar solution should allow the button for those talk namespaces. That leaves "you" with what? ~8 core namespaces shared acrosss all the wiki-projects to bicker over? Out of those remaining namespaces, only the Project: ns (ns-4) would have any legit reason to host talk-page like discussions (a la Village Pump for example) where the button is useful.

Get into the namespaces numbered ~100 or higher from one Wiki-domain to the next, and you'll find using content namespaces to include/exclude button generation will not be as neatly uniform as the core namespaces are. This area is where 'ickypedia blinders' cause developers to make changes that typically don't go over well @ any project BUT Wikipedia or Commons (I can almost bet next week's pay-check that whatever solution is applied at the end of the day, it will conflict with the existing ability to use the filter).

My vote is to set a default using whatever manner or method makes the most sense for the core namespaces that all wikis share and leave the far lower trafficked assignable namespaces out of it - let folks deal with it or solve it on their own locally if the presence of the button so annoying to them. Prost. :) -- George Orwell III (talk) 08:52, 28 July 2014 (UTC)[reply]

We want to be able to configure this behind the scenes on a per-wiki basis. For example, Meta uses signatures in the main namespace, while this wiki does not. It's more about how to determine exactly how this configuration interacts with other wiki elements. For instance, does the presence of __NEWSECTIONLINK__ indicate we should allow the signature button on that page? I don't know the answer to that.

I should also stress that this relates to the MediaWiki software in general, which is used by many others besides the WMF (for example, a lot of companies use MediaWiki internally for planning and collaboration between staff). We need a solution that will work out-of-the-box for all wikis, as well as to be configurable by the server administrator as required. — This, that and the other (talk) 09:43, 28 July 2014 (UTC)[reply]

I think you answered your own question - especially if your rationale goes beyond the Wiki foundation projects and into the "commercial" aspects of the software. Again the core namespaces are not likely not be re-tasked into blogs or newsfeeds but additional namespaces might be. If that rationale is true, the logical approach would be set only the .ns-talk namespaces as the extension's default for sig. button generation while leaving deviation or modification of said default a matter left to local administration to wrangle with post-deployment. -- George Orwell III (talk) 23:15, 28 July 2014 (UTC)[reply]

Also, I don't think I'm "poo-poo'ing" the existing settings, insofar as there are none. The status quo is to show the signature button in all namespaces, which seems rather inadequate. — This, that and the other (talk) 09:43, 28 July 2014 (UTC)[reply]

Well that point on 'showing in all namespaces' goes back to the rather bloated default package of defaults loaded with WikiEditor and the hoops one has to jump through just to customize the basics that are sold as "tools" in a tool-bar. For example, I can appreciate the need to cover Asian character sets along with the others but there should be a way for at least the local administration if not User:s themselves to pick and choose individual sets. Sure, one can add characters to existing sets and add entirely new sets but there is no way to prevent sets in the existing defaults from loading every time the tab is selected - well at least I can't find a way other than removing the entire booklet and rebuilding it without the unwanted sets (I think this is due to the setting 'deferLoad': true, in that same .js mentioned above usurping anything I might have set to removeFromToolbar in my local .js file(s)). If you know better, please, I'm I dying to find out how its done.

Anyway, the point I'm trying to make is that its great to incorporate defaults that allow for a positive "out-of-box experience" but they should not be so embedded in the module that customizing/deviating from those defaults necessitates the negation then duplication of the original coding involved. As the move to more mobile platforms plays out and/or the need for screen-space management increases, it seems things like which default loaded buttons (or tabs) you want loaded by default in which namespace scenario(s) is something that should be standardized in one's User: preferences rather than locked into additional scripting and/or patching as those options currently seem to be. -- George Orwell III (talk) 23:15, 28 July 2014 (UTC)[reply]

I loveFtCG, but it would be nice if it could delete templates like {{Category ordered by date|Files licensed by third parties|2013|08|13}}. Thanks! (t) Josve05a (c) 00:09, 1 August 2014 (UTC)[reply]

Hi Josve05a, I'm really sorry it's taken me this long to answer! Do you think FtCG should remove all invocations of the template "Category ordered by date", or only those with "Files licensed by third parties" as the first parameter? — This, that and the other (talk) 02:51, 17 August 2014 (UTC)[reply]

All instances, since Commons don't have (didn't the last time I checked) that template. (t) Josve05a (c) 07:16, 17 August 2014 (UTC)[reply]

Is it possible to make FtCG to add:
[[Category:Files uploaded by Josve05a (cleanup)]] [[Category:Files transferred from en.wikipedia by Josve05a]] ‎ to all files I tranfer? (t) Josve05a (c) 00:11, 5 September 2014 (UTC)[reply]

Ping. (t) Josve05a (c) 15:26, 14 September 2014 (UTC)[reply]

Hi, my home-wiki is Russian.

It is rather often it is needed to move files from Commons to ru-wiki: because a set of files is found not corresponding to the free content criteria yet is useful for many articles under fair use restrictions.

Before writing some bot from a scratch I am wondering if For the Common Good can be a little bit changed (or some settings applied to it as it is) so it could transfer sets of files from Commons to ru.wikipedia.org File: namespace?

The relevant discussion about a bot (in Russian) is currently here.

Best regards, Seva — Preceding unsigned comment added by Neolexx (talk • contribs) 16:49, 4 August 2014 (UTC)[reply]

+1. Please help. Details here: Википедия:Запросы к ботоводам#Выгрузка файлов из Викисклада в Рувики (via google translate) --Fastboy (talk) 17:20, 4 August 2014 (UTC)[reply]

Fastboy Neolexx: My apologies for not replying any sooner. Such a tool would certainly be possible to create. Indeed, in the past, I used a "lightly hacked" version of For the Common Good to transfer files from Wikitravel Shared (a site similar in nature to Wikimedia Commons) to local Wikivoyage editions after the establishment Wikivoyage in late 2012. So it is certainly possible. I will be happy to look at this in the coming week. — This, that and the other (talk) 12:25, 7 August 2014 (UTC)[reply]

That would be terrific! By all other means the app seems fit perfectly to our needs uncluding the ability of an editable "template dictionary". I have translated your answer at our forum - as there is no rush then to do and to debug something from a scratch, it is better to wait then. --NeoLexx (talk) 17:25, 7 August 2014 (UTC)[reply]

Hi Fastboy and Neolexx, I have uploaded version 1.0.5.11 of For the Common Good to http://atlight.github.io. In conjunction with the instructions at User:This, that and the other/For the Common Good/Reverse transfers, it should now be possible to run FtCG in reverse! If you find any problems or would like additional features to be added, please let me know. Thanks for your interest in FtCG. — This, that and the other (talk) 02:45, 17 August 2014 (UTC)[reply]

• Thank you! I will start learning and testing immediately. --NeoLexx (talk) 07:41, 17 August 2014 (UTC)[reply]
• Sorry for silly question, but where does the installation go by default? I installed it on Windows 8, closed and now no signs at Program files. --NeoLexx (talk) 08:18, 17 August 2014 (UTC)[reply]
  • Oh, OK, sorry. It is not installed, it is a single exe. --NeoLexx (talk) 08:20, 17 August 2014 (UTC)[reply]
• To be clear, what is the license you want to be mentioned for this program? I didn't find it at the download page. --NeoLexx (talk) 08:23, 17 August 2014 (UTC)[reply]
  • The current version is released into the public domain. Even so, I appreciate it if you provide attribution if you choose to make copies of the program. I will probably release the next version under a license such as MIT, but for the moment, it is in the public domain. — This, that and the other (talk) 09:25, 17 August 2014 (UTC)[reply]
• Hello. I tried reverse and it worked. I spent decent time to make a config but then I transferred twenty images very quickly. But I found some obstacles that slowed me down:

1. FtCG doesn't memorize chexbox settings (I had to ckeck "ignore warnings" every other image)
2. FtCG doesn't have automating to bypass a ban to create image with a name that already exists in commons. Of cauze admins doesn't have this problem. But I had to rename each image manually. It would be nice if you could set some prefix/postfix to new file name once and FtCG would apply it for each next image.
3. One more feature I'd like to see: mandatory replacements or replacement groups (one of). If such "mandatory" replacement pattern not found, FtCG must make a very nicely visible error warning.

Could you make some of such features? Or, could I contribute to code? ~Nirvanchik~ ^⊤άλҟ 07:34, 21 October 2014 (UTC)[reply]

And, by the way, in reverse order you can configure only "source" wiki which is commons and which is English, and you can't configure "destination" wiki, which is not English, so I had to use very coplicated replacement pattarn to change image description template by Russian version of these template, and to move all variables correctly. It would be nice if reverse wiki could be supported in more natural way. ~Nirvanchik~ ^⊤άλҟ 07:39, 21 October 2014 (UTC)[reply]

Btw thanks for that previous support! It really helped! ~Nirvanchik~ ^⊤άλҟ 07:43, 21 October 2014 (UTC)[reply]

Assuming you are the "tto" on Freenode who asked "just wondering if you could clarify for me why you added the 512-character limit on special page titles in r18220?" I didn't add a 512-character limit, I raised the limit from 255 to 512 bytes on the basis that 255 bytes was not sufficient. 512 bytes was sufficient for use cases then in existence. -- Tim Starling (talk) 09:28, 7 August 2014 (UTC)[reply]

That was me :) Thanks for the clarification. So it was mostly an arbitrary choice, then. That was what I was interested in knowing. — This, that and the other (talk) 09:59, 7 August 2014 (UTC)[reply]

Did you notice that this redirect format doesn't work? I'm not sure if it is the page or Mediawiki which should be fixed. --Stefan2 (talk) 17:37, 17 August 2014 (UTC)[reply]

It's the long standing bug 6151. I've been poking around at the MediaWiki title code recently, so I might try to fix it... although the fact that it hasn't been fixed in 8 years isn't promising... — This, that and the other (talk) 23:06, 17 August 2014 (UTC)[reply]

Your recent article submission to Articles for Creation has been reviewed! Unfortunately, it has not been accepted at this time. Please check the submission for any additional comments left by the reviewer. You are encouraged to edit the submission to address the issues raised and resubmit when they have been resolved.

• If you would like to continue working on the submission, go to Draft:Beth Sotelo and click on the "Edit" tab at the top of the window.
• If you need any assistance, you can ask for help at the or on the .
• You can also get real-time chat help from experienced editors.

Coin945 (talk) 07:33, 5 September 2014 (UTC)[reply]

Your recent article submission to Articles for Creation has been reviewed! Unfortunately, it has not been accepted at this time. Please check the submission for any additional comments left by the reviewer. You are encouraged to edit the submission to address the issues raised and resubmit when they have been resolved.

• If you would like to continue working on the submission, go to Draft:Beth Sotelo and click on the "Edit" tab at the top of the window.
• If you need any assistance, you can ask for help at the or on the .
• You can also get real-time chat help from experienced editors.

Coin945 (talk) 11:20, 10 September 2014 (UTC)[reply]

Hello TTATO,
I don't mean to be pushy, but you said on Wikipedia talk:Twinkle that you would do preliminary work on Twinkle tomorrow (which is probably yesterday now), however Twinkle is still tagging pages with {{db-nocontent}}. Please tell me why this is the case as my new templates are now finished and are ready to be moved. Thanks, Passengerpigeon (talk) 14:54, 15 September 2014 (UTC)[reply]

Hi Passengerpigeon, this is a bit of a "chicken or egg" problem. But so long as the new A3 templates are set up as redirects to db-nocontent for the time being, there shouldn't be an issue. I can't promise when the change to Twinkle will be deployed, but hopefully it will be available on-wiki not long after I finish writing the code tonight. — This, that and the other (talk) 23:15, 15 September 2014 (UTC)[reply]

{{db-a3}} will not change in the move, and {{db-a3-notice}} currently redirects to {{db-nocontent-notice}} but will be overwritten by {{db-nocontent-notice}} once the move takes place, thus everything should work the same way it does currently. Passengerpigeon (talk) 23:32, 15 September 2014 (UTC)[reply]

Hello This, that and the other. This message is part of a mass mailing to people who appear active in reviewing articles for creation submissions. First of all, thank you for taking part in this important work! I'm sorry this message is a form letter – it really was the only way I could think of to covey the issue economically. Of course, this also means that I have not looked to see whether the matter is applicable to you in particular.

The issue is in rather large numbers of copyright violations ("copyvios") making their way through AfC reviews without being detected (even when easy to check, and even when hallmarks of copyvios in the text that should have invited a check, were glaring). A second issue is the correct method of dealing with them when discovered.

If you don't do so already, I'd like to ask for your to help with this problem by taking on the practice of performing a copyvio check as the first step in any AfC review. The most basic method is to simply copy a unique but small portion of text from the draft body and run it through a search engine in quotation marks. Trying this from two different paragraphs is recommended. (If you have any question about whether the text was copied from the draft, rather than the other way around (a "backwards copyvio"), the Wayback Machine is very useful for sussing that out.)

If you do find a copyright violation, please do not decline the draft on that basis. Copyright violations need to be dealt with immediately as they may harm those whose content is being used and expose Wikipedia to potential legal liability. If the draft is substantially a copyvio, and there's no non-infringing version to revert to, please mark the page for speedy deletion right away using {{db-g12|url=URL of source}}. If there is an assertion of permission, please replace the draft article's content with {{subst:copyvio|url=URL of source}}.

Some of the more obvious indicia of a copyvio are use of the first person ("we/our/us..."), phrases like "this site", or apparent artifacts of content written for somewhere else ("top", "go to top", "next page", "click here", use of smartquotes, etc.); inappropriate tone of voice, such as an overly informal tone or a very slanted marketing voice with weasel words; including intellectual property symbols (™,®); and blocks of text being added all at once in a finished form with no misspellings or other errors.

I hope this message finds you well and thanks again you for your efforts in this area. Best regards--Fuhghettaboutit (talk) 02:20, 18 November 2014 (UTC).[reply]

       Sent via--MediaWiki message delivery (talk) 02:20, 18 November 2014 (UTC)[reply]

Good day.

My name is Sergey Semenov, I'm the administrator Russian Wikipedia. I am writing to you about the reverse transfer images from the Commons in the Russian Wikipedia using a program For the Common Good. Unfortunately, this program is quite difficult to master, and will move quite a lot.

I have uploaded to Commons several thousand images of tombstones set in the cemeteries of Russia. Unfortunately, in our country there is complete freedom of panorama, so these files can at any time be removed. I decided to move them to the Russian Wikipedia template FoP-Russia. In connection with this appeal to you to write the configuration files for the particular transport mechanism to simplify the programming work far from the participants. In today's conditions, the use of mass transfer of files can lead to disastrous results.

P. S. I'm sorry for the mistakes I badly speak English and translate through Google translator. --SerSem (talk) 12:55, 1 December 2014 (UTC)[reply]

Hi Sergey, thanks for your message, and don't worry about your English, I understand it well! I understand that reverse transfers with FtCG aren't as easy as they perhaps should be. I'll have a moment later today to see if I can prepare you a configuration file that will do what you ask. Thanks, — This, that and the other (talk) 03:40, 2 December 2014 (UTC)[reply]

Thank you very much. I'll wait. --SerSem (talk) 12:51, 2 December 2014 (UTC)[reply]

I made this configuration file for For the Common Good: http://atlight.github.io/ftcg/ForTheCommonGood_SerSem.cfg You should download it, rename it to ForTheCommonGood.cfg, and move it to the same location as ForTheCommonGood.exe.

Be aware of a couple of things:

1. You must turn off the "Tag file with {{now commons}}" check box above the "Transfer" button.
2. If you want to go through each of your uploads, you can download this text file: http://atlight.github.io/ftcg/SerSem_files.txt and click the "Other source" option to load this text file into FtCG.
3. There is no template on ruwiki for CC-BY-SA version 4.0 (see c:template:cc-by-sa-4.0). You will need to create this template on ruwiki before transferring.

I would say that, since you have such a huge number of files, it might be better to ask for a bot to perform the transfers. I think you will find FtCG too slow for this work. But if you wish to give it a go, I hope it helps you. — This, that and the other (talk) 01:13, 3 December 2014 (UTC)[reply]

Thank you very much for your help, I was able to master the program and begin to transfer files with its help. All I do not need to unload, I have old photos uploaded to Commons. With the help of your program I have unloaded in Russian Wikipedia about 700 photos. This is a very important and necessary option in the program. --SerSem (talk) 18:01, 4 December 2014 (UTC)[reply]

• Good day. I tried to upload a list of files at once from the category "Literatorskie mostki", but I did not succeed. If I use the text in this form, as provided by you in the file, the program writes the message: "An API error occured. Bad title" File: "". If I add the "File:" at the beginning of each line, the program writes the message: "An API error occured. Bad title:" File: <>. JPG ". What could be wrong? --SerSem (talk) 14:39, 9 December 2014 (UTC)[reply]
  • I would suggest that you check the encoding of the text file. For the Common Good expects the file to be stored in the UTF-8 encoding. Alternatively, you could upload the file to the Internet so I could look at it and check it for any problems. — This, that and the other (talk) 00:17, 10 December 2014 (UTC)[reply]

	The Technical Barnstar
	For assistance in establishing unloading unfree files in the Russian Wikipedia Commons. The administrator Russian Wikipedia SerSem (talk) 18:03, 4 December 2014 (UTC)[reply]

Hi Purodha, I was triaging some old Toolserver migration bugs, and noticed that there is a task phab:T63028 relating to one of your tools. Do you intend to migrate this tool to Tool Labs? — This, that and the other (talk) 00:16, 1 December 2014 (UTC)[reply]

Although I do not unterstand the phab:T63028 web page, I understand that someone ist asking whether or not I plan to migrate former toolserver tools to tools labs. I do. I only do not have plans as to when I have time to do it. --Purodha Blissenbach (talk) 19:39, 8 December 2014 (UTC)[reply]

Bugzilla seems not wo work any more. It redirects to something else. My account to bugzilla was lost in the process. So, for the time being, I am out of this business. --Purodha Blissenbach (talk) 09:48, 9 December 2014 (UTC)[reply]

@Purodha: Bugzilla was migrated to the new Phabricator issue tracking system a few weeks ago. You can create a Phabricator account that is attached to your Wikimedia SUL account, if you want to comment on bugs. See mw:Phabricator/Help#Creating_your_account for some info.

In any case I'll update the Phabricator task to say that you haven't forgotten about it. Thanks for the reply! — This, that and the other (talk) 09:56, 9 December 2014 (UTC)[reply]

Thank you. I knew about the migration, and I was on the Phabricator page that should allow me to connect to my old bugzilla account a few day ago. That is why I wrote that my access was lost. Maybe, I just have to wait for it to be migrated, I did not really dive into the details. -- Purodha Blissenbach (talk) 10:44, 9 December 2014 (UTC)[reply]

You are invited to join the discussion at Wikipedia:Village pump (technical)/Archive 133#Custom notices on user .js and .css pages. Thanks. — {{U|Technical 13}} ^{(e • t • c)} 15:04, 6 January 2015 (UTC)[reply]

TTO, Template:Infobox academic division has been re-nominated for deletion/merger, following a DRV. You participated in the previous TfD discussion, and I thought you would appreciate the opportunity to comment on the newly re-opened/re-listed discussion at Wikipedia:Templates for discussion/Log/2015 January 22#Template:Infobox academic division. Dirtlawyer1 (talk) 07:26, 22 January 2015 (UTC)[reply]

Now re-re-relisted for more betterness (under the original link), containing the original discussion, but not any comments made in the re-listing. Sorry for the mess. Martijn Hoekstra (talk) 15:13, 22 January 2015 (UTC)[reply]

An RfC has been opened at RfC to physically restrict access to the Helper Script. You are invited to comment. --Kudpung กุดผึ้ง (talk) 16:28, 1 February 2015 (UTC)[reply]

Hi! In attempt to load the file from Ruvika jumps out the message: "The Internet inquiry isn't executed. The inquiry was interrupted: The inquiry is cancelled." Photo: http://radikall.com/images/2015/02/13/ecRa7.jpg --Dogad75 (talk) 10:43, 13 February 2015 (UTC)[reply]

I am a technician from TRwiki. I wanna activate Twinkle. I created following pages(from ENwiki) but "TW tab" didnot appeared.

• tr:MediaWiki:Gadget-Twinkle.js
• tr:MediaWiki:Gadget-morebits.js
• tr:MediaWiki:Gadget-morebits.css
• tr:Vikipedi:Twinkle/Preferences
• tr:MediaWiki:Gadget-twinklediff.js
• tr:MediaWiki:Gadget-twinklefluff.js
• tr:MediaWiki:Gadget-twinklespeedy.js
• tr:MediaWiki:Gadget-twinkleconfig.js

And I made necessary changes in Gadgets tab. Wikipedia:Twinkle/Localisation pages is outdated. Is there a new instruction page? What I am missing? --Mavrikant (talk) 01:27, 22 February 2015 (UTC)[reply]

@Mavrikant: Try altering the Gadgets-definition line to the following:

Twinkle[ResourceLoader|dependencies=mediawiki.user,mediawiki.util,jquery.ui.dialog,jquery.tipsy|rights=autoconfirmed]|morebits.js|morebits.css|Twinkle.js|twinklespeedy.js|twinklediff.js|twinkleconfig.js|twinklefluff.js

— This, that and the other (talk) 06:28, 22 February 2015 (UTC)[reply]

Nope :( I even tryed before enwiki's Gadgets-definition: Twinkle[ResourceLoader|dependencies=mediawiki.user,mediawiki.util,jquery.ui.dialog,jquery.tipsy,moment|rights=autoconfirmed]|morebits.js|morebits.css|Twinkle.js|twinkleprod.js|twinkleimage.js|twinklebatchundelete.js|twinklewarn.js|twinklespeedy.js|friendlyshared.js|twinklediff.js|twinkleunlink.js|twinkledelimages.js|friendlytag.js|twinkledeprod.js|friendlywelcome.js|twinklexfd.js|twinklebatchdelete.js|twinklebatchprotect.js|twinkleconfig.js|twinklefluff.js|twinkleprotect.js|twinklearv.js|friendlytalkback.js I also tried MediaWiki:Gadget-Twinkle.js of Simplewiki. I haven't seen TW tab near search bar yet. There was old version (2009) of Twinkle stored subpages of User:Vito Genovese/Twinkle, I suspicious that old files sabotages new Twinkle but I cleaned main pages of old Twinkle. Do you need technician rights to look what is wrong? --Mavrikant (talk) 13:33, 22 February 2015 (UTC)[reply]

It is working. I followed new version of Wikipedia:Twinkle/Localisation page. Thank you Siddhartha Ghai and User:This, that and the other --Mavrikant (talk) 14:33, 22 February 2015 (UTC)[reply]

Hello, This, that and the other. Please check your email; you've got mail!
It may take a few minutes from the time the email is sent for it to show up in your inbox. You can at any time by removing the {{You've got mail}} or {{ygm}} template.

— MusikAnimal ^talk 03:10, 26 February 2015 (UTC)[reply]

Did you get my email? I'm eager to move forward with the block module but am having trouble with testing. Should I use the fragmented modules on testwiki (as opposed to one big twinkle.js)? How can I get the perl script to upload there instead of enwiki? I can't get the concatenated twinkle.js to work in my userspace since it requires morebits. Morebits doesn't appear to be a module that I can use with mw.loader.load and mw.loader.using, and even trying putting the Twinkle init stuff in a callback of $.getScript things still don't load in the right order. I feel like there must be an easier way. Thanks — MusikAnimal ^talk 23:45, 28 February 2015 (UTC)[reply]

Yeah, I often have trouble getting Twinkle to show up in the UI on testwiki. Normally I will just open my browser's F12 tools and directly call the callback, e.g. Twinkle.protect.callback(). — This, that and the other (talk) 01:34, 1 March 2015 (UTC)[reply]

Beautiful :) Not sure why I didn't think of that! Many thanks — MusikAnimal ^talk 02:52, 1 March 2015 (UTC)[reply]

I take it you wish not to communicate through email? I understand if you do not, there's just some matters I'd rather discuss in private. Anyway, I've been working hard and have the interface for the blocking module more or less done. I thought I'd run this by you before I move on to the actual blocking functionality, just in case something stands out that I'm doing wrong. Pull request is here, feel free to comment. Thanks! — MusikAnimal ^talk 03:13, 2 March 2015 (UTC)[reply]

Hello, This, that and the other,

The Editing team is asking for your help with VisualEditor. I am contacting you because you posted to a feedback page for VisualEditor. Please tell them what they need to change to make VisualEditor work well for you. The team has a list of top-priority problems, but they also want to hear about small problems. These problems may make editing less fun, take too much of your time, or be as annoying as a paper cut. The Editing team wants to hear about and try to fix these small things, too. 

You can share your thoughts by clicking this link. You may respond to this quick, simple, anonymous survey in your own language. If you take the survey, then you agree your responses may be used in accordance with these terms. This survey is powered by Qualtrics and their use of your information is governed by their privacy policy.

More information (including a translateable list of the questions) is posted on wiki at mw:VisualEditor/Survey 2015. If you have questions, or prefer to respond on-wiki, then please leave a message on the survey's talk page.

Unsubscribe from this list • Sign up for VisualEditor's multilingual newsletter • Translate the user guide

Thank you, Whatamidoing (WMF) (talk) 15:56, 26 March 2015 (UTC)[reply]

Hello, This, that and the other. Please check your email; you've got mail!
Message added 02:00, 8 April 2015 (UTC). It may take a few minutes from the time the email is sent for it to show up in your inbox. You can at any time by removing the {{You've got mail}} or {{ygm}} template.

— MusikAnimal ^talk 02:00, 8 April 2015 (UTC)[reply]

Wikipedia:Lua/Modules, a page you substantially contributed to, has been nominated for deletion. Your opinions on the matter are welcome; please participate in the discussion by adding your comments at Wikipedia:Miscellany for deletion/Wikipedia:Lua/Modules and please be sure to sign your comments with four tildes (~~~~). You are free to edit the content of Wikipedia:Lua/Modules during the discussion but should not remove the miscellany for deletion template from the top of the page; such a removal will not end the deletion discussion. Thank you. Steel1943 (talk) 20:29, 20 April 2015 (UTC)[reply]

Hi,

This is a notification to let you know that there is a requested move discussion ongoing at Talk:Hillary_Rodham_Clinton/April_2015_move_request#Requested_move. You are receiving this notification because you have previously participated in some capacity in naming discussions related to the article in question.

Thanks. And have a nice day. NickCT (talk) 18:55, 26 April 2015 (UTC)[reply]

Hi, You participated in the previous Persondata RfC. I just wanted to notify you that a new RfC regarding the methodical removal of Persondata is taking place at Wikipedia:Village pump (proposals). Thanks, —Msmarmalade (talk) 08:15, 6 May 2015 (UTC)[reply]

Some opposers of this move have now contended that there is a "Critical fault in proposal evidence", which brings the opinions expressed into question. Please indicate if this assertion in any way affects your position with respect to the proposed move. Cheers! bd2412 T 04:36, 8 May 2015 (UTC)[reply]

Hello, This, that and the other. You have new messages at Wikipedia:Requests for undeletion#User talk:User.
You can remove this notice at any time by removing the {{Talkback}} or {{Tb}} template.

I thought I'd post this here as well since i assume you were asking about this in order to find Twinkle defects. Steel1943 (talk) 14:05, 30 May 2015 (UTC)[reply]

Hello, This, that and the other. You have new messages at Eman235's talk page.
You can remove this notice at any time by removing the {{Talkback}} or {{Tb}} template.

Hello, This, that and the other. Please check your email; you've got mail!
It may take a few minutes from the time the email is sent for it to show up in your inbox. You can at any time by removing the {{You've got mail}} or {{ygm}} template.

Hi. You are invited to comment at RfC for BARC - a community desysoping process. Kudpung กุดผึ้ง (talk) 06:58, 24 July 2015 (UTC)[reply]

Hi there TTO (I hope that abbreviation is ok, I'm very lazy),

I'm just writing to say I've been meaning to reply to your April 2014 heads-up on my talk page regarding the above. Unfortunately I was probably either taking a break from the insanity that is Wikipedia or else just busy with other things when you posted. What a shame that was removed (was it because TSL doesn't meet USA-dominated notability standards or something like that?). Very annoying.

Kind regards,

--TyrS 07:07, 4 August 2015 (UTC)[reply]

Hi TyrS! Wow, that was a long time ago. I had forgotten about it. If you head over to the Wikiquote link, you will see the page was deleted because it had "no sourced quotes", so I suspect it was not a matter of notability - rather, one of sourcing. If you want to further work on the page, I imagine Wikiquote has a process for requesting undeletion or deletion review, in the same way as we have our processes here. — This, that and the other (talk) 07:10, 4 August 2015 (UTC)[reply]

Hi, as a user in the edit filter manager user group we wanted to let you know about the new wikipedia-en-editfilters mailing list. As part of our recent efforts to improve the use of edit filters on the English Wikipedia it has been established as a venue for internal discussion by edit filter managers regarding private filters (those only viewable by administrators and edit filter managers) and also as a means by which non-admins can ask questions about hidden filters that wouldn't be appropriate to discuss on-wiki. As an edit filter manager we encourage you to subscribe; the more users we have in the mailing list the more useful it will be to the community. If you subscribe we will send a short email to you through Wikipedia to confirm your subscription, but let us know if you'd prefer another method of verification. I'd also like to take the opportunity to invite you to contribute to the proposed guideline for edit filter use at WP:Edit filter/Draft and the associated talk page. Thank you! Sam Walton (talk) and MusikAnimal ^talk 18:22, 9 September 2015 (UTC)[reply]

please delete the user page for master vijay singh

vijay15:05, 29 September 2015 (UTC)Dispuralive (talk)

Thank you for working on "Allow minor edits to be filtered out of Special:Contributions"! I'm looking forward to it going live. ~ Jeff Q (talk) 08:58, 9 October 2015 (UTC)[reply]

Thanks... but I should point out that the code hasn't been reviewed yet. Unfortunately, changes like this normally take at least a month to be approved, quite often longer. — This, that and the other (talk) 10:26, 9 October 2015 (UTC)[reply]

May I ask what purpose this page serves? —Skyllfully ^(talk | _contribs) 02:30, 28 October 2015 (UTC)[reply]

@Skyllfully: I was probably trying to debug some problem with the MediaWiki software or something like that. Is the page showing up in some database report or backlog? — This, that and the other (talk) 02:33, 28 October 2015 (UTC)[reply]

Nope, I found it in Main Page's WhatLinksHere maintenance report. —Skyllfully ^(talk | _contribs) 02:35, 28 October 2015 (UTC)[reply]

Hi,
You appear to be eligible to vote in the current Arbitration Committee election. The Arbitration Committee is the panel of editors responsible for conducting the Wikipedia arbitration process. It has the authority to enact binding solutions for disputes between editors, primarily related to serious behavioural issues that the community has been unable to resolve. This includes the ability to impose site bans, topic bans, editing restrictions, and other measures needed to maintain our editing environment. The arbitration policy describes the Committee's roles and responsibilities in greater detail. If you wish to participate, you are welcome to review the candidates' statements and submit your choices on the voting page. For the Election committee, MediaWiki message delivery (talk) 16:41, 23 November 2015 (UTC)[reply]

Hey, after a (brief) discussion at WT:BASEBALL, I'd like to nominate all the templates at Category:Minor league baseball affiliates navigational boxes for deletion, as they are redundant to the main Major League Baseball teams' navboxes (which already include links to all of an MLB team's MiLB affiliates, with a more correct breakdown of classifications). As I've never done a mass XFD nomination before, and I really don't relish dong it all manually, I'd appreciate a pass through with the bot for tagging and some advice on the setting up of the appropriate discussion. If you can, ping me to let me know. Thanks. oknazevad (talk) 03:18, 1 December 2015 (UTC)[reply]

Hi. I'll get TTObot to perform the tagging once the TFD nomination is set up. See Wikipedia:Templates_for_discussion/Log/2011_September_11#BTCC.2FPTR_season_templates for an example of how to format a multiple template discussion: simply give it a descriptive heading, and write out one :{{Tfd links|...}} line for each template, like this:

:{{Tfd links|MLB Team}}
:{{Tfd links|MLB Blue Jays franchise}}
:{{Tfd links|MLB Braves franchise}}
:{{Tfd links|MLB Brewers franchise}}
:{{Tfd links|MLB Cardinals franchise}}
:{{Tfd links|MLB Chicago Cubs franchise}}
:{{Tfd links|MLB Indians franchise}}
:{{Tfd links|MLB Nationals franchise}}
:{{Tfd links|MLB Orioles franchise}}
:{{Tfd links|MLB Phillies franchise}}
:{{Tfd links|MLB Pirates franchise}}
:{{Tfd links|MLB Rays franchise}}
:{{Tfd links|MLB Reds franchise}}
:{{Tfd links|MLB Royals franchise}}
:{{Tfd links|MLB Team Arizona Diamondbacks}}
:{{Tfd links|MLB Team Boston Red Sox}}
:{{Tfd links|MLB Team Colorado Rockies}}
:{{Tfd links|MLB Team Houston Astros}}
:{{Tfd links|MLB Team Los Angeles Angels}}
:{{Tfd links|MLB Team Los Angeles Dodgers}}
:{{Tfd links|MLB Team Miami Marlins}}
:{{Tfd links|MLB Team Minnesota Twins}}
:{{Tfd links|MLB Team New York Mets}}
:{{Tfd links|MLB Team New York Yankees}}
:{{Tfd links|MLB Team Oakland Athletics}}
:{{Tfd links|MLB Team San Diego Padres}}
:{{Tfd links|MLB Team San Francisco Giants}}
:{{Tfd links|MLB Team Seattle Mariners}}
:{{Tfd links|MLB Team Texas Rangers}}
:{{Tfd links|MLB Tigers franchise}}
:{{Tfd links|MLB White Sox franchise}}

Let me know once the TFD nomination has been started. Thanks, — This, that and the other (talk) 03:27, 1 December 2015 (UTC)[reply]

I made the nominations. It's at Wikipedia:Templates for discussion/Log/2015 December 3#Minor league affiliates navboxes. oknazevad (talk) 20:48, 3 December 2015 (UTC)[reply]

Done. You may like to notify the following users, who created the templates:

• Gateman1997
• Vikreykja
• SportsMaster
• Dale Arnett
• Enkrates
• JB82
• Evill72
• Tommie91
• NClark128

— This, that and the other (talk) 22:50, 3 December 2015 (UTC)[reply]

In regards to this edit, I feel that the intended word was sysadmins, not admins. It seems like the gist of that section is that there is nothing that an editor can do (admin or otherwise, with the occasional but negligible odd occurrence where an admin really screws up) that can break Wikipedia. In order to truly cause permanent damage, you'd need to be a sysadmin — ie. with access to the actual backend/databases/servers/whathaveyou.  DiscantX 13:42, 20 December 2015 (UTC)[reply]

The reason I removed "sys" is because the text of the section seemed to be talking about admins (as in local users with sysop rights). The first sentence is "In a few cases, there are things sysops can do that will slow down or crash the site". It's clearly talking about sysops on the wiki, not system administrators in the back rooms; it even links to WP:Administrators. Then: "If you get chastised for trying to delete Wikipedia:Sandbox and crashing the site, don't try to delete the same page again". Again talking about sysops. I don't think I agree with the message of the section, but that is beside the point; I think my edit was correct. — This, that and the other (talk) 13:46, 20 December 2015 (UTC)[reply]

I don't particularly agree with the tone of the message but the two lines "although there are a few things admins can do maliciously which are very difficult to clean up, it shouldn't ever be possible to do something which will result in permanent data loss or unfixable breakage" and "If you're unsure about something, you can ask a sysadmin on IRC if it makes you feel better, but generally it's not necessary," plus that the preceding sections reference sysadmins rather than admins seems to suggest that the message of the article in whole is not to worry about edits, because non-employees can't break the site in an irreversible fashion — having the section title say admins can break the site and then go on to say that they can't do any serious damage so "don't be afraid to do similar things... This damages Wikipedia far more than a minor temporary slowdown" seems contradictory.

The whole section is a bit vague, but regardless of what the original author intended to say, I think it is true that only a sysadmin could truly break the site, not an admin (you may be a bit more familiar with the backend, but I imagine that even if every admin were to start acting maliciously it could be reversed by a sysadmin by a manual change outside of the normal tools).  DiscantX 14:13, 20 December 2015 (UTC)[reply]

This, that and the other, hope your holidays are happy, and a happy new year! Steel1943 (talk) 17:49, 23 December 2015 (UTC)[reply]

Hello, This, that and the other. You have new messages at Wikipedia:Village_pump_(technical)#Question_about_DIFF_pages.
You can remove this notice at any time by removing the {{Talkback}} or {{Tb}} template.

Hi. After discussions at Wikipedia talk:WikiProject Tennis#Tn template and a "successful" TfD for Wikipedia:Templates for discussion/Log/2016 February 22#Template:Tn Yuki Bhambri, where decision was taken that these articles are not needed, I want to nominate all templates in Category:Tennis name templates for deletion. Is this something you and your bot, User:TTObot, can help with? The templates where only used on a handful articles and I removed them so they are not currently used anywhere and I follow all related pages at my sandbox and watchlist. I would not ask if I would not think a nomination would be successful. Qed237 (talk) 21:32, 3 March 2016 (UTC)[reply]

@Qed237: Thanks. If you start the TFD discussion, then I can provide a link to that discussion from the edit summary. Otherwise I will just provide a generic deletion summary, like "Nominated for deletion". — This, that and the other (talk) 23:09, 3 March 2016 (UTC)[reply]

@This, that and the other: Discussion opened at Wikipedia:Templates for discussion/Log/2016 March 4#Tn templates. Thank you. Qed237 (talk) 00:26, 4 March 2016 (UTC)[reply]

@Qed237: Done (I had to do it in 2 passes because some of the accents in the names of the players played havoc with my script). — This, that and the other (talk) 08:19, 4 March 2016 (UTC)[reply]

Okay. Thank you very much. Qed237 (talk) 10:00, 4 March 2016 (UTC)[reply]

Thank you for answering my question on Twinkle. That helped and I have been thinking about reporting it. This is not for a second opinion on content or to have the content in the article.This is because I think Twinkle was misused with false summary edits. I just want an second opinion by someone that knows Twinkle and Wikipedia policies better. Just too much to read and take in at one time. The situation is solved but I still question some things. In short what happen, I edited some nonconstructive edits that was half accurate (unknown to me they were in the wrong place) and my edits were done in verified accuracy when I corrected them. Instead of looking at the original edit it was reverted back to them twice by different editors, however, in both summaries did not fit my edits, twinkle was used both times. In the first one the summary had nothing to do with my edits. The second was a little better but still did not match the situation. This whole thing could had been avoided if the original edits were read than being revert back to them or changed when they were made. Also, maybe realize I was correcting what was there and then explain what the original edits should not been there and not made my edits to be the ones in the wrong place like nothing was there before. So, is reverting my good-faith verified accuracy edits back to nonconstructive edits in the wrong place with summaries that did not match my edits and using twinkle abuse? I have felt like my edits were being called vandalism because Twinkle is used for vandalism and nonconstructive. And to me, my edits were to fix nonconstructive edits. Also, When the first editor that reverted my edits, I had wrote on their talk page. no answer. The second editor that reverted my edits, we had a confusing conversation until I understand the original edits I corrected were in the wrong place. That editor did remove most and corrected the rest. The situation is over. If I knew about Twinkle before hand I would had reported it because I feel it is against Twinkle but is it? Truthseeker1022 (talk) 03:33, 30 April 2016 (UTC)[reply]

Where should I go to request a uw template be added to Twinkle? The template in question is {{uw-afcaddition}}. Anarchyte (work | talk) 10:05, 9 June 2016 (UTC)[reply]

[posted to User talk:Jeffq#Filtering minor edits from user contributions]: Hi Jeff. Back in October last year, you asked whether there is a way to hide minor edits from user contributions pages. This feature has finally been implemented in MediaWiki software, and will be available here on 16 June. You can try it out at Wikipedia Beta. — This, that and the other (talk) 01:41, 10 June 2016 (UTC)[reply]

Thanks for letting me know! ~ Jeff Q (talk) 10:50, 10 June 2016 (UTC)[reply]

...meow...

Mountebank1 (talk) 00:28, 24 August 2016 (UTC)[reply]

Hello, This, that and the other. Voting in the 2016 Arbitration Committee elections is open from Monday, 00:00, 21 November through Sunday, 23:59, 4 December to all unblocked users who have registered an account before Wednesday, 00:00, 28 October 2016 and have made at least 150 mainspace edits before Sunday, 00:00, 1 November 2016.

The Arbitration Committee is the panel of editors responsible for conducting the Wikipedia arbitration process. It has the authority to impose binding solutions to disputes between editors, primarily for serious conduct disputes the community has been unable to resolve. This includes the authority to impose site bans, topic bans, editing restrictions, and other measures needed to maintain our editing environment. The arbitration policy describes the Committee's roles and responsibilities in greater detail.

If you wish to participate in the 2016 election, please review the candidates' statements and submit your choices on the voting page. MediaWiki message delivery (talk) 22:08, 21 November 2016 (UTC)[reply]

Hi This, that and the other. You are invited to comment at a further discussion on the implementation of this user right to patrol and review new pages that is taking place at Wikipedia:New pages patrol/RfC on patrolling without user right. Kudpung กุดผึ้ง (talk) 21:12, 23 November 2016 (UTC)[reply]

There is an (apparent) problem with the addition of the "help=off" parameter that you added to Template:Db-meta in this edit. The problem is that sometimes editors use the "help=off" parameter even without notifying the article author of the speedy delete nomination. Thus, as an administrator, when I am reviewing articles up for speedy deletion, and I find that the author has not been notified, I don't get the help section to provide notice to the author automatically. As I commented at [1], using the "help=off" parameter is like saying, "I didn't notify the article creator that I nominated this page for speedy deletion, and I want to make it more difficult than normal for anyone else to do so, too." If it was your intention that the help=off parameter should only be used or activated once the author has been given notice, it doesn't seem to be working that way. I don't know enough about template parameters to fix the template myself. --Metropolitan90 (talk) 04:38, 5 December 2016 (UTC)[reply]

@Metropolitan90: As you identified, the parameter was added so that the help section is not shown when the creator has been notified. Twinkle, as far as I can see, only adds |help=off when the creator is about to be notified by the tool. If Twinkle has been asked not to notify the page creator, it will not add help=off. However, in the very rare case that the posting to user talk fails (such as because the user talk page is fully protected), the help=off parameter will be added regardless. I suspect (and hope) this is a vanishingly rare scenario.

If people are misusing the parameter, the solution is not to remove the parameter; it might be to change the template documentation, engage with individual users, or identify if any tools, gadgets or scripts are to blame. If you can provide some diffs of users who have been using the parameter incorrectly, it would help to identify the source of the problem. However, at the end of the day, I can't control what other users are doing with the parameter I added. — This, that and the other (talk) 06:59, 5 December 2016 (UTC)[reply]

Thanks, I will follow up when I have diffs to provide. --Metropolitan90 (talk) 02:00, 6 December 2016 (UTC)[reply]

Hello everyone, and sincere apologies if you're getting this message more than once. Just a heads-up that there is currently work on an extension in order to enable CSS styling in templates. Please check the document on mediawiki.org to discuss best storage methods and what we need to avoid with implementation. Thanks, m:User:Melamrawy (WMF), 09:11, 6 February 2017 (UTC)[reply]

I'm contacting you because you participated in this proposal discussion. While the proposal was approved, it has not received developer action. The request is now under consideration as part of the 2017 Developer Wishlist, with voting open through the end of day on Tuesday (23:59 UTC). The latter link describes the voting process, if you are interested. —swpb^T 18:02, 13 February 2017 (UTC)[reply]

Bots Newsletter, April 2017

Greetings! The BAG Newsletter is now the Bots Newsletter, per discussion. As such, we've subscribed all bot operators to the newsletter. You can subscribe/unsubscribe from future newsletters by adding/removing your name from this list. Highlights for this newsletter include: Arbcom Magioladitis ARBCOM case has closed. The remedies of the case include: Community encouraged to review common fixes Community encouraged to review policy on cosmetic edits Developers encouraged to improve AWB interface Bot approvals group encouraged to carefully review BRFA scope Reminders/Restrictions specific to Magioladitis BRFAs We currently have 27 open bot requests at Wikipedia:Bots/Requests for approval, and could use your help processing! Discussions There are multiple ongoing discussions surrounding bot-related matters. In particular: RFC on COSMETICBOT Efforts at WP:CHECKWIKI to identify cosmetic fixes Requested move for the Bot Owners' Noticeboard A phabricator ticket T162685 has been made to have a "bots" tag, so issues related to bot frameworks can be tracked New things Several new things are around: A BAG Guide has been created (WP:BAGG, discussion). Users now have the option to hide AWB from their watchlists via a script (WP:HIDEAWB, discussion) The guidance on how to deal with bot issues has been overhauled (WP:BOTISSUE, discussion) The bot policy has been updated to clarify that bot operators are required to register accounts. (WP:BOTACCOUNT, discussion) Wikimania Wikimania 2017 is happening in Montreal, during 9–13 August. If you plan to attend, or give a talk, let us know! Thank you! edited by:Headbomb 11:35, 12 April 2017 (UTC)[reply] (You can unsubscribe from future newsletters by removing your name from this list.)

I noticed you have experience in JavaScript. I'm hoping you can help me with a problem I've run into writing a userscript.

Please see my post at Wikipedia talk:WikiProject JavaScript#Nested RegExp.

Thank you. The Transhumanist 12:27, 5 May 2017 (UTC)[reply]

I notice that you pushed the code for this to GitHub, but it's not reflected on my Twinkle yet, and it's been a few weeks. Can you deploy from there to here, or does @MusikAnimal: have to do it? – Train2104 (t • c) 22:37, 5 July 2017 (UTC)[reply]

@Train2104: I'm not an administrator, so no, I can't. MusikAnimal can though. I've been waiting for mw:Gadgets 2.0 for about 6 years - hopefully one day we will get it, and then non-admins will be able to manage gadgets. — This, that and the other (talk) 23:05, 5 July 2017 (UTC)[reply]

 Done Just ping me whenever it needs to be synced, only takes a few minutes :) I don't think there's a way to get notifications about commits to select repos on GitHub, or else I'd just go by that — MusikAnimal ^talk 23:49, 5 July 2017 (UTC)[reply]

Bots Newsletter, July 2017

Greetings! Here is the 4th issue of the Bots Newsletter (formerly the BAG Newletter). You can subscribe/unsubscribe from future newsletters by adding/removing your name from this list. Highlights for this newsletter include: BAG BU Rob13 and Cyberpower678 are now members of the BAG (see RfBAG/BU Rob13 and RfBAG/Cyberpower678 3). BU Rob13 and Cyberpower678 are both administrators; the former operates BU RoBOT which does a plethora of tasks, while the latter operates Cyberbot I (which replaces old bots), Cyberbot II (which does many different things), and InternetArchiveBot which combats link rot. Welcome to the BAG! BRFAs We currently have 12 open bot requests at Wikipedia:Bots/Requests for approval, and could use your help processing! Discussions Efforts at WP:CHECKWIKI to identify cosmetic fixes are still ongoing. The RFC on COSMETICBOT has concluded with "a clear consensus exists to adopt the proposed language". The new wording is now live. The venue for bot appeals and reexaminations has been changed from WP:BRFA to WP:BOTN (see discussion) The Wikipedia:Bot owner's noticeboard is now the Wikipedia:Bots/Noticeboard (see discussion). New things A historical correction was made to WP:BOTPOL (see discussion). WP:HIDEBOTS now mentions how to hide all bots from your watchlist, not only specific bots. The phabricator ticket T162685 is now closed, and we now have "#Bots-Framework" tag, so issues related to bot frameworks can be tracked. Wikibits.js has been removed (see discussion). 21 inactive bots have been deflagged (see discussion). WP:BOTISSUE has been updated to mention that BAG members can act as neutral mediators in bot-related disputes. WP:INTERWIKIBOT has been updated to reflect the post-February 2013 practice of putting interwiki links on Wikidata, rather than on Wikipedia (see discussion). Upcoming HTML Tidy will be phased out in June 2018, or possibly earlier. This may affect some bots (see FAQ). Wikimania Wikimania 2017 is happening in Montreal, during 9–13 August. If you plan to attend, or give a talk, let us know! Thank you! edited by: Headbomb 17:12, 19 July 2017 (UTC)[reply] (You can subscribe or unsubscribe from future newsletters by adding or removing your name from this list.)

Category:Wikipedia bots running on the Wikimedia Labs cluster, which you created, has been nominated for possible deletion, merging, or renaming. A discussion is taking place to see if it abides with the categorization guidelines. If you would like to participate in the discussion, you are invited to add your comments at the category's entry on the categories for discussion page. Thank you. -- MarcoAurelio (talk) 10:34, 5 August 2017 (UTC)[reply]

Hello. I would like to nominate a number of templates for discussion, and I noticed that your bot TTObot may help with it. The problematic templates are:

• Template:Marvel Comics characters (A)
• Template:Marvel Comics characters (B)
• Template:Marvel Comics characters (C)
• Template:Marvel Comics characters (D)
• Template:Marvel Comics characters (E)
• Template:Marvel Comics characters (F)
• Template:Marvel Comics characters (G)
• Template:Marvel Comics characters (H)
• Template:Marvel Comics characters (I)
• Template:Marvel Comics characters (J)
• Template:Marvel Comics characters (K)
• Template:Marvel Comics characters (L)
• Template:Marvel Comics characters (M)
• Template:Marvel Comics characters (N)
• Template:Marvel Comics characters (O)
• Template:Marvel Comics characters (P)
• Template:Marvel Comics characters (Q)
• Template:Marvel Comics characters (R)
• Template:Marvel Comics characters (S)
• Template:Marvel Comics characters (T)
• Template:Marvel Comics characters (U)
• Template:Marvel Comics characters (V)
• Template:Marvel Comics characters (W)
• Template:Marvel Comics characters (X)
• Template:Marvel Comics characters (Y)
• Template:Marvel Comics characters (Z)
• Template:Marvel Comics characters (0–9)

All those navboxes are linking articles by a trivial theme (the first character of their names). There are several templates already that group Marvel characters by more reasonable criteria, such as those that appear in a same publication (like {{Fantastic Four}}), so those ones are not really needed. Cambalachero (talk) 15:09, 11 September 2017 (UTC)[reply]

@Cambalachero: With only 27 templates it's probably easier to do it by hand. If you had, say, 50 or 100 templates to tag, then TTObot might be a good choice. — This, that and the other (talk) 09:49, 14 September 2017 (UTC)[reply]

I have proposed renaming of Category:Users who do not wish to receive talkbacks to "Wikipedians...". – Fayenatic London 10:09, 12 October 2017 (UTC)[reply]

Hello, This, that and the other. Voting in the 2017 Arbitration Committee elections is now open until 23.59 on Sunday, 10 December. All users who registered an account before Saturday, 28 October 2017, made at least 150 mainspace edits before Wednesday, 1 November 2017 and are not currently blocked are eligible to vote. Users with alternate accounts may only vote once.

The Arbitration Committee is the panel of editors responsible for conducting the Wikipedia arbitration process. It has the authority to impose binding solutions to disputes between editors, primarily for serious conduct disputes the community has been unable to resolve. This includes the authority to impose site bans, topic bans, editing restrictions, and other measures needed to maintain our editing environment. The arbitration policy describes the Committee's roles and responsibilities in greater detail.

If you wish to participate in the 2017 election, please review the candidates and submit your choices on the voting page. MediaWiki message delivery (talk) 18:42, 3 December 2017 (UTC)[reply]

Hello This, that and the other. Your account has been added to the "New page reviewers" user group, allowing you to review new pages and mark them as patrolled, tag them for maintenance issues, or in some cases, tag them for deletion. The list of articles awaiting review is located at the New Pages Feed. New page reviewing is a vital function for policing the quality of the encylopedia, if you have not already done so, you must read the new tutorial at New Pages Review, the linked guides and essays, and fully understand the various deletion criteria. If you need more help or wish to discuss the process, please join or start a thread at page reviewer talk.

• URGENT: Please consider helping get the huge backlog down to a manageable number of pages as soon as possible.
• Be nice to new users - they are often not aware of doing anything wrong.
• You will frequently be asked by users to explain why their page is being deleted - be formal and polite in your approach to them too, even if they are not.
• Don't review a page if you are not sure what to do. Just leave it for another reviewer.
• Remember that quality is quintessential to good patrolling. Take your time to patrol each article, there is no rush. Use the message feature and offer basic advice.

The reviewer right does not change your status or how you can edit articles. If you no longer want this user right, you may ask any administrator to remove it for you at any time. In case of abuse or persistent inaccuracy of reviewing, the right can be revoked at any time by an administrator. — xaosflux ^Talk 04:53, 29 December 2017 (UTC)[reply]

If you want to be on the NPP mailing list, sign up at Wikipedia:New pages patrol/Reviewers/Newsletter list. — xaosflux ^Talk 04:54, 29 December 2017 (UTC)[reply]

Looks like I conflicted @Alex Shih:, but same message. — xaosflux ^Talk 04:55, 29 December 2017 (UTC)[reply]

Yes. Same message. Thank you! Alex Shih (talk) 04:57, 29 December 2017 (UTC)[reply]

A tag has been placed on Offing, requesting that it be deleted from Wikipedia. This has been done under two or more of the criteria for speedy deletion, by which pages can be deleted at any time, without discussion. If the page meets any of these strictly-defined criteria, then it may soon be deleted by an administrator. The reasons it has been tagged are:

• It is an article with no content whatsoever, or whose contents consist only of external links, a "See also" section, book references, category tags, template tags, interwiki links, a rephrasing of the title, or an attempt to contact the subject of the article. (See section A3 of the criteria for speedy deletion.) Wikipedia has standards for the minimum necessary information to be included in short articles; you can see these at Wikipedia:Stub. Also please note that articles must be on notable subjects and should provide references to reliable sources that verify their content.
• It consists of a dictionary definition or other article that has been transwikied to another project and the author information recorded. (See section A5 of the criteria for speedy deletion.)

If you think this page should not be deleted for this reason, you may contest the nomination by visiting the page and clicking the button labelled "Contest this speedy deletion". This will give you the opportunity to explain why you believe the page should not be deleted. However, be aware that once a page is tagged for speedy deletion, it may be deleted without delay. Please do not remove the speedy deletion tag from the page yourself, but do not hesitate to add information in line with Wikipedia's policies and guidelines. If the page is deleted, and you wish to retrieve the deleted material for future reference or improvement, then please contact the deleting administrator, or if you have already done so, you can place a request here. Matuko 09:19, 24 January 2018 (UTC)

A tag has been placed on Offing, requesting that it be deleted from Wikipedia. This has been done under two or more of the criteria for speedy deletion, by which pages can be deleted at any time, without discussion. If the page meets any of these strictly-defined criteria, then it may soon be deleted by an administrator. The reasons it has been tagged are:

• It is an article with no content whatsoever, or whose contents consist only of external links, a "See also" section, book references, category tags, template tags, interwiki links, a rephrasing of the title, or an attempt to contact the subject of the article. (See section A3 of the criteria for speedy deletion.) Wikipedia has standards for the minimum necessary information to be included in short articles; you can see these at Wikipedia:Stub. Also please note that articles must be on notable subjects and should provide references to reliable sources that verify their content.
• It consists of a dictionary definition or other article that has been transwikied to another project and the author information recorded. (See section A5 of the criteria for speedy deletion.)

If you think this page should not be deleted for this reason, you may contest the nomination by visiting the page and clicking the button labelled "Contest this speedy deletion". This will give you the opportunity to explain why you believe the page should not be deleted. However, be aware that once a page is tagged for speedy deletion, it may be deleted without delay. Please do not remove the speedy deletion tag from the page yourself, but do not hesitate to add information in line with Wikipedia's policies and guidelines. If the page is deleted, and you wish to retrieve the deleted material for future reference or improvement, then please contact the deleting administrator, or if you have already done so, you can place a request here. Matuko 09:19, 24 January 2018 (UTC)

@Matuko: I think {{wi}} articles ought to be considered more as soft redirects, so that the article CSD criteria do not apply. Let's see what an admin thinks. — This, that and the other (talk) 09:23, 24 January 2018 (UTC)[reply]

Bots Newsletter, March 2018

Greetings! Here is the 5th issue of the Bots Newsletter (formerly the BAG Newletter). You can subscribe/unsubscribe from future newsletters by adding/removing your name from this list. Highlights for this newsletter include: ARBCOM Magioladitis 2 happened, leading to further restrictions on Magioladitis (decision, summary). Betacommand 3 was proposed to be amended to lift the indefinite ban on Δ, but was unsuccessful (decision). A motion concerning Crosswiki issues (mostly concerning Wikidata) was passed (see discussion). BAG Hersfold was removed from the BAG due to long term inactivity. BRFAs We currently have 6 open bot requests at Wikipedia:Bots/Requests for approval, and could use your help processing! Discussions While there were no large-scale bot-related discussion in the past few months, you can check WP:BOTN and WT:BOTPOL (and their corresponding archives) for smaller issues that came up. New things WP:BOTDICT, a dictionary of common bot-related terms (see discussion). 6 inactive bots have been deflagged (see discussion). The 2017 Community Wishlist Survey happened. Two bot-related proposal passed, #6 deploy Article Alerts to other languages and #10 Commons deletion notification bot, although other entries may affect bots as well. Category:Wikipedia bots and its subcategories has had some cleanup. Bot-related pages that were historically important but are no longer of interests can be found in Category:Wikipedia bots (historical) The edit summary limit has been increased to 1000 characters (see T6715). If a bot you operate relied on the old truncation limit (255 characters), please review/update your code, as overly long summaries can be disruptive/annoying. If you want to use extra characters to have more information in your edit summary, please do so intelligently. You will soon be able to ping users from the edit summary (see T188469). If you wish to use this feature in your bot, please do so intelligently. Upcoming HTML Tidy will be phased out in June 2018, or possibly earlier. This may affect some bots (see FAQ). Thank you! edited by: Headbomb 03:12, 3 March 2018 (UTC)[reply] (You can subscribe or unsubscribe from future newsletters by adding or removing your name from this list.)

Hello,

There will be some changes to the way wikitext is parsed during the next few weeks. It will affect all namespaces. You can see a list of pages that may display incorrectly at Special:LintErrors. Since most of the easy problems have already been solved at the English Wikipedia, I am specifically contacting tech-savvy editors such as yourself with this one-time message, in the hope that you will be able to investigate the remaining high-priority pages during the next month.

There are approximately 10,000 articles (and many more non-article pages) with high-priority errors. The most important ones are the articles with misnested tags and table problems. Some of these involve templates, such as infoboxes, or the way the template is used in the article. In some cases, the "error" is a minor, unimportant difference in the visual appearance. In other cases, the results are undesirable. You can see a before-and-after comparison of any article by adding ?action=parsermigration-edit to the end of a link, like this: https://en.wikipedia.org/wiki/Arthur_Foss?action=parsermigration-edit (which shows a difference in how {{infobox ship}} is parsed).

If you are interested in helping with this project, please see Wikipedia:Linter. There are also some basic instructions (and links to even more information) at https://lists.wikimedia.org/pipermail/wikitech-ambassadors/2018-April/001836.html You can also leave a note at WT:Linter if you have questions.

Thank you for all the good things you do for the English Wikipedia. Whatamidoing (WMF) (talk) 21:18, 19 April 2018 (UTC)[reply]

An editor has asked for a discussion to address the redirect List is of South Australian organisations providing support to people with disability. Since you had some involvement with the List is of South Australian organisations providing support to people with disability redirect, you might want to participate in the redirect discussion if you have not already done so. UnitedStatesian (talk) 18:54, 22 May 2018 (UTC)[reply]

Hi TTO. I've been trying to get a basic grasp on subst and safsubst recently, and I see you have had it for years. Why, do you think, Special:Diff/849795156 ended up looking like that? Did you enter "revisionuser" manually in {{RMassist/core}} instead of using {{RMassist}} that includes a safesubst of REVISIONUSER? Sam Sailor 12:40, 11 July 2018 (UTC)[reply]

Yes, I did enter that manually. No idea why it didn't work. Perhaps I had a good grasp of subst and safesubst in 2011 when I wrote that page, but I have evidently lost touch with template substitution since then. — This, that and the other (talk) 23:51, 11 July 2018 (UTC)[reply]

Is this yours? Primefac (talk) 13:12, 11 July 2018 (UTC)[reply]

@Primefac: Yeah, sorry about that. I thought I'd pitch in and enact a non-admin closure, but I was unaware that the destination title was salted, so I ended up having to ask for a requested move. It did get moved eventually. — This, that and the other (talk) 23:50, 11 July 2018 (UTC)[reply]

Cool, no worries. Primefac (talk) 00:07, 12 July 2018 (UTC)[reply]

Bots Newsletter, August 2018

Greetings! Here is the 6th issue of the Bots Newsletter. You can subscribe/unsubscribe from future newsletters by adding/removing your name from this list. Highlights for this newsletter include: ARBCOM Nothing particular important happened. Those who care already know, those who don't know wouldn't care. The curious can dig ARBCOM archives themselves. BAG There were no changes in BAG membership since the last Bots Newsletter. Headbomb went from semi-active to active. In the last 3 months, only 3 BAG members have closed requests - help is needed with the backlog. BOTREQs and BRFAs As of writing, we have... 24 active BOTREQs, please help if you can! 5 open BRFAs and 3 BRFAs in need of BAG attention (see live status). 54 approved bot tasks since the start of 2018. Of note, Community Tech bot 5 (the #10 Wish on the 2017 Community Survey) was approved to notify users concerning problematic images and files from Wikimedia Commons. Also If you're a bot operator that can help with Tidy/Linter error cleanup (see discussion, discussion), please file a BRFA! 8 inactive bots have been deflagged (see discussion, discussion, discussion). Discussions These are some of the discussions that happened / are still happening since the last Bots Newsletter. Many are stale, but some are still active. Use of tags by bots – Exploring the use of a new 'bot' tag. Mass page moves – Bot policy question/clarification about mass moves. Creation of redirects – Bot policy question/clarification about the creation of redirects. Guidance on disruptive use of semi–automated tools? – Related to meatbots (see also MOS discussion, which resulted in small addition to MOS:VAR). Discussion concerning WP:BOTFLAG/WP:RC – A reminder that bots should use the bot flag when it makes sense to use it (see also VPT discussion and CREATEBOT update). Out of curiosity... (to all bot operators) – BotPasswords vs OAuth usage amongst bot operators. Introducing Toolhub – Toolhub is looking for feedback. New things {{Automated tools}}, a new template linking to user-activated tools and scripts has been created. It can be used in articles previews, and can be placed on any non-mainspace page/template (e.g. {{Draft article}}) to provide convenient links to editors. AWB 5.10.0.0 is out, after nearly 20 months without updates. If you run an old version, you will be prompted to install the new version automatically. See the changelog for what's new. Note that the next version will require .NET Framework 4.5. Many thanks to Reedy and the AWB team. BotWatch, "a listing of editors that have made >2 edits per minute [without] a bot flag", is being developed by SQL (see discussion). Massive updates and improvements have been made to Citation bot in the past few months (see discussions, discussions, discussions). You can activate the bot here, amongst other methods. HTML Tidy has been phased out (see Tech News #28). {{Newbot}} has been reorganized a bit (diff). In particular, it links to previously approved BRFAs (see discussion). Wikipedia:Bots#See also has been reorganized a bit (diff). The bot dictionary has two new entries, context bot and context-sensitive edit. The bot request header has been updated to include better guidance (see discussion). The subcategories of Category:Wikipedia bot requests for approval have been sorted in a consistent manner to make past BRFAs easier to find. Thank you! edited by: Headbomb 15:04, 18 August 2018 (UTC)[reply] (You can subscribe or unsubscribe from future newsletters by adding or removing your name from this list.)

Hi. I have a mass Tfd nomination at Wikipedia:Templates for discussion/Log/2018 October 7 which consists of 48 pages. Can your bot please tag all the template for deletion. Thanks. Pkbwcgs (talk) 10:04, 7 October 2018 (UTC)[reply]

@Pkbwcgs: I may not have time to do this in the coming few days, as I am extremely busy IRL right now. It's not an enormous task, so you might be able to find a taker at Wikipedia:AutoWikiBrowser/Tasks. — This, that and the other (talk) 10:09, 7 October 2018 (UTC)[reply]

I am doing it right now with AWB. Pkbwcgs (talk) 10:11, 7 October 2018 (UTC)[reply]

Hello, This, that and the other. Voting in the 2018 Arbitration Committee elections is now open until 23.59 on Sunday, 3 December. All users who registered an account before Sunday, 28 October 2018, made at least 150 mainspace edits before Thursday, 1 November 2018 and are not currently blocked are eligible to vote. Users with alternate accounts may only vote once.

The Arbitration Committee is the panel of editors responsible for conducting the Wikipedia arbitration process. It has the authority to impose binding solutions to disputes between editors, primarily for serious conduct disputes the community has been unable to resolve. This includes the authority to impose site bans, topic bans, editing restrictions, and other measures needed to maintain our editing environment. The arbitration policy describes the Committee's roles and responsibilities in greater detail.

If you wish to participate in the 2018 election, please review the candidates and submit your choices on the voting page. MediaWiki message delivery (talk) 18:42, 19 November 2018 (UTC)[reply]

Hey, I was wondering if your bot User:TTObot could help me nominate all templates in Category:Elementbox templates. Template:Elementbox was converted into Template:Infobox element which uses a different syntax and does not use any of these templates which are marked as deprecated. --Gonnym (talk) 12:49, 6 February 2019 (UTC)[reply]

Bots Newsletter, August 2019

Greetings! Here is the 7th issue of the Bots Newsletter, a lot happened since last year's newsletter! You can subscribe/unsubscribe from future newsletters by adding/removing your name from this list. Highlights for this newsletter include: ARBCOM Nothing of note happened. Just like we like it. BAG Several (1 + 12 = 13) users have been retired/resigned from the BAG due to inactivity, per our new activity requirements (discussion). BAG members are expected to be active on Wikipedia to have their finger on the pulse of the community. After two years without any bot-related activity (such as posting on bot-related pages, posting on a bot's talk page, or operating a bot), BAG members will be retired from BAG following a one-week notice. Retired members can re-apply for BAG membership as normal if they wish to rejoin the BAG. Two BAG members retired Madman (talk · contribs) retired. BU Rob13 (talk · contribs) vanished and retired. Three new BAG members have been voted in, welcome to the BAG! Primefac (talk · contribs) joined on 2018-12-12 (RfBAG). Primefac operates PrimeBOT (talk · contribs) which does a plethora of tasks. TheSandDoctor (talk · contribs) joined on 2019-01-21 (RfBAG). TheSandDoctor operates several bots including DeprecatedFixerBot (talk · contribs). Enterprisey (talk · contribs) joined on 2019-08-07 (RfBAG). Enterprisey operates EnterpriseyBot (talk · contribs), which does a plethora of tasks, RemindMeBot (talk · contribs) which posts reminders, and codes several scripts. We thank former members for their service and wish Madman a happy retirement. We note that Madman and BU Rob13 were not inactive and could resume their BAG positions if they so wished, should their retirements happens to be temporary. BOTDICT Two new entries feature in the bots dictionary Editor-hostile wikitext – describes wikitext structuring that is editor hostile, even if it renders correctly Spectrum of usefulness – describes how tasks are deemed useful or not BOTPOL Activity requirements: BAG members now have an activity requirement. The requirements are very light, one only needs to be involved in a bot-related area at some point within the last two years. For purpose of meeting these requirements, discussing a bot-related matter anywhere on Wikipedia counts, as does operating a bot (RFC). Copyvio flag: Bot accounts may be additionally marked by a bureaucrat upon BAG request as being in the "copyviobot" user group on Wikipedia. This flag allows using the API to add metadata to edits for use in the New pages feed (discussion). There is currently 1 bot using this functionality. Mass creation: The restriction on mass-creation (semi-automated or automated) was extended from articles, to all content-pages. There are subtleties, but content here broadly means whatever a reader could land on when browsing the mainspace in normal circumstances (e.g. Mainspace, Books, most Categories, Portals, ...). There is also a warning that WP:MEATBOT still applies in other areas (e.g. Redirects, Wikipedia namespace, Help, maintenance categories, ...) not explicitely covered by WP:MASSCREATION. BOTREQs and BRFAs As of writing, we have... 20 active BOTREQs, please help if you can! 14 open BRFAs and 1 BRFA in need of BAG attention (see live status). In 2018, 96 bot task were approved. An AWB search shows approximately 29 were withdrawn/expired, and 6 were denied. Since the start of 2019, 97 bot task were approved. Logs show 15 were withdrawn/expired, and 15 were denied. 10 inactive bots have been deflagged (see discussion). 5 other bots have been deflagged per operator requests or similar (see discussion). New things All bot-related discussion pages now have a centralized and searchable archive box (see discussion). Discussions are searchable per noticeboard, or globally. {{Bot}} now supports |status=expired (see discussion). This led to the deletion of Category:Indefinitely blocked Wikipedia bots as useless (see discussion). WP:BOTREQ now mentions WP:SCRIPTREQ and WP:AWBTASKS as alternatives to bot requests. The bot creation guide now mentions bot flags, and two new languages Awk and MATLAB. Other minor tweaks have been made. AAlertBot has received major code updates. In particular, WP:AALERTS will now report splits, mergers, and AFC submissions. Citation bot has received several updates (User talk:Citation bot/Archive 10/11/12/13/14/15/16/17). In particular, the bot stopped the automated removal of |publisher= from {{cite journal}}, and stopped the automated addition of CiteSeerX links, and now uses OAuth to authenticate those who make requests of the bot. Other discussions These are some of the discussions that happened / are still happening since the last Bots Newsletter. Many are stale, but some are still active. Wikipedia:Bots/Noticeboard/Archive 12#Adminbots requests page Wikipedia:Bots/Noticeboard/Archive 12#Double-redirect tagging (2019) Wikipedia:Bots/Noticeboard/Archive 12#Long and Winding Road to Parsoid Wikipedia:Bots/Noticeboard/Archive 13#Bot-like user scripts Wikipedia:Bots/Noticeboard/Archive 13#WP:URLREQ Wikipedia:Bots/Noticeboard/Archive 13#Wikipedia:Bots/Status Wikipedia talk:Bot Approvals Group#Minimum edits Wikipedia talk:Bot policy#Minor update to WP:BOTISSUE Wikipedia talk:Bot policy#Semi-automated Portal creation Wikipedia talk:Bot policy#Clarification on "Bots operated by multiple users" Wikipedia talk:Bot policy#Bots triggered by multiple users Wikipedia talk:Bots#How to use Special:ApiFeatureUsage See also the latest discussions at the bot noticeboard. Thank you! edited by: Headbomb 17:24, 7 August 2019 (UTC)[reply] (You can subscribe or unsubscribe from future newsletters by adding or removing your name from this list.)

Greetings,

the instructions of User:TTObot say that I should request a mass-tagging task here. Is it possible to tag all the templates on Wikipedia:Deletion review/Log/2019 September 7 with a tag for Wikipedia:Templates for discussion/Log/2019 September 14#Template:Venezuela Squad 1990 FIBA World Championship? Jo-Jo Eumerus (talk, contributions) 11:39, 14 September 2019 (UTC)[reply]

Looks like Frietjes got in before me :) This, that and the other (talk) 01:59, 15 September 2019 (UTC)[reply]

Hello! Voting in the 2019 Arbitration Committee elections is now open until 23:59 on Monday, 2 December 2019. All eligible users are allowed to vote. Users with alternate accounts may only vote once. The Arbitration Committee is the panel of editors responsible for conducting the Wikipedia arbitration process. It has the authority to impose binding solutions to disputes between editors, primarily for serious conduct disputes the community has been unable to resolve. This includes the authority to impose site bans, topic bans, editing restrictions, and other measures needed to maintain our editing environment. The arbitration policy describes the Committee's roles and responsibilities in greater detail. If you wish to participate in the 2019 election, please review the candidates and submit your choices on the voting page. If you no longer wish to receive these messages, you may add {{NoACEMM}} to your user talk page. MediaWiki message delivery (talk) 00:09, 19 November 2019 (UTC)[reply]

Hello,

Google Code-In, Google-organized contest in which the Wikimedia Foundation participates, starts in a few weeks. This contest is about taking high school students into the world of opensource. I'm sending you this message because you recently edited a documentation page at the English Wikipedia.

I would like to ask you to take part in Google Code-In as a mentor. That would mean to prepare at least one task (it can be documentation related, or something else - the other categories are Code, Design, Quality Assurance and Outreach) for the participants, and help the student to complete it. Please sign up at the contest page and send us your Google account address to google-code-in-admins@lists.wikimedia.org, so we can invite you in!

From my own experience, Google Code-In can be fun, you can make several new friends, attract new people to your wiki and make them part of your community.

If you have any questions, please let us know at google-code-in-admins@lists.wikimedia.org.

Thank you!

--User:Martin Urbanec (talk) 21:58, 23 November 2019 (UTC)[reply]

Hi there, I'm HasteurBot. I just wanted to let you know that Draft:Invalid dinosaur, a page you created, has not been edited in 5 months. The Articles for Creation space is not an indefinite storage location for content that is not appropriate for articlespace.

If your submission is not edited soon, it could be nominated for deletion. If you would like to attempt to save it, you will need to improve it.

You may request Userfication of the content if it meets requirements.

If the deletion has already occured, instructions on how you may be able to retrieve it are available at WP:REFUND/G13.

Thank you for your attention. HasteurBot (talk) 01:23, 28 December 2019 (UTC)[reply]

Hi. Thank you for your recent edits. An automated process has detected that when you recently edited The Offbeat of Avenues, you added a link pointing to the disambiguation page Michael McDonald (check to confirm | fix with Dab solver). Such links are usually incorrect, since a disambiguation page is merely a list of unrelated topics with similar titles. (Read the FAQ • Join us at the DPL WikiProject.)

It's OK to remove this message. Also, to stop receiving these messages, follow these opt-out instructions. Thanks, DPL bot (talk) 09:28, 30 December 2019 (UTC)[reply]

Template:No talkback has been nominated for deletion. You are invited to comment on the discussion at the entry on the Templates for discussion page. Andy Mabbett (Pigsonthewing); Talk to Andy; Andy's edits 19:36, 24 October 2020 (UTC)[reply]

Hello! Voting in the 2020 Arbitration Committee elections is now open until 23:59 (UTC) on Monday, 7 December 2020. All eligible users are allowed to vote. Users with alternate accounts may only vote once. The Arbitration Committee is the panel of editors responsible for conducting the Wikipedia arbitration process. It has the authority to impose binding solutions to disputes between editors, primarily for serious conduct disputes the community has been unable to resolve. This includes the authority to impose site bans, topic bans, editing restrictions, and other measures needed to maintain our editing environment. The arbitration policy describes the Committee's roles and responsibilities in greater detail. If you wish to participate in the 2020 election, please review the candidates and submit your choices on the voting page. If you no longer wish to receive these messages, you may add {{NoACEMM}} to your user talk page. MediaWiki message delivery (talk) 01:41, 24 November 2020 (UTC)[reply]

Category:Scribunto modules with errors has been nominated for deletion. A discussion is taking place to decide whether this proposal complies with the categorization guidelines. If you would like to participate in the discussion, you are invited to add your comments at the category's entry on the categories for discussion page. Thank you. Gonnym (talk) 10:11, 19 November 2021 (UTC)[reply]

Hello! Voting in the 2021 Arbitration Committee elections is now open until 23:59 (UTC) on Monday, 6 December 2021. All eligible users are allowed to vote. Users with alternate accounts may only vote once. The Arbitration Committee is the panel of editors responsible for conducting the Wikipedia arbitration process. It has the authority to impose binding solutions to disputes between editors, primarily for serious conduct disputes the community has been unable to resolve. This includes the authority to impose site bans, topic bans, editing restrictions, and other measures needed to maintain our editing environment. The arbitration policy describes the Committee's roles and responsibilities in greater detail. If you wish to participate in the 2021 election, please review the candidates and submit your choices on the voting page. If you no longer wish to receive these messages, you may add {{NoACEMM}} to your user talk page. MediaWiki message delivery (talk) 00:22, 23 November 2021 (UTC)[reply]

I created an article for a Jade Thompson, about 10 years ago. I just read your message today. Michuk (talk) 23:10, 24 November 2021 (UTC)[reply]

Bots Newsletter, December 2021

BRFA activity by month Welcome to the eighth issue of the English Wikipedia's Bots Newsletter, your source for all things bot. Maintainers disappeared to parts unknown... bots awakening from the slumber of æons... hundreds of thousands of short descriptions... these stories, and more, are brought to you by Wikipedia's most distinguished newsletter about bots. Our last issue was in August 2019, so there's quite a bit of catching up to do. Due to the vast quantity of things that have happened, the next few issues will only cover a few months at a time. This month, we'll go from September 2019 through the end of the year. I won't bore you with further introductions — instead, I'll bore you with a newsletter about bots. Overall Between September and December 2019, there were 33 BRFAs. Of these, Y 25 were approved, and 8 were unsuccessful (N2 3 denied, ? 3 withdrawn, and 2 expired). September 2019 Y Monkbot 16, DannyS712 bot 60, Ahechtbot 6, PearBOT 3, Qbugbot 3 · N2 DannyS712 bot 5, PkbwcgsBot 24 · ? DannyS712 bot 61, TheSandBot 4 TParis goes away, UTRSBot goes kaput: Beeblebrox noted that the bot for maintaining on-wiki records of UTRS appeals stopped working a while ago. TParis, the semi-retired user who had previously run it, said they were "unlikely to return to actively editing Wikipedia", and the bot had been vanquished by trolls submitting bogus UTRS requests on behalf of real blocked users. While OAuth was a potential fix, neither maintainer had time to implement it. TParis offered to access to the UTRS WMFLabs account to any admin identified with the WMF: "I miss you guys a whole lot [...] but I've also moved on with my life. Good luck, let me know how I can help". Ultimately, SQL ended up in charge. Some progress was made, and the bot continued to work another couple months — but as of press time, UTRSBot has not edited since November 2019. Article-measuring contest resumed: The list of Wikipedians by article count, which had lain dead for several years, was triumphantly resurrected by GreenC following a bot request. October 2019 Y OAbot 3, DannyS712 bot 47, Pathbot 2, PearBOT 2, DannyS712 bot 59, DannyS712 bot 62, HasteurBot 14, PearBOT 4, WOSlinkerBot 4, MilHistBot 5 Curb Safe Charmer adopts reFill: TAnthony pointed out that reFill 2's bug reports were going unanswered; creator Zhaofeng Li had retired from Wikipedia, and a maintainer was needed. As of June 2021, Curb Safe Charmer had taken up the mantle, saying: "Not that I have all the skills needed but better me than nobody! 'Maintainer' might be too strong a term though. Volunteers welcome!" November 2019 Y BHGbot 4, YiFeiBot 2, DannyS712 bot III 64 · ? PearBOT Old bots do new tricks: DannyS712 bot III 64 prowled redirects, YiFeiBot 2 archived GoCE requests, and BHGbot 4 removed links to portals deleted at MfD (until its authorization was revoked in January at operator BrownHairedGirl's request). December 2019 Y DemonDays64 Bot, DannyS712 bot III 66, Bot1058 6, Monkbot 15, MilHistBot 6, PearBOT 5, DannyS712 bot IV 65 · N2 SportsStatsBot · Xinbenlv bot, SteveBot 8 Redirects to be autopatrolled: A RfC took place at WP:NPP, closing with unanimous consensus that new redirects should be automatically marked as patrolled by bot. DannyS712 wasted no time, and submitted DannyS712 bot III 66 the next day; it passed two days after that. 200,000 bios get short descs: Along a similar vein, Bot1058 6 was approved to remove disambiguation pages from Category:Monitored short pages and a new bot (DemonDays64 Bot) changed lots of http links to https using JavaScript Wiki Browser. One particularly neat task, PearBOT 5, automatically generated short descriptions for more than 200,000 biographies. In the next issue of Bots Newsletter: What's next for our intrepid band of coders, maintainers and approvers? What happens when two bots want to clerk the same page? What happens when an adminbot goes hog wild? Will reFill ever get fixed? What's up with ListeriaBot, anyway? Python 3.4 deprecation? In my PyWikiBot? (It's more likely than you think!) These questions will be answered — and new questions raised — by the January 2022 Bots Newsletter. Tune in, or miss out! Signing off... jp×g 04:29, 10 December 2021 (UTC)[reply] (You can subscribe or unsubscribe from future newsletters by adding or removing your name from this list.)

Template:Circle has been listed at templates for discussion. You are invited to comment on the discussion at the entry on the Templates for discussion page. Gonnym (talk) 12:14, 23 December 2021 (UTC)[reply]

Hello, This, that and the other. This is a bot-delivered message letting you know that Draft:Invalid dinosaur, a page you created, has not been edited in at least 5 months. Drafts that have not been edited for six months may be deleted, so if you wish to retain the page, please edit it again or request that it be moved to your userspace.

If the page has already been deleted, you can request it be undeleted so you can continue working on it.

Thank you for your submission to Wikipedia. FireflyBot (talk) 23:02, 16 January 2022 (UTC)[reply]

Bots Newsletter, January 2022

BRFA activity by month Welcome to the ninth issue of the English Wikipedia's Bots Newsletter, your source for all things bot. Vicious bot-on-bot edit warring... superseded tasks... policy proposals... these stories, and more, are brought to you by Wikipedia's most distinguished newsletter about bots. After a long hiatus between August 2019 and December 2021, there's quite a bit of ground to cover. Due to the vastness, I decided in December to split the coverage up into a few installments that covered six months each. Some people thought this was a good idea, since covering an entire year in a single issue would make it unmanageably large. Others thought this was stupid, since they were getting talk page messages about crap from almost three years ago. Ultimately, the question of whether each issue covers six months or a year is only relevant for a couple more of them, and then the problem will be behind us forever. Of course, you can also look on the bright side – we are making progress, and this issue will only be about crap from almost two years ago. Today we will pick up where we left off in December, and go through the first half of 2020. Overall In the first half of 2020, there were 71 BRFAs. Of these, Y 59 were approved, and 12 were unsuccessful (with N2 8 denied, ? 2 withdrawn, and 2 expired). January 2020 Yeah, you're not gonna be able to get away with this anymore. Y ST47Bot, Seppi333Bot, Qbugbot 4 · N2 PkbwcgsBot 25, PkbwcgsBot 26 A new Pywikibot release dropped support for Python 3.4, and it was expected that support for Python 2.7 would be removed in coming updates. Toolforge itself planned to drop Python 2 support in 2022. Two new bots dropped in January 2020: ST47Bot, the successor to STBot, and Seppi333Bot, whose task was to perform a weekly update of four "massive" wikitables for WikiProject Molecular Biology. Cydebot, an adminbot operated by Cyde since 2006, was blocked after going berserk on categories that hadn't yet been CfD'd. February 2020 Y AnomieBOT 78, Cewbot 2, DannyS712 bot 67, DannyS712 bot III 63, PearBOT 6, DemonDays64 Bot 2 · N2 PearBOT On February 1, some concerns were raised about ListeriaBot performing "nonsense" edits. Semi-active operator Magnus Manske (who originally coded the Phase II software|precursor of MediaWiki) was pinged. Meanwhile, the bot was temporarily blocked for several hours until the issue was diagnosed and resolved. On February 18, ST47Bot got into a tussle with Amalthea (bot), and had to be partially-blocked from Wikipedia:Sockpuppet investigations/Cases/Overview. March 2020 Y MajavahBot, SDZeroBot, TheSandBot 6, TheSandBot 7, Bitbotje, FACBot 6, TheSandBot 8, Qbugbot 5, Cewbot 3, SDZeroBot 2, PrimeBOT 31, WikiCleanerBot 12 · AntiCompositeBot In March, a long discussion was started at Wikipedia talk:Bot policy by Skdb about the troubling trend of bots "expiring" without explanation after their owners became inactive. This can happen for a variety of reasons -- API changes break code, hosting providers' software updates break code, hosting accounts lapse, software changes make bots' edits unnecessary, and policy changes make bots' edits unwanted. The most promising solution seemed to be Toolforge hosting (although it has some problems of its own, like the occasional necessity of refactoring code). Some of the twelve bot tasks approved this month were TheSandBot 6 (removing blocked users from Category:Wikipedia usernames with possible policy issues), and TheSandBot 7 (removing unblocked users from Category:Wikipedians who are indefinitely blocked for promotional user names). SDZeroBot 2 was approved to refine geographic stub tags. New bots approved this month were MajavahBot (to patrol WP:EFFPR), SDZeroBot (to merge stub tags), and Bitbotje (fixing DISPLAYTITLE modifications, DEFAULTSORT errors and broken behavior switches in draftspace). April 2020 Y TheSandBot 9, BHGbot 5, DannyS712 bot 69, SDZeroBot 3, ST47ProxyBot, WugBot 4, SDZeroBot 4, DatBot 10, WikiCleanerBot 11, WikiCleanerBot 13, WikiCleanerBot 14, AntiCompositeBot 2, Cewbot 4 · N2 DaedanBot 1 · Creffbot A discussion on the bot noticeboard, "Re-examination of ListeriaBot", was started by Barkeep49, who pointed out repeated operation outside the scope of its BRFA (i.e. editing pages in mainspace, and adding non-free images to others). Some said it was doing good work, and others said it was operating beyond its remit. It was blocked on April 10; the next day it was unblocked, reblocked from article space, reblocked "for specified non-editing actions", unblocked, and indeffed. The next week, several safeguards were implemented in its code by Magnus; the bot was allowed to roam free once more on April 18. ST47ProxyBot joined the stable in April, after a BRFA started in December was finally completed. As an adminbot, it was authorized to block IP addresses belonging to open proxies, public VPN services, and web hosts. New tasks approved for existing bots included BHGbot 5 (diffusing categories), TheSandBot 9 (taking over some tasks from the inactive RonBot), and WugBot 4 (updating data at {{Interactive COVID-19 maps}}). Also, DatBot 10 was approved to scale down non-free SVGs — I didn't even know that was a thing. A discussion at Wikipedia talk:Bot policy was started by Thryduulf about whether WP:BOTCOMM should explicitly specify that bot operators must be responsive to concerns raised on English Wikipedia specifically (as opposed to Phabricator, SourceForge, Toolforge, et cetera). Eventually, the policy was amended to its current form: Issues and enquiries are typically expected to be handled on the English Wikipedia. Pages reachable via unified login, like a talk page at Commons or at Italian Wikipedia could also be acceptable [...] External sites like Phabricator or GitHub (which require separate registration or do not allow for IP comments) and email (which can compromise anonymity) can supplement on-wiki communication, but do not replace it. May 2020 Y MajavahBot 3, DannyS712 bot 70, CitationCleanerBot 5, Dreamy Jazz Bot 4, QEDKbot, William Avery Bot 2, DannyS712 bot 68, PrimeBOT 32, TheSandBot 10, Bot1058 7, BHGbot 6, EaglesBot 2, Cewbot 5, WikiCleanerBot 17 · N2 MDanielsBot, PhuzBot 3, Gedimon · ? PearBOT 7 MajavahBot 3, an impressively meta bot task, was approved this month for maintaining a list of bots running on the English Wikipedia. The page, located at User:MajavahBot/Bot status report, is updated every 24 hours; it contains a list of all accounts with the bot flag, as well as their operator, edit count, last activity date, last edit date, last logged action date, user groups and block status. Other approvals for this month were William Avery Bot 2 (processing redirects in {{R from scientific name}}), DannyS712 bot 68 (allowing users to schedule bot reminders for themselves), TheSandBot 10 (removing blocked/locked users from Category:User talk pages with conflict of interest notices), Bot1058 7 (updating Wikipedia:Requested moves/Technical requests/Permalink), Dreamy Jazz Bot 4 (adding {{WikiProject Biography|living=no}} to talk pages where their associated article is in a year of death category), and QEDKbot (deleting and nominating empty categories). General syntax fixing tasks were approved for DannyS712 bot 70, CitationCleanerBot 5, PrimeBOT 32, BHGbot 6, Cewbot 5, and EaglesBot 2, as well as WikiCleanerBot 15, 16, and 17. Seven bots who fell below activity requirements (with neither the bots nor their operators having any edits or logged actions in two years) had their bot flags removed. They were NekoBot, Robert SkyBot, DASHBotAV, VoxelBot, JackieBot, ReferenceBot, and CensusBot. On May 12, EmausBot was blocked. June 2020 Y QEDKbot 2, AnomieBOT 79, WOSlinkerBot 6, Yapperbot 2, Yapperbot, AnomieBOT 80, Dreamy Jazz Bot 5, WikiCleanerBot 18, HasteurBot 15, MusikBot II 4, NoSandboxesHere · N2 RedWarn · ? Seppi333Bot 2 In July 2017, Headbomb made a proposal that a section of the Wikipedia:Dashboard be devoted to bots and technical issues. In November 2019, Lua code was written superseding Legobot's tasks on that page, and operator Legoktm was asked to stop them so that the new code could be deployed. After no response to pings, a partial-block of Legobot for the dashboard was proposed. Some months later, on June 16, Headbomb said: "A full block serves nothing. A partial block solves all current issues [...] Just fucking do it. It's been 3 years now." The next day, however, Legoktm disabled the task, and the dashboard was successfully refactored. On June 7, RexxS blocked Citation bot for disruptive editing, saying it was "still removing links after request to stop". A couple weeks later, a discussion on the bots noticeboard was opened, saying "it is a widely-used and useful bot, but it has one of the longest block logs for any recently-operating bot on Wikipedia". While its last BRFA approval was in 2011, its code and functionality had changed dramatically since then, and AntiCompositeNumber requested that BAG require a new BRFA. Maintainer AManWithNoPlan responded that most blocks were from years ago (when it lacked a proper test suite), and problems since then had mostly been one-off errors (like a June 2019 incident in which a LTA had "weaponized" the bot to harass editors). David Tornheim opened a discussion about whether bots based on closed-source code should be permitted, and proposed that they not. He cited a recent case in which a maintainer had said "I can only suppose that the code that is available on GitHub is not the actual code that was running on [the bot]". Some disagreed: Naypta said that "I like free software as much as the next person, and I strongly believe that bot operators should make their bot code public, but I don't think it should be that they must do so". Two new bots had their first BRFAs approved: Yapperbot, to replace Legobot for handling the Feedback Request Service, and NoSandboxesHere, to remove {{user sandbox}} from articles in draftspace using Category:Non-userspace pages using User sandbox. Conclusion What's next for our intrepid band of coders, maintainers and approvers? Will Citation bot ever be set free to roam the project? What's the deal with all those book links that InternetArchiveBot is adding to articles? Should we keep using Gerrit for MediaWiki? What if we had a day for bots to make cosmetic edits? These questions will be answered — and new questions raised — by the February 2022 Bots Newsletter. Tune in, or miss out! Signing off... jp×g 23:22, 31 January 2022 (UTC)[reply] (You can subscribe or unsubscribe from future newsletters by adding or removing your name from this list.)

Template:Bigredbox has been nominated for deletion. You are invited to comment on the discussion at the entry on the Templates for discussion page. – Jonesey95 (talk) 04:58, 6 May 2022 (UTC)[reply]

Hello! Voting in the 2022 Arbitration Committee elections is now open until 23:59 (UTC) on Monday, 12 December 2022. All eligible users are allowed to vote. Users with alternate accounts may only vote once.

The Arbitration Committee is the panel of editors responsible for conducting the Wikipedia arbitration process. It has the authority to impose binding solutions to disputes between editors, primarily for serious conduct disputes the community has been unable to resolve. This includes the authority to impose site bans, topic bans, editing restrictions, and other measures needed to maintain our editing environment. The arbitration policy describes the Committee's roles and responsibilities in greater detail.

If you wish to participate in the 2022 election, please review the candidates and submit your choices on the voting page. If you no longer wish to receive these messages, you may add {{NoACEMM}} to your user talk page. MediaWiki message delivery (talk) 00:32, 29 November 2022 (UTC)[reply]

Hello, This, that and the other. It has been over six months since you last edited the Articles for Creation submission or Draft page you started, "Invalid dinosaur".

In accordance with our policy that Wikipedia is not for the indefinite hosting of material deemed unsuitable for the encyclopedia mainspace, the draft has been deleted. When you plan on working on it further and you wish to retrieve it, you can request its undeletion. An administrator will, in most cases, restore the submission so you can continue to work on it.

Thanks for your submission to Wikipedia, and happy editing. Liz ^{Read! Talk!} 16:18, 18 January 2023 (UTC)[reply]

Hey! Would you mind changing User:This, that and the other/sandbox/redirect tags so that it won't be categorized in Pages with templates in the wrong namespace? Thanks! ~ Eejit43 (talk) 03:32, 22 January 2023 (UTC)[reply]

@Eejit43 I have no idea what that page was for, so I marked it for speedy deletion. Thanks! This, that and the other (talk) 03:39, 22 January 2023 (UTC)[reply]

Template:Tutorial sandbox header VE has been nominated for deletion. You are invited to comment on the discussion at the entry on the Templates for discussion page. – Jonesey95 (talk) 15:34, 28 June 2023 (UTC)[reply]

The redirect Mediazilla has been listed at redirects for discussion to determine whether its use and function meets the redirect guidelines. Anyone, including you, is welcome to comment on this redirect at Wikipedia:Redirects for discussion/Log/2023 October 1 § Mediazilla until a consensus is reached. * Pppery * _{it has begun...} 16:01, 1 October 2023 (UTC)[reply]

Hello This, that and the other:

WikiProject Articles for creation is holding a month long Backlog Drive!
The goal of this drive is to reduce the backlog of unreviewed drafts to less than 2 months outstanding reviews from the current 4+ months. Bonus points will be given for reviewing drafts that have been waiting more than 30 days. The drive is running from 1 November 2023 through 30 November 2023.

You may find Category:AfC pending submissions by age or other categories and sorting helpful.

Barnstars will be given out as awards at the end of the drive.

There is a backlog of over 2600 pages, so start reviewing drafts. We're looking forward to your help! MediaWiki message delivery (talk) 13:25, 31 October 2023 (UTC)[reply]

Hello! Voting in the 2023 Arbitration Committee elections is now open until 23:59 (UTC) on Monday, 11 December 2023. All eligible users are allowed to vote. Users with alternate accounts may only vote once.

The Arbitration Committee is the panel of editors responsible for conducting the Wikipedia arbitration process. It has the authority to impose binding solutions to disputes between editors, primarily for serious conduct disputes the community has been unable to resolve. This includes the authority to impose site bans, topic bans, editing restrictions, and other measures needed to maintain our editing environment. The arbitration policy describes the Committee's roles and responsibilities in greater detail.

If you wish to participate in the 2023 election, please review the candidates and submit your choices on the voting page. If you no longer wish to receive these messages, you may add {{NoACEMM}} to your user talk page. MediaWiki message delivery (talk) 00:27, 28 November 2023 (UTC)[reply]