This is an archive of past discussions with User:DatGuy. Do not edit the contents of this page. If you wish to start a new discussion or revive an old one, please do so on the current talk page.

Why this: https://en.m.wikipedia.org/wiki/File:Jimmy_Savile,_Headstone.jpg

It is not legible anymore.

Also, we EU-ans do not care about US copyright law. The author and the object was in the UK all the time. Please ping me as I do not have your talk page on Watchlist. Zezen (talk) 04:51, 31 July 2019 (UTC)__DTREPLYBUTTONSCONTENT__-->__DTELLIPSISBUTTON__{"threadItem":{"timestamp":"2019-07-31T04:51:00.000Z","author":"Zezen","type":"comment","level":1,"id":"c-Zezen-2019-07-31T04:51:00.000Z-Your_bot_overreducing_UK_images","replies":["c-LABcrabs-2019-08-01T19:39:00.000Z-Zezen-2019-07-31T04:51:00.000Z"]}}-->

I'm having similar issues, but I'm in Canada, and I upload a few non-free files such as the Dance Dance Revolution Extreme game cover; the bot shrunk the already small image, even after I reverted the shrinking. Wikipedia operates in USA, so it uses those laws, but that shouldn't be an issue with the resolution you uploaded at. I'm hoping that the bot owner will provide an opt-out on a page-per-page basis. --LABcrabs (talk) 19:39, 1 August 2019 (UTC)__DTREPLYBUTTONSCONTENT__-->__DTELLIPSISBUTTON__{"threadItem":{"timestamp":"2019-08-01T19:39:00.000Z","author":"LABcrabs","type":"comment","level":2,"id":"c-LABcrabs-2019-08-01T19:39:00.000Z-Zezen-2019-07-31T04:51:00.000Z","replies":[]}}-->

As pretext, there's guidelines for the recommended sizes for images here, the important part is "images should be rescaled as small as possible to still be useful as identified by their rationale, and no larger."

Regarding Zezen, since Wikipedia is a free encyclopedia, it is always preferred to have a free image. However, since this is sometimes impossible, the non-free content policy exists, which outlines how images like the one you're referring to are maintained. I'm not sure why you feel the need to specify the images are from the UK, as Wikipedia operates through policy that isn't country-specific.

@LABcrabs: after you uploaded File:DDR Extreme PS2 JP.png, another bot task tagged [1] the image for reduction per IMAGERES. You reverted [2] DatBot's size reduction, and after DQBot deleted the old revision [3] the process repeated [4]. The reduced image seems fine to me as it isn't losing any needed content, and if you don't mind I'll be reverting it to that version (reply if you do mind), but for future reference I believe you can add {{bots}} to the top of your file page.

Thanks, Dat Guy^Talk_Contribs 20:13, 1 August 2019 (UTC)__DTREPLYBUTTONSCONTENT__-->__DTELLIPSISBUTTON__{"threadItem":{"timestamp":"2019-08-01T20:13:00.000Z","author":"DatGuy","type":"comment","level":1,"id":"c-DatGuy-2019-08-01T20:13:00.000Z-Your_bot_overreducing_UK_images","replies":["c-LABcrabs-2019-08-02T02:11:00.000Z-DatGuy-2019-08-01T20:13:00.000Z"],"displayName":"Dat Guy"}}-->

Thanks for the comment, DatGuy. I typically upload CD covers at 320x320, so I personally prefer a width of 320 for video game covers. Should I add "Bots|deny=DatBot" or "Bots|deny=JJMC89 Bot" as template code, however? I'll use the latter, but if it's supposed to be the former, please let me know. --LABcrabs (talk) 02:11, 2 August 2019 (UTC)__DTREPLYBUTTONSCONTENT__-->__DTELLIPSISBUTTON__{"threadItem":{"timestamp":"2019-08-02T02:11:00.000Z","author":"LABcrabs","type":"comment","level":2,"id":"c-LABcrabs-2019-08-02T02:11:00.000Z-DatGuy-2019-08-01T20:13:00.000Z","replies":["c-DatGuy-2019-08-02T12:22:00.000Z-LABcrabs-2019-08-02T02:11:00.000Z"]}}-->

DatBot only resizes the image after it's tagged with {{Non-free reduce}}, so the latter should do it. Dat Guy^Talk_Contribs 12:22, 2 August 2019 (UTC)__DTREPLYBUTTONSCONTENT__-->__DTELLIPSISBUTTON__{"threadItem":{"timestamp":"2019-08-02T12:22:00.000Z","author":"DatGuy","type":"comment","level":3,"id":"c-DatGuy-2019-08-02T12:22:00.000Z-LABcrabs-2019-08-02T02:11:00.000Z","replies":[],"displayName":"Dat Guy"}}-->

Dear Dat Guy

Thanks for the explanation and pinging.

With this Jimmy Saville the bot messed up this rule you quoted:

images should be rescaled as small as possible to still be useful as identified by their rationale, and no larger

Most of the letters are now illegible while description mentions these words.

Comments? Pls ping again when replying. Zezen (talk) 14:13, 2 August 2019 (UTC)__DTREPLYBUTTONSCONTENT__-->__DTELLIPSISBUTTON__{"threadItem":{"timestamp":"2019-08-02T14:13:00.000Z","author":"Zezen","type":"comment","level":1,"id":"c-Zezen-2019-08-02T14:13:00.000Z-Your_bot_overreducing_UK_images","replies":["c-DatGuy-2019-08-02T14:46:00.000Z-Zezen-2019-08-02T14:13:00.000Z"]}}-->

@Zezen: you can use {{Non-free manual reduce}}. If you believe that it's as small as it can be while keeping the text readible, you can add {{Non-free no reduce}}. Dat Guy^Talk_Contribs 14:46, 2 August 2019 (UTC)__DTREPLYBUTTONSCONTENT__-->__DTELLIPSISBUTTON__{"threadItem":{"timestamp":"2019-08-02T14:46:00.000Z","author":"DatGuy","type":"comment","level":2,"id":"c-DatGuy-2019-08-02T14:46:00.000Z-Zezen-2019-08-02T14:13:00.000Z","replies":[],"displayName":"Dat Guy"}}-->

But it is too late now, I guess? Or will it get magically restored by your bot after I put {{Non-free no reduce}}?

Little bot knowledge here... Zezen (talk) 15:24, 2 August 2019 (UTC)__DTREPLYBUTTONSCONTENT__-->__DTELLIPSISBUTTON__{"threadItem":{"timestamp":"2019-08-02T15:24:00.000Z","author":"Zezen","type":"comment","level":1,"id":"c-Zezen-2019-08-02T15:24:00.000Z-Your_bot_overreducing_UK_images","replies":["c-DatGuy-2019-08-03T17:29:00.000Z-Zezen-2019-08-02T15:24:00.000Z"]}}-->

@Zezen: adding non-free no reduce will not change it. In most cases, you would click the 'revert' button in 'file history.' However, since the old revision has been deleted, you need to ask an admin to do it I believe. By the way see here for how to indent your messages, it makes talk pages much more readable. Dat Guy^Talk_Contribs 17:29, 3 August 2019 (UTC)__DTREPLYBUTTONSCONTENT__-->__DTELLIPSISBUTTON__{"threadItem":{"timestamp":"2019-08-03T17:29:00.000Z","author":"DatGuy","type":"comment","level":2,"id":"c-DatGuy-2019-08-03T17:29:00.000Z-Zezen-2019-08-02T15:24:00.000Z","replies":[],"displayName":"Dat Guy"}}-->

Bots Newsletter, August 2019

Greetings! Here is the 7th issue of the Bots Newsletter, a lot happened since last year's newsletter! You can subscribe/unsubscribe from future newsletters by adding/removing your name from this list. Highlights for this newsletter include: ARBCOM Nothing of note happened. Just like we like it. BAG Several (1 + 12 = 13) users have been retired/resigned from the BAG due to inactivity, per our new activity requirements (discussion). BAG members are expected to be active on Wikipedia to have their finger on the pulse of the community. After two years without any bot-related activity (such as posting on bot-related pages, posting on a bot's talk page, or operating a bot), BAG members will be retired from BAG following a one-week notice. Retired members can re-apply for BAG membership as normal if they wish to rejoin the BAG. Two BAG members retired Madman (talk · contribs) retired. BU Rob13 (talk · contribs) vanished and retired. Three new BAG members have been voted in, welcome to the BAG! Primefac (talk · contribs) joined on 2018-12-12 (RfBAG). Primefac operates PrimeBOT (talk · contribs) which does a plethora of tasks. TheSandDoctor (talk · contribs) joined on 2019-01-21 (RfBAG). TheSandDoctor operates several bots including DeprecatedFixerBot (talk · contribs). Enterprisey (talk · contribs) joined on 2019-08-07 (RfBAG). Enterprisey operates EnterpriseyBot (talk · contribs), which does a plethora of tasks, RemindMeBot (talk · contribs) which posts reminders, and codes several scripts. We thank former members for their service and wish Madman a happy retirement. We note that Madman and BU Rob13 were not inactive and could resume their BAG positions if they so wished, should their retirements happens to be temporary. BOTDICT Two new entries feature in the bots dictionary Editor-hostile wikitext – describes wikitext structuring that is editor hostile, even if it renders correctly Spectrum of usefulness – describes how tasks are deemed useful or not BOTPOL Activity requirements: BAG members now have an activity requirement. The requirements are very light, one only needs to be involved in a bot-related area at some point within the last two years. For purpose of meeting these requirements, discussing a bot-related matter anywhere on Wikipedia counts, as does operating a bot (RFC). Copyvio flag: Bot accounts may be additionally marked by a bureaucrat upon BAG request as being in the "copyviobot" user group on Wikipedia. This flag allows using the API to add metadata to edits for use in the New pages feed (discussion). There is currently 1 bot using this functionality. Mass creation: The restriction on mass-creation (semi-automated or automated) was extended from articles, to all content-pages. There are subtleties, but content here broadly means whatever a reader could land on when browsing the mainspace in normal circumstances (e.g. Mainspace, Books, most Categories, Portals, ...). There is also a warning that WP:MEATBOT still applies in other areas (e.g. Redirects, Wikipedia namespace, Help, maintenance categories, ...) not explicitely covered by WP:MASSCREATION. BOTREQs and BRFAs As of writing, we have... 20 active BOTREQs, please help if you can! 14 open BRFAs and 1 BRFA in need of BAG attention (see live status). In 2018, 96 bot task were approved. An AWB search shows approximately 29 were withdrawn/expired, and 6 were denied. Since the start of 2019, 97 bot task were approved. Logs show 15 were withdrawn/expired, and 15 were denied. 10 inactive bots have been deflagged (see discussion). 5 other bots have been deflagged per operator requests or similar (see discussion). New things All bot-related discussion pages now have a centralized and searchable archive box (see discussion). Discussions are searchable per noticeboard, or globally. {{Bot}} now supports |status=expired (see discussion). This led to the deletion of Category:Indefinitely blocked Wikipedia bots as useless (see discussion). WP:BOTREQ now mentions WP:SCRIPTREQ and WP:AWBTASKS as alternatives to bot requests. The bot creation guide now mentions bot flags, and two new languages Awk and MATLAB. Other minor tweaks have been made. AAlertBot has received major code updates. In particular, WP:AALERTS will now report splits, mergers, and AFC submissions. Citation bot has received several updates (User talk:Citation bot/Archive 10/11/12/13/14/15/16/17). In particular, the bot stopped the automated removal of |publisher= from {{cite journal}}, and stopped the automated addition of CiteSeerX links, and now uses OAuth to authenticate those who make requests of the bot. Other discussions These are some of the discussions that happened / are still happening since the last Bots Newsletter. Many are stale, but some are still active. Wikipedia:Bots/Noticeboard/Archive 12#Adminbots requests page Wikipedia:Bots/Noticeboard/Archive 12#Double-redirect tagging (2019) Wikipedia:Bots/Noticeboard/Archive 12#Long and Winding Road to Parsoid Wikipedia:Bots/Noticeboard/Archive 13#Bot-like user scripts Wikipedia:Bots/Noticeboard/Archive 13#WP:URLREQ Wikipedia:Bots/Noticeboard/Archive 13#Wikipedia:Bots/Status Wikipedia talk:Bot Approvals Group#Minimum edits Wikipedia talk:Bot policy#Minor update to WP:BOTISSUE Wikipedia talk:Bot policy#Semi-automated Portal creation Wikipedia talk:Bot policy#Clarification on "Bots operated by multiple users" Wikipedia talk:Bot policy#Bots triggered by multiple users Wikipedia talk:Bots#How to use Special:ApiFeatureUsage See also the latest discussions at the bot noticeboard. Thank you! edited by: Headbomb 17:24, 7 August 2019 (UTC)__DTREPLYBUTTONSCONTENT__-->__DTELLIPSISBUTTON__{"threadItem":{"timestamp":"2019-08-07T17:24:00.000Z","author":"Headbomb","type":"comment","level":1,"id":"c-Headbomb-2019-08-07T17:24:00.000Z-Bots_Newsletter,_August_2019","replies":[]}}--> (You can subscribe or unsubscribe from future newsletters by adding or removing your name from this list.)

Do you think it could send out warnings before reporting? While some AFs display interface warnings, not all do, and often reports have a red link for a talk page. -- Lofty abyss 10:15, 9 August 2019 (UTC)__DTREPLYBUTTONSCONTENT__-->__DTELLIPSISBUTTON__{"threadItem":{"timestamp":"2019-08-09T10:15:00.000Z","author":"Lofty abyss","type":"comment","level":1,"id":"c-Lofty_abyss-2019-08-09T10:15:00.000Z-Bot_warnings","replies":["c-DatGuy-2019-08-10T12:46:00.000Z-Lofty_abyss-2019-08-09T10:15:00.000Z"],"displayName":"Lofty"}}-->

@Lofty abyss: which filters are you referring to more specifically? If there's consensus then I'll need to do another BRFA since it wasn't in the scope of the original one. Dat Guy^Talk_Contribs 12:46, 10 August 2019 (UTC)__DTREPLYBUTTONSCONTENT__-->__DTELLIPSISBUTTON__{"threadItem":{"timestamp":"2019-08-10T12:46:00.000Z","author":"DatGuy","type":"comment","level":2,"id":"c-DatGuy-2019-08-10T12:46:00.000Z-Lofty_abyss-2019-08-09T10:15:00.000Z","replies":["c-Lofty_abyss-2019-08-10T13:11:00.000Z-DatGuy-2019-08-10T12:46:00.000Z"],"displayName":"Dat Guy"}}-->

All kinds. Wouldn't it be better for a bot, like ClueBot, to warn before reporting? -- Lofty abyss 13:11, 10 August 2019 (UTC)__DTREPLYBUTTONSCONTENT__-->__DTELLIPSISBUTTON__{"threadItem":{"timestamp":"2019-08-10T13:11:00.000Z","author":"Lofty abyss","type":"comment","level":3,"id":"c-Lofty_abyss-2019-08-10T13:11:00.000Z-DatGuy-2019-08-10T12:46:00.000Z","replies":["c-DatGuy-2019-08-15T09:03:00.000Z-Lofty_abyss-2019-08-10T13:11:00.000Z"],"displayName":"Lofty"}}-->

I don't believe there's anything in ClueBot's implementation regarding abuse filters. If someone else would want to make a dedicated bot for it, they can feel free. Dat Guy^Talk_Contribs 09:03, 15 August 2019 (UTC)__DTREPLYBUTTONSCONTENT__-->__DTELLIPSISBUTTON__{"threadItem":{"timestamp":"2019-08-15T09:03:00.000Z","author":"DatGuy","type":"comment","level":4,"id":"c-DatGuy-2019-08-15T09:03:00.000Z-Lofty_abyss-2019-08-10T13:11:00.000Z","replies":[],"displayName":"Dat Guy"}}-->

DatBot is picking up false positives when users are entering "album". I think it's reading it as "bum". Can you update the filter settings, please? Cheers, caknuck _° needs to be running more often 06:15, 14 August 2019 (UTC)__DTREPLYBUTTONSCONTENT__-->__DTELLIPSISBUTTON__{"threadItem":{"timestamp":"2019-08-14T06:15:00.000Z","author":"Caknuck","type":"comment","level":1,"id":"c-Caknuck-2019-08-14T06:15:00.000Z-\"album\"","replies":["c-DatGuy-2019-08-14T19:11:00.000Z-Caknuck-2019-08-14T06:15:00.000Z"]}}-->

@Caknuck: do you know the filter ID/username of reportee? Dat Guy^Talk_Contribs 19:11, 14 August 2019 (UTC)__DTREPLYBUTTONSCONTENT__-->__DTELLIPSISBUTTON__{"threadItem":{"timestamp":"2019-08-14T19:11:00.000Z","author":"DatGuy","type":"comment","level":2,"id":"c-DatGuy-2019-08-14T19:11:00.000Z-Caknuck-2019-08-14T06:15:00.000Z","replies":["c-Caknuck-2019-08-15T06:01:00.000Z-DatGuy-2019-08-14T19:11:00.000Z"],"displayName":"Dat Guy"}}-->

ProducersUnited (talk · contribs · logs), filter 260. caknuck _° needs to be running more often 06:01, 15 August 2019 (UTC)__DTREPLYBUTTONSCONTENT__-->__DTELLIPSISBUTTON__{"threadItem":{"timestamp":"2019-08-15T06:01:00.000Z","author":"Caknuck","type":"comment","level":3,"id":"c-Caknuck-2019-08-15T06:01:00.000Z-DatGuy-2019-08-14T19:11:00.000Z","replies":["c-DatGuy-2019-08-15T09:01:00.000Z-Caknuck-2019-08-15T06:01:00.000Z"]}}-->

@Caknuck: The filter was triggered because of the addition of "nigga" in reference to Chris Browns' Side Nigga. I think this false positive is acceptable, but you can report it here. Dat Guy^Talk_Contribs 09:01, 15 August 2019 (UTC)__DTREPLYBUTTONSCONTENT__-->__DTELLIPSISBUTTON__{"threadItem":{"timestamp":"2019-08-15T09:01:00.000Z","author":"DatGuy","type":"comment","level":4,"id":"c-DatGuy-2019-08-15T09:01:00.000Z-Caknuck-2019-08-15T06:01:00.000Z","replies":["c-Caknuck-2019-08-15T15:20:00.000Z-DatGuy-2019-08-15T09:01:00.000Z"],"displayName":"Dat Guy"}}-->

My bad. It was 98.204.92.72 (talk · contribs · WHOIS) and filter 384. Sorry! caknuck _° needs to be running more often 15:20, 15 August 2019 (UTC)__DTREPLYBUTTONSCONTENT__-->__DTELLIPSISBUTTON__{"threadItem":{"timestamp":"2019-08-15T15:20:00.000Z","author":"Caknuck","type":"comment","level":5,"id":"c-Caknuck-2019-08-15T15:20:00.000Z-DatGuy-2019-08-15T09:01:00.000Z","replies":[]}}-->

Precious

Two years!

--Gerda Arendt (talk) 10:03, 20 August 2019 (UTC)__DTREPLYBUTTONSCONTENT__-->__DTELLIPSISBUTTON__{"threadItem":{"timestamp":"2019-08-20T10:03:00.000Z","author":"Gerda Arendt","type":"comment","level":1,"id":"c-Gerda_Arendt-2019-08-20T10:03:00.000Z-Precious_anniversary","replies":[]}}-->

Precious

Two years!

--Gerda Arendt (talk) 10:03, 20 August 2019 (UTC)__DTREPLYBUTTONSCONTENT__-->__DTELLIPSISBUTTON__{"threadItem":{"timestamp":"2019-08-20T10:03:00.000Z","author":"Gerda Arendt","type":"comment","level":1,"id":"c-Gerda_Arendt-2019-08-20T10:03:00.000Z-Precious_anniversary_2","replies":[]}}-->

Why is it that every time I click on a Datbot vandalism report in my watchlist, it is always a false positive? The IPs in question have apparently never edited. Kudpung กุดผึ้ง (talk) 04:22, 25 August 2019 (UTC)__DTREPLYBUTTONSCONTENT__-->__DTELLIPSISBUTTON__{"threadItem":{"timestamp":"2019-08-25T04:22:00.000Z","author":"Kudpung","type":"comment","level":1,"id":"c-Kudpung-2019-08-25T04:22:00.000Z-False_positives?","replies":["c-DatGuy-2019-08-28T08:28:00.000Z-Kudpung-2019-08-25T04:22:00.000Z"],"displayName":"Kudpung \u0e01\u0e38\u0e14\u0e1c\u0e36\u0e49\u0e07"}}-->

Do you have the user in question? If they have no edits they're most likely SPA of known vandals. You can check in 'filter log' under 'user contributions'. Dat Guy^Talk_Contribs 08:28, 28 August 2019 (UTC)__DTREPLYBUTTONSCONTENT__-->__DTELLIPSISBUTTON__{"threadItem":{"timestamp":"2019-08-28T08:28:00.000Z","author":"DatGuy","type":"comment","level":2,"id":"c-DatGuy-2019-08-28T08:28:00.000Z-Kudpung-2019-08-25T04:22:00.000Z","replies":[],"displayName":"Dat Guy"}}-->