User talk:IagoQnsi/Archive 2

Archive 1

Archive 2

Archive 3

Your unilateral actions on Category:Heterosexuality symbols

It's a little unfortunate that you charged ahead and created Category:Heterosexuality symbols unilaterally without consulting with anybody or asking for any advice, especially since I'm far from persuaded that your knowledge of such matters is deep. To start with "Category:Symbols of heterosexuality" would have probably been a better name... AnonMoos (talk) 16:44, 17 October 2018 (UTC)

Sorry, I just saw that Heterosexuality contained an awful lot of symbols and thought it would be easier to navigate if they were subcategorized. I'm happy to discuss this and potentially undo some of what I did; I didn't start a discussion because it didn't seem like it was warranted (it's pretty typical for categories like Heterosexuality to have a "symbols" category, albeit often inside an "in art" category). You're right about the category name, and I've gone ahead and changed it to "Symbols of heterosexuality". --IagoQnsi (talk) 17:04, 17 October 2018 (UTC)

Well, at some point I'm going to have to go through all the subcategories and check on them, and it's something that I'm not looking forward to doing, or that I really have time for right at the moment (I've already put off doing it for close to a week). I already have reason to doubt your understanding of the word "interlinked" (see the immediately preceding subsection of this talk page). AnonMoos (talk) 15:05, 22 October 2018 (UTC)

File:PEGI Sex.svg

This is exactly what I was afraid of. Two circles cannot be "interlinked" unless there is some over-and-under action, resulting in a mathematical Hopf link. Please look at various relevant Commons categories and Wikipedia articles, such as "Celtic knot", "Category:Knots in art and decoration", "Croatian interlace" etc. etc.
I'm really not looking forward to cleaning up the mess you seem to have created... AnonMoos (talk) 15:39, 22 October 2018 (UTC)

@AnonMoos: As I put in the description, Category:Interlinked Venus and Mars symbols is for symbols that are interlinked or overlapping. It just seemed impractical to include that in the title name. If you have an idea for a better name for a category that includes both overlapping and interlinking symbols, I welcome your suggestion --IagoQnsi (talk) 17:06, 23 October 2018 (UTC)

That's the kind of thing I meant when I referred to the inadvisability of doing things unilaterally without any consultation above. Someone who looks at Category:Interlinked Venus and Mars symbols (one link) will not see your note on Category:Interlinked Venus and Mars symbols (that's what happened to me), and in any case, the word "interlinked" has a highly-precise and specific technical meaning which can't really be blurred in the way that you want to blur it. This means that you've kind of created a mess, which I'm not looking forward to trying to clean up (or setting aside the time to clean it up, for that matter)... AnonMoos (talk) 00:13, 24 October 2018 (UTC)

@AnonMoos: I put a similar note on the "(one link)" category as well. I don't agree that "interlinked" can't be blurred (given that it's a category name that I just made up, it doesn't really have any prior meaning in the context of Wikimedia Commons). That said, I do agree that it's a suboptimal name, and like I said, if you have a better name I welcome it. With tools like Cat-a-lot, this should not be much work to revise. --IagoQnsi (talk) 01:06, 24 October 2018 (UTC)

It's nice that you announced what you meant in more relevant places, but there's still a problem with the names. I think "overlapping" allows for a lot more stretching of its meaning than "interlinked". Of course this means that "one link" could not be used in the renamed version of Category:Interlinked Venus and Mars symbols (one link)... -- AnonMoos (talk) 15:18, 24 October 2018 (UTC)

@AnonMoos: "Overlapping" works for me; feel free to change it. Perhaps the "one link" category could become "Singly overlapping Venus and Mars symbols". Alternatively, it could be "Overlapping Venus and Mars symbols representing heterosexuality", which technically a different scope (and probably a few images would have to be moved), but it's the same intent that I had when creating the "one link" category. --IagoQnsi (talk) 17:00, 24 October 2018 (UTC)

I think it would be a good idea to distinguish Venus + Mars symbol combination symbolizing heterosexuality ("Heterosexual symbols with overlapping Venus and Mars symbols"?) from others that don't really have that symbolism, but as I said above, it may take me some days to find the time to go through all the individual images to sort through and reclassify them... AnonMoos (talk) 21:03, 26 October 2018 (UTC)

December

Fixing the Venus and Mars symbols symbols categories was as annoying as I thought it would be beforehand, but I finally did it... My opinion remains just as strong as ever that File:Font Awesome 5 solid venus-mars.svg uses a rather poor visual technique, which obfuscates and obscures its intended meaning to an "awesome" degree, but that won't prevent it from continuing to exist on Commons. AnonMoos (talk) 16:21, 16 December 2018 (UTC)

Valued Image Promotion

★ Your nomination has been reviewed and promoted ★
Congratulations! The image you nominated was reviewed and has now been promoted as a valued image. It is considered to be the most valued image on Commons within the scope:
portraits of Kevin Venegas.
If you would like to nominate another image, please do so at Valued images candidates.

review

•  Support Useful & used --Archaeodontosaurus (talk) 05:14, 17 October 2018 (UTC)

Result: 1 support, 0 oppose =>
promoted. Archaeodontosaurus (talk) 04:52, 21 October 2018 (UTC)

Valued Image Promotion

★ Your nomination has been reviewed and promoted ★
Congratulations! The image you nominated was reviewed and has now been promoted as a valued image. It is considered to be the most valued image on Commons within the scope:
portraits of Russell Cicerone.
If you would like to nominate another image, please do so at Valued images candidates.

review

•  Support Useful & used --Archaeodontosaurus (talk) 05:14, 18 October 2018 (UTC)

Result: 1 support, 0 oppose =>
promoted. Archaeodontosaurus (talk) 07:17, 22 October 2018 (UTC)

Valued images?

By the way, I'm curious how you get so many Valued Image promotions. I tried once with File:Shoelace knot.svg (which seems pretty useful to me), and basically got bubkes... AnonMoos (talk) 16:13, 24 October 2018 (UTC)

@AnonMoos: Looking at that image's VI nomination, it seems like the issue was that the scope was too specific. I bet that image would pass with a scope like "illustration of shoelace knot" -- simpler and broader is best (COM:VIS goes into a lot more detail). That's really the crux of VI -- find the right scope.

I have gotten a decent number of images through there, but if you look through my VI images, all but two of them basically have the same scope: "portraits of [some person]". I don't have much competition with other photographers for most of my subjects (mostly second-division pro soccer players), so it's not too hard for me to get the "best" photo if I have an image that's half decent.

By the way, the nomination you linked wasn't going to work at VI, but it would have probably passed at QI. QI isn't about being the best in a particular scope; it's just about the image being excellent, so that might be more what you're looking for. I have a few QI images, but I don't try there as much because my photos tend to fall short of their technical expectations. (I take photos at soccer matches. Whenever there's a stoppage in play, I take a break from shooting action shots and try to get close-up portraits instead. I don't have time to change my shutter speed and sensitivity for the portraits, so they're grainier than they would be if I was only shooting portraits.) Your SVG diagrams don't have any issues like that, so I bet you'd do well there. --IagoQnsi (talk) 16:52, 24 October 2018 (UTC)

Thanks for the advice, but I had the impression that Quality Images and Featured Images are kind of biased against non-photographs (with relatively infrequent exceptions). The image File:Shoelace knot.svg isn't visually stunning or anything, it's just very, very useful for one particular purpose, which is what led me towards Valued Images -- but the reception I got there didn't really encourage me to try again... AnonMoos (talk) 16:33, 16 December 2018 (UTC)

File:2016 MLS All-Star Game logo.jpg

File:2016 MLS All-Star Game logo.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. Please remember to respond to and – if appropriate – contradict the arguments supporting deletion. Arguments which focus on the nominator will not affect the result of the nomination. Thank you!

Taivo (talk) 09:20, 2 November 2018 (UTC)

Notification about possible deletion

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. Please remember to respond to and – if appropriate – contradict the arguments supporting deletion. Arguments which focus on the nominator will not affect the result of the nomination. Thank you!

Affected:

• File:Pizza Hut logo prototype, 2010.svg

And also:

• File:Pizza Hut logo, 1999–2014.svg
• File:Pizza Hut logo, 2010–2014.png
• File:Pizza Hut logo, 2014.png

Yours sincerely, Magog the Ogre (talk) (contribs) 19:52, 9 December 2018 (UTC)

COM:A

Hey IagoQnsi,

Have you considered being an admin? You seem to have the knowledge to be one. -- 1989 (talk) 05:55, 19 January 2019 (UTC)

@1989: Hey 1989, thanks for the message. I have thought about it a little bit, but never too seriously. Your suggestion that I'd be a good candidate is a big confidence boost -- I think I might try to write up an application today. –IagoQnsi (talk) 17:22, 28 January 2019 (UTC)

If you do decide to go for it, good luck. -- 1989 (talk) 17:27, 28 January 2019 (UTC)

If you need a nominator, let me know. -- 1989 (talk) 06:01, 29 January 2019 (UTC)

File:FC Cincinnati 2019 kit reveal IMG 0882.jpg

Wikimedia Commons does not accept derivative works of non-free works such as File:FC Cincinnati 2019 kit reveal IMG 0882.jpg. It only accepts free content, which is images and other media files that can be used by anyone, for any purpose. Reproductions of copyrighted works are also subject to the same copyright, and therefore this file must unfortunately be considered non-free. For more information, please read Commons:Derivative works and Commons:Freedom of panorama. You can ask questions about Commons policies in Commons:Help desk. The file you added has been deleted. If you believe that this file was not a derivative work of a non-free work, you may request undeletion.

And also:

• File:FC Cincinnati 2019 kit reveal IMG 0883.jpg

Yours sincerely, IagoQnsi (talk) 18:31, 12 February 2019 (UTC)

Code issues in User:IagoQnsi/common.js

Hi IagoQnsi, 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:IagoQnsi/common.js. Glad to see you coding in javascript! Have you ever considered becoming a MediaWiki hacker?
2. Though, that change appears to introduce 29 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 60 character 18: Unclosed string. - Evidence: talk_tag: '
2. ISSUE: line 61 character 61: Unclosed string. - Evidence: == {{Autotranslate|1=:%FILE%|base=No watermarks/heading}} ==
3. ISSUE: line 63 character 33: Expected '}' to match '{' from line 56 and instead saw 't'. - Evidence: talk_summary: 'Please don't upload watermarked images'
4. ISSUE: line 63 character 35: Expected ']' to match '[' from line 2 and instead saw 'upload'. - Evidence: talk_summary: 'Please don't upload watermarked images'
5. ISSUE: line 63 character 41: Missing semicolon. - Evidence: talk_summary: 'Please don't upload watermarked images'
6. ISSUE: line 63 character 53: Missing semicolon. - Evidence: talk_summary: 'Please don't upload watermarked images'
7. ISSUE: line 63 character 61: Unclosed string. - Evidence: talk_summary: 'Please don't upload watermarked images'
8. ISSUE: line 64 character 6: Unclosed string. - Evidence: },
9. ISSUE: line 65 character 5: Unclosed string. - Evidence: {
10. ISSUE: line 63 character 60: Missing semicolon. - Evidence: talk_summary: 'Please don't upload watermarked images'
11. ISSUE: line 66 character 15: Missing semicolon. - Evidence: label: 'Low quality',
12. ISSUE: line 66 character 18: Missing semicolon. - Evidence: label: 'Low quality',
13. ISSUE: line 66 character 28: Unclosed string. - Evidence: label: 'Low quality',
14. ISSUE: line 66 character 26: Missing semicolon. - Evidence: label: 'Low quality',
15. ISSUE: line 67 character 13: Missing semicolon. - Evidence: tag: '{' + '{Low quality|1=}}',
16. ISSUE: line 67 character 19: Missing semicolon. - Evidence: tag: '{' + '{Low quality|1=}}',
17. ISSUE: line 67 character 23: Missing semicolon. - Evidence: tag: '{' + '{Low quality|1=}}',
18. ISSUE: line 67 character 33: Bad assignment. - Evidence: tag: '{' + '{Low quality|1=}}',
19. ISSUE: line 67 character 38: Unclosed string. - Evidence: tag: '{' + '{Low quality|1=}}',
20. ISSUE: line 68 character 21: Missing semicolon. - Evidence: img_summary: 'Low quality image',
21. ISSUE: line 68 character 24: Missing semicolon. - Evidence: img_summary: 'Low quality image',
22. ISSUE: line 68 character 32: Missing semicolon. - Evidence: img_summary: 'Low quality image',
23. ISSUE: line 68 character 40: Unclosed string. - Evidence: img_summary: 'Low quality image',
24. ISSUE: line 68 character 38: Missing semicolon. - Evidence: img_summary: 'Low quality image',
25. ISSUE: line 70 character 5: Expected '}' to match '{' from line 70 and instead saw '{'. - Evidence: == {{autotranslate|1=:%FILE%|base=Provide better quality/heading}} ==
26. ISSUE: line 70 character 6: Missing semicolon. - Evidence: == {{autotranslate|1=:%FILE%|base=Provide better quality/heading}} ==
27. ISSUE: line 70 character 21: Bad assignment. - Evidence: == {{autotranslate|1=:%FILE%|base=Provide better quality/heading}} ==
28. ISSUE: line 70 character 22: Missing semicolon. - Evidence: == {{autotranslate|1=:%FILE%|base=Provide better quality/heading}} ==
29. ISSUE: line 70 character 22: Expected '(end)' and instead saw ':'. - Evidence: == {{autotranslate|1=:%FILE%|base=Provide better quality/heading}} ==

Your CommonsMaintenanceBot (talk) at 19:30, 13 February 2019 (UTC).

Code issues in User:IagoQnsi/common.js

Hi IagoQnsi, 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:IagoQnsi/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 60 column 19: Unexpected token ILLEGAL

Your CommonsMaintenanceBot (talk) at 19:30, 13 February 2019 (UTC).

Code issues in User:IagoQnsi/common.js

Hi IagoQnsi, 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:IagoQnsi/common.js. Glad to see you coding in javascript! Have you ever considered becoming a MediaWiki hacker?
2. Though, that change appears to introduce 23 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 61 character 33: Expected '}' to match '{' from line 56 and instead saw 't'. - Evidence: talk_summary: 'Please don't upload watermarked images'
2. ISSUE: line 61 character 35: Expected ']' to match '[' from line 2 and instead saw 'upload'. - Evidence: talk_summary: 'Please don't upload watermarked images'
3. ISSUE: line 61 character 41: Missing semicolon. - Evidence: talk_summary: 'Please don't upload watermarked images'
4. ISSUE: line 61 character 53: Missing semicolon. - Evidence: talk_summary: 'Please don't upload watermarked images'
5. ISSUE: line 61 character 61: Unclosed string. - Evidence: talk_summary: 'Please don't upload watermarked images'
6. ISSUE: line 62 character 6: Unclosed string. - Evidence: },
7. ISSUE: line 63 character 5: Unclosed string. - Evidence: {
8. ISSUE: line 61 character 60: Missing semicolon. - Evidence: talk_summary: 'Please don't upload watermarked images'
9. ISSUE: line 64 character 15: Missing semicolon. - Evidence: label: 'Low quality',
10. ISSUE: line 64 character 18: Missing semicolon. - Evidence: label: 'Low quality',
11. ISSUE: line 64 character 28: Unclosed string. - Evidence: label: 'Low quality',
12. ISSUE: line 64 character 26: Missing semicolon. - Evidence: label: 'Low quality',
13. ISSUE: line 65 character 13: Missing semicolon. - Evidence: tag: '{' + '{Low quality|1=}}',
14. ISSUE: line 65 character 19: Missing semicolon. - Evidence: tag: '{' + '{Low quality|1=}}',
15. ISSUE: line 65 character 23: Missing semicolon. - Evidence: tag: '{' + '{Low quality|1=}}',
16. ISSUE: line 65 character 33: Bad assignment. - Evidence: tag: '{' + '{Low quality|1=}}',
17. ISSUE: line 65 character 38: Unclosed string. - Evidence: tag: '{' + '{Low quality|1=}}',
18. ISSUE: line 66 character 18: Missing semicolon. - Evidence: talk_tag: '{' + '{subst:Provide better quality|1=:%FILE%}}',
19. ISSUE: line 66 character 24: Missing semicolon. - Evidence: talk_tag: '{' + '{subst:Provide better quality|1=:%FILE%}}',
20. ISSUE: line 66 character 31: Label 'subst' on Provide statement. - Evidence: talk_tag: '{' + '{subst:Provide better quality|1=:%FILE%}}',
21. ISSUE: line 66 character 38: Missing semicolon. - Evidence: talk_tag: '{' + '{subst:Provide better quality|1=:%FILE%}}',
22. ISSUE: line 66 character 45: Missing semicolon. - Evidence: talk_tag: '{' + '{subst:Provide better quality|1=:%FILE%}}',
23. ISSUE: line 66 character 55: Bad assignment. - Evidence: talk_tag: '{' + '{subst:Provide better quality|1=:%FILE%}}',
24. ISSUE: line 66 character 56: Missing semicolon. - Evidence: talk_tag: '{' + '{subst:Provide better quality|1=:%FILE%}}',
25. ISSUE: line 66 character 56: Expected '}' to match '{' from line 66 and instead saw ':'. - Evidence: talk_tag: '{' + '{subst:Provide better quality|1=:%FILE%}}',
26. ISSUE: line 66 character 57: Expected an identifier and instead saw '%'. - Evidence: talk_tag: '{' + '{subst:Provide better quality|1=:%FILE%}}',
27. ISSUE: line 66 character 58: Missing semicolon. - Evidence: talk_tag: '{' + '{subst:Provide better quality|1=:%FILE%}}',
28. ISSUE: line 66 character 63: Expected an identifier and instead saw '}'. - Evidence: talk_tag: '{' + '{subst:Provide better quality|1=:%FILE%}}',
29. ISSUE: line 66 character 67: Unclosed string. - Evidence: talk_tag: '{' + '{subst:Provide better quality|1=:%FILE%}}',
30. ISSUE: line 67 character 21: Missing semicolon. - Evidence: img_summary: 'Low quality image',
31. ISSUE: line 67 character 24: Missing semicolon. - Evidence: img_summary: 'Low quality image',
32. ISSUE: line 67 character 32: Missing semicolon. - Evidence: img_summary: 'Low quality image',
33. ISSUE: line 67 character 40: Unclosed string. - Evidence: img_summary: 'Low quality image',
34. ISSUE: line 67 character 38: Missing semicolon. - Evidence: img_summary: 'Low quality image',
35. ISSUE: line 68 character 22: Missing semicolon. - Evidence: talk_summary: 'Do you have better quality file?'
36. ISSUE: line 68 character 24: Missing semicolon. - Evidence: talk_summary: 'Do you have better quality file?'
37. ISSUE: line 68 character 28: Missing semicolon. - Evidence: talk_summary: 'Do you have better quality file?'
38. ISSUE: line 68 character 33: Missing semicolon. - Evidence: talk_summary: 'Do you have better quality file?'
39. ISSUE: line 68 character 40: Missing semicolon. - Evidence: talk_summary: 'Do you have better quality file?'
40. ISSUE: line 68 character 48: Missing semicolon. - Evidence: talk_summary: 'Do you have better quality file?'
41. ISSUE: line 68 character 55: Unclosed string. - Evidence: talk_summary: 'Do you have better quality file?'
42. ISSUE: line 69 character 5: Unclosed string. - Evidence: }
43. ISSUE: line 70 character 3: Unclosed string. - Evidence: ];
44. ISSUE: line 71 character 1: Unclosed string. - Evidence:
45. ISSUE: line 72 character 17: Expected ':' and instead saw 'User'. - Evidence: //importScript('User:IagoQnsi/Gadget-QuickDelete-custom.js');
46. ISSUE: line 72 character 21: Expected an identifier and instead saw ':'. - Evidence: //importScript('User:IagoQnsi/Gadget-QuickDelete-custom.js');
47. ISSUE: line 72 character 22: Missing semicolon. - Evidence: //importScript('User:IagoQnsi/Gadget-QuickDelete-custom.js');
48. ISSUE: line 72 character 62: Unclosed string. - Evidence: //importScript('User:IagoQnsi/Gadget-QuickDelete-custom.js');
49. ISSUE: line 72 character 59: Missing semicolon. - Evidence: //importScript('User:IagoQnsi/Gadget-QuickDelete-custom.js');
50. ISSUE: line 73 character 17: Missing semicolon. - Evidence: //importScript('User:Kanonkas/twinkle.js');
51. ISSUE: line 73 character 17: Too many errors. (82% scanned). - Evidence: undefined

Your CommonsMaintenanceBot (talk) at 19:31, 13 February 2019 (UTC).

Congratulations, dear license reviewer

If you use the helper scripts, you will find the links next to the search box (vector) or as single tabs (monobook). They are named license+ and license-.

Hi IagoQnsi, thanks for your request for license reviewer status. The request has been closed as successful, and you've been added to the list of reviewers. You can now start reviewing files – please see Commons:License review and Commons:Flickr files if you haven't done so already. We also have a guide how to detect copyright violations. Potential backlogs include Flickr review and files from other sources. You can use one of the following scripts by adding one of the lines to your common.js:

importScript('User:ZooFari/licensereviewer.js'); // stable script for reviewing images from any kind of source OR

importScript('User:Majora/LicenseReview.js'); // contains also user notification when review fails, auto blacklist-check and auto-thank you message for Flickr-reviews.

Please feel free to join us on IRC: #wikimedia-commons ^webchat on irc.freenode.net. You can also add {{User license reviewer}} to your user page if you wish. Thank you for your contributions on Commons! 1989 (talk) 19:31, 14 February 2019 (UTC)

@1989: Thanks a ton! :) –IagoQnsi (talk) 22:44, 14 February 2019 (UTC)

Notification about possible deletion

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. Please remember to respond to and – if appropriate – contradict the arguments supporting deletion. Arguments which focus on the nominator will not affect the result of the nomination. Thank you!

Affected:

• File:CINvBST 2017-05-20 - The Bailey (34420771910).jpg

And also:

• File:CINvCHI 2017-06-28 - The Bailey (26325669177).jpg
• File:CINvCHI 2017-06-28 - The Bailey (40487751674).jpg
• File:CINvCHI 2017-06-28 - The Bailey celebrates win (40301763495).jpg
• File:CINvCHI 2017-06-28 - The Bailey celebrates win (40483657184).jpg
• File:CINvCHI 2017-06-28 - The Bailey celebrates win (41197562671).jpg
• File:CINvCLE 2017-05-17 - The Bailey (34403855580).jpg
• File:CINvCLE 2017-05-17 - The Bailey (34626884962).jpg
• File:CINvCLE 2017-05-17 - The Bailey (34628992652).jpg
• File:CINvCLE 2017-05-17 - The Bailey (34658668411).jpg
• File:CINvCLE 2017-05-17 - The Bailey (34659223011).jpg
• File:CINvCLE 2017-05-17 - The Bailey (34659236951).jpg
• File:CINvCLE 2017-05-17 - The Bailey (34751187456).jpg
• File:CINvIND 2018-09-29 - champions celebration, The Bailey (30243847407).jpg
• File:CINvIND 2018-09-29 - champions celebration, The Bailey (44271477705).jpg
• File:CINvIND 2018-09-29 - The Bailey (44459642614).jpg
• File:CINvIND 2018-09-29 - The Bailey (45132864522).jpg
• File:CINvLOU 2017-05-31 - The Bailey (34210441114).jpg
• File:CINvLOU 2017-05-31 - The Bailey (34924959891).jpg
• File:CINvLOU 2017-05-31 - The Bailey (35013957466).jpg
• File:CINvLOU 2017-05-31 - The Bailey (35016468156).jpg
• File:CINvLOU 2018-04-07 - The Bailey (40749062605).jpg
• File:CINvLOU 2018-04-07 - The Bailey tifo Streamer Things (41641257501).jpg
• File:CINvNSH 2018-08-04 - The Bailey (44069042382).jpg
• File:CINvPGH 2018-04-21 - The Bailey (40963027805).jpg
• File:CINvPGH 2018-09-01 - The Bailey (45085487181).jpg
• File:The Bailey (27761708705).jpg
• File:The Bailey (29784631580).jpg
• File:The Bailey (30079237935).jpg
• File:The Bailey celebrates goal (26713734973).jpg

Yours sincerely, IagoQnsi (talk) 00:34, 15 February 2019 (UTC)

Category:Works by the Raspberry Pi Foundation

Category:Works by the Raspberry Pi Foundation is considered to fulfill the criteria for speedy deletion and has been marked on its page. The following reason has been specified: An appropriate category with the proper and descriptive name - Category:Raspberry Pi original accessories for official accessories made by Pi Foundation already exist If you believe the content does not meet the criteria for speedy deletion, you may replace the speedy deletion tag with a regular deletion request (if the content has not been deleted) or request undeletion (if the content has already been deleted). All your uploads, including deleted ones, are listed in your upload log. If you need help, please read our frequently asked questions or visit the help desk. Please do not remove this message from your talk page. You may set up archiving instead. Warning: Wikimedia Commons takes copyright violations very seriously and persistent violators will be blocked from editing.

Maybe I simply should ask you here first, if so - sorry for my to speedy acting Jasc PL (talk) 18:18, 16 March 2019 (UTC)

@Jasc PL: The purpose of that category was for files created by the Raspberry Pi Foundation -- i.e. official photos taken by the Foundation. Probably a poor name on my part; "Works" should probably be changed to "Photographs" or "Files". –IagoQnsi (talk) 20:38, 16 March 2019 (UTC)

@IagoQnsi: yes, in my opinion "Works" was unclear, including near everything: boards, publications, events... - breaking existing category tree. There is, and will be only the few photos taken directly by the Foundation - I asked them, so they taken and upload some especially for us with CC licence but without NC.

However, there is probably a problem with the pictures that need to be categorized more than once at the same subcategory level in Category:Raspberry Pi accessories, e.g. image of Pi case or so "should" exist together in ...by application > cases, ...by producer and ...by model. Is it allowable or definitely unproper? I'am not sure what should I do. --Jasc PL (talk) 13:09, 17 March 2019 (UTC)

@Jasc PL: Yes that's fine. The purpose of having "X by Y" categories is precisely so that you can sort things that belong in X multiple ways. –IagoQnsi (talk) 13:16, 25 March 2019 (UTC)

File:Fanart - Hello Internet by kittyninjafish.png

File:Fanart - Hello Internet by kittyninjafish.png 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. Please remember to respond to and – if appropriate – contradict the arguments supporting deletion. Arguments which focus on the nominator will not affect the result of the nomination. Thank you!

DanielRigal (talk) 17:24, 6 June 2019 (UTC)

COM:VPC

---

Hello. This message is being sent to inform you that there is currently a discussion at COM:VPC#IagoQnsi's_own_reviews. This is in relation to an issue with which you may have been involved.

--Roy17 (talk) 12:44, 26 July 2019 (UTC)

editToken

Hello IagoQnsi. I just wanted to let you know that editToken is deprecated, and you still use it in one or more of your userspace scripts. If you want your user script(s) to work properly, please replace editToken with csrfToken in source code of the scripts. You'll need to change the following script(s):

• User:IagoQnsi/SVGedit.js

Regards, Ahmad^talk 20:53, 17 October 2019 (UTC)

Important message for file movers

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)

Google Code-In 2019 is coming - please mentor some documentation tasks!

Hello,

Google Code-In, Google-organized contest in which the Wikimedia Foundation participates, starts in a few weeks. This contest is about taking high school students into the world of opensource. I'm sending you this message because you recently edited a documentation page at Wikimedia Commons.

I would like to ask you to take part in Google Code-In as a mentor. That would mean to prepare at least one task (it can be documentation related, or something else - the other categories are Code, Design, Quality Assurance and Outreach) for the participants, and help the student to complete it. Please sign up at the contest page and send us your Google account address to google-code-in-admins@lists.wikimedia.org, so we can invite you in!

From my own experience, Google Code-In can be fun, you can make several new friends, attract new people to your wiki and make them part of your community.

If you have any questions, please let us know at google-code-in-admins@lists.wikimedia.org.

Thank you!

--User:Martin Urbanec (talk) 22:04, 23 November 2019 (UTC)

Notification about possible deletion

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. Please remember to respond to and – if appropriate – contradict the arguments supporting deletion. Arguments which focus on the nominator will not affect the result of the nomination. Thank you!

Affected:

• File:PAX 2009 - Ratchet cosplay (3899562562).jpg

Yours sincerely, Yuraily Lic (talk) 13:33, 6 January 2020 (UTC)

Notification about possible deletion

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. Please remember to respond to and – if appropriate – contradict the arguments supporting deletion. Arguments which focus on the nominator will not affect the result of the nomination. Thank you!

Affected:

• File:PAX 2008 - Darth Vader (2812267863).jpg

And also:

• File:PAX 2008 - Darth Vader (2812268409).jpg

Yours sincerely, Yuraily Lic (talk) 17:07, 8 February 2020 (UTC)

A barnstar for you!

The Original Barnstar

I came across the category for the English Dept of Arizona University. Brilliant. I look at the pages on University's looking for women who need Women in Red articles and sadly disappointed to see so many thoughtless "all rights reserved" tags (grr!) so your creation/support of a shining good example needs recognition. It now has a new sub cat for Looser's new wiki article. Well done Victuallers (talk) 11:18, 20 February 2020 (UTC)

File:PAX South 2015 - Majora's Mask display (16351880202).jpg

File:PAX South 2015 - Majora's Mask display (16351880202).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. Please remember to respond to and – if appropriate – contradict the arguments supporting deletion. Arguments which focus on the nominator will not affect the result of the nomination. Thank you!

Yuraily Lic (talk) 10:04, 14 March 2020 (UTC)

Notification about possible deletion

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. Please remember to respond to and – if appropriate – contradict the arguments supporting deletion. Arguments which focus on the nominator will not affect the result of the nomination. Thank you!

Affected:

• File:NCAA Baseball Championship wordmark color darkbg.svg

And also:

• File:NCAA Baseball wordmark color darkbg.svg
• File:NCAA Basketball Championship wordmark color darkbg.svg
• File:NCAA Basketball wordmark color darkbg.svg
• File:NCAA Beach Volleyball wordmark color darkbg.svg
• File:NCAA Bowling Championship wordmark color darkbg.svg
• File:NCAA Bowling wordmark color darkbg.svg
• File:NCAA Cross Country Championships wordmark color darkbg.svg
• File:NCAA Cross Country wordmark color darkbg.svg
• File:NCAA DI Cross Country Championship wordmark color darkbg.svg
• File:NCAA DI Football Championship wordmark color darkbg.svg
• File:NCAA DI Men's Golf Championship wordmark color darkbg.svg
• File:NCAA DI Men's Soccer Championship wordmark color darkbg.svg
• File:NCAA DI Men's Swimming & Diving Championship wordmark color darkbg.svg
• File:NCAA DI Men's Tennis Championship wordmark color darkbg.svg
• File:NCAA DI Softball Championship wordmark color darkbg.svg
• File:NCAA DI Women's Golf Championships wordmark color darkbg.svg
• File:NCAA DI Women's Swimming & Diving Championship wordmark color darkbg.svg
• File:NCAA DII Baseball Championship wordmark color darkbg.svg
• File:NCAA DII Cross Country Championship wordmark color darkbg.svg
• File:NCAA DII Football Championship wordmark color darkbg.svg
• File:NCAA DII Men's Basketball Championship wordmark color darkbg.svg
• File:NCAA DII Men's Golf Championships wordmark color darkbg.svg
• File:NCAA DII Men's Lacrosse Championship wordmark color darkbg.svg
• File:NCAA DII Men's Tennis Championship wordmark color darkbg.svg
• File:NCAA DII Soccer Championships wordmark color darkbg.svg
• File:NCAA DII Softball Championship wordmark color darkbg.svg
• File:NCAA DII Women's Golf Championship wordmark color darkbg.svg
• File:NCAA DII Women's Volleyball Championship wordmark color darkbg.svg
• File:NCAA DIII Baseball Championship wordmark color darkbg.svg
• File:NCAA DIII Cross Country Championship wordmark color darkbg.svg
• File:NCAA DIII Football Championship wordmark color darkbg.svg
• File:NCAA DIII Men's Basketball Championship wordmark color darkbg.svg
• File:NCAA DIII Men's Golf Championship wordmark color darkbg.svg
• File:NCAA DIII Men's Ice Hockey Championship wordmark color darkbg.svg
• File:NCAA DIII Men's Tennis Championship wordmark color darkbg.svg
• File:NCAA DIII Men's Volleyball Championship wordmark color darkbg.svg
• File:NCAA DIII Soccer Championships wordmark color darkbg.svg
• File:NCAA DIII Softball Championship wordmark color darkbg.svg
• File:NCAA DIII Women's Golf Championship wordmark color darkbg.svg
• File:NCAA DIII Women's Volleyball Championship wordmark color darkbg.svg
• File:NCAA Fencing Championships wordmark color darkbg.svg
• File:NCAA Fencing wordmark color darkbg.svg
• File:NCAA Field Hockey Championship wordmark color darkbg.svg
• File:NCAA Field Hockey wordmark color darkbg.svg
• File:NCAA Football Championship wordmark color darkbg.svg
• File:NCAA Football wordmark color darkbg.svg
• File:NCAA Golf Championships wordmark color darkbg.svg
• File:NCAA Golf wordmark color darkbg.svg
• File:NCAA Gymnastics Championships wordmark color darkbg.svg
• File:NCAA Gymnastics wordmark color darkbg.svg
• File:NCAA Ice Hockey Championship wordmark color darkbg.svg
• File:NCAA Ice Hockey wordmark color darkbg.svg
• File:NCAA Indoor Track & Field Championship wordmark color darkbg.svg
• File:NCAA Lacrosse Championship wordmark color darkbg.svg
• File:NCAA Lacrosse wordmark color darkbg.svg
• File:NCAA Rifle Championship wordmark color darkbg.svg
• File:NCAA Rifle wordmark color darkbg.svg
• File:NCAA Rowing Championship wordmark color darkbg.svg
• File:NCAA Rowing wordmark color darkbg.svg
• File:NCAA Skiing Championship wordmark color darkbg.svg
• File:NCAA Skiing wordmark color darkbg.svg
• File:NCAA Soccer Championships wordmark color darkbg.svg
• File:NCAA Soccer wordmark color darkbg.svg
• File:NCAA Softball Championship wordmark color darkbg.svg
• File:NCAA Softball wordmark color darkbg.svg
• File:NCAA Swimming & Diving Championship wordmark color darkbg.svg
• File:NCAA Swimming & Diving wordmark color darkbg.svg
• File:NCAA Tennis Championship wordmark color darkbg.svg
• File:NCAA Tennis wordmark color darkbg.svg
• File:NCAA Track & Field Championship wordmark color darkbg.svg
• File:NCAA Track & Field wordmark color darkbg.svg
• File:NCAA Volleyball Championship wordmark color darkbg.svg
• File:NCAA Volleyball wordmark color darkbg.svg
• File:NCAA Water Polo Championship wordmark color darkbg.svg
• File:NCAA Water Polo wordmark color darkbg.svg
• File:NCAA Women's Basketball wordmark color darkbg.svg
• File:NCAA Wrestling Championship wordmark color darkbg.svg
• File:NCAA Wrestling wordmark color darkbg.svg

Yours sincerely, IagoQnsi (talk) 06:22, 2 April 2020 (UTC)

File:Font Awesome 5 brands python.svg

File:Font Awesome 5 brands python.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. Please remember to respond to and – if appropriate – contradict the arguments supporting deletion. Arguments which focus on the nominator will not affect the result of the nomination. Thank you!

+mt 22:29, 7 July 2020 (UTC)

File:SDCC 2015 - Chris Hardwick, Kathleen Kennedy, J. J. Abrams & Lawrence Kasdan (19671857652).jpg

File:SDCC 2015 - Chris Hardwick, Kathleen Kennedy, J. J. Abrams & Lawrence Kasdan (19671857652).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 may soon be deleted. If you have written permission from the copyright holder, please replace the copyvio tag with {{subst:OP}} and have them send us a free license release via COM:VRT. If you disagree that the file is a copyright violation for any other reason, please replace the copyvio tag with a regular deletion request. This file is a copyright violation for the following reason: Effectively a screenshot of a copyright video Warning: Wikimedia Commons takes copyright violations very seriously and persistent violators will be blocked from editing.

 

FredWalsh (talk) 23:19, 15 July 2020 (UTC)

File:SDCC 2015 - Chris Hardwick, Kathleen Kennedy, J. J. Abrams & Lawrence Kasdan (19678974245).jpg

File:SDCC 2015 - Chris Hardwick, Kathleen Kennedy, J. J. Abrams & Lawrence Kasdan (19678974245).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 may soon be deleted. If you have written permission from the copyright holder, please replace the copyvio tag with {{subst:OP}} and have them send us a free license release via COM:VRT. If you disagree that the file is a copyright violation for any other reason, please replace the copyvio tag with a regular deletion request. This file is a copyright violation for the following reason: Effectively a screenshot of a copyright video Warning: Wikimedia Commons takes copyright violations very seriously and persistent violators will be blocked from editing.

 

FredWalsh (talk) 23:19, 15 July 2020 (UTC)

File:SDCC 2015 - Star Wars The Force Awakens panel (19060708933).jpg

File:SDCC 2015 - Star Wars The Force Awakens panel (19060708933).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.) This file is a copyright violation for the following reason: Effectively a screenshot of a copyright video Warning: Wikimedia Commons takes copyright violations very seriously and persistent violators will be blocked from editing.

 

FredWalsh (talk) 23:27, 15 July 2020 (UTC)

File:SDCC 2015 - Star Wars The Force Awakens panel (19493503478).jpg

File:SDCC 2015 - Star Wars The Force Awakens panel (19493503478).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.) This file is a copyright violation for the following reason: Effectively a screenshot of a copyright video Warning: Wikimedia Commons takes copyright violations very seriously and persistent violators will be blocked from editing.

 

FredWalsh (talk) 23:27, 15 July 2020 (UTC)

File:SDCC 2015 - Star Wars The Force Awakens panel (19493532750).jpg

File:SDCC 2015 - Star Wars The Force Awakens panel (19493532750).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.) This file is a copyright violation for the following reason: Effectively a screenshot of a copyright video Warning: Wikimedia Commons takes copyright violations very seriously and persistent violators will be blocked from editing.

 

FredWalsh (talk) 23:27, 15 July 2020 (UTC)

Notification about possible deletion

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. Please remember to respond to and – if appropriate – contradict the arguments supporting deletion. Arguments which focus on the nominator will not affect the result of the nomination. Thank you!

Affected:

• File:SDCC 2015 - Chris Hardwick, Kathleen Kennedy, J. J. Abrams & Lawrence Kasdan (19671857652).jpg

And also:

• File:SDCC 2015 - Chris Hardwick, Kathleen Kennedy, J. J. Abrams & Lawrence Kasdan (19678974245).jpg
• File:SDCC 2015 - Star Wars The Force Awakens panel (19060708933).jpg
• File:SDCC 2015 - Star Wars The Force Awakens panel (19493503478).jpg
• File:SDCC 2015 - Star Wars The Force Awakens panel (19493532750).jpg

Yours sincerely, IagoQnsi (talk) 04:07, 16 July 2020 (UTC)

Notification about possible deletion

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. Please remember to respond to and – if appropriate – contradict the arguments supporting deletion. Arguments which focus on the nominator will not affect the result of the nomination. Thank you!

Affected:

• File:PAX 2008 - Darth Vader (2812268409).jpg

And also:

• File:RTX 2014 - Stormtroopers (14570897691).jpg

Yours sincerely, Yuraily Lic (talk) 23:04, 21 July 2020 (UTC)

Notification about possible deletion

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. Please remember to respond to and – if appropriate – contradict the arguments supporting deletion. Arguments which focus on the nominator will not affect the result of the nomination. Thank you!

Affected:

• File:PAX South 2016 - Star Wars cosplay (24095589713).jpg

Yours sincerely, Yuraily Lic (talk) 20:34, 6 August 2020 (UTC)

Notification about possible deletion

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. Please remember to respond to and – if appropriate – contradict the arguments supporting deletion. Arguments which focus on the nominator will not affect the result of the nomination. Thank you!

Affected:

• File:RTX 2016 - Cosplay (28051951086).jpg

Yours sincerely, Yuraily Lic (talk) 15:04, 11 August 2020 (UTC)

File:Tom Scott signature red.svg

File:Tom Scott signature red.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. Please remember to respond to and – if appropriate – contradict the arguments supporting deletion. Arguments which focus on the nominator will not affect the result of the nomination. Thank you!

BegbertBiggs (talk) 23:30, 10 October 2020 (UTC)

Notification about possible deletion

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. Please remember to respond to and – if appropriate – contradict the arguments supporting deletion. Arguments which focus on the nominator will not affect the result of the nomination. Thank you!

Affected:

• File:JimmyV cropped.jpg

Yours sincerely, IagoQnsi (talk) 20:55, 19 October 2020 (UTC)

File:Coach K talks to bench (Duke Chronicle 1988-04-01).jpg

File:Coach K talks to bench (Duke Chronicle 1988-04-01).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.

 

And also:

• File:Duke at GT - Billy King shoots (Duke Chronicle 1988-04-01).jpg
• File:Duke Chronicle 1988-04-01 page 1.jpg
• File:Duke Chronicle 1988-04-01 page 17.jpg
• File:Duke Chronicle 1988-04-01 page 18.jpg
• File:Duke Chronicle 1988-04-01 page 20.jpg

Yours sincerely, IagoQnsi (talk) 22:28, 19 October 2020 (UTC)

Some peanut butter stew for you!

	Peanut butter stew
	Thank you for uploading all the Tom Lehrer lyric sheets! Have some peanut butter stew, inspired by one of Lehrer's songs. FunnyMath (talk) 19:53, 24 October 2020 (UTC)

@FunnyMath: Oh hey, thanks friend! Cheers, IagoQnsi (talk) 20:30, 24 October 2020 (UTC)

File:United States Soccer Federation logo 2016.svg

File:United States Soccer Federation logo 2016.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. Please remember to respond to and – if appropriate – contradict the arguments supporting deletion. Arguments which focus on the nominator will not affect the result of the nomination. Thank you!

168.227.97.142 16:56, 2 November 2020 (UTC)

File:Joe Scott 2020 Air Force portrait.jpg

File:Joe Scott 2020 Air Force portrait.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.) This file is a copyright violation for the following reason: This is not an official U.S. Air Force Academy photo. The Academy simply used the University of Georgia's photo of Scott. Warning: Wikimedia Commons takes copyright violations very seriously and persistent violators will be blocked from editing.

 

User who nominated the file for deletion (Nominator) : Arbor to SJ.

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 (talk) 22:10, 10 November 2020 (UTC)

File tagging File:JimmyV cropped.jpg

This media was probably deleted.

Thanks for uploading File:JimmyV cropped.jpg. 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). The file probably has been deleted. If you sent a permission, try to send it again after 14 days. Do not re-upload. When the VRT-member processes your mail, the file can be undeleted. Additionally you can request undeletion here, providing a link to the File-page on Commons where it was uploaded ([[:File:JimmyV cropped.jpg]]) and the above demanded information in your request.

 

Missvain (talk) 19:55, 2 December 2020 (UTC)

File:Cyberpunk 2077 logo.svg

File:Cyberpunk 2077 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. Please remember to respond to and – if appropriate – contradict the arguments supporting deletion. Arguments which focus on the nominator will not affect the result of the nomination. Thank you!

SCP-2000 05:25, 12 December 2020 (UTC)

File:Valour FC logo V mark.png

File:Valour FC logo V mark.png 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. Please remember to respond to and – if appropriate – contradict the arguments supporting deletion. Arguments which focus on the nominator will not affect the result of the nomination. Thank you!

Saschaporsche (talk) 19:16, 4 March 2021 (UTC)

File:PG Sittenfeld in Eden Park (24490386410).jpg

File:PG Sittenfeld in Eden Park (24490386410).jpg has been marked for speedy deletion as promotional material. Wikimedia Commons doesn't allow advertisements. Use Google Ads, Facebook ads or find other forums/websites. If you continue to upload advertisements, you may have to face some strict administrative actions. Please act wisely! 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) : 24.26.33.113.

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 (talk) 04:40, 11 March 2021 (UTC)

File:PG Sittenfeld in Eden Park (24759702656).jpg

File:PG Sittenfeld in Eden Park (24759702656).jpg has been marked for speedy deletion. (Reason: <Improper use. Political advertising) 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) : 24.26.33.113.

And also:

• File:PG Sittenfeld in Eden Park (24785916175).jpg ( Nominator : 24.26.33.113 )

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 (talk) 05:11, 11 March 2021 (UTC))

File:Cyberpunk 2077 logo zh-hans.svg

File:Cyberpunk 2077 logo zh-hans.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. Please remember to respond to and – if appropriate – contradict the arguments supporting deletion. Arguments which focus on the nominator will not affect the result of the nomination. Thank you!

Liuxinyu970226 (talk) 00:01, 3 May 2021 (UTC)

File:Cyberpunk 2077 logo zh-hant.svg

File:Cyberpunk 2077 logo zh-hant.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. Please remember to respond to and – if appropriate – contradict the arguments supporting deletion. Arguments which focus on the nominator will not affect the result of the nomination. Thank you!

Liuxinyu970226 (talk) 00:02, 3 May 2021 (UTC)

File:Heart Health Park logo.svg

File:Heart Health Park 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. Please remember to respond to and – if appropriate – contradict the arguments supporting deletion. Arguments which focus on the nominator will not affect the result of the nomination. Thank you!

Royalbroil 13:40, 15 May 2021 (UTC)

File:MLS is Back Tournament text logo.png

File:MLS is Back Tournament text logo.png 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 may soon be deleted. If you have written permission from the copyright holder, please replace the copyvio tag with {{subst:OP}} and have them send us a free license release via COM:VRT. If you disagree that the file is a copyright violation for any other reason, please replace the copyvio tag with a regular deletion request. This file is a copyright violation for the following reason: Derived from a deleted file Warning: Wikimedia Commons takes copyright violations very seriously and persistent violators will be blocked from editing.

 

A1Cafel (talk) 07:44, 4 July 2021 (UTC)

File:Мари Краймбрери на «Страна FM».jpg and File:Живое исполнение Мари Краймбрери «Он тоже любит дым».wav

@IagoQnsi, hello! Could you please check these files: File:Мари Краймбрери на «Страна FM».jpg and File:Живое исполнение Мари Краймбрери «Он тоже любит дым».wav. Check also as you did here. Thank you! — Calvinn1 (talk) 12:11, 6 August 2021 (UTC)

File:Resident Evil Village logo black.svg

File:Resident Evil Village logo black.svg 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.) This file is a copyright violation for the following reason: Above per COM:TOO, see Commons:Deletion requests/File:Resident Evil 8 Village Logo.svg Warning: Wikimedia Commons takes copyright violations very seriously and persistent violators will be blocked from editing.

 

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

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 (talk) 23:40, 6 August 2021 (UTC)

Threshold of originality

Some of your recently-uploaded video game logos do not "consist only of simple geometric shapes or text", I think. These are the most striking examples:

• 
• File:Viewtiful Joe logo black.svg

Just wanted to let you know. —Dexxor (talk) 09:31, 7 August 2021 (UTC)

@Dexxor: Viewtiful Joe probably is over the line, so I've tagged that one for speedy deletion, but the rest of them I feel are below the threshold of originality. --IagoQnsi (talk) 21:03, 7 August 2021 (UTC)

Map of Cities in the USA and Canada with MLB, MLS, NBA, NFL or NHL Teams

Please check out the update. Thx for advice and patience. Greetings Lencer (talk) 18:57, 9 August 2021 (UTC)

File:MineCon2015ExpoHall.jpg

File:MineCon2015ExpoHall.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. Please remember to respond to and – if appropriate – contradict the arguments supporting deletion. Arguments which focus on the nominator will not affect the result of the nomination. Thank you!

Slenderman7676 (talk) 20:22, 10 August 2021 (UTC)

File tagging File:No Agenda cover 857.png

This media may be deleted.

Thanks for uploading File:No Agenda cover 857.png. 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.

 

Adeletron 3030 (talk) 20:58, 16 March 2022 (UTC)

@Adeletron 3030: Huh? If you click the source link, there's a license statement right at the bottom of the page. –IagoQnsi (talk) 21:55, 16 March 2022 (UTC)

My bad. Adeletron 3030 (talk) 03:18, 17 March 2022 (UTC)

WHAT'S WRONG !!

YOU DO NOT HAVE THE RIGHT TO DELETE MY IMAGE IF SUCH IMAGE HAS CREATIVE COMMONS, THEREFORE REMOVES THAT MESSAGE FROM DELETING, ALSO THE IMAGE IS FROM FLICK AND IS PUBLIC DOMAIN, SO DO NOT THE BORRES, BECAUSE YOU HAVE NO RIGHT! AND ANSWER NOW! — Preceding unsigned comment added by Silvn 21 (talk • contribs) 23:17, 20 April 2018 (UTC)

Please

Help me not to delete my image, I did not know that I had copyright. — Preceding unsigned comment added by Silvn 21 (talk • contribs) 18:49, 23 April 2018 (UTC)

(talk page stalker) @Silvn 21: Hi, and welcome. You should have commented at Commons:Deletion requests/File:Sofia Fanart.jpg instead. See also COM:LL and COM:SIGN.   — Jeff G. ツ _{please ping or talk to me} 10:32, 31 August 2022 (UTC)

Adding Screen shot

Hi there, I'm having a hard time adding a screen shot of our app on our company's article. It says the image is within a image, or does not look real. It is a screen shot of the phone screen using our app. How do you advise moving forward? — Preceding unsigned comment added by Dawood34 (talk • contribs) 21:47, 27 April 2018 (UTC)

(talk page stalker) @Dawood34: Hi, and welcome. I am sorry to inform you that you have triggered Special:AbuseFilter/153 by trying to cross-wiki upload a png image as a new user and Special:AbuseFilter/158 by trying to cross-wiki upload logos with self-cc-by-sa licenses as a new user.. Such uploads of png images are not allowed at all. You indicated it's your own work. Usually when someone uploads a png image, it's a copyright violation taken from the web. Please upload the full-size original of it per COM:HR, including any metadata, but it may be judged too complex to be under TOO in the country of origin, so you may need to license it on your official website or social media or send permission via VRT. Also, any png image will look fuzzy when scaled down (due to design decisions discussed in phab:T192744) or jaggy when scaled up, so you may want to upload an svg or jpg version, too. If you can't get a compliant license, the image may still be uploaded to English Wikipedia in compliance with en:WP:F because we don't allow Fair Use here. If you use our Upload Wizard instead, you should be able to avoid that filter. See also COM:SIGN.   — Jeff G. ツ _{please ping or talk to me} 09:59, 31 August 2022 (UTC)

File:No Agenda cover 565.png

File:No Agenda cover 565.png 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. Please remember to respond to and – if appropriate – contradict the arguments supporting deletion. Arguments which focus on the nominator will not affect the result of the nomination. Thank you!

--Minorax^«¦talk¦» 14:47, 2 May 2022 (UTC)

File:Fcsb-logo.svg

File:Fcsb-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. Please remember to respond to and – if appropriate – contradict the arguments supporting deletion. Arguments which focus on the nominator will not affect the result of the nomination. Thank you!

  — Jeff G. ツ _{please ping or talk to me} 09:37, 31 August 2022 (UTC)

Thanks for fixing my font awesome goof

Thanks for letting me know (and fixing) that font awesome isn't actually linked to unicode. I appreciate it! Smasongarrison (talk) 12:29, 1 October 2022 (UTC)

@Smasongarrison: And thank you for your gracious reply! I know it's not the nicest to log in and find out you've been reverted a bunch, so thanks for being understanding. Cheers, IagoQnsi (talk) 16:41, 1 October 2022 (UTC)

Please talk to me before you just modify my work

I reverted the file you decided to rescale. You do not refer to any policy or other issue other than your personal preference. Please do not modify my files before talking about it please. Thank you. --Don (talk) 05:49, 8 October 2022 (UTC)

@WPPilot: Per Commons:Overwriting existing files, existing files should be overwritten to replace them with "higher resolution versions of the same file, however, without using artificial methods to generate higher resolution". When you upscaled File:N72EX by Don Ramey Logan.jpg on 05:14, 28 March 2020, you did so using those artificial methods, which is why I reverted to the original scale version. However, since you have disputed the change, I have now uploaded the original scale version as a separate file at File:N72EX by Don Ramey Logan (original scale).jpg. I have changed the English Wikipedia article to use this file as I believe it is the better version of the photo. –IagoQnsi (talk) 06:21, 8 October 2022 (UTC)

I nominated MY FILE for removal under speedy deletion. This is not how you do things here I am afraid. Go back to your soccer pics please and leave my work alone unless you are willing to communicate like a normal person. --Don (talk) 07:04, 8 October 2022 (UTC)

I have been here a long time, please be respectful of my work. I am asking you now to simply leave it alone. Find something else to edit. --Don (talk) 07:14, 8 October 2022 (UTC)

The original file, here on MY computer is 4000px wide. All versions I have loaded were duratives of it, by MY downsizing them. Please stop and find something else to do. --Don (talk) 07:21, 8 October 2022 (UTC)

The current version of this file was downscaled to 1,078 × 642, then that 1,078 × 642 version was upscaled to 2,000 × 1,191. You can tell this occurred because the JPEG artifacts are bigger than they would be on a file that had never been upscaled. If you want to upload a new 2,000 × 1,191 version by downscaling your 4000px version to 2000px, that would be fantastic (or in fact, you could upload the original 4000px without any downscaling at all). IagoQnsi (talk) 07:27, 8 October 2022 (UTC)

For the LAST time, please find something else to do. This is a nice big project, the file is now signed by me and I will delete the prior versions, simply move on please.--Don (talk) 07:32, 8 October 2022 (UTC)

You have already exceeded 3 R & R rule and have now again removed the copyright and sig on my file. STOP! I will be issuing a Digital Take down notice, to Wiki today for this file. STOP, leave me file alone.--Don (talk) 15:31, 8 October 2022 (UTC)

Copyright violations

---

Hello IagoQnsi. You have uploaded one or more files that are copyright violations. You have done so despite requests from editors not to do so, and despite their instructions. See Commons:Licensing for the copyright policy on Wikimedia Commons. You may also find Commons:Copyright rules by subject matter useful. This is your last warning. The next time you upload a file that violates copyright, you will be blocked. Please leave me a message if you have further questions.

File tagging File:Go gopher plush.jpg

This media may be deleted.

Thanks for uploading File:Go gopher plush.jpg. 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.

 

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

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) 17:07, 31 December 2022 (UTC)

File:Tom Lehrer lyrics, When You Are Old and Gray.pdf

File:Tom Lehrer lyrics, When You Are Old and Gray.pdf 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. Please remember to respond to and – if appropriate – contradict the arguments supporting deletion. Arguments which focus on the nominator will not affect the result of the nomination. Thank you!

Andrei Romanenko (talk) 03:23, 5 January 2023 (UTC)

File:Channel Super Fun logo.jpg

File:Channel Super Fun logo.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. Please remember to respond to and – if appropriate – contradict the arguments supporting deletion. Arguments which focus on the nominator will not affect the result of the nomination. Thank you!

Bassie f (talk) 05:03, 16 January 2023 (UTC)

File:Transfermarkt favicon.png

File:Transfermarkt favicon.png 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. Please remember to respond to and – if appropriate – contradict the arguments supporting deletion. Arguments which focus on the nominator will not affect the result of the nomination. Thank you!

TM-Garo (talk) 19:07, 17 February 2023 (UTC)

File:Southern-nazarene logo from NCAA.svg

File:Southern-nazarene logo from NCAA.svg 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 may soon be deleted. If you have written permission from the copyright holder, please replace the copyvio tag with {{subst:OP}} and have them send us a free license release via COM:VRT. If you disagree that the file is a copyright violation for any other reason, please replace the copyvio tag with a regular deletion request. This file is a copyright violation for the following reason: Copyright infringement / piracy Warning: Wikimedia Commons takes copyright violations very seriously and persistent violators will be blocked from editing.

 

User who nominated the file for deletion (Nominator) : 2600:1700:F02:61A0:4512:3522:38F8:CE95.

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) 01:46, 21 February 2023 (UTC)

File:Southern-nazarene logo from NCAA.svg

File:Southern-nazarene logo from NCAA.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. Please remember to respond to and – if appropriate – contradict the arguments supporting deletion. Arguments which focus on the nominator will not affect the result of the nomination. Thank you!

—‍Mdaniels5757 (talk • contribs) 01:42, 24 February 2023 (UTC)

File tagging File:No Agenda cover placeholder.jpg

This media may be deleted.

Thanks for uploading File:No Agenda cover placeholder.jpg. 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.

 

Trade (talk) 23:21, 8 March 2023 (UTC)

Lynn Strongin, poet.jpg

I saw you tagged Lynn Strongin, poet.jpg as missing permission. I am an admin on the English Wikipedia and I created the original article on Lynn Strongin. I also contacted the original photographer of the image, Deborah Munro, to see if she'd consent to uploading the image to Wikimedia Commons under the Creative Commons license. She did consent and created a Wikimedia Commons account and uploaded/released the image under the Creative Commons license. I have the emails with Munro agreeing to do this and then following through. Would it be sufficient for me to send those emails through the Wikimedia VRTS release generator, or do I need to get Munro to send a new email?--SouthernNights (talk) 14:05, 23 March 2023 (UTC)

No need to respond. I was able to have the person who took the photo, Deborah Munro, complete the Wikimedia VRT release generator and send in the release. That combined with the release when Munro uploaded the photo should be good.--SouthernNights (talk) 20:58, 23 March 2023 (UTC)

Oh, hey, glad you got it worked out! :) –IagoQnsi (talk) 01:22, 24 March 2023 (UTC)

Лапин Евгений Владимирович

Здравствуйте,хочу выразить свое не согласие по поводу авторских прав, художник Лапин умер в 2003 году и оставил после себя много картин , я являюсь его внуком и прямым наследником на все картины ,я единственный владелец картин и поэтому владелец авторских прав .Они находятся в моем доме и я являюсь их собственником , прошу не совершать ошибку и не удалять архивы моей семьи. BLOODSHED26 (talk) 16:42, 24 March 2023 (UTC)

No permission tagging

Could you elaborate why you tagged this? whym (talk) 09:49, 29 March 2023 (UTC)

It looked like it was a posed studio/on-set portrait of a possibly famous person (Tsubaki Sannomiya appears to be a porn actress), which by definition would have to be taken by someone working with her or something like that, so I figured we needed permission. –IagoQnsi (talk) 11:27, 29 March 2023 (UTC)

Thank you. In that case, I would rather go for a regular deletion request. I think I'll do so for this file shortly. I'll link this in the DR but feel free to say more about it there. whym (talk) 12:44, 29 March 2023 (UTC)

My own picture that i made was suppressed

Hi! i made a picture of an helmet of american football. i posted it but it was tagged as possible violation of copyright. how is it possible as i made it myself based ? is there something i can do to avoid this please? Chrys Laspals (talk) 12:18, 31 March 2023 (UTC)

@Chrys Laspals: Hi Chrys, I don't remember exactly what your images looked like, but based on the logs, it looked like I believed the images included a copyrighted logo. If the images were entirely your own work, you may be able to get them undeleted by making a request at COM:REFUND. Best, IagoQnsi (talk) 03:34, 1 April 2023 (UTC)

Thanks i'll do this Chrys Laspals (talk) 12:14, 2 April 2023 (UTC)

DR

Could i please get your input on Deletion requests/File:The Sims 4 Fishnet Tights (7).jpg and Deletion requests/File:The Sims 4th Gen Logo.webp? Trade (talk) 11:53, 3 April 2023 (UTC)

Better source request for File:Oberlin College yearbook 1912 (hiohi1911ober).pdf

Thanks for uploading File:Oberlin College yearbook 1912 (hiohi1911ober).pdf. You provided a source, but it is difficult for other users to examine the copyright status of the file because the source is incomplete. Please consider clarifying the exact source so that the copyright status may be checked more easily. It is best to specify the exact web page where you found the file, rather than only giving the source domain or the URL of the file itself. Please update the file description with a URL that will be more helpful to other users in determining the copyright status. If you have uploaded other files, consider checking that you have specified their source in a complete manner. You can find a list of files you have uploaded by following this link. If you have any questions please ask them at the help desk or me at my talkpage. Thank you.

---

 

--ShakespeareFan00 (talk) 20:18, 16 August 2023 (UTC)

Question

if you can upload some logos of mostly sports teams i follow worldwide, highly appreciated. i took time to look for regular image editors. this to begin:

https://en.m.wikipedia.org/wiki/FC_Deccan#

https://m.facebook.com/photo.php?fbid=453815190096582&set=a.453815146763253&type=3 93.140.4.183 01:07, 29 August 2023 (UTC)