User talk:DatGuy/Archives/2017/October


New topicon for EFH

FYI, I created {{Edit filter helper topicon}}. Noticed you were in the permission group and use topicons. Cheers ☆ Bri (talk) 14:30, 1 October 2017 (UTC)

The WikiProject Video Games Newsletter, Q3 2017

The WikiProject Video Games Newsletter
Volume 10, No. 3 — 3rd Quarter, 2017
  Previous issue | Index | Next issue  

Project At a Glance
As of Q3 2017, the project has:


Content


Project Navigation
To opt-out or sign up to receive future editions of this newsletter, click here to update the distribution list.
(Delivered ~~~~~)

MediaWiki message delivery (talk) 00:12, 2 October 2017 (UTC)

23:25, 2 October 2017 (UTC)

DatBot 6

Just an update, as I know you are busy. I've tried to examine the maths section of the code on the picture that is causing a problem. When you have time, please have a look at User:Ronhjones/ResizerTest. Ronhjones  (Talk) 20:54, 17 August 2017 (UTC)

(Non-administrator comment) User:Ronhjones, the API tells that the resolution is 471×415 pixels,[6] but if I open the actual JPG file in my web browser, then my web browser says 336×296. This looks weird. --Stefan2 (talk) 14:27, 18 August 2017 (UTC)
@Stefan2: I did suggest a bad file - looks like the bot is right and the Wiki image page is wrong - if on clicks the image to get to https://upload.wikimedia.org/wikipedia/en/7/7b/Everybody%27s_Fool_%28Evanescence_single_-_cover_art%29.jpg then that looks like the right size, it's the image on File:Everybody's Fool (Evanescence single - cover art).jpg which is obviously too big, suspect it will just need a re-upload over the top to fix the page data. DatGuy, since the bot is doing it's job OK, and getting the true data, are you happy if we start it? Ronhjones  (Talk) 17:51, 18 August 2017 (UTC)
@Ronhjones: Sure, just be wary. Not going to be able to fix any bugs for a few more weeks. Dat GuyTalkContribs 18:05, 18 August 2017 (UTC)
Thnaks, have done that. I can confirm a re-upload of the same file has fixed the pixel display size of File:Everybody's Fool (Evanescence single - cover art).jpg, some weird corruption in that file's data - but if I see that again, I know the fix. Ronhjones  (Talk) 19:35, 18 August 2017 (UTC)
Hi DatGuy, I set User:DatBot/NonFreeImageResizer/Run to Run on the 18th - coming back after a couple of days away, I see it did not start Bot, did I do something wrong? Ronhjones  (Talk) 19:49, 21 August 2017 (UTC)
@Ronhjones and Jd22292: Well, considering my computer is probably in the middle of an ocean right now, it's probably had an issue. I'm working on rewriting the Toolforge code to use Pillow. Dat GuyTalkContribs 12:04, 29 August 2017 (UTC)
Thanks for update. Very curious to know how it's in the middle of an ocean... Hope you have success in fixing the bot. Ronhjones  (Talk) 19:41, 29 August 2017 (UTC)
@Ronhjones: I'd prefer not to say on this easily accessible talk page :). Dat GuyTalkContribs 17:27, 31 August 2017 (UTC)
OK :-). Not sure if will help, I'm running the code one file at a time, like a macro, just to cut down the backlog a bit (not a lot - limited bandwidth!) - using Pillow, I needed to add
from PIL import ImageFile
ImageFile.LOAD_TRUNCATED_IMAGES = True
Else I got endless errors in "littleimage.py" of the sort - "IOError: image file is truncated" (https://stackoverflow.com/questions/12984426/python-pil-ioerror-image-file-truncated-with-big-images) Ronhjones  (Talk) 17:52, 2 September 2017 (UTC)
Just to add that my code with Pillow 2.7 is working just fine on GIF files (unlike PIL, which used to corrupt them - which is why Theo's code separates out GIF files). So I am concentrating on all the very old GIF files, some of which have have a reduce tag on them for years. Ronhjones  (Talk) 19:12, 5 September 2017 (UTC)
Maybe. The code could use to be updated and rewritten, but PC is still in the ocean. Thankfully I have an actual laptop now, so replies should be quicker. The issue that makes it unusable on Linux is the process of copying exif metadata, which can be seen at the top of littleimage.py. Dat GuyTalkContribs 12:52, 6 September 2017 (UTC)
I'll take your word on that, I've hardly used Linux. The Windoze pyexiv2 module works just fine for me. I can concentrate on the GIFs anyway - we don't get that many, so an occasional blitz (once I've done the 650 that are tagged) should suffice. Hope you enjoy your new laptop, Ronhjones  (Talk) 20:21, 6 September 2017 (UTC)
  • @Ronhjones: Just an update, this monday I'll probably get to dual-boot my laptop with linux, which should making testing a lot easier. Dat GuyTalkContribs 20:02, 20 September 2017 (UTC)
    • Nice. I'll think I'll stick with Windoze for now. I've actually sorted out the GIFs (Wikipedia:Bots/Requests for approval/RonBot 2) - not every GIF did reduce OK, some issues...
      1. Black image - I needed to test output file size - much smaller than expected, there's something in the structure of about 1% of the GIFs here that Pillow gives a bad result
      2. Chequerboard patterning - Bot runs in Supervised mode, where the edits are checked later, no other way of finding that out, seems to be due to the low numbers of colours in the palette, where there was a graduation of colour in the original image.
      3. Animated! - had to count the number of frames, the Pillow module will only do a single frame.
Thus we still need DatBot6 doing just the files it did before. Note GIFs are now in Category:Wikipedia non-free file size reduction requests (been moved from Category:Wikipedia non-free file size reduction requests for manual processing), with all the other images for reduction, so DatBot6 will need to skip them (as did Theo's code) Ronhjones  (Talk) 20:58, 20 September 2017 (UTC)
@Ronhjones: I'm still trying to build pyexiv2 on toolforge, but would you like me to continue the manual runs? Dat GuyTalkContribs 06:19, 30 September 2017 (UTC)
If you can that would be great. I had to stop tagging files as the category was a bit full, Between myself (in semi-auto mode) and Theo's old bot we are only doing about 150-300 a day, and others are still tagging the odd file, so the category is reducing only slowly. And there is still 120,000 files which will probably need tagging and reducing - probably 6-12 months to do. Ronhjones  (Talk) 16:56, 30 September 2017 (UTC)
@Ronhjones and Ronjones: Since it's already taken nearly 6 hours (6 hours! wow!) and it's still not through the backlog, I've started another instance that should go in reverse alphabetical order. You can move on to the manual ones if you want :). Dat GuyTalkContribs 18:51, 1 October 2017 (UTC)
We are the same person... :-) I've been using my alt account to log my semi-auto reductions using the python code with a "raw_input("Press Enter to continue...")" just before the upload command (and I can view the reduced file in the temp directory before hitting return). I think you have done about 3/4 of the backlog (was about 2000 files), at about 5 files a minute, so an hour or two will complete - then we can start tagging again - only 125,000 files to go (not all in one go!) I'm doing TIFs tonight in PhotoShop - I think that just leaves SVG and PDF in the manual - both rather slow to do.... Ronhjones  (Talk) 19:27, 1 October 2017 (UTC)
I see there is no backlog. :-) If I start tagging again - how many files a day would you be happy processing until you get the bot remotely working? - don't want to overload your PC &/or connection. Ronhjones  (Talk) 21:05, 1 October 2017 (UTC)
@Ronhjones: My PC and connection will be fine for the foreseeable future. Feel free to tag as much as you like :). Also, I know that was your alt account but I wasn't sure which one you were logged into to get the ping. Dat GuyTalkContribs 12:21, 3 October 2017 (UTC)
No problem. I did 1000 last night - it takes a while to look through them, so I'll try to do same (on days I have the time). Only use alt account for the occasional edit when at work - don't like using admin password on other PCs. Current searches are all the new files that have appeared! - I was down to >180625 pixels completed. Ronhjones  (Talk) 19:50, 3 October 2017 (UTC)

Some stroopwafels for you!

 

I know they're Dutch,

but stroopwafels are tasty,

have one with coffee.


Waggie (talk) 16:59, 8 October 2017 (UTC)

14:21, 9 October 2017 (UTC)

15:31, 16 October 2017 (UTC)

Again on the timing between Ronhjones's non-free size tagging and DatBot resizing

I am only starting this discussion to stave off issues other uses might have, not that I have a personal complaint I know @Ronhjones: has a method to tag non-frees > 0.1MP, which is fine, and DatBot operates on this information to resize (again, also generally fine). I know we've discussed that if a user objects to the potential resize, they can change the tag Ronjhones adds to a form that has DatBot will not touch it. The elements are all fine and within policy.

What I do see going to be a problems with what is happening is that the interaction is getting faster. this one took under 5 hrs between the tag and reduction. This is not generally considered enough time for one to react to such changes, and I can see users getting upset. The only buffer on this is that the original images are not removed in a timely manner (at least 7 days checking DatBot's history) but this means if DatBot reacts before the user can change the template, they need to go to admin to fix. Given some attitudes towards non-free presently, this could end up at AN, again. Editors don't like their NFC messed with, I've found. I know there's been very minimal issues to date, I'm just concerned it could get worse.

I know I mentioned the delay between Ronhjones and DatBot before. Since we can coordinate between tagging and DatBot, I am wondering that if Ronhjones includes a date and time parameter in that tagging template that DatBot can read and not take action until at least, say, 24-48hrs has passed. This should be minimum work for either of you if there's agreement on that format, I'd think (I don't know how DatBot works exactly). --MASEM (t) 01:46, 17 October 2017 (UTC)

@Masem: Regarding Again, I don't think there ever was a prequel to this discussion? The AN thread was about the task not starting. Anyways, if Ronhjones agrees I could add a function to make sure that the page hasn't been edited for 24 hours (if you consider that to be a sufficient time) before resizing the file. FYI DatBot runs at 9:00 AM (midnight) UTC every day unless there's a big backlog, which I then manually activate. Dat GuyTalkContribs 11:12, 17 October 2017 (UTC)
@Masem: This has always been the case. Before Datbot6 we had Theo's Little Bot#1, which used the same criteria - All the files in Category:Wikipedia non-free file size reduction requests would be processed on the next bot's run (which as DatBot6, was once daily). What you may not have noticed in the past was that Theo's bot broke down at least 2 years ago and started only doing some files a day until it crashed, so the reductions were not done as was always expected, and there was always a backlog. Since DatGuy and I have changed nothing, then I think you need to raise it at Wikipedia talk:Non-free content and see if you can get a consensus to change the standard action. If that is the case then either DatBot could delay or we could have a time sorted category - something like "Category:Wikipedia non-free file size reduction requests after X days". However I suspect that some editors might feel, that we then have a legal issue in leaving oversized non-free files, when we have identified that they are oversized. Also it is often not possible to decide on the quality of a reduction until it has actually been carried out (otherwise it's just a guess). Finally, an admin is not necessary to fix a reduction - that's why we have the 7 days of showing both old and new images, so that reverts can be done if truly necessary. Only after the 7 days has past, and the orphaned versions are revision deleted, does one need the help of an admin. Ronhjones  (Talk) 18:40, 17 October 2017 (UTC)

Incorrect orphan tagging?

Hi. Just wanted to point you to this change which your bot made marking an image as an orphan even though it has been continually used on a page. There's no need for immediate action, a different bot removed the tag (which is how I noticed it was there in the first place), but thought you could use an example of mistagging. Thanks! Protonk (talk) 15:17, 18 October 2017 (UTC)

@Protonk: I'm not sure you understand the function for the bot. If you'd take a look at Template:Di-orphaned fair use, it's different than Template:Orphaned non-free revisions. My bot only resizes the version that doesn't fall under NFCC, specifically #3. Also, I pretty much created the code for RonBot (with help from Ronhjones), which works hand in hand with DatBot. I couldn't run it since it's an adminbot :). Dat GuyTalkContribs 15:35, 18 October 2017 (UTC)
Hmm. It does seem I've misunderstood the function. Sorry about that. I also didn't know about the (new?) NFU requirement to delete old image revisions. Thanks for the update. Protonk (talk) 15:58, 18 October 2017 (UTC)
@Protonk: "Low- rather than high-resolution/fidelity/bit rate is used." Also, the oldest BRFA I could find about this topic is Wikipedia:Bots/Requests for approval/ImageResizeBot, and the oldest approved one is Wikipedia:Bots/Requests for approval/NeuRobot 2. Dat GuyTalkContribs 16:35, 18 October 2017 (UTC)

New Page Reviewer Newsletter

Hello DatGuy/Archives/2017, thank you for your efforts reviewing new pages!
 

Backlog update:

  • The new page backlog is currently at 12,878 pages. We have worked hard to decrease from over 22,000, but more hard work is needed! Please consider reviewing even just a few pages a day.
  • We have successfully cleared the backlog of pages created by non-confirmed accounts before ACTRIAL. Thank you to everyone who participated in that drive.

Technology update:

  • Primefac has created a script that will assist in requesting revision deletion for copyright violations that are often found in new pages. For more information see User:Primefac/revdel.

General project update:


If you wish to opt-out of future mailings, go here. TonyBallioni (talk) 17:47, 21 October 2017 (UTC)

DatBot NonFreeImageResizer producing horrible image quality

See File:Grean Fictions poster.jpg, where the bot reduced the image area by 38% but reduced the file size by 70%, leaving a horribly artifacted image. Perhaps better jpeg settings could be used? --Paul_012 (talk) 14:30, 20 October 2017 (UTC)

It isn't great, but it isn't *too* horrible that it's unreadable. I'll look into the settings. Dat GuyTalkContribs

Your GA nomination of Dominica at the 2016 Summer Olympics

Hi there, I'm pleased to inform you that I've begun reviewing the article Dominica at the 2016 Summer Olympics you nominated for GA-status according to the criteria.   This process may take up to 7 days. Feel free to contact me with any questions or comments you might have during this period. Message delivered by Legobot, on behalf of MWright96 -- MWright96 (talk) 06:41, 23 October 2017 (UTC)

Your GA nomination of Dominica at the 2016 Summer Olympics

The article Dominica at the 2016 Summer Olympics you nominated as a good article has been placed on hold  . The article is close to meeting the good article criteria, but there are some minor changes or clarifications needing to be addressed. If these are fixed within 7 days, the article will pass; otherwise it may fail. See Talk:Dominica at the 2016 Summer Olympics for things which need to be addressed. Message delivered by Legobot, on behalf of MWright96 -- MWright96 (talk) 07:21, 23 October 2017 (UTC)

18:18, 23 October 2017 (UTC)

A problem with the DatBot NonFreeImageResizer

Hi, I've lately found that the DatBot NonFreeImageResizer makes quite a few screenshots (Mostly from older software without ClearType text) look horrible, and makes the text in those screenshots completely unreadable. See File:ViolaWWW.png and the older versions of File:Microsoft Internet Mail and News screenshot.png File:Windows Write.png File:EComStation.png. Could you perhaps look into this problem?

Thanks in advance!

Matan2001 (talk) 18:33, 24 October 2017 (UTC)

Your GA nomination of Tuvalu at the Olympics

Hi there, I'm pleased to inform you that I've begun reviewing the article Tuvalu at the Olympics you nominated for GA-status according to the criteria.   This process may take up to 7 days. Feel free to contact me with any questions or comments you might have during this period. Message delivered by Legobot, on behalf of MWright96 -- MWright96 (talk) 18:01, 26 October 2017 (UTC)

Your GA nomination of Tuvalu at the Olympics

The article Tuvalu at the Olympics you nominated as a good article has been placed on hold  . The article is close to meeting the good article criteria, but there are some minor changes or clarifications needing to be addressed. If these are fixed within 7 days, the article will pass; otherwise it may fail. See Talk:Tuvalu at the Olympics for things which need to be addressed. Message delivered by Legobot, on behalf of MWright96 -- MWright96 (talk) 18:41, 26 October 2017 (UTC)

Your GA nomination of Dominica at the 2016 Summer Olympics

The article Dominica at the 2016 Summer Olympics you nominated as a good article has passed  ; see Talk:Dominica at the 2016 Summer Olympics for comments about the article. Well done! If the article has not already been on the main page as an "In the news" or "Did you know" item, you can nominate it to appear in Did you know. Message delivered by Legobot, on behalf of MWright96 -- MWright96 (talk) 17:02, 24 October 2017 (UTC)

00:20, 31 October 2017 (UTC)