/Archive

pics edit

Hi can u help me, so I can not use a photo of celeb from internet? I have to take a photo of the celeb myself and then uplaod it here so that I can use it in the celeb's wiki page? — Preceding unsigned comment added by Maengss (talk • contribs) 07:54, 16 September 2018 (UTC)Reply

Hi Maengss, you cannot upload a copyrighted image unless the creator has released it under a free license - please see COM:L. Indeed, you could also take a photo of the celebrity yourself, release it under a free license (e.g. CC BY-SA 4.0), and upload it to commons. Thine Antique Pen (talk) 13:49, 21 October 2018 (UTC)Reply

Renaming files edit

File:(No) = 福岡県 三池港 【 Pictures taken in Japan 】.jpg is not a name following the guidelines, because it's not more informative than the previous name. Please take care when accepting renaming requests. --Ruthven (msg) 18:07, 3 November 2018 (UTC)Reply

Hi Ruthven. I thought that replacing "IMG 4900" with "福岡県 三池港" made the name more informative than before, and combined with "Unless there is a compelling reason not to, uploader requests should be honored" in COM:RENAME, thought that it was okay to move the file. Please let me know if I'm missing something; I'd be happy to change how I consider rename requests in the future. Thanks, Thine Antique Pen (talk) 18:54, 3 November 2018 (UTC)Reply
Sure, better than before, but all the rest of the filename doesn't mean anything. The file should be named something like Miike Port – Fukuoka Prefecture – 福岡県 三池港.jpg. --Ruthven (msg) 19:24, 3 November 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

 
File:1336690359 373311342 2-Fotos-de--VENDO-BILLETE-DE-UN-PESO-DE-1940.jpg has been marked for speedy deletion. (Reason: Broken redirect (迷子のリダイレクト))

Why not upload a picture of a plant, animal, or anything else which fits into our scope. You can contribute any media type you want, including but not limited to images, videos, music, and 3D models. Start uploading now! If you don't have anything to upload at the moment, why not take a look at our best images or best videos, sounds and 3D models. If you have any doubts/questions don't hesitate to visit our help desk.

User who nominated the file for deletion (Nominator) : MathXplore.

I'm a computer program; please don't ask me questions but ask the user who nominated your file(s) for deletion or at our Help Desk. //Deletion Notification Bot 2 (talk) 06:16, 7 December 2022 (UTC)Reply