User talk:Krinkle

From Wikimedia Commons, the free media repository
Jump to navigation Jump to search

I reply to messages left on my talk, on my talk page.
If I left a message on your talk page, I will reply there (unless you specify otherwise).


Addition of hewiki to Commons:Auto-protected files[edit]

Hey mate, Face-smile.svg
After consulting with the rest of the community here on hewiki, we'd like to add /wikipedia/he/ to your automatic protection bot.
We promise to be good hosts and hopefully cause no problems. Face-tongue.svg
Hoping to receive your blessings,
Bharel (talk) 20:50, 2 January 2017 (UTC)
p.s. I like your name. Krinkle. It's catchy.[reply]

@Bharel: Okay! I've added it (code change, gallery). Is there a "tomorrow" page as well? Adding the "tomorrow" page means images are protected ahead of time. That way image are safe even if the bot is delayed after midnight. --Krinkle 05:49, 3 January 2017 (UTC)[reply]
Yes there is indeed. This is the page name - "ויקיפדיה:עמוד ראשי/מחר". Thank you very much! Bharel (talk) 05:58, 3 January 2017 (UTC)[reply]
@Bharel: Done! Krinkle 00:02, 4 January 2017 (UTC)[reply]

OCR buttons[edit]

Hi there,
I'm trying to integrate OCR-buttons into the Proofread extension on frrwiki. Meanwhile I imported the necessary OCR.js, Gadget-OCR.js and Gadget-PR-ocr.js from dewiki, but it doesn't work yet. The problem might be, that on frrwiki there is no separate Wikisource project, but frr-Wikisource runs within frr-Wikipedia in special namespaces. And Common.js might have to be prepared for that gadget. I'd be glad, if you could find the time to get this running. Thanks in advance!
--Murma174 (talk) 10:01, 25 March 2017 (UTC)[reply]

@Murma174: Hi. Sorry, but I'm not familiar enough with the Wikisource OCR gadget to know why it doesn't work. It seems the original author (s:de:User:Xarax) has been inactive since 2009. Are you certain that it works on dewiki? Perhaps ask around the discussion board at s:de:Wikisource:Skriptorium? –Krinkle 22:13, 28 March 2017 (UTC)[reply]
Yes, I noticed, that Xarax isn't active anymore. Thanks for your reply anyway, and the link! I'll try it there. --Murma174 (talk) 22:35, 28 March 2017 (UTC)[reply]


Please unprotect this file. I have to change the license and set the OTRS-permission. --sasha (krassotkin) 10:30, 29 June 2017 (UTC)[reply]

Hello Krassotkin, this file was never protected!? -- User: Perhelion 12:58, 29 June 2017 (UTC)[reply]
  • Oh yes, I mean in this case the file can't be unprotected!? -- User: Perhelion 20:22, 29 June 2017 (UTC)[reply]

File:The Devil bargains with God over Job's faith in Duomo (San Gimignano).jpg[edit]

Commons:Auto-protected files/wikipedia/fr

Thanks to modify the author : Category:Bartolo di Fredi instead Category:Lippo Memmi.

--Doalex (talk) 17:28, 9 August 2017 (UTC)[reply]

✓ Done --Doalex 09:30, 10 August 2017

Urgent request[edit]

Hello, You removed jquery.mwExtension module in 3863dd231f2f. It breaks a number of widely used scipts such as COM:VFC and by default enabled scripts such as global replace (See Commons:AN#Commons_delinker_not_working). The aforementioned scripts are used hundred of times daily. See also Commons:Village_pump#FulfillEditRequest.js_doesn.27t_work. Anything you can do to fix it? :) Thanks in advice. --Steinsplitter (talk) 13:08, 25 August 2017 (UTC)[reply]

I crated phab:T174164 for tracking. Best :) --Steinsplitter (talk) 13:24, 25 August 2017 (UTC)[reply]
✓ Done --Krinkle 20:48, 25 August 2017 (UTC)[reply]

User talk:Polarlys/Archiv1[edit]

When you edited User talk:Polarlys/Archiv1 to fix the self-closing span tags, you didn't actually remove the self closing bit. The "/>" shuold be ">". Just wondering if you could fix it? -- WOSlinker (talk) 08:47, 9 September 2017 (UTC)[reply]

✓ Done. --Krinkle 18:31, 19 September 2017 (UTC)[reply]


Dag Krinkle, I just noticed you on the and I'm hoping you might be able to help. I was one of the co-founders of and the first sysop, but then took an extended break from wiki (stretching years), but I have now returned to Unfortunately, there's not a lot of activity on, and I'm the only one keeping watch over it. I'm wondering, if I can't get admin rights through, whether anyone else might be able to help me. bedankt, Pippu d'Angelo (talk) 03:59, 17 October 2017 (UTC)[reply]

@Pippu d'Angelo: Hi. I help maintain issues with JavaScript and CSS on all wikis via my access from m:Interface editors. I don't know much about specifically. If you need help from administrator issues, perhaps you can ask the help of m:Global sysops or stewards. --Krinkle 21:34, 23 October 2017 (UTC)[reply]
Thanks Krinkle, all good, I ended up making contact with the correct people on - all fixed, cheers. Pippu d'Angelo (talk) 21:58, 23 October 2017 (UTC)[reply]

Auto-protection of File:Kingdom of Hungary against Moldovans flag in battle.jpg[edit]


I am trying to edit File:Kingdom of Hungary against Moldovans flag in battle.jpg to add more information, but for some reason the KrinkleBot has marked it for auto-protection.

Can you please help?

Thanks --Codrin.B (talk) 22:00, 15 December 2017 (UTC)[reply]


Hello Krinkle, I'm wondering about this template name. Is it still needed or can we replace the 32 inclusions? -- User: Perhelion 16:53, 30 January 2018 (UTC)[reply]

@Perhelion: I think the template should be kept because Beta Wikiversity still exists and users can still transfer new files. So unless the "CommonsHelper" tool has been improved to map "beta" to "en", we need to keep the alias on our side. --Krinkle 19:11, 30 January 2018 (UTC)[reply]

TemplateParam.php for commonswiki[edit]

This has been enabled for commonswiki. See TemplateParam.php. --Bamyers99 (talk) 17:06, 27 April 2018 (UTC)[reply]

@Bamyers99 Thanks, this will be very useful! --Krinkle 18:50, 27 April 2018 (UTC)[reply]

Re: "it seems to not work for Template:Talkarchive"

The program only scans for template usage in Article (Main) namespace and File namespace. --Bamyers99 (talk) 15:36, 1 June 2018 (UTC)[reply]
@Bamyers99 Yeah, I realised that. And the program explains it on the page, so that is good. --Krinkle 15:42, 1 June 2018 (UTC)[reply]

Krinkle bot errors?[edit]

Greetings, Krinkle. It seems that over the last couple of days, your bot has not performed its usual function of adding cascade-protected files to Commons:Auto-protected files/wikipedia/en. I'd appreciate your help in sorting it out; the automatic protection of main-page images is invaluable to the main page. The files in question are this one, which was transcluded here, and this one, transcluded here. Also pinging @Legoktm and Steinsplitter: . Regards, Vanamonde93 (talk) 11:39, 9 June 2018 (UTC)[reply]

Fixed. Grid engine job was stucking. --Steinsplitter (talk) 12:15, 9 June 2018 (UTC)[reply]
Wonderful, thank you. I will let you know here if there are further problems. Vanamonde93 (talk) 13:04, 9 June 2018 (UTC)[reply]
@Steinsplitter: Thanks! May I ask, how did you know? And how did you resolve it? --Krinkle 19:08, 9 June 2018 (UTC)[reply]
I killed the job (and the i run it once by hand to get it updating immediately, cron is ok). I saw this issue on other tools as well (Delinker job gets stuck as well sometimes). --Steinsplitter (talk) 19:10, 9 June 2018 (UTC)[reply]


It seems the bot stopped updating MediaWiki:Gadget-markAdmins-data.js again. Could you have a look at this? The issue with missing rights to edit the page should be solved soon, as I already made a request on COM:BN. --Didym (talk) 20:52, 11 September 2018 (UTC)[reply]

Your erroneous dating of photos[edit]

In this edit and this edit you added dates for two photos that cannot be correct, because the subject died years before the date you inserted. If you had checked his article you would have seen this, and if you had looked at the edit history of the file description pages you would have seen that I had already removed erroneous dates. On what basis did you add these dates? I notice they were different from the dates I removed. And can you please now check that you haven't introduced wrong dates for other images by the same procedure? Thank you for your clean-up efforts but some sanity checking and verification is surely needed before doing something like adding a date to a photo that doesn't already have one. Beorhtwulf (talk) 23:56, 3 December 2018 (UTC)[reply]

@Beorhtwulf Thanks for noticing. The date isn't random. It's based on the Flickr page where it says the photo was taken on that date (it is not something basic like the upload date). The Flickr page contains a discussion about this, and the Commons file page also has an edit with the same mistake many years ago (which you also reverted back then). If you have looked into every link and connected bit of information, you would have known why I made the edit I did. But I think we can agree that it doesn't make sense to do so for every change we make. Instead, we should learn from our mistakes and leave behind clues for our future selves. I have done so. --Krinkle 20:56, 8 December 2018 (UTC)[reply]


Hi @Krinkle: ,

Thanks for your modification in {{Sisterprojects}}. Could you also do the other modifications asked in its Talk page? Thanks! Thomas Linard (talk) 10:52, 9 December 2018 (UTC)[reply]

Gadget-Numeral converter[edit]

Hello Krinkle, greetings from Assamese wikipedia. Our community is interested in installing a Numeral converter gadget that you have developed and maintained Hindi (hi:मीडियाविकि:Gadget-Numeral_converter.js) as well as many other Indic Wikis. So I am reaching out to you to help us tweak the gadget to handle Assamese numerals. We would also need your help to install it in Assamese Wikipedia as we don't have any local Interface editor. Could you please help us in this regard? Please let me know if you need any more information from our side. --SlowPhoton (talk) 14:31, 12 January 2019 (UTC)[reply]

KrinkleBot outage[edit]


The bot appears to have stopped editing.

Thanks in advance for your attention. —David Levy 00:26, 19 February 2019 (UTC)[reply]

@David Levy Thanks. It's back up now. I did some maintenance last night and forgot to re-enable the scheduler. --Krinkle 04:25, 19 February 2019 (UTC)[reply]

KrinkleBot outage March 15, 2019[edit]

It has not run in about 18 hours. Commons:Auto-protected files/wikipedia/en needs updating. Thank you. Maile66 (talk) 22:41, 15 March 2019 (UTC)[reply]

@Maile66: Looks like the automated way to run the bot every 15 minutes in Toolforge got stuck. Should be all good now. Thanks for the heads up! --Krinkle 23:54, 15 March 2019 (UTC)[reply]
Hi there -- is the bot working properly now? I tried to request a protection about 15 mins ago but no luck as yet. ETA Another editor requested a different file several hours ago, which doesn't seem to be picking up, so I think there might be a problem. Espresso Addict (talk) 03:37, 16 March 2019 (UTC)[reply]
It's not working. Maile66 (talk) 13:20, 16 March 2019 (UTC)[reply]
@Maile66: It's back up now. The scheduler got stuck with an unknown error. If this happens again, I'll have to look into what's going on there. Thanks! --Krinkle 16:35, 16 March 2019 (UTC)[reply]

KrinkleBot outage April 4, 2019[edit]

It seems to have fallen down on the job. File:2019 State of the Union Guests (40029398563) (cropped).jpg should be on the main page in about half an hour. It's been in the lead queue at DYK for about 2-1/2 hours waiting to be protected. Thanks in advance. Maile66 (talk) 23:31, 4 April 2019 (UTC)[reply]

@Maile66: Looking at global usage it does not appear used on either of "Main Page" nor "Wikipedia:Main Page/Tomorrow". Those are the pages that KrinkleBot monitors and synchronises. I've checked the Toolforge scheduler, and it appears to be running without issue :). --Krinkle 23:42, 4 April 2019 (UTC)[reply]
DYK Queue/6 due on the main page in 15 minutes. I protected it at en.Wikipedia. Am I missing something? Maile66 (talk) 23:45, 4 April 2019 (UTC)[reply]
@Maile66: I am not familiar with the internals of DYK and Main Page templates on English Wikipedia. The bot monitors "Main Page" and "Wikipedia:Main Page/Tomorrow". Perhaps other editors working on Main Page or DYK know more about how this normally works. --Krinkle 23:51, 4 April 2019 (UTC)[reply]
OK. We got it straightened out, and everything is fine now. Maile66 (talk) 01:33, 5 April 2019 (UTC)[reply]
To elaborate, an administrator performed a requested edit that removed (accidentally, I presume) the DYK queue's transclusion from Wikipedia:Main Page/Tomorrow. Hopefully, this notice will prevent similar mishaps in the future.
Apologies for the false alarm, and thanks again for keeping the bot chugging along. —David Levy 03:09, 5 April 2019 (UTC)[reply]
@David Levy: No problem, and thanks for helping out. I wonder if we could improve on this, perhaps by letting the bot monitor an additional page? For the current config, see here. It already monitors lots of pages on various wikis. Adding another one would be no trouble at all! --Krinkle 15:39, 5 April 2019 (UTC)[reply]

Commons:Auto-protected files/wikipedia/zh[edit]

Please add zh:Wikipedia:首页/全部 to sourcepages. The image used in 你知道嗎? (Did you know) section is randomly picked from a set of images. So the bot edits this page many times in a day. Wikipedia:首页/全部 includes all images. Add it to solve this problem. --Xiplus (talk) 23:39, 28 April 2019 (UTC)[reply]

@Xiplus. Thanks, the change has been committed and deployed. --Krinkle 16:47, 11 May 2019 (UTC)[reply]


Hi, bevor ich es vergesse: danke für de:Wikipedia:Technik/Skin/Gadgets/. Ich habe gesehen das du deutsch sprichst. Deshalb zur Information ein Link nach de:Wikipedia Diskussion:Kurier#Bildbeschreibung. Viele Grüße, Summer ... hier! (talk) 20:48, 11 May 2019 (UTC)[reply]

@Summer You're welcome. Das Bildbeschreibung Problem hatte ich mir auch schon bemerkt (T223007). Es wird jetzt untersucht bei T222935. --Krinkle 15:25, 12 May 2019 (UTC)[reply]
Wenn man in dem systemweiten javascript 'mw.loader.load( "ext.gadget.CommonsDirekt" );' einträgt, wird es vermutlich kein Problem mehr geben. :-) --Summer ... hier! (talk) 16:12, 12 May 2019 (UTC)[reply]

help ~[edit]

Good morning Krinkle ~ I found your name here File:Kristen-Bell-HD-Picture.jpg, if you have the time ~ I have uploaded some of my own work ~ which I know how to do ~ but I have several drafts that I am working on and I wanted to upload trademarks from the companies I am working on ~ I have been trying to learn from other articles, but I am not experienced enough and don't even know where to start ~ I am a firm believer in copyrighted work as I am a member of ~ {under centm} ~ there is no rush but here is my Wikipedia page Mitchellhobbs I will add your page to my watch list ~~ thanks again Mitchellhobbs (talk) 14:20, 2 June 2019 (UTC)[reply]

@Mitchellhobbs: Hi! Glad to hear you enjoy photography and care about copyright. What exactly is it you'd like help with? --Krinkle 14:51, 2 June 2019 (UTC)[reply]
Thanks Kringle ~ Southwire is the first one that I would like to work on logo ~ southwire ~ if I am barking up the wrong tree I don't mean to If I learn the proper way to do it ~ I think I might be able to continue in a proper path ~ like I said I am inexperienced in the trade marks ~ Mitchellhobbs (talk) 15:03, 2 June 2019 (UTC)[reply]
@Mitchellhobbs: Thanks for helping write articles. Before you upload images or graphics that other people have made, familiarise yourself with the guide at Commons:Copyright. It is very likely not allowed to upload those images for Wikipedia because we require all material to be "freely usable". This usually means the material has to be in the public domain, or the author has to agree to make it available under a "free license". A free license usually means that you allow other people to copy or remix the material without copyright-related limitations. A free license may impose some usage restrictions such as attributing the author's name, and sometimes to require any remixed works to be under the same free license. When uploading your own work, you can make that choice. When uploading the work of other people, this requires their permission because they own the copyright. --Krinkle 15:20, 2 June 2019 (UTC)[reply]


File:Ali eisami.jpg apparently appears only as a Wikipedia file, not on Commons. It was probably manually protected at Wikipedia. I'm not sure. When the DYKUpdate bot showed an error that the image was not protected, I listed it at Wikipedia:Main Page/Commons media protection. The appearance on the Main Page was in a DYK hook on May 5. This file still shows here on Krinklebot as protected. Perhaps it's time to remove it? Maile66 (talk) 00:03, 8 July 2019 (UTC)[reply]

@Maile66: Hi, the bot I operate for English Wikipedia automatically protects the files that editors and administrators of English Wikipedia claim through internal references from the templates on w:Wikipedia:Main_Page/Tomorrow. This is not something I or the bot decide on. In this case, it looks like the protection for "File:Ali_eisami.jpg" is coming from w:Wikipedia:Main Page/Commons_media_protection. If a file is wrongly protected, please ask on the relevant talk pages there. Sorry about the confusion! --Krinkle 02:20, 8 July 2019 (UTC)[reply]
Got it. Thanks. 02:29, 8 July 2019 (UTC)

Database schema[edit]

MediaWiki 1.28.0 database schema.svg

Hi! Is there a more latest database schema to provide as svg file on Commons? Kind regards, Doc Taxon (talk) 07:09, 16 July 2019 (UTC)[reply]

@Doc Taxon Not yet. I've documented my workflow at mw:Manual:Database_layout/diagram instructions and am currently looking for a fellow volunteer to help me maintain them. Perhaps you're interested? --Krinkle 12:14, 16 July 2019 (UTC)[reply]
Thanks for the invitation. I am not so very familiar with producing SVG, but I read your workflow and think to learn it by doing. Let's try ... Doc Taxon (talk) 07:04, 17 July 2019 (UTC)[reply]
Cool. Feel free to e-mail me or ping on Freenode IRC for more direct communication if you run into trouble or want help. --Krinkle 19:37, 17 July 2019 (UTC)[reply]
See mw:Topic:Vf90jqxbapc69dlh. --Krinkle 01:21, 21 January 2020 (UTC)[reply]

Welcomeip -> Welcomeanon[edit]

Even nieuwsgierig, maar is dat ter voorbereiding van de verandering van hoe de MediaWiki-software straks met ongeregistreerde gebruikers omgaat? --Donald Trung 『徵國單』 (No Fake News 💬) (WikiProject Numismatics 💴) (Articles 📚) 06:54, 31 August 2019 (UTC)[reply]

Changing translations[edit]

Please clean up translated pages after changing translatable pages. After your recent changes to Template:Welcome, translated pages are full of pink parts (even e.g. the German one you indicated on your user page to speak), while some changes need little to no language knowledge to carry out in translations (or even need not to be marked as modified to start with, see the punctuation change). These lead to duplication (when you’ve split translation units, the text remained in the one retaining the unit number in translations), bad layout and extra work for translators. (By the way, I don’t think a such widespread template should be changed that substantially before prior discussion to start with.) —Tacsipacsi (talk) 11:15, 31 August 2019 (UTC)[reply]

@Tacsipacsi: Hi, thanks for caring. Sorry if I skipped a necessary technical step in editing this template. I pay attention to edit notices and documentation pages and have been around for a while here, but can't find how this would've been known to me, or how to avoid it.
As I understand it, these markings are only visible within the template system, not outside of it on an actual talk page. It indicates to potential contributors that there have been changes in the English version that they can apply if they wish. That seems useful.
What do you mean by "cleaning up"? Do you want the translations to not be marked as fuzzy? Or translate to dozens of languages I don't speak well?
Regarding splitting and duplication, I'm familiar with how the Translate extension works and took care to avoid such issues. (E.g. moved the existing translation unit, not copying the text only). Did I miss one? --Krinkle 11:35, 31 August 2019 (UTC)[reply]
The pink background is only visible on pages using the Translate extension on their own (in this particular case, it’s practically only the template subpages, but templates used on translatable Commons page show it also on the pages they’re embedded in). This is because the CSS with the color is only loaded there, but the HTML markup is present everywhere. Look at the version of the German translation I linked above and imagine there’s nothing pink there: the title of the top right box is still in separate row—this is how it looked like on user talk pages. The last bullet point in that box has completely broken layout because of the invalid wiki code it has. These two could have been fixed if you followed the rule that’s not documented anywhere and used spaces after translation unit identifier instead of newline for inline translation units (i.e. the ones which don’t stand on their own line in the expanded wiki text, but have something, like the image or the bullet point). (Yes, Translate is severely under-documented, there are many good practices, tips and workarounds that appear only in random talk archives.) However, what is to be seen in the top left box is not so easy to fix: the last sentences of the first paragraph are repeated once more, but this time in English. If you really want to split it, maybe the best solution would have been to first split the units where needed without any text changes, split the translated versions as well, and only then modify the text. But why is it worth splitting? Why is it worth having an outdated and a missing translation instead of just an outdated one? Why is it worth having translations do two edits when making the page’s translation up-to-date instead of one?
By cleanup I mean changes that make the text as readable as possible without actually speaking the language: splitting translated units where the English was split, removing content that was removed (like the bullet list items), fixing markup (e.g. adding/removing bullet points), and at all, confirming that the translations look acceptable (you can click on translations’ links on a user talk page to see the template in action there, it works without reloading the page). —Tacsipacsi (talk) 22:05, 31 August 2019 (UTC)[reply]
@Tacsipacsi: I looked at the Dutch and German translations, and they looked acceptable to me. I agree the bullet point missing is not great, and as a former graphic designer it does bother me. But, I do not think many people would notice, and it certainly does not compromise the ability to understand the content while we wait for updated translations. I'll apply some of your suggestions. Thanks for keeping up the standard of quality! --Krinkle 17:33, 2 September 2019 (UTC)[reply]

Is the bot down?[edit]

It seems to have not run for several hours. Maile66 (talk) 23:15, 7 September 2019 (UTC)[reply]

@Maile66: Looks like it got stuck again in the Toolforge scheduler system. I've force quit it and it should now be back on schedule. Thanks for letting me know. --Krinkle 02:01, 8 September 2019 (UTC)[reply]

Many thanks[edit]

Hello Krinkle, thank you very much for fixing wikispecies:User:Rillke/createRedirects.js.
I think, many users are happy; especially in Wikispecies. Thanks and greetings. Orchi (talk) 11:22, 15 October 2019 (UTC)[reply]

krinkle bot[edit]

Hi, Krinkle! I'm working on clarifying our instructions at Wikipedia:Did_you_know/Admin_instructions#Image where right now we tell people to check that Krinkle has protected the image, and I'm wondering about that process. When does Krinkle actually start doing that? The next time the bot runs after a prep has been moved to queue no matter how many queues are slotted, or for the top two queues, or what? And approximately how often does it run? Thanks for any help! --Valereee (talk) 12:03, 17 October 2019 (UTC)[reply]

Duplicate jquery.ui[edit]

Hi! In MediaWiki:Gadget-dashboard.UndeletionRequester.js, due to your recent change, jquery.ui is loaded three times: the two immediately after each other (lines 523 and 524) are really annoying, but the whole function declaration is already in an mw.loader.using(['jquery.ui', ]).then( block. I know it has almost no performance penalty, but it looks ugly, so please remove the last two (and maybe check if you made are similar mistakes elsewhere). Thanks in advance, —Tacsipacsi (talk) 14:10, 26 October 2019 (UTC)[reply]

Hi Tacsipacsi,
There is no performance impact of specifying the same module multiple times as they are automatically de-duplicated by ResourceLoader's JavaScript code before it interacts with the browser cache or server. It will not request or check anything multiple times as a result of such change.
As volunteer global interface editor, I am migrating thousands of gadgets and user scripts with a semi-automated script where a pattern find/replace is matched and I approve or reject each change. I have implemented the algorithms and pattern matching behind this migration in a way that usually avoids duplicate entries being left behind (for cleanliness). However, when entries span multiple lines in the source code, my algorithm will not detect them and instead migrate them separately. This is a compromise where I've prioritised that scripts remain fully functional with no performance impact, in a way that will not require multiple weeks of my time. This might sometimes produce syntax that is different from how a human would write it. If you prefer I skip this on some wikis, or help out, let me know :) --Krinkle 20:55, 29 October 2019 (UTC)[reply]
Oh, I see. As it’s purely about “prettiness”, this change is absolutely worth it, keep it on! :) (Although it does have some performance impact: RL has to do a few comparison operations. But that’s really negligible as long as we’re creating web pages, and not self-driving cars or nuclear power plants.) —Tacsipacsi (talk) 21:08, 29 October 2019 (UTC)[reply]
This is actually important work, and given that importance, I think Timo should be compensated for that - I hope its kind of priced-in their contract. If Krinkle wouldn't help with these changes, most scripts would be already broken and communities would be probably develop a disfavour for changes, either preventing important updates to the code base or facing a less productive community. -- Rillke(q?) 00:02, 30 October 2019 (UTC)[reply]

Gadget infobox nalopen[edit]

Hoi Timo, zou jij MediaWiki:Gadget-Infobox.js even door willen lopen of er niet iets raars inzit of er wat kan worden verbeterd? Mike wil deze graag voor iedereen aanzetten. Alvast bedankt, Multichill (talk) 21:13, 9 November 2019 (UTC)[reply]

Add to protected for[edit]

Can we add images that appear on Wikipedia:Picture of the day/On the main pages to the files that KrinkleBot adds to Commons:Auto-protected files/wikipedia/en? This may seem redundant right now but trust me it is better for us at I can explain in more detail if you would like but the reason is kind of complicated. --- C&C (Coffeeandcrumbs) 12:51, 3 January 2020 (UTC)[reply]

You will notice that Krinklebot is constantly protecting and unprotecting these files every ten minutes. This is because the Main Page is scheduled tomorrow to use a randomizer. It should instead protect all the files that are going to possibly appear. It can do that by protecting all the files that appear on Wikipedia:Picture of the day/On the main pages. --- C&C (Coffeeandcrumbs) 11:22, 23 January 2020 (UTC)[reply]
Thanks Coffeeandcrumbs, this is now done (config change). I've restarted the bot to take this change into account. --Krinkle 18:56, 26 January 2020 (UTC)[reply]
Thank you so much! --- C&C (Coffeeandcrumbs) 22:58, 26 January 2020 (UTC)[reply]

File:MediaWiki database schema latest.svg[edit]

Hoi Timo, moet deze niet weer eens bijgewerkt worden? Vooral handig nu de boel zo op de schop gaat. Multichill (talk) 20:05, 20 January 2020 (UTC)[reply]

@Multichill: Zie mw:Topic:Vf90jqxbapc69dlh. --Krinkle 20:28, 20 January 2020 (UTC)[reply]

Bot down[edit]

Hi, KrinkleBot is down, or at least slower than normal. Thanks for looking. 03:54, 28 March 2020 (UTC)[reply]

License migration - we need help with a script[edit]

Hi Krinkle !

We try to restart the old project of license migration: Commons_talk:License_Migration_Task_Force#Restart_2020.

We could use a script that adds a few buttons and change the license migration tags. We had once but that does not work anymore.

I noticed that you have been fixing the script for license review. So perhaps you can help fix the script for license migration? Or make a new one if that is easier? You can read more about it in the link above. --MGA73 (talk) 09:27, 10 April 2020 (UTC)[reply]

@MGA73: Thanks, I'll keep an eye out, but won't be able to help this time around. I don't have enough time to do this in my volunteer capacity. --Krinkle 18:48, 27 August 2020 (UTC)[reply]
Hi! Thank you for the reply! I actually forgot about it because I'm busy on Japanese Wikipedia fixing images. I think it has been implemented in MediaWiki talk:Gadget-LicenseReview.js but it is not working anymore. I don't know if it takes 5 hours or 5 minutes to fix. But don't worry. No need to stress about it :-) --MGA73 (talk) 18:52, 27 August 2020 (UTC)[reply]


Hoi Timo, ik zie dat je MediaWiki:Gadget-UploadWizard.js hebt verwijderd. Wordt MediaWiki:Gadget-UploadWizard en subpagina's nu nog gebruikt of niet? Multichill (talk) 20:20, 30 August 2020 (UTC)[reply]

Volgens mij niet, de gadget definitie heb ik ge-update om MediaWiki:Gadget-NoUploadWizard te gebruiken als label. --Krinkle 20:46, 30 August 2020 (UTC)[reply]


Hey Krinkle,

Is there a way you could move your changes on the page referenced to Template:Main Page Template/styles.css? It may be a better alternative than performing a change that affects the whole site. 1989 (talk) 13:11, 30 January 2021 (UTC)[reply]

@1989: I think the change benefits pages generally, but I agree that with it only having been seen as an issue on the Main Page currently, it would be nice if it could be loaded as part of a template style. However, this is not possible as template styles are not permitted to affect parts of the interface outside the content area. The contentSub element is not part of the wikitext rendering container, and thus template styles may not reach it. --Krinkle 20:14, 30 January 2021 (UTC)[reply]
The changes caused the gap from the text under the title to be closer together with the content displayed. I have a global user page. Do you notice the difference when seeing my user page here and enwiki? That part is somewhat bothersome. 1989 (talk) 21:55, 30 January 2021 (UTC)[reply]
@1989: Fixed. --Krinkle 23:30, 30 January 2021 (UTC)[reply]


Hallo Krinkle - da Perhelion nicht mehr aktiv ist, suche ich jemand, der das Script ein wenig verbessern kann. Ich fand Deinen Namen in der Versionsgeschichte und hoffe, Du hast Interesse und Zeit, mir zu helfen. Liebe Grüße -- MaxxL - talk 10:21, 16 March 2021 (UTC)[reply]

The bot is down as of June 8, 2021, 15:31[edit]

We have gotten a message at DYK that we cannot post on the main page, because the lead image is not protected here.

Please restart the bot. Thanks. Maile66 (talk) 22:33, 8 June 2021 (UTC)[reply]

@Maile66 Thanks. There is various levels of automatic restart in place for this provided by Toolforge, but something happened yesterday causing this to get stuck. There are plans to offer wikitech:Help:Toolforge/Kubernetes (T283238) to Toolforge users via a new command, which I will switch KrinkleBot to when it becomes available. I hope this will take care of the last few cases where the scheduler can get stuck. --Krinkle 17:36, 9 June 2021 (UTC)[reply]

Stopping the bot[edit]

Hello. There should be a way to stop the bot from updating e.g. Commons:Auto-protected files/wikipedia/fr for a day or two. An editor wants to edit File:Flag of Taliban.svg, but your bot constantly adds it to Commons:Auto-protected files/wikipedia/fr where it gets protected cascadingly. Thanks 4nn1l2 (talk) 14:16, 21 August 2021 (UTC)[reply]

I'd rather not as that would risk other files. However, if French Wikipedia are okay with the change one could upload it under a new name and ask them to use that instead. The other option is to make an {{Edit request}} on the file talk page, for an administrator to handle (Commons:Administrators' noticeboard). I see this has been done already, although in a way that is somewhat unusual. I recommend uploading the file, and then updating the edit request to state that you'd like this file replaced. It's a bit scary to ask someone to copy and paste raw SVG syntax into a file without any mistakes and then upload it straight over a popular and sensitive file like this one without testing it first. --Krinkle (talk) 19:55, 21 August 2021 (UTC)[reply]
French Wikipedia is not an issue here. This file is highly used on many other projects and needs to be fixed, especially now that Afghanistan is the top news in the world. Commons should not be sidetracked by a sister project. If we on Commons decide the file needs to be edited, we should be able to do that. And we should not be defeated by a bot. So I still think it's wise to add some functionality to your code, so that other admins can temporarily stop it if need be (for example by adding a nobot flag such as {{ValidationOptOut}} to the page which the bot understands and respects) and the method should be explained on its user page. This is not just me, another admin came up with this natural solution, and let's not forget that admins are not supposed to know all the ins and outs and technical stuff. Thanks 4nn1l2 (talk) 09:39, 22 August 2021 (UTC)[reply]
I appreciate that you point out the separation of technical concerns and project concerns.
Your original request was in my opinion vague and needlessly led with a specific technical solution without (also) adequately explaining the actual project concern. I stand by that it would have been a mistake to simply take your technical request to unprotect an entire wiki's main page without me understanding why, and leaving me unable to help in a potentially much faster and more effective way based on the underlying problem.

This might not apply to you. But I've observed this pattern on-wiki for over a decade now, where we as fellow contributors communicate in this way. We have decades of poorly thought-out solutions and bad tools as a result. Not because we lack the right people, resources, or ideas, but because we're too darn proud to just explain the problem and give others a chance to actually help, thus leading to either people ignoring you because the solution is unacceptable to other project concerns (as was the case here, and we make no progress), or because people just did as told and subsequently shrink the commnunity by excluding the developer and reducing quality and integrity in the long-term (by preventing someone like me from improving the tool since I don't know what the underlying needs are, and would become disengaged and leave it alone, instead of innovating; as has happened numerous times).

In August, it sounded to me like there was one person who wanted to change one file once for some unknown reason on one wiki but couldn't due to it being protected via a different wiki. And you seemingly not knowing how things work, proposed to opt-out that other wiki to solve "your" specific problem. I know that's not how you meant it, but that's how it came across to me. As I mentioned, the community generally prefers and has solved this use case differently (through edit request or by uploading under a different name and switching). I believe those are reasonable solutions that we use and recommend all the time for this purpose. Of course, you know all that already.

This time around, our (other) admins helpfully explained the use case, and Legoktm investigated. The file name and news event and the need for frequent changes make sense. My previous recommendation would've been a poor fit for this. There is a specific file that we righfully expect will need to be edited frequently, urgently, and we want to open that up to non-admins. That's a very reasonable and understandable project concern. As a general strategy, I think you'll find you get quicker and more useful responses and technical solutions if you present those as such. I don't mind a technical idea to go along with it, by all means help and think along, sometimes it can work out that way and it can certainly help verify that I understand the problem if the technical idea aligns with what I interpreted. But also sometimes it won't work out that way, and there's a large amount of technical ideas and solutions that you then miss out on as a result and then we as a community stagnate and fail to make progress.

We've come up with a quick fix, and the solution we're going with after this is to have an on-wiki page that will list files that are excluded from auto-protection. Any admin will be able to add and remove filenames from the list, and the bot won't protect those. This should make situations like these in the future a lot easier to deal with. --Krinkle (talk) 14:27, 25 February 2022 (UTC)[reply]

Krinklebot not running[edit]

Looks like it hasn't run since two days ago, I just had to manually protect today's enwiki main page files. AntiCompositeNumber (talk) 01:46, 6 November 2021 (UTC)[reply]

Fixed, thanks for the note. It just needed the Pywikibot upgrade. Legoktm (talk) 00:33, 7 November 2021 (UTC)[reply]

KrinkleBot protected 2022 Russian invasion of Ukraine map[edit]

Can you remove the map from user page of KrinkleBot please? The file needs to be frequently edited and is fully protected because of cascading image page, thanks. Commons:Auto-protected files/wikipedia/fr Viewsridge (talk) 06:34, 25 February 2022 (UTC)[reply]