User talk:Dan Koehl/2019
.jpg){kind=link}
Code issues in User:Dan Koehl/common.js
[edit]Hi Dan Koehl, 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:
- You edited User:Dan Koehl/common.js. Glad to see you coding in javascript! Have you ever considered becoming a MediaWiki hacker?
- Though, that change appears to introduce 4 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.
- 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!
- ISSUE:
line 1 character 2: Expected a string and instead saw {. - Evidence:{{{}}}// [[File:Krinkle_RTRC.js]] - ISSUE:
line 1 character 3: Expected ':' and instead saw '{'. - Evidence:{{{}}}// [[File:Krinkle_RTRC.js]] - ISSUE:
line 1 character 4: Expected a JSON value. - Evidence:{{{}}}// [[File:Krinkle_RTRC.js]] - ISSUE:
line 1 character 5: Expected '(end)' and instead saw '}'. - Evidence:{{{}}}// [[File:Krinkle_RTRC.js]]
Your CommonsMaintenanceBot (talk) at 02:38, 12 February 2019 (UTC).
 |
File:ConestogaValleyArial.JPG 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.)
|
— Huntster (t @ c) 05:37, 2 August 2019 (UTC)
.jpg&action=edit&redlink=1){kind=link}
|
File:Hillsborough High School (New Jersey).jpg 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.)
|
— Huntster (t @ c) 05:37, 2 August 2019 (UTC)
.jpg){kind=link}
Important message for file movers
[edit]
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:35, 7 November 2019 (UTC)