Open main menu

Feel free to leave a comment or greeting at the bottom of this page.


My Talk Archives:
Archive-01 ~ Archive-02 ~ Archive-03
Archive-04 ~ Archive-05 ~ Archive-06
Archive-07 ~ Archive-08 ~ Archive-09
Archive-10 ~ Archive-11 ~ Archive-12
Archive-13 ~ Archive-14 ~ Archive-15
Archive-16 ~ Archive-17 ~ Archive-18
Archive-19 ~ Archive-20 ~ Archive-21
Archive-22 ~ Archive-23 ~ Archive-24
Archive-25 ~ Archive-26 ~ Archive-27
Archive-28 ~ Archive-29 ~ Archive-30
Archive-31 ~ Archive-32 ~ Archive-33
Archive-34 ~ Archive-35 ~ Archive-36
Archive-37 ~ Archive-38 ~ Archive-39
Display all archives (very large)

A barnstar for you!Edit

Vitruvian Barnstar Hires.png The Technical Barnstar
This for your hardworks on enhancing Wikipedia through technical works such as programming, bot building and approving, Village pump, etc. I appreciate your selfless service to the encyclopedia. You are a typical metapedian of our wiki. Thanks for helping others in technical area. Thank you for taking the time for this. Thank you! PATH SLOPU 07:45, 3 June 2019 (UTC)

A barnstar for you!Edit

Administrator Barnstar Hires.png The Admin's Barnstar
I think you deserve a barnstar for Special:Redirect/logid/100058795. ~ ToBeFree (talk) 00:08, 21 June 2019 (UTC)

A barnstar for you!Edit

Barnstar of Diligence Hires.png The Barnstar of Diligence
I was going back through several bot-related discussions, some heated up, some less-so, and it struck me just how consistently reasonable, thoughtful, and well-articulated you were, as an editor, as a BAG member, and as a 'crat.

So here's a barnstar for that, because quality deserves recognition. Headbomb {t · c · p · b} 19:27, 23 June 2019 (UTC)

Inactive adminsEdit

Hi, Xaosflux,

I just noticed that you removed sysop status from some inactive admins. I was just looking at some accounts and came across User:Melchoir who doesn't seem to have done any edits or logged actions in over a year. Did s/he slip through the cracks? I'd love for any inactive admins to come back and be active but I wondered about this admin after looking at their activity. Thanks. Liz Read! Talk! 15:55, 1 August 2019 (UTC)

(tpw) Can't figure this one out... I've left the first note for them. Thank you Liz. –xenotalk 16:50, 1 August 2019 (UTC)
Hi @Xeno and Liz: Melchoir has a logged action from Octoboer 2018. — xaosflux Talk 17:23, 1 August 2019 (UTC)
Ah, doesn't show up in the default "logs" found in the sidebar. Didn't realize thanks counted as activity! –xenotalk 17:30, 1 August 2019 (UTC)
@Xeno: I don't personally think it should, and the policy reads "neither edits nor administrative actions" so I don't think that a "thanks" or a "patrol" would be considered an "administrative action" - but the last time this came up there was decent argument that "any" edit or logged action, even if not publicly available should count to belay inactivity. I'm also in the camp that our inactivity policy is too lax though, but I've accepted that the arguments at the time supported that process. — xaosflux Talk 17:36, 1 August 2019 (UTC)
In fact, the message you left them (templated) even said "any edits or logged actions". — xaosflux Talk 17:38, 1 August 2019 (UTC)
I can't believe a "Thanks" counts as much as an edit or admin action! That seems absurd. But I know you guys follow the guidelines, you don't write them so I'll just file this one as "an example to bring up at the next RfC". Thanks for figuring this one out. Liz Read! Talk! 04:04, 2 August 2019 (UTC)
@Liz: yea its a real edge case for sure, there is a 'resysoping' RfC starting up now - I'd probably wait for that to complete before trying to re-discuss "admin activity requirements" in a new RfC - but if the first one passes it could be a good follow up. — xaosflux Talk 04:30, 2 August 2019 (UTC)

Cincinnati landmark designationEdit

Hi Xaosflux - I wrote the inputs necessary for template:designation. Would you be able to edit it to implement them? I tested it here and it looks good, works well. I have the code to be added, listed out here. Thank you -ɱ (talk) 16:02, 6 August 2019 (UTC)

@: I can't where I am right now, would you please add or reactivate an edit request on the associated talk page to get it in the queue? — xaosflux Talk 17:28, 6 August 2019 (UTC)
Okay, no problem. As soon as you can, that would be very nice, really appreciated. I reactivated the request. ɱ (talk) 20:27, 6 August 2019 (UTC)
Hi - I really don't think anyone's active enough or has the user right to help me on that page, besides you. Could you help me with those brief edits I laid out? Thank you ɱ (talk) 14:08, 14 August 2019 (UTC)
Yeah - mine's the one right at the top. ɱ (talk) 14:11, 14 August 2019 (UTC)
@: yea, sorry saw that right after. OK, so I'm a bit confused on your edit request at Wikipedia_talk:WikiProject_Historic_sites#edittemplateprotected. How many different pages do you need a change to be made on? For each of them, is there a sandboxed version ready to "go-live"? — xaosflux Talk 14:14, 14 August 2019 (UTC)
Yeah adding the designation requires adding bits of code to five separate pages, listed in the request. I have tested it all on sandboxes; the result from those sandboxes is what you can see here: Template:Designation/Supported designations/State. Thanks ɱ (talk) 14:41, 14 August 2019 (UTC)
OK, see my special note there. — xaosflux Talk 15:01, 14 August 2019 (UTC)

What's broken?Edit

Hi SilkTork, noticed you had to do this - can you elaborate on what is broken, as it must be broken for everyone else then? — xaosflux Talk 16:03, 6 August 2019 (UTC)

I can't see the editnotice (Group notice / Page notice) on article space anymore. I wondered if it was me. I found it useful to put in language notices in the page notice, such as at Beer: [1], but now if I go to articles I can't edit page notice anymore - the link is no longer there (unless there is already a page notice, as there is with Beer). See [2], etc. SilkTork (talk) 16:12, 6 August 2019 (UTC)
@SilkTork: hmm - did adding that group actually fix it? (It really shouldn't). Which skin are you using? — xaosflux Talk 17:26, 6 August 2019 (UTC)
Does this link to testwiki show the pagenotice redlink? — xaosflux Talk 17:38, 6 August 2019 (UTC)
Also, are you using the source editor or visual editor? — xaosflux Talk 17:38, 6 August 2019 (UTC)

The testwiki makes no difference for me. I am using MonoBook. I don't use visual editor. Is it just me then? I am wondering if it's something I added to [3]. SilkTork (talk) 18:19, 6 August 2019 (UTC)

@SilkTork: you may have some script collisions going on for sure. Could you try turning off meta:User:SilkTork/global.js and then trying the testwiki link again? — xaosflux Talk 18:24, 6 August 2019 (UTC)

I emptied meta:User:SilkTork/global.js and the testwiki still doesn't show me the page notice. SilkTork (talk) 18:44, 6 August 2019 (UTC)

I've changed browser, changed skin, and emptied User:SilkTork/common.css of the last few changes. Nothing worked. Not even a combination of all those things. So I have restored everything.

You still have the page notice when you go to Wine? SilkTork (talk) 19:03, 6 August 2019 (UTC)

@SilkTork: I'm getting a bit lost on why you are broken! To be sure we are on the same page, you are referring to what would currently be a red link targeting Page notice while editing Wine correct? I do see that. It is normally hidden, but unhidden based on .css in MediaWiki:Group-sysop.css (and also unhidden for certain other groups). You're not blocking certain .css's are by chance? — xaosflux Talk 19:06, 6 August 2019 (UTC)
We are on the same page. So, how would I be blocking certain .css's? Where should I start looking for that? SilkTork (talk) 21:34, 6 August 2019 (UTC) I see the link on your page, and on articles where there is already a page notice, but not on articles which don't already have a page notice, so this is selective. SilkTork (talk) 21:37, 6 August 2019 (UTC)
@SilkTork: if you go to the page and click edit, then view the compiled page source in your browser, do you see any lines including "editnotice-link" ? — xaosflux Talk 21:58, 6 August 2019 (UTC)
If I understand you. I go to Wine. Click edit. Then - in Chrome - I right click on the page and select View page source. And then do a search for "editnotice". I have done that, and "editnotice" wasn't found. I then looked just for "notice", and found 14 instances, including "HideFundraisingNotice". I'm not sure which script does that one. I'll roll back all scripts in SilkTork/common.css, SilkTork/common.js, SilkTork/monobook.css, SilkTork/monobook.js, and SilkTork/vector.js to see if that changes anything. SilkTork (talk) 22:33, 6 August 2019 (UTC)

Well I cleared everything. Then did a complete scrub with PrivacyEraser so the cache and cookies were gone from my PC and browser. Nothing has changed. I still don't see the page notice link. SilkTork (talk) 22:50, 6 August 2019 (UTC)

@SilkTork: OK, I'm at a loss and opened phab:T229986. I was able to replicate the problem on testwiki with an alternate account of mine as well. — xaosflux Talk 00:45, 7 August 2019 (UTC)
@SilkTork: OK, so it wasn't that phab ticket - there was actually something else wrong on testwiki. Can you try it over there now just to see if you are only broken here? — xaosflux Talk 03:22, 8 August 2019 (UTC)
Broken there as well. SilkTork (talk) 09:46, 8 August 2019 (UTC)

So the phab ticket is closed, and I still can't access page notice unless already activated on the article. Where do we go from here? Is this issue just me? I know you managed to create it for yourself, but do other admins have this issue? SilkTork (talk) 03:06, 30 September 2019 (UTC)

@SilkTork: as far as I know, you are the only person with the issue reporting - the phab decline said you may want to follow up at Wikitech-l. — xaosflux Talk 13:58, 30 September 2019 (UTC)

Bots Newsletter, August 2019Edit

Bots Newsletter, August 2019
BAG laurier.svg


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:

  • Nothing of note happened. Just like we like it.

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.

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.


Two new entries feature in the bots dictionary

  • 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.

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
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.

See also the latest discussions at the bot noticeboard.

Thank you! edited by: Headbomb 17:24, 7 August 2019 (UTC)

(You can subscribe or unsubscribe from future newsletters by adding or removing your name from this list.)

Help with Javascript regarding WikiLoveEdit

Hello! :)

Recently we just activated the WikiLove extension in SqWiki. We just finished localizing it but there are two technical details which we'd like to change. We have only two interface admins (I'm one of those) and for the moment being, none of us knows hows to do these changes in the .js page. I thought I'd ask for help in the EnWiki interface admins and since I saw your name in that list and you've helped me in the past... :P Can I write what I need help with here? Or if you don't feel like you're the best person for that, can you tell me who I might write to for it? Thank you in advance! :) - Klein Muçi (talk) 14:17, 13 August 2019 (UTC)

@Klein Muçi: hello, what would you like to change on your wikilove? I just sent you a wikilove on sqwiki to show that it works. — xaosflux Talk 14:43, 13 August 2019 (UTC)
I see you have already started working on it at w:sq:MediaWiki:WikiLove.jsxaosflux Talk 14:45, 13 August 2019 (UTC)
Yes, it does. We only want to change two small technical details, as I said. The first is regarding the template you just used. It's set up with a drop-down menu like with all other types of templates. But, unlike the other cases, this doesn't have subtypes. We tried setting it up as a type without subtypes but then the icon and description disappear. Is there any way to be just like it is only without a drop-down menu?
And secondly, please see the templates at "Medalje komunitetit" called "Medalje gjysmë D" and "Medalje gjysmë M". Those are the Albanian half stars awards. Those are the only templates that have a message form where the user can write, needed to put the name of the collaborator with whom they're sharing the award. We want to make the text (a hint) that appears at the message form disappear when the form is clicked and reappear if nothing was added to it or if it was emptied. How can we do that?
Thank you a lot for your fast replies! :) - Klein Muçi (talk) 14:56, 13 August 2019 (UTC)
@Klein Muçi: I'm getting a little stuck on this, but would you like to try this on testwiki? The changes take about 10mins before they are usable, but you will be able to try without breaking your running wiki. I can add you some temporary access on there if you would like? — xaosflux Talk 16:01, 13 August 2019 (UTC)
Thank you but I'm not sure that would be a good idea. We don't have a very active community so breaking the wiki is not really a problem. I'm just not good enough with the JavaScript syntax and wouldn't know what to do there more than what I'm already doing at SqWiki. Maybe is better than nothing, I'm not sure as I've never used TestWiki before, so if that's the case, then yes, please do grant me access there. Maybe I can make it work by experimenting. But I was hoping more on some help with the coding part. - Klein Muçi (talk) 17:04, 13 August 2019 (UTC)

@Klein Muçi: OK, I'll add you temporary access at testwiki - just clean up your tests when you are done and don't break it too much :D I suggest you follow up at mw:Extension talk:WikiLove or WP:VPT here. — xaosflux Talk 17:19, 13 August 2019 (UTC)

Thank you! :) I'll try asking at WP:VPT. Is there anyone from the list here who you think can help me with it? As far as you know them, I mean. Apart from Cyberpower, I've bothered him quite a lot about IABot lately. XD (And Kaldari, for similar reasons. :P ) As for the TestWiki, maybe I won't be able to deal with it a lot often these two weeks as tomorrow I start my vacations but as soon as I get back, I'll catch up with my wikiwork. :P - Klein Muçi (talk) 17:57, 13 August 2019 (UTC)
@Klein Muçi: all of our IAdmins watch VPT here, looking at the WikiLove project on phabricator does include Kaldari as a project member, though @Quiddity: may be able to direct you to someone that can help with WikiLove specific code quicker. — xaosflux Talk 18:10, 13 August 2019 (UTC)
I see. Okay then. I'll try using the VPT after Quiddity answers. :) - Klein Muçi (talk) 18:46, 13 August 2019 (UTC)
@Klein Muçi: I can only second what Xaosflux suggested, to ask at mw:Extension talk:WikiLove (and I see that you've already edited mw:Extension:WikiLove#Custom_configuration, so thank you for those improvements!). Kaldari is indeed the expert, so you could try pinging him when you write on the extension talkpage there. Hope that helps. Quiddity (talk) 10:37, 14 August 2019 (UTC)
@Quiddity: thank you! :) I've pinged him some days ago about a similar problem but I'm trying one more time. :P @Kaldari: please take a look at the conversation. As I wrote on your talkpage, I've finished working with the extension and we're using it already but there are two technical difficulties we're having with it and I'd need a bit help with the coding regarding them. @Xaosflux: sorry for having this conversation here but I didn't want to start from scratch somewhere else if I wasn't really forced to. :P Hope for your understatement. - Klein Muçi (talk) 14:35, 14 August 2019 (UTC)

@Klein Muçi: it's OK. It looks like even our own local copy of MediaWiki:WikiLove.js has issues (e.g. the "Adding more kitten images" doesn't seem to actually do anything). If you move this to Extension_talk:WikiLove, feel free to copy and paste the entire conversation above for reference. — xaosflux Talk 14:52, 14 August 2019 (UTC)

Yeah, good idea. I'll pass the entire conversation there, regardless if the problems get solved or not, hoping it may help some people in the future. @Kaldari: pinging a second time as the first one had problems and I'm not sure if it succeeded or not. - Klein Muçi (talk) 15:12, 14 August 2019 (UTC)
@Xaosflux: The kitten additions at MediaWiki:WikiLove.js seem to be working fine. Just keep re-clicking the kitten icon until you see one of the new ones show up. Kaldari (talk) 10:20, 15 August 2019 (UTC)
@Klein Muçi: You can add an item without a subitem like this:
$.wikiLoveOptions.types.puppy = {
	name: 'Puppy',
	fields: [ 'header', 'message' ],
	header: 'You get a puppy',
	text: '[[File:2009-08-16 Puppy at Duke East 1.jpg|left|150px]]\n$1\n<br style="clear: both;"/>',
	icon: ''
Kaldari (talk) 13:43, 15 August 2019 (UTC)
Thanks for the responses Kaldari (I see the local kittens working now, they change when you leave and return to the kitten selector). — xaosflux Talk 13:45, 15 August 2019 (UTC)
@Klein Muçi: once you have your changes tested and working, if you have time to add to the documentation (with examples) at mw:Extension:WikiLove#Custom_configuration it would be appreciated! — xaosflux Talk 13:46, 15 August 2019 (UTC)
@Kaldari: I've tried the aforementioned way. It ends up without a description or image at the second step, only showing the "preview" button. To many inexpert eyes, it looks broken like that and they keep pressing the type button to choose it, thinking their command hasn't been registered by the extension. That's why I asked if there's a way to make it without a drop-down menu while showing the description and image of the type. I understand there's not a way for that now so I'll leave it like that. What about the second question regarding the disappearing and reappearing of the text in the message form? If my explanation seems confusing, I'm talking about this: [4] - Random link I searched on Google that seems to pinpoint the subject right. Isn't there a way to make the text in the message form disappear when clicked and reappear if it remains/becomes empty?
@Xaosflux: I've thought about that. The problem is that most of the changes I've made, were made with the trial and error method. :P And, although I can understand what I'm doing, I'm not able to explain it well enough for the others. That's why I set up the Portuguese Wikipedia as an example (since that was the one I copied the code from and started experimenting) and the Albanian one. I was hoping to at least help people with examples, if they ever needed them, or at least, urge some more experienced editors to write some good technical advice from the examples that were added. I think adding this conversation to the talkpage of that page will be a great help too. - Klein Muçi (talk) 23:58, 15 August 2019 (UTC)

Klein Muçi Are you looking to include an input placeholder? This would be best managed as an input field, and not with a javascript hack to add it in. — xaosflux Talk 00:42, 16 August 2019 (UTC)

@Xaosflux: please, try to give me Medalje gjysmë D (found in Medalje komuniteti) with the extension. A form will follow with some text in Albanian on it saying to erase said text and replace it with a user's name. I just want that text to disappear automatically when the form is clicked and then reappear if nothing was written on it. So the one who is using the extension won't need to delete the text manually before writing the user's name. It's a very common thing in website these days. A message with text as a hint appears telling you what to do and disappears immediately as soon as you click on it and start writing (reappearing if the form was left empty again). I thought it would require no more than a line of javascript code and to be honest, I'm a little surprised I'm having difficulties explaining it. :P - Klein Muçi (talk) 01:51, 16 August 2019 (UTC)
@Klein Muçi: As soon as this patch gets merged, the description for stand-alone types will no longer be broken. Getting images to work properly for stand-alone types will be more complicated. There is currently no support for placeholders in WikiLove. Kaldari (talk) 13:36, 16 August 2019 (UTC)
Okay, that finally answers everything I needed then. I didn't know the term I was looking for was "placeholder". I'm coping the entire conversation, including this sentence, to the talkpage of the extension. Thank you to everyone involved! :) - Klein Muçi (talk) 14:56, 16 August 2019 (UTC)
@Klein Muçi: on general purposes web pages, there are other types of page hacks that can accomplish things like that (using script handlers for onfocus/onblur/etc to replace form data) but that's really not something we would want to shim in. @Kaldar: I don't think it would be "hard" to add placehold functionality to WikiLove right - just would take time for a developer to work on it when they wanted to. — xaosflux Talk 15:03, 16 August 2019 (UTC)
@Xaosflux: I understand now. I often work with new users, teaching them how to work around Wikipedia and one of the usual problems that arise is the one related to the general interface of the Wikimedia projects. Many things we take for granted in different famous web pages we use on a day to day basis, work differently on Wikipedia. For the average social media user, the whole project seems a bit too technical sometimes, very crude and old fashioned. Being that many famous web pages use similar interfaces for accomplishing similar things, many new users expect instinctively to find things the same way here and get a bit confused when they don't. For example, many new users try to ping someone the same way they do in other websites, @ + Name, no template brackets or forum words like "ping" used. To help with that, one of the pinging templates at SqWiki is {{@|Name}}. As an admin, I'm always helping on this side of the project and that's why I started working with the WikiLove extension because that would greatly help with our barnstar templates that not many new users know how to award them. Therefore, in my opinion, this placehold functionality would help greatly in many areas of the project since it would give us the ability to use forms with hints when needed, like many web pages do these days. For the moment being, the only way we can give hints is with edit notices and, in some cases, tooltips (and comments but that's a bit too technical for the new users) and they work great but I think that could help much too. - Klein Muçi (talk) 15:32, 16 August 2019 (UTC)

Some baklava for you!Edit

Baklava - Turkish special, 80-ply.JPEG For your continuous help regardless of the topic, a full tray of baklava only for you. - Klein Muçi (talk) 18:21, 13 August 2019 (UTC)

Can you please update the Duggar family page to reflect the changes that have been made?Edit

Can you please update the Duggar family page to reflect the changes that have been made? — Preceding unsigned comment added by 2601:6C0:C201:7E45:F43A:4019:693F:A742 (talk) 19:50, 17 August 2019 (UTC)

Not done no thanks. — xaosflux Talk 23:02, 17 August 2019 (UTC)

Please comment on Wikipedia:Village pump (policy)Edit

The feedback request service is asking for participation in this request for comment on Wikipedia:Village pump (policy). Legobot (talk) 04:33, 19 August 2019 (UTC)

Hi Dear Love YouEdit

give me please admin i am from pakistan — Preceding unsigned comment added by RjFaraz Lahore (talkcontribs) 12:46, 19 August 2019 (UTC)

  • @RjFaraz Lahore: Hi. I am not sure, are you asking for love, or are you asking for admin privileges? —usernamekiran(talk) 13:13, 19 August 2019 (UTC)
Not done see Wikipedia:Not now. — xaosflux Talk 13:16, 19 August 2019 (UTC)
while we are at it, kindly see third point in WP:NOTDATINGSERVICE Face-grin.svgusernamekiran(talk) 14:51, 19 August 2019 (UTC)

Tech News: 2019-34Edit

15:21, 19 August 2019 (UTC)

File:OOjs UI icon edit-ltr-progressive.svg listed for discussionEdit

A file that you uploaded or altered, File:OOjs UI icon edit-ltr-progressive.svg, has been listed at Wikipedia:Files for discussion. Please see the discussion to see why it has been listed (you may have to search for the title of the image to find its entry). Feel free to add your opinion on the matter below the nomination.

This bot DID NOT nominate any file(s) for deletion; please refer to the page history of each individual file for details. Thanks, FastilyBot (talk) 01:02, 21 August 2019 (UTC)

EFH iconEdit

I think I used the wrong file for the Wiki logo. I don't know if it was png or svg. The quality is noticeable when I compare the info box with other user right boxes. I'm a bit picky about this, but I don't want to created a long unnecessary upload history. — JudeccaXIII (talk) 02:33, 22 August 2019 (UTC)

@JudeccaXIII: most userbox icon art is in SVG. — xaosflux Talk 02:38, 22 August 2019 (UTC)

Please comment on Wikipedia talk:Naming conventions (broadcasting)Edit

The feedback request service is asking for participation in this request for comment on Wikipedia talk:Naming conventions (broadcasting). Legobot (talk) 04:28, 26 August 2019 (UTC)

Chet DouglasEdit

Dear xaosflux, please restore the article Chet Douglas, so that the revisions can be imported to de:user:Doc Taxon/Chet because of copyleft attributions. Then the article can be deleted again. Thank you, Doc Taxon (talk) 08:58, 27 August 2019 (UTC)

@Doc Taxon: please let me know when you have finished the export. — xaosflux Talk 09:37, 27 August 2019 (UTC)
 Done and thanks a lot Doc Taxon (talk) 11:16, 27 August 2019 (UTC)
@Sandstein: other admins do such jobs. Learn to administrate! Doc Taxon (talk) 11:16, 27 August 2019 (UTC)
@Doc Taxon: I see you did not "import" in the native sense this to dewiki. While importing the prior version is not needed for copyright purposes, maintaining the authors is. I've placed the authors list at: w:de:Benutzer Diskussion:Doc Taxon/Chet. This should be maintained with the article. — xaosflux Talk 12:59, 27 August 2019 (UTC)
Oh, I imported to de:user:Doc Taxon/Chet2, so all is okay. Thank you again, Doc Taxon (talk) 13:40, 27 August 2019 (UTC)
@Doc Taxon: ah OK! Feel free to delete my manual history paste. Best regards, — xaosflux Talk 13:45, 27 August 2019 (UTC)


You asked me if I have retired this bot. The answer is no, but events in the real world (I have 6 children in, or entering adolescence) have not allowed me time to make contributions on various maintenance activities I took on in prior years. I am reluctant to retire it, as I can imagine scenarios such as friends making requests for assistance on narrow projects where it would be useful. Is that ok with you? If there is some pressing need to retire accounts that do not have immediate requirements for reasons such as heightened security threats against Wikipedia, then of course I would like to understand more. J JMesserly (talk) 20:06, 29 August 2019 (UTC)

Hi @J JMesserly: those notes are semi-automated cleanups that are done from time to time (looks like you got one in 2016 as well). It looks like you haven't used that bot account in over ten years. It is OK policy wise to not deflag it. Should you retire it, you can always have it come back out of retirement with a new WP:BRFA - but no worries. — xaosflux Talk 23:03, 29 August 2019 (UTC)

The Signpost: 30 August 2019Edit

2019 Arbitration Committee pre-election RfCEdit

A request for comment is now open to provide an opportunity to amend the structure, rules, and procedures of the 2019 English Wikipedia Arbitration Committee election and resolve any issues not covered by existing rules. You are receiving this message because you were listed as a user who would like to be notified when the 2019 RfC begins. MediaWiki message delivery (talk) 21:52, 31 August 2019 (UTC)

  • Hi, I find the RfC mightily confusing. My questions:
    • Usually an RfC has a nominator, initiator, whatever. Does this one?
    • I understand I can endorse as many statements as I wish. I don't see that I have the right to oppose? If so, why not?
    • What does this mean: "Users should only edit one summary or view, other than to endorse."
  • I have the feeling this is not an ordinary RfC and that these "statements" are more like recommendations to the current Committee to change their procedures for the upcoming election. Is that true? If not, maybe you could give me the big picture here. Thanks very much.--Bbb23 (talk) 22:27, 3 September 2019 (UTC)
    @Bbb23: Hi there! This isn't a "usual" RfC. One very important response to your points above: the current arbitration committee does not have any special influence on this RfC - and in fact most will abstain from it. The ArbCom elections are very specifically not run by ArbCom, they are run by "the community" - so these become hard rules and are certainly not suggestions that the current committee gets control over. Anyone can volunteer to help "coordinate" the election parts, and there will be a formal commission as well. In general, the arbcom election "rules" are maintained from year-to-year, unless otherwise amended in these annual RfC's. Anyone is welcome to add suggestions to change anything. As for the current structure, I think it is good to eliminate conflict (instead of Point 1, and a list of "support"/"oppose"s; it has Subject: Point 1, Point 2, Point n -- where one of the points can be "don't change from the status quo". Does that help? — xaosflux Talk 23:33, 3 September 2019 (UTC)
    Your explanation about the current Committee helps a lot. But who gets to decide whether the rules should be changed? Some uninvolved administrator determines "consensus" on each point (and then changes the rules)? And, if I understand you properly, if someone says change the # of arbitrators from 13 to 15, rather than oppose the change, someone would have to make their own statement that says don't change the number of arbitrators, and the consensus would have to be determined by comparing the number of endorsers for each statement (I assume with all the qualifiers of this is not a vote)? Seems somewhat cumbersome to me, but that's neither here nor there: I'm just trying to understand how this works. I guess I never paid attention in previous years.--Bbb23 (talk) 23:40, 3 September 2019 (UTC)
    @Bbb23: RfC's don't necessarily require administrators to close, I think there is a "closers" sign up at Wikipedia_talk:Requests_for_comment/Arbitration_Committee_Elections_December_2019#Closers?. As far as "how is consensus determined" - well that's not something unique to this, but it is normally more than strict "vote counting"; as far as putting "don't change thiss subject" in their own sections - it may be less cumbersome when there are many points that one subject could change to (and only 1 where it is "none of the above"). I added one subject to propose a change to, and also added the "don't" section to make this easy. All that being said, there is no strict rules to how the RfC has to run, so if you want to start a new section and format it different I don't think anyone is going to really stop you. For your # of arbitrators type proposal, I think it would be best set up as something like this:
  1. Change the number of Arbitrators from 13 because of foo bar.
    1. Change to 15
      1. Supporters
    2. Leave at 13
      1. Supporters
    3. Change to n
      1. Supporters
    4. Change to m
      1. Supporters
  • That way each additional "to x" wouldn't need an entirely new section, and anyone who said "leave at 13" wouldn't need to revisit each section with a fresh "oppose". — xaosflux Talk 23:55, 3 September 2019 (UTC)
    Thanks for spending so much time explaining this rather novel system. I'm not sure if I'm going to do anything at all, but at least if I do, I'll have a better grasp of what's going on.--Bbb23 (talk) 00:13, 4 September 2019 (UTC)

Please comment on Wikipedia talk:WikiProject TaiwanEdit

The feedback request service is asking for participation in this request for comment on Wikipedia talk:WikiProject Taiwan. Legobot (talk) 04:31, 1 September 2019 (UTC)

Tech News: 2019-36Edit

09:07, 4 September 2019 (UTC)

Administrators' newsletter – September 2019Edit

News and updates for administrators from the past month (August 2019).


Administrator changes

added BradvChetsfordIzno
readded FloquenbeamLectonar
removed DESiegelJake WartenbergRjanagTopbanana

CheckUser changes

removed CallaneccLFaraoneThere'sNoTime

Oversight changes

removed CallaneccFoxHJ MitchellLFaraoneThere'sNoTime

Technical news

  • Editors using the mobile website on Wikipedia can opt-in to new advanced features via your settings page. This will give access to more interface links, special pages, and tools.
  • The advanced version of the edit review pages (recent changes, watchlist, and related changes) now includes two new filters. These filters are for "All contents" and "All discussions". They will filter the view to just those namespaces.



Sent by MediaWiki message delivery (talk) 00:37, 7 September 2019 (UTC)

Please comment on Talk:List of the Cenozoic life of Washington (state)Edit

The feedback request service is asking for participation in this request for comment on Talk:List of the Cenozoic life of Washington (state). Legobot (talk) 04:28, 8 September 2019 (UTC)

Help with mass editingEdit

Hello, Xaosflux! I need advice on something related to mass editing.

At my home wiki we're talking about changing some hundreds (if not thousands) articles "at once". Consulting with a dictionary, we found out we've been writing the Albanian term for "References" wrong and we may need to fix it. SqWiki has more than 70 thousand articles at the moment speaking and most of them may require fixing. What may be the best way to achieve this? I tried using JWB but, as far as I saw, I couldn't generate a list of all the articles in the Mainspace (I could only generate category lists, not namespace lists) but maybe I'm wrong. Even if it is possible, the problem with JWB is that it would require me to accept every single change made manually and that thing could be a bit tedious. I've never used AWB before so I don't know if that would be a better way to address it. (JWB has been easier to use and has helped get the job done so I've never bothered to download anything to start using AWB.) I was thinking of having a bot making the change but the problem is that I'm very inexperienced with bots and we don't really have any active bots in the community now (besides IABot and Listeria) so I have none to ask for help from SqWiki in that direction. Any idea of what would be the best approach of solving this? - Klein Muçi (talk) 12:17, 9 September 2019 (UTC)

@Klein Muçi: for a task that large, you may want to deal with custom scripting. You could do this with AWB as well. On sqwiki, bot registration is required, as well as AWB registration. See w:sq:Wikipedia:Botët and w:sq:Wikipedia:AutoWikiBrowser/CheckPage. There is no way to make all the edits "at once" unless they are all from a tempalte, even bot processes work as "one edit at a time". For a huge page run, one method is to download the text dump of your entire project, run a scan on that, and use it to generate the list of the pages you would want to edit; then you could feed that list to a program like AWB or a custom script. — xaosflux Talk 12:46, 9 September 2019 (UTC)
I already knew how bots processed work (that's why I used quotation marks :P ) but I'm a bit more clear about the whole situation in general now. So I must do the scan manually/with a third party application? I was hoping of being able to generate the list automatically from AWB or maybe "borrow" one bot from EnWiki. I'm not sure I can find someone on our community to write a custom script for that. :/
To make myself more clear, we only need to do this change: == Referenca == -> == Referime ==
So all in all, we need a program that scans every article in Mainspace and if it finds one with the text "== Referenca =="" changes it to "== Referime ==". - Klein Muçi (talk) 13:14, 9 September 2019 (UTC)
@Klein Muçi: the AWB application contains a database scanner, see Wikipedia:AutoWikiBrowser/Database Scanner for information; and you can get a database dump here. — xaosflux Talk 13:34, 9 September 2019 (UTC)
Okay, I'll try using AWB for the whole task then. Thank you! :) - Klein Muçi (talk) 14:57, 9 September 2019 (UTC)

I downloaded AWB and tried using it but I can't log in. :/ I have 2FA enabled. I followed all the instructions about it regarding the bot password but at the end it says I'm not enabled to use AWB because my name is not on the list of EnWiki enabled names. I don't want to use it on EnWiki and I am already on the enabled users list on SqWiki (although I'm an admin there and normally I don't need to be at the list at all). How do I tell AWB I want to use it on SqWiki, not EnWiki? Or is the bot password thing only allowed on EnWiki and you can't log in on other languages if you have 2FA enabled? - Klein Muçi (talk) 02:02, 11 September 2019 (UTC)

@Klein Muçi: (I saw you reverted this but just wanted to make sure it was a clear answer!). If you have 2FA enabled, it is global on your account. To use AWB you will need to use a PER-PROJECT Special:BotPasswords. Some projects require AWB users to be registered on a local check page. Finally, normally to enable "bot" mode on AWB you should be logged in with an account that has the "bot" usergroup/flag on it. Hope that helps! — xaosflux Talk 03:12, 11 September 2019 (UTC)
Yes, I fixed it. I'm working with it right now. Thank you a lot for your help! :) - Klein Muçi (talk) 10:47, 11 September 2019 (UTC)

Actions while blockedEdit

I didn't mention anything that wasn't discussed in the remove-unblockself discussion :-) I can imagine other things that are possible, but I know I shouldn't mention them, in case they do work. My point was that you can't perform any blocking/unblocking except the scenarios I mentioned. Nyttend (talk) 01:19, 12 September 2019 (UTC)

Bots without flagsEdit

I think I'm being dense and just missing something, but what are the general thoughts/rules regarding bots without a bot flag? Example, User A wants to run ABot on AWB, but is running fully-supervised tasks. To me it wouldn't make sense to grant the bot flag (since it's basically a glorified AWB-specific alt account) but giving it a flag means people won't be crying for it to be blocked. I say that I'm missing something because I have this feeling that {{bot}} (or WP:BOT) mentions this case, but I don't remember where. Primefac (talk) 19:23, 12 September 2019 (UTC) (please ping on reply)

@Primefac: last I checked, AWB doesn't have an option to assert or not assert a bot flag on each edit, if you have bot access it always does and if you don't well it can't. That being said, it would be the same as any other bot framework - so fully automated tasks of any magnitude should be flagged, as they should be running under an approved BRFA task and not flooding watchlists or recent changes. To the larger question, any bot that may ever need to make use of bot permissions should have the bot flag, and any edits that don't require higher scrutiny (as determined by way of getting a BRFA task approved) should assert that flag on edits. If someone were going to run an AWB framework bot that for some reason needed to not flag its edits as bot (e.g. a Report Publishing Bot that would WANT to be seen on watchlists) it would be a reason to not flag it. Does that help? — xaosflux Talk 19:31, 12 September 2019 (UTC)
Sort of. I guess to get more specific I'm wondering about this BRFA, wherein a fully-supervised task for a not-yet-approved bot has been proposed; I suggested just using an "AWB-exclusive" account, but they said they wanted to use the bot-named account. As a bot this falls afoul of CONTEXTBOT, but as a supervised edit it's fine; do we approve a "bad" BRFA for a bot and AGF the creator won't go fully-auto, or do we approve the BRFA and not assign the bot flag, or do we make them create a new "AWB" account?
If you think we've moved to the point where a broader discussion is needed, feel free to move this to the appropriate venue. Primefac (talk) 21:41, 12 September 2019 (UTC)
@Primefac: regarding that specific BRFA: it is for "thousands" of article edits so the primary factors are: (the usual) is there community support that if these thousands of edits were made by editors they are fine? As for questions about flagging, prime points would be: (a) what is the edit rate (i.e. is there going to be a recent changes or watchlist flooding?) and (b) do these edits warrant usual BRD type scrutiny?

So based on that I'd say:

  1. If (a) is fairly low and (b) is yes - it can be an unflagged not-quite-a-bot and use xWB.
  2. If (a) is fairly low and (b) is no - it can be an unflagged not-quite-a-bot and use xWB, or be flagged.
  3. If (a) is high and (b) is no, it should be flagged.
  4. If (a) is high and (b) is yes, it should be denied as-is.
Does that help? — xaosflux Talk 23:02, 12 September 2019 (UTC)
It does, ta. Primefac (talk) 23:50, 12 September 2019 (UTC)

Please comment on Talk:SturmabteilungEdit

The feedback request service is asking for participation in this request for comment on Talk:Sturmabteilung. Legobot (talk) 04:34, 14 September 2019 (UTC)

Please comment on Talk:Democrat PartyEdit

The feedback request service is asking for participation in this request for comment on Talk:Democrat Party. Legobot (talk) 04:27, 21 September 2019 (UTC)

You've got mail!Edit

Hello, Xaosflux. Please check your email; you've got mail!
Message added 15:50, 21 September 2019 (UTC). It may take a few minutes from the time the email is sent for it to show up in your inbox. You can remove this notice at any time by removing the {{You've got mail}} or {{ygm}} template.

MusikAnimal talk 15:50, 21 September 2019 (UTC)

Unbundling edit-protectEdit

Moved to User_talk:Vanamonde93/Main_page_protector#Unbundling_edit-protect

Hi Xaosflux. Valereee and myself are planning to propose the creation of a new userright to allow main page regulars to work on main page content while it is protected. I know you've participated in some related discussions before (I know we had a conversation about it, though I cannot now find it); would you be interested in collaborating? Also (and irrespective of your answer to the above) would you help me understand your comment at this discussion, where you listed the rights that would have to be unbundled? I was under the impression it was only edit-protected and and protect; am I wrong about that? Best, Vanamonde (Talk) 19:11, 25 September 2019 (UTC)

@Vanamonde93: this is certainly something that you should workshop up before throwing to the wolves at VPP! I'd be open to consulting on it, in general I'm open to unbundling (though it's not really UN bundling, it is just creating an additional lesser-included group - you are not really trying to remove access from admins). There are several technical hurdles that would need to be dealt with depending on how you want to go about accomplishing the change. Once those are determined, there will be the usual pile of "community" hurdles, but all good things in time. So first things first: our main page is "cascade protected", which means it has "full protection" and anything transcluded on it (including nested transclusions) is also protected. A side affect of this is that you can add protection to any page by adding them to a transclusion. From a pure mediawiki perspective, there is one primary "permission" that allows this type of editing right now: (protect) which allows access to Change protection levels and edit cascade-protected pages. At the very least this would require developers to create a new permission such as "(editcascadeprotected)". Then a group could be used to assign both the existing "editprotected" and this new permission - allowing people to edit all those pages. It would also allow editing of things such as a protected template that was used in a system message (which normally required editinterface) so we'd have to at the least decide on what the "rules" were and accept that risk that someone could break the rules. Depending on what "rules" we make and how you want to go about implementing this I may be more or less supportive - but I'm still generally supportive of letting the proposal get a fair chance to be evaluated by the community at large. There are also a couple of "cheap" (in terms of developer time) ways to do this, though they have their own risks and may not get much community support:
  1. Lower main page protection, at least by uncascading protecting it and using less protected transclusions for primary "content" sections controlled with existing groups (e.g. templateeditor or extendedconfirmed). This is how the Romanian Wikipedia (rowiki) does it for example.
  2. Allow for "limited admins". This would give people access to the full admin tool set, but they would have a rule that "limits" them to specific things, breaking the rule could result in loss of access or other sanctions. This is an option at meta-wiki for example (c.f. meta:Meta:Requests_for_adminship#Other_access).
  3. Create a new usergroup that adds existing mediawiki permissions of (protect) and (editprotected), along with rules for what they may be used for. (Like limited admin above, but with more tech controls - this is a very minor tech change unlikely to get developer pushback). Rules could be like "you may not use action=protect", "you may not edit pages transcluded to mediawiki space", etc. Such a group could possibly be used to do normal protected editing, such as processing approved edit requests on articles - or not, depending on what rules you want to use.
Does that help? — xaosflux Talk 19:55, 25 September 2019 (UTC)
Ping also to Valereee. — xaosflux Talk 19:55, 25 September 2019 (UTC)
@Xaosflux: yes, that's very helpful, thank you. I'm glad to see my technically ignorant self was not entirely wrong on most of it. My intent was to follow option 3. Option 1 has been shot down before, and has people yelling "security!". Option 2 is possible, but it a) seems complex and b) is going to give access to viewing deleted content, which isn't logged, and therefore cannot be monitored, and which the WMF won't give out without an RFA-like process, and so cannot be handed out without such a process without I think it's less likely to get anywhere. If it's okay with you, I will copy this discussion over to the user subpage I just made, so we can continue discussion in a single location. Vanamonde (Talk) 20:01, 25 September 2019 (UTC)
@Vanamonde93: oh sure that's fine. Option 3 above is about as easy to do as creating some of the other more recent groups such as extendedmover and Wikipedia_talk:Page_mover/Archive_1#RFC_-_Proposed:_"Page_mover"_permission_to_be_created is a fairly decent framework you may be able to reuse. It is a good idea to start with a clear definition of the problem, and a proposed technical solution - possibly even ruling out why other not-yet-existing tech solutions are not a good idea. Leaving a lot of the "rules" open to comment helps encourage people to contribute (e.g. the "criteria for granting", "criteria for revoking" sections). As well as if you want it to "be more" (e.g. not just limit it to one problem). — xaosflux Talk 20:08, 25 September 2019 (UTC)

Please comment on Wikipedia talk:Manual of StyleEdit

The feedback request service is asking for participation in this request for comment on Wikipedia talk:Manual of Style. Legobot (talk) 04:28, 27 September 2019 (UTC)

Welcome botEdit

Hello, Xaosflux! :)

I've recently wrote to Enterprisey for the same subject but didn't get any response by him and I thought I could try asking you since you've always helped me with the problems I've had in the past. Since I don't wanna bother you too much, long story short is that we need a welcome bot at our community in SqWiki to be able to use WikiLove. I was searching how to make one on Google but all I could find was past discussions on EnWiki Bot Approval Group how you've always voted against them and no other help on how to create one. :P The situation is different on our community. Can you help me with that in any way? If you want to read a bit more thoroughly about what I'm saying, please read the original request on Enterprisey's talk page here. Also feel free to ask me about any other details you might need info on. - Klein Muçi (talk) 15:37, 29 September 2019 (UTC)

@Klein Muçi: wikilove and "welcome bots" shouldn't be dependent on each other, though they could be used in coordination. Depending on your goals you would need to write a bot to read the new user creation log, and then send talk messages; if you want it to happen right away the bot would need to always be running - so you would need somewhere to host it. I suggest you talk to someone that is running a welcome bot somewhere for some background. A quick search shows w:it:Utente:GnuBotmarcoo running on itwiki by w:it:Utente:.avgas. — xaosflux Talk 16:17, 29 September 2019 (UTC)
Now that I think of it, maybe we don't need it to use WikiLove. We use the extension to easily give the template manually but the bot can just put {{Tung}} (the welcoming template in our community) automatically without any help needed from the extension. I was also going to ask about the time thing. I've always wondered how is it possible that some bots run all the time and are run by different people simultaneously. Apparently you've answered that too. Do you think I should ask him for help on how to create a new bot dedicated to our community or just to lend us their bot? Also, on a side note, since bots are an integral part of Wikipedia work these days, don't you think we should have some information somewhere on how to run one? Or some scripts readily made for the most wanted types of bots? Like, the welcoming one, maybe one to fight common vandalism and stuff like that? I've learned many things regarding the extensions and gadgets by seeing the code behind them on other projects or reading help pages dedicated to them. With bots that is impossible. :/ - Klein Muçi (talk) 16:47, 29 September 2019 (UTC)
@Klein Muçi: for the most part "bots" are not part of core functionality - they are aids for individual users. Some bot operators choose to publish their bot code, some don't. Some very common functions have been rolled in to core or extensions though - for example "welcomes" have an integrated pop-up at certain milestone edits. Additionally the mw:Extension:NewUserMessage extension is available and may be what is best for sqwiki since you don't have a large bot operator collective. You can request it at phabricator, see phab:T209432 for an example of it being enabled at tcywiki. Anti-vandalism is also being improved with mw:ORES across projects. — xaosflux Talk 17:23, 29 September 2019 (UTC)
I understand but so is the case with gadgets and they are treated with way more "respect" than bots. :P I'm not saying to force people to publish their code but it would be nice to have some help pages describing the most common details about bot operating (like hosting and stuff) and some information about Python or PHP basic scripts. Somewhere "to grab" if you want to start learning how to deal with them. That would help a lot of people that don't come with programming backgrounds (like me). Also there are many times that, like gadgets, many bots evolve beyond aiding only individual users. Like IA Bot, Sinebot or Listeria Bot. Making the technical side more accessible to the common public would increase the number of cases like these. Again, not talking here about making their specific code public.
The extension you mention does indeed look like a better option than having a bot for that. It's exactly what I was searching for. I'll make a request at the Phabricator. Thank you! :) I'm sorry I always bother you with my requests but I've tried asking other people and my attempts haven't been very successful, as you've seen. :P Thank you again! :) - Klein Muçi (talk) 02:33, 30 September 2019 (UTC)
Question: Is there any extension that does the same job as the SineBot? Some days ago I wrote to its creator to make the bot work in our community too but since you gave me a better solution in the welcoming situation, I was wondering... - Klein Muçi (talk) 04:53, 1 October 2019 (UTC)
@Klein Muçi: none that I know of, well I suppose mw:Structured Discussions - but that isn't available for any more testing right now and has been known to be very contentious with certain editing communities. — xaosflux Talk 11:32, 1 October 2019 (UTC)

I see... Well, let's hope Slakr answers my post then. :P Thank you! :) - Klein Muçi (talk) 12:50, 1 October 2019 (UTC)

@Klein Muçi: keep in mind that effectively running a "missed signature bot" requires a lot of resources (much more than a "welcome bot", not as much as a "vandalism bot") because it has to review every single edit (at least to certain namespaces), and to be useful needs to do it fairly quickly - not to mention continuously. — xaosflux Talk 13:26, 1 October 2019 (UTC)
I understand. I was hoping to not run it myself, to be honest. Maybe something similar with SuggestBot and IA Bot could be done with it. - Klein Muçi (talk) 13:35, 1 October 2019 (UTC)
So that leaves you with a few directional options to chase:
  1. Try to get an extension made for something you want
  2. Try to get the meta:Community Tech team to do it
  3. Encourage bot operators to step forward from your community
  4. Try to get other communities to do it for you
Of those, 1 and 2 are slow processes, but may result in a solution (like the welcome extension I mentioned above) - a good way to engage these groups is via the annual meta:Community Wishlist Survey 2019 (the 2020 will get advertised around when it is coming out). #3 requires people, commitment, and resources; #4 is a "good luck" situation, you might get someone from somewhere to help out, but they could always stop abruptly in the future. Best wishes, — xaosflux Talk 13:41, 1 October 2019 (UTC)
I like the idea of asking for an extension. It's not a big deal on our community so we can wait for it and it may offer as a definitive solution. How do I do it? I ask at the Phabricator? - Klein Muçi (talk) 14:16, 1 October 2019 (UTC)
Best way to get traction: put it on the next wishlist survey and lobby for people to support it. — xaosflux Talk 14:20, 1 October 2019 (UTC)

Shouldn't a phab-task be an easier and faster way? Just asking. I'm not much familiar with Phabricator. - Klein Muçi (talk) 16:14, 1 October 2019 (UTC) @Klein Muçi: you're welcome to make a "feature request" as a phabricator task but it probably won't go anywhere - it is literally asking for some unknown person to invent something. Having a task, and getting support at the wishlist survey are good idea, but like I said they are not quick. Using a phab task to do things like "add approved extension to our project" or "tweak thing thing" or "x is a bug" are usually quicker turn-arounds. — xaosflux Talk 17:10, 1 October 2019 (UTC)

I understand now. Okay then. I'll be on the lookout for the wishlist survey. :P Thank you, as always. - Klein Muçi (talk) 18:09, 1 October 2019 (UTC)

The Signpost: 30 September 2019Edit

Tech News: 2019-40Edit

16:51, 30 September 2019 (UTC)

Administrators' newsletter – October 2019Edit

News and updates for administrators from the past month (September 2019).

Guideline and policy news

  • Following a discussion, a new criterion for speedy category renaming was added: C2F: One eponymous article, which applies if the category contains only an eponymous article or media file, provided that the category has not otherwise been emptied shortly before the nomination. The default outcome is an upmerge to the parent categories.

Technical news

  • As previously noted, tighter password requirements for Administrators were put in place last year. Wikipedia should now alert you if your password is less than 10 characters long and thus too short.



  • The Community Tech team has been working on a system for temporarily watching pages, and welcomes feedback.

Sent by MediaWiki message delivery (talk) 11:55, 2 October 2019 (UTC)

Please comment on Wikipedia talk:Template editorEdit

The feedback request service is asking for participation in this request for comment on Wikipedia talk:Template editor. Legobot (talk) 04:29, 3 October 2019 (UTC)

Tech News: 2019-41Edit

15:36, 7 October 2019 (UTC)

Please comment on Wikipedia talk:Requests for permissionsEdit

The feedback request service is asking for participation in this request for comment on Wikipedia talk:Requests for permissions. Legobot (talk) 04:29, 9 October 2019 (UTC)

Precious anniversaryEdit

Cornflower blue Yogo sapphire.jpg
Five years!

--Gerda Arendt (talk) 07:17, 10 October 2019 (UTC)

2019 CheckUser and Oversight appointments: Candidates appointedEdit

The Arbitration Committee is pleased to welcome the following editors to the functionary team:

The Committee thanks the community and all candidates for helping to bring this process to a successful conclusion.

The Committee also welcomes the following user back to the functionary team:

The Committee also thanks Timotheus Canens (talk · contribs · deleted contribs · logs · edit filter log · block user · block log) for his long history of contributions to the functionary team. Timotheus Canens voluntarily resigned his CheckUser and Oversight permissions in September 2019.

For the Arbitration Committee,

Katietalk 15:47, 14 October 2019 (UTC)

Discuss this at: Wikipedia talk:Arbitration Committee/Noticeboard#2019 CheckUser and Oversight appointments: Candidates appointed
  • Nice. –xenotalk 15:51, 14 October 2019 (UTC)

Tech News: 2019-42Edit

23:55, 14 October 2019 (UTC)

Please comment on Wikipedia talk:Manual of Style/Capital lettersEdit

The feedback request service is asking for participation in this request for comment on Wikipedia talk:Manual of Style/Capital letters. Legobot (talk) 04:31, 15 October 2019 (UTC)

Happy First Edit Day!Edit

Balloons-aj.svg Hey, Xaosflux. I'd like to wish you a wonderful First Edit Day on behalf of the Wikipedia Birthday Committee!
Have a great day!
PATH SLOPU 15:31, 15 October 2019 (UTC)

Happy First Edit Day!Edit

Return to the user page of "Xaosflux".