Wikipedia talk:Ultraviolet/2021/October

Wikipedia:RedWarn/Install nominated for CSD, request deletion
I was unable to tag Wikipedia:RedWarn/Install so please delete it. Kent2121 (talk) 13:34, 26 October 2021 (UTC)
 * The page does not match any CSD criteria you have tagged the page for. Chlod ( RW • say hi!) 13:36, 26 October 2021 (UTC)
 * @Kent2121 What exactly is your rationale? It clearly doesn't meet G1. &#8213; Qwerfjkl  talk  13:37, 26 October 2021 (UTC)

Addition of Welcoming abilities
Hello! I have been using RedWarn a lot and I enjoy using it because of it's ease of use and how quick I can revert edits (faster than Twinkle even!). However there is one thing that bugs me and that is, RedWarn only allows you to warn users upon reverting their edit, even if they hadn't even been welcomed yet. While there isn't a policy that says you must welcome a user before you warn them, I see welcoming a user as seeing their edits in good faith and not biting them. So I propose that if the user does not have a talk page yet, upon reverting their edit with RedWarn, you will have the option to either add a warning to their talk page or welcome them. Another way this could be implemented is to include the Welcome templates in the Warn UI (possibly changing the name to Warn or Welcome). This is a great way to show that we want users to contribute to Wikipedia and could possibly increase the retention of users. Twinkle has already implemented this as a feature (although not in the same sense as I proposed) in which you have the option to welcome a user or warn them, and if they don't have a talk page, while viewing the history of a page, there will be a button that says [welcome] which you can click and welcome the user. Some of the welcome templates even address issues that a warn can be used for, allowing users to realize their mistakes and seeing other things they should look at, instead of only knowing that the one thing they did was wrong and getting a warning for it which places them 1 step closer to getting blocked. ― Blaze The WolfTalkBlaze Wolf#6545 19:42, 4 October 2021 (UTC)
 * @Blaze The Wolf, There is no point in welcoming a vandal, or a spammer etc., otherwise welcoming messages would be sent out automatically. The level 1 warning is supposed to be assuming good faith. &#8213; Qwerfjkl  talk  06:24, 5 October 2021 (UTC)
 * Welcome messages aren't sent out automatically because we don't know who is and isn't a vandal or sock. I myself see it as bad faith to automatically assume every newcomer is a vandal (although i do admit that I always tend to look at IPs edits less carefully than a new user's), and since not every newcomer is a vandal, some may not understand Wikipedia's rules and might think what they're doing is just fine. Yes the warnings do tell them what they did was wrong and (most of the time) link them to the place that tells them why what they did is wrong, but there are a whole bunch of other things they might do wrong in the future if they only receive warning templates, because they only know that one individual thing is wrong. Most welcome templates at least link to a few other places that tell newcomers a bit more about what is and isn't wrong. But like I said, not all newcomers are wanting to contribute constructively. ― Blaze The WolfTalkBlaze Wolf#6545 13:30, 5 October 2021 (UTC)
 * @Blaze The Wolf You can use some quick templates packs to add welcome messages to talk pages. The list is here. &#8213; Qwerfjkl  talk  15:28, 5 October 2021 (UTC)

First time set-up screen not scrollable (Chrome)
I just installed 16.1 and the "First time setup" configuration screen was unfortunately not scrollable for me. I could only see the first few options and the rest were cut off. In order to see the entire config page I had to zoom out in my browser to about 50% and squint. :) I'm on Chrome and can provide further details/screenshot if necessary. Cheers! Mvolz (talk) 12:20, 27 September 2021 (UTC)


 * Quick question - was this on mobile? Rema goxer  (talk) 19:47, 5 October 2021 (UTC)


 * No, on desktop! Mvolz (talk) 19:11, 10 October 2021 (UTC)

Discussion at User talk:SD0001/Making user scripts load faster
You are invited to join the discussion at User talk:SD0001/Making user scripts load faster. ― Qwerfjkl  &#124; 𝕋𝔸𝕃𝕂 (please use&#32; on reply) 18:22, 15 June 2021 (UTC)
 * Well, this is not a problem with RedWarn conflicting with either scriptManager or the script caching code. Rather, some bizarre issue of something else conflicting with RedWarn that may be from the voluminous User:Qwerfjkl/common.js or some browser extension.I couldn't reproduce the issue on my end even after copying all of User:Qwerfjkl/common.js to User:SD0001/common.js, so it's more likely a browser extension(?). – SD0001  (talk) 18:29, 15 June 2021 (UTC)

From the stack trace, one thing that you may to take care of is this: DevTools failed to load source map: Could not load content for https://redwarn.toolforge.org/cdn/css/jquery.contextMenu.min.css.map: HTTP error: status code 404, net::ERR_HTTP_RESPONSE_CODE_FAILURE DevTools failed to load source map: Could not load content for https://redwarn.toolforge.org/cdn/js/jquery.contextMenu.min.js.map: HTTP error: status code 404, net::ERR_HTTP_RESPONSE_CODE_FAILURE DevTools failed to load source map: Could not load content for https://redwarn.toolforge.org/cdn/js/material.min.js.map: HTTP error: status code 404, net::ERR_HTTP_RESPONSE_CODE_FAILURE which was also showing up for me. – SD0001  (talk) 18:32, 15 June 2021 (UTC)


 * @SD0001 I have now tested this on my mobile device, which has no extensions, and still has the same problem. However, I can still edit pages through links like this: https://en.wikipedia.org/w/index.php?title=$PAGENAME$&action=submit and User:BrandonXLF's section editor. &#8213; Qwerfjkl  &#124; 𝕋𝔸𝕃𝕂 (please use&#32; on reply) 20:16, 15 June 2021 (UTC)
 * Control of the Toolforge instance is entirely with Ed, so I can't help with this one. Chlod ( RW • say hi!) 23:10, 15 June 2021 (UTC)
 * This is the error that is preventing me from saving edits (I think): mdlLogic.js:1 Uncaught URIError: URI malformed

at decodeURIComponent at Function.t.EPPyTH (mdlLogic.js:1) at t (mdlLogic.js:1) at Object.mw.loader.load ( :2:180) at Object.preloadDeflate ( :351:854) at :40:348 &#8213; Qwerfjkl  &#124; 𝕋𝔸𝕃𝕂 (please use&#32; on reply) 16:27, 16 June 2021 (UTC)
 * Pinging @Chlod @Ed6767 &#8213; Qwerfjkl talk  07:23, 4 July 2021 (UTC)
 * I'm not sure if I can comment on this issue without knowing the insa and outs. As an official policy I still stand by not supporting other scripts/mods, but will take a look if and when I can. ✨ Ed  talk!  ✨ 20:17, 5 July 2021 (UTC)
 * @Ed6767 The 'edit-not-saving' issue seems to only happen in the 2017 Wiki editor. &#8213; Qwerfjkl talk  10:22, 17 July 2021 (UTC)
 * To do sometime in the future (maybe within this week). Chlod ( RW • say hi!) 09:25, 9 August 2021 (UTC)
 * @Chlod Thanks, I have disabled RedWarn in the meantime; this interferes with a large number of my user scripts. &#8213; Qwerfjkl  talk  19:13, 25 August 2021 (UTC)

The issue should be fixed now. On an unrelated note, this script seems to also be loading links under   on my end (not sure why, <abbr title="https://en.wikipedia.org/w/load.php?lang=en&modules=ext.CodeMirror%2Ccharinsert%2CeventLogging%2CnavigationTiming%2Cpopups%2CwikimediaEvents%7Cext.CodeMirror.data%2Clib%7Cext.CodeMirror.mode.mediawiki%7Cext.centralNotice.geoIP%7Cext.centralauth.ForeignApi%7Cext.centralauth.centralautologin.clearcookie%7Cext.cx.entrypoints.contributionsmenu%7Cext.cx.eventlogging.campaigns%7Cext.cx.icons%7Cext.cx.widgets.callout%7Cext.echo.api%2Cinit%7Cext.uls.common%2Ccompactlinks%2Cinterface%2Cpreferences%2Cwebfonts%7Cjquery%2Coojs%2Csite%7Cjquery.client%2Ccookie%2CtextSelection%2Cui%7Cjquery.uls.data%7Cmediawiki.ForeignApi%2CString%2CTitle%2CUri%2Capi%2Cbase%2Ccldr%2Ccookie%2Cexperiments%2CjqueryMsg%2Clanguage%2Cstorage%2Cuser%2Cutil%2CvisibleTimeout%7Cmediawiki.ForeignApi.core%7Cmediawiki.editfont.styles%7Cmediawiki.libs.pluralruleparser%7Cmediawiki.page.ready%7Cmediawiki.page.watch.ajax%7Cmediawiki.ui.button%2Cicon%7Coojs-ui.styles.icons-editing-styling%7Cskins.vector.legacy.js%7Cuser.defaults&skin=vector&version=g0cos">here's the URL), which throws up an   exception. Perhaps properly handle this exception and load with the original function if that's the case? Chlod ( RW • say hi!) 03:49, 26 October 2021 (UTC)
 * @Chlod don't think that's happening. For mw.loader.load, it only intercepts calls to  which also have ,   and  . –  SD0001  (talk) 04:07, 26 October 2021 (UTC)
 * The offending URL was . It seems like URL-encoded links in   were not accounted for. Chlod ( RW • say hi!) 00:15, 27 October 2021 (UTC)
 * I see. Fixed in Special:Diff/1052058248. – SD0001  (talk) 04:05, 27 October 2021 (UTC)
 * Thanks for fixing this! &#8213; Qwerfjkl  talk  07:15, 26 October 2021 (UTC)