User talk:Gnash
Our first steps tour and our frequently asked questions will help you a lot after registration. They explain how to customize the interface (for example the language), how to upload files and our basic licensing policy (Wikimedia Commons only accepts free content). You don't need technical skills in order to contribute here. Be bold when contributing and assume good faith when interacting with others. This is a wiki. More information is available at the community portal. You may ask questions at the help desk, village pump or on IRC channel #wikimedia-commons (webchat). You can also contact an administrator on their talk page. If you have a specific copyright question, ask at the copyright village pump. |
|
-- 21:29, 24 April 2011 (UTC)
This message was added automatically by Nikbot, 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. --Nikbot
File:AndroidKitKatHomeScreen.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.) Warning: Wikimedia Commons takes copyright violations very seriously and persistent violators will be blocked from editing.
|
Ellin Beltz (talk) 17:31, 9 April 2015 (UTC)
File:AndroidKitKatHomeScreen.jpg has been listed at Commons:Deletion requests so that the community can discuss whether it should be kept or not. We would appreciate it if you could go to voice your opinion about this at its entry.
If you created this file, please note that the fact that it has been proposed for deletion does not necessarily mean that we do not value your kind contribution. It simply means that one person believes that there is some specific problem with it, such as a copyright issue. Please see Commons:But it's my own work! for a guide on how to address these issues. |
Amitie 10g (talk) 18:54, 9 April 2015 (UTC)
Overwrite[edit]
Hello! I've seen you've overwritten my file File:Münster, LVM -- 2017 -- 6359.jpg. I've reverted your changes. Please respect COM:OVERWRITE. Take care, the image has a special status (Quality image)! I only licensed the image as I uploaded it. And if there is any optimization, I'll will do with my RAW file. Just ask me instead of uploading and overwrite an image where you are not the author. Any other change: Please upload the image with a new name as derivated image. Thank you. --XRay talk 11:28, 2 April 2017 (UTC)
- @XRay: Hi. Lossless image optimization is often performed by bots and sometimes humans on MediaWiki to reduce load. Please understand that no information is lost, only quantization tables and Huffman trees are rearranged in a JPEG file to save space. Quality images are the ones which profit the most from these optimizations for they're usually popular and large image files. While the amount of devotion you put in your images is welcomed, this can not be done upstream as it is specific to compressed file formats, but keep in mind though no information is altered by reorganizing the JPEG data. I will not revert to version as of 02 April 2017 unless we reach consensus and I will happily work with you on reaching that goal.
- Gamer-Actu (talk) 11:50, 2 April 2017 (UTC)
- I'll check the optimization. But you should really don't overwrite images. We have the rules COM:OVERWRITE and I do not accept minor changes too. And: Your optimization adds a new file in the history. The file needs additional space. An optimization of only a few byte is not good enough. I am modifing only at the source, usually a RAW file. I think there is other work to so than overwriting files. --XRay talk 13:03, 2 April 2017 (UTC)
- @XRay: I did overlook that, indeed. When I said "reducing load" I didn't mean that files will take less space but that the network will be put under less stress.
- If you really truly don't trust my words when I'm telling you that data hasn't been altered at all you could just download both versions and export them to any lossless compression image file format and note that they are identical; I actually just exported the two images to PNG using Paint and both their size and their checksums were identical. What more proof would one need.
- Also if I'm being honest with you, I am not sure I understand the meaning of your two last sentences.
- Gamer-Actu (talk) 13:28, 2 April 2017 (UTC)
- Also small footprint, to make sure there is no misunderstanding; I've seen you added "Don't change the EXIF data." to your revert commits.
- As I stated earlier the content of the file has been left completely untouched and this includes all the metadata. So, as a matter of fact, I did not change the EXIF data.
- Gamer-Actu (talk) 13:38, 2 April 2017 (UTC)
- Sorry, writing in english is not the best way for me. (BTW: You should create your user page with babel information.) I trust your words and I really know the difference of load and space. But I still don't accept overwriting. May be others see this and overwrite images too, it isn't exemplary. Next upload with my workflow will overwrite changes by third party. The optimum is not everything. And the creation of the thumbnails is not affected by your minor improvement of the file size. And the last two sentences. My workflow starts with a RAW file. All modifications should be done beginning with this RAW data. And overwriting with a modified JPG file is never a good way. If there is a better way to improve the file size, it should be a part of my workflow. If you think you need a smaller file, upload the file as derivate with a new name and add your name aus author. These is a part of the license condition. But IMO this makes no sense. --XRay talk 13:56, 2 April 2017 (UTC)
- @XRay: Yeah, I get all that. Not that I agree with all of it but I do see your point.
- And overwriting with a modified JPG file is never a good way., I fear that you don't want to acknowledge that I am not reencoding the image again. I do well know that modifying a lossy source is a terrible idea but this is not what has been done here. Maybe you should check the description of some of the tools I've used to get a better sense of what is actually being done: JPEGOPTIM MAN, jpegtran.
- Anyway, I'll let you decide if you want to revert back to my changes on your images. No matter what, I invite you to optimize all your pictures before uploading them as of now. While it may not seem like that big of a deal, a few megabytes saved here and there can make things quite faster to retrieve.
- Gamer-Actu (talk) 14:27, 2 April 2017 (UTC)
- FYI: I've checked the modified file. The segments were reordered and the format switched from baseline to progressive. You should not progressive JPEG's (seen at segment SOF2): Help:JPEG#Progressive_JPEGs --XRay talk 09:36, 3 April 2017 (UTC)
- That's exactly what I told you I did…
- Lol, you should have read that link you gave me about progressive JPEGs with more caution, I've already stumbled upon it long ago: Phabricator. It's just one single programmer that didn't want to fix a bug in MediaWiki's handling of progressive JPEGs (that has been fixed since then), everyone else has been taken aback seing how ridicule of an idea this was.
- Anyway, really sad to see how you react seeing people improving on your work, that's at the heart of Wikimedia. I'm surprised it didn't happen to you before. You're missing out on so much.
- Also, now that you know it exists, you should really do that kind of optimization beforehand.
- Gamer-Actu (talk) 10:49, 3 April 2017 (UTC)
- For the record, Tim Starling is not "just one single programmer". He has been working in MediaWiki for the last 15 years, contributed thousands of changes to MediaWiki, both fixing bugs and developing big, complex features. It's not "that [he] didn't want to fix a bug in MediaWiki's". Thumbnailing progressive JPEGs need more memory, as the full image needs to be loaded in memory. That's an issue intrinsic to the format and the way ImageMagick works, not a MediaWiki bug. As Tim clearly stated. At most, you could consider it a task for the wikimedia administrators that they should be dedicating X more GB of server RAM to thumbnailing (no, infinite is not an option). The bug was "closed" indicating that it won't be done, not "fixed". Later changes may mean that it is now possible to thumbnail such files, but that doesn't change the underlying problem of progressive thumbnails (unless you have evidence that the current thumbnailer in use is now capable of not loading the full image…). Platonides (talk) 14:53, 4 February 2018 (UTC)
File:TWDC Logo.svg has been listed at Commons:Deletion requests so that the community can discuss whether it should be kept or not. We would appreciate it if you could go to voice your opinion about this at its entry.
If you created this file, please note that the fact that it has been proposed for deletion does not necessarily mean that we do not value your kind contribution. It simply means that one person believes that there is some specific problem with it, such as a copyright issue. Please see Commons:But it's my own work! for a guide on how to address these issues. |
Ups and Downs (↕) 05:49, 17 January 2018 (UTC)
COM:AN[edit]
— Jeff G. ツ please ping or talk to me 06:05, 4 February 2018 (UTC)
File tagging File:Facebook New Logo (2015).svg[edit]
This media may be deleted.
|
Thanks for uploading File:Facebook New Logo (2015).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). Warning: unless the permission information is given, the file may be deleted after seven days. Thank you. |
StSl (talk) 12:45, 18 April 2018 (UTC)
Image optimizer tools[edit]
FYI, policy is in the making to ban image optimizer overwrites. - Alexis Jazz ping plz 01:58, 29 July 2019 (UTC)
Notification about possible deletion[edit]
Some contents have been listed at Commons:Deletion requests so that the community can discuss whether they should be kept or not. We would appreciate it if you could go to voice your opinion about this at their entry.
If you created these pages, please note that the fact that they have been proposed for deletion does not necessarily mean that we do not value your kind contribution. It simply means that one person believes that there is some specific problem with them, such as a copyright issue. Please see Commons:But it's my own work! for a guide on how to address these issues. |
Affected: