User talk:Eatcha/Archive 2

Code issues in User:Eatcha/common.js

Hi Eatcha, I am a bored bot (this is kind of a computer program) that is watching the recent changes and tapping buttons like I did now.

Curious about the reason? Possibly not but I will tell you anyway:

1. You edited User:Eatcha/common.js. Glad to see you coding in javascript! Have you ever considered becoming a MediaWiki hacker?
2. Though, that change appears to introduce 24 new jshint issues — the page's status is now having warnings. Note that invalid or ambiguous code often has unwanted side effects like breaking other tools for you. If you cannot find out how to fix it, I suggest blanking the page for now.
3. To help you understanding where the issues are, I have aggregated a report here and now. If you have questions, don't hesitate to ask users experienced in javascript writing for help. But do not ask the bot's operators (chronically overwrought) unless you suspect an error of mine. If you prefer not getting spammed by me, you can opt-out reports by adding {{ValidationOptOut|type=all}} to your user page or cmb-opt-out anywhere on your your global user page on Meta. Good luck at Wikimedia Commons and happy hacking!

1. ISSUE: line 15 character 15: 'i' is already defined. - Evidence: for(var i = 0; i < rightJS.Tags.length; i++){
2. ISSUE: line 75 character 375: Bad or unnecessary escaping. - Evidence: (function($,mw){'use strict';if(!mw.libs||mw.libs.threadSign)throw new Error('Initializing of threadSign stopped because it was already executed');var name='AutoSign',ns=mw.config.get('wgNamespaceNumber'),$textarea,$editform,minoredit,txtOld='',CmtE='',txtLen,lrLen,txtEndLen,txtOldEnd,reUser='',signTxt=[],txtOldL;var c=$.extend({usersignature:window.usersignature||'-- ~~\~~',sigAccessKey:'>',sigText:null},mw.config.get(['wgDBname','wgAction','wgContentLanguage','wgRelevantUserName','wgFormattedNamespaces','wgUserName','wgPageName','wgIsArticle']));var ts={version:'v1.93d',$sigBox:$(),$label:$(),onoff:$.noop,init:function(){if(ts.config instanceof Object)
3. ISSUE: line 101 character 294: Bad or unnecessary escaping. - Evidence: $textarea.textSelection('setSelection',{start:pos}).textSelection('scrollToCaretPosition').focus();return txt;},getUser:function(){var txt=txtOld;var strRe=new RegExp('\\[\\[(?:'+c.wgFormattedNamespaces[2]+'(?:in)?|'+c.wgFormattedNamespaces[3]+'|User(?:[ _]talk)?): ?([^\\]\\|[]+)(?:\\|([^\\]\[]+))?\\]\\]','ig');var topicPosters=txt.match(strRe)||[];var posterList=[];topicPosters=$.grep(topicPosters.reverse(),function(p,i){return $.inArray(p,topicPosters)===i;});var u=topicPosters.length,reUser,userDict={};while(u--)
4. ISSUE: line 196 character 6: Missing semicolon. - Evidence: }
5. ISSUE: line 350 character 32: Missing semicolon. - Evidence: return el.innerText
6. ISSUE: line 772 character 59: Expected a conditional expression and instead saw an assignment. - Evidence: while( elemToRemove = container.childNodes[i] ) {
7. ISSUE: line 837 character 20: 'i' is already defined. - Evidence: for( var i = 0; i < liveSelflinks.length; i++ ) {
8. ISSUE: line 875 character 20: 'i' is already defined. - Evidence: for( var i = 0; i < oldPsdLinks.length; i++ ) {
9. ISSUE: line 885 character 24: 'i' is already defined. - Evidence: for( var i = 0; i < psdLinks.length; i++ ) {
10. ISSUE: line 903 character 24: 'i' is already defined. - Evidence: for( var i = 0; i < psdLinks.length; i++ ) {
11. ISSUE: line 904 character 34: 'psdContainer' is already defined. - Evidence: var psdContainer = ascendToCommentContainer( psdLinks[i], /* live */ false );
12. ISSUE: line 906 character 36: 'psdTextContent' is already defined. - Evidence: var psdTextContent = normalizeTextContent( surrTextContentFromElem( psdContainer ) );
13. ISSUE: line 981 character 21: Unreachable 'break' after 'return'. - Evidence: break;
14. ISSUE: line 988 character 22: 'currNode' is already defined. - Evidence: var currNode = corrCmt;
15. ISSUE: line 1049 character 20: 'i' is already defined. - Evidence: for( var i = 0; i < allHeaders.length; ) {
16. ISSUE: line 1062 character 30: 'currNode' is already defined. - Evidence: var currNode = allHeaders[i];
17. ISSUE: line 1074 character 21: Function declarations should not be placed in blocks. Use a function expression or move the statement to the top of the outer function. - Evidence: function hasDiscussionPage( dataMw ) {
18. ISSUE: line 1100 character 35: Don't make functions within a loop. - Evidence: } );
19. ISSUE: line 1567 character 13: Function declarations should not be placed in blocks. Use a function expression or move the statement to the top of the outer function. - Evidence: function sanitizeUsername( u ) {
20. ISSUE: line 1644 character 21: Function declarations should not be placed in blocks. Use a function expression or move the statement to the top of the outer function. - Evidence: function finishReply( _ ) {
21. ISSUE: line 1751 character 49: 'cmtAuthor' used out of scope. - Evidence: "value='Replying to " + cmtAuthor + "'/><br />" : "" ) +
22. ISSUE: line 1766 character 25: 'cmtAuthor' used out of scope. - Evidence: cmtAuthor &&
23. ISSUE: line 1767 character 25: 'cmtAuthor' used out of scope. - Evidence: cmtAuthor !== mw.config.get( "wgUserName" ) &&
24. ISSUE: line 1768 character 47: 'cmtAuthor' used out of scope. - Evidence:  !/(\d+.){3}\d+/.test( cmtAuthor ) ) {
25. ISSUE: line 1769 character 92: 'cmtAuthor' used out of scope. - Evidence: replyDialogField.value = window.replyLinkPreloadPingTpl.replace( "##", cmtAuthor );
26. ISSUE: line 1925 character 10: Missing semicolon. - Evidence: }
27. ISSUE: line 2157 character 20: 'i' is already defined. - Evidence: for( var i = 0; i < insideArchived.length; i++ ) {

Your CommonsMaintenanceBot (talk) at 09:49, 11 April 2019 (UTC).

Code issues in User:Eatcha/common.js

Hi Eatcha, I am a bored bot (this is kind of a computer program) that is watching the recent changes and tapping buttons like I did now.

Curious about the reason? Possibly not but I will tell you anyway:

1. You edited User:Eatcha/common.js. Glad to see you coding in javascript! Have you ever considered becoming a MediaWiki hacker?
2. Though, that change appears to introduce 6 new jshint issues — the page's status is now having warnings. Note that invalid or ambiguous code often has unwanted side effects like breaking other tools for you. If you cannot find out how to fix it, I suggest blanking the page for now.
3. To help you understanding where the issues are, I have aggregated a report here and now. If you have questions, don't hesitate to ask users experienced in javascript writing for help. But do not ask the bot's operators (chronically overwrought) unless you suspect an error of mine. If you prefer not getting spammed by me, you can opt-out reports by adding {{ValidationOptOut|type=all}} to your user page or cmb-opt-out anywhere on your your global user page on Meta. Good luck at Wikimedia Commons and happy hacking!

1. ISSUE: line 15 character 15: 'i' is already defined. - Evidence: for(var i = 0; i < rightJS.Tags.length; i++){
2. ISSUE: line 75 character 375: Bad or unnecessary escaping. - Evidence: (function($,mw){'use strict';if(!mw.libs||mw.libs.threadSign)throw new Error('Initializing of threadSign stopped because it was already executed');var name='AutoSign',ns=mw.config.get('wgNamespaceNumber'),$textarea,$editform,minoredit,txtOld='',CmtE='',txtLen,lrLen,txtEndLen,txtOldEnd,reUser='',signTxt=[],txtOldL;var c=$.extend({usersignature:window.usersignature||'-- ~~\~~',sigAccessKey:'>',sigText:null},mw.config.get(['wgDBname','wgAction','wgContentLanguage','wgRelevantUserName','wgFormattedNamespaces','wgUserName','wgPageName','wgIsArticle']));var ts={version:'v1.93d',$sigBox:$(),$label:$(),onoff:$.noop,init:function(){if(ts.config instanceof Object)
3. ISSUE: line 101 character 294: Bad or unnecessary escaping. - Evidence: $textarea.textSelection('setSelection',{start:pos}).textSelection('scrollToCaretPosition').focus();return txt;},getUser:function(){var txt=txtOld;var strRe=new RegExp('\\[\\[(?:'+c.wgFormattedNamespaces[2]+'(?:in)?|'+c.wgFormattedNamespaces[3]+'|User(?:[ _]talk)?): ?([^\\]\\|[]+)(?:\\|([^\\]\[]+))?\\]\\]','ig');var topicPosters=txt.match(strRe)||[];var posterList=[];topicPosters=$.grep(topicPosters.reverse(),function(p,i){return $.inArray(p,topicPosters)===i;});var u=topicPosters.length,reUser,userDict={};while(u--)
4. ISSUE: line 269 character 26: 'j' is already defined. - Evidence: for(var j=globaluserinfo.groups.length-1; j>=0; j--){
5. ISSUE: line 271 character 30: 'i' is already defined. - Evidence: var i=document.createElement('IMG');
6. ISSUE: line 283 character 22: 'i' is already defined. - Evidence: var i=document.createElement('IMG');
7. ISSUE: line 290 character 18: 'i' is already defined. - Evidence: var i=document.createElement('SPAN');
8. ISSUE: line 361 character 18: 'u' is already defined. - Evidence: var u=a.match(/\/wiki\/User:([^\/]+)/);
9. ISSUE: line 366 character 18: 'u' is already defined. - Evidence: var u=['',document.getElementById('mw-log-user').defaultValue];

Your CommonsMaintenanceBot (talk) at 09:52, 11 April 2019 (UTC).

Code issues in User:Eatcha/common.js

Hi Eatcha, I am a bored bot (this is kind of a computer program) that is watching the recent changes and tapping buttons like I did now.

Curious about the reason? Possibly not but I will tell you anyway:

1. You edited User:Eatcha/common.js. Glad to see you coding in javascript! Have you ever considered becoming a MediaWiki hacker?
2. Though, that change appears to introduce 37 new jshint issues — the page's status is now having warnings. Note that invalid or ambiguous code often has unwanted side effects like breaking other tools for you. If you cannot find out how to fix it, I suggest blanking the page for now.
3. To help you understanding where the issues are, I have aggregated a report here and now. If you have questions, don't hesitate to ask users experienced in javascript writing for help. But do not ask the bot's operators (chronically overwrought) unless you suspect an error of mine. If you prefer not getting spammed by me, you can opt-out reports by adding {{ValidationOptOut|type=all}} to your user page or cmb-opt-out anywhere on your your global user page on Meta. Good luck at Wikimedia Commons and happy hacking!

1. ISSUE: line 15 character 15: 'i' is already defined. - Evidence: for(var i = 0; i < rightJS.Tags.length; i++){
2. ISSUE: line 75 character 375: Bad or unnecessary escaping. - Evidence: (function($,mw){'use strict';if(!mw.libs||mw.libs.threadSign)throw new Error('Initializing of threadSign stopped because it was already executed');var name='AutoSign',ns=mw.config.get('wgNamespaceNumber'),$textarea,$editform,minoredit,txtOld='',CmtE='',txtLen,lrLen,txtEndLen,txtOldEnd,reUser='',signTxt=[],txtOldL;var c=$.extend({usersignature:window.usersignature||'-- ~~\~~',sigAccessKey:'>',sigText:null},mw.config.get(['wgDBname','wgAction','wgContentLanguage','wgRelevantUserName','wgFormattedNamespaces','wgUserName','wgPageName','wgIsArticle']));var ts={version:'v1.93d',$sigBox:$(),$label:$(),onoff:$.noop,init:function(){if(ts.config instanceof Object)
3. ISSUE: line 101 character 294: Bad or unnecessary escaping. - Evidence: $textarea.textSelection('setSelection',{start:pos}).textSelection('scrollToCaretPosition').focus();return txt;},getUser:function(){var txt=txtOld;var strRe=new RegExp('\\[\\[(?:'+c.wgFormattedNamespaces[2]+'(?:in)?|'+c.wgFormattedNamespaces[3]+'|User(?:[ _]talk)?): ?([^\\]\\|[]+)(?:\\|([^\\]\[]+))?\\]\\]','ig');var topicPosters=txt.match(strRe)||[];var posterList=[];topicPosters=$.grep(topicPosters.reverse(),function(p,i){return $.inArray(p,topicPosters)===i;});var u=topicPosters.length,reUser,userDict={};while(u--)
4. ISSUE: line 269 character 26: 'j' is already defined. - Evidence: for(var j=globaluserinfo.groups.length-1; j>=0; j--){
5. ISSUE: line 271 character 30: 'i' is already defined. - Evidence: var i=document.createElement('IMG');
6. ISSUE: line 283 character 22: 'i' is already defined. - Evidence: var i=document.createElement('IMG');
7. ISSUE: line 290 character 18: 'i' is already defined. - Evidence: var i=document.createElement('SPAN');
8. ISSUE: line 361 character 18: 'u' is already defined. - Evidence: var u=a.match(/\/wiki\/User:([^\/]+)/);
9. ISSUE: line 366 character 18: 'u' is already defined. - Evidence: var u=['',document.getElementById('mw-log-user').defaultValue];
10. ISSUE: line 576 character 28: The object literal notation {} is preferable. - Evidence: var qui_system = new Object();
11. ISSUE: line 577 character 11: ['online'] is better written in dot notation. - Evidence: qui_system['online'] = [ "Online", "//upload.wikimedia.org/wikipedia/commons/thumb/a/ab/Green_pog.svg/15px-Green_pog.svg.png" ];
12. ISSUE: line 578 character 11: ['around'] is better written in dot notation. - Evidence: qui_system['around'] = [ "Around", "//upload.wikimedia.org/wikipedia/commons/thumb/b/b2/Purple_pog.svg/15px-Purple_pog.svg.png" ];
13. ISSUE: line 579 character 11: ['busy'] is better written in dot notation. - Evidence: qui_system['busy'] = [ "Busy", "//upload.wikimedia.org/wikipedia/commons/thumb/d/d7/Blue_pog.svg/15px-Blue_pog.svg.png" ];
14. ISSUE: line 580 character 11: ['sleep'] is better written in dot notation. - Evidence: qui_system['sleep'] = [ "Sleeping", "//upload.wikimedia.org/wikipedia/commons/thumb/0/0c/Red_pog.svg/15px-Red_pog.svg.png" ];
15. ISSUE: line 581 character 11: ['offline'] is better written in dot notation. - Evidence: qui_system['offline'] = [ "Offline", "//upload.wikimedia.org/wikipedia/commons/thumb/4/46/Black_pog.svg/15px-Black_pog.svg.png" ];
16. ISSUE: line 582 character 11: ['unknown'] is better written in dot notation. - Evidence: qui_system['unknown'] = [ "Unknown", "//upload.wikimedia.org/wikipedia/commons/thumb/1/1a/White_pog.svg/15px-White_pog.svg.png" ];
17. ISSUE: line 630 character 30: 'statusRegExp' is already defined. - Evidence: var statusRegExp = /&action=edit&addfriend=(.*)/;
18. ISSUE: line 633 character 25: 'qui_cmt' is already defined. - Evidence: var qui_cmt = "Adding [[User:"+new_friend+"|"+new_friend+"]] to my [[WP:Qui|Qui]] friends";
19. ISSUE: line 646 character 30: 'statusRegExp' is already defined. - Evidence: var statusRegExp = /&action=edit&delfriend=(.*)/;
20. ISSUE: line 648 character 25: 'userexp' is already defined. - Evidence: var userexp = new RegExp("\\[\\[User:"+del_friend+watcherspage+".*[\r\n]*", "g" );
21. ISSUE: line 649 character 25: 'qui_cmt' is already defined. - Evidence: var qui_cmt = "Removing [[User:"+del_friend+"|"+del_friend+"]] from my [[WP:Qui|Qui]] friends";
22. ISSUE: line 666 character 19: 'body' is already defined. - Evidence: else var body = document.getElementsByTagName( 'body')[0];
23. ISSUE: line 672 character 45: Script URL. - Evidence: link.href = "javascript:qui_openMenu();";
24. ISSUE: line 730 character 5: 'body' used out of scope. - Evidence: body.appendChild( indicator );
25. ISSUE: line 731 character 2: Unnecessary semicolon. - Evidence: };
26. ISSUE: line 736 character 2: Unnecessary semicolon. - Evidence: };
27. ISSUE: line 741 character 2: Unnecessary semicolon. - Evidence: };
28. ISSUE: line 746 character 2: Unnecessary semicolon. - Evidence: };
29. ISSUE: line 759 character 2: Unnecessary semicolon. - Evidence: };
30. ISSUE: line 761 character 28: The object literal notation {} is preferable. - Evidence: var buddy_list = new Object();
31. ISSUE: line 784 character 2: Unnecessary semicolon. - Evidence: };
32. ISSUE: line 796 character 27: ['status'] is better written in dot notation. - Evidence: buddy_list[friend]["status"] = local_status;
33. ISSUE: line 800 character 2: Unnecessary semicolon. - Evidence: };
34. ISSUE: line 808 character 13: eval can be harmful. - Evidence: eval( "var queryResult="+ d.responseText );
35. ISSUE: line 814 character 31: ['lastseen'] is better written in dot notation. - Evidence: buddy_list[friend]["lastseen"] = local_lastseen;
36. ISSUE: line 819 character 2: Unnecessary semicolon. - Evidence: };
37. ISSUE: line 822 character 43: ['status'] is better written in dot notation. - Evidence: var friend_status = buddy_list[friend]["status"];
38. ISSUE: line 823 character 45: ['lastseen'] is better written in dot notation. - Evidence: var friend_lastseen = buddy_list[friend]["lastseen"];
39. ISSUE: line 827 character 37: 'friend_lastseen_string' is already defined. - Evidence: else var friend_lastseen_string = "";
40. ISSUE: line 837 character 22: 'friend_lastseen_string' used out of scope. - Evidence: + 'D</a>)' + friend_lastseen_string;
41. ISSUE: line 839 character 23: ['HTMLobj'] is better written in dot notation. - Evidence: buddy_list[friend]["HTMLobj"] = menu_item;
42. ISSUE: line 842 character 2: Unnecessary semicolon. - Evidence: };
43. ISSUE: line 847 character 2: Unnecessary semicolon. - Evidence: };
44. ISSUE: line 852 character 2: Unnecessary semicolon. - Evidence: };
45. ISSUE: line 856 character 2: Unnecessary semicolon. - Evidence: };
46. ISSUE: line 879 character 2: Unnecessary semicolon. - Evidence: };

Your CommonsMaintenanceBot (talk) at 10:08, 11 April 2019 (UTC).

Quality Image Promotion

Your image has been reviewed and promoted Congratulations! Sunrise at TaniJubbar Lake.jpg, which was produced by you, was reviewed and has now been promoted to Quality Image status. If you would like to nominate another image, please do so at Quality images candidates. We also invite you to take part in the categorization of recently promoted quality images. Comments Good quality. --Berthold Werner 06:35, 9 April 2019 (UTC)

Your image has been reviewed and promoted Congratulations! Cool lights on the road.jpg, which was produced by you, was reviewed and has now been promoted to Quality Image status. If you would like to nominate another image, please do so at Quality images candidates. We also invite you to take part in the categorization of recently promoted quality images. Comments  Support Good quality. --Piotr Bart 17:38, 9 April 2019 (UTC)

Your image has been reviewed and promoted Congratulations! Crest of the Government of India and Indian armed forces.jpg, which was produced by you, was reviewed and has now been promoted to Quality Image status. If you would like to nominate another image, please do so at Quality images candidates. We also invite you to take part in the categorization of recently promoted quality images. Comments Good quality. --Cayambe 05:27, 9 April 2019 (UTC)

Your image has been reviewed and promoted Congratulations! Bunch of Green Grapes.jpg, which was produced by you, was reviewed and has now been promoted to Quality Image status. If you would like to nominate another image, please do so at Quality images candidates. We also invite you to take part in the categorization of recently promoted quality images. Comments  Support Good quality. --MB-one 09:20, 9 April 2019 (UTC)

Your image has been reviewed and promoted Congratulations! Wood stored as fuel for Bonfire in Jammu and Kashmir.jpg, which was produced by you, was reviewed and has now been promoted to Quality Image status. If you would like to nominate another image, please do so at Quality images candidates. We also invite you to take part in the categorization of recently promoted quality images. Comments Blown details. Looks like an oil painting in some points. As for a photograph I would decline. Maybe if it would even be made more artificial...I don't know. --Der Angemeldete 14:52, 28 March 2019 (UTC) What you don't know ? Do you want changes ? -- Eatcha 20:26, 3 April 2019 (UTC) Der Angemeldete, you didn't replied so I tried to fix it without knowing the problem, Is it okay now ? --Eatcha 14:55, 6 April 2019 (UTC)  Support Good quality. --Piotr Bart 19:13, 9 April 2019 (UTC)

--QICbot (talk) 05:34, 12 April 2019 (UTC)

Quality Image Promotion

Your image has been reviewed and promoted Congratulations! Tata TAMO Racemo.jpg, which was produced by you, was reviewed and has now been promoted to Quality Image status. If you would like to nominate another image, please do so at Quality images candidates. We also invite you to take part in the categorization of recently promoted quality images. Comments  Support Good quality. --Poco a poco 21:27, 10 April 2019 (UTC)

Your image has been reviewed and promoted Congratulations! Param Yodha sthal.jpg, which was produced by you, was reviewed and has now been promoted to Quality Image status. If you would like to nominate another image, please do so at Quality images candidates. We also invite you to take part in the categorization of recently promoted quality images. Comments Could you try to get that verical? --Ermell 13:06, 6 April 2019 (UTC) what do you mean? -- Eatcha 13:15, 6 April 2019 (UTC) The subject is perfectly upright. What is probably meant is to make the edges of the sign vertical and parallel. I have tried this in DXO and the structure looks twisted and distorted. I don't think there much that can be done; the perspective looks quite acceptable as it is. What could be done, however, is to cut down the space at the left of the picture, allowing a greater space on the right, the side into which the sign is 'looking'... a classic compositional ploy. Though it would need a change in aspect ratio. Acabashi 18:34, 6 April 2019 (UTC) @Acabashi & @Ermell I uploaded a new Image. which one do you think is better ? And please feel to revert If the previous version was better. Thanks for your reviews and suggestions. -- Eatcha 20:06, 6 April 2019 (UTC) CommentThe easiest way is to put the streetlights upright, which corresponds to reality. But here they're probably leaning outwards. If both sides of the sign are vertical and the horizontal side is also aligned it should look good.--Ermell 07:42, 7 April 2019 (UTC) Ermell, I edited the photo and streetlights are now at right angle from the ground, what do you think ? -- Eatcha 15:18, 7 April 2019 (UTC) Comment I don't think the streetlights are rectangular here. You should concentrate on the sign and align the sides exactly horizontally and vertically, then it will certainly look best.--Ermell 19:59, 7 April 2019 (UTC) Is this okay ? I think the street lights are some what tilted w.r.t the sign, but I still tried. -- Eatcha 14:30, 8 April 2019 (UTC)  Support Looks good now. Thanks. --Ermell 18:57, 10 April 2019 (UTC)

--QICbot (talk) 05:30, 13 April 2019 (UTC)

Quality Image Promotion

Your image has been reviewed and promoted Congratulations! Stacked Firewood.jpg, which was produced by you, was reviewed and has now been promoted to Quality Image status. If you would like to nominate another image, please do so at Quality images candidates. We also invite you to take part in the categorization of recently promoted quality images. Comments Good quality. --Seven Pandas 23:47, 11 April 2019 (UTC)

Your image has been reviewed and promoted Congratulations! Lion statue at Victoria Memorial, Kolkata 01.jpg, which was produced by you, was reviewed and has now been promoted to Quality Image status. If you would like to nominate another image, please do so at Quality images candidates. We also invite you to take part in the categorization of recently promoted quality images. Comments {{{3}}}

--QICbot (talk) 05:26, 14 April 2019 (UTC)

Code issues in User:Eatcha/common.js

Hi Eatcha, I am a bored bot (this is kind of a computer program) that is watching the recent changes and tapping buttons like I did now.

Curious about the reason? Possibly not but I will tell you anyway:

1. You edited User:Eatcha/common.js. Glad to see you coding in javascript! Have you ever considered becoming a MediaWiki hacker?
2. Though, that change appears to introduce 3 new jshint issues — the page's status is now having warnings. Note that invalid or ambiguous code often has unwanted side effects like breaking other tools for you. If you cannot find out how to fix it, I suggest blanking the page for now.
3. To help you understanding where the issues are, I have aggregated a report here and now. If you have questions, don't hesitate to ask users experienced in javascript writing for help. But do not ask the bot's operators (chronically overwrought) unless you suspect an error of mine. If you prefer not getting spammed by me, you can opt-out reports by adding {{ValidationOptOut|type=all}} to your user page or cmb-opt-out anywhere on your your global user page on Meta. Good luck at Wikimedia Commons and happy hacking!

1. ISSUE: line 14 character 15: 'i' is already defined. - Evidence: for(var i = 0; i < rightJS.Tags.length; i++){
2. ISSUE: line 74 character 375: Bad or unnecessary escaping. - Evidence: (function($,mw){'use strict';if(!mw.libs||mw.libs.threadSign)throw new Error('Initializing of threadSign stopped because it was already executed');var name='AutoSign',ns=mw.config.get('wgNamespaceNumber'),$textarea,$editform,minoredit,txtOld='',CmtE='',txtLen,lrLen,txtEndLen,txtOldEnd,reUser='',signTxt=[],txtOldL;var c=$.extend({usersignature:window.usersignature||'-- ~~\~~',sigAccessKey:'>',sigText:null},mw.config.get(['wgDBname','wgAction','wgContentLanguage','wgRelevantUserName','wgFormattedNamespaces','wgUserName','wgPageName','wgIsArticle']));var ts={version:'v1.93d',$sigBox:$(),$label:$(),onoff:$.noop,init:function(){if(ts.config instanceof Object)
3. ISSUE: line 100 character 294: Bad or unnecessary escaping. - Evidence: $textarea.textSelection('setSelection',{start:pos}).textSelection('scrollToCaretPosition').focus();return txt;},getUser:function(){var txt=txtOld;var strRe=new RegExp('\\[\\[(?:'+c.wgFormattedNamespaces[2]+'(?:in)?|'+c.wgFormattedNamespaces[3]+'|User(?:[ _]talk)?): ?([^\\]\\|[]+)(?:\\|([^\\]\[]+))?\\]\\]','ig');var topicPosters=txt.match(strRe)||[];var posterList=[];topicPosters=$.grep(topicPosters.reverse(),function(p,i){return $.inArray(p,topicPosters)===i;});var u=topicPosters.length,reUser,userDict={};while(u--)
4. ISSUE: line 268 character 26: 'j' is already defined. - Evidence: for(var j=globaluserinfo.groups.length-1; j>=0; j--){
5. ISSUE: line 270 character 30: 'i' is already defined. - Evidence: var i=document.createElement('IMG');
6. ISSUE: line 282 character 22: 'i' is already defined. - Evidence: var i=document.createElement('IMG');
7. ISSUE: line 289 character 18: 'i' is already defined. - Evidence: var i=document.createElement('SPAN');
8. ISSUE: line 360 character 18: 'u' is already defined. - Evidence: var u=a.match(/\/wiki\/User:([^\/]+)/);
9. ISSUE: line 365 character 18: 'u' is already defined. - Evidence: var u=['',document.getElementById('mw-log-user').defaultValue];
10. ISSUE: line 577 character 25: Use '!==' to compare with 'null'. - Evidence: if ((sectionRaw != null) && (sectionRaw[1].indexOf('T') < 0)){
11. ISSUE: line 621 character 38: Use '===' to compare with 'null'. - Evidence: if ((counter == null) || (typeof counter == 'undefined')){
12. ISSUE: line 630 character 54: Use '===' to compare with 'null'. - Evidence: if ((archiveNameRegMatch == null) || (typeof archiveNameRegMatch == 'undefined')){

Your CommonsMaintenanceBot (talk) at 06:42, 19 April 2019 (UTC).

Code issues in User:Eatcha/useridentifier.js

Hi Eatcha, I am a bored bot (this is kind of a computer program) that is watching the recent changes and tapping buttons like I did now.

Curious about the reason? Possibly not but I will tell you anyway:

1. You edited User:Eatcha/useridentifier.js. Glad to see you coding in javascript! Have you ever considered becoming a MediaWiki hacker?
2. Though, that change appears to introduce 5 new jshint issues — the page's status is now having ERRORS. Note that invalid or ambiguous code often has unwanted side effects like breaking other tools for you. If you cannot find out how to fix it, I suggest blanking the page for now.
3. To help you understanding where the issues are, I have aggregated a report here and now. If you have questions, don't hesitate to ask users experienced in javascript writing for help. But do not ask the bot's operators (chronically overwrought) unless you suspect an error of mine. If you prefer not getting spammed by me, you can opt-out reports by adding {{ValidationOptOut|type=all}} to your user page or cmb-opt-out anywhere on your your global user page on Meta. Good luck at Wikimedia Commons and happy hacking!

1. ISSUE: line 1 character 3: Expected a string and instead saw {. - Evidence: {{Speedydelete |1= Reason Here}}
2. ISSUE: line 1 character 4: Expected ':' and instead saw 'Speedydelete'. - Evidence: {{Speedydelete |1= Reason Here}}
3. ISSUE: line 1 character 17: Expected a JSON value. - Evidence: {{Speedydelete |1= Reason Here}}
4. ISSUE: line 1 character 17: Expected '}' and instead saw '|'. - Evidence: {{Speedydelete |1= Reason Here}}
5. ISSUE: line 1 character 18: Expected '(end)' and instead saw '1'. - Evidence: {{Speedydelete |1= Reason Here}}

Your CommonsMaintenanceBot (talk) at 18:06, 19 April 2019 (UTC).

Code issues in User:Eatcha/useridentifier.js

Hi Eatcha, I am a bored bot (this is kind of a computer program) that is watching the recent changes and tapping buttons like I did now.

Curious about the reason? Possibly not but I will tell you anyway:

1. You edited User:Eatcha/useridentifier.js. Glad to see you coding in javascript! Have you ever considered becoming a MediaWiki hacker?
2. Though, that change appears to introduce 1 new esprima issue — the page's status is now having ERRORS. Note that invalid or ambiguous code often has unwanted side effects like breaking other tools for you. If you cannot find out how to fix it, I suggest blanking the page for now.
3. To help you understanding where the issues are, I have aggregated a report here and now. If you have questions, don't hesitate to ask users experienced in javascript writing for help. But do not ask the bot's operators (chronically overwrought) unless you suspect an error of mine. If you prefer not getting spammed by me, you can opt-out reports by adding {{ValidationOptOut|type=all}} to your user page or cmb-opt-out anywhere on your your global user page on Meta. Good luck at Wikimedia Commons and happy hacking!

1. ERROR: Cannot parse line 1 column 19: Invalid left-hand side in assignment

Your CommonsMaintenanceBot (talk) at 18:06, 19 April 2019 (UTC).

Code issues in User:Eatcha/common.css

Hi Eatcha, I am a bored bot (this is kind of a computer program) that is watching the recent changes and tapping buttons like I did now.

Curious about the reason? Possibly not but I will tell you anyway:

1. You edited User:Eatcha/common.css. Glad to see you coding in css! Have you ever considered becoming a MediaWiki hacker?
2. Though, that change appears to introduce 2 new prettyCss issues — the page's status is now having warnings. Note that invalid or ambiguous code often has unwanted side effects like breaking other tools for you. If you cannot find out how to fix it, I suggest blanking the page for now.
3. To help you understanding where the issues are, I have aggregated a report here and now. If you have questions, don't hesitate to ask users experienced in css writing for help. But do not ask the bot's operators (chronically overwrought) unless you suspect an error of mine. If you prefer not getting spammed by me, you can opt-out reports by adding {{ValidationOptOut|type=all}} to your user page or cmb-opt-out anywhere on your your global user page on Meta. Good luck at Wikimedia Commons and happy hacking!

1. WARNING: suggest-relative-unit:px: line 33 char number 11 - Evidence: 20px
2. WARNING: suggest-relative-unit:px: line 41 char number 13 - Evidence: 55px
3. WARNING: suggest-relative-unit:px: line 42 char number 12 - Evidence: 18px

Your CommonsMaintenanceBot (talk) at 18:30, 19 April 2019 (UTC).

Query regarding your recent deletion taggings

How is this file a derivative work? In fact, the file uploaded at the Commons is the oldest & the highest resolution version available on the net. And it is released under a proper license by its author Nivisharma845.

I haven't properly looked at your other similar recent taggings, but those files also don't seem like derivative works, e.g. how are the files like [1], [2], [3], etc. derivative works? - NitinMlk (talk) 14:50, 21 April 2019 (UTC)

NitinMlk, where is the EXIF of that file ? Certainly that is a derivative work. Please upload the full resolution original file with EXIF data. Regards, -- 🇪🅰〒ℂ🇭🅰- 💬 15:42, 21 April 2019 (UTC)

File:WhatsApp-Image-20160611 (1).jpg, it is copvio from https://twitter.com/iamayeshanazir/status/740582332432846849?lang=en . It will be speedily deleted now. Regards, -- 🇪🅰〒ℂ🇭🅰- 💬 15:47, 21 April 2019 (UTC)

File:Maan2.JPG, this has a black frame so indeed a derivative work + Oos too, I should have marked it with speedy. -- 🇪🅰〒ℂ🇭🅰- 💬 15:53, 21 April 2019 (UTC)

I didn't upload any one of these files. Normally inexperienced/newbie uploaders tweak their pics before uploading them here, which I guess affects their EXIF details, but that doesn't make them derivative work. Anyway, thanks for responding, and this time you tagged at least two of them correctly. - NitinMlk (talk) 15:58, 21 April 2019 (UTC)

File:Ayesha Nazir Jatt.jpg was uploaded by User:RamishAsgharPTI who also uploaded another image of this same female-homo-sapien named Ayesha Nazir which is a copyvio from twitter see File:Ayesha Nazir Jatt Meeting with Imran Khan.jpg. This user is not a newbie who somehow deleted the EXIF but an offender. -- 🇪🅰〒ℂ🇭🅰- 💬 17:17, 21 April 2019 (UTC)

Source of derivative work is not properly indicated: File:Malala Yousafzai.svg

This file may be deleted.

A file that you have uploaded to Wikimedia Commons, File:Malala Yousafzai.svg, is a derivative work, containing an "image within an image". Examples of such works would include a photograph of a sculpture, a scan of a magazine cover, or a map that has been altered from the original. In each of these cases, the rights of the creator of the original must be considered, as well as those of the creator of the derivative work. While the description page states who made this derivative work, it currently doesn't specify who created the original work, so the overall copyright status is unclear. If you did not create the original work depicted in this image, you will need to specify the owner of the copyright. Please edit the file description and add the missing information, or the file may be deleted. If you created the original content yourself, enter this information as the source. If someone else created the content, the source should be the address to the web page where you found it, the name and ISBN of the book you scanned it from, or similar. You should also name the author, provide verifiable information to show that the content is in the public domain or has been published under a free license by its author, and add an appropriate template identifying the public domain or licensing status, if you have not already done so. Please add the required information for this and other files you have uploaded before adding more files. If you need assistance, please ask at the help desk. Thank you!

 

Yann (talk) 04:24, 22 April 2019 (UTC)

File tagging File:Katie Bouman.svg

This media was probably deleted.

Thanks for uploading File:Katie Bouman.svg. This media is missing permission information. A source is given, but there is no proof that the author or copyright holder agreed to license the file under the given license. Please provide a link to an appropriate webpage with license information, or ask the author or copyright holder to send an email with copy of a written permission to VRT (permissions-commons@wikimedia.org). You may still be required to go through this procedure even if you are the author yourself; please see Commons:But it's my own work! for more details. After you emailed permission, you may replace the {{No permission since}} tag with {{subst:PP}} on file description page. Alternatively, you may click on "Challenge speedy deletion" below the tag if you wish to provide an argument why evidence of permission is not necessary in this case. Please see this page for more information on how to confirm permission, or if you would like to understand why we ask for permission when uploading work that is not your own, or work which has been previously published (regardless of whether it is your own). The file probably has been deleted. If you sent a permission, try to send it again after 14 days. Do not re-upload. When the VRT-member processes your mail, the file can be undeleted. Additionally you can request undeletion here, providing a link to the File-page on Commons where it was uploaded ([[:File:Katie Bouman.svg]]) and the above demanded information in your request.

 

Yann (talk) 04:26, 22 April 2019 (UTC)

@Yann, what If I ask Katie Bouman to send an OTRS ? or should I ask her to send a self-portrait + send permission to OTRS ? I think the Image I used was not her work, so I guess the second option would be better. And the SVG of malala yousafzai is created using a public domain Image, what to do ? Best, -- 🇪🅰〒ℂ🇭🅰- 💬 06:31, 22 April 2019 (UTC)

Hi,

Yes, the source has to be free, so you need a permission from the copyright holder of the picture.

For Malala Yousafzai, your drawing doesn't seem to look like the source. I think you used File:Malala Yousafzai Azam.jpg rather than the one you mention. Regards, Yann (talk) 06:41, 22 April 2019 (UTC)

Uploads

Hi, please make sure to add a license template when you upload a file. Jcb (talk) 18:12, 25 April 2019 (UTC)

Jcb, thanks for notifying me, I just added license template to all of my uploads. -- 🇪🅰〒ℂ🇭🅰- 💬 18:33, 25 April 2019 (UTC)

Thanks! Jcb (talk) 20:34, 25 April 2019 (UTC)

Blue?

If you increase the yellow, temp and decrease the blue/green slightly it will become a QI. Compare the text in these two images, the other one looks more golden

This looks golden, I just increased the yellow using lightroom and It's a QI now

Thanks for reviewing my QI nominations. I am fairly new to photography, especially the post-processing stuff. Can you explain what do you mean by "pull down the blue", and how can I work on it? KCVelaga (talk · mail) 05:55, 27 April 2019 (UTC)

Hi KCVelaga,
I should have avoided using jargon, Sorry for that. Your images of statues which are made of bronze/copper looks blueish(maybe because of the sky) and by decreasing the blue, increasing the temperature and slight increase in yellow can make them look more natural. You can use Adobe Lightroom for that, If you have the RAW files these images can become very good QIs. You can compare this between File:CQHM Abdul Hamid statue at Param Yodha Sthal Delhi.jpg and File:Subedar Joginder Singh statue at Param Yodha Sthal Delhi.jpg, the first one is not a QI only because of its bad lighting which can be fixed if you have the RAW files.

If you wish you can learn these things from YouTube. Here is a 8 minute tutorial that might help you https://www.youtube.com/watch?v=0lCPsiCxShU

Regards, 🇪🅰〒ℂ🇭🅰- 💬 14:34, 27 April 2019 (UTC)

@Eatcha: Thanks for your elaborate reply, and guiding me through the process. I will definitely go through the tutorial and do some practice. KCVelaga (talk · mail) 16:41, 27 April 2019 (UTC)

FP Promotion

★ This image has been promoted to Featured picture! ★ The image File:Sunrise at TaniJubbar Lake.jpg, that you nominated on Commons:Featured picture candidates/File:Sunrise at TaniJubbar Lake.jpg has been promoted. Thank you for your contribution. If you would like to nominate another image, please do so.

/FPCBot (talk) 21:03, 27 April 2019 (UTC)

FP Promotion

★ This image has been promoted to Featured picture! ★ The image File:Joy & Heron - Animated CGI Spot by Passion Pictures.webm, that you nominated on Commons:Featured picture candidates/File:Joy & Heron - Animated CGI Spot by Passion Pictures.webm has been promoted. Thank you for your contribution. If you would like to nominate another image, please do so.

/FPCBot (talk) 05:03, 1 May 2019 (UTC)

Thank you

I will see this video this summer, and I'll try to modify some of my pictures. Thank you for your words.--Drow male (talk) 23:13, 4 May 2019 (UTC)

Reviewing quality images

Hi Eatcha! Can you please be more considerate when reviewing images for QI mark? From what I've seen, a lot of images that you have reviewed as "Good quality" ended up in discussions and other revieweres didn't let them pass. Some of the users even questioned how it's possible that such images were marked as "Good quality" pictures. I'd politely suggest that you have a look at Commons:Image guidelines and maybe just nominate pictures first so you can have a better idea where the QI mark sits. It's often more about technical quality than anything else. Also, I don't think it's a good idea to try to "fix" other users image when, in fact, you might accidentally make them worse. All the best, --Podzemnik (talk) 01:13, 5 May 2019 (UTC)

@Podzemnik, Okay I'll only nominate images at QIC for the next 6 months, no voting and no editing.
Thanks -- 🇪A〒ℂ🇭A  💬 15:03, 5 May 2019 (UTC)

Hi Eatcha, I hope I didn't discourage you :) Your work is great and I enjoy it, it's just the QI mark might be tricky to grasp from the beginning. To me personally, it helped from the beginning that I only nominated images. Especially those pictures that were declined helped me to improve and understand what is expected for a QI mark. Regards from New Zealand, --Podzemnik (talk) 19:34, 5 May 2019 (UTC)

Quality Image Promotion

Your image has been reviewed and promoted Congratulations! Hadres Kellergasse.jpg, which was produced by you, was reviewed and has now been promoted to Quality Image status. If you would like to nominate another image, please do so at Quality images candidates. We also invite you to take part in the categorization of recently promoted quality images. Comments perspective correction required --Eatcha 10:19, 3 May 2019 (UTC) ??? perspective is OK --Manfred Kuzel 16:40, 3 May 2019 (UTC)  Support Not sure about the perspective but certainly a very good picture. --Eatcha 18:40, 4 May 2019 (UTC)

--QICbot (talk) 05:28, 7 May 2019 (UTC)

File:Dave Marcus profile pic (cropped).png

File:Dave Marcus profile pic (cropped).png has been marked as a possible copyright violation. Wikimedia Commons only accepts free content—that is, images and other media files that can be used by anyone, for any purpose. Traditional copyright law does not grant these freedoms, and unless noted otherwise, everything you find on the web is copyrighted and not permitted here. For details on what is acceptable, please read Commons:Licensing. You may also find Commons:Copyright rules useful, or you can ask questions about Commons policies at the Commons:Help desk. If you are the copyright holder and the creator of the file, please read Commons:But it's my own work! for tips on how to provide evidence of that. The file you added has been deleted. If you have written permission from the copyright holder, please have them send us a free license release via COM:VRT. If you believe that the deletion was not in accordance with policy, you may request undeletion. (It is not necessary to request undeletion if using VRT; the file will be automatically restored at the conclusion of the process.) This file is a copyright violation for the following reason: https://ca.finance.yahoo.com/news/meet-team-behind-facebook-messengers-plans-get-next-billion-users-143718983.html Warning: Wikimedia Commons takes copyright violations very seriously and persistent violators will be blocked from editing.

 

Patrick Rogel (talk) 22:46, 7 May 2019 (UTC)

It's not my upload, I just cropped it from File:Dave_Marcus_profile_pic.png. -- 🇪A〒ℂ🇭A  💬 05:06, 8 May 2019 (UTC)