Wikipedia talk:Ultraviolet

Bug Report Feature Request

Going Ultraviolet

Hello there! By now, you may have already noticed that RedWarn hasn't had any major updates since 16.1 (released on March 8, 2021), and we've only been sending out some minor patches and bugfixes since then. In that time, we've been hard at work developing a complete rewrite of the project since September 2020, and we've finally done enough work to be able to release a beta version of this rewrite soon.

Because of many different factors, including the rewrite having diverged so much from the original code, the team has decided to give this version of RedWarn a brand new name. We've decided to call it Ultraviolet; electromagnetic radiation found past the opposite side of red on the visible light spectrum. Releases of the userscript will eventually be available on user pages of 10nm — 10 nanometers being the smallest possible wavelength of ultraviolet light. We're still working on getting a user-friendly version of Ultraviolet available; we ask for your patience as we get closer to releasing more feature-filled builds of Ultraviolet.

Is this a new script or just a rebranded version of RedWarn?

In essence, Ultraviolet is a rewritten version of RedWarn. That said, most of the original code has been removed or replaced. Significant work has also been done to make the process of using the script smooth and universal, removing nearly all of the UI-related bugs experienced in the current version of RedWarn. In addition, we're also working on Safari support, mobile usability, internationalization (other languages), wiki-specific configurations, a dark mode, and a lot more features that make Ultraviolet just work out of the box.

What this means for RedWarn

For a while, we've been holding off on development of further versions of RedWarn in favor of the rewrite. Expanding on the current code is a feat that would take a significant amount of time, on par with just rewriting the script itself. For now, RedWarn will still be supported and given security updates and patches for minor bugs. Once Ultraviolet has been completed and integrates all the features of RedWarn, we will decommission RedWarn and ask users to switch to the new userscript.

What this means for you, as a user

Stick to RedWarn while we're still working on implementing all the features of RedWarn into Ultraviolet. Rest assured, we will still provide updates that prioritize user safety and security, so you can still use RedWarn without the fear of compromise. We highly recommend to anyone who does counter-vandalism patrol often to use only RedWarn for now in order to avoid any catastrophic bugs. We're still finishing up on making the script backwards-compatible with your existing RedWarn configuration, after that we'll begin providing beta versions of Ultraviolet, so that anyone who wishes to use Ultraviolet before it has caught up with RedWarn can do so.

You'll be able to keep on using RedWarn until we've made our first release version (i.e. 1.0) of Ultraviolet. After that, we will require you to switch to Ultraviolet from RedWarn, as we will be dropping support for RedWarn. Although this may be a bit of a bother, we ask for your patience in this eventual transition.

What else this means

We'll be moving away from the RedWarn name entirely in the coming months. The team believes it's important to move away from the name, as most of Ultraviolet has been built from scratch and holds little to no resemblance to RedWarn (at least in terms of the code), and due to some other reasons.

This is a big milestone for us as userscript developers, and we hope to have your full support. In case you have any questions or concerns, please feel free to ask us about them below. Thanks!

Written by Chlod, Berrely, Sennecaster, and Remagoxer. Published by Chlod (RW • say hi!) 19:39, 22 February 2022 (UTC).

@Chlod, is there any update on the progress of this? There's no rush, just curious. — Qwerfjkltalk 21:34, 7 December 2022 (UTC)

Hi there, @Qwerfjkl! The developers are currently busy on a few things, me specifically being busy (in recent months) with Deputy, although now that the bulk of the starting work on that has wrapped up, I can start working on Ultraviolet again. In the meantime, we've been doing some background work that'll help us facilitate the move from GitLab.org to Wikimedia GitLab, and we're currently planning how to perform that migration within the near future. Next up on the list of major features up for implementation is a module for marking pages for speedy deletion, so that's on my list of things to research. Hope this answers your question! Chlod (UV • say hi!) 03:31, 8 December 2022 (UTC)

Hi @Chlod, is UV is in full swing operation or still in the process of moving? ♒️ 98TIGERIUS 🐯 21:12, 24 June 2023 (UTC)

I think it's still moving but close to completion, I would advise to remain with redwarn as UV is still in beta and doesn't have all the features of redwarn fully implemented. Zippybonzo | Talk (he|him) 21:52, 24 June 2023 (UTC)

Thanks for the heads up @Zippybonzo. ♒️ 98TIGERIUS 🐯 04:58, 25 June 2023 (UTC)

@98Tigerius: All of our old RedWarn pages have moved already. We just haven't changed the top banner since UV doesn't have a 1.0 release yet. Right now, UV is already equipped with a lot of the basic features, and it's just a matter of porting all of the old features back in (and for MAT and Quick Templates, redesigning the process entirely). Implementing these would benefit a sprint, but it's slowly been just me doing the work as other members of the team have been busy with real life things (and so have I). I don't like giving timetables when I don't know if I can fulfill it, so there's no estimations on when UV 1.0 will be out. @Zippybonzo's right in that UV still lacks features, but if you don't use anything in Wikipedia:Ultraviolet/Compatibility matrix labeled "Not yet", then switching over shouldn't be an issue. Ultimately it's up to you on whether you'd like to switch or not. Chlod (UV • say hi!) 07:37, 25 June 2023 (UTC)

Great and thanks a lot for giving more info about the progress of UV. I already used UV for short period but switch back to RW. You are doing well and all development team, keep it up! ♒️ 98TIGERIUS 🐯 13:50, 25 June 2023 (UTC)

Correct the gitlab link in the script

Moved from Wikipedia talk:Ultraviolet/2023/January § Correct the gitlab link in the script

 – Aaron Liu (talk) 02:09, 20 November 2023 (UTC)

Ultraviolet - Issue

---

resultdone

---

Assignee

Chlod (WM GitLab)

---

Last updated

12:54, 26 January 2023 (UTC)

Moved from User talk:10nm/beta.js

−

* https://gitlab.com/ultraviolet/ultraviolet/

+

* https://gitlab.wikimedia.org/repos/10nm/ultraviolet/

The repo has changed. Aaron Liu (talk) 18:40, 7 January 2023 (UTC)

Already done in code, but not yet deployed. Expect the change in a short while, as a quick change for AIV is on the way. Chlod (UV • say hi!) 03:08, 26 January 2023 (UTC)

@Chlod When would this be deployed? Aaron Liu (talk) 02:10, 20 November 2023 (UTC)

@Aaron Liu:  Done! Chlod (UV • say hi!) 05:58, 20 November 2023 (UTC)

Thanks! Aaron Liu (talk) 12:40, 20 November 2023 (UTC)

I would suggest some fixes and a template addition

I would like to suggest some suggestions to Ultraviolet:

For the fourth warning, the Warning word should be lowercase (Final warning), change "ONLY Warning" to "Only warning", add the only warning template for {{uw-attempt4im}} (4im user warning template when a user excessively triggers edit filters), and please remove the extra period and space (as it shows here) when a user is reporting a vandal to AIV/UAA using Ultraviolet. Thanks. – 64andtim ^{(talk to me!)} 05:24, 29 November 2023 (UTC)

I'll add in {{uw-attempt4im}} in a bit, but the others may require code changes. The extra period and space is caused by not having a reason specified. Unfortunately, this may need a bit of work since the removal of the period and space has to work with any language. Will get to those later on. Chlod (UV • say hi!) 07:21, 4 December 2023 (UTC)

RedWarn not working on Firefox?

So I recently switched to Firefox from Opera GX aaaaaand of course RedWarn isn't seeming to work. I'm not exactly sure what could be going wrong. ― Blaze Wolf^Talk_{blaze__wolf} 22:48, 1 December 2023 (UTC)

Nevermind it's suddenly working now. I dunno what it was. ― Blaze Wolf^Talk_{blaze__wolf} 22:59, 1 December 2023 (UTC)

This has been long resolved, but for the record, RedWarn was down from 22:22 to 22:49 on December 2 due to issues with Toolforge. We depend on Toolforge to distribute libraries used by the script, hence the downtime. Chlod (UV • say hi!) 07:52, 4 December 2023 (UTC)

Yep you told me that on the Discord server I believe. ― Blaze Wolf^Talk_{blaze__wolf} 12:38, 4 December 2023 (UTC)

AI warning templates

I propose adding {{uw-ai1}} - {{uw-ai3}} to the warning templates menu for UW and RW (if possible). Queen of Hearts ❤️ (no relation) 06:23, 4 December 2023 (UTC)

@Queen of Hearts: These are  already in the configuration as "LLM misuse". Search for "AI" also works but it's much lower down the list. Feel free to use those as needed. Chlod (UV • say hi!) 07:46, 4 December 2023 (UTC)

 Self-trout or maybe even  Self-whale... for when a trout just isn't enough. Queen of Hearts ❤️ (no relation) 07:48, 4 December 2023 (UTC)

Update on Ultraviolet

Hello everyone! As you all may know already, Ultraviolet has been in development for 3 years now but still is yet to release a 1.0 version. Quite a few features from the latest version of RedWarn (16.1, released on 7 March 2021) are still not supported in Ultraviolet. This is due to our team being mainly student developers, who have unfortunately had to focus on schoolwork and other commitments.

Because of this, I'm planning on applying for a WMF rapid grant to to release a stable 1.0 version of Ultraviolet with full feature compatibility with RW 16.1 this coming summer. The internal architecture of Ultraviolet will also be updated in order to remove as many external dependencies as possible, only relying on dependencies bundled with MediaWiki. This will speed up the script’s load time and could also improve user privacy and security. Hopefully, the new architecture will be able to be much more understandable by editors who wish to contribute code patches to Ultraviolet.

Here's a list of what's planned, in semi-order of priority:

• Replace Webpack and TSX-DOM with Vite and Vue.js – T348406
  • Use the new Material Web Components library for UI – T348405
• Full feature compatibility with RW 16.1 – #rw_compat
• Implement i18n using built-in mw.message instead of i18next – T348470
  • Integrate TranslateWiki for translation contributions from the community
• Implement unit/integration testing using Playwright – T333548
• Write documentation at WP:UV with any time remaining

I'd like to ask what the community thinks of this proposal. Are there any specific features/areas that you would like me to focus on? Any feedback is appreciated! ―sportzpikachu _{my talkcontribs} 13:43, 24 December 2023 (UTC)

Sounds pretty good! As long is it has feature compatibility it'd be greatly appreciated.
Also, is it possible for there to be an OOUI theme? Material looks kinda jarring among WP for me.
Is it possible for RW to integrate with Wikipedia:AntiVandal? It has a far superior "queue" UI that ranks edits according to their ORES scores IMO. Aaron Liu (talk) 20:28, 29 December 2023 (UTC)

The team should use Codex. I think it's better than Material. Plantaest (talk) 21:58, 2 January 2024 (UTC)

Thanks for the feedback @Aaron Liu and @Plantaest! We'll take a look at integrating AntiVandal, but the current plan for UV has been to integrate with WP:RTRC, which seems to offer similar features.

Codex/OOUI support is not currently planned, since it is still in beta and lacks a lot of the functionality that Material has in comparison. However, we'll keep an eye out for when Codex has the features that UV needs. ―sportzpikachu _{my talkcontribs} 10:19, 3 January 2024 (UTC)

RWTEXT in quick templates aren't replaced unless you type in a textbox

Ultraviolet - Issue

---

Unassigned

---

stateto do

Special:Diff/1192480271 is the result of not filling in any fields that correspond to the quick template's RWTEXT parts. The RWTEXT parts seem to be only replaced if you type in them once, as you can workaround this by typing and then deleting in a field. Aaron Liu (talk) 20:27, 29 December 2023 (UTC)