User talk:Ronhjones/Archive 35

File:Seal of Rassilon.svg

Unfortunately, I don't think you've really explained the basic point -- what possible purpose does "reducing" a vector even serve???

When you resize a raster to have fewer pixels, you actually are reducing the amount of information in the image. In strong contrast, when you diminish the default display size of a vector SVG, you haven't "reduced" anything -- the SVG file contains exactly the same information as it did before, and you can run various software to display it at 10,000 pixels wide (if you want). In fact, you've done absolutely nothing that accomplishes anything useful. AnonMoos (talk) 00:30, 6 October 2017 (UTC)

(Non-administrator comment) All files have a size. With a pixel image, you answer this question: is it really necessary to have two pixels, or would only one pixel be enough? For vector images, the question is slightly modified: is it really necessary to have two vectors, or would only one vector be enough? A vector file also has a default display size in pixels, but this is just an arbitrary number and doesn't really have anything to do with the size of the file.

For pixel images, we have a guideline, WP:IMAGERES, which suggests that 100,000 pixels usually is enough. However, I don't think we have a guideline for how many vectors we need in the event of a vector file. --Stefan2 (talk) 12:14, 6 October 2017 (UTC)

@AnonMoos: An SVG has a nominal page size, which is shown on the image page - and that is the size it is displayed (as a png!) when you look at the image page with its description. All we can do is reduce the page size of the svg so that the default image png appears below 100,000 pixels. We cannot really have non-free png images showing at over 100,000 pixels when we have the ability to stop that. As it says on File:Seal of Rassilon.svg - "nominally 564 × 549 pixels" - which is the size that wiki makes the png for the page - you only get the true svg image if you then click that png image and goto https://upload.wikimedia.org/wikipedia/en/b/b3/Seal_of_Rassilon.svg. I have a reducing system outlined at User:Ronhjones/SVGreduce. I've done dozens of SVGs this way.  Ronhjones  ^(Talk) 13:58, 6 October 2017 (UTC)

Why should we decrease the default display size of a vector SVG, when it does nothing which is useful or meaningful? AnonMoos (talk) 14:38, 6 October 2017 (UTC)

@AnonMoos: (1) It stops the wiki software making and automatically displaying a png that is in excess of 100,000 pixels, which is an unnecessary violation of the NF guideline, and might even cause legal issues. (2) When we conduct a search for oversized images, a properly reduced SVG will not keep coming up in the list - FWIW there are about 800 SVGs to do.  Ronhjones  ^(Talk) 15:00, 6 October 2017 (UTC)

(1) It only affects what it looks like on the file information page. On a wiki page, the file may have a different size – you could use [[File:Example.svg|1px]] and [[File:Example.svg|99999px]] as you like. Also, WP:NFCC#3 is all about reducing the amount of non-free content on Wikipedia, but if you only change the default display size, you're only changing an arbitrary number – the amount of non-free stuff on Wikipedia remains unchanged. (2) Depends on how you search for oversized images. The database table stores information about the file type, so you could use a query which excludes SVG files. --Stefan2 (talk) 18:04, 6 October 2017 (UTC)

(I) Correct. Wiki pre-makes a png the same size as the nominal svg size, and that is what is saved and displayed on the image page (the image displayed is https://upload.wikimedia.org/wikipedia/en/thumb/b/b3/Seal_of_Rassilon.svg/564px-Seal_of_Rassilon.svg.png not the svg! - I think it's done that way as not all browsers will render an svg direct) - If you saw a png at 564 × 549 then you would be putting a reduce tag on it. I can't see a valid reason for wiki to display an obviously oversized bitmap image, when it not necessary. (2) Yes one can (and I do most times) separate off the "manual reductions types" - filetype:bitmap gives jpg, png, bmp. and filemime:gif works for RonBot2 to find gifs. That just leaves the TIFs, SVGs and the PDFs (even more fiddly to reduce!) in the manual reduction category. Ronhjones  ^(Talk) 18:21, 6 October 2017 (UTC)

Ideally we should not be allowing svg files to be used for non-free images, as (by default) they are high resolution images. However, I believe that has already been discussed and the practice allowed. Ronhjones  ^(Talk) 18:24, 6 October 2017 (UTC)

Ronhjones -- I don't want to get too vituperative, but the Jargon file has an entry on "Cargo cult programming" (Wikipedia even has an article on it). Reducing the default display size of a vector SVG strikes me as a cargo-cult way of taking fair-use precautions... AnonMoos (talk) 10:26, 7 October 2017 (UTC)

@AnonMoos: You may well be right. As I said, I don't agree with SVGs for fair-use as they are "high definition", and fair use has always been "low resolution", but although we might not agree with the policies which have been agreed by consensus, we have to follow them and allow SVGs to be fair-use. As an aside I note one editor (not me) has been reducing some fair-use SVG logos and has gone to the extreme of reducing the page size to, like, 20 x 20 pixels - maybe he anticipates the fair-use guideline going down, who knows, it make no difference to the article page. I'm not looking solely at Wikipedia use, more the bigger picture, as that oversized PNG image on the file page will be indexed and cached by all the search engines. I think we all have a duty to protect Wikipedia where possible, and to let Google and others to cache way oversized PNG images (and some are way much bigger than your image), may well attract some unhelpful lawyers. Maybe you would like to bring it up at Wikipedia talk:Non-free content, if you can get a consensus not to reduce the oversize files, then we could de-tag about 800 images or so. Ronhjones  ^(Talk) 13:47, 7 October 2017 (UTC)

Tech News: 2017-41

Latest tech news from the Wikimedia technical community. Please tell other users about these changes. Not all changes will affect you. Translations are available.

Recent changes

• The number of active users listed by {{NUMBEROFACTIVEUSERS}} and on Special:Statistics will now only include Wikidata edits as activity on Wikidata and not on other wikis too. [1]
• Previously you could create wiki links starting with two colons. Now you need to use one colon. [[::File:X.jpg]] now has to be [[:File:X.jpg]]. There is now a new Linter category. You can see a list on Special:Linterrors/multi-colon-escape. The Linter extension helps you find technical errors in articles. You can read more about using Linter. [2]

Problems

• You will not be able to edit or upload files to Commons for around 30 minutes on 11 October. This will start at 06:00 UTC. This is because of work to let Commons show 3D models. [3]

Changes later this week

• The font in the edit window is monospace by default. Today you can change preferences to another font family or use "the browser default" instead of monospace. Switching to the browser default has only changed the font on Macs. The option to use browser default will be removed this week. [4]
• If you want to print a page or make a PDF of a page you can do so in the side menu. The way the pages look when you do this will change. You can read more on mediawiki.org.
• The new version of MediaWiki will be on test wikis and MediaWiki.org from 10 October. It will be on non-Wikipedia wikis and some Wikipedias from 11 October. It will be on all wikis from 12 October (calendar).

Meetings

• You can join the next meeting with the Editing team. During the meeting, you can tell developers which bugs you think are the most important. The meeting will be on 10 October at 19:00 (UTC). See how to join.
• You can join the technical advice meeting on IRC. During the meeting, volunteer developers can ask for advice. The meeting will be on 11 October at 15:00 (UTC). See how to join.

Tech news prepared by Tech News writers and posted by bot • Contribute • Translate • Get help • Give feedback • Subscribe or unsubscribe.

14:21, 9 October 2017 (UTC)

Recent message

Hi there, I just saw a message from you at this page. https://en.wikipedia.org/wiki/File:Skyfaring_A_Journey_with_a_Pilot_-_Book_Cover.jpg

I will need some assistance on resolving this one.

Thanks much.Kaisertalk (talk) 23:10, 9 October 2017 (UTC)

I went in and re-read your message. It appears like I might not have an action here and an Admin (or a Bot) will attempt to re-size the image. If there is something that is required from my end, please let me know and I will have it covered. Thanks. Kaisertalk (talk) 23:15, 9 October 2017 (UTC)

@Kaisertalk: Correct, nothing to do. DatBot6 will resize it within 24h (normally). Then the page stays untouched for 7 days (to check it has not been excessively corrupted), and then RonBot1 will hide the unused versions. Ronhjones  ^(Talk) 23:40, 9 October 2017 (UTC)

@Ronhjones: Great! Thanks much.Kaisertalk (talk) 23:57, 9 October 2017 (UTC)

File:American Government, Tenth Edition.jpg

Has the EXIF data for this file been messed with? See especially the camera model and software used. When the bot goes over that file, there's many warnings about possibly corrupt exif data. Then there's "OverflowError: cannot fit 'long' into an index-sized integer." Dat Guy^Talk_Contribs 11:39, 11 October 2017 (UTC)

I tried $ wget -O - 'https://upload.wikimedia.org/wikipedia/en/0/07/American_Government%2C_Tenth_Edition.jpg' | exiftool /dev/stdin which outputs this:

Extended content

ExifTool Version Number  : 9.46 File Name  : stdin Directory  : /dev File Type  : JPEG MIME Type  : image/jpeg DCT Encode Version  : 100 APP14 Flags 0  : (none) APP14 Flags 1  : (none) Color Transform  : Unknown (RGB or CMYK) Exif Byte Order  : Little-endian (Intel, II) Image Description  : Digital Camera Make  : Zoran Corporation Camera Model Name  : COACH Orientation  : Horizontal (normal) X Resolution  : 96 Y Resolution  : 96 Resolution Unit  : inches Software  : COACHWare 1.0 Modify Date  : 2007:06:20 13:44:19 White Point  : 0 0 Primary Chromaticities  : 0 0 0 0 0 0 Y Cb Cr Coefficients  : 0 0 0 Y Cb Cr Positioning  : Co-sited Reference Black White  : 0 0 0 0 0 0 Copyright  : Copyright 2002 Exposure Time  : 1/8 F Number  : 8.2 Exposure Program  : Aperture-priority AE ISO  : 100, 100 Exif Version  : 74 Date/Time Original  : 2007:06:20 13:44:19 Create Date  : 2007:06:20 13:44:19 Compressed Bits Per Pixel  : 0.764714 Shutter Speed Value  : 1 Aperture Value  : 2.8 Brightness Value  : 0 Exposure Compensation  : 0 Max Aperture Value  : 2.8 Subject Distance  : 0 m Metering Mode  : Multi-segment Light Source  : Unknown Flash  : No Flash Focal Length  : 0.0 mm Flashpix Version  : 0100 Color Space  : sRGB Exif Image Width  : 960 Exif Image Height  : 1280 Related Sound File  : RelatedSound Focal Plane X Resolution  : 0 Focal Plane Y Resolution  : 0 Focal Plane Resolution Unit  : Unknown (0) Exposure Index  : 15 Sensing Method  : One-chip color area File Source  : Unknown (6915) Scene Type  : Unknown (31745) Image Width  : 360 Image Height  : 480 Encoding Process  : Progressive DCT, Huffman coding Bits Per Sample  : 8 Color Components  : 3 Y Cb Cr Sub Sampling  : YCbCr4:4:4 (1 1) Aperture  : 8.2 Image Size  : 360x480 Shutter Speed  : 1/8 Focal Length  : 0.0 mm Light Value  : 9.1

However, the file information page on Wikipedia says that the title is "obe", that the camera model is "are 1.0" and a number of other strange things which do not match the Exiftool output. Strange --Stefan2 (talk) 11:50, 11 October 2017 (UTC)

Interesting...

1. The file is the original upload - no deleted version.
2. Photoshop CS6 decodes the EXIF somewhat differently...

• Zoran Corporation
• COACH (model)
• 960x1280
• 96 pixels per inch
• Flash did not fire
• 1.0sec; f/8; ISO 100
• 20/06/2007 13:44:19 (creation date)
• COACHWare 1.0 (software package)
• Copyright2002 (I assume for software)

My guess is that it's an early digital camera (2002), maybe using a non-standard EXIF, might even be a special bench mounted camera. Zoran Corporation says COACH was a "digital camera chip". I'll do the reduce manually with photoshop. Ronhjones  ^(Talk) 20:31, 11 October 2017 (UTC)

Proposed deletion of File:MM-8 The Key to the Universe.png

The file File:MM-8 The Key to the Universe.png has been proposed for deletion because of the following concern:

There are two book cover images used in the article. One book cover is used in the infobox and this book cover is used in the Titles section of the article. This book cover fails WP:NFCC#3a in that the other book cover already is used in the article for means of identification and fails WP:NFCC#8 because there is no commentary about the cover thereby doing nothing to increase the reader's understanding of the film and its exclusion is not detrimental to the understanding of the film.

While all constructive contributions to Wikipedia are appreciated, pages may be deleted for any of several reasons.

You may prevent the proposed deletion by removing the {{proposed deletion/dated files}} notice, but please explain why in your edit summary or on the file's talk page.

Please consider addressing the issues raised. Removing {{proposed deletion/dated files}} will stop the proposed deletion process, but other deletion processes exist. In particular, the speedy deletion process can result in deletion without discussion, and files for discussion allows discussion to reach consensus for deletion. Aspects (talk) 23:52, 12 October 2017 (UTC)

@Aspects: I've little interest in the image - it was just a transfer from File:MM-8 The Key to the Universe.bmp, as bmp images are not supported on wiki any more, so we could not reduce the size to NFCC guideline (except by changing the file type, which meant a new file name). The original uploader of the bmp image in 2010 is User:Double sharp Ronhjones  ^(Talk) 00:07, 13 October 2017 (UTC)

Tech News: 2017-42

Latest tech news from the Wikimedia technical community. Please tell other users about these changes. Not all changes will affect you. Translations are available.

Recent changes

• When you edit a template with the visual editor it follows the template's format configuration on how to save it. You can now change the format in more powerful ways if your wiki wants it. [5][6]
• The TwoColConflict extension is a new way to solve edit conflicts. It makes it easier to copy and paste the relevant text to the text field. It has been a beta feature for the last five months. You can now try out the new interface on a page where you will actually get simulated edit conflicts. You can give feedback to the developers.

Problems

• There is a problem with recent changes pages and your watchlist that show a large number of pages. Until it is fixed, Wikidata edits will not be shown on recent changes or in your watchlist on Commons or Russian Wikipedia. If necessary, Wikidata edits will be removed from all wikis. [7]
• Notifications are not working for some actions. For example some users don't get a notification when they are mentioned. The developers are working on fixing this. [8]
• Users on some wikis could not change their preferences. This has now been fixed. [9]

Changes later this week

• Editors and readers who still use Internet Explorer 8 on Windows XP will not be able to use Wikipedia from 17 October. Internet Explorer 8 on Windows XP can't connect securely to the wikis. When we allow them to do so it means that we get less security for everyone else. If you use Internet Explorer 8 on Windows XP you can install Firefox 52 ESR instead. Around 0.1% of the traffic to the Wikimedia wikis comes from Internet Explorer 8 on Windows XP. [10]
• The new version of MediaWiki will be on test wikis and MediaWiki.org from 17 October. It will be on non-Wikipedia wikis and some Wikipedias from 18 October. It will be on all wikis from 19 October (calendar).

Meetings

• You can join the next meeting with the Editing team. During the meeting, you can tell developers which bugs you think are the most important. The meeting will be on 17 October at 19:00 (UTC). See how to join.
• You can join the technical advice meeting on IRC. During the meeting, volunteer developers can ask for advice. The meeting will be on 18 October at 15:00 (UTC). See how to join.

Tech news prepared by Tech News writers and posted by bot • Contribute • Translate • Get help • Give feedback • Subscribe or unsubscribe.

15:31, 16 October 2017 (UTC)

Reduction of images with text

I commonly upload images with small text at a resolution higher than 100,000 pixels (so that the text is readable), which I believe is in line with the WP:Image resolution guidelines. (I never upload anything with an edge longer than 500 pixels, however.) It's my understanding that you manually review all the images before they are downsized. I was just wondering if you would consider checking images for small text before resizing them. Having readable text makes the images more useful. The guidelines basically specify that reasonable image sizes are between 1 megapixel and 0.1 megapixel, so I don't think we need to be so strict about changing everything to 0.1 megapixel. You might even want to consider changing the reduction threshold from within 5% of 0.1 to within 50% or something more liberal. Just an idea :) Kaldari (talk) 23:49, 16 October 2017 (UTC)

@Kaldari: I did not set the threshold to 5% - it's been there for years. You would have to start a discussion at Wikipedia talk:Non-free content, but I doubt if it would get changed much - A large allowance would just effectively re-set the guideline to a bigger size (There are images that I have seen being uploaded at 105% of the guideline already) I think 5% was put there just to very stop small reductions, as jpgs always degrade slightly on re-saving and a 5% reduction is therefore not sensible - but I'm a long way from there, I'm only down to 164386 pixels at present (there are over 100,000 images between 105,000 pixels and 164386 - so this is a long term project). Yes, I do screen the images first, but you cannot always guess what the reduction will look like, and some text is not necessary to be read anyway - e.g. film posters often have text getting smaller and smaller with each line of text at the bottom of the poster - we have hundreds of these, and reducing to the guideline is quite satisfactory, with all the important data still visible. Only after the reduction is done, (and we have the fixed 7 days review period) can editors properly review the result and decide to keep or revert back or upload an alternative size. If someone reverts - I will find the revert on the next night's check. then either tag with {{non-free no reduce}} or {{non-free manual reduce}}, depending on what the reduced version looked like.

Fair enough. Thanks for the explanation. Kaldari (talk) 00:55, 17 October 2017 (UTC)

I do have to ask though. Are you intending on tagging everything larger than 100,000 pixels? There is nothing at WP:Image resolution that says images need to be smaller than 100,000 (or 105,001). Tagging an image that is 110,000 pixels just wastes database and server resources for no good reason. If the guidelines actually said that images should be no larger than 100,000, I could understand, but that's not what it says. It says 100,000 is the "low pixel count end of the range" and 1,000,000 is the "high end of the range". It sounds like you want to eliminate the range completely and just use 100,000 as an upper limit. Kaldari (talk) 01:11, 17 October 2017 (UTC)

@Kaldari: We have a guideline, it's not there just for convenience, it also has legal implications. If an image is oversize and that well explained in the FUR, then that's fine, or we have reduced and found it wanting and changed it to a larger than guideline image then we have an explantion for the oversize. But if the image can be reduced to the guideline and still be useful, and we then ignore that, then are we not giving some lawyer some extra ammunition? As I said above, if you wish to have the allowance changed then it must be by consensus - if that changed it would not be a big issue for the bot code (it currently works out the percentage change, and if under 5% removes the template, and does not reduce). It has always been said to to worry too much about server space - you would need to get input from the WMF if you think that is a major issue. I can slowly go down to any new guideline that the community wants. I do note that the guideline is somewhat smaller than it used to be - it was set at 100,000 pixels in mid 2011, I'm not sure what it was before, I think about 150,000 - thus I suspect that the community will not want to increase it back up again. Ronhjones  ^(Talk) 19:13, 17 October 2017 (UTC)

Screenshots of Microsoft software

Hello. Please review Template:Non-free Microsoft screenshot and this TfD discussion; we have a specific exception in place for screenshots of Microsoft software that makes it possible for us to use these screenshots under fair-use. You may safely ignore any non-free image that has this template. Warren -talk- 21:20, 7 October 2017 (UTC)

@Warren: Added to my exception list to skip those files. (sorry for late reply, I did implement it and forgot to do the reply) Ronhjones  ^(Talk) 19:16, 17 October 2017 (UTC)

Sticky Notes with insights on Windows 10.png

Hello!

This is Codename Lisa. You probably know why I am here.

File:Sticky Notes with insights on Windows 10.png is downsized by the bot and the result is not of very good quality. Old revisions are already hidden. Any assistance in restoring quality would be appreciated.

Best regards,
Codename Lisa (talk) 07:06, 18 October 2017 (UTC)

@Codename Lisa: No problem. Will do when home in 6h.  Ronhjones  ^(Talk) 12:03, 18 October 2017 (UTC)

@Codename Lisa: All fixed. Ronhjones  ^(Talk) 21:44, 18 October 2017 (UTC)

Thank you!

In exchange, uploaded a downsized version with what I hope to be acceptable quality and less pixel count than what the bot normally approves of.

Oh, and by the way, thank you for all your cooperation too. I would say "I love you" but Hollywood has totally ruined that phrase.

Best regards,
Codename Lisa (talk) 17:09, 19 October 2017 (UTC)

@Codename Lisa: No worries. Always glad to help. I suspect there are not many more screenshots to be evaluated (unless someone upload a new one...! - there's usually 50 new non-free images every day - where do they all end up...) as the images I'm looking at now are around 160,000 pixels. And you can say what you like, never mind Hollywood - it's over the other side of the pond anyway. Ronhjones  ^(Talk) 18:13, 19 October 2017 (UTC)

Template:Orfurrev without date

Files with {{subst:orfurrev}} without a date in the template end up in CAT:ORPHREV seven days after they were last edited. Accordingly, File:Thebachelor2012.jpg and File:Chesswarriors.jpg have been there for a few days. However, it looks as if your bot doesn't touch those files. Is it something with the bot which should be fixed, or is it better to change the template so that manual review automatically is requested if no date is specified? --Stefan2 (talk) 20:24, 18 October 2017 (UTC)

@Stefan2: RonBot has not touched them as they were not in the cat yesterday (RonBot emptied it!) - the issues is that Joe's bot has had problems User_talk:Joe_Decker#Joe.27s_null_bot_8_Stalling_or_slow.3F - without a null edit on every file they won't move for weeks, so now RonBot has a huge backlog to clear tonight - lets hope no connection issues! Ronhjones  ^(Talk) 21:40, 18 October 2017 (UTC)

@Stefan2: RonBot ran for over 8 hours. File:Thebachelor2012.jpg has been done. File:Chesswarriors.jpg has not - it's in Category:Non-free files with orphaned versions more than 7 days old and should be done tonight - maybe it got into the cat after RonBot started - I'll keep an eye out to make sure it gets processed. There are still files in the cat that are way over 7 days old - e.g. File:Road to Mother.jpg, Obviously Joe's bot is still working on the backlog. It's about time the devs fixed the software, so we don't need thousands of null edits...  Ronhjones  ^(Talk) 12:29, 19 October 2017 (UTC)

Unfortunately, I don't think it's possible to "fix" Mediawiki so that the category automatically is updated every second. It's not viable to check for parser functions in category names on all pages on Wikipedia every second. --Stefan2 (talk) 13:06, 19 October 2017 (UTC)

@Stefan2:I agree that it can't check every page (5 million daily checks - not going to happen!), but there are only a moderate number of time related categories, wouldn't hurt for them to have an index of those cats, and run a daily process - a bit like Joe's bot, but all self contained, and less(?) likely to fail on occasions OR even a hidden index of pages (saving page name and date/time of proposed change, when page is added to the category), so the date/time triggers triggers the update and thus only one "null edit" in the 7 days (= less server load). Ronhjones  ^(Talk) 18:24, 19 October 2017 (UTC)

@Stefan2: Noted that File:Chesswarriors.jpg is not done - checked log, found "addmanual" - so it tried to add the manual flag- but as it's not using the standard "Orphaned non-free revisions" template - it can't do it. I'll have to look to see how we can modify the bot to use "non-free reduced" template. Life is never simple... Ronhjones  ^(Talk) 23:53, 19 October 2017 (UTC)

Code has a RegEx to include "non-free reduced" - added some more debug to see what is going wrong Ronhjones  ^(Talk) 00:04, 20 October 2017 (UTC)

Your bot probably needs to accept all redirects to the template - and if there's no date parameter, then you need to add the date of the latest previous edit. --Stefan2 (talk) 00:07, 20 October 2017 (UTC)

File:Theburningposter.jpg

Is reversion really the correct thing to do here? There are more differences than just the pixel count. --Stefan2 (talk) 19:56, 20 October 2017 (UTC)

@Stefan2: Normally I would just set it up for DatBot - but on my screen the old version is a better contrast and the text resolves ok, the newer image has a lower contrast and will suffer on reduction. I checked all the hidden ones, they are all more contrasty than the Drown Soda version Ronhjones  ^(Talk) 20:06, 20 October 2017 (UTC)

File:John Tucker Must Die (soundtrack album - cover art).jpg

Got an idea on what to do with this file? There's an old revision from 2007 which is apparently lost, but the revision is not marked as 'deleted', so my bot adds {{subst:orfurrev}}. Your bot requests manual review and when an admin tries to delete old revisions, the admin only removes the template - the old revision is still marked as 'not deleted'. It's already gone through this process twice – I happened to spot the file when my bot tagged the file for a third time. --Stefan2 (talk) 20:21, 20 October 2017 (UTC)

@Stefan2: Fixed. Tried to just delete the "bad" file - just deleted everything, so restored - no better! Then properly deleted everything, and just restored all the valid data (all the text edits and just the one good file) Ronhjones  ^(Talk) 20:34, 20 October 2017 (UTC)

Double check

About this, you understand that this person's username is the same as Martin Shkreli and that they are editing about pharmaceuticals? More than one person in the world has that name, and the risk of impersonation for the subject of that WP article, who is the subject of controversy and legal actions, is extremely high. Jytdog (talk) 23:32, 21 October 2017 (UTC)

@Jytdog: Supplied documents look OK to me. Ronhjones  ^(Talk) 23:46, 21 October 2017 (UTC)

That is a bit....casual given the high profile of Shkreli and all the controversy. In my view (fwiw) you all should be very, very sure due to the high risk here. Jytdog (talk) 23:48, 21 October 2017 (UTC)

He's not even edited since that date... Special:Contributions/Martinshkreli Ronhjones  ^(Talk) 23:53, 21 October 2017 (UTC)

Yes that is true, his last edit was in April, diff. But it is now an unblocked, active account. Again if you are plenty confident, fine, but the risk here is very high and i hope you are very sure. If you are not very sure, please reconsider the unblock. Thanks for your time. Jytdog (talk) 01:34, 22 October 2017 (UTC)

File:The Golem 1915 Film Poster.jpg

Any reason for reducing an obviously PD poster? --Stefan2 (talk) 20:55, 22 October 2017 (UTC)

@Stefan2: When it was tagged it had a {{Non-free poster}} license, hence it dropped into Category:All non-free media. I tend to concentrate on the image, and decide if reduction will be reasonable - just missed the date. Looks like Sphilbrick missed that as well. I'll revert it back to the big one, now you changed the license. Ronhjones  ^(Talk) 21:04, 22 October 2017 (UTC)

User talk:184.0.142.164

You blocked 184.0.142.164 (talk · contribs · WHOIS), I think he needs talk page access denied too. DuncanHill (talk) 23:06, 22 October 2017 (UTC)

The Signpost: 23 October 2017

• News and notes: Money! WMF fundraising, Wikimedia strategy, WMF new office!

• Featured content: Don, Marcel, Emily, Jessica and other notables

• Humour: Guys named Ralph

• In focus: Offline Wikipedia developed at OFF.NETWORK Content Hackathon

• Blog: The future of offline access to Wikipedia: The Kiwix example

• In the media: Facebook and poetry

• Special report: Working with GLAMs in the UK

• Traffic report: Death, disaster, and entertainment

* Read this Signpost in full * Single-page * Unsubscribe * MediaWiki message delivery (talk) 02:36, 23 October 2017 (UTC)

RonBot Toolforge suggestion

Been some time since I touched that bot, but I was wondering whether you'd be up to running it on wikitech:Toolforge? Wouldn't use your PC then, and would work if you don't have power or internet. You can also remove read permissions (so people can't see your username+password for the first task), so it's pretty secure. Email me if you'd like to hear more /end what sounds like a horrible advertisement. Dat Guy^Talk_Contribs 14:59, 23 October 2017 (UTC)

Edits to Cozi Zuehlsdorff

Judging by this edit content to Cozi Zuehlsdorff being the same as a previously reverted version which resulted in Alphanexus being blocked for 24hrs (by you, is still in effect), this is most likely the same user editing while blocked. I am not sure what the suitable course of action would be (temp block? page protection?), but thought I would bring this to your attention. --TheSandDoctor (talk) 05:16, 23 October 2017 (UTC)

@TheSandDoctor: Does look suspicious. Let's try pending changes - all anon edits need approval and don't show except for logged in editors - ideal for BLP. Ronhjones  ^(Talk) 14:45, 23 October 2017 (UTC)

Thanks for the ping (greatly appreciated), thank you for changing the protection. --TheSandDoctor (talk) 15:31, 23 October 2017 (UTC)

Tech News: 2017-43

Latest tech news from the Wikimedia technical community. Please tell other users about these changes. Not all changes will affect you. Translations are available.

Recent changes

• You can use ccnorm_contains_any when you create an abuse filter. This can be used to look for multiple words or phrases within a string. It will find words where some characters have been replaced. You can read more in the documentation. [11]

Changes later this week

• When you search in some languages the search function could use specific other languages if the first language didn't work. This is called a fallback language. This didn't work properly and created bad searches. The search index is being fixed to work better. [12]
• The new version of MediaWiki will be on test wikis and MediaWiki.org from 24 October. It will be on non-Wikipedia wikis and some Wikipedias from 25 October. It will be on all wikis from 26 October (calendar).

Meetings

• You can join the next meeting with the Editing team. During the meeting, you can tell developers which bugs you think are the most important. The meeting will be on 24 October at 18:30 (UTC). See how to join.
• You can join the technical advice meeting on IRC. During the meeting, volunteer developers can ask for advice. The meeting will be on 25 October at 15:00 (UTC). See how to join.

Future changes

• There is a Structured Commons community focus group for Commons and Wikidata contributors who want to give input on structured data on Wikimedia Commons. You can sign up to join it. [13]

Tech news prepared by Tech News writers and posted by bot • Contribute • Translate • Get help • Give feedback • Subscribe or unsubscribe.

18:18, 23 October 2017 (UTC)

Mitch Halpern

I got a message from you to resize the image file to conform with Fair Use but when I try uploading a smaller image I get the error message: "File extension ".tiff" does not match the detected MIME type of the file (image/png)". I've tried changing the extension and nothing seems to work, so I don't understand what I am supposed to do. Thanks, Evenrød (talk) 06:07, 21 October 2017 (UTC)

@Evenrød: That's an easy one to answer (I think) - the image on Wikipedia is a TIFF file, I suspect you have reduced it and saved it as a PNG file - it's a system limitation that you can't change file types. Normally a bot would reduce the image automatically the next day, but they can only do jpg, png, and most gifs, so tiff, svg, and pdf need a manual reduction. The image when reduced needs to be saved as a TIFF - if that's an issue with your software, then let me know, and I can do it with PhotoShop. If you use the whole image, then the max size to fit the NFCC guideline (100,000 pixels) would be 370 x 269. You might want to consider a small crop of the sides before reduction to allow a bigger image of the person (it also would show better in the article, as the infobox template sizes the image by the width). Ronhjones  ^(Talk) 15:40, 21 October 2017 (UTC)

@Ronhjones: That seems to have worked. Thanks! Evenrød (talk) 06:57, 24 October 2017 (UTC)

Dorset Perception video

Hello Ron,
What is the reason for visually reducing File:Dorset Perception - Shpongle live at Psy-Fi 2017.webm in size? Only the audio is copyrighted, whereas the video recording is mine. Doesn't that mean I have the right to show the video in full size? Greetings, Nederlandse Leeuw (talk) 15:32, 26 October 2017 (UTC)

@Nederlandse Leeuw: That's an interesting case! As there is only one license (fair use) on the page, then that has applied to the whole file. If you wish to donate the video part then that will need a separate license. I suggest...

1. Change the heading "Licensing" to "Licensing (Audio)"
2. Follow that section with another section to be "Licensing (Video)", and add the license of your choice e.g. {{self|cc-by-sa-3.0}}?"
3. Add {{non-free no reduce}} as well - helps stop further reduction requests.
4. And then revert the video back to the larger size.

Hope that makes sense.  Ronhjones  ^(Talk) 16:15, 26 October 2017 (UTC)

It does, thanks, done! Greetings, Nederlandse Leeuw (talk) 18:49, 26 October 2017 (UTC)

Removal of fuboTV links

Good Afternoon,

I was recently updating certain television networks to include fuboTV. A streaming service that currently carries all these networks, similar to SlingTV or Playstation Vue, and it looks like you removed these? Could you share why and if there's a way for us to get our links on the page. It isn't my intention to spam users, and it's possible I may have been going about this the wrong way. Any insight here would be greatly appreciated.

Thank you! BBhajan (talk) 21:43, 27 October 2017 (UTC)

@BBhajan: External links have to follow the External links policy - WP:EL. You cannot put them in the body of an article, they have to go into the external links section at the end - but only if they are suitable - it is unlikely that links to a streaming service would be suitable. Ronhjones  ^(Talk) 21:51, 27 October 2017 (UTC)

Ronhjones Goguryeo–Sui War

dear Ronhjones https://en.wikipedia.org/wiki/Goguryeo%E2%80%93Sui_War Why do you protect the wiki document that ruined by Wandrative it? Wandrative believe and claim 'Nationalist pseudohistory' Wandrative He is a person who exaggerates Korean history unconditionally. You protect the document so many people read the wrong history. Protect documents from distortion ruined by Wandrative

Edit warring always results in protection. Pages are constructed by consensus. Discuss changes on the talk page. Use {{Edit Protected}} to suggest changes. Ronhjones  ^(Talk) 22:44, 29 October 2017 (UTC)

Hello. Just in case someone is interested and is not able to find the talk page discussion about the topic, it has been going on in the talk page: Goguryeo-Sui War. The title of the topic has been oddly named as: 'Protected edit request on 15 October 2017' by User:Dldusgml1234. Quite a name that seems to be off content (I suggest people to go through it). Within the section, User:Dldusgml1234 and User:Lathdrinor has been participating alongside myself. As it would be obviously apparent even on this page alone, User:Dldusgml1234 has resorted to continuous Wikipedia:Harassment and name callings thoroughly (and does not add reasons why) - without focusing on the actual topic of debate itself. During the actual times when he minutely focuses on the content, User:Dldusgml1234 was not hesitant to use logical fallacies such as Onus probandi, Post hoc ergo propter hoc, and the Historian's fallacy.

If I were to go into the shell of User:Dldusgml1234 and tell what I recognize about him in his manner:

1 - User:Dldusgml1234 has been 'ruining' various Goguryeo related articles. He desires to only represent the minimum estimation and erase the maximum, while I try to represent both. He also removed random unrelated content within the articles; Goguryeo and Goguryeo-Sui War repetitively.

2 - User:Dldusgml1234 is the one trying to enforce his own Nationalist pseudo-historical views - he erases all other angles of information that are conflicting with his own 'opinions'. I recognize that he is an Chinese individual (Despite his over enthusiastic and vigorous claims of him being 'Korean' - nobody asked him or wanted to know) who participates in numerous Chinese Historical Theft Campaigns/ or if he is indeed 'Korean', as he passionately claims - he is highly possibly a member of an extreme right-wing South-Eastern Korean who directly descends from the Silla. They are notorious for their active participation of 'belittling' Goguryeo whilst 'glorifying' Silla.

3 - User:Dldusgml1234 fabricates Korean history unconditionally, he tries to remove any positive aspects of history that portrays Goguryeo.

-Furthermore, I cant believe how he can come to this level of name calling and reasoning when the topic of debate was simply about representing BOTH the minimum count(600,000) and the maximum count (3,000,000), or not representing them at all. I emphasize once again that he participated in active Wikipedia:Vandalism, as he erased random sourced unrelated content withing the articles repeatedly. Wandrative (talk) 17:16, 30 October 2017 (UTC)

Tech News: 2017-44

Latest tech news from the Wikimedia technical community. Please tell other users about these changes. Not all changes will affect you. Translations are available.

Recent changes

• You can now block users from emailing you through the Wikimedia wikis. [14]

Changes later this week

• The new version of MediaWiki will be on test wikis and MediaWiki.org from 31 October. It will be on non-Wikipedia wikis and some Wikipedias from 1 November. It will be on all wikis from 2 November (calendar).

Meetings

• You can join the next meeting with the Editing team. During the meeting, you can tell developers which bugs you think are the most important. The meeting will be on 31 October at 18:30 (UTC). See how to join.
• You can join the technical advice meeting on IRC. During the meeting, volunteer developers can ask for advice. The meeting will be on 1 November at 16:00 (UTC). See how to join.

Tech news prepared by Tech News writers and posted by bot • Contribute • Translate • Get help • Give feedback • Subscribe or unsubscribe.

00:20, 31 October 2017 (UTC)

File:Monckton1.jpg

Why are you deleting revisions and requesting reduction of a file which is listed as PD? --Stefan2 (talk) 21:58, 2 November 2017 (UTC)

Why do editors put {{Orphaned non-free revisions}} on such an image so that RonBot tags it for being too big...? Reverted, thanks. Ronhjones  ^(Talk) 22:04, 2 November 2017 (UTC)

I suppose User:Kailash29792 simply made a mistake, but I hope RonBot always requests a manual review if the file is listed as free. --Stefan2 (talk) 22:54, 2 November 2017 (UTC)

• File:P47d photo small.jpg is another one. Tagged by the same user, so maybe his edits to the file namespace should be checked for errors. --Stefan2 (talk) 00:03, 3 November 2017 (UTC)

@Stefan2: Fixed that as well. I've scanned through past uploads - nearly all film posters and non-free, I think probably tagged in error - just followed a habit of uploading and then added {{Orphaned non-free revisions}}. Ronhjones  ^(Talk) 00:33, 3 November 2017 (UTC)

Tech News: 2017-45

Latest tech news from the Wikimedia technical community. Please tell other users about these changes. Not all changes will affect you. Translations are available.

Recent changes

• You will no longer see the patrol log on Special:Log unless you specifically select it. [15]

Changes later this week

• The 2017 Community Wishlist Survey begins on 6 November. You can post proposals from 19:00 UTC and until November 19.
• The new version of MediaWiki will be on test wikis and MediaWiki.org from 7 November. It will be on non-Wikipedia wikis and some Wikipedias from 8 November. It will be on all wikis from 9 November (calendar).

Meetings

• You can join the technical advice meeting on IRC. During the meeting, volunteer developers can ask for advice. The meeting will be on 8 November at 16:00 (UTC). See how to join.

Future changes

• URLs that link to sections on Wikimedia wikis with non-Latin scripts have looked like this: https://ru.wikipedia.org/wiki/Википедия#.D0.98.D1.81.D1.82.D0.BE.D1.80.D0.B8.D1.8F instead of https://ru.wikipedia.org/wiki/Википедия#История. This will soon be fixed. Old links will still work. [16][17]

Tech news prepared by Tech News writers and posted by bot • Contribute • Translate • Get help • Give feedback • Subscribe or unsubscribe.

18:45, 6 November 2017 (UTC)

File:Liberators-Kultur-Terror-Anti-Americanism-1944-Nazi-Propaganda-Poster.jpg

If that image is further significantly reduced, then it will become almost useless for its intended purpose (some of the text is already almost unreadable). It's not an album cover... AnonMoos (talk) 07:38, 6 November 2017 (UTC)

@AnonMoos: Tag changed Ronhjones  ^(Talk) 17:07, 6 November 2017 (UTC)

Thanks -- the details of the fair-use templating/tagging system is confusing to me, and I didn't know that option existed... AnonMoos (talk) 00:25, 7 November 2017 (UTC)

Sorry

Sorry, wrong user talk--87.239.38.118 (talk) 02:18, 7 November 2017 (UTC)

Ronnie O max

Hi Ron, I noticed you just reduced the image at File:Ronnie O'Sullivan's first maximum break.gif. I had tried to do this myself when it was tagged but it broke the animation. I was wondering which package you used to do? Betty Logan (talk) 01:37, 12 November 2017 (UTC)

@Betty Logan: https://ezgif.com/resize is the only one I've found, but it does work well. You can make it get the file for you by entering the url of the gif - click on the image and copy the url - e.g. https://upload.wikimedia.org/wikipedia/en/c/c2/Ronnie_O%27Sullivan%27s_first_maximum_break.gif. Pity it won't send it back direct! Ronhjones  ^(Talk) 01:40, 12 November 2017 (UTC)

File:Luneta Tower.jpg

Hi Ronhjones, I don't think its necessary to reduce the size of File:Luneta Tower.jpg which you've tagged since the file is already has low resolution. It's a poor photocopy of an image depicting a proposed building which never got built.Hariboneagle927 (talk) 08:42, 11 November 2017 (UTC)

@Hariboneagle927: Non-free images are only allowed in articles, so the size justification has to relate to the depicted size in the article. Anyway, I do see that it is a poor image, and to reduce it 268x372, might be extreme (always difficult until the bot comes along and actually does it!), once wiki then reduces it to fit the infobox. I have therefore gone back to the original with my large PC screen and resampled it as big as possible, then reduced it with a slightly tighter side crop (to keep more height - the guideline is based on area, and keeping unwanted black is not a good idea). So it's now only slight;y shorter that the first upload and I think just as sharp - compare https://upload.wikimedia.org/wikipedia/en/archive/8/84/20171111141824%21Luneta_Tower.jpg and https://upload.wikimedia.org/wikipedia/en/8/84/Luneta_Tower.jpg - side by side in two browser windows. Ronhjones  ^(Talk) 14:33, 11 November 2017 (UTC)

Okay, I understand.Hariboneagle927 (talk) 02

45, 12 November 2017 (UTC)

Tech News: 2017-46

Latest tech news from the Wikimedia technical community. Please tell other users about these changes. Not all changes will affect you. Translations are available.

Changes later this week

• The diff you see when you compare two different versions of a page has changed on MediaWiki.org and the test wiki. This is to make it easier to find a text change in a moved paragraph. It will hopefully soon come to more wikis. You can report bugs in Phabricator. [18]
• A new user group on Commons will be able to upload MP3 files. The plan is to have this user group from 17 November. [19]
• Wikis using Flagged Revisions will get the New filters for Edit Review by default on the recent changes pages. It will be possible to opt-out in user preferences. [20]
• The new version of MediaWiki will be on test wikis and MediaWiki.org from 14 November. It will be on non-Wikipedia wikis and some Wikipedias from 15 November. It will be on all wikis from 16 November (calendar).

Meetings

• You can join the technical advice meeting on IRC. During the meeting, volunteer developers can ask for advice. The meeting will be on 15 November at 16:00 (UTC). See how to join.

Future changes

• Support for uploading and viewing 3D models is coming soon to Wikimedia Commons. The feature will support the .STL file format. You can see an example on the test wiki. [21]

Tech news prepared by Tech News writers and posted by bot • Contribute • Translate • Get help • Give feedback • Subscribe or unsubscribe.

19:19, 13 November 2017 (UTC)

File:Klah rug.jpg

Just so you know: I already created a Commons file for this (same name) . Turns out to be PD for life + 70 years. If you shrunk the Commons image size, please restore. Thanks, Pete Tillman (talk) 21:19, 13 November 2017 (UTC), OP, years ago

Commons page is fine. Sorry to be kind of clueless about this stuff. Anyway, it's definitely PD, so feel free to speedy-delete my old WP upload. Cheers, Pete Tillman (talk) 21:26, 13 November 2017 (UTC)

@Tillman: Deleted as "now on commons" Ronhjones  ^(Talk) 22:29, 13 November 2017 (UTC)

NFCC guide implemented on NHL uniform images

Hi, what is the specific item in NFCC guidelines by which the images of NHL uniforms have been reduced in size? Tdunsky (talk) 21:03, 14 November 2017 (UTC)

@Tdunsky: The guideline for non-free images is at WP:Image resolution, and is 100,000 pixels. It has been that since mid 2011, however until a year ago (when the search engine improved) it had not been possible to search for oversized images, and thus there was a considerable backlog (300,000 oversize images). Being able to tag / get images reduced / revdel old images takes some effort (and some new bots) and we are still not finished - currently images of fileres: 393 have just been done. (fileres: is the square root of pixels - a strange Wiki variable!) It is a guideline as there will be a few isolated cases where 100,000 pixels losses so much detail that it makes the image unusable - these are often screenshots where the text just gets corrupted at that resolution (although, there can usually be some reduction from the original). Obviously for over size images, one would expect a good rationale to be added to show that need. Typically of the oversized images examined, 99.8% have been reduced without an issue. The reduction (by bot) is a straightforward size reduction, sometimes it may be better to crop the image to 100,000 pixels, but that can only be done manually - that, of course, can best be done during the fixed 7 days between reduction and revdel. Revdel is now done by my bot and will not revdel any file with a current oversized image, but instead flags it as a problem for a manual admin review. Ronhjones  ^(Talk) 22:05, 14 November 2017 (UTC)

Windows screenshots again

You are still adding non-free reduce templates to Screenshots of Microsoft Windows again, after you said you'd add an exception for these. Keep your word. Warren -talk- 05:18, 15 November 2017 (UTC)

@Warren: My exception list is currently...

• Non-free Microsoft screenshot
• Non-free no reduce
• Non-free manual reduce
• Orphaned
• Non-free reduce
• Non-free manual gif reduce
• OTRS
• Di-
• Ffd

Not sure why it's not skipping the images. More investigation required. I might go belt and braces and add {{Non-free no reduce}} to all the Microsoft screenshots. Thanks for the heads-up. Ronhjones  ^(Talk) 20:31, 15 November 2017 (UTC)

CSD

Hi, Ronjhones,

Greetings! How could User:Vivek13791/sandbox not pass G11 esp. when his stated intent is to use WP as a business profile and uplift his business per this edit.G11 is applicable in any-space and this was not even close to the border-line.Anyway, all of your declined speedies are at MfD.Warm regards:)Winged Blades ^Godric 16:42, 19 November 2017 (UTC)

@Blades of Godric: It's a draft article - i.e not finished. Users are allowed to create drafts either in Draft space, or as a sub page of their user name - I've created most of my drafts that way, and at first there is no way they will pass the policies. Note it must be a subpage as they are not indexed by Google, unlike the main user page which is indexed (and can attract a U5 csd if found there). If you check the page HTML source, you will find <meta name="robots" content="noindex,follow"/> on line 21. An advert in a subpage, is hardly an advert if no one sees it... Ronhjones  ^(Talk) 16:50, 19 November 2017 (UTC)

Tech News: 2017-47

Latest tech news from the Wikimedia technical community. Please tell other users about these changes. Not all changes will affect you. Translations are available.

Recent changes

• If you use the Chrome web browser on Android you can see a download icon on the mobile website. You can download a formatted PDF. It will work in other mobile browsers in the future. [22]
• The abuse filter now has a function called get_matches. You can use it to store matches from regular expressions – one of each capturing group. You can read more in Phabricator.

Problems

• Last week's MediaWiki version didn't come to all Wikipedias because of a database crash. It will be on all wikis on 20 November. [23][24][25]

Changes later this week

• There is no new MediaWiki version this week.

Meetings

• You can join the next meeting with the Editing team. During the meeting, you can tell developers which bugs you think are the most important. The meeting will be on 21 November at 19:30 (UTC). See how to join.
• You can join the technical advice meeting on IRC. During the meeting, volunteer developers can ask for advice. The meeting will be on 22 November at 16:00 (UTC). See how to join.

Future changes

• Language converter syntax will no longer work inside external links. Wikitext like http://-{zh-cn:foo.com; zh-hk:bar.com; zh-tw:baz.com}- must be replaced. You will have to write -{zh-cn: http://foo.com ; zh-hk: http://bar.com ; zh-tw:http://baz.com }- instead. This only affects languages with Language Converter enabled. Examples of such languages are Chinese and Serbian. This will happen next week. [26][27]

Tech news prepared by Tech News writers and posted by bot • Contribute • Translate • Get help • Give feedback • Subscribe or unsubscribe.

19:19, 20 November 2017 (UTC)

The Signpost: 24 November 2017

• News and notes: Cons, cons, cons

• Arbitration report: Administrator desysoped; How to deal with crosswiki issues; Mister Wiki case likely

• Technology report: Searching and surveying

• Interview: A featured article centurion

• WikiProject report: Recommendations for WikiProjects

• In the media: Open knowledge platform as a media institution

• Traffic report: Strange and inappropriate

• Featured content: We will remember them

• Recent research: Who wrote this? New dataset on the provenance of Wikipedia text

• Humour: Good faith (but still incomprehensible)

* Read this Signpost in full * Single-page * Unsubscribe * MediaWiki message delivery (talk) 02:39, 24 November 2017 (UTC)

Non-free images

Hi. If I upload another non-free image, what size should I make it to comply with the smaller size requirement? Onel5969 ^{TT me} 21:06, 24 November 2017 (UTC)

@Onel5969: Easy choice...

1. http://web.archive.org/web/20160202074403/http://tools.wmflabs.org/image-resize-calc/ will work it out for you ----- OR
2. Just put {{non-free reduce}} at the top of the source text once uploaded, and it will be done for you in 24h.

Ronhjones  ^(Talk) 21:10, 24 November 2017 (UTC)

Thank you, will do in future. Onel5969 ^{TT me} 21:13, 24 November 2017 (UTC)

Thanks

When somebody makes what I think is a particularly good or helpful edit, or completes a job that I started, I like to use the notification system to thank them, but for some reason the notification system doesn't extend to the deletion log. Since I'm quite active on the image front and constantly making more work for tireless editors like you to complete I'd like to thank you for your efforts. Here's the edit in question:

• 20:43, 24 November 2017 Ronhjones (talk | contribs) changed visibility of a revision on page File:Coleman logo.jpg: content hidden (Orphaned non-free file(s) deleted per F5)

..Just one of a great many, which I don't really have time to address individually. I wish that the notification could be extended to cover all kinds of edit. If you know of anywhere to request such changes please feel free to point them to this post. Regards, nagualdesign 21:06, 24 November 2017 (UTC)

@Nagualdesign: Suggestions to software changes can be made at Wikipedia:Village_pump_(technical) Ronhjones  ^(Talk) 21:12, 24 November 2017 (UTC)

 Done I left a message there. Fingers crossed. nagualdesign 02:09, 25 November 2017 (UTC)

Richardson family murders

Can you make any comment on the subject of the removal of the perpetrator's name from this article? The information has been revdel'ed more than 50 times from the article and its talk page, and you removed it 22:21, February 27, 2014‎ under OTRS ticket 2014022710014548 . An editor has restored her name twice and that editor and a second editor are arguing that the OTRS removal is irrelevant and that they may restore the information without discussing it with you, any other OTRS agen, or raising it on the OTRS board. The talk page thread is Talk:Richardson family murders#Adding daughters name, as she is now over 18 Meters (talk) 07:21, 25 November 2017 (UTC)

@Meters: Obviously I cannot say who the ticket was from. I think my text in the edit summary will convey enough of an answer. This was a one-off removal as (let's us say) a courtesy deletion, and then see how any consensus later evolved - I was not prepared to revert it again, partly because I don't know enough about any relevant US Law - we have the same system here in the UK, as Canada. Also at the time I could not find much supporting data (obviously the Canadian papers referenced, had removed those pages because of the time that had past).

File talk:Nanduri Sambasiva Rao Director General of Police Andhra Pradesh.jpg

Contested deletion

This page is not unambiguously promotional, because... (your reason here) --CSHN Murthy (talk) 03:10, 25 November 2017 (UTC) the article is not promotional; it deals with facts, and describe a person who turned a role model by ascending to highest position of State of Andhra Pradesh from a scratch. In Indian democratic and political system it is very difficult for a person, who hails from a low middle income group, to reach this position. The person is a pride of the town Ongoleby virtue of becoming an illustrious son of its soilCSHN Murthy (talk) 03:10, 25 November 2017 (UTC)

@CSHN Murthy: ??? I have not deleted any of your pages. Just a copyright image, as is stated on your talk page, and the editors there are correct that it cannot be a non-free image until he dies. Ronhjones  ^(Talk) 16:52, 25 November 2017 (UTC)

Contested deletion

File talk:Nanduri Sambasiva Rao Director General of Police Andhra Pradesh.jpg‎;

I Contested deletion of the above file image under non-free content.However the story came under attack from another editor of wiki who responded to me saying that the content uploaded was under copyright holder and free license. In this context I wish to apologize because when I uploaded the image, it was this box which appeared after upload and it was written there as copyright holder and free license. I could have checked it for the non-free content policy of wiki which allows images/photos from public domain such as news papers and books besides websites. It also allows where there is no possibility of having a direct image of the object or person. I have uploaded the image of Sambasiva Rao, Nanduri from the linked in website available in public domain. Hope this satisfies you and I request you to kindly restore the image immediately. I am a regular contributor for wikipedia and am quite busy writing for the last one month for wiki under Asian month. I must also recall the call from wikipedia for uniformed forces. Hence do not block the story or remove the image. Though I am reading the relevant wikipolicies, I am failing in terms of searching and scrolling for ticking the exact item under which the image falls. Also some editors of wikipedia are not able to understand the socio and historical significance of stories I am writing for next generation wiki readers both within India and abroad. Kindly help and avoid blcoking the stories and images.CSHN Murthy (talk)

==Please reply on my CSHN Murthy at the earliest.CSHN Murthy (talk) 13:13, 25 November 2017 (UTC)

Replied on talk page Ronhjones  ^(Talk) 16:57, 25 November 2017 (UTC)

Eight years of adminship, today.

Wishing Ronhjones a very happy adminship anniversary on behalf of the Wikipedia Birthday Committee! Chris Troutman (talk) 03:12, 26 November 2017 (UTC)

Doesn't time fly... Ronhjones  ^(Talk) 14:50, 26 November 2017 (UTC)

Protection - List of disability-related terms

Ron, you recently put List of disability-related terms with negative connotations under pending changes. In view of the continued high volume of IP editing, with no discussion or edit summaries, would you consider upgrading it to semi-protection for a period? It's a sensitive topic and there are lots of issues but they need talking about: Noyster (talk), 14:25, 26 November 2017 (UTC)

@Noyster: I see what you are up against. Protection level changed. Ronhjones  ^(Talk) 14:52, 26 November 2017 (UTC)

Cold Water Cowboys file controversy

Hi. I have a question about This file. It is not part of the film, but a personal work (photograph) of the producer Tyson Hepburn. He asked me to upload this file. He is willing to give out this file under the Creative Commons licence and would like to have full version (not reduced) of this file available. How to proceed with this? He wrote an email to the OTRS team about this file, but go no reply and file still displays in its minimal version. -- Bbarmadillo (talk) 19:12, 26 November 2017 (UTC)

@Bbarmadillo: There are two e-mails on OTRS - ticket 2017112210009497 to photosubmission, where he has replied, and they have replied back and are now waiting for confirmation of copyright holder and the license required. Also ticket 2017112310014005 to permission-commons - who won't have a clue where it is as it's not (yet) on commons - that was 2 days ago and there is a long backlog there. I suggest he replies to 2017112210009497 - they will ask the same questions on the other ticket - when they get round to it. Ronhjones  ^(Talk) 19:29, 26 November 2017 (UTC)

@Ronhjones: Thank you. Told him to answer ticket 2017112210009497. -- Bbarmadillo (talk) 03:58, 27 November 2017 (UTC)

Nazi eugenics

Did you mean to set full protection on this article indefinitely? ~Oshwah~^{(talk) (contribs)} 03:49, 27 November 2017 (UTC)

@Oshwah: Probably not... Set to 1st Dec Ronhjones  ^(Talk) 14:53, 27 November 2017 (UTC)

User: MacTheSlayer

Hell Ron, Could I please bring to your attention the activities of MacTheSlayer (talk · contribs · deleted contribs · logs · filter log · block user · block log) whom you blocked some time ago for three months. They have now resumed adding incorrect "sources" which do not agree with the quoted ideology. an I leave this with you please? Regards, David, David J Johnson (talk) 14:38, 27 November 2017 (UTC)

@David J Johnson: Oh Dear... Checked last edit, the phrase added did not appear in the reference... Re-blocked. Ronhjones  ^(Talk) 14:58, 27 November 2017 (UTC)

Ron, Many thanks for your help. David J Johnson (talk) 15:01, 27 November 2017 (UTC)

Tech News: 2017-48

Latest tech news from the Wikimedia technical community. Please tell other users about these changes. Not all changes will affect you. Translations are available.

Recent changes

• You can now test the new advanced search function beta feature on mediawiki.org. It makes it easier to use some of the special search functions that most editors don't know exist. It will come to German and Arabic Wikipedia this week. It will come to more wikis later. [28]
• You can now upload large files with the Internet Archive upload tool. Previously you could not upload files larger than 100 MB. [29]
• You can now use the Timeless skin on all wikis. You can choose skins in Special:Preferences#Appearance. [30]

Changes later this week

• The new version of MediaWiki will be on test wikis and MediaWiki.org from 28 November. It will be on non-Wikipedia wikis and some Wikipedias from 29 November. It will be on all wikis from 30 November (calendar).

Meetings

• You can join the next meeting with the Editing team. During the meeting, you can tell developers which bugs you think are the most important. The meeting will be on 28 November at 19:30 (UTC). See how to join.
• You can join the technical advice meeting on IRC. During the meeting, volunteer developers can ask for advice. The meeting will be on 29 November at 16:00 (UTC). See how to join.

Tech news prepared by Tech News writers and posted by bot • Contribute • Translate • Get help • Give feedback • Subscribe or unsubscribe.

20:30, 27 November 2017 (UTC)

Outstanding contributions recognition

Outstanding Contributions Recognition

Ron, over the time I've spent here, I've seen you regularly and most diligently manning the speedy desk, and quite speedily at that. Your work and contributions are absolutely impeccable. I don't know how you've kept the motivation going on through close to the decade you've been an administrator, but what you're doing right now, makes you a true outstanding contributor, quite deserving of the "Outstanding Contributions Award" (I know, sounds tacky, but believe me, it works :D) Ron, keep up the great work! :) Love, Lourdes

Thanks for the compliment :-) Ronhjones  ^(Talk) 00:09, 28 November 2017 (UTC)

Al Jazeera calligraphy animation

When resizing File:Al_jazeera_Calligraphy_Animation.gif (an animation intended to illustrate Arabic calligraphic composition), you seem to have completely eliminated the animation. Is there any chance that you could upload a resized version that retains the animation? Failing that, could you restore the original? Downsizing the animation doesn't offer any protection to a logo that's found elsewhere on Wikipedia as an svg. Baradys (talk) 01:19, 29 November 2017 (UTC)

@Baradys: Oooh, no idea what went wrong with that. Well spotted, thanks. Now all fixed. Ronhjones  ^(Talk) 01:43, 29 November 2017 (UTC)

Thank you. Baradys (talk) 06:39, 29 November 2017 (UTC)

ANI Experiences survey

The Wikimedia Foundation Community health initiative (led by the Safety and Support and Anti-Harassment Tools team) is conducting a survey for en.wikipedia contributors on their experience and satisfaction level with the Administrator’s Noticeboard/Incidents. This survey will be integral to gathering information about how this noticeboard works - which problems it deals with well, and which problems it struggles with.

The survey should take 10-20 minutes to answer, and your individual responses will not be made public. The survey is delivered through Google Forms. The privacy policy for the survey describes how and when Wikimedia collects, uses, and shares the information we receive from survey participants and can be found here:

• https://wikimediafoundation.org/wiki/2017_AN/Incidents_Survey_Privacy_Statement

If you would like to take this survey, please sign up on this page, and a link for the survey will be mailed to you via Special:Emailuser.

• Sign up here to receive a link to a survey

Thank you on behalf of the Support & Safety and Anti-Harassment Tools Teams, Patrick Earley (WMF) talk 18:24, 1 December 2017 (UTC)

Image size

In your revert on File:Kobayashi ga Kawai Sugite Tsurai v1 cover.jpg, you say "There is a proper guideline of 100,00 pixels". However, the policy Wikipedia:Non-free content criteria only states under 3b that minimal extent of use requires "Low- rather than high-resolution". Wikipedia:Non-free content#Image_resolution, a guideline, states in the first sentence:

There is no firm guideline on allowable resolutions for non-free content; images should be rescaled as small as possible to still be useful as identified by their rationale, and no larger. This metric is very qualitative, and thus difficult to enforce.

It's clearly something left up to interpretation and can't be blindly applied to every type of media and in every context. The 100,000 figure there only serves as a baseline, not some hard-line to die over. As I stated earlier, I based my 300px width on a careful survey of uploaded manga covers. This serves as a de facto accepted standard rather than your arbitrary "rule". I also experimented with various widths to make sure the legibility of line art and character faces wouldn't be obscured (both very in manga covers). You can actually see an example of the damage you're causing on File:The Strange Tale of Panorama Island Suehiro Maruo.jpg, where the line art looks like blurred garbage and none of the details are recognizable anymore, all for the sake of 30px. By any reasonable interpretation, 300 pixels is really small and unusable for printing or depriving the copyright holder, which is the whole reason for the restricting. Please try to understand the spirit of the law rather than the letter. You might try to argue that the thumbnail width is 230px so nothing needs to be larger than that, but you'd ignore users who have it larger for accessibility purposes and the fact that screens are only getting higher resolution. On the common 1920px resolution, it's only 16% of the screen and on 4K (3840px wide) screens, it's a measly 8%. I'd also like to remind you that Wikipedi'a standards for non-free content are actually more strict than the legal concept of fair use, so you're also being more overzealous than an already cautious policy. I suggest you better spend your time elsewhere than crusading on a mere 300 pixels when there are countless copyvios on Commons and so many articles missing images. People like you who waste others' time with wikibureaucracy when they'd rather be productively contributing are what's wrong with Wikipedia. Opencooper (talk) 22:43, 1 December 2017 (UTC)

@Opencooper: and the guideline says quite clearly You also may wish to add the {{non-free no reduce}} template to the image rationale page to indicate that your image resolution purposely exceeds the 0.1 megapixels guideline, though this still requires you to include a valid rationale that explains this reasoning; large images using this template without a rationale to explain the large size may be reduced despite this. - I see nothing in the FUR to warrant an oversized image - there is no critical commentary in the article which requires a higher level of detail. The reduction to meet the guideline is not a great one and would result in size of 251 x 397. Ronhjones  ^(Talk) 23:19, 1 December 2017 (UTC)

As stated before 0.1 MP is only a guideline and 300px is still pretty close to it. Note for example that Commons requires 2MP for featured images. This is nowhere even close to that or the 300dpi usually necessary for printing (in fact, you'd only have a 1-inch wide print at this resolution). You're literally splitting hairs over the tiniest of differences. If this was a image with maybe 700px or more, I'd sympathize with you and say that some explanation is warranted. I've already given you my reasoning for these images though and don't believe the images are large enough to merit any special explanation on their FUR. As for it only being a reduction of 50px, sure, but I don't appreciate having to look at each image and seeing if the bot destroyed detail like on the Panorama cover above, and I also don't believe in making images lower-res than they need to for the accessibility reason given before. It's a waste of time for both of us; surely you have something more productive you could be doing... Opencooper (talk) 23:35, 1 December 2017 (UTC)

@Opencooper:We have a guideline and there were way too many well oversized images. Others have agreed with me that it is not an acceptable situation, and could have possible legal consequences to leave a high number of oversized images without a full rationale. I did not set the guideline, that was done way back in 2011 - but it's only been a year since it's been able to search for all the oversized images. I think we will have to agree to disagree. As for commons, I delete and find plenty of copyvios every day over there, and write e-mails at OTRS - non-free images is just a small part of my daily edits. Ronhjones  ^(Talk) 23:46, 1 December 2017 (UTC)

Yeah I guess we'll just have to agree to disagree. However, since your message, you've tagged three more of my uploads for reduction... Most of my manga cover uploads are at 300px and I have over 100 uploads and will continue to upload at 300px, so I'd appreciate if you didn't tag my images unless you have community consensus to do so (I don't have a problem with reducing those larger or other people's uploads, and in fact a few on my watchlist have been reduced; 300px is just where I draw the line). If AWB has a way to filter by uploader do that, or if you need me to add a hidden category I can do that as well, but using an automated tool is not a reason for not checking your edits. Opencooper (talk) 00:05, 2 December 2017 (UTC)

We'll have to generate a consensus then. Ronhjones  ^(Talk) 00:28, 2 December 2017 (UTC)

ArbCom 2017 election voter message

Hello, Ronhjones. Voting in the 2017 Arbitration Committee elections is now open until 23.59 on Sunday, 10 December. All users who registered an account before Saturday, 28 October 2017, made at least 150 mainspace edits before Wednesday, 1 November 2017 and are not currently blocked are eligible to vote. Users with alternate accounts may only vote once.

The Arbitration Committee is the panel of editors responsible for conducting the Wikipedia arbitration process. It has the authority to impose binding solutions to disputes between editors, primarily for serious conduct disputes the community has been unable to resolve. This includes the authority to impose site bans, topic bans, editing restrictions, and other measures needed to maintain our editing environment. The arbitration policy describes the Committee's roles and responsibilities in greater detail.

If you wish to participate in the 2017 election, please review the candidates and submit your choices on the voting page. MediaWiki message delivery (talk) 18:42, 3 December 2017 (UTC)

Tech News: 2017-49

Latest tech news from the Wikimedia technical community. Please tell other users about these changes. Not all changes will affect you. Translations are available.

Recent changes

• It is now possible to upload MP3 files to Commons. Only users with MP3 file upload rights can upload MP3 files. [31]
• You can now use live updates for recent changes if you use the new filters. This feature updates the filtered recent changes every three seconds when you activate it. [32]
• There is an experimental onion service for Wikimedia projects. [33]

Changes later this week

• The new version of MediaWiki will be on test wikis and MediaWiki.org from 5 December. It will be on non-Wikipedia wikis and some Wikipedias from 6 December. It will be on all wikis from 7 December (calendar).
• Very old versions of the Opera Web browser are no longer supported. This means that technical development will not be tested to make sure it works with those Opera versions. Use Opera 15 or above or another browser if you have problems. [34]
• Almost 170 wikis with no high-priority errors in Linter categories will switch to use the Remex parsing library. This is to replace Tidy. A few larger wikis such as German and Italian Wikipedia will also make this switch. It will happen on 5 December. Other wikis will be recommended to switch soon when they have fixed the errors that must be fixed. Tidy will be removed in the middle of 2018. [35][36]

Meetings

• You can join the next meeting with the Editing team. During the meeting, you can tell developers which bugs you think are the most important. The meeting will be on 5 December at 19:30 (UTC). See how to join.
• You can join the technical advice meeting on IRC. During the meeting, volunteer developers can ask for advice. The meeting will be on 6 December at 16:00 (UTC). See how to join.

Future changes

• The 2017 Community Wishlist Survey will decide what the Community Tech team will work on next year. You can vote for wishes on the survey page until 10 December. You can see what has happened to last year's wishes on the 2016 results page.
• The Community Liaisons team at the Wikimedia Foundation is looking for active tech ambassadors. This is to make sure the Wikimedia communities get all the information they need about new features and can be involved in the technical development. [37]

Tech news prepared by Tech News writers and posted by bot • Contribute • Translate • Get help • Give feedback • Subscribe or unsubscribe.

17:51, 4 December 2017 (UTC)

Thanks!

Hello, Ronhjones. You have new messages at South Nashua's talk page.
You can remove this notice at any time by removing the {{Talkback}} or {{Tb}} template.

South Nashua (talk) 20:32, 4 December 2017 (UTC)

Hi

Hi, Please remind me the required size of photos. was it 300x300? oh and not bad with the clean up of pics. Artix Kreiger (talk) 19:24, 4 December 2017 (UTC)

@Artix Kreiger:. NFCC guideline is 100,000 pixels. Easy answer is to always add {{non-free reduce}} if you are not sure. Bot will reduce to max size for you under 24h - if no reduction required, the bot just removes the template. Ronhjones  ^(Talk) 21:32, 4 December 2017 (UTC)

List of All-Ireland Senior Football Championship finals

Please explain why my edits on All-Ireland_Senior_Football_Championship_finals appear to constitute vandalism. Thankyou Aburnarkle (talk) 08:57, 5 December 2017 (UTC)

@Aburnarkle:. No idea. Many apologies. I've been trying to work out (and searching) why I even went to the page - I have to assume that there must have been a report at WP:AIV - not that I can even find that now!. Looks like I must have clicked the wrong "talk" link by accident and should have done User talk:46.7.145.63 (now done). Sorry for the inconvenience. Ronhjones  ^(Talk) 20:38, 6 December 2017 (UTC)

Emesa helmet

Does this photograph really need to be reduced? It's already pretty small, and I'm worried that a further reduction will make some of the interesting details hard to see. One of the helmet's most distinctive features is the presence of holes beneath the eyes to increase vision, for example, and these would be hard to see if smaller (especially the notch in the lowest hole on each side: per an account of the helmet's restoration, "The small holes beneath the eyes in the visor had been designed so that the wearer could look down to the ground in front of him, but evidently they were not enough, and it is amusing to find that they had been enlarged, in each case, by a narrow notch cut in the central lobe, no doubt in an emergency as this adjustment is not the work of a craftsman."). Thanks, --Usernameunique (talk) 21:09, 6 December 2017 (UTC)

@Usernameunique: Why not let bot reduce it and see the result first. You then have 7 days to revert to the original. If you revert because the image has lost too much quality, then add {{non-free no reduce}} to stop further tagging. Ronhjones  ^(Talk) 21:22, 6 December 2017 (UTC)

Your draft article, Draft:Anthony Ortega (musician)

Hello, Ronhjones. It has been over six months since you last edited the Articles for Creation submission or Draft page you started, "Anthony Ortega".

In accordance with our policy that Wikipedia is not for the indefinite hosting of material deemed unsuitable for the encyclopedia mainspace, the draft has been nominated for deletion. If you plan on working on it further, or editing it to address the issues raised if it was declined, simply and remove the {{db-afc}}, {{db-draft}}, or {{db-g13}} code.

If your submission has already been deleted by the time you get there, and you wish to retrieve it, you can request its undeletion by following the instructions at this link. An administrator will, in most cases, restore the submission so you can continue to work on it.

Thanks for your submission to Wikipedia, and happy editing. TKK! bark with me! 23:24, 9 December 2017 (UTC)

Not fair use?

Hi there, your bot placed a notice on an image I uploaded, File:Sensim_Sed_cushion_cover_by_Jessie_Newbery.png, I dont understand what i am suppose to do... there is a fair use rational for this image in the Jessie Newbery Article... --Peabodybore (talk) 19:09, 6 December 2017 (UTC)

@Peabodybore: File:Sensim Sed cushion cover by Jessie Newbery.png - nothing to do. It's all been done by robots. The non-free guideline is 100,000 pixels, Theo's bot has set the image as big as possible for you, and now my bot has deleted the unused versions - leaving just the one version showing. Ronhjones  ^(Talk) 20:34, 6 December 2017 (UTC)

ok cool, thanks. I have also worked on the Jessie Newbery article in which the image is used, so that the article covers the embroidery technique and design approach that are shown in this artwork.--Peabodybore (talk) 12:19, 11 December 2017 (UTC)

South Carolina Research Authority's Wiki Page

Hi Ron -

I hope you are doing well. I noticed the page for South Carolina Research Authority is quite out of date and was hoping to update it, but it is protected by you (thank you). The entire leadership section is out of date (people and salaries) and the realigned mission of SCRA is: to foster South Carolina's Innovation Economy by supporting entrepreneurs, enabling academic research and its commercialization, and connecting industry to innovators. The current page has a lot of discussion about the Applied Technologies sector which is no longer relevant. Any help you can provide to update the information is much appreciated!

Thanks Jessica Cokins (my contact information can be found on www.scra.org)

  — Preceding unsigned comment added by 206.74.178.105 (talk) 16:09, 11 December 2017 (UTC)

I've reduced the protection level. Do remember that any changes need to be supported by reliable sources - no original research WP:OR Ronhjones  ^(Talk) 16:34, 11 December 2017 (UTC)

Tech News: 2017-50

Latest tech news from the Wikimedia technical community. Please tell other users about these changes. Not all changes will affect you. Translations are available.

Recent changes

• URLs that link to sections on Wikimedia wikis with non-Latin scripts have looked like this: https://ru.wikipedia.org/wiki/Википедия#.D0.98.D1.81.D1.82.D0.BE.D1.80.D0.B8.D1.8F instead of https://ru.wikipedia.org/wiki/Википедия#История. This has now been fixed on all wikis. Old links will still work. [38]
• A new tag marks edits where a redirect was created or removed. This still works when the editor writes something else in the edit summary. You can see the tags for example in the recent changes feed, article history, user contributions or on your watchlist. [39]
• If you use Chrome on Android, you can now use the print to PDF button to create a PDF of an article. [40]
• Filter by number of edits or filter by time range have been grouped on a same menu on the recent changes page if you use the new filters. The "View new changes since $1" link is now more prominent. [41]
• Some of the web fonts that were provided by the Universal Language Selector extension are being removed. This is to reduce the load time on pages. The web fonts were added many years ago to help users read text in scripts which did not have fonts or had broken fonts. This is not the case any more. You can check the status page for a list of all web fonts and whether they are currently being used and especially for special requirements. [42]

Changes later this week

• The new version of MediaWiki will be on test wikis and MediaWiki.org from 12 December. It will be on non-Wikipedia wikis and some Wikipedias from 13 December. It will be on all wikis from 14 December (calendar).

Meetings

• You can join the next meeting with the Editing team. During the meeting, you can tell developers which bugs you think are the most important. The meeting will be on 12 December at 19:30 (UTC). See how to join.
• You can join the technical advice meeting on IRC. During the meeting, volunteer developers can ask for advice. The meeting will be on 13 December at 16:00 (UTC). See how to join.

Future changes

• You can discuss new or improved blocking tools with the Wikimedia Foundation Anti-Harassment Tools team. They will work on building better blocking tools. Leave comments on the talk page.

Tech news prepared by Tech News writers and posted by bot • Contribute • Translate • Get help • Give feedback • Subscribe or unsubscribe.

17:58, 11 December 2017 (UTC)

Youngblood

Hi, re your edit of the file File:Youngblood 01 cover.jpg, it is 87kb. What are our standards for size, as in how small does it have to be, so it is not too big? Thank you. Rybkovich (talk) 20:07, 11 December 2017 (UTC)

@Rybkovich: The guideline link as quoted in the banner is 100,000 pixels. This works for 99.9% of cases - it is a guideline as there are a small amount of images that do not reduce to the guideline without excessive corruption, and for this the guideline states - You also may wish to add the {{non-free no reduce}} template to the image rationale page to indicate that your image resolution purposely exceeds the 0.1 megapixels guideline, though this still requires you to include a valid rationale that explains this reasoning; large images using this template without a rationale to explain the large size may be reduced despite this. The guideline was set in 2011, but we did not have the means (then) to find the images that were in excess of the guideline. A quick calculation suggests your image will be 257x388 to meet the guideline. Hope that helps. Ronhjones  ^(Talk) 20:23, 11 December 2017 (UTC)

Got it. Thank you. Rybkovich (talk) 20:30, 11 December 2017 (UTC)

File:HP Gram Logo.png

...is only 304px high... --NapoliRoma (talk) 00:10, 14 December 2017 (UTC)

@NapoliRoma: The guideline is not the height or the width - that was dropped in 2011, it's the total area. Ronhjones  ^(Talk) 20:36, 14 December 2017 (UTC)

Non-free reduce tags

Greetings, Ronhjones. I've read User:Ronhjones/Reduce, but I'm still not clear on the size criteria used for the "non-free reduce" tagging. I'm pretty much focused on two things -- album covers, and film posters (or film video covers). My understanding of Wikipedia guidelines was that, for those images, anything that was 300 pixels or less in its shortest dimension was considered small enough. But I'm seeing some images of that size being tagged anyway, this being one example. — Mudwater ^(Talk) 23:11, 14 December 2017 (UTC)

@Mudwater: I do believe (but not 100% certain) that the 300px "idea" was pre 2011, when the current guideline was drawn up, where the area of an image is the measured value and 100,000 pixels is the desired maximum. Normally album covers (i.e. square) will end up at 316x316 pixels - I can confirm there are a lot at that size. The guideline is at WP:Image resolution - you can have bigger - but we would expect some sort of reason for that - as the pages says You also may wish to add the {{non-free no reduce}} template to the image rationale page to indicate that your image resolution purposely exceeds the 0.1 megapixels guideline, though this still requires you to include a valid rationale that explains this reasoning; large images using this template without a rationale to explain the large size may be reduced despite this.. Hope that helps. Ronhjones  ^(Talk) 23:35, 14 December 2017 (UTC)

I see. Thanks for explaining. — Mudwater ^(Talk) 23:38, 14 December 2017 (UTC)

thank you!

{{AFC submission}} was what it took! Many thanks! Barryraphael (talk) 00:12, 17 December 2017 (UTC)