User talk:JJMC89/Archives/2022/April

New administrator activity requirement

The administrator policy has been updated with new activity requirements following a successful Request for Comment.

Beginning January 1, 2023, administrators who meet one or both of the following criteria may be desysopped for inactivity if they have:

1. Made neither edits nor administrative actions for at least a 12-month period OR
2. Made fewer than 100 edits over a 60-month period

Administrators at risk for being desysopped under these criteria will continue to be notified ahead of time. Thank you for your continued work.

22:52, 15 April 2022 (UTC)

Brewers Cubs Rivalry

I Was Brewers Logo Because Why There's Violations No Need To Remove Logo From Brewers Logo Against Copyright Andrei Kenshin (talk) 17:20, 22 April 2022 (UTC)

(talk page watcher)@Andrei Kenshin: I can tell from your account's history that you're really quite new to Wikipedia. As such, you might not be aware that Wikipedia has many different policies and guidelines when it comes to using images in articles, and some of these are related to using non-free content. Some of these policies and guidelines can make using images tricky and it's easy to make mistakes; a mistake is OK, though, and everyone makes them, especially when they're new to Wikipedia like you are. However, repeating the same mistake over and over again isn't a good thing since it indicates a pattern and it's accounts that start demonstrating such patterns that usually end up getting blocked. What you've been doing at Brewers–Cubs rivalry is edit warring with the bot run by JJMC89 over non-free content use. The bot keeps removing the logo from that article because that's what it been task to do, and it will keep removing the file each time you re-add it as long as the file's use in that article doesn't comply with Wikipedia's non-free content use policy. Moreover, trying to argue with the bot via edit summaries isn't going to make the file's use in the article policy compliant. You're very lucky that JJMC89 (who's a Wikipedia administrator) or some other administrator hasn't blocked your account already for edit warring over this, but that luck will almost certainly run out it you revert one more time to re-add that logo to the article. Non-free sport team logos are generally only considered acceptable to use in the main articles about the teams themselves. Some primary logos may be so old or so simple that they can also be used in rivalry articles that they're either no longer protected by copyright or not eligible to be protected by copyright in the first place, but many are copyright protected and thus they can't be used in any articles other than the main articles about the teams they represent. The Brewers' primary logo is one of those that can't be used in a rivalry article; so, if you want to use something for the Brewers in the rivalry article, you will have to find something else like a wordmark or one of the files in c:Category:Milwaukee Brewers to use instead. — Marchjuly (talk) 20:53, 22 April 2022 (UTC)

File:Author Mikey Walsh.png

Hi JJMC89. Just letting you know about WP:MCQ#Mikey Walsh since it's related to this particular photo and almost certainly the email that you checked. -- Marchjuly (talk) 02:37, 14 April 2022 (UTC)

Hi JJMC89. Would you mind double checking this? Apparently the ticket is now OK and the {{Permission received}} template you added has been replaced by {{Permission ticket}}. If thing’s are now sorted out, the file probably should be tagged for a move to Commons. — Marchjuly (talk) 19:30, 16 April 2022 (UTC)

Krd accepted the follow-up email, so it should be fine to move it to Commons. — JJMC89 07:28, 23 April 2022 (UTC)

Non-free images bot -- 3D sculpture

@JJMC89: Reposting my query re: your image resizing bot. Originally posted on your Talk page in March.

I had a question about your bot that marks non-free images for resizing -- I've uploaded several freely licensed images that contain non-free content (copyrighted sculptures), and your bot has marked them for resizing several times. I've reduced the image sizes significantly before uploading, and I do feel there is a genuine need for them to be larger than the size your bot has changed them to. Most of them are sculptures that cannot be understood or viewed without a higher level of detail, and they essentially become unidentifiable when resized to your bot's specifications. I know the policies re: non-free content are strict for a reason, but there is some amount of room for higher sized images when discussing works of art -- it's a grey area, and certainly deserve some level of explanation for why a slightly higher image size is required, but it's well-documented that there is not a one-size fits all policy for use of images like these. I just wonder if you've taken situations like this (which I know are pretty niche) into account when designing the bot. Is there any way for me to stop the bot from reducing these images further than what I reduce them to, and do you think a situation like this makes sense as an exception to the extremely-low-resolution standards? Thanks for your time!

19h00s (talk) 20:51, 18 April 2022 (UTC)

I see you've already been advised at WT:NFC. — JJMC89 07:41, 23 April 2022 (UTC)

overzealous JJMC89bot w/r/t scientific figure

Hi JJMC89, your bot (and DatBot) and I have been having a tug of war with regard to an non-free image file. Basically, I had reduced the size of the non-free image file before I uploaded it, then another user further cropped it. As it were, the file was readable (it's an image of an illustrative scientific figure with lots of text), but between the collaborative work of JJMC89Bot and DatBot, the image had been repeatedly reduced to a size that can barely be read on the screen if you have better than 20/20 vision. I understand and appreciate the work of these bots, but in this case they seem to be going a bit far in my opinion. What can be done about this?

Cheers. Spotty's Friend (talk) 00:59, 21 April 2022 (UTC)

Edit warring (with bots) isn't a good idea. I would start with cropping the caption and table out of the image. If they are needed, then put them in the article to make them accessible. (MOS:TEXTASIMAGES) — JJMC89 07:49, 23 April 2022 (UTC)

Block of 72.143.192.155

Hi JJMC89! I noticed you blocked 72.143.192.155. I'd like to let you know that this user is on the range 72.143.192.128/26; you may want to block the range. In addition, this user is using the address 2605:8D80:64C:CDE5:402B:7212:9117:AF66, which you may also want to block. Thanks for the block and revdel! Tol (talk | contribs) @ 06:22, 23 April 2022 (UTC)

It looks like the user is on the wider range of 72.143.192.0/24, per this comment at AIV. The user seems to have switched to 72.143.192.57 for an edit. Tol (talk | contribs) @ 06:34, 23 April 2022 (UTC)

Thanks for the heads up. I gave the /24 a longer vacation. — JJMC89 07:27, 23 April 2022 (UTC)

No problem; thanks! Tol (talk | contribs) @ 18:29, 23 April 2022 (UTC)

A quick request

I'm sorry for making this report at the wrong place. Where should I file this report? Thank you for your help and time. --A.S. Brown (talk) 02:14, 24 April 2022 (UTC)

See the instructions at the top of WP:SPI for how to open an investigation. — JJMC89 02:25, 24 April 2022 (UTC)

Thank you for all your help! --A.S. Brown (talk) 02:26, 24 April 2022 (UTC)

Thanks

Thanks for unblocking my IP address! I have now created a new account and you can find it here Wolfquack (talk) 17:16, 24 April 2022 (UTC)

If you can add one of those templates on how to use the site that would be helpful. Wolfquack (talk) 17:18, 24 April 2022 (UTC)

WE HERE HATE CHINA

They need to have their talk page access revoked. Thanks. Scorpions13256 (talk) 05:13, 29 April 2022 (UTC)

 Done — JJMC89 05:15, 29 April 2022 (UTC)

Technical problem

Could you fix whatever is wrong with User talk:Zachiscool123? The decline of the unblock request got mangled, and I haven't been successful fixing it. Thanks.--Bbb23 (talk) 16:07, 30 April 2022 (UTC)

 Fixed The template cannot be indented with :. — JJMC89 19:08, 30 April 2022 (UTC)

The one thing I didn't try. Good to know. Thanks.--Bbb23 (talk) 19:25, 30 April 2022 (UTC)