User talk:Althair/2019 - Wikimedia Commons


1 person in discussion

Article Images

This message was added automatically by MifterBot (Talk • Contribs • Owner), if you need some help about it please read the text above again and follow the links in it, if you still need help ask at the   → Commons:Help desk in any language you like to use. --MifterBot (Talk • Contribs • Owner) 01:05, 17 January 2019 (UTC)Reply

 

Dear Althair,

You are receiving this message because we noticed that you voted in R1 of the 2018 Picture of the Year contest, but not yet in the second round. Wikimedia users are invited to vote for their favorite images featured on Commons during the last year (2018) to produce a single Picture of the Year.

Hundreds of images that have been rated Featured Pictures by the international Wikimedia Commons community in the past year were entered in this competition. These images include professional animal and plant shots, breathtaking panoramas and skylines, restorations of historical images, photographs portraying the world's best architecture, impressive human portraits, and so much more.

There are two total rounds of voting. In the first round, you voted for as many images as you liked.

In the final (and current) round, you may vote for a maximum of three images. The image with the most votes will become the Picture of the Year 2018.

Round 2 will end 17 March 2019, 23:59:59.

Click here to vote now!

Thanks,
the Wikimedia Commons Picture of the Year committee 18:04, 16 March 2019 (UTC)

¡Enhorabuena por la recuperación del flag! Strakhov (talk) 19:41, 20 March 2019 (UTC)Reply

Kzl55 (talk) 09:43, 30 March 2019 (UTC)Reply

And also:

 This file has not been uploaded completely due to a software problem (see phab:T190988). Please re-upload it by clicking on "Upload a new version of this file" link below the section titled "File history". Then, please remove the {{Incomplete upload}} tag from the file description page.
At least 30 days after the addition of the tag, volunteers will assess the quality of image and may crop it if being in use or deemed useful. Otherwise, the image may be deleted summarily (CSD#F7).

4nn1l2 (talk) 12:09, 21 June 2019 (UTC)Reply

Hi MONUMENTA, 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:MONUMENTA/common.js. Glad to see you coding in javascript! Have you ever considered becoming a MediaWiki hacker?
  2. Though, that change appears to introduce 22 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 36 character 1: Unbegun comment. - Evidence: */
  2. ISSUE: line 445 character 39: Use '===' to compare with 'null'. - Evidence: if ( text == null ) { return ''; }
  3. ISSUE: line 748 character 52: Use '!==' to compare with 'null'. - Evidence: if ( self.note.content != null ) {
  4. ISSUE: line 1030 character 116: Don't make functions within a loop. - Evidence: !Array.exists( this.annotations, function ( note ) { return note.model.id == id; } )
  5. ISSUE: line 1046 character 65: Use '===' to compare with '0'. - Evidence: if ( !this.main_div || this.main_div.length == 0 ) { this.main_div = null; } else { this.main_div = this.main_div[ 0 ]; }
  6. ISSUE: line 1093 character 23: Don't make functions within a loop. - Evidence: } );
  7. ISSUE: line 1241 character 29: 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 intersect_rectangles( a, b ) {
  8. ISSUE: line 1271 character 71: Use '!==' to compare with 'null'. - Evidence: display !== 'none' && display != null &&
  9. ISSUE: line 1413 character 55: Use '!==' to compare with 'null'. - Evidence: if ( !config || ImageAnnotator_config != null ) { return; }
  10. ISSUE: line 1429 character 62: Use '!==' to compare with 'null'. - Evidence: self.haveAjax = ( LAPI.Ajax.getRequest() != null );
  11. ISSUE: line 1877 character 29: 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 get_size( info ) {
  12. ISSUE: line 1889 character 48: Use '!==' to compare with '0'. - Evidence: if ( i != 0 || !self.may_edit || !info.protection || mw.config.get( 'wgNamespaceNumber' ) != 6 ) { return; }
  13. ISSUE: line 2015 character 40: 'item' is already defined. - Evidence: for ( var item in self.defaults ) {
  14. ISSUE: line 2122 character 60: Use '!==' to compare with 'null'. - Evidence: IA.haveAjax = ( LAPI.Ajax.getRequest() != null );
  15. ISSUE: line 2242 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 track( evt ) {
  16. ISSUE: line 2269 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 pause( evt ) {
  17. ISSUE: line 2275 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 resume( evt ) {
  18. ISSUE: line 2285 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 stop_tracking( evt ) {
  19. ISSUE: line 2332 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 start_tracking( evt ) {
  20. ISSUE: line 2365 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 add_new( evt ) {
  21. ISSUE: line 2631 character 31: Don't make functions within a loop. - Evidence: } );
  22. ISSUE: line 3084 character 66: Use '!==' to compare with 'null'. - Evidence: self.haveAjax = ( LAPI.Ajax.getRequest() != null );

Your CommonsMaintenanceBot (talk) at 23:12, 18 August 2019 (UTC).Reply

Hi MONUMENTA, 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:MONUMENTA/common.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 36 column 1: Unexpected token *

Your CommonsMaintenanceBot (talk) at 23:12, 18 August 2019 (UTC).Reply

Magog the Ogre (talk) (contribs) 00:57, 28 August 2019 (UTC)Reply

Magog the Ogre (talk) (contribs) 01:03, 28 August 2019 (UTC)Reply

Magog the Ogre (talk) (contribs) 01:38, 28 August 2019 (UTC)Reply

 

A community discussion has been closed where the consensus was to grant all file movers the suppressredirect user right. This will allow file movers to not leave behind a redirect when moving files and instead automatically have the original file name deleted. Policy never requires you to suppress the redirect, suppression of redirects is entirely optional.

Possible acceptable uses of this ability:

  • To move recently uploaded files with an obvious error in the file name where that error would not be a reasonable redirect. For example: moving "Sheep in a tree.jpg" to "Squirrel in a tree.jpg" when the image does in fact depict a squirrel.
  • To perform file name swaps.
  • When the original file name contains vandalism. (File renaming criterion #5)

Please note, this ability should be used only in certain circumstances and only if you are absolutely sure that it is not going to break the display of the file on any project. Redirects should never be suppressed if the file is in use on any project. When in doubt, leave a redirect. If you forget to suppress the redirect in case of file name vandalism or you are not fully certain if the original file name is actually vandalism, leave a redirect and tag the redirect for speedy deletion per G2.

The malicious or reckless breaking of file links via the suppressredirect user right is considered an abuse of the file mover right and is grounds for immediate revocation of that right. This message serves as both a notice that you have this right and as an official warning. Questions regarding this right should be directed to administrators. --Majora (talk) 21:36, 7 November 2019 (UTC)Reply