User talk:JJMC89

This user has opted out of talkbacks

JJMC89 Bot removed Image Files on my User Page

Hello JJMC89 it is great to talk to you the first time. I'm a 13 year Wikipedia user. And I returned to the platform on this new account.

2 years ago... I saw I edited my user page on my 2nd Wikipedia account (This account) and it said on JJMC89 Bot 'Describe What you changed' text and said "Removed WP:NFCC violation(s). Non-free files are only permitted in articles." Was it because of copyrighted images? And I don't have the rights to use that image since the image can only be used in articles? Thank you and have a great blessed day! :) Legoweatherboy (talk) 03:18, 27 September 2024 (UTC)

Yes, per WP:NFCC#9, non-free images are only permitted in articles. — JJMC89 18:36, 27 September 2024 (UTC)

Thank you. If I remembering this correctly. There is a notice on non-free image files? Legoweatherboy (talk) 21:07, 27 September 2024 (UTC)

Each file has a license. Ones that are not free will have one of the non-free ones. — JJMC89 18:00, 28 September 2024 (UTC)

Got it. Thank you for helping me out. Legoweatherboy (talk) 19:10, 29 September 2024 (UTC)

One moment, last thing. What are the block times if you continue to put non-free files on your user page. When the bot keeps reverting changes.

Warning, Temporary Block, then Permanent Block, etc. Legoweatherboy (talk) 15:53, 2 October 2024 (UTC)

Updating Template:Non-diffusing subcategory

Hi, when the bot renames a parent category on a category page, and that parent category is also specified as a parameter within {{Non-diffusing subcategory}}, please could the bot also update that parameter? E.g. [1].

Likewise, {{uncited category}} in an article page, e.g. [2]. – Fayenatic London 10:50, 1 October 2024 (UTC)

This is similar to User talk:JJMC89/Archives/2024/April#CFD bot requests except for linking instead of categorization. Please open a discussion at WT:CFD/W to get input from the other regulars before I implement. — JJMC89 17:55, 6 October 2024 (UTC)

Titles ending in /

Are you sure about this? There's a bunch of existing matches, and all the ones I checked looked legitimate. —Cryptic 18:14, 5 October 2024 (UTC)

Thanks for bring it up. I've reduced it to the user and user talk namespaces, where most of the problems are. — JJMC89 18:39, 5 October 2024 (UTC)

Renaming and locking account?

I noticed you renamed editor qwerty account to something weird and then globally locked it. He's always been a great user with me. Was there a compromised account that I also need to look out for happening to me? Just wondering. Fyunck(click) (talk) 06:31, 6 October 2024 (UTC)

The account was vanished (at the user's request). I cannot disclose the reason for vanishing, but I can say that the account was not compromised. (We don't vanish accounts for that.) — JJMC89 17:52, 6 October 2024 (UTC)

Thanks. Just wanted to understand. So if I understand vanishing, you actually move the account to a wikipedia coded account number, then delete the old account. That way if a user ever wants to come back with a different handle it makes it easier to transition the info to that new handle? I never knew that. If you ever deal with him again please give him my best wishes. Cheers. Fyunck(click) (talk) 19:04, 6 October 2024 (UTC)

The account is not deleted. Vanishing on a technical level is changing the username to 'Renamed user ' + random string and locking it. Global renamers (or Stewards) approve requests. The software determines the new username and locks the account (lock logged by m:User:AccountVanishRequests). Vanishing is for users leaving the project(s) permanently. — JJMC89 19:24, 6 October 2024 (UTC)

Wikipedia:Sockpuppet investigations/Cyonsw

There's a clerk request at the above SPI, but I'm not asking you to take care of it. I'm coming here because I'm hoping you can assist me with the SPI helper script so I can do what I'm asking a clerk to do. Active clerks are in short supply these days, so it'd be good for me not to have to request a clerk for anything I'm permitted to do myself. Also, the list of socks is not complete (I'll add the new ones soon).

So, I've stared at the SPI helper script to assist in single-tagging one group and double-tagging the other group - and I could swear I've done this before with the script - but I can't figure it out. And there's now way I can try something and then just revert it easily, so getting it right is kind of important. Assuming you know, can you explain to me how it's done? Thanks.--Bbb23 (talk) 18:18, 6 October 2024 (UTC)

User:GeneralNotability/spihelper#Block/tag socks may help you. I would do the tagging for each group separately.

1. Confirmed to Bleedroots:
   • Bleedroots:
     • tag: CU confirmed master
     • alt master: suspected alt master
   • Others confirmed to Bleedroots:
     • tag: CU confirmed sock
     • alt master: suspected alt master

   You should be prompted for the alt master after clicking Done.: Cyonsw

2. Possilikely to Cyonsw:
   • tag: Suspected sock

— JJMC89 18:46, 6 October 2024 (UTC)

Well, it didn't work. The first part (confirmed to Bleedroots) worked fine, but the second part did not. All of the accounts that are confirmed to Bleedroots and suspected to Cyonsw now have only the suspected tag. I guess in retrospect I didn't put the suspected in the right column, don't know really. Is there a way to retag that group using the script, or do I have to manually do it?--Bbb23 (talk) 21:32, 6 October 2024 (UTC)

You can just go back to the same block/tag screen to retag. In an effort to check if my instructions were incorrect, I fixed the tags on the confirmed Bleedroots socks. They should have tag (first dropdown) as CU confirmed sock and alt master (second dropdown) as suspected alt master. Then after clicking Done, specify the alt master as Cyonsw. — JJMC89 21:56, 6 October 2024 (UTC)

I think I understand what I did wrong on the second round of tagging, but we'll never know because AFAICT you fixed all of them, right (I spot-checked several)? Did you run the script or what (you didn't edit the SPI itself)?--Bbb23 (talk) 22:13, 6 October 2024 (UTC)

Yes, I ran the script and fixed all of the confirmed Bleedroots socks. (Adding a comment on the SPI is optional.) Feel free to revert my tags if you would like to test yourself. — JJMC89 22:16, 6 October 2024 (UTC)

Heh, I think not. I will close the SPI now. Thanks very, very much for your patience and help. Maybe some of it will sink in for next time, although it doesn't happen too often.--Bbb23 (talk) 00:47, 7 October 2024 (UTC)