User talk:Alexis Jazz/Archives/2022

About zhihu.com

I don't know what you think about zhihu.com, but it is a website similar to wiki or Q&A. I personally don't think this type of website is reliable.Although zhihu.com seems to have added other features, I can be sure that https://www.zhihu.com/question/19734059 you restored is a Q&A page. The /question/ has been marked in the URL. Rastinition (talk) 16:34, 1 January 2022 (UTC)

[1] Rastinition, I don't understand Chinese and can't navigate the site very well. Zhihu was the only one I couldn't quickly figure out. What mostly matters there is who answered the question. If it's just answered by a random person (like Quora most of the time), you were right in removing it. If it was answered by a developer who worked on the font or with a relation to those who did, it could be useful. If you believe it was answered by someone with no relation to the font developers I have no objection to the removal of the zhihu.com link. — Alexis Jazz (talk or ping me) 16:58, 1 January 2022 (UTC)

Media Viewer

Thank you so much. I kind of hate to be difficult here, but the more I dig, the worse it gets. Hell, I just remembered that I have CC-licensed some of my work in the past... and then found this:

https://en.wikipedia.org/wiki/Battle_of_Spotsylvania_Court_House#/media/File:Battle_of_Spottsylvania_by_Thure_de_Thulstrup.jpg

Compare MediaViewer's read of the copyright status and attribution of that with File:Battle_of_Spottsylvania_by_Thure_de_Thulstrup.jpg.

I don't want to make a huge fuss over this, and, honestly, I'm half inclined to relicense that to a simple Attribution, since I think CC-by is honestly a bit more strict than I'd like. But I spent literal weeks on that, and Britain gives out copyright like candy, and that's just... blatant.

I'm happy to wait, but it's been 8 years at this point, and I'm kind of losing hope. Adam Cuerden ^(talk)_{Has about 7.5% of all FPs} 18:26, 16 January 2022 (UTC)

Adam Cuerden, thanks. I won't lead you on, either I'm unable to fix it and will inform you of that soon (bug me if I forget!) or there will be a proposal fairly soon. (think weeks, not years) My question I asked on phab:T68606 still stands though: if you use a pipe symbol or {{!}} instead of a new line, what happens? — Alexis Jazz (talk or ping me) 19:38, 16 January 2022 (UTC)

I tried this with File:Esther_Bubley_-_An_instructor_of_the_Capitol_Transit_Company_teaching_a_woman_to_operate_a_one-man_streetcar.jpg https://en.wikipedia.org/wiki/American_women_in_World_War_II#/media/File:Esther_Bubley_-_An_instructor_of_the_Capitol_Transit_Company_teaching_a_woman_to_operate_a_one-man_streetcar.jpg - I'm not seeing any change in behaviour, but feel free to use that for testing. Adam Cuerden ^(talk)_{Has about 7.5% of all FPs} 20:15, 16 January 2022 (UTC)

Adam Cuerden, I see. On File:Mathew B. Brady - William Sidney Mount.jpg the restoration had it's own bullet point, on Esther Bubley it doesn't, so newline or not makes no difference for MediaViewer. I figured maybe MV was simply chopping off everything after the first line, I actually can't rule out yet whether or not it does, but it's not that simple. Leave it like this anyway, variations are always useful for testing. — Alexis Jazz (talk or ping me) 21:43, 16 January 2022 (UTC)

https://en.wikipedia.org/wiki/Charles_O%27Conor_(American_politician)#/media/File%3ACharles_OConor_-_Brady-Handy.jpg might be a good test case as well. A simple two-creator file. Adam Cuerden ^(talk)_{Has about 7.5% of all FPs} 23:57, 17 January 2022 (UTC)

Adam Cuerden, here's a.. proof of concept? User:Alexis Jazz/MVattrib. Let me know what you think. Takes a moment to load because it just waits for a second before doing anything as otherwise the elements don't exist yet. (this can be much improved, it's a proof of concept) This isn't exactly the optimal solution, but the only thing Wikimedia/MediaWiki developers are really interested in is structured data. Unfortunately they cocked up the implementation, resulting in massive duplication of license information. I'm not sure if it's even possible yet to transclude information from structured data in wikitext (I've given up hope a long time ago so I don't keep track), but right now anyway the license information in wikitext is leading. Being license compliant should be top priority for them, but, sigh, what did I expect.
One thing though: I'm not sure I'll be comfortable creating a proposal. I've been shat on sufficiently for this month and probably the next as well. — Alexis Jazz (talk or ping me) 10:20, 23 January 2022 (UTC)

Adam Cuerden, in case it wasn't clear, the shitting is entirely unrelated to you. It's just stuff that happens and it drains my energy. You don't need me to create a proposal anyway. Any comment on the script? — Alexis Jazz (talk or ping me) 04:09, 24 January 2022 (UTC)

Afraid I've not had a chance yet - been a funny two days - but I will ASAP. I hope things improve. Commons can be...odd. Adam Cuerden ^(talk)_{Has about 7.5% of all FPs} 16:17, 24 January 2022 (UTC)

Adam Cuerden, no need to self-censor for me. A Commons admin accused me of making death threats, which they fabricated. I doubt you can surprise me. — Alexis Jazz (talk or ping me) 23:53, 24 January 2022 (UTC)

Been barely functional due to sleep issues. Kinda prone to it. Adam Cuerden ^(talk)_{Has about 7.5% of all FPs} 01:10, 26 January 2022 (UTC)

Adam Cuerden, I can relate. Also, I added a screenshot to User:Alexis Jazz/MVattrib. — Alexis Jazz (talk or ping me) 01:03, 8 February 2022 (UTC)

It looks pretty decent, now that I've checked. Probably could figure out what we could leave out or keep in from there, but it's hardly the "Unfunctional mess" that was being claimed. Adam Cuerden ^(talk)_{Has about 7.6% of all FPs} 04:14, 8 February 2022 (UTC)

Signpost newsroom reset

Regarding this, it should be OK – I follow the instructions in the comment that includes the text RESETTING. In other words, only the status table starting after the commented section is reset after publication. Sometimes another editor does the reset, and they should be following the same instructions. ☆ Bri (talk) 18:43, 1 February 2022 (UTC)

• Bri, Wikipedia:Wikipedia Signpost/Newsroom (diff 1041810600)? — Alexis Jazz (talk or ping me) 18:53, 1 February 2022 (UTC)
  • You're right. It looks like we had some reset issues in 2H2021, maybe due to rotation of publication managers. Not sure why I did it that way anymore. ☆ Bri (talk) 19:00, 1 February 2022 (UTC)

File:The Avenger (1937 film).jpg

Hello Jazz, in instances like this, please address the requestor, not me. Thanx, - FlightTime (open channel) 23:33, 7 February 2022 (UTC)

• FlightTime, I addressed both, but as a file mover, you're supposed to check requests for validity. It's okay you missed one, happens to the best of us, but I figure you'd want to know if/when you miss one, don't you? — Alexis Jazz (talk or ping me) 00:59, 8 February 2022 (UTC)

Hey Sorry for being a little snappy above, bad day I guess and just wanted to say nice research on on the Gatorade file, keep up the good work. Cheers, - FlightTime (open channel) 18:05, 12 February 2022 (UTC)

Please see

Can File:Shyamoupti Mudly.jpeg be allowed on local English Wikipedia upload as the file could be adequately covered by a free-license via Commons (for example taking the photograph of the actress). Please have a look. If this continues, then all will bypass rules and upload copyright images. 42.106.249.159 (talk) 18:13, 9 March 2022 (UTC)

• 42.106.249.159, if you have an account with some edits you can log in and enable Twinkle to nominate the file for deletion. You can also do it without Twinkle but it's more complicated: Wikipedia:Files for discussion#instructions. You could also ask User:Shinnosuke15 directly why they think the image meets WP:NFCC as I doubt they uploaded the image in bad faith. — Alexis Jazz (talk or ping me) 19:15, 9 March 2022 (UTC)

  I also feel that the upload was not done in bad faith, but in this way User:Shinnosuke15 or others will upload copyright images of all living people in articles misusing WP:NFCC policy. WP:NFCC is used for logos, TV & Film posters only. 42.106.249.159 (talk) 19:48, 9 March 2022 (UTC)

  I have tagged the image with {{di-replaceable non-free use}} 42.106.249.159 (talk) 19:55, 9 March 2022 (UTC)

  42.106.249.159, that seems like an appropriate tag. Btw, there are a few additional cases where non-free content is allowed, like collapsed structures, one-time events that have passed, people who passed away and people/groups whose looks played a role in their notability and who no longer look like they did when they were doing what made them notable. — Alexis Jazz (talk or ping me) 20:21, 9 March 2022 (UTC)

  I agree but none of the ones you mentioned applies here for the image in question 42.106.249.218 (talk) 20:39, 9 March 2022 (UTC)

I found the picture in a news article. Can it be uploaded in commons? If not, it can be deleted. Shinnosuke15, 06:50, 10 March 2022 (UTC)

Shinnosuke15, no. Commons only accepts freely licensed files. On Wikipedia non-free files require a non-free rationale, which when the subject is a person is most commonly that the person is deceased so no new picture can be taken. From what I can tell Shyamoupti Mudly is alive. Is she one of the presenters in https://www.youtube.com/watch?v=_XkcHxSrwqw ? That video has a free license, I could take a screenshot from it. (or you could, either way it would be easier if the whole video was uploaded if it's useful) The video description isn't clear but YouTube search gave me that video when I looked for her name. — Alexis Jazz (talk or ping me) 09:50, 10 March 2022 (UTC)

She is not Shyamoupti Mudly. She is actually Ishita Mukherjee, she says at the end of the video that she will play the character of Dipanwita in Alo Chhaya. The show had ended now and I have crossed checked it. 42.106.217.86 (talk) 12:16, 10 March 2022 (UTC)

42.106.217.86, thank you, no idea why YouTube search returned that video in that case as her name doesn't seem to be in the description or comments and the video has no subtitles. Actually, who exactly? The closest name I see in Alo Chhaya is Ipshita Mukherjee. Could an image of her be useful for any article? — Alexis Jazz (talk or ping me) 15:05, 10 March 2022 (UTC)

Sorry for the spelling mistake. Yes, its Ipshita Mukherjee. I don't think its useful anywhere since the actress don't have any Wikipedia article. 42.106.217.86 (talk) 15:35, 10 March 2022 (UTC)

42.106.217.86, if she played a main character in a production that has a Wikipedia article, perhaps it could be used there. I don't know if she has, though. Oh well, I uploaded it anyway: File:Ipshita Mukherjee XkcHxSrwqw 5.46.jpg. — Alexis Jazz (talk or ping me) 15:49, 10 March 2022 (UTC)

👍👍👍 42.106.217.86 (talk) 17:33, 10 March 2022 (UTC)

Hey Jazz

I'm betting you understand what's going on here Category:Wikipedia files requiring renaming, Looks like a loose bot or something, so many files. - FlightTime (open channel) 04:54, 11 March 2022 (UTC)

FlightTime, I do indeed.. I saw a few of these requests some days ago. This is about files that have a local description page (typically a DYK notice or similar) that were moved on Commons. It was only a few back then, now it's more. @Mitar:, file movers can't help you. We can't move a file page to a name that exists as a Commons image. I'm not sure if administrators could, you could ask I guess but I wouldn't be surprised if they can't do it either. You just have to recreate the page at the desired location and request deletion of the old page. Sure, we can do that, but so can you, so there's no point in requesting renames. — Alexis Jazz (talk or ping me) 05:50, 11 March 2022 (UTC)

Yes, I made few requests few days ago and I saw them resolved. So I thought it worked so I made requests for all cases where I found the issue. So I think there are few issues here a) why those descriptions are not moved when commons file is renamed, I think that should probably be filled as a bug in Phabricator, no? b) what is the best way to resolve existing cases for which I put the template on. If renaming cannot be done, then that is tricky. Doesn't recreation of the page loses history? It would be nice if original history is retained. How to do that? Mitar (talk) 08:44, 11 March 2022 (UTC)

I have asked admins here. Mitar (talk) 12:35, 11 March 2022 (UTC)

Mitar, for those old requests I just requested their deletion and recreated them at the target. (indeed destroying the history) Here are some things you could do:
1. Sure, you could file a Phab task. I'm not sure if this qualifies as a bug or a feature request. If you wrongly file it as a bug they might close it as invalid instead of changing the subtype. Either way I wouldn't expect them to do anything about it, they are way too busy awarding themselves barn stars for inefficient tools with few features. (I should know, I wrote a more efficient tool with many features) and rationalizing bugs reports away. But who knows, maybe a volunteer will pick it up. Keep the hope alive.
2. Ask an admin if they can move it. Because I don't know for sure.
3. If they can't be moved the only way to retain history would be a crosswiki round robin move variant. Move the file on Commons without leaving a redirect, move the file locally, move the file on Commons back. This isn't going to happen.
4. I could rollback your requests if you want (I have the rollbacker right) so you can substitute the page at the intended target, the edit summary would show the subst template, providing a tiny bit of history. — Alexis Jazz (talk or ping me) 12:36, 11 March 2022 (UTC)

Jazz, thank you very much. I'm not sure I understand everything, but now I can figure it out. I get confused when there's cross wiki stuff, I tend to stay away from those requests, anyway thanx again for your (good) explanation. Cheers, - FlightTime (open channel) 01:24, 12 March 2022 (UTC)

Mitar, I was just thinking. As similar tasks are carried out by CommonsDelinker and Filedelinkerbot, this should probably be handled by a bot as well. So if you file any Phab task it should be to request a user right that allows overriding the create protection so you can file a request on Wikipedia:Bot requests. — Alexis Jazz (talk or ping me) 05:26, 2 April 2022 (UTC)

You are right. This whole thing should be handled by a bot and make sure things are consistent. Should we maybe just ask an author of one of those bots to add this feature? Mitar (talk) 11:51, 2 April 2022 (UTC)

Mitar, they can't, not without the right to override the create protection. Asking Magnus is probably a waste of time, he's always busy. As for Krd, I wouldn't ask them either, but that's much more complicated. Just file a Phab task for the creation of a right to override the create protection first, think of Wikipedia:Bot requests second. — Alexis Jazz (talk or ping me) 12:02, 2 April 2022 (UTC)

I made it: https://phabricator.wikimedia.org/T305548 Mitar (talk) 12:19, 6 April 2022 (UTC)

Alexis Jazz, are you sure about tagging all of these pages for deletion? Some of them have notices about being Featured images. It's a big deletion to handle and if they have been mistagged, that is a lot of page restorations to do. Liz ^{Read! Talk!} 21:20, 14 March 2022 (UTC)

Liz, 155 of them have been recreated at the current filename with the same content, but feel absolutely free to perform another spot check, though I don't believe I missed anything. 17 had been recreated by Cyberbot I, that's the icky stuff. Even if I screwed up, there's c:Help:Gadget-Restore-a-lot. — Alexis Jazz (talk or ping me) 23:33, 14 March 2022 (UTC)

It looks like Explicit took care of them. He is more knowledgeable about files than I am so I'm glad he took that on. I installed your script but have no used it yet so I'm not confident it using it to evaluate files. Liz ^{Read! Talk!} 23:54, 14 March 2022 (UTC)

File:Ipshita Mukherjee XkcHxSrwqw 5.46.jpg

Hello Alexis Jazz I hope you're doing well. I have a query is there any problem with the file. You could have moved the file to commons. Or if I'm mistaken then I sorry. Thanks, stay safe. C1K98V ^{(💬 ✒️ 📂)} 06:15, 19 March 2022 (UTC)

C1K98V, anyone who wishes to do so could move the file to Commons. I'm not editing Commons while this remains unresolved (the "If there is no evidence" part is true), and I haven't mustered up the courage yet to face the checkuser team again. — Alexis Jazz (talk or ping me) 12:04, 19 March 2022 (UTC)

Atops and Abots

Hey, Alexis Jazz. I noticed you created these two templates. Why did you create these new templates instead of using what they actually wrap? Gonnym (talk) 06:18, 22 March 2022 (UTC)

Gonnym, I'm the developer of Bawl. Bawl has a checkbox to close sections as you reply, and the reply/edit summary become the result/status. As Bawl aims to work on any MediaWiki wiki, hardcoding {{Archive top}} did not make sense. Getting the template name from d:Q10809044 and d:Q6663585 is technically possible, but doesn't provide the parameters. Using unnamed parameters (1= and 2=) is not guaranteed to work with the template on all wikis, and some wikis could have the closing message as part of {{Archive bottom}} instead of top. The solution was {{Atops}} and {{Abots}} with a generic HTML fallback. If a wiki doesn't like the generic HTML fallback (enwiki wouldn't), Atops/Abots can be created to direct Bawl (or in the future possibly other scripts/extensions) to the right template with the right parameter names. — Alexis Jazz (talk or ping me) 11:32, 22 March 2022 (UTC)

Special:WantedTemplates

Hi! Would it be possible for you to add

/* <nowiki> */

to the top and

/* </nowiki> */

to the bottom of User:Alexis Jazz/Bawl-extra.js? By putting these tags inside of javascript comments, it won't impact the functionality of your script, but it will keep the backend software from transcluding Template:Preloadparams. You will know if the tags worked if Special:WhatLinksHere/Template:Preloadparams no longer shows your javascript page. By fixing these, we can keep the number of entries in Special:WantedTemplates to a minimum. Thank you in advance for your help! Plastikspork _―Œ^(talk) 15:19, 26 March 2022 (UTC)

Plastikspork, hmm, seems like an error of a different kind. It's supposed to be possible to substitute that page to generate some templates. Those templates have parameters, one of which is {{{preloadparams}}}. To prevent that from getting substituted on template creation I wrote it as {<noinclude></noinclude>{{preloadparams}}} which, as I see now, caused it to get interpreted as a template. I moved the noinclude tags one curly bracket over, this probably fixes it. — Alexis Jazz (talk or ping me) 17:25, 26 March 2022 (UTC)

Thanks! Plastikspork _―Œ^(talk) 19:51, 26 March 2022 (UTC)

Per your edit summary

Hello, Super Goku V here. I figured I should respond here to your request rather than in your userspace. (Sorry if that was an incorrect assumption.) So, to start the explanation of what happened off, I should note that I had made a few edits prior to my comment because the Template:sources-talk was causing issues when using DiscussionTools and trying to put my comment in the middle of the discussion. I ended up moving the template to the bottom of the page and double spaced it so that it wouldn't cause more trouble. (I didn't know if it was possible to make a sub-section due to some, if not all, AfD discussions being transcluded on other pages.) After that, I clicked the reply button next to the nominator's initial comment to begin. Since they had two points I wanted to address, I decided at some point to split my response so that it would be easier to discuss if someone replied to it. And since User:IndentBot had corrected me in the past, I went to their talk page and eventually ended up at Wikipedia:Bots/Requests for approval/IndentBot#Changes to bot, which I thought was showing me the proper way to indent. (Which as you implied, is apparently not the right way to do so.)
So, I wrote up the text for both comments in the same comment through DiscussionTools. Since I was in Source mode, I could see that only the second comment was going to have a signature. Knowing this, I added "----~~" to the end of my first comment, so that it would be signed as well. For my second comment, I only added the dashes as I prefer signing with dashes. (In fact, if you look closely at the edit, you can see that the signatures are not identical; the manual signature does not have a space between the dashes and my username while the one added thru DiscussionTools annoyingly added a space.) Upon submitting, it somehow added an additional colon to both of my comments, presumably because my indentation is causing an issue, DiscussionTools apparently wasn't designed with someone writing multiple comments at once, and/or replying to the original comment caused an issue. (Testing does show something isn't working right, but it only occurred the first time.) If I do figure out anything else, I will make sure to let you know in case it helps you with Bawl. --Super Goku V (talk) 06:50, 1 April 2022 (UTC)

Super Goku V, thanks for the details! You are already helping: Bawl (and this goes for every reply-solution out there, including DiscussionTools) was never designed for placing multiple comments at once. So I should warn users who try to do that and inform that it's better to place two comments in two edits. I just tested and if I'd respond to KidAd with Bawl now the comment would end up above the {{sources-talk}} line with a single asterisk indentation. This is the expected behavior, the {{sources-talk}} has no indentation so it's considered to be the end of that discussion. Having a {{sources-talk}} that doesn't "belong" to anyone floating about in the middle of a discussion isn't ideal, but what can you do. DiscussionTools just made a mess: Wikipedia:Articlesfordeletion/WillSmithassaultofChrisRockattheOscars (diff 1080186239) inserted above the sources-talk (as Bawl would) but with an empty newline and a change in indentation. (as Bawl wouldn't) Wikipedia:Articlesfordeletion/WillSmithassaultofChrisRockattheOscars (diff 1080186549) was a wikitext edit that added a comment below the {{sources-talk}}. A few wikitext appended comments later there's another DiscussionTools comment, and it goes above the {{sources-talk}}: Wikipedia:Articlesfordeletion/WillSmithassaultofChrisRockattheOscars (diff ~1080189833). If something should be forced to the bottom of the page (I generally keep my references inline nowadays to avoid this, external links are fine on discussion pages), it should have its own (sub)section to avoid these issues. You can always use noinclude if you don't want that to be transcluded. Anyway, I wonder why you don't add the dashes to your default signature in Special:Preferences so you never get that extra space? — Alexis Jazz (talk or ping me) 12:29, 1 April 2022 (UTC)

No problem and that is good to hear. I do want to quickly correct my earlier post; the template when I added my comment was {{refList}} and it was modified three minutes later by another user to be {{sources-talk}}. (That doesn't likely change things as your test lined up with what happened to me, so presumably refList also has no indentation.) I will try to keep in mind that using both noinclude and a subsection would have taken care of the issue. --Super Goku V (talk) 00:59, 3 April 2022 (UTC)

As for making a default signature, I should say that I do not know if I noticed the spacing issue before or after making the comment. Regardless, I didn't think about doing so, possibly because I don't edit that much compared to other users. Either way, as you can see, I ended up figuring out that I could just manually add the signature to the end of my comment instead of letting DiscussionTools automatically do so for me. It also works with multiple signatures at once, even if that isn't useful given your recommendation to do two separate edits instead. --Super Goku V (talk) 00:59, 3 April 2022 (UTC)

Super Goku V, about the indentation, you are right as indentation isn't part of the template. For the template to have indentation, it would have had to be :{{sources-talk}} or :{{refList}}. * would also work, and in case of Bawl # would also work, oddly DT doesn't recognize # as a possible indentation. (it's common enough for votes, isn't it?) When you add your signature manually, I suspect DT does the same thing Bawl does: wipe it before automatically appending the signature. Actually accepting your manual signature can result in more complications, so that doesn't happen. Though, the adjustment to not trim whitespace characters or add a space at the end if the last non-whitespace character is a dash or minus sign, shouldn't be terrible complicated, so I'll probably add that to Bawl. — Alexis Jazz (talk or ping me) 06:00, 3 April 2022 (UTC)

File permission problem with File:Claudi Bockting by Trudy Kroese.jpg

Thanks for uploading File:Claudi Bockting by Trudy Kroese.jpg, which you've attributed to No reply to latest email in VRT of 12/21/2021. I noticed that while you provided a valid copyright licensing tag, there is no proof that the creator of the file has agreed to release it under the given license.

If you are the copyright holder for this media entirely yourself but have previously published it elsewhere (especially online), please either

• make a note permitting reuse under the CC-BY-SA or another acceptable free license (see this list) at the site of the original publication; or
• Send an email from an address associated with the original publication to permissions-en@wikimedia.org, stating your ownership of the material and your intention to publish it under a free license. You can find a sample permission letter here. If you take this step, add {{OTRS pending}} to the file description page to prevent premature deletion.

If you did not create it entirely yourself, please ask the person who created the file to take one of the two steps listed above, or if the owner of the file has already given their permission to you via email, please forward that email to permissions-en@wikimedia.org.

If you believe the media meets the criteria at Wikipedia:Non-free content, use a tag such as {{non-free fair use}} or one of the other tags listed at Wikipedia:File copyright tags#Fair use, and add a rationale justifying the file's use on the article or articles where it is included. See Wikipedia:File copyright tags for the full list of copyright tags that you can use.

If you have uploaded other files, consider checking that you have provided evidence that their copyright owners have agreed to license their works under the tags you supplied, too. You can find a list of files you have created in your upload log. Files lacking evidence of permission may be deleted one week after they have been tagged, as described in section F11 of the criteria for speedy deletion. You may wish to read Wikipedia's image use policy. If you have any questions please ask them at the Media copyright questions page. Thank you. VernoWhitney (talk) 15:11, 3 May 2022 (UTC)

I'm afraid the template got a bit mangled there, but this is basically saying that while we've received some emails about this image there were some questions asked for required information back in December and we've not yet received a reply. VernoWhitney (talk) 15:15, 3 May 2022 (UTC)

VPT comment

Just a note for the future, regarding calling people's work "not salvageable": I don't mind at all, but I imagine other people may not take it as well. Enterprisey (talk!) 22:14, 15 May 2022 (UTC)

Enterprisey, sorry, I realize now that likely comes across different from how I meant it. What I meant with that was that it would be more efficient for me personally, to create the script installer/manager I envision, to start from scratch rather than fork script-installer. Script-installer does what it was written to do, that's just different from being a good starting point for any particular person to create something similar but different. Of course, forking is quite often more work. Forking is only easier when the original code merely needs a few tweaks to add all desired features or if it happens to be extremely easy to build upon or if the recreation of the original functionality would take months. In practice only the first possibility happens occasionally, where some minor tweaks make something work just the way you want it to. When I first discovered script-installer I absolutely loved it! Finally no more messing around with common.js. After a while I found some issues though, the biggest being that it still uses the deprecated importScript() which simply doesn't work on the mobile site. I guess if you must keep using importScript() (I admit, importScript() looks cleaner) you'd have to define importScript(), either in minerva.js (not sure about the load order so that might not work) or conditionally in common.js.
Much of my older work I'd also call "not salvageable" btw, especially for others. Take User:Alexis Jazz/LuckyRename for example, it works well (for now.. it uses synchronous HTTP requests, so it could break in the future if browsers really stop supporting them) but when I wrote it there were many things I didn't know. It's mostly salvageable for me as I'm familiar with it, but if anyone else wanted to add half a dozen features? They'd probably be better off starting from scratch.
Long story short, it was a crappy choice of words. Sorry. — Alexis Jazz (talk or ping me) 00:29, 16 May 2022 (UTC)

Enterprisey, I feel rather bad about this. You've contributed a ton to Wikimedia. I had been hammering away at some regular expressions for hours (you know how it is) and wasn't thinking properly about what the words I wrote actually meant. I don't really know what else to say, just hoping you can forgive me.. — Alexis Jazz (talk or ping me) 18:36, 16 May 2022 (UTC)

Thanks for the laugh

I actually lol'd at your comment. As to who would colorize just pants, Mickey Mouse (in some images as least) seems to be doing ok without color anywhere other than his pants ;). Thanks for making me smile! HouseBlastertalk 17:28, 17 May 2022 (UTC)

File:NCAA 2018 Division III Women's Tennis Championship logo.svg

Hi Alexis Jazz. Do you think you could update File:NCAA 2018 Division III Women's Tennis Championship logo.svg? The most recent version can be found here. Perhaps all that's needed is the primary logo with the event name without any of the specific year information; otherwise, you may have someone trying to upload a new version each year. -- Marchjuly (talk) 02:30, 26 May 2022 (UTC)

Marchjuly, WP:EVADEGDPR just struck again. NCAA.com shows nothing but some GDPR whining. It's not impossible for me to get around, but perhaps it's just easier to ask someone not affected? I wonder why you can't do it yourself though? And as for using only a primary or partial logo, you should discuss that Talk:NCAA Women's Division III Tennis Championship. — Alexis Jazz (talk or ping me) 02:45, 26 May 2022 (UTC)

My bad. I wasn't aware of the GDPR stuff. I'm not able to download anything at the moment, but I'll give it a try later on. Thanks again. -- Marchjuly (talk) 03:08, 26 May 2022 (UTC)

Marchjuly, np. If you can't make it work or find someone not affected by the GDPR stuff feel free to ask again, but I'm sure there'll be some sports nut who can do this more easily. Using only the primary logo is usually a good idea, but only if the isolated primary logo is also used by the organization in publications. If they never do (and I can't even visit their website, so how would I know?), it's not a good idea. Which is why I suggested to discuss that on the talk page of the article. — Alexis Jazz (talk or ping me) 03:34, 26 May 2022 (UTC)

Ok, that's odd

Hi, hope you are well. I started Pamela Balash-Webber, and decided to add a non-free image of her since the situation allowed it. Took it from [2], and according to [3] it was taken by her husband. So, why does the meta-data [4] seem to insist the pic is from 2021? Gråbergs Gråa Sång (talk) 14:05, 21 June 2022 (UTC)

Gråbergs Gråa Sång, and it was taken with an iPhone 12 which was released in 2020. So how did Andre get his hands on that, considering he died in 2014?
How old is Pamela on that photo anyway? Maybe 30? I'm not very good at guessing age, but she's nowhere near 50. So I think this photo was taken before the digital age. And now, people use the camera on their phone as an improvised image scanner. — Alexis Jazz (talk or ping me) 18:46, 21 June 2022 (UTC)

That would explain it. I prefer it to "vampires". Gråbergs Gråa Sång (talk) 18:57, 21 June 2022 (UTC)

Gråbergs Gråa Sång, vampires with iPhones, interesting idea. Btw, I suddenly see: I think the photo is framed. Look at the black part of her wetsuit. Does that look like a reflection? — Alexis Jazz (talk or ping me) 22:01, 21 June 2022 (UTC)

Could very well be. Gråbergs Gråa Sång (talk) 05:50, 22 June 2022 (UTC)

Orphaned non-free image File:Holden (car brand).webp

⚠

Thanks for uploading File:Holden (car brand).webp. The image description page currently specifies that the image is non-free and may only be used on Wikipedia under a claim of fair use. However, the image is currently not used in any articles on Wikipedia. If the image was previously in an article, please go to the article and see why it was removed. You may add it back if you think that that will be useful. However, please note that images for which a replacement could be created are not acceptable for use on Wikipedia (see our policy for non-free media).

Note that any non-free images not used in any articles will be deleted after seven days, as described in section F5 of the criteria for speedy deletion. Thank you. --B-bot (talk) 17:21, 2 July 2022 (UTC)

"Sproftacchel" listed at Redirects for discussion

An editor has identified a potential problem with the redirect Sproftacchel and has thus listed it for discussion. This discussion will occur at Wikipedia:Redirects for discussion/Log/2022 July 5#Sproftacchel until a consensus is reached, and anyone, including you, is welcome to contribute to the discussion. Jak86 (talk)(contribs) 16:30, 5 July 2022 (UTC)

A barnstar for you!

The Technical Barnstar

I am literally crying right now. Everyone was using your tool, Bawl, and I have to say, it crushes DiscussionTools in every aspect (except there is no visual mode)! I made a signature for all of my alternate accounts, and DiscussionTools kept breaking it by making two signatures! But Bawl is much smarter than that, and it fixed the problem in a jiffy! As it's only in beta right now, I only use it on my alts, but, oh, wow—this might be the first beta I'll install on my main account! — 3PPYB6 — TALK — CONTRIBS — 15:32, 6 July 2022 (UTC)

3PPYB6, thank you! Actually there is a visual mode, though it's more limited than DT or VE: check "Enable switching between editors" on the Advanced tab in settings and/or change "Default editor for comments and new sections" to "VisualLight". (which I thought was a nice name, "light" referring to both visual light and its speed as lightweight solution) Alternatively, if you aren't already, you might find using live preview helpful, found on the Editing tab in settings. They are mutually exclusive though: you can't have VisualLight and live preview active at the same time. While typing plain text, Bawl's live preview is (probably unlike any live preview feature you've used before) actually fast most of the time. — Alexis Jazz (talk or ping me) 18:47, 6 July 2022 (UTC)

Thanks for letting me know! Should I find Bawl to be safe to use (I installed it yesterday on my test account and other alts), I will definitely install it! Farewell, DiscussionTools! — 3PPYB6 — TALK — CONTRIBS — 00:20, 7 July 2022 (UTC)

File:Heleen Mees, July 2020 (cropped).jpg

Hello. Is there any particular reason why you uploaded this here instead of Wikimedia Commons? --Minorax^«¦talk¦» 10:34, 10 July 2022 (UTC)

Minorax, fabricated death threats and because I never played Fortnite which seemingly caused an imaginary horse to be mistaken for a gun. Commons lost admins Zhuyifei1999 and Majora to that debacle. — Alexis Jazz (talk or ping me) 11:20, 10 July 2022 (UTC)

Would you mind if I move the file to commons? It's clearer than the other cropped version available there. --Minorax^«¦talk¦» 11:25, 10 July 2022 (UTC)

Minorax, no problem. I never tagged my own files with {{Copy to Wikimedia Commons}} as that would have potentially been considered block evasion. Beware that actually using that crop may result in a revert. There's a very strange story behind that which I can't remember if I'm allowed to share publicly.
And if you're wondering why I haven't contributed to Commons even after my unblock, I'm rather uneasy with the way my unblock was granted. Saying you find an argument of the user disingenuous while also saying you now trust them in the same sentence comes across as.. really odd. Simply put, I'm not entirely sure why I was blocked in the first place, why I remained blocked despite a lack of evidence and why exactly I was unblocked.
I don't think anybody is quite sure why I was blocked indef in the first place. What I did wasn't great, but none of the procedures for an actual death threat were followed and the block was placed four days after the misinterpreted message so it wasn't a case of having to halt disruption immediately either. I possibly remained blocked due to my less-than-ideal response to the initial block. The unblock is a bit of a mystery because frankly, I never apologized for the death threats that were made up.
It's all largely a mystery, so anything I say could theoretically get me blocked again, at least that's how I see it. As long as I say nothing they hopefully won't block me again. — Alexis Jazz (talk or ping me) 11:58, 10 July 2022 (UTC)

Can, could

Hi, I see that you have written "This could change if Iran becomes a Berne Convention member in the future". A native speaker of English, I think, confirmed your grammar by writing "Likewise, that could change." In both case, I would have probably used can instead of could. Is my use of the word can grammatically correct in the following sentences?

• "This can be hosted at Commons."
• "this work can be transferred to Commons."

Thanks! 4nn1l2 (talk) 00:10, 13 July 2022 (UTC)

4nn1l2, I remember this joke:
Student: "Teacher, can I go to the bathroom?"
English teacher: "Yes, you can."
S: *gets up from chair*
EN: "Where do you think you're going?"
S: "You said I could go to the bathroom?"
EN: "You can go, but you may not! Sit down."
Cambridge dictionary explains a few things about these modal verbs. weloveteachingenglish.com offers a quite comprehensive collection of examples and information on them. Your use of "can" is appropriate here. In these instances "could" would have been acceptable as well, but I'd say "can" is better in this context. "Can" describes the ability here (it is possible to host it on Commons) while "could" would be more ambiguous as it could refer to either the chance it is already hosted on Commons or the chance of it getting hosted on Commons in the future. Well, generally speaking at least, because could may well end up being used as a synonym for can which could certainly irritate English teachers.
Btw, I'd say you host something on Commons, not at. I'm not sure if at could also be correct. It might be. — Alexis Jazz (talk or ping me) 01:30, 13 July 2022 (UTC)

Precious anniversary

Precious

One year!

--Gerda Arendt (talk) 05:22, 14 July 2022 (UTC)

hello - nice to meet you

Thanks for your work on the Patrick Lancaster page. 666hopedieslast (talk) 23:27, 14 July 2022 (UTC)

So I got this mail from User:TechConductCommittee

..and I'll just share it publicly.

Hello AlexisJazz,
This is a message from the Code of Conduct committee. We recently received a report regarding several of your recent comments at Wikimedia Phabricator, related to VisualEditor.
The Committee concluded your comments are unnecessarily antagonistic and impolite towards other members of the technical community and as such, they don't meet the standards set by the Code of Conduct <https://mediawiki.org/wiki/Code_of_Conduct>. While we appreciate your help in the technical community, we ask you to keep the "Assume good faith" principle in mind.
Thank you for your understanding. In case you have any questions, please feel free to reach us via techconductwikimediaorg
Sincerely,
Martin Urbanec

Martin Urbanec, I don't even know which comments you are referring to. "recent" and "visualeditor", that barely narrows it down. And I'm not exactly a big fan of these behind-closed-doors judgments. You could have told me a report was filed before you discussed it, with links. You could have given me a chance to explain what I said (whatever it is I said), a chance to apologize, a chance to re-word/retract statements that were negatively perceived. I find it disappointing you didn't do any of those things.
The method reminds me of the debacle with my ban from Commons by the checkuser team. A group that judges people behind closed doors, does not give the subject a chance to explain their side before making a decision, only vaguely refers to what they're talking about and with unclear (or possibly nonexistent) accountability. It feels like a WP:CABAL.
@PPelberg (WMF): you asked me if I was interested in talking with you and an engineer from the editing team about edit notices in a text or voice chat. I suspect the WMF may be looking into me. I've noticed some unusual activity on Phabricator, and now this. While I hope everything is unrelated, I'm concerned what may or may not be going on. I don't think I feel safe communicating over any private channels anymore.
@Fram: got any advice? — Alexis Jazz (talk or ping me) 12:15, 31 July 2022 (UTC)

I think you did the right thing here, bringing this out in the open. I had for too long just replied to the mails without informing the community, which I should have done. As for phabricator, I avoid it like the plague, the people applying the rules there seem to do so only to avoid difficult questions and to impose their own preference, and it is strictly forbidden to question e.g. the urgency or importance given to tasks, as that disrupts their work. Basically, some people there seem to think phabricator exists for the developers, not for the community, and they can do as they please. Obviously I don't know in this case if they have valid reasons to complain about your edits or not; but they should clearly indicate which edits, or at least the edits to which task(s), they have issue with, so you and others can see what's it all about. Without this, it is random abuse of power. Fram (talk) 08:21, 1 August 2022 (UTC)

hi @Alexis Jazz – I appreciate you making me aware of the message you received from the Code of Conduct Committee.

While I don't have any information about the CoC situation, I agree with you in thinking that @Martin Urbanec likely does.

Anyway, I'd like for us to see if we can work together to get mobile edit notices deployed. I'll follow up with you about that on Wikipedia_talk:EditNoticesOnMobile tomorrow. PPelberg (WMF) (talk) 23:43, 1 August 2022 (UTC)

Fram, thanks. Yeah, the way they waive rules around seems often more disruptive than the "disruption" they are claiming to fight.
PPelberg, seems like Martin Urbanec is stonewalling me here. While I'd hope not, maybe they just forgot to reply, it's far from unexpected from a cabal that can't even be bothered to supply links of perceived bad conduct.
I just found a bug in DiscussionTools. Seems like quite a doozy! Normally I'd open a Phabricator ticket, but I don't feel terribly inclined today. I don't use DT anyway. — Alexis Jazz (talk or ping me) 05:57, 3 August 2022 (UTC)

User:Martin Urbanec, now I found another bug in DT. It's a JS error, fun. I could open a Phab ticket, or watch Nyan Cat again. Na-nananana na na nanananana na na nananananana na na nananananana — Alexis Jazz (talk or ping me) 02:53, 5 August 2022 (UTC)

This was phab:T314964. You could have known 5 days earlier. — Alexis Jazz (talk or ping me) 13:41, 13 August 2022 (UTC)

As Martin Urbanec seems incapable of speech, maybe Eugene233 or Nurieta would be able to enlighten the situation.
I just encountered a JS error on another project. Not quite sure what causes it but it also shows in a private window and I have no reason to even attempt to investigate or report it right now. If you really "appreciate my help in the technical community", the least you could do is tell me which comments Martin's mail was about.
And if you want to do more (and you should!), I'd say seriously reconsider your current procedures. Accusing someone of not assuming good faith without listening to their side first is itself an assumption of bad faith. — Alexis Jazz (talk or ping me) 05:32, 6 August 2022 (UTC)

503 backend fetch failed again when trying to edit, Varnish XID 887837102. Just another data point in phab:T303165 / phab:T295427 so probably not that interesting. — Alexis Jazz (talk or ping me) 10:21, 8 August 2022 (UTC)

Found another bug in DiscussionTools. This one only affects beta cluster.. for now. One would think the TechConductCommittee could muster up the strength to cough up some links to get me to report this crap before it hits production instead of scribbling down a note in my personal notepad about it.
@Ladsgroup and MusikAnimal: you're the last two non-auxiliary members on the committee. If you can share some links of what Urbanec was talking about, please do. — Alexis Jazz (talk or ping me) 08:04, 11 August 2022 (UTC)

Found a bug in mw:Page Previews. Going once.. going twice..? — Alexis Jazz (talk or ping me) 17:04, 11 August 2022 (UTC)

Found a bug in DiscussionTools on beta cluster. Looks pretty serious!
GOING ONCE! GOING TWICE! ANYBODY? ANYBODY AT ALL? — Alexis Jazz (talk or ping me) 12:13, 18 September 2022 (UTC)

Found a UI issue on the mobile site.
Doubt anyone will care. — Alexis Jazz (talk or ping me) 20:44, 22 September 2022 (UTC)

Found something again. Once more, it's DT. Showing something it shouldn't.
This one is gonna piss people off. Currently on beta cluster. — Alexis Jazz (talk or ping me) 12:00, 23 September 2022 (UTC)

@Huji, User:Jayprakash12345: not sure if the auxiliary members have access to the information, but do you have links for the comments Martin was talking about? — Alexis Jazz (talk or ping me) 16:55, 24 September 2022 (UTC)

@Alexis Jazz: pardon the late response. Is the question still valid? huji—TALK 16:49, 5 October 2022 (UTC)

Huji, I'm glad to see any response! Yes, this is still an open question. Can you provide links? — Alexis Jazz (talk or ping me) 18:32, 5 October 2022 (UTC)

Huji, any news yet? I found another JS error, I'd prefer reporting these as opposed to writing them down as a personal memo. — Alexis Jazz (talk or ping me) 08:41, 8 October 2022 (UTC)

@Alexis Jazz: sorry to be a pain in the neck but can you please clarify what "links for the comments Margin was talking about" refers to? If you have the link or know exactly where I can find it, I can try and check if I have access to the linked page(s). huji—TALK 19:38, 9 October 2022 (UTC)

For the records, CoCC's message does say where questions about that message can be asked. English Wikipedia is not that place. Martin Urbanec (talk) 21:33, 9 October 2022 (UTC)

Huji,
sorry to be a pain in the neck but can you please clarify what "links for the comments Margin was talking about" refers to? If you have the link or know exactly where I can find it, I can try and check if I have access to the linked page(s).
Martin said in his mail (top of this section) "We recently received a report regarding several of your recent comments at Wikimedia Phabricator, related to VisualEditor."
I'm still trying to figure out which comments this refers to. I can't explain, rephrase, apologize, take back or learn from mistakes if I don't even know what it's about.
Martin Urbanec,
For the records, CoCC's message does say where questions about that message can be asked. English Wikipedia is not that place.
I know Fram's case. The only option given in that mail is to mail back. I don't want any "but x said.." later on, there's nothing confidential here. If you can't answer publicly (I don't mind asking on a talk page of your choosing, but not mail), how is anyone to take this seriously? — Alexis Jazz (talk or ping me) 07:31, 10 October 2022 (UTC)

Sorry for slow response, again, and thanks for the clarification.

As an extended member, I was involved in this case and have no access to the information above. That said, even if I had access, I am not sure if I or any CoC member/extended-member would link to them publicly. You could ask privately, but making links public may be in violation of the CoC policy. Coincidenally, this discussion is also ongoing now and points to the same consideration. huji—TALK 13:01, 16 October 2022 (UTC)

Huji, but this must be a joke. You were involved, you and Martin accused me of "unnecessarily antagonistic and impolite" comments, but you won't link any of them!
Can you imagine this anywhere else? You stole my beer. I won't tell you which beer, how much beer, what you did with it or when you did it. You have no idea what I'm talking about, but that doesn't matter. I'm accusing you, and you have absolutely no way to handle this because I refuse to give you any details, hiding behind some policy. So you can't apologize for it, because you don't know what I'm talking about. You can't give an alibi, because I won't you give any details. I decided you're guilty, therefore, you are! Judge, jury and executioner.
I'll say this: the sole reason for the TechConductCommittee to exist is to silence dissidents. You can't prove me wrong, because I won't give you any details. My policy says that information is confidential. — Alexis Jazz (talk or ping me) 13:34, 16 October 2022 (UTC)

@Alexis Jazz: was I personally involved? It may be that I cannot remember it (pardon my poor memory). But was I personally involved? PS: I recognize my poor memory is a predicament, but please don't call it "a joke"; that is not nice. huji—TALK 12:40, 21 October 2022 (UTC)

Huji, above you said (13:01, 16 October 2022): As an extended member, I was involved in this case. Not sure how else I could reasonably interpret that? — Alexis Jazz (talk or ping me) 13:22, 21 October 2022 (UTC)

@Alexis Jazz: my bad! I mean to write "as an extended member I was not involved in this case". I understand how my typo could have caused confusion and apologize for it. huji—TALK 01:48, 22 October 2022 (UTC)

..found another bug. This one causes a broken link to the main page. Fun!
All I'm asking for are links. Well that, or for the original complaint to just be dropped.
[edit]Found another little bug! Related to notifications. I'd report all this stuff, all I'm asking is a little common courtesy. — Alexis Jazz (talk or ping me) 09:17, 8 October 2022 (UTC)

The "Code of Conduct Committee" is incredibly shitty. This behavior of theirs, sending threatening e-mails like this one and not elaborating on what they found to be problematic, is unfortunately common. The vagueness makes it impossible to respond to complaints or defend yourself or provide context. It's a symptom of Wikimedia Foundation Inc. trying to silence critics and criticism. The organization is pretty deeply incompetent and corrupt. --MZMcBride (talk) 00:28, 4 October 2022 (UTC)

At least you can take comfort in the message you received being signed at all. Apparently this other kangaroo court doesn't even disclose its membership. Truly corrupt and bad!! --MZMcBride (talk) 00:33, 4 October 2022 (UTC)

MZMcBride, thank you for the moral support. :-)
Members being anonymous (like the case review committee you linked) wouldn't have to be a problem per se as long as the procedure is transparent and community-vetted, and members can ultimately be held accountable and can (when needed) be overruled by the community. That's all more complicated with anonymity but not impossible. At any rate, they should strive to communicate openly, like on talk pages, whenever possible. Not mail.
@GreenMeansGo, @4nn1l2, with this and Wikipedia:Village pump (WMF)/Archive 5#Cabals, stonewalling and the WMF is A-okay with that this may mark the end or near-end of this nightmare. They won, and I need to move on. I'm considering one last thing, to re-ask Krd on their talk page what AFBorchert asked them in March 2020, you never know if maybe they'd actually answer. I don't care for amnesty (I'm already technically unblocked anyway), I don't even care if Commons blocks me again. If just that question could be answered publicly, I'd be.. okay I guess, and I might upload some of the stuff I've been sitting on. I just wanted my name to be cleared, but if it's not going to happen it's not going to happen.
I may follow Zhuyifei1999's example. Maybe just as cold turkey, maybe tepid turkey. I'm finishing up Factotum because I had already sunk too many months into it. Finally wrapping up this case, one way or another, is also something that needed to be done. Letting go is hard, but it's time. If you'd advise against asking Krd one last time, this is it. Otherwise, that question will mark the end this story for me, whatever the answer. If Ombuds ever gets around to the case and I'm no longer around, I hereby give them permission to tell GMG and 4nn1l2 whatever they would have told me. — Alexis Jazz (talk or ping me) 19:32, 5 October 2022 (UTC)

A barnstar for you!

	The Technical Barnstar
	Not the first person to give you one of these for Bawl, but something tells me I will not be the last. It is an awesome tool, with awesome features, and is steadily improving. However, beyond a doubt, the best feature is how quickly you respond to any bug reports, and how quickly you implement feature requests. Thank you!! HouseBlastertalk 01:53, 6 August 2022 (UTC)

A barnstar for you!

	The Barnstar of Diligence
	For the diligence you've showed in dealing with requests of all sorts regarding Bawl for many weeks in a row now. Your effort is appreciated and your work is acknowledged. - Klein Muçi (talk) 15:31, 4 September 2022 (UTC)

Script bug

I can't select any edits with Wikipedia:Kill-It-With-Fire (Cat-a-lot works). This might be a script conflict. — Qwerfjkltalk 20:46, 6 September 2022 (UTC)

Qwerfjkl, I tried it and only found an issue when opening (showing their forms) both at the same time. I made a change and now they seem to work even in that scenario. — Alexis Jazz (talk or ping me) 04:23, 7 September 2022 (UTC)

September 2022

STOP

You are flooding user talks with a bad change, stop immediately. — xaosflux ^Talk 15:57, 11 September 2022 (UTC)

Your high edits are not only flooding recent changes and watchlists, but causing the new message banner to be activated unnecessarily for every user_talk that you are touching. This is disruptive to other editors and should not be done. Continued high speed flooding of user talks may result in a block. — xaosflux ^Talk 16:00, 11 September 2022 (UTC)

Xaosflux, why is it a bad change?
Seems I only missed about 50 pages, not really a big deal to skip those. I didn't think of the new message banner. Now that I think of it, it's maybe a bit silly that it activates when somebody, for instance, fixes a typo in a minor edit. I just didn't want to bother the bot operators with something I could do myself.
I'll run a test to see if a revert takes away the new message banner. Update: tried both undo and rollback, neither removes the new message banner. — Alexis Jazz (talk or ping me) 16:11, 11 September 2022 (UTC)

Maybe next time mark such changes as minor so you don't annoy other editors with that message banner... Sheep (talk) 16:44, 11 September 2022 (UTC)

Sheep8144402, they were marked as minor, but as you already found out, that still triggers the banner. (does help to filter recent changes/watchlist though) — Alexis Jazz (talk or ping me) 16:52, 11 September 2022 (UTC)

If these changes were truly necessary, it would have been better to put in a bot request in order to avoid flooding watchlists. – Jonesey95 (talk) 17:16, 11 September 2022 (UTC)

This. Bots have a special permission that they can use to avoid triggering new message banners. This triggering of user banners was the major problem you were causing, that your edits did not appear improve the pages for the users that you impacted compounded it; additionally the Wikipedia:Talk page guidelines say that you should not change talk comments that have been replied to. — xaosflux ^Talk 18:00, 11 September 2022 (UTC)

Xaosflux,
say that you should not change talk comments that have been replied to
This was a technical change, the visible content didn't change. The script that was used to place the comments has been renamed. It won't be renamed again. The script can't recognize the old markers anymore, the changes were needed so it could recognize them again and I preferred doing a simple search&replace over implementing legacy support which would likely result in new bugs.
@Jonesey95, @Andrybak, I made a little userscript just now to filter my changes (or those by any other user) from your watchlist/recentchanges: User:Alexis Jazz/ShushChanges. — Alexis Jazz (talk or ping me) 04:13, 12 September 2022 (UTC)

This is not an appropriate response. Please try again. – Jonesey95 (talk) 04:56, 12 September 2022 (UTC)

Jonesey95, your response is indeed not appropriate. I already said above I didn't realize the message banners that would pop up, I've offered you a script to filter my contributions (or those from any other user you'd like to filter) from your watchlist/recentchanges to ease the pain (something I didn't have to do at all) and I've tried to explain the motivation behind the changes.
Your response is not constructive. — Alexis Jazz (talk or ping me) 06:06, 12 September 2022 (UTC)

I appreciate that what's done is done now, so please consider this as advice for the future: maintaining backwards compatible support would have been a more user-friendly approach, and allowed older messages to be converted gradually if it were deemed necessary. Non-substantive changes to talk pages, in addition to obscuring substantive changes in the watchlist, also add volume to diffs spanning multiple edits, which some editors use to catch up on changes since they last viewed the page. In essence, your edits have inconvenienced, to some degree, all editors monitoring pages that have been edited using your discussion tool, whether or not they are users of your tool. Because of the large number of affected editors, the aggregate inconvenience adds up rapidly. isaacl (talk) 20:49, 12 September 2022 (UTC)

Isaacl, backwards compatibility would have been relatively expensive, complicating regular expressions and adding to CSS selectors, both of which impact performance. And that would remain until the end of time. The tool isn't really widespread. Backwards compatibility would have an impact forever, updating existing pages was only going to hurt once. Would have been better if done by a bot, but as I said, didn't want to bother the bot operators over just a few hundred pages. Given the backlash, I guess I should have, or I should have just given up.
maintaining backwards compatible support would have been a more user-friendly approach
Let me know when the WMF is ready to send me a paycheck. Hundreds of hours I sank into this. I thought it would be something great, but maybe I was delusional. Maybe all I did was waste hundreds of hours on a buggy mess and inconvenience a large number of editors. I don't know how I could even tell. — Alexis Jazz (talk or ping me) 03:45, 13 September 2022 (UTC)

You've received lots of positive feedback for your tools, so clearly a lot of your fellow collaborators have benefitted. They can't offer you a paycheck, just their appreciation. Even as someone who doesn't use your tools, I appreciate the work you've invested. I know personally the pains of maintaining backwards compatibility, so I know it can mean tradeoffs that aren't ideal from a design perspective, but are the price paid to keep the community happy. For instance, the format of the IDs and class name could have been left unchanged. I know it would have been an irritant but that's the way of software development. I look forward to seeing what new features are developed. isaacl (talk) 04:05, 13 September 2022 (UTC)

Isaacl, thanks. And yeah, that would have been an irritant. I'd always have to keep that one thing that wasn't changed in mind. My thinking was, I was changing it to "FTT" now so if the tool is ever renamed (or forked) again, "FTT" can remain as a meaningless initialism so this move is a one-off. I'm not looking for a paycheck, but if anyone wants something done in a particular way, they can't expect anyone to do it for free.
If you have inspiration for features, feel free to share. — Alexis Jazz (talk or ping me) 07:14, 13 September 2022 (UTC)

The watchlist flooding is really unfortunate. I don't appreciate the fact that these edits constitute more than a fifth of my watchlist for today. —⁠andrybak (talk) 18:01, 11 September 2022 (UTC)

Xaosflux, this is 100% WP:OTHERSTUFF which I just stumbled upon but I think it's rather unfair that I got all this while Whatamidoing (WMF) got zero flak for nearly 350 edits exclusively to user talk pages that weren't even marked as minor. It's not exactly the same case I admit, but it still doesn't seem quite fair. — Alexis Jazz (talk or ping me) 12:55, 17 September 2022 (UTC)

I agree that was a bad cleanup, especially from a WMF Staffer! — xaosflux ^Talk 23:01, 17 September 2022 (UTC)

A barnstar for you!

	The Teamwork Barnstar
	For your help with Skeeter Reece. Gråbergs Gråa Sång (talk) 14:37, 19 September 2022 (UTC)

Special:WantedTemplates

Hi, I have been cleaning up Special:WantedTemplates and noticed that your javascript page is showing up in Special:WhatLinksHere/Template:' + FTT.basicmsgs.smiley + '. This is because the backend software is parsing the curly braces as templates. An easy way to fix this is to put

// <nowiki>

above line 3270, and

// </nowiki>

below line 3270 in your script. This won't impact the functionality, since they are in javascript comments, but will remove the pages from Special:WantedTemplates. Thanks in advance for your help! Plastikspork _―Œ^(talk) 22:37, 23 September 2022 (UTC)

Plastikspork, oops. — Alexis Jazz (talk or ping me) 23:40, 23 September 2022 (UTC)

Orphaned non-free image File:Holden (car brand).webp

⚠

Thanks for uploading File:Holden (car brand).webp. The image description page currently specifies that the image is non-free and may only be used on Wikipedia under a claim of fair use. However, the image is currently not used in any articles on Wikipedia. If the image was previously in an article, please go to the article and see why it was removed. You may add it back if you think that that will be useful. However, please note that images for which a replacement could be created are not acceptable for use on Wikipedia (see our policy for non-free media).

Note that any non-free images not used in any articles will be deleted after seven days, as described in section F5 of the criteria for speedy deletion. Thank you. --B-bot (talk) 17:12, 28 September 2022 (UTC)

Invitation to Gerrit

I have come to explain how MediaWiki development works. Please take this in good faith.

You need two people to make a change: one of them writes it and submits it for review, the other approves it. They both take responsibility for fixing or reverting the change if any issues are found afterwards.

It follows that, if you need a change made in MediaWiki and you write the patch yourself, you only need to convince one other person to read your code and take responsibility for it. But if you ask someone else to write the patch, then you need to convince two people.

To rephrase: if you write your patches, I will approve them (most of the time). If I write your patches, one of us would need to find someone else to approve them, and I already have a hard enough time finding people to pay attention to my own patches when they aren't work-related.

If you're looking to make your life easier with some MediaWiki changes, please submit some patches in Gerrit (and add me as a reviewer). It's how I started, and I'm hoping I can get you into MediaWiki development as well. Matma Rex talk 10:51, 30 September 2022 (UTC)

Matma Rex, thank you for the offer. I see the conundrum/difficulty.
Maybe one day. I have some personal issues that are long overdue to being dealt with and I expect the dealing to involve a long (perhaps even indefinite) wikibreak, but I can't say much for sure. — Alexis Jazz (talk or ping me) 16:13, 30 September 2022 (UTC)

what?

In this edit to User:Alexis Jazz/Factotum/Modules, you mentioned me in the edit summary with this text: still no machine-readable labels I suppose? [Factotum]. I do not know what you are talking about. If you want to talk to me, do me the courtesy of using a talk page; an edit summary is not the place to conduct a conversation.

—Trappist the monk (talk) 20:04, 30 September 2022 (UTC)

Trappist the monk, yeah sorry too many tabs open. I thought I hadn't archived the thread in which you replied before yet, but I see now I actually did archive that already and only User talk:Alexis Jazz/Factotum#Bug report remained open. So never mind.
Sorry, some things are driving me crazy and I'm taking shortcuts because of it. — Alexis Jazz (talk or ping me) 20:17, 30 September 2022 (UTC)

Trappist the monk, I'm sorry for the messy confusion. We cool? — Alexis Jazz (talk or ping me) 13:06, 1 October 2022 (UTC)

Nomination of List of RenderWare games for deletion

A discussion is taking place as to whether the article List of RenderWare games is suitable for inclusion in Wikipedia according to Wikipedia's policies and guidelines or whether it should be deleted.

The article will be discussed at Wikipedia:Articles for deletion/List of CryEngine games until a consensus is reached, and anyone, including you, is welcome to contribute to the discussion. The nomination will explain the policies and guidelines which are of concern. The discussion focuses on high-quality evidence and our policies and guidelines.

Users may edit the article during the discussion, including to improve the article to address concerns raised in the discussion. However, do not remove the article-for-deletion notice from the top of the article until the discussion has finished.

Respiciens (talk) 12:37, 13 October 2022 (UTC)

Special:WantedTemplates

Hi, I have been cleaning up Special:WantedTemplates and noticed that your javascript page is showing up in Special:WhatLinksHere/Template:'+FTT.MD.POTDBG.templatename+'. This is because the backend software is parsing the curly braces as templates. An easy way to fix this is to put

// <nowiki>

at the top of your script, which matches the

// </nowiki>

you already have at the bottom of your script. This won't impact the functionality, since they are in javascript comments, but will remove the pages from Special:WantedTemplates. Thanks in advance for your help! Plastikspork _―Œ^(talk) 16:34, 23 October 2022 (UTC)

Plastikspork, I had a nowiki at the bottom but forgot the nowiki at the top. Sorry! — Alexis Jazz (talk or ping me) 16:39, 23 October 2022 (UTC)

Rather sadly, I can see the logic

Three weeks ago, in a first-of-its-kind case, a jury in an Illinois federal court ruled that tattoo artist Catherine Alexander’s copyright was violated when the likeness of her client, World Wrestling Entertainment star Randy Orton, was depicted in a video game. Alexander has tattooed Orton’s arms from his shoulders to his wrists. She won, but not much: $3,750, because the court ruled that, though her copyright had been violated, her tattoos didn’t impact game profits. Nonetheless, it set a precedent.

I remember Carrie Fisher Joking "Every time I look in a mirror, I have to pay George Lucas 10 cents." Gråbergs Gråa Sång (talk) 09:23, 25 October 2022 (UTC)

Gråbergs Gråa Sång, claiming copyright is, afaik, not done in the world of tattoo artists. So she didn't win much and probably damaged her reputation in the process. Besides, who's going to get a tattoo from her now, knowing she may sue over it?
Perhaps tattoo artists should adopt CC0, but they probably wouldn't like the formalities. Maybe WTFPL. I suppose you could contact Creative Commons to suggest something, pretty sure they have more followers than I do. — Alexis Jazz (talk or ping me) 09:58, 25 October 2022 (UTC)

Orphaned non-free image File:Holden (car brand).webp

⚠

Thanks for uploading File:Holden (car brand).webp. The image description page currently specifies that the image is non-free and may only be used on Wikipedia under a claim of fair use. However, the image is currently not used in any articles on Wikipedia. If the image was previously in an article, please go to the article and see why it was removed. You may add it back if you think that that will be useful. However, please note that images for which a replacement could be created are not acceptable for use on Wikipedia (see our policy for non-free media).

Note that any non-free images not used in any articles will be deleted after seven days, as described in section F5 of the criteria for speedy deletion. Thank you. --B-bot (talk) 18:20, 25 November 2022 (UTC)

ArbCom 2022 Elections voter message

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:30, 29 November 2022 (UTC)

Archive links

Regarding this edit: just wondering if you meant to remove the links to your talk page archives? isaacl (talk) 22:50, 24 December 2022 (UTC)

Isaacl, yes, didn't like the list. You can find them through Special:PrefixIndex anyway if you really need them. (but few people would) — Alexis Jazz (talk or ping me) 00:44, 25 December 2022 (UTC)