User talk:Krinkle: Difference between revisions

Re. commons:File:Albert goldthorpe all4cups.jpg

Per your comments in IRC, I found the pic, just after you'd left - see File:Albert goldthorpe all4cups.jpg uploaded back in 2004 by Grinner.

Not sure if this helps with (c) though, per the messages about "should not be transferred to Wikimedia Commons".

Let me know if you want me to do any more.  Chzz  ►  11:31, 6 April 2010 (UTC)[reply]

Thanks for adding the Commonscat. Just a note to let you know that it is not necessary to put ref names in "quotes". Mjroots (talk) 05:39, 7 May 2010 (UTC)[reply]

Should User:Krinkle/SpeedyMaintanceCat really include in {{Db-maintenance}}? As DumbBOT (talk · contribs) creates the categories, it uses the subpage, and it simultaneously listed for speedy deletion and ends up at C:SD. Category:Wikipedia files on Wikimedia Commons as of 27 June 2010 has been deleted three times so far because of this. — ξ^xplicit 01:09, 27 June 2010 (UTC)[reply]

Hi Explicit,

I'm trying to figure out how this happened, becuase I've verified multiple times, including another time just now, that User:Krinkle/SpeedyMaintanceCat doesn't spit out {{Db-maintenance}} unless the category it is included in is empty AND is atleast a day old. I have seen multiple times in the past that DumbBOT staticly makes the categories based on June 1, 2010 (2010-06-01). That's not my fault, he should fix his bot to atleast pass the right date, as the other bots that created subcategories do. This is also the reason the subcategories are incorrectly sorted in Category:Wikipedia files on Wikimedia Commons because he passes the date as 2010-06-01. See also Template:Wikipedia files on Wikimedia Commons starter, which is the template DumbBOT uses to create the subcategories. That template expects three parameters (1=, 2= and 4=) to be passed. Which is used for category sortkey, and since this week also for User:Krinkle/SpeedyMaintanceCat. Either way, if the date is passed correctly SpeedyMaintanceCat works fine. The speedy tempalte was shown directly on creation because the future-date category was created using June 1st template. So my SpeedyMaintanceCat-template calculates that June 1st is more then 1 day ago, and it also sees that the category is empty. Krinkle (talk) 15:37, 27 June 2010 (UTC)[reply]

Hello, per your request, I've granted you Rollback rights! Just remember:

• Rollback gives you access to certain scripts, including Huggle and Igloo, some of which can be very powerful, so exercise caution
• Rollback is only for blatant vandalism
• Having Rollback rights does not give you any special status or authority
• Misuse of Rollback can lead to its removal by any administrator
• Please read Help:Reverting and Wikipedia:Rollback feature to get to know the workings of the feature
• You can test Rollback at Wikipedia:New admin school/Rollback
• You may wish to display the {{User wikipedia/rollback}} userbox and/or the {{Rollback}} top icon on your user page

If you have any questions, please do let me know.

--HJ Mitchell | Penny for your thoughts? 00:59, 15 September 2010 (UTC)[reply]

Hi Krinkle. Because your comment at MediaWiki talk:History short led to the initiation of Wikipedia:Miscellany for deletion/MediaWiki:History short, you may be interested in Wikipedia:Deletion review/Log/2010 October 23#MediaWiki:History short. Cunard (talk) 06:52, 24 October 2010 (UTC)[reply]

I went and protected the title and other users had tagged it as a hoax. I can unprotect the title and hope that a proper article comes along. Not exaactly my area of, um, expertise either. :P --PMDrive1061 (talk) 00:50, 23 December 2010 (UTC)[reply]

Hello Krinkle, I am Б. Јанкулоски, admin on mk.wiki. I'd like to thank you for the script updates and ask you if you can help us with two issues.

One is that the default of our collapsible lists (mk:Шаблон:Расклопен список) default to expanded, even though no one has set it to be like that.

The second issue I would like to ask for help with is the mk:Шаблон:Coord template where I have been trying some changes and additions in it and its subtemplates to make it show Macedonian letters for the directions (east, west, north, south), but cannot achieve it at all. Would you know how that can be achieved? I will tell you the abbreviations to be used in stead of E, W, N, S if it is possible to replace these.

I look forward to hearing from you and thank you again for your care! --B. Jankuloski (talk) 00:55, 27 February 2011 (UTC)[reply]

Just to let you know, I had to revert your change to the Hidden template due to not working with some versions of IE. See on Wikipedia:Village pump (technical) for details. -- WOSlinker (talk) 12:34, 28 February 2011 (UTC)[reply]

Hi, Thanks for your jquery & mw.loader tips. Surely it will help. -- Mahir78 (talk) 17:53, 5 March 2011 (UTC)[reply]

John Vandenberg tells me that you've devised a new patrol-links script that's implemented on Wikisource. Is it functional? If yes, can I have a copy? DS (talk) 16:59, 7 March 2011 (UTC)[reply]

To use it at en.wikisource go to Preferences and tick "Makes patrol links execute within the page"

To use it on another wiki, edit your personal common.js and install it. Read here how.

Please don't copy the script, instead import it per the instructions on the documentation page. That way you will stay tuned with the latest version and it won't brake when the software updates.

Will that work in other skins? I use Classic instead of Vector. DS (talk) 02:04, 8 March 2011 (UTC)[reply]

Not tested but should work (let me know if it doesn't). Just remember to put it in common.js or classic.js instead of vector.js. Krinkle (talk) 10:58, 8 March 2011 (UTC)[reply]

Following our IRC conversation we've come to the conclusion you had a different expectation from the script. It does not introduce [Patrol] links on Special:NewPages, instead it binds to the ones already there on the new page itself so you won't have to view the "Succesfully marked as patrolled"-page but instead can mark it directly.

Because of that nature it can be very helpful for patrollers on wikis with edit-patrol. It's not very useful for newpage-patrol.

If you want to really ajaxify your workflow check out m:User:Krinkle/RTRC-docs. Krinkle (talk) 20:54, 11 March 2011 (UTC)[reply]

These pages[1] do not seem to offer a link to mark as patrolled. If you can fix this, assuming a fix is needed, please do so. thanks -- Uzma Gamal (talk) 13:26, 12 March 2011 (UTC)[reply]

no fix needed, there never were patrol links there, so they're not missing. There was or is a local javascript gadget on en.wikipedia that adds these dynamically but I'm not the developer of it, so I wouldn't know. Krinkle (talk) 02:43, 3 April 2011 (UTC)[reply]

All I get is

<table id="mp-topbanner" style="width:100%; background:#f9f9f9; margin:1.2em 0 6px 0; border:1px s

And I cant fix it because it seems the mainpage is edit protected to only alow admins to edit. I get the "view Source" tag when looking at an older revision. Colincbn (talk) 21:49, 20 May 2011 (UTC)[reply]

Don't know what's going on there, seems to be working fine now :). Krinkle (talk) 23:26, 30 August 2011 (UTC)[reply]

Two questions:

• Why can you edit that page even though you're not an admin?
• Your edits to that page apparently have been disrupting all the gadgets; please self-revert. See Wikipedia:Village pump (technical) for details.Jasper Deng (talk) 21:43, 16 January 2012 (UTC)[reply]
  • If it worked on the test wiki, did you remember to take into account that its version is far ahead of Wikipedia's production version in terms of development?Jasper Deng (talk) 22:03, 16 January 2012 (UTC)[reply]
    • I did, and also tested on a local version that does match Wikipedia's production version (1.18wmf1). Krinkle (talk) 22:56, 16 January 2012 (UTC)[reply]
      • Then why did your changes bomb so spectacularly? Malleus Fatuorum 23:04, 16 January 2012 (UTC)[reply]

Hi, I need some help for Bengali Wikipedia at Commons CSS and js for hlist and other updates. I have already updates from enwiki for hlist at MediaWiki:Common.css and MediaWiki:Common.js. But its not working. Look at Template:CSS and JS MediaWiki messages. Thank you in advance.--- Jayanta Nath ^{(Talk|Contrb)} 05:38, 20 February 2012 (UTC)[reply]

I deleted MediaWiki:Pubmedurl. What is the equivalent for ISBN? ---— Gadget850 (Ed) ^talk 01:41, 9 May 2012 (UTC)[reply]

There is none for ISBN, ISBNs are linked to Special:BookSources.

The override for "RFC"s url is MediaWiki:rfcurl (which has already been deleted in 2011). Krinkle (talk) 01:58, 9 May 2012 (UTC)[reply]

I figured out rfcurl. Thought there would be an interface page for ISBN. Thanks for your help. ---— Gadget850 (Ed) ^talk 02:00, 9 May 2012 (UTC)[reply]

You're welcome! Krinkle (talk) 02:11, 9 May 2012 (UTC)[reply]

I have reverted this gadget back to a previous version and in doing so, have undone your most recent change. If this change is still appropriate, please could you re-do it? Thanks — Martin (MSGJ · talk) 14:32, 17 May 2012 (UTC)[reply]

My edit fixed an issue with the code introduced recently, which has been backed out now.

btw, could you leave a message on the talk page as well? Also, please elaborate on "causing problems for some users" there, so that someone can fix it. --Krinkle (talk) 20:28, 17 May 2012 (UTC)[reply]

Hello! I switched to all-lowercase for the following reasons:
1. The English Wikipedia's convention is to style headings in sentence case (apart from proper nouns and such). I see no grammatical distinction warranting the use of uppercase here.
2. The use of lowercase reduces the likelihood of mistaking the text for part of an article's title.
Is there a particular reason, apart from the fact that it happens to be the upcoming MediaWiki default, why the uppercase styling should be used? —David Levy 02:47, 25 May 2012 (UTC)[reply]

I reverted your change to the message override for a few reasons.
1) The override was created to simulate the interface as it would be if 1.20wmf4 was deployed already. In there it uses uppercase. User:Siebrand (community member, developer and localization expert at translatewiki.net) pointed Amir that it should use a capital after colon, and so this was the way it was implemented in the software. I restored that per his judgement, and to prevent unrelated responses in the VPT thread about this, since I imagine some linguistics might complain about this grammatical "error" (if it is that, which I'm not sure of).
2) Although at this point neither is "permanent", it was announced that this software change was created locally, whereas your change was not announced, explained or justified anywhere (not even in the edit summary)

Also, your point about mistaking it for part of the title is a good point. Which is one of the reasons I very much dislike this re-ordered construction, entirely. To make tabbed browsing easier, I recommend using a reversed breadcrumb in the page title (Action < Page name < Site name). Up until now that was the case for all actions and special pages. But this is now broken for Diff and History. For example, right now I see tabs "Editing User:Kr..", "My Watchlist - W.." and "Wikipedia:Villag..". I can't tell whether this last tab is view, diff or history. Krinkle (talk) 03:06, 25 May 2012 (UTC)[reply]

Thanks for the detailed explanation. Having read the VPT discussion before performing the edits, my understanding was (and still is) that the changes were made in response to the complaints posted there, with the default messages from 1.20wmf4 serving as an expedient solution thereto. There was no mention of a desire to simulate their exact formatting, which we frequently override for various reasons (including adherence to the English Wikipedia's style conventions, which don't always jibe with the MediaWiki defaults). Having personally performed similar tweaks on several occasions, I regarded these as routine and uncontroversial.

As a professional proofreader and copy editor, I'm confident that neither version constitutes an "error" from a linguistic standpoint. From a stylistic standpoint, the all-lowercase format more closely reflects the English Wikipedia's conventions. —David Levy 03:45, 25 May 2012 (UTC)[reply]

Just a 3rd party comment: I think "Difference between revisions" should be lowercase. It seems to jump out too much like this. --hydrox (talk) 20:30, 25 May 2012 (UTC)[reply]

I noticed at Berlin, actually, but thanks for reminding me to fix it - I'd quite forgotten. Should be resolved now, though. Thanks! - Jarry1250 ^{[Deliberation needed]} 00:17, 6 June 2012 (UTC)[reply]

Please take this example change as a good point to step back, and think about 'caution' when editing.

You took this example code

this.a = checkInt(x)

// ^ semicolons are optional

and changed it to

this.a = checkInt(x);

// ^ semicolons are optional

What can be said about that? At the very least you frustrated the intent of the example!

I would go back to the article and recheck and rethink your changes. Using 'lint' as a reason to change'correct' the example is simply wrong. For instance, is changing

t = b; b = a; a = t;

to

t = b;

b = a;

a = t;

really worth destroying the point that you can have more than one executable statement on one line?

This section is after all about the syntax of the language, and is not supposed to be an illustration of perfection based on the ideals of one person's opinion.

And yes, WP:ENGVAR edits upset me too. Think about the article first and foremost! Shenme (talk) 04:27, 22 August 2012 (UTC)[reply]

Hi. So in this edit you added dependencies, but you forgot one out: the gadget also needs mediawiki.user (it calls mw.user.sessionId() somewhere). for some bizarre reason this only creates problem when i use IE (i think i use other gadgets and scripts that *do* load mediawiki,user, so in my case it's basically a race condition, and i guess in IE popup wins the race, so the call to mw.user.sessionId() throws an exception). Could you please add the missing dependency?

thanks a bunch - קיפודנחש (aka kipod) (talk) 19:11, 19 December 2012 (UTC)[reply]

I've tried to make fixes to this gadget before but never with good results. It is a big mess. The referenced edit has been reverted since. Please ask on MediaWiki talk:Gadget-popups.js and one of the maintainers can help you instead. Krinkle (talk) 21:16, 19 December 2012 (UTC)[reply]

Thanks.

the reason i came here instead of MediaWiki talk:Gadget-popups.js is simple: the last message on this page is a bug report i wrote several months ago (it deals with the discrepancy between "page size" in bytes and "raw page length" in characters), and it never received any response (not even a "wontfix" kind of answer), so i assume this page is dysfunctional. i will talk with one of the other sysops that sometimes modifies the code of this gadget.

peace - קיפודנחש (aka kipod) (talk) 15:32, 20 December 2012 (UTC)[reply]

Several users (myself included) are still having css-related edit page display errors (see Wikipedia:Village_pump_(technical)#Strange_error_in_edit_mode for the screen shot/story). My edit page shows the new line and redirect (used to be table) in the edit field and there is no find/replace button. Even after closing the advanced bar and reopening, the find/replace button is still missing. Can this be fixed? Carlossuarez46 (talk) 17:36, 29 March 2013 (UTC)[reply]

Can you comment on this? Can postedit be used, instead of jsMessage? πr² (t • c) 00:54, 3 July 2013 (UTC)[reply]

Hi,

Thanks for the bug reports. I wrote a message to Ltrlg about them. Are they really a problem ?

• I think the default value for "required" is false, so it's not important to have this line if "false" is the desired value. Do you think it should be added whatever its value ?
• Tabs or whitespace are equivalent for JSON I think.

I see <templatedata>...</templatedata> as a block of code that users shouldn't be preoccupied with its formatting, and it's not really important if the formatting changes when you modify this block with a tool. Technically, I don't see how a tool could keep the existing formatting of a JSON block, except by doing complex comparisons which won't bring any real value. --NicoV ^{(Talk on frwiki)} 05:44, 25 July 2013 (UTC)[reply]

Normalisation and conversion side-effects (whitespace and stripping of default values) is a problem in two ways:

• Different tools normalise in different ways (2 spaces, 4 spaces, 8 spaces, tabs, ..), thus cause every other edit to become a mess. Normalisation is only acceptable if it happens on the server-side and always in the same way.
• Stripping of default values is generally bad in my opinion as the defaults could change. Besides, this one is actually quite simple to prevent in a tool (parse the original object and keep it, don't build a new object from the form input but update the original based on values that were changed by the user, this will also prevent things like "[object Object]" unless the user touched that field).

There were other problems I noticed in your script, such as the "interesting" way in which it builds the JSON. There are built-in tools (both in the browser and in MediaWiki) to generate valid JSON. Concatenating strings seems like a rather complicated way to do it. Look into the native JSON.stringify( data, null, 4 );, for example (or the JSON2.js polyfill if you want to support older browsers).

I appreciate all the various efforts on such short notice coming from all of you to create different tools for it. However I'd prefer not to have them be promoted on the documentation page of the MediaWiki extension itself.

At this early stage, things will likely change a lot. The last thing I want to be occupied with right now is problems caused by side-effects introduced or broken by gadgets like these. Feel free to use them and promote them locally, but at least for now I'd like to not promote them on the extension page itself ("at your own risk", unofficial, kind of thing).

Lastly, I'd like to have an edit interface for this inside WikiEditor and/or VisualEditor and it should be maintained inside the extension, not separately as a gadget. That way when things change, it will be associated with the version installed on the wiki in question, and it would be a lot easier to maintain that way by having the two in 1 place. Of course, as usual, gadgets would remain able to override this feature with a different one to your liking, but at least there'd be an official one that is supported and maintained for all wikis/languages. Krinkle (talk) 15:41, 25 July 2013 (UTC)[reply]

Thanks for the answer. I totally agree that that kind of tools should be part of the extension itself (that's why I opened bugzilla 51734). Okay for the promotion on the extension page: I also added a list of tools on the TemplateData help page on mw, feel free to remove them if you think it's not appropriate (but it's the only common place between all the wikis).

I will transmit your remarks to Ltrlg. I only copied his script here, translated it into English and made some promotion on enwiki. But now the script on frwiki handles translation and being used from another wiki, so the only version is there. --NicoV ^{(Talk on frwiki)} 17:20, 25 July 2013 (UTC)[reply]

For JSON.stringify : I didn’t know the third argument (I thought only non-indented JSON can be generated), I will see how to use it.

Keeping the objet forces to rename a property at each time the user changes the name. Why not? This could simplify the script in some ways.

I can try to create an intelligent normaliser (at least detect tabulations; maybe number of space)

— Ltrl G^☎, 17:58, 25 July 2013 (UTC)[reply]

Heads up! --Dirk Beetstra ^{T C} 09:55, 25 April 2014 (UTC)[reply]

Hey. I saw you made a cleanup edit to MediaWiki:Gadget-ProveIt.js. However, as I mentioned at the top of the file, I track this in git (pull requests always welcome). Currently, there is a pretty significant bug open, which is fixed and tested locally. I'm going to release the version from git (to fix the bug), and then remerge your changes into the git repository. I've made a GitHub issue so I won't forget. Thanks again. Superm401 - Talk 22:26, 29 June 2014 (UTC)[reply]

Sorry, it actually linked to Google Code, but that points to GitHub since I moved there. Superm401 - Talk 22:29, 29 June 2014 (UTC)[reply]

I've now merged your change into git and deployed it (along with a couple other things). Thanks again, and sorry for the delay. Superm401 - Talk 04:09, 27 July 2014 (UTC)[reply]

Hey, I saw this change you made and wanted to ask: where can I learn more about which modules are optional? I've been assuming that I could rely on the contents of the mw object, so I'd like to learn more to avoid the mistake. Thanks, {{Nihiltres|talk|edits}} 15:42, 9 July 2014 (UTC)[reply]

@Nihiltres: All modules are optional. The only thing available synchronously by default are the deprecated legacy functions from the "wikibits" module. All other modules should be explicitly declared as dependency to ensure that they will be loaded and (more importantly) that your code executes after it has finished loading. Modules like "mediawiki.util" are almost always available because it's most likely there will be another gadget on the page that loaded it for you already, but that's a fragile thing to depend on. And, while it does load the module, it may not load it in time.
See also ResourceLoader/Modules, ResourceLoader/Migration guide, mw:Developing with ResourceLoader
Krinkle (talk) 15:54, 9 July 2014 (UTC)[reply]

...in which sense? Helder.wiki 17:25, 9 July 2014 (UTC)[reply]

@Helder.wiki: I added that code minutes earlier in the previous edit. It's safer by not relying on $.param to cast non-string values to strings (and cast them as "false"/"true"; not 0/1). In this case AutoEd doesn't inspect the value at all, but I'd rather have the value used be explicitly there, since there is no such thing as boolean values in a query string. Krinkle (talk) 18:58, 9 July 2014 (UTC)[reply]

Ok. Helder.wiki 19:12, 9 July 2014 (UTC) PS: be aware that edits like this do not generate notifications due to bugzilla:54639.[reply]

Hi Krinkle,

I noticed you put some documentation on top of my GoogleTrans gadget.

I also noticed you are an actual developer of wikimedia.

How about a cursor hover translation feature for all of Wikipedia. The GoogleTrans gadget certainly shows it can be done.

Having all knowledge in one place for all people is a truly noble goal, but isn't overcoming language barriers an associated and also noble goal for such a project. And cursor hover translation certainly is quicker to look up a word (or small amounts of selected text -- which GoogleTrans also does) than manually looking up a dictionary.

Google isn't maintaining the word translator in the Google toolbar anymore. There is imtranslator.net, but it is a bit clunky with an extra translation window hanging around the screen. Cursor hover translation is also very good when you are trying to brush up on a language, when you know it a bit and want to get better at it, like Russian speakers in the Ukraine trying to learn a bit of Ukrainian, or English speaking Canadians trying to brush up on their high school French. The full page translations that Google does are not very good if you are actually trying to learn the source language. For instance, I can read French well, but will need to translate a word every paragraph or so. And, as for my Spanish, I need this once or twice a sentence.

Reading other wiki languages is very good for your understanding of the world. I remember reading in the eswiki that the USA had to borrow 41 cents to every dollar it spent recently. That was a very good statement that the US really was in budget problems. Such a detail would have been scrubbed out of the enwiki by legislative aids in Washington. So, as it turns out, in a world where everybody uses the enwiki, it's difficult to put embarrassing truth in an article there. This means you need to be able to read a wiki other than the enwiki to get a good view of a contraversial subject. This means you will be rewarded by reading wikis in languages you are not fully proficient in. This means that cursor hover word and selected text translation is an aid that will help this.

As for cost, I don't think it will be that much. Google charges 20$ a million characters of translation, that's 5000 translations for a dollar if each word is 10 characters. Perhaps only allowing single word translations instead of selected text might keep the cost manageable.

Endo999 (talk) 02:06, 28 August 2014 (UTC)[reply]

Oh Krinkle,

I like the hovercards, good feature.

Endo999 (talk) 02:09, 28 August 2014 (UTC)[reply]

Hi Endo999,

I maintain user scripts, gadgets and contribute to the wiki, in my spare time as a volunteer. I also work as a Wikimedia developer on the MediaWiki software, the infrastructure behind it, and various products used alongside it such as VisualEditor (see mw:User:Krinkle). I'm not directly involved with Hovercards but I'm glad you like it!

Having inline translations sounds like an interesting idea to incorporate into a native MediaWiki extension. I'm not in a position to decide whether we can use Google's services, but I'd recommend getting in touch with the Wikimedia Language engineering team to find out. Perhaps e-mail Alolita Sharma and see what the possibilities are. --Krinkle (talk) 23:12, 29 August 2014 (UTC)[reply]

Is there any way you could make this work without adding tons of pages to Category:Pages using duplicate arguments in template calls? Plastikspork _―Œ^(talk) 04:25, 31 March 2015 (UTC)[reply]

Thanks. Replied at Wikipedia talk:Editnotice#Make use of MediaWiki:Editnotice-notext. --Krinkle (talk) 05:16, 31 March 2015 (UTC)[reply]

RTRC worked till yesterday but now it just loads forever. It never happened before. Can you fix the problem? Supdiop ^talk 07:28, 18 June 2015 (UTC)[reply]

It started working again, maybe I should have waited for some time. Supdiop ^talk 17:51, 18 June 2015 (UTC)[reply]

@Supdiop: No, please don't wait! I was able to fix it this quickly largely thanks to your message. There isn't a whole lot I can do since Wikimedia Labs having issues is what caused the problem (see labs-announce post). However I was able to improve RTRC's initialisation process to failover more gracefully. From now on, the application will continue to load if Labs is unavailable – though without the latest interface and translation data (which come from translatewiki.net, via my Tool Labs tool). Thanks! --Krinkle (talk) 18:27, 18 June 2015 (UTC)[reply]

Thanks for fixing it very quickly and also for creating it! I will notify you if it happens again. Supdiop ^talk 20:28, 18 June 2015 (UTC)[reply]

Please see Wikipedia talk:Tools/Navigation popups#Anyone else getting recent breakage?. Will popups be restored please? DuncanHill (talk) 01:44, 7 August 2015 (UTC)[reply]

Thanks for notifying me. It looks like the issue has been resolved. I'm glad popups can finally enjoy in the performance optimisations provided by ResourceLoader. Krinkle (talk) 17:26, 7 August 2015 (UTC)[reply]

Hi, I am partoller at wiki commons. I would like to use Real-Time recent Changes tool to patrol recent changes in commons. please help me to use it. I tried a lot, but i failed. i need your kind help. I am waiting your instructions. -- --Iqsrb722 (talk) 05:07, 15 November 2015 (UTC)[reply]

@Iqsrb722: I works for me at commons:Special:BlankPage/RTRC. In what way is it failing? –Krinkle 00:40, 17 November 2015 (UTC)[reply]

No, actually i could not find the link, thats why i disturbed you, Oh, thanks for your kind assistance.--Iqsrb722 (talk) 07:47, 17 November 2015 (UTC)[reply]

@Iqsrb722: Cool, I'm glad it's working. Thanks for using RTRC! –Krinkle 16:05, 17 November 2015 (UTC)[reply]

Hey, Krinkle, Elitre pinged you on my talk page, but I wanted to double up here, just in case (I'm sure you're not getting enough messages about this already! :D ). Anyway, I know from VPT that the changes to the rollback function were to be reverted, which might be why my script (User:Writ Keeper/Scripts/massRollback.js) started working again, after people had reported problems with it earlier today. I also made a fix to it; originally, I was scavenging the rollback token from the URLs of the rollback links, to save on the API call, but since I guess they're shifting to POST instead of GET, the rollback token will be taken out of the URL. So I stopped being lazy and just implemented the API call to get the token.

So, ultimately, is that all I need to do to keep this working in the future? What else might I need to do? I guess I'm not sure exactly how the rollback function is/will be changing, and how it would affect the API calls I'm making in my script. Any help would be appreciated, thanks! Writ Keeper ⚇♔ 18:56, 27 May 2016 (UTC)[reply]

@Writ Keeper: Yep, that's all. But, I do have a few further suggestions for you: edit 1, edit 2, and (biggest) edit 3. --Greetings, Krinkle (talk) 19:35, 27 May 2016 (UTC)[reply]

I've made the first two suggested changes (thanks!). Y'know, as far as the third goes, people keep trying to get me to use the mw.api instead of straight jQuery calls; why is that? I mean, in this case, I guess it saves us from having a separate call for the rollback token, which is definitely nice. But by and large, I don't really feel like it's that much simpler than just using jQuery, though admittedly that's likely because I'm just used to jQuery. What's the case to be made for switching to the mw.api calls? Writ Keeper ⚇♔ 20:34, 27 May 2016 (UTC)[reply]

Hi Krinkle, I changed some pictures for the Main Page at Wikipedia:Main Page/Commons media protection, but KrinkleBot has not yet protected them at Commons, c:Commons:Auto-protected files/wikipedia/en. Can you see what's wrong? Stephen 04:03, 29 August 2016 (UTC)[reply]

@Step: Thanks, it's back up now. –Krinkle (talk) 20:54, 4 September 2016 (UTC)[reply]

Krinkle: The bot doesn't appear to be functioning. —David Levy 22:19, 13 October 2016 (UTC)[reply]

Replied on Commons. (Fixed last week.) –Krinkle (talk) 21:45, 19 October 2016 (UTC)[reply]

Krinkle: The bot appears to be down again. —David Levy 02:26, 19 November 2016 (UTC)[reply]

Wow, that was fast. Thanks! —David Levy 02:35, 19 November 2016 (UTC)[reply]

	The Technical Barnstar
	Thanks again for resolving the issues I've had with my installed JavaScripts. MCMLXXXIX 05:23, 21 March 2017 (UTC)[reply]

The portal system is being overhauled.

They could really use some input from JS programmers on what is possible.    — The Transhumanist   22:44, 14 May 2018 (UTC)[reply]

Please see WP:RS. The content should be removed as this website is at best, spam. It can never, under any circumstance be used to source anything on Wikipedia. You can see many discussions about this and related websites at WP:RSN. Praxidicae (talk) 10:10, 4 October 2018 (UTC)[reply]

Thanks for your fix at New Year's day. Unfortunately, the link was broken by an over-enthusiastic editor who mistook my insertion of the date template with changes to the dates! I had to undo your edit to reinstate the date markup, but I've ensured your correction is still there. Thanks. The Parson's Cat (talk) 09:15, 2 January 2019 (UTC)[reply]

Thanks for creating ESLint.

User:Atsme while reveiwing this page as a part of our page curation process had the following comments:

The article needs RS (not blogs, PRs) and has been tagged as such.

To reply, leave a comment here and prepend it with {{Re|Atsme}}. And, don't forget to sign your reply with ~~~~ .

Message delivered via the Page Curation tool, on behalf of the reviewer.

^Atsme _Talk 📧 13:36, 7 July 2019 (UTC)[reply]

@Atsme: Is there a specific statement or claim that you believe should have a better source, or do you mean a better source to indicate the notability of the subject? --Krinkle (talk) 14:10, 7 July 2019 (UTC)[reply]

Hi, Krinkle - there are quite a few refs that are blogs, one is a PR. My suggestion is more along the line of adding updated academic and/or MSM sources for the benefit of our readers. Of course, if the blogs are authored by independent experts, that's fine. There's no question that the article passes notability but by now, there should be some higher quality secondary sources out there. I was also wondering if ESLint was one of the tools our techs use to clean up lint on the pedia. Happy editing!! ^Atsme _Talk 📧 15:10, 7 July 2019 (UTC)[reply]

Hi. First, I wanted to thank you for all those great technical helps. There is something that I noticed recently; I think OrphanTalk is out of service, just wanted to ask if you are going to fix it. Thanks. Ahmad^Talk 19:10, 14 July 2019 (UTC)[reply]

@Ahmad Hi, this happens due to phab:T166949. If you're on Freenode IRC, you can always ask in #wikimedia-cloud for the tool to be restarted (be sure to mention "T166949"). I have restarted it now. Thanks! --Krinkle (talk) 20:02, 14 July 2019 (UTC)[reply]

Thank you! I'll check IRC from now on. Ahmad^Talk 20:06, 14 July 2019 (UTC)[reply]

	The Tireless Contributor Barnstar
	Thanks for your contributions across Wikimedia projects. Masum Reza📞 16:53, 7 August 2019 (UTC)[reply]