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)

UAA report formatting

Ultraviolet - Issue

---

resultdone

---

Last updated

02:57, 11 September 2023 (UTC)

Looks like there's some missing punctuation in the UAA report template – see this diff, where I reported a username for "Promotional username", with some additional information. I'd imagine that should have come out as "Promotional username. Single contribution so far was..." instead. Box of wolves (feed) 02:34, 11 September 2023 (UTC)

Should be fixed in a few minutes. Chlod (UV • say hi!) 02:43, 11 September 2023 (UTC)

Thanks! Box of wolves (feed) 02:44, 11 September 2023 (UTC)

 Fixed! Let me know if there's still issues. Chlod (UV • say hi!) 02:57, 11 September 2023 (UTC)

You got it. Hopefully I won't have to use it again anytime soon! Box of wolves (feed) 03:01, 11 September 2023 (UTC)

Is RedWarn or UV for me?

I currently use Twinkle and only patrol for vandalism and errors on pages on my watchlist. Should I try one of these tools, or are they mainly meant for people who patrol Special:RecentChanges? (I have had the rollbacker role for years.) Jc3s5h (talk) 14:03, 11 September 2023 (UTC)

Hi @Jc3s5h, RedWarn and UV are both quite similar to Twinkle and aren't just for RC reviewers. Give them both a try, and see which one you prefer :) ✨ Ed talk! ✨ 12:54, 12 September 2023 (UTC)

If I want to try UV, do I have to disable Twinkle first? Jc3s5h (talk) 13:38, 12 September 2023 (UTC)

@Jc3s5h, No. They might have overlapping features though. — Qwerfjkltalk 20:33, 12 September 2023 (UTC)

UV not working

I installed Ultraviolet (upgraded from RedWarn), but when I try to use it on Chrome, I the error InvalidStateError: Failed to execute 'transaction' on 'IDBDatabase': A version change transaction is running. in the JavaScript console and the page freezes up. However, UV seems to load properly Microsoft Edge. Rusty4321 ^{talk contributions} 00:55, 16 September 2023 (UTC)

Hi, @Rusty4321! Could you provide the full text of the error? This will help pinpoint the exact part of the code causing the issue. Chlod (UV • say hi!) 01:11, 16 September 2023 (UTC)

@Chlod Sure!

The full error message is below (in the collapsed content). It is spammed over and over in the console and the script does not load.

Extended content

AppLog.ts:65 [Ultraviolet 0.1.5] [ERROR] InvalidStateError: Failed to execute 'transaction' on 'IDBDatabase': A version change transaction is running. log @ AppLog.ts:65 error @ AppLog.ts:142 (anonymous) @ UltravioletIDB.ts:123 (anonymous) @ tslib.es6.js:76 l @ tslib.es6.js:72 transaction @ ultraviolet.js:33 (anonymous) @ UltravioletIDB.ts:184 (anonymous) @ tslib.es6.js:76 l @ tslib.es6.js:72 (anonymous) @ UltravioletIDB.ts:181 (anonymous) @ UltravioletIDB.ts:181 (anonymous) @ tslib.es6.js:76 l @ tslib.es6.js:72 runRequest @ ultraviolet.js:33 (anonymous) @ UltravioletIDBObjectStore.ts:73 (anonymous) @ tslib.es6.js:76 l @ tslib.es6.js:72 get @ ultraviolet.js:33 (anonymous) @ API.ts:220 (anonymous) @ tslib.es6.js:76 l @ tslib.es6.js:72 loadGroupNames @ ultraviolet.js:33 (anonymous) @ API.ts:140 (anonymous) @ tslib.es6.js:76 l @ tslib.es6.js:72 init @ ultraviolet.js:33 (anonymous) @ Ultraviolet.ts:204 c @ tslib.es6.js:73 Promise.then (async) u @ tslib.es6.js:75 c @ tslib.es6.js:73 Promise.then (async) u @ tslib.es6.js:75 c @ tslib.es6.js:73 Promise.then (async) u @ tslib.es6.js:75 (anonymous) @ tslib.es6.js:76 l @ tslib.es6.js:72 initialize @ ultraviolet.js:28 (anonymous) @ Ultraviolet.ts:281 (anonymous) @ tslib.es6.js:76 l @ tslib.es6.js:72 start @ ultraviolet.js:28 6463 @ Ultraviolet.ts:364 __webpack_require__ @ bootstrap:19 (anonymous) @ startup:4 __webpack_require__.O @ chunk loaded:23 (anonymous) @ startup:5 (anonymous) @ ultraviolet.js:33

Rusty4321 ^{talk contributions} 01:58, 16 September 2023 (UTC)

Thanks, @Rusty4321! I've pushed a change that should alleviate this, but I can't fully reproduce this on my end since this is a pretty rare race condition. Please give it a try, and tell me if it didn't work so I can try something else. Chlod (UV • say hi!) 02:16, 16 September 2023 (UTC)

@Chlod It's still happening, but suspect it may be something on my end. I'll double-check my common.js and rwconfig.json. Rusty4321 ^{talk contributions} 18:00, 24 September 2023 (UTC)

@Chlod It's happening still. By the way, I'm using Google Chrome on macOS, which might help with debugging. Rusty4321 ^{talk contributions} 18:09, 24 September 2023 (UTC)

Hi, @Rusty4321! Sorry for the late response. Please run the following in your browser console (⌥ Option+⌘ Cmd+J).

window.indexedDB.deleteDatabase("ultravioletDB").onsuccess = () => console.log("Database deleted.");

This will delete the Ultraviolet data stored on your local browser, allowing it to rebuild. Ultraviolet does not need to be running or loaded. Let me know if this works. Chlod (UV • say hi!) 16:07, 26 September 2023 (UTC)

@Chlod I don't know what it is with this issue, but it just doesn't seem to work. I've cleared all my browser cookies, cache, and data for all Wikimedia Foundation sites (at least, if that's what the "Clear Data" button does), but it still doesn't work. Rusty4321 ^{talk contributions} 03:35, 27 September 2023 (UTC)

I think I got it fixed. Seemed like TamperMonkey or an adblocker were interfering. Disabled tampermonkey and the ad blocker. Rusty4321 ^{talk contributions} 21:54, 13 October 2023 (UTC)

vandalism4 warning filed multiple times

Ultraviolet - Issue

---

resultwon't fix

Please write your message here. RecycledPixels (talk) 09:27, 20 September 2023 (UTC) A vandal, Asie kij (talk · contribs · deleted contribs · nuke contribs · logs · filter log · block user · block log), that I had watchlisted, received multiple additional final warnings from a user of your script, and after the vandal had already been reported to AIV. Apparently, your script was able to identify the fact that the vandal had been warned multiple times in order to issue a uw-vandalism4 warning, but repeatedly failed to notice that the vandal had already been given that warning, and failed to prompt the user of your script to report to AIV, which would have been embarrassing, since the AIV report was already there. RecycledPixels (talk) 09:27, 20 September 2023 (UTC)

Hi, @RecycledPixels! I take it that you're reporting this on behalf of @GMH Melbourne after the discussion you started on their talk page. RedWarn already informs the user if a level 4 warning has been given in its warning dialog (and, in fact, encourages the user to file an AIV report instead), and also prevents a user from filing duplicate AIV reports. Ultraviolet, its successor as RedWarn is no longer actively worked on, also does this.

It seems GMH Melbourne has configured RedWarn to automatically warn the user after performing a revert, which bypasses the warning dialog under the assumption that the editor knows what they're doing. In this situation, it did exactly as it was programmed and exactly as the user had configured it; no defect or bug occurred. My suggestion for GMH Melbourne would be to disable automatic warning or to be more vigilant when patrolling. Vandalism patrollers are expected to exercise caution as part of their use of the tools provided to them. This includes noticing the same page showing up in RecentChanges, and remembering that the user they have reverted the edits of. Chlod (UV • say hi!) 10:55, 20 September 2023 (UTC)

About adding review log entries

Ultraviolet - Issue

---

T349141

View on Phabricator

---

stateto do

typefeature

Hey there! I currently use RedWarn to review pending changes, and I have a suggestion for the Ultraviolet team as you work on the 1.0 release. I'd really appreciate if the script added entries to the review log when performing a rollback in the pending changes view. Currently, an entry is added only when the big red X "revert changes" is clicked, not during regular rollbacks. I definitely think it'd help reviewers keep track of their activity, and keeps all of the information in one place at Special:Log. I believe Twinkle already does this. Let me know if you have any questions! —TechnoSquirrel69 (sigh) 04:57, 10 October 2023 (UTC)

Hi TechnoSquirrel69, I've opened a issue for this feature on phabricator -- Asartea ^{Talk | Contribs} 20:44, 17 October 2023 (UTC)

Update on UV

Hello! I'm curious what the status of Ultraviolet is right now as I haven't seen any updates for it in a while. I'm assuming you guys are just busy outside of Wikipedia which is fine, I'm merely curious as to how things are going. ― Blaze Wolf^Talk_{blaze__wolf} 19:07, 17 October 2023 (UTC)

Hey @Blaze Wolf, thanks for the inquiry! It is true that many of us are busy IRL, but I've started to work on Ultraviolet more during these past few weeks. You can see activity happening on our phabricator project and also on our Gitlab. As always, you can let us know if you have any feedback regarding Ultraviolet/RedWarn and we'll do our best to get back to you. We're also welcoming any editors who know a bit of Typescript to contribute to the UV codebase! You can always reach out to us through this talk page or the other methods on WP:Ultraviolet/Contact. ―sportzpikachu _{my talkcontribs} 19:23, 17 October 2023 (UTC)

Woah someone who isn't Chlod answering questions related to UV. I forget that you guys have places where people can view progress that is happening. Thanks for the update! ― Blaze Wolf^Talk_{blaze__wolf} 19:38, 17 October 2023 (UTC)