Wikipedia talk:Ultraviolet/2022/February

Page contents not supported in other languages.
From Wikipedia, the free encyclopedia

Shift right click context menu

RedWarn Web - Issue
#88
resultdone
prioritymild
typebug
Assignee

There is a feature in RedWarn where you can press and hold shift while right clicking on any link that leads to any user related page and it will bring up a custom context menu that has some useful features. This usually works totally fine.

But I've noticed an instance where it does not. When I am at Special:AbuseLog looking for vandalism, I'd like to be able to right click on users to use the context menu in various ways. This works totally fine with IPs, and totally fine with users that have a userpage (not redlinked). Users without a user or talk page, on the other hand, seem to break it. Pressing shift and right clicking on a redlink related to a logged in account will result in nothing. Oddly enough, though, it works on the contribs link, even if that's red too.

tl;dr trying to use the shift right click menu on the user page or talk page of users without said pages will fail to open the menu. The contribs link works fine regardless, though. Thanks! ― Levi_OPTalk 20:20, 12 January 2022 (UTC)

Hi, Levi OP! Sportzpikachu is working on a fix for the issue you described. We'll give you a ping once the issue has been fixed. Thanks! Chlod (RW • say hi!) 00:51, 17 January 2022 (UTC)
 Fixed in Special:Diff/1070362592. Chlod (RW • say hi!) 03:05, 7 February 2022 (UTC)
(edit conflict) @Levi OP: Fix has been completed and deployed with the help of Chlod. Thanks for helping us find this bug! ―sportzpikachu my talkcontribs 03:06, 7 February 2022 (UTC)

CSD and XfD in RedWarn

I want to request a feature that when CSD and XfD tagging, users can select opt-in or opt-out an option to notify page creator and save their record in userspace CSD log and XfD log in their preferences. Vitaium (talk) 12:33, 12 February 2022 (UTC)

Hi, Vitaium! This is definitely a planned feature, and we'll be actively working towards implementing it in the coming months. The RedWarn team is currently reorganizing so we're not actively implementing new features (until starting later this month), but it will eventually be implemented soon. Chlod (RW • say hi!) 12:35, 12 February 2022 (UTC)

Rollback links

Hi! I just turn off the Twinkle rollback links in diff pages, so RedWarn rollback links are only there. But the RedWarn rollback links disappeared also. How to fix it? —Ctrlwiki (talk) 00:50, 13 February 2022 (UTC)

@Ctrlwiki:  Fixed with Special:Diff/1071511566. Chlod (RW • say hi!) 01:20, 13 February 2022 (UTC)
Thanks chlod. —Ctrlwiki (talk) 02:44, 13 February 2022 (UTC)

macOS Monterey

RedWarn Web - Issue
Unassigned
stateto do

Is there a known issue with macOS Monterey 12.0.1? I’m unable to use RedWarn since getting a new MacBook Pro. The pop-up window that creates the warning text no longer has visible OK/Cancel buttons, and is not scrollable. The buttons and some of the text seem to have been lost outside the edges of the window. I’m using Firefox 95.0.2. MichaelMaggs (talk) 16:22, 10 January 2022 (UTC)

@MichaelMaggs, I use Chrome on MacOS 12.1 on an M1 Macbook Air and don't have any issues, but the issue could be because the MacBook Pro may scale content differently and RedWarn does have scaling issues that are being worked on by the current development team. As an interim solution, you might want to try using the zoom in/out feature in Firefox and see if that lets you see the buttons. ✨ Ed talk! ✨ 23:53, 11 January 2022 (UTC)
Thanks Ed, zooming out x4 in Firefox then zooming back in by the same amount is indeed a workaround. I'll do that for now. MichaelMaggs (talk) 19:35, 12 January 2022 (UTC)
Just checking whether this has been noted by the RedWarn team as no issue template has yet been added here. MichaelMaggs (talk) 15:43, 19 January 2022 (UTC)
Apologies for the wait - we've taken note of this issue and will hopefully get to it soon. Remagoxer (talk) 18:12, 19 January 2022 (UTC)
Hi, I see that this section now has a box saying "won't fix". That's concerning to me, as it no doubt will be to everyone else who contributes to Wikipedia using a 2022 MacBook Pro. The suggested 'workaround' is so clunky and difficult, requiring scrolling and at least eight mouse clicks, as to make RedWarn on the laptop no longer a feasible option. I wonder whether there's a discussion about this somewhere that I can contribute to? I can't see that the issue even made it into GitLab, though I may have missed it. MichaelMaggs (talk) 11:37, 15 February 2022 (UTC)

Issues with template tool "Not using edit summary for more experinced users"

RedWarn Web - Issue
resultdone

Hello- Two issues with the "Not using edit summary for more experinced users" tool:

  • The title has a typo in the word "experienced"
  • Populating the "Additional info" line produces nothing in the resulting message, at least in my experience. I can see that in the preview box below that, we have the option to add a note before or after the template message, but that is different from the behavior of other template tools I have used. (Note also that the preview box is not identified as such). Eric talk 14:50, 16 February 2022 (UTC)
Can confirm both issues. I am also adding that selecting a related page also results in nothing the message changing, meaning that the additional info box and related page box are broken with that message. ― Blaze WolfTalkBlaze Wolf#6545 14:57, 16 February 2022 (UTC)
@Eric and @Blaze Wolf:
  • I've fixed the typo with this edit
  • The issue with the aforementioned template is that, unlike other standardised warning templates that support additional text in the unnamed, third parameter, {{Uw-editsummary2}} requires you to add it in the |more param, which isn't supported. You can see this issue in Twinkle as well. I'll see if I can put it an edit request to hopefully fix this.
— Berrely • Talk∕Contribs 16:53, 16 February 2022 (UTC)
Thanks, Berrely! Eric talk 17:41, 16 February 2022 (UTC)
PS- Can it take some time for your spelling change to take effect? I'm still seeing the typo when I go to invoke the tool. No big deal, just curious. I logged out and hit Ctrl-F5 before my second attempt just to be sure. Eric talk 17:47, 16 February 2022 (UTC)
Eric apologies that I can't check since I'm on a beta, but if I recall correctly there should be a preferences tabs labelled "Warnings" or the like where there is an option to reload warnings from the database. — Berrely • Talk∕Contribs 18:36, 16 February 2022 (UTC)
I don't see that, but don't worry, it's not a big deal! Eric talk 19:42, 16 February 2022 (UTC)
@Eric: I see a button under Warnings, "Clear changes and sync with public database". Have you tried that? ― Qwerfjkltalk 20:07, 16 February 2022 (UTC)
Yep, that's it ^^ — Berrely • Talk∕Contribs 20:08, 16 February 2022 (UTC)
Oops...RedWarn preferences! Light dawns on Marblehead... Thanks to you both, and let's just keep this quiet, ok? Eric talk 21:32, 16 February 2022 (UTC)

RedWarn menu's unusable with Dark mode

RedWarn Web - Issue
resultnext major update

Hello! So recently, SkyeWolf369 pointed out an issue with RedWarn. When you use Wikipedia's dark mode, the buttons for RedWarn turn white so that you can see them, however the text in the menus associated with those buttons also turns white making it impossible to actually see anything in the menus when using RedWarn in Wikipedia's dark mode. A solution would either be to (somehow) keep the text from changing to white if it's detected you are using dark mode on Wikipedia, or turn the menus black so that the text is visible when using dark mode. ― Blaze WolfTalkBlaze Wolf#6545 15:31, 17 February 2022 (UTC)

The user has said they solved it by using this:
dialog#dialogEngineDialog {
background-color: black;
}
― Blaze WolfTalkBlaze Wolf#6545 15:46, 17 February 2022 (UTC)
I just found the HTML element for the dialog box then set the background color to black. SkyeWolf369 (talk) 15:49, 17 February 2022 (UTC)
Hi, Blaze Wolf! Unfortunately due to the way dialog boxes are currently implemented, there's no easy solution to this that doesn't look bad (i.e. lack of contrast, images not changing colors, etc.). We're working on fully supporting dark mode in a future update, but can't dedicate resources to fixing this right now. Chlod (RW • say hi!) 09:24, 18 February 2022 (UTC)
Thats ok I will just use my fix then if its ok with yall. SkyeWolf369 (talk) 13:09, 18 February 2022 (UTC)
ALright sounds good. Glad to know that you're at least going to support it in a later update. ― Blaze WolfTalkBlaze Wolf#6545 16:33, 18 February 2022 (UTC)

Question about Ultraviolet

Hello, RedWarn developers.

In this confusing time, I’ve decided to ask these few questions about Ultraviolet.

  1. Will Ultraviolet remain as a user script, and not a separate file like Huggle?
  2. If I continue to use RedWarn, then is it just an outdated version or is it automatically redirected to Ultraviolet?
  3. Will the script be available as User:10nm/.js or User:10nm/Ultraviolet.js?

Thank you. — 3PPYB6 — TALK — CONTRIBS — 21:52, 22 February 2022 (UTC)

My guess is the answer to 2 will be that it will be an outdated version, considering there's a userbox for using Ultraviolet and Redwarn together. ― Blaze WolfTalkBlaze Wolf#6545 22:04, 22 February 2022 (UTC)
Hi @3PPYB6! To answer your questions, (1) yes, Ultraviolet remains a userscript, (2) if you still choose to use RedWarn after Ultraviolet is released, you can still keep using RedWarn, although we won't be bringing any more updates or security patches to the script, potentially putting you at risk, and (3) User:10nm/.js. Chlod (RW • say hi!) 22:54, 22 February 2022 (UTC)

Ultraviolet beta testers when?

I understand that it's in very early beta now so it would unwise to give the public access to it. But I was just wondering when the project will be accepting beta testers (that I suppose may know how to safely test out stuff in their own test environment). I ask this of course because I'm interested and feel like I might be able to help out since I managed to help solve a small bug with RW earlier. So how long do we need to wait? Satricious (talk) 09:18, 23 February 2022 (UTC)

We're currently working on a few things (including preferences) but hopefully proper beta testing will be able to start very soon. Stay tuned for updates :) Remagoxer (talk) 09:26, 23 February 2022 (UTC)
Alright, I'll be waiting. Good luck to you and the rest of the team! :^) Satricious (talk) 09:46, 23 February 2022 (UTC)

RedWarn vs Ultraviolet

What is the difference between RedWarn and Ultraviolet? —Ctrlwiki (talk) 11:51, 21 February 2022 (UTC)

@Ctrlwiki Features comparison is here. You can read more about the rename to Ultraviolet here and here. Maybe I missed out something, but anyway those linked links are what I have read about. — Paper9oll (🔔 • 📝) 14:44, 21 February 2022 (UTC)
Ctrlwiki we're currently working on the transition and we'll publish an announcement when necessary :) For now, it's best not to use Ultraviolet, as it is a beta. — Berrely • Talk∕Contribs 19:22, 21 February 2022 (UTC)
You all will rename the RedWarn to Ultraviolet, is that what you all mean? If not, if ultraviolet is already published, can I still use RedWarn? And why other RedWarn users are already in RW 17, but others still 16.1—Ctrlwiki (talk) 23:52, 21 February 2022 (UTC)
And one thing I noticed, Ultraviolet is written in Typescript, although I don't have any idea in programming language, but Chrome doesn't support Typescript only JS. So probably Ultraviolet won't work on Chrome. Is that right? —Ctrlwiki (talk) 00:07, 22 February 2022 (UTC)
Typescript compiles to JavaScript if I'm not mistaken so I don't think a tool's source code being written in TS would affect its compatibility with major web browsers. -Liancetalk/contribs 04:41, 22 February 2022 (UTC)
@Ctrlwiki, my understanding is yes, you'll still be able to use RedWarn and Ultraviolet is the new name for RedWarn 17. Regarding TypeScript, it is compiled down into JavaScript that the browser can run and they have also been able to add Safari support. There's a good but quite technical video on YouTube with an explanation and its benefits here. There seem to be some minor misconceptions regarding the terms of the license that should have been cleared up with me, but I did write the license with a rename in mind and am happy to see that a release is on the horizon and a new name has been considered and I look forward to use UV into the future and I hope you do too :) ✨ Ed talk! ✨ 15:15, 22 February 2022 (UTC)
@Ed6767: so it means, I can still be able to use Ultraviolet written in Typescript using Google chrome? —Ctrlwiki (talk) 00:17, 23 February 2022 (UTC)
@Ctrlwiki, yep as the TypeScript is converted into JavaScript for the browser :) ✨ Ed talk! ✨ 16:38, 23 February 2022 (UTC)

"Saving message..." dialog does not go away after submitting warning unless ESC is hit

Hi there, I just wanted to report some potentially odd behavior. I do not know if this is the intended behavior and I have not tried investigating this much so I am not filing this as a bug report.

Context: I recently got rollback rights, and set my "Rollback method" (preferences) as "Rollback". (Also, my dialog animation is the default option if that's helpful). Note that I did not face this issue prior to getting rollback rights and setting my preferences as such.

Actual behavior: After reverting some vandalism (which works), I got prompted to select a warning message as usual, and after sending out the warning, the "Saving message..." dialog remains and does not go away UNLESS I hit escape. The warning message does get successfully sent out to the user though. I do not get redirected to the user's talk page.

Expected behavior: Revert, select warning message, send it out, "Saving message" dialog appears until the message gets successfully sent out, then get redirected to talk page of the warned user.

JavaScript logs: Nothing unusual in my opinion. (image)

(Note: You might think the dialog remains because the warning message being sent out to the user is facing issues (connection issues, etc..) but no, the warning does get sent out to the user. Despite this, the dialog still remains)

(Note 2: I do not need to hit escape for the message to get sent out. The dialog appears, the message gets sent out while the dialog is up, and the dialog still remains up even after the message has been successfully sent out)

I have not tried looking more into this as I am a bit busy today but I just thought I'd post this to see if anyone else is facing any of these issues, or if any devs can reproduce this with the information I've given so far. Thanks. Satricious (talk) 05:44, 15 February 2022 (UTC)

Same here. I am facing the same issue. I had also posted a query earlier. Kpddg (talk • contribs) 06:53, 15 February 2022 (UTC)
Well I certainly am blind for not seeing that! Satricious (talk) 15:06, 15 February 2022 (UTC)
NOTE TO DEVS (potential fix): I found some time to investigate this.
I feel like the culprit is on User:RedWarn/.js line 2214: if (callback != null) { callback(); return; };. (or rather, /src/js/info.js#L685)
I suspect that the return statement must be removed. Once the callback function has been executed, there will be no way for the code to reach the rest of the handleFinish() function. And I don't think the callback function takes care of anything that handleFinish does? (I think the only use of callback is on line 5130?).
I did something similar to what I described above (I was too lazy and just removed line 2214 completely lol) and it works :) Satricious (talk) 15:08, 15 February 2022 (UTC)
@Satricious: Hi, thanks for reporting this issue! I've looked into it and that line should not affect anything apart from multiAct, which it does not seem you are using. Addtionally, having a return; statement after the callback should not cause any problems as it is meant to stop the code afterwards from running. Do you have any diff links of reverts/warns that this may happen at? Additionally, please try clearing your cache AND localStorage, as redwarn stores some UI data there. Thanks! ―sportzpikachu my talkcontribs 03:06, 16 February 2022 (UTC)
@Sportzpikachu: Of course, I'll do that and get back to you. But before that, could you maybe tell me how I could more effectively setup a 'test'-like environment to debug stuff? It takes a bit of time for me to find vandalism, quickly open up my JS console and make runtime changes to the functions and then carry on with the reversion (usually someone steps in before me, so I carry out my rather questionable 'tests' in my sandbox). You asked for diffs, all the rollbacks in my sandbox (except for the last one) have faced this issue but I don't really know how you would get any useful information just from diffs alone. Satricious (talk) 03:26, 16 February 2022 (UTC)
@Satricious: Thanks! I personally warn my alt (User:Sportshead) on my sandbox. I asked for diffs because sometimes due to encoding issues with Unicode characters UI might crash. If it is happening still on your sandbox, then it shows that unicode is not the factor. I'll look into it more, thanks! ―sportzpikachu my talkcontribs 03:28, 16 February 2022 (UTC)
@Sportzpikachu: That's really helpful. I'll continue to test this later today (busy student life lol) and let you know. But I'll give you this, I just updated and rebooted my system, did a fresh install of chromium (should take care of clearing your cache AND localStorage and logged into this account, and proceeded with a revert, and I encountered this exact issue. Quite confusing... Satricious (talk) 04:18, 16 February 2022 (UTC)
@Satricious: Interesting. I'll attempt a reproduction during my lunch break (in 20 minutes). ―sportzpikachu my talkcontribs 04:37, 16 February 2022 (UTC)
@Sportzpikachu: Hey, I'm sorry, I was wrong! I think I might have figured it out. Actually, when I removed that line (which you are correct about not being affected unless multiAct is used), I actually did a minor refactor of the code just cause I saw a few things I thought could be improved, one refactor seems to have fixed this error: namely, In here (gitlab), I changed this to this, and it worked! I just removed the handleFinish() out of the if statement since it looks like it needed to be executed anyway.
(EDIT: to be clear, there is no need to remove the line that I did that messed with the callback, just factor out the handleFinish function and it should work) Satricious. (talk) 05:24, 16 February 2022 (UTC)
I'm not very well-versed with the code, so can you help out with what needs to be fixed? Am still facing the issue. Kpddg (talk • contribs) 08:36, 16 February 2022 (UTC)
@Kpddg and Satricious: Hello, thanks for the feedback! I've updated the code with Satricious' fix and it should be onwiki soon. Thanks! ―sportzpikachu my talkcontribs 08:51, 16 February 2022 (UTC)
Okay thank you :) Kpddg (talk • contribs) 08:53, 16 February 2022 (UTC)
Quick update, unfortunately due to some issues with our continuous deployment script logging into the bot account the script isn't able to update just yet. I'll notify both of you once we are able to resolve the issue. ―sportzpikachu my talkcontribs 09:05, 16 February 2022 (UTC)
 Done here @Kpddg, Satricious. Thank you for your feedback! ―sportzpikachu my talkcontribs 09:25, 16 February 2022 (UTC)
Thanks @Sportzpikachu and Satricious. It is fine now! Kpddg (talk • contribs) 09:47, 16 February 2022 (UTC)
@Satricious @Sportzpikachu, this is one of the few parts of RedWarn I haven't written, but the code was in the callback to allow for the page to be watched prior to the page redirecting. Without this, the page will redirect with the potential of the watchlist request not going through, so the last structure seems to be correct and the bug may be further up, perhaps in the watchlist code? ✨ Ed talk! ✨ 12:35, 24 February 2022 (UTC)
@Ed6767: You are correct. I just quickly investigated and it looks like in the rw.info.watchPage() function, mw.Api().postWithToken (docs) returns a jQuery Promise which might fail (and it does, I tested). So I changed the code (while using the original code that still had the handleFinish() function) in the rw.info.watchPage() function to this and it worked for me. Sorry I kind of introduced another bug while trying to fix one. @Sportzpikachu if you fix this please don't use my code this time haha I don't trust myself. But I think that's at least somewhere in the right direction since that's how you're handling the errors in the function. Satricious (talk) 13:19, 24 February 2022 (UTC)

Error message "Please select a warning level" and "Please sign your notice" appears after previewing talk page

RedWarn Web - Issue
Unassigned
stateto do

Hello! So this is a bug that I've encountered for a while now, however I haven't been able to reliably replicate it. When I undo an edit by clicking one of the rollback buttons and preview the user's talk page to see if they have been warned before (and how many times), when I go back to the warning screen (with a warning already pre-selected) the error message "Please select a warning level" appears at the bottom, and if you try and click the warn button, the error message will be replaced with a new one saying "Please sign your notice". I'm not sure what causes it and like I said I haven't been able to reliably replicate it, however it does happen fairly often. ― Blaze WolfTalkBlaze Wolf#6545 20:55, 24 February 2022 (UTC)

Ultraviolet

Once RedWarn, always RedWarn. (unless I’m forced to switch) – AssumeGoodWraith (talk | contribs) 23:58, 22 February 2022 (UTC)

@AssumeGoodWraith, UV is what was going to be RedWarn version 17 anyway. I'm sure once the feature set is matched you may see it as a worthwhile upgrade but RedWarn will remain open source so you can always use it or any other versions of RedWarn without restriction. ✨ Ed talk! ✨ 16:42, 23 February 2022 (UTC)

@AssumeGoodWraith — Nobody can stop your unwavering loyalty. However, just a note that in the future, there will be no more security updates/patches, so your RedWarn is potentially going to be compromised. — 3PPYB6 — TALK — CONTRIBS — 01:11, 23 February 2022 (UTC)

@3PPYB6: I just realised, I can literally just add my name to the username list and use Ultraviolet right now. @Chlod probably won't like it. – AssumeGoodWraith (talk | contribs) 05:38, 23 February 2022 (UTC)
@AssumeGoodWraith: Only interface administrators and the 10nm account itself can edit User:10nm/beta.js. This prevents others from hijacking scripts. Like I said above, there's nothing stopping you from copying lines 93 to 102 into a different JS file, maybe even your common.css file (since it is ES5-compatible). Again, however, we make no guarantee that Ultraviolet will be able to work properly when we've finalized the first beta version, and highly suggest against using it right now if you don't want a slew of problems. I'm personally indifferent on the matter, but if you choose to ignore the warning, be prepared for the consequences. Chlod (RW • say hi!) 05:47, 23 February 2022 (UTC)
@Chlod: I meant testing it on my testing account. – AssumeGoodWraith (talk | contribs) 05:51, 23 February 2022 (UTC)
Nothing stopping you from doing that either. Chlod (RW • say hi!) 05:52, 23 February 2022 (UTC)
... And upon further inspection, is this just RedWarn with a different look and more features? – AssumeGoodWraith (talk | contribs) 05:53, 23 February 2022 (UTC)
Yes, as it is meant to be.

In essence, Ultraviolet is a rewritten version of RedWarn.

In fact, there are even less features since we haven't ported everything. See Wikipedia:Ultraviolet/Compatibility matrix for the list of missing things. Chlod (RW • say hi!) 05:57, 23 February 2022 (UTC)
@AssumeGoodWraith I was literally thinking about creating a test account, waiting for its autoconfirmation, and then installing something that I would call “User:3PPYB6/UVBeta.js” which is just an essential “hackers’ public beta”, when you just remove the disallow list. — 3PPYB6 — TALK — CONTRIBS — 13:26, 23 February 2022 (UTC)

@3PPYB6: Just take the User:AssumeGoodTest script, change the name to your name, then install it. – AssumeGoodWraith (talk | contribs) 13:31, 23 February 2022 (UTC)

@3PPYB6, @AssumeGoodWraith both of you are of course free to do so (we can hardly stop you), but be aware there are reasons that the script is locked to team members only, which includes the possibility of bugs which may permanently affect your ability to run future version of UV. While we can support such issues within the UV team we make no guarantee that we will be able to fix them for any public versions before we do a actual public beta release. -- Asartea Talk | Contribs 13:49, 23 February 2022 (UTC)
Hence why I"m waiting for an official public beta test before installing it on my alt. I don't wanna end up screwing myself over because something was very broken. ― Blaze WolfTalkBlaze Wolf#6545 01:24, 25 February 2022 (UTC)
Quick question, what permissions are required for the use of Ultraviolet (when there's a public beta release of course)? Only asking so I can request those permissions be given to my alt since I'm not going to be using my alt for much testing for the time being. ― Blaze WolfTalkBlaze Wolf#6545 01:25, 25 February 2022 (UTC)

More username problems.

RedWarn Web - Issue
resultdone

When reporting this username, the "target" form comes out blank. – AssumeGoodWraith (talk | contribs) 06:56, 25 February 2022 (UTC)

@AssumeGoodWraith:  Fixed. Chlod (RW • say hi!) 09:52, 25 February 2022 (UTC)

Going Ultraviolet =

I'm excited for this new RedWarn! I would assume the redirect will be changed from WP:RW to WP:UV? Regardless, I'm excited to see Ultraviolet and what will come of it. Also, the FYI at the top of the page needs to be changed to say that the team is working on Ultraviolet and not RW 17 ― Blaze WolfTalkBlaze Wolf#6545 19:47, 22 February 2022 (UTC)
We will get around to it shortly :). We are still in the process of moving and it has been very hectic on our part. Sennecaster (Chat) 19:48, 22 February 2022 (UTC)
Also in the post above this one, Berrely said this, "For now, it's best not to use Ultraviolet, as it is a beta." How would one use Ultraviolet if it hasn't even been made publicly available yet? ― Blaze WolfTalkBlaze Wolf#6545 19:49, 22 February 2022 (UTC)
@Blaze Wolf: It actually does exist as User:10nm/beta.js and is publicly available, but we've locked it to team members for now since there's existing bugs that will likely mess with your RedWarn configuration and how we store data on the browser for caching. We're still hammering these out, and when they're gone, we'll set it to allow everyone to use the script.
Of course, this doesn't stop anyone from loading the script directly from Toolforge, but I'd advise against that for the reasons I've just written above. Chlod (RW • say hi!) 19:54, 22 February 2022 (UTC)
Ah alright. If I were to use it early I would probably only use it on my alt since 1. RW is now being phased out as UV is being released and 2. That would be the most ideal way for me to help test it if I were to decide to try and load the script from Toolforge. ― Blaze WolfTalkBlaze Wolf#6545 19:56, 22 February 2022 (UTC)
Looking forward to it! 😀 Aasim - Herrscher of Wikis 20:03, 22 February 2022 (UTC)
Awesome! I've had trouble with RW, so I have high hopes on UV. Explodicator7331 (talk) 20:57, 22 February 2022 (UTC)
I checked, and some other wikis also have RedWarn. They use the same script. On your wiki page here, it states:

The RedWarn name, logo and likeness is restricted "for the use of development of Wikimedia tools only".

Does that mean that other wikis cannot use the name RedWarn even if they use the same script? I.hate.spam.mail.here (talk | contributions) 00:41, 25 February 2022 (UTC)
@I.hate.spam.mail.here: This is exactly why I was very hesitant to sign the agreement, since it would cause some extremely vague issues as presented here. The quote above depends on the interpretation, and only a court of law can do that (IANAL). The current team behind RedWarn and Ultraviolet isn't going to do anything about those scripts, as most of them are already compliant with the license (which basically sums up to "link to our GitLab repository" and leave the license text in there). As for whatever the licensor who provides the RedWarn name decides, that's beyond our control. Chlod (RW • say hi!) 00:54, 25 February 2022 (UTC)
@Chlod: Based on what you said, I fully support the rename. Wikipedia's supposed to be free content, after all... I.hate.spam.mail.here (talk | contributions) 01:01, 25 February 2022 (UTC)
@Chlod, you are correct that as the owner of the RedWarn name it's really up to me to enforce the agreement unless I violated it myself, and the "Wikimedia projects only" applies to you as the licensor and doesn't override the Apache License for anyone else. The "wikimedia projects only" term was to prevent you going back on yourself and profiteering off the name or changing the projects goals (not that you would, but as a precautionary measure) along with to encourage a rename (which was the ultimate goal). If you contacted me I would've been willing to clarify this for you, but I have not had any real contact since the agreement was signed and I am sorry that you have felt left to assume without my input. ✨ Ed talk! ✨ 19:01, 25 February 2022 (UTC)
@Ed6767: I'm not really privy to the fact that I had to involve my name into legalities for an open-source project just because I had kept the RedWarn users in mind. Had RedWarn performed an instant rename at the time, we would have made less progress as we had to pick up the remains of whatever infrastructure and code was left behind and change it immediately, and then ask the >300 RedWarn users to switch gears seemingly out of random.
But, and I'll mention it here for full transparency to the wider Wikipedia community, you threatened to remove the rest of the team's access of the RedWarn account and the GitLab repo if we didn't split or let you leave. I had no choice but to sign the document or else cause a massive inconvenience to all RedWarn users. Worst case scenario, we wouldn't be able to push important security updates that prevent XSS attacks.
Restricting control of "[your] FOSS project" (your words from back then, not mine) from its most active maintainers because you held the technical right is not in the spirit of open-source. Not saying this as a RedWarn developer but as an open-source contributor in general: and sorry if any of this comes off as abrasive, but there is nothing else to describe my feelings besides "furious". Chlod (RW • say hi!) 02:24, 26 February 2022 (UTC)
And plus, there's no reason for us to bother you with the technicalities of the name license of a project that you wanted to leave so badly. Chlod (RW • say hi!) 02:25, 26 February 2022 (UTC)
I don't exactly understand what was preventing Ed from leaving in the first place. But like Chlod said, I'm not a lawyer. So there may have been something legally preventing them from leaving without signing the document (i also don't know why Ed wanted to leave but I'm not going to question it). I do feel that, based on how Chlod described it, Ed was being rather aggressive, however that is not for me to judge since I'm not part of the team or a dev. ― Blaze WolfTalkBlaze Wolf#6545 02:30, 26 February 2022 (UTC)
@Blaze Wolf: For transparency, we had an internal vote on which direction to take RedWarn as Ed wanted to branch RedWarn Patrol/React (now Teyora) outwards. Two votes were for a split, another two for making RedWarn the subgroup of a higher organization. Of course, the votes were discounted by Ed, who wanted to disassociate from the rest of the team. Reading back on our conversations, it seems what "[prevented] Ed from leaving in the first place" was a "PR disaster", according to him. Chlod (RW • say hi!) 02:34, 26 February 2022 (UTC)
Of course, I'm not at liberty to quote more, link to the messages, or show the conversation, since (a) it's prevented by policy and (b) it's in a private channel reserved for team members only. You can choose to believe me, you can choose not to.Chlod (RW • say hi!) 02:38, 26 February 2022 (UTC)
What exactly is Teyora? That's something I've never heard of and I also have never heard of RedWarn Patrol/React (outside of the broken RW Patrol on Recent Changes which I hope UV will either fix or just remove). I think I would understand Ed's frustration with the vote ending up as a tie. Maybe in that situation there should've been a community vote to help break the tie, but I'm not part of the RW team so I don't know how things work. ― Blaze WolfTalkBlaze Wolf#6545 02:41, 26 February 2022 (UTC)
@Blaze Wolf: The team was composed of 9 members, Ed said that he won't be following the vote even before half of us had voted, and there was even the perfect opportunity for a tiebreaker given the uneven member count. As for RedWarn React/Patrol, it was a web-based Huggle-like tool that was mostly built by me and Leijurv, prior to being renamed to Teyora and transferred out of the RedWarn organization on GitLab. Ed had initially planned to deprecate the userscript in favor of the standalone tool, which is why sometimes you'll also see "RedWarn Lite" or "RedWarn Web" (both being the userscript) in documentation or code.
Do note that I'm saying "Ed" here and not "the team", as these weren't unanimous decisions. Chlod (RW • say hi!) 02:47, 26 February 2022 (UTC)
Ah alright. So it sounds like the RW Patrol that is on the Recent Changes page is a remnant of that, that just never got removed. I'm not going to question any further since you are limited in what you can tell me. ― Blaze WolfTalkBlaze Wolf#6545 02:57, 26 February 2022 (UTC)
@Blaze Wolf, in the original versions of RedWarn there were links added next to items in your recent changes, however due to issues this was made into RedWarn Patrol. The RedWarn Patrol was basically like a layer on top of Recent Changes that let you navigate and see edits at the same time without the page reloading. I'm not sure when it broke exactly but it was never a priority for us so just wasn't removed. ✨ Ed talk! ✨ 17:02, 26 February 2022 (UTC)
@Chlod, I know I made mistakes with RedWarn, but my memory doesn't match half of these things you're saying and the chat logs I have mostly contradict what you're saying, and I still don't understand why you didn't resolve this in private instead of this constant public escalation.
  • The vote was initiated by you and (Redacted) won (in my chat log), which is what ultimately happened. I don't have a record of a tie happening and as it happened through Discord reactions they could be changed afterwards.
  • I said (Redacted) i.e. I wasn't going to use the RedWarn name for my new projects or the new parent org. This didn't mean I wasn't going to follow the vote.
  • You said (Redacted)
and that
(Redacted)
  • I said this regarding "my FOSS project" which you took out of context:
(Redacted) i.e. implying that I didn't want that. I admit my wording was very harsh and absolutely terrible and I don't even know what I was getting at, and not in the spirit of open source or the community in mind, but only because you and I were arguing about it and it was incredibly spur of the moment. I also said that I (Redacted) which could also be seen that I knew my wording wasn't the best and regretted that message. The "PR nightmare" was because I didn't want to drag the rest of the team down if it publicly looked like we had a mess internally for when I left because you all worked very hard on RedWarn. However, that was the end of the discussion and the split happened. I never intentionally threatened that and am sorry you felt that harshly worded message was read like a threat and really wish you clarified this with me as the agreement was always quite flexible from my point of view, as I wanted the best for both projects.
  • RedWarn Lite was the original name, but RedWarn Web was chosen by users in the survey a couple years ago if I remember correctly. I also remember that the survey also opted in favour of phasing out RedWarn Web but this was nearly two years ago so I can't remember exactly.
I have taken a step back to learn from the mistakes I made and have been rethinking a lot of things to ensure that these issues never reoccur in any community project I lead, or rather, direct in the future. Regardless, you and I both got what we wanted in the end. You got control of the project and the name subject to conditions and I had the creative freedom I wanted and both projects are now better off than before the split in my opinion. I'll no longer be commenting on this specific issue. ✨ Ed talk! ✨ 16:59, 26 February 2022 (UTC)
@Ed6767: I have oversighted discord logs above per the oversight policy, as a result of this RfC. This unfortunately does dramatically alter the content of your message, so you may wish to review the remaining parts of your post. Please do not reinstate the oversighted content -- TNT (talk • she/her) 17:14, 26 February 2022 (UTC)
My apologies @TheresNoTime, I didn't know about this policy and thank you for redacting it. ✨ Ed talk! ✨ 17:35, 26 February 2022 (UTC)
​ Ed6767 has been posting Discord logs without my permission in the past before, it doesn't affect me right now as my Discord account is deleted but can these be OSed as well? Naleksuh (talk) 23:12, 26 February 2022 (UTC)
@Naleksuh: Oh really.. not great to hear—could you email us the diffs etc and I'll get them oversighted -- TNT (talk • she/her) 23:15, 26 February 2022 (UTC)
​I email you twice in the last two weeks and never got anything back. Why not start there? Also, does it still apply if the edit in question was made before the Discord log rule (i.e. it is retroactive)? Naleksuh (talk) 23:17, 26 February 2022 (UTC)
@Naleksuh, yes it will be retroactive, but this is veering off topic and I don't recall exactly publishing logs. The only incident I recall (perhaps incorrectly) involving yourself occurred prior to the RFC in 2020 or early 2021 and was an explanation for why you had been banned from the RedWarn discord server, but I'm sure she'd be happy to if you provided diffs. ✨ Ed talk! ✨ 23:19, 26 February 2022 (UTC)
An explanation for who? No one asked you why, you just jumped in to announce it, posting logs. And the logs were from DMs, not any server. Naleksuh (talk) 23:21, 26 February 2022 (UTC)
@Naleksuh, for yourself. Please email me the diff content in question as I don't remember this exactly. It was nearly two years ago now. ✨ Ed talk! ✨ 23:22, 26 February 2022 (UTC)
Please let 10nm handle RedWarn and Ultraviolet from here on out. Teyora and Redwarn/Ultraviolet are separate and independent and going in their own directions. Sennecaster (Chat) 17:17, 26 February 2022 (UTC)
That's correct and is the case and I have no plans to change that. ✨ Ed talk! ✨ 17:25, 26 February 2022 (UTC)
To clarify, that would include refraining from attempts at usurping Ultraviolet as well. Chlod (RW • say hi!) 17:36, 26 February 2022 (UTC)
But why did the team choose the name 'Ultraviolet'? I.hate.spam.mail.here (talk | contributions) 01:02, 25 February 2022 (UTC)
@I.hate.spam.mail.here: Two reasons: (1) WP:UV was an available shortcut at the time, and (2) on the visible spectrum, violet is on the opposite side of red. By the end of the beta, Ultraviolet won't just be a clone of RedWarn, so we kicked it up a notch and went for ultraviolet (which is past visible light on the electromagnetic spectrum, when going from largest wavelength to smallest). Chlod (RW • say hi!) 01:13, 25 February 2022 (UTC)
Thanks for the quick reply! I.hate.spam.mail.here (talk | contributions) 01:34, 25 February 2022 (UTC)
Retrieved from "https://en.wikipedia.org/w/index.php?title=Wikipedia_talk:Ultraviolet/2022/February&oldid=1108914624"