Wikipedia talk:Ultraviolet/2024/January
![]() | This is an archive of past discussions. Do not edit the contents of this page. If you wish to start a new discussion or revive an old one, please do so on the current talk page. |
Using Ultraviolet tool on id Wiki
If I want to install and make use of this tool on id Wiki, should I simply paste {{subst:lusc|User:10nm/beta.js}}
or I need to make certain modification prior to saving it?
One more thing to ask, when I was redirected from Ultraviolet install page to my common.js to do installation manually on en wiki, I already have this text on it: "importScript('User:10nm/beta.js'); // Backlink: [[User:10nm/beta.js]]
".
Is it part of this tool or I can delete it? Ultraviolet states that "If the page doesn't exist or is empty, paste the code you just copied into the empty code editor. Otherwise, just paste the code on a new line below all other userscripts you have loaded." Is that code what it refers to? Natsuikomin (talk) 10:31, 10 January 2024 (UTC)
- Moreover, do I need to include
importScript('User:10nm/beta.js'); // Backlink: [[User:10nm/beta.js]]
in my common.js on id wiki as well? Natsuikomin (talk) 10:43, 10 January 2024 (UTC)- Hi @Natsuikomin! If you want to use Ultraviolet on another wiki, you will have to load a version of the Ultraviolet userscript (which you can create under your own user, or load the enwiki version with
{{subst:lusc|en:User:10nm/beta.js}}
. You'll also need to make a local copy of WP:Ultraviolet/configuration.json on the wiki. ―sportzpikachu my talkcontribs 11:49, 10 January 2024 (UTC)- What about the importScript() function? Natsuikomin (talk) 12:10, 10 January 2024 (UTC)
- That can't handle interwiki scripts (I think). — Qwerfjkltalk 19:24, 10 January 2024 (UTC)
- I wasn' talking about that. Please read my first comment right below the heading. But I'm indeed wondering about the possibility of interwiki script, Thanks for replying. Natsuikomin (talk) 21:56, 10 January 2024 (UTC)
- That can't handle interwiki scripts (I think). — Qwerfjkltalk 19:24, 10 January 2024 (UTC)
- Will Ultraviolet team make it possible to have this tool available on any language Wikipedia just like User:Evad37/OneClickArchiver do in the second method? Natsuikomin (talk) 00:24, 11 January 2024 (UTC)
- @Natsuikomin - we're working on inter-wiki portability for the full release of UV. There will be options for i18n and also l10n. Phabricator task: T348470 ―sportzpikachu my talkcontribs 10:00, 11 January 2024 (UTC)
- What about the importScript() function? Natsuikomin (talk) 12:10, 10 January 2024 (UTC)
- Hi @Natsuikomin! If you want to use Ultraviolet on another wiki, you will have to load a version of the Ultraviolet userscript (which you can create under your own user, or load the enwiki version with
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)
- Hmm, what features needed are missing from Codex? It is also stable and not in beta; in fact it's at 1.2 already.
They are similar, but AntiVandal seems vastly superior due to its queue that is ranked in decreasing severity. Aaron Liu (talk) 12:44, 3 January 2024 (UTC) - I think that Codex is not currently in beta version, the project page https://doc.wikimedia.org/codex/latest/ doesn't indicate this. The use of Codex is a long-term visionary endeavor. Plantaest (talk) 23:16, 3 January 2024 (UTC)
- Hmm, what features needed are missing from Codex? It is also stable and not in beta; in fact it's at 1.2 already.
- @Plantaest: There's too much user experience friction with shifting from one UI framework to another. They have different widgets/components, design principles, and capabilities. UV was originally made with a theming system to enable a "Wikimedia" theme to eventually be added in, but it's additional workload and maintenance load (that could turn into technical debt) for us and it's currently best if we stick to what we use now than expend pre-1.0 effort on switching libraries. Chlod (UV • say hi!) 03:19, 4 January 2024 (UTC)
- Ok, I understand. Best wishes to your team. Plantaest (talk) 04:06, 4 January 2024 (UTC)
- The team should use Codex. I think it's better than Material. Plantaest (talk) 21:58, 2 January 2024 (UTC)
- The grant proposal is on meta at m:Grants:Programs/Wikimedia Community Fund/Rapid Fund/Development of the Ultraviolet counter-vandalism userscript (ID: 22449356) for those curious. Feel free to leave any feedback there! ―sportzpikachu my talkcontribs 16:50, 7 January 2024 (UTC)
- I wonder if it is because UV is a legacy system already despite being in beta for four years, including one year as RedWarn...
- I think Codex/OOUI is a good step forward for RW/UV. It might be able to usurp Twinkle and maybe even have cross wiki compatibility! :D Awesome Aasim 05:09, 24 January 2024 (UTC)
- No comment on the viability of implementing this (I have no idea what I'm talking about anyways), but I can't tell you how much help it would be to editors who work do cross-wiki work to have a reliable global CV suite even remotely comparable to the tools we have on enwiki. Also, consider that the WMF is likely to give the grant application significantly more attention if it's pitched as a tool for the global community rather than just for us enwiki snobs. (/j) —TechnoSquirrel69 (sigh) 05:17, 24 January 2024 (UTC)