Autopatrol given edit

 

Hello. I just wanted to let you know that I have granted autopatrol rights to your account; the reason for this is that I believe you are sufficiently trustworthy and experienced to have your contributions automatically marked as "reviewed". This has no effect on your editing, it is simply intended to make it easier for users that are monitoring Recent changes or Recent uploads to find unproductive edits amidst the productive ones like yours. In addition, the Flickr upload feature and an increased number of batch-uploads in UploadWizard, uploading of freely licensed MP3 files, overwriting files uploaded by others and an increased limit for page renames per minute are now available to you. Thank you. INeverCry 20:49, 16 February 2013 (UTC)Reply

Thanks. — SMcCandlish [talk] [cont] ‹(-¿-)› 08:11, 5 March 2013 (UTC)Reply

Welcome, Dear Filemover! edit

العربيَّة  Deutsch  español  English  français  português  русский  українська  বাংলা  മലയാളം  한국어  日本語  Tiếng Việt  中文(中国大陆)‎  中文(台灣)‎  中文(简体)‎  中文(繁體)‎  +/−


 

Hi SMcCandlish, you're now a filemover. When moving files please respect the following advice:

  • Use the CommonsDelinker link in the {{Rename}} template to order a bot to replace all ocurrences of the old title with the new one. Or, if there was no rename-request, please use the Move & Replace-tab.
  • Please leave a redirect behind unless you have a valid reason not to do so. Other projects, including those using InstantCommons, might be using the file even though they don't show up in the global usage. Deleting the redirects would break their file references. Please see this section of the file rename guideline for more information.
  • Please know and follow the file rename guidelines.

Green Giant (talk) 10:31, 8 July 2018 (UTC)Reply

@Green Giant: Thank you. I'll carefully re-review the regs (and pay more attention to language matters!). — SMcCandlish [talk] [cont] ‹(-¿-)› 20:17, 8 July 2018 (UTC)Reply

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:36, 7 November 2019 (UTC)Reply