User talk:Geo Swan

• User Talk:Geo Swan/archive/2005
• User Talk:Geo Swan/archive/2006
• User Talk:Geo Swan/archive/2007
• User Talk:Geo Swan/archive/2008
• User Talk:Geo Swan/archive/2009
• User Talk:Geo Swan/archive/2010
• User Talk:Geo Swan/archive/2011
• User Talk:Geo Swan/archive/2012
• User Talk:Geo Swan/archive/2013
• User Talk:Geo Swan/archive/2014
• User Talk:Geo Swan/archive/list

TUSC token 70dfd90b6e52c9080a8e30c0dd592336

I am now proud owner of a TUSC account! 70dfd90b6e52c9080a8e30c0dd592336 Geo Swan (talk) 01:31, 14 September 2009 (UTC)

File:A Pumpkin Spice Latte from Second Cup.jpg

File:A Pumpkin Spice Latte from Second Cup.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 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!

🎂CAKE🎂 13:22, 23 January 2015 (UTC)

File:Second Cup Coffee Mckenzie Towne High Street Calgary Alberta Canada Chai Tea Latte.jpg

File:Second Cup Coffee Mckenzie Towne High Street Calgary Alberta Canada Chai Tea Latte.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 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!

🎂CAKE🎂 13:25, 23 January 2015 (UTC)

Please be more careful with flickr images

You really ought to slow down and be more careful when you're mass-uploading images from flickr. The results of your current strategy are a lot of poorly categorized and formatted images. I've just tagged almost a dozen files you uploaded that were exact duplicates of existing images. In one case, you've uploaded the same image three times. You also just threw generic categories on hundreds of images at once, without checking what the image was of. I understand that there's a lot of BPL images that you're trying to work through, but you are creating ten times as much work for editors like me who have to clean up. (I am more or less the only active editor on Commons who knows the old Boston Elevated Railway stations, so it's basically up to me to do it.)

Please consider following these suggestions: If you cannot identify the subject of the image enough to properly categorize it (down to the proper station or building category, if it exists), do not upload it. If you have not checked for duplicates first, do not upload it. If you do not have the time to remove the default formatting and properly format the description template, do not upload it. I can teach you how to do any of these if you're not sure how to.

It's better to have 20 images that are properly identified, formatted, and categorized than 2,000 images that aren't useful to the end user. Pi.1415926535 (talk) 08:23, 25 January 2015 (UTC)

Queen East and CNR overpass

Thanks for the Cats. I will include them in future uploads. Secondarywaltz (talk) 19:04, 4 February 2015 (UTC)

One of booledozer's

File:2015 Pan Am Village Jan 2015.jpg was uploaded recently from Flickr. I thought you might want to clean it up. Secondarywaltz (talk) 18:55, 4 March 2015 (UTC)

Thanks [1]  Done Geo Swan (talk) 23:36, 4 March 2015 (UTC)

Copyright status: File:This postcard shows a radial car that has just crossed the Canal bridge heading for Hamilton. The earliest postmark found for this card is June 25, 1912.jpg

This media may be deleted.

Thanks for uploading File:This postcard shows a radial car that has just crossed the Canal bridge heading for Hamilton. The earliest postmark found for this card is June 25, 1912.jpg. I notice that the file page either doesn't contain enough information about the license or it contains contradictory information about the license, so the copyright status is unclear. If you created this file yourself, then you must provide a valid copyright tag. For example, you can tag it with {{self|GFDL|cc-by-sa-all}} to release it under the multi-license GFDL plus Creative Commons Attribution-ShareAlike All-version license or you can tag it with {{PD-self}} to release it into the public domain. (See Commons:Copyright tags for the full list of license tags that you can use.) If you did not create the file yourself or if it is a derivative of another work that is possibly subject to copyright protection, then you must specify where you found it (e.g. usually a link to the web page where you got it), you must provide proof that it has a license that is acceptable for Commons (e.g. usually a link to the terms of use for content from that page), and you must add an appropriate license tag. If you did not create the file yourself and the specific source and license information is not available on the web, you must obtain permission through the OTRS system and follow the procedure described there. Note that any unsourced or improperly licensed files will be deleted one week after they have been marked as lacking proper information, as described in criteria for speedy deletion. If you have uploaded other files, please confirm that you have provided the proper information for those files, too. If you have any questions about licenses please ask at Commons:Village pump/Copyright or see our help pages. Thank you.

No required license templates were detected at this file page. Please correct it, or if you have any questions please check my FAQ or contact me on my talk page. Yours sincerely, Jarekt (talk) 13:43, 9 April 2015 (UTC)

about an admin removing talk page discussion

talk page permanent link.

This is just FYI. Obviously, you should not comment there at this point! --Abd (talk) 20:20, 10 April 2015 (UTC)

User:Abd, I believe we are all accountable to one another. In particular, when User:Fastily was entrusted with administrator authority I believe that did not lift him to an unaccountable status.

Several months ago Fastily told me something about how he felt free to ignore communications from me because he had concluded I had a grudge against him over an "imagined slight". That was complete nonsense, as I believe that that every single time I have left a comment for him I voiced a specific policy based concern. I saw that you counseled Fastily to try to ignore that comments came from me, and to try and read them as if there was a valid policy based core to them, that was worth paying attention to. That was excellent advice. I do try to draft comments to him that are policy based, that contain my best advice, that are worth paying attention to, no matter how much of my time he has squandered through his on-going refusal to be held accountable.

I've wondered whether he does, at some level, recognize that I am raising valid points. I've wondered whether the core of his problem with me is that he thinks something like: "That so-and-so Geo Swan! It is as if he is insisting I explicitly acknowledge I made a mistake! Why can't he trust that I am intelligent enough to get his point, without looking for me to say I got his point?"

I do look for him to start explicitly acknowledging his mistakes -- but only because he keeps making the same mistakes over and over and over again. Geo Swan (talk) 15:04, 11 April 2015 (UTC)

Okay, Geo. My suggestion. You used the word "terrible." Strike it! Really. Look, I know exactly how you are thinking. I warned an administrator on en.wiki. He blew me off, and predicted I'd be banned in short order. Well, I was banned, long story, but not before he was desysopped over his interactions with me. I had given him good advice.

As to my own ban, I didn't care. One abusive administrator can drive away many possibly productive users, so I considered the cost to be low. I'm not personally that important and I can still help users as a banned editor! I often have. Successfully. I have not appealed the Wikipedia community ban because it helps me avoid dealing with that community, which I consider too-often-toxic. Many good people. A few who are full of hatred and other toxins. And the good people mostly do nothing about it, so the good people are responsible for the toxicity. I did what I could while I was there. It was popular with some, but, I found, ultimately unpopular with the Arbitration Committee, which has a high level of mistrust for those the members consider "outsiders."

Here, what Fastily is doing is dangerous, and, it's not impossible, it could lead to desysopping here. However, that is not where I go with it. My goal is to preserve and support valuable users, which very certainly includes him. Had I not read your comments as being worthy of attention, I would not have intervened, though there is also how he was treating naive users. I might have still commented about that, except I didn't notice it, in particular. Your comments and his reaction are what I noticed.

My general position is that by not warning users (and especially administrators) of problematic behavior, we enable it and ultimately lead the user down the rosy path to ruin -- besides the damage that accumulates in the mean time. Wikis don't go back and fix these things, usually.

In my first arbitration on Wikipedia, the Committee only admonished me about one thing: not escalating quickly. I thought that really funny, because I was not quick, because I attempted to engage the administrator's friends, to encourage them to warn him. That took time. What I was warning about was not controversial, in fact, the violations of policy were blatant and clear. The case was actually open and shut. And still they would not warn their friend. They thought I was "grandstanding" because I mentioned that the future was watching. The future is always watching!

Now, back to Fastily. He has not responded to my last comment.[2] He has no obligation to respond. I will assume he read it. This is of the nature of a warning, and was so titled. That is all carefully considered. This is a (mild) escalation from your warnings. It is a bit more visible if the matter becomes important. I've suggested to Fastily that he may ignore comments that make him feel uncomfortable. That is greatly superior to his blanking of them, unless they are true vandalism.

He has now asked you not to edit his user talk page. That's questionable, since he's an active administrator. I prefer to give him some time to reflect before confronting this. Eventually, we may bring this up for him. If he responds unsatisfactorily, we can consult the administrative community, let me put it that way. Let's assume that Fastily is intelligent, when not run by his reactivity. He will reform his behavior, if that is necessary.

What he should know is that his talk page is watched. Every wiki action may be watched, but that one is relatively routine. His response so far, to me, has been civil. He explained himself, and that revealed a great deal; among other things, it confirms what you wrote above. My approach is not to condemn him and certainly not to harass him; we see other users making that grevious error: they think an admin is "wrong" so they badger him and demand response and repeatedly post. We are not going to do that. You will respect his request not to edit his user talk page. Instead of doing that, if you have a concern, you will engage other users. The generic way to do that is on a noticeboard; if you file a noticeboard request where, ordinarily, it would be superior to ping the admin himself, you will simply note that restriction, and so you will be seeking assistance in an alternate way. You may also ping me, or any other user not banned from his talk page.

There is always a way to do what is ultimately legitimate. If we drop our own reactivity, i.e., the idea that there is something Wrong with this administrator, we will find the way, it's predictable.

But, I can imagine: "If there is nothing wrong with him, why are we even concerned?" We are concerned because we see something is missing, the presence of which would make a difference, and we are standing for that. This is how I've been trained. It works. --Abd (talk) 16:35, 11 April 2015 (UTC)

• Thanks for the reply. From everything I have read ARBCOM's decisions can be strange and counter-intuitive. Geo Swan (talk) 18:49, 11 April 2015 (UTC)

They can. It's a setup in the structure. There have been arbitrators who realized the problem, but who were unable to do anything about it. This happens when communities develop as Wikipedia developed, they can get stuck in what seemed to work at the beginning, that becomes difficult to change later. I can tell stories....

Now, back to our topic here. First of all, the deletion by Fastily was completely proper, it was a basic speedy deletion based on a no-license template placed on the file. You correctly warned (gently) the user about his incivility on user talk:Fastily. However, you then suggested going to an undeletion request, without having investigated the facts. I assume that Fastily would have responded to a polite request from the same user, especially with an apology (as he did make with a ping to Fastily.) But the response would probably have been to inform the user of the deletion reason. It was very simple, this was standard Commons process. A user who does this kind of work had placed a tag on the file indicating license was missing, and the uploading user was notified. In fact, that uploading user does not have email enabled, and has not edited anywhere since March 27, while the file was tagged on March 30. If a file is tagged for missing license, and the tag is not removed within, I think 7 days, the file is deleted. It is almost-bot. It isn't done by bot because the admin will presumably look to see that the license field doesn't have a license. You pointed to the deletion log for Fastily. That will show what he's doing. If you don't realize the situation with missing-license tags and how Commons must handle that, you might think he's a crazy deletionist.

Here is Fastily's deletion log for April 8.[3]. 419 deletion log entries in one day. What, is he mad?

Perhaps. That's a complicated question, eh? Look at that log. He started out with 14 undeletions in 1 minute, at 05:16. He is either using a semi-automated tool or is faster than I've ever been able to be in tests for repetitive editing (I've investigated the limits and 14 per minute is high. Bursts of ten per minute is not difficult.) Key: the edits must be repetitive and they must be set up in some way. These undeletions were accumulated from OTRS. No decision to make with them. He also has delegated followup to a bot, FastilyClone. This is what FastilyClone did immediately with one of the undeletions: [4]. It removed a speedy deletion tag that had been placed there for missing permission.

Then Fastily started to handle tagged files. The first deletions were for copyvio -- probably missing permissions, from files where it is believed that permission is needed. I count 33 deletions like this at 5:21. Fastily is way up there in edit rate. The only decision being made here is telling a semiautomated editor to "delete every page with a standing copyvio tag meeting certain conditions." I notice that it's been three days since these deletions, and none of these pages have been undeleted. Later, we can look at the link and see what has reappeared. But this must be understood.

These are all files with a tag that informs anyone looking at the page that it is going to be deleted, and copyvio files are deleted on sight, and I'm not sure about details. The files we are concerned with were not deleted for copyvio

At 5:25 he starts on No permission, no license, or no source files. These have all been tagged for seven days. Normally, the users will have been notified of the tagging, as happened with the three files here. He deletes 282 files, then he deletes the categories he has been working from. Those categories are created by the tags, automatically. We could almost say that no human has looked at the files, after the tagging. He does not have time to see much, if he is paying any attention at all. the file deletions end at 5:29, so total elapsed time is no more than five minutes. That is over fifty files per minute.

Now, this must be understood. The vast majority of these deletions are harmless at worst. Notice the deletion reason: 05:25, 8 April 2015 Fastily deleted page File:Alice in Arm-Chair.jpg (No license since 30 March 2015: you may re-upload the file, but please include a license tag) (global usage; delinker log). They all say that, except that some say "permission" and some say "source" instead of "license."

That deletion reason is then shown when CommonsDelinker removes the links from a Wikipedia article. To fix this, just upload the file again with the necessary information! Yes, you could ask the administrator to undelete, but if you have uploaded the file, which takes more total labor? And if you don't know what to put in the field, you ask.

But users frequently don't understand the process. Further, if you do upload the file again, and it's deleted again, you can take some flak. It shouldn't happen, a file that has been deleted with that reason should not create a reason to sanction the user, unless the user has simply reuploaded with no effort to deal with the deletion reason.

There are flaws and missing support for users in the Commons process, but the problem is not an administrator like Fastily, who was just following policy and procedure here.

The administrative pages can be murder, sometimes. A user can go there and end up blocked. You sent this user to COM:REFUND without knowing the circumstances. Next time, do your homework! The Undeletion page can bring on a lot of hostile attention, sometimes. I'm wary of going there. I will, but only when I have all my ducks in a row, and I have a stonewalling deleting admin, and no way around it (i.e., someone else to ask). This is what the user put there: a claim that the files were "incorrectly deleted." In fact, they were deleted correctly, and any file in that condition would be deleted, it is totally routine. You had not paid attention to the deletion reason, which was not copyright violation, it was purely formal. So the user argued that the file was indeed PD. As it was.

Notice that Yann actually restored the files, and added the PD-old tag -- as the user could have added -- then redeleted when he realized another problem: they were poorer resolution scans than other files that already existed.

Now, Yann could have simply left the files in place, he didn't do that. That could have saved the user from needing to change the filename on en.wiki. Commons does not always consider that. However, as can be seen from the discussion, someone should delete all the duplicate files anyway. There is a bot which goes around cross-wiki that can rename files. But this gets beyond my pay grade.

I think the user is okay, he's just got a bit of egg on his face, it will come out in the wash. He wanted to improve the project, rescue the files that he thought were improperly deleted. If you look at his user page, you'll see that he has a bit of a chip on his shoulder about Commons. That's not unusual at all, Commons can, indeed, be arcane and difficult. But this part of it is routine and not difficult. Especially if users are supported and guided.

So this part I want to commend: attempting to guide the user. When we do that, we will make mistakes, I understand that. I make lots of them. The problem was largely in a quick assumption that Fastily had erred. What LX told you, you could have seen for yourself. (Great that you thanked LX, by the way.)

I am still learning my way around Commons. The main thing I've identified here, to work on, is routine incivility, tolerated. I think it's possible to develop some consensus on this. The biggest issue, I think, is that most think of it an an intractable problem, they are in despair over doing anything about it. It's not intractable, and it won't go away by itself. The generic wiki problem is that people think that if there is some behavior that harms the community, the thing to do is block the user. It's understandable, but totally naive. I have seen the results of failure to enforce civility policy, and the results of it being enforced in a naive way, and of it being enforced in a supportive way. Supportive enforcement reduces loss of users from toxic environment, and reduces loss of users banned for being uncivil, because incivility breeds incivility. I've been short-blocked for incivility. I thanked the administrator. Why not? Don't I want the environment to be civil? Did it matter if I was actually uncivil or not? Why would it matter? Only in an environment that is toxic would it matter, where any alleged offense is taken as a proof of bad character. Clean block log? This must be a good user! Make him an admin! User with a long block log jaywalks? Throw the book at him! Bad User! Can't Learn!

No, incivility offenses can indicate passion and caring. So warn and guide. Don't punish.

But I came to Commons in February to assist a Wikiversity user whose files were being decimated. My first task was to get him to simmer down and shut up, because his very natural reactions were making it all worse, and he was headed for a block. I believe that nearly all of his files were legitimate, but handling this may actually take some policy/guideline changes, so I'm working on that. (And the results may help hundreds or thousands of users, I do not have narrow horizons.) He will also need to go through OTRS for some files .... and he's disappeared. He's almost eighty, he just stopped responding abruptly to email. I hope he's okay.... I dug up his university phone number -- he is still a professor -- and called. No response yet. --Abd (talk) 23:08, 11 April 2015 (UTC)

File:Tallships in Toronto harbour, just before dusk, 2013 06 20 -g.JPG

File:Tallships in Toronto harbour, just before dusk, 2013 06 20 -g.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 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!

197.164.47.11 17:08, 11 May 2015 (UTC)

• This nomination is obvious vandalism. Secondarywaltz (talk) 19:18, 11 May 2015 (UTC)

File:ISN 00696 military commission -- Appointing Authority stays hearings until further notice--other commissions litigation can proceed.pdf

File:ISN 00696 military commission -- Appointing Authority stays hearings until further notice--other commissions litigation can proceed.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 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!

Ellin Beltz (talk) 15:13, 19 May 2015 (UTC)

Bird's-eye view

Hallo, hi noted you reverted a lot of changes in categorization i've done. I though that that category was a little confusing, being too much similar to some of its mother cateogries (like aerial photographs, or high angle shots/views from above). Being this term used principally for paints, drawings and so on i removed some files from them tentatively. If you have some better ideas on organize files please let's discuss. Regards. --Ciaurlec (talk) 10:51, 28 May 2015 (UTC)

Firstly i have to thank you for citing me the discussion page: i'm used to control on disussion pages of the categories, but you have to agree that it's quite difficult for someone who doesn't partecipate to it to recover such discussion. I arrived on that category because i'm interested on cartography, and on aerial photographs, intending "all the files shooted vertically", (and so useful for cartographic purposes). "Bird's-eye view" (it:Prospettiva aerea) it's a common term used in architechtural drawing, and in the old maps, well before shooting. It's interesting to discover how german and dutch languages uses it in the same way even for photographies, even if theese aren't shot by an airplane; it's even funny to discover too how a "worm's-eye view" existed! Probably the two proposals mades by Jim henderson, point the sense of that discussion. I agree with the second one, being suitable for me the fact of considering it as a part of the wider category Category:Wiews, who does'n treat only about photography (shots, photographic effects, or film techniques), but more about perspective. Another fact is probably to separate files related to drawings, maps and so on by the photos. Possibly categories as Category:Bird's-eye views of Burgerweeshuis (Amsterdam)‎ and Category:Bird's-eye views of animals‎ should be have some different paths, having in common only the angle of perspective. --Ciaurlec (talk) 15:55, 28 May 2015 (UTC)

File:Nakasuk Elementary School, Iqaluit, Nunavut, Canada.jpg

File:Nakasuk Elementary School, Iqaluit, Nunavut, Canada.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 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!

Rcsprinter123 (talk) 12:34, 30 May 2015 (UTC)

Copyright status: File:Streetcars in congested traffic in Kansas City.jpg

This media may be deleted.

Thanks for uploading File:Streetcars in congested traffic in Kansas City.jpg. I notice that the file page either doesn't contain enough information about the license or it contains contradictory information about the license, so the copyright status is unclear. If you created this file yourself, then you must provide a valid copyright tag. For example, you can tag it with {{self|GFDL|cc-by-sa-all}} to release it under the multi-license GFDL plus Creative Commons Attribution-ShareAlike All-version license or you can tag it with {{PD-self}} to release it into the public domain. (See Commons:Copyright tags for the full list of license tags that you can use.) If you did not create the file yourself or if it is a derivative of another work that is possibly subject to copyright protection, then you must specify where you found it (e.g. usually a link to the web page where you got it), you must provide proof that it has a license that is acceptable for Commons (e.g. usually a link to the terms of use for content from that page), and you must add an appropriate license tag. If you did not create the file yourself and the specific source and license information is not available on the web, you must obtain permission through the OTRS system and follow the procedure described there. Note that any unsourced or improperly licensed files will be deleted one week after they have been marked as lacking proper information, as described in criteria for speedy deletion. If you have uploaded other files, please confirm that you have provided the proper information for those files, too. If you have any questions about licenses please ask at Commons:Village pump/Copyright or see our help pages. Thank you.

Use of the PD template requires evidence that a photo was published before 1923 (not merely taken before 1923), and the book you have cited as the source for this photo was published in 2002. Steve Morgan (talk) 08:43, 2 June 2015 (UTC)

Copyright status: File:In 1916 an 'interurban' streetcar line ran from Kansas City to Lawrence Kansas.jpg

This media may be deleted.

Thanks for uploading File:In 1916 an 'interurban' streetcar line ran from Kansas City to Lawrence Kansas.jpg. I notice that the file page either doesn't contain enough information about the license or it contains contradictory information about the license, so the copyright status is unclear. If you created this file yourself, then you must provide a valid copyright tag. For example, you can tag it with {{self|GFDL|cc-by-sa-all}} to release it under the multi-license GFDL plus Creative Commons Attribution-ShareAlike All-version license or you can tag it with {{PD-self}} to release it into the public domain. (See Commons:Copyright tags for the full list of license tags that you can use.) If you did not create the file yourself or if it is a derivative of another work that is possibly subject to copyright protection, then you must specify where you found it (e.g. usually a link to the web page where you got it), you must provide proof that it has a license that is acceptable for Commons (e.g. usually a link to the terms of use for content from that page), and you must add an appropriate license tag. If you did not create the file yourself and the specific source and license information is not available on the web, you must obtain permission through the OTRS system and follow the procedure described there. Note that any unsourced or improperly licensed files will be deleted one week after they have been marked as lacking proper information, as described in criteria for speedy deletion. If you have uploaded other files, please confirm that you have provided the proper information for those files, too. If you have any questions about licenses please ask at Commons:Village pump/Copyright or see our help pages. Thank you.

Use of the PD template requires evidence that a photo was published before 1923 (not merely taken before 1923), and the book you have cited as the source for this photo was published in 2002. Steve Morgan (talk) 08:47, 2 June 2015 (UTC)

File:In 1916 an 'interurban' streetcar line ran from Kansas City to Lawrence Kansas.jpg

File:In 1916 an 'interurban' streetcar line ran from Kansas City to Lawrence Kansas.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 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!

JuTa 20:42, 2 June 2015 (UTC)

Metrolinx not MetroLinx

"Metrolinx, an agency of the Government of Ontario under the Metrolinx Act, 2006, was created to improve the coordination and integration of all modes of transportation in the Greater Toronto and Hamilton Area." See http://www.metrolinx.com/en/aboutus/about_us_index.aspx There is no evidence presented and it is just wrong. Secondarywaltz (talk) 03:24, 8 June 2015 (UTC)

Questionable uploads from Flickr

You are correct in questioning the authorship of File:Mandy Moore's New Album - Live Performance (3590622457).jpg and File:Mandy Moore Sings "Love To Love Me Back" (3591431394).jpg, because they are watermarked. They are screenshots from http://soundcheck.walmart.com/Artists/mandy-moore/2009 which is © 2015 Wal-Mart Stores, Inc. I have tagged them as copyright violations. Thanks for catching that. Secondarywaltz (talk) 16:12, 11 June 2015 (UTC)

File:Mandy Moore's New Album - Live Performance (3590622457).jpg

File:Mandy Moore's New Album - Live Performance (3590622457).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 find Commons:Copyright rules useful. You can ask questions about Commons policies in Commons:Help desk. The file you added has been deleted. If you believe that the deletion was not in accordance with policy, you may request undeletion. Wikimedia Commons takes copyright violations very seriously and persistent violators will be blocked from editing.

 

Secondarywaltz (talk) 16:13, 11 June 2015 (UTC)

File:Mandy Moore Sings "Love To Love Me Back" (3591431394).jpg

File:Mandy Moore Sings "Love To Love Me Back" (3591431394).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 find Commons:Copyright rules useful. You can ask questions about Commons policies in Commons:Help desk. The file you added has been deleted. If you believe that the deletion was not in accordance with policy, you may request undeletion. Wikimedia Commons takes copyright violations very seriously and persistent violators will be blocked from editing.

 

Secondarywaltz (talk) 16:14, 11 June 2015 (UTC)

Copyright status: File:USCGC Raymond Evans uses her stern-launching ramp to deploy her pursuit boat.jpg

This media may be deleted.

Thanks for uploading File:USCGC Raymond Evans uses her stern-launching ramp to deploy her pursuit boat.jpg. I notice that the file page either doesn't contain enough information about the license or it contains contradictory information about the license, so the copyright status is unclear. If you created this file yourself, then you must provide a valid copyright tag. For example, you can tag it with {{self|GFDL|cc-by-sa-all}} to release it under the multi-license GFDL plus Creative Commons Attribution-ShareAlike All-version license or you can tag it with {{PD-self}} to release it into the public domain. (See Commons:Copyright tags for the full list of license tags that you can use.) If you did not create the file yourself or if it is a derivative of another work that is possibly subject to copyright protection, then you must specify where you found it (e.g. usually a link to the web page where you got it), you must provide proof that it has a license that is acceptable for Commons (e.g. usually a link to the terms of use for content from that page), and you must add an appropriate license tag. If you did not create the file yourself and the specific source and license information is not available on the web, you must obtain permission through the OTRS system and follow the procedure described there. Note that any unsourced or improperly licensed files will be deleted one week after they have been marked as lacking proper information, as described in criteria for speedy deletion. If you have uploaded other files, please confirm that you have provided the proper information for those files, too. If you have any questions about licenses please ask at Commons:Village pump/Copyright or see our help pages. Thank you.

JuTa 21:52, 13 June 2015 (UTC)

• I've fixed that. Secondarywaltz (talk) 22:02, 13 June 2015 (UTC)

Bots

You are receiving this message because a technical change may affect a bot, gadget, or user script you have been using. The breaking change involves API calls. This change has been planned for two years. The WMF will start making this change on 30 June 2015. A partial list of affected bots can be seen here: https://lists.wikimedia.org/pipermail/wikitech-l/2015-June/081931.html This includes all bots that are using pywikibot compat. Some of these bots have already been fixed. However, if you write user scripts or operate a bot that uses the API, then you should check your code, to make sure that it will not break.

What, exactly, is breaking? The "default continuation mode" for action=query requests to api.php will be changing to be easier for new coders to use correctly. To find out whether your script or bot may be affected, then search the source code (including any frameworks or libraries) for the string "query-continue". If that is not present, then the script or bot is not affected. In a few cases, the code will be present but not used. In that case, the script or bot will continue working.

This change will be part of 1.26wmf12. It will be deployed to test wikis (including mediawiki.org) on 30 June, to non-Wikipedias (such as Wiktionary) on 1 July, and to all Wikipedias on 2 July 2015.

If your bot or script is receiving the warning about this upcoming change (as seen at https://www.mediawiki.org/w/api.php?action=query&list=allpages ), it's time to fix your code!

• The simple solution is to simply include the "rawcontinue" parameter with your request to continue receiving the raw continuation data (example <https://www.mediawiki.org/w/api.php?action=query&list=allpages&rawcontinue=1>). No other code changes should be necessary.
• Or you could update your code to use the simplified continuation documented at https://www.mediawiki.org/wiki/API:Query#Continuing_queries (example <https://www.mediawiki.org/w/api.php?action=query&list=allpages&continue=>), which is much easier for clients to implement correctly.

Either of the above solutions may be tested immediately, you'll know it works because you stop seeing the warning.

Do you need help with your own bot or script? Ask questions in e-mail on the mediawiki-api or wikitech-l mailing lists. Volunteers at m:Tech or w:en:WP:Village pump (technical) or w:en:Wikipedia:Bot owners' noticeboard may also be able to help you.

Are you using someone else's gadgets or user scripts? Most scripts are not affected. To find out if a script you use needs to be updated, then post a note at the discussion page for the gadget or the talk page of the user who originally made the script. Whatamidoing (WMF) (talk) 19:03, 17 June 2015 (UTC)

File:Tugboat M. R. Kane pushes a barge, 2014 11 28 (1) (15900517631).jpg

File:Tugboat M. R. Kane pushes a barge, 2014 11 28 (1) (15900517631).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 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!

/St1995 09:58, 29 June 2015 (UTC)

Notice of upload removal

Dear Geo Swan:

The Wikimedia Foundation (“Wikimedia”) has taken down content that you posted at File:Baffin_Island_fjord_Nunavut.jpg due to Wikimedia’s receipt of a validly formulated notice that your posted content was infringing an existing copyright. When someone sends us a validly formulated notice of copyright infringement, the Digital Millennium Copyright Act (“DMCA”) Section (c)(1)(C) requires Wikimedia to take the content down, and to notify you that we have removed that content. This notice, by itself, does not mean that the party requesting that the content be taken down are suing you. The party requesting the take down might only be interested in removing the content from our site.

What Can You Do?

You are not obligated to take any action. However, if you feel that your content does not infringe upon any copyrights, you may contest the take down request by submitting a ‘counter notice’ to Wikimedia. Before doing so, you should understand your legal position, and you may wish to consult with an attorney. If you choose to submit a counter notice, the alleged copyright holder can either refuse to contest the counter notice or decide to file a lawsuit against you to restrain Wikimedia from re-posting the content. Please note that Wikimedia will not be a party to any legal action that arises from you sending a counter notice, and that Wikimedia is unable to provide you with legal advice.

Filing a Counter Notice

If you choose to submit a counter notice, you must send a letter asking Wikimedia to restore your content to legal@wikimedia.org, or to our service processor at the following address: Wikimedia Foundation, c/o CT Corporation System, 818 West Seventh Street, Los Angeles, California, 90017. The letter must comply with DMCA standards, set out in Section (g)(3)(A-D), and must contain the following:

• A link to where the content was before we took it down and a description of the material that was removed;
• A statement, under penalty of perjury, that you have a good faith belief that the content was removed or disabled as a result of mistake or misidentification of the material to be removed or disabled;
• Your name, address, and phone number;
• If your address is in the United States, a statement that says “I consent to the jurisdiction of the Federal District Court for the district where my address is located, and I will accept service of process from the person who complained about the content I posted”; alternatively, if your address is outside the United States, a statement that says “I agree to accept service of process in any jurisdiction where the Wikimedia Foundation can be found, and I will accept service of process from the person who complained about the content I posted”; and finally,
• Your physical or electronic signature.

Pursuant to the DMCA, Wikimedia must inform the alleged copyright holder that you sent us a counter notice, and give the alleged copyright holder a copy of the counter notice. The alleged copyright holder will then have fourteen (14) business days to file a lawsuit against you to restrain Wikimedia from reposting the content. If Wikimedia does not receive proper notification that the alleged copyright holder has initiated such a lawsuit against you, we will repost your content within ten (10) to fourteen (14) business days.

Miscellaneous

As a matter of policy and under appropriate circumstances, Wikimedia will block the accounts of repeat infringers as provided by Section 512(i)(1)(A) of the DMCA.

If you would like to learn more about Wikimedia’s policies, please refer to the Wikimedia Terms of Use, available at Terms of use, and the Wikimedia Legal Policies, available at m:Legal/Legal_Policies. More information on DMCA compliance may also be found at:

• http://www.chillingeffects.org/dmca512/faq
• https://www.eff.org/issues/dmca
• http://www.copyright.gov/onlinesp/

Wikimedia appreciates your support. Please do not hesitate to contact us if you have any questions regarding this notice.

Sincerely, Jalexander--WMF 23:47, 30 June 2015 (UTC)

@Geo Swan: Hi Geo Swan, I saw your note on my talk page and have copied the information template below. I'm not 100% sure if we should include the template itself in all of the posts but I'll talk that over as an option with the team. What your note did point out to me however is what we should DEFINETLY have as a link in the post is a link to the actual takedown letter we got that resulted in the notice. That takedown almost always has information about both the file and the people claiming ownership and you have a right to see that. We already post links to it on the Village Pump and the DMCA Noticeboard but for some reason it wasn't linked here and that's an oversight. You can find it on foundation wiki at DMCA_Baffin_Island_fjord and the linked file on that page. Jalexander--WMF 22:38, 1 July 2015 (UTC)

{{Information
|Description=Baffin Island fjord Nunavut
|Source=[http://www.flickr.com/photos/readmuchmor/5430190695/ Baffin Island fjord Nunavut]
|Date=2011-02-09 06:25
|Author=[http://www.flickr.com/people/57442335@N02 Chris Toombes] from Canada
|Permission=
|other_versions=
}}

Copyright status: File:The Wire Issue33v17.pdf

This media may be deleted.

Thanks for uploading File:The Wire Issue33v17.pdf. I notice that the file page either doesn't contain enough information about the license or it contains contradictory information about the license, so the copyright status is unclear. If you created this file yourself, then you must provide a valid copyright tag. For example, you can tag it with {{self|GFDL|cc-by-sa-all}} to release it under the multi-license GFDL plus Creative Commons Attribution-ShareAlike All-version license or you can tag it with {{PD-self}} to release it into the public domain. (See Commons:Copyright tags for the full list of license tags that you can use.) If you did not create the file yourself or if it is a derivative of another work that is possibly subject to copyright protection, then you must specify where you found it (e.g. usually a link to the web page where you got it), you must provide proof that it has a license that is acceptable for Commons (e.g. usually a link to the terms of use for content from that page), and you must add an appropriate license tag. If you did not create the file yourself and the specific source and license information is not available on the web, you must obtain permission through the OTRS system and follow the procedure described there. Note that any unsourced or improperly licensed files will be deleted one week after they have been marked as lacking proper information, as described in criteria for speedy deletion. If you have uploaded other files, please confirm that you have provided the proper information for those files, too. If you have any questions about licenses please ask at Commons:Village pump/Copyright or see our help pages. Thank you.

No required license templates were detected at this file page. Please correct it, or if you have any questions please check my FAQ or contact me on my talk page. Yours sincerely, Jarekt (talk) 17:15, 10 July 2015 (UTC)

File:The Wire Issue27v14.pdf

File:The Wire Issue27v14.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 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!

92.213.15.188 17:11, 12 July 2015 (UTC)

File:Amtrak Cascades train from Seattle WA to Vancouver BC.jpg

File:Amtrak Cascades train from Seattle WA to Vancouver BC.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 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!

Pi.1415926535 (talk) 18:41, 14 July 2015 (UTC)

Category:Edmund_P._Giambastiani_Jr.

Category:Edmund_P._Giambastiani_Jr. has been listed at Commons:Categories for discussion so that the community can discuss ways in which it should be changed. We would appreciate it if you could go to voice your opinion about this at its entry. If you created this category, please note that the fact that it has been proposed for discussion 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. If the category is up for deletion because it has been superseded, consider the notion that although the category may be deleted, your hard work (which we all greatly appreciate) lives on in the new category. In all cases, please do not take the category discussion personally. It is never intended as such. Thank you!

Gbawden (talk) 14:28, 23 July 2015 (UTC)

Road-rail vehicles cat update

Regarding your message to me back in late April 2015, you should know that I've removed the last five images incorrectly categories as Category:Road-rail vehicles. I hope none of them are falsely given this category again, and I wonder how they could've been categorized this way in the first place. ----DanTD (talk) 21:06, 24 July 2015 (UTC)

Copyright status: File:141215 U ISN324 GOVERNMENTS UNCLASSIFIED SUMMARY PUBLIC.pdf

This media may be deleted.

Thanks for uploading File:141215 U ISN324 GOVERNMENTS UNCLASSIFIED SUMMARY PUBLIC.pdf. I notice that the file page either doesn't contain enough information about the license or it contains contradictory information about the license, so the copyright status is unclear. If you created this file yourself, then you must provide a valid copyright tag. For example, you can tag it with {{self|GFDL|cc-by-sa-all}} to release it under the multi-license GFDL plus Creative Commons Attribution-ShareAlike All-version license or you can tag it with {{PD-self}} to release it into the public domain. (See Commons:Copyright tags for the full list of license tags that you can use.) If you did not create the file yourself or if it is a derivative of another work that is possibly subject to copyright protection, then you must specify where you found it (e.g. usually a link to the web page where you got it), you must provide proof that it has a license that is acceptable for Commons (e.g. usually a link to the terms of use for content from that page), and you must add an appropriate license tag. If you did not create the file yourself and the specific source and license information is not available on the web, you must obtain permission through the OTRS system and follow the procedure described there. Note that any unsourced or improperly licensed files will be deleted one week after they have been marked as lacking proper information, as described in criteria for speedy deletion. If you have uploaded other files, please confirm that you have provided the proper information for those files, too. If you have any questions about licenses please ask at Commons:Village pump/Copyright or see our help pages. Thank you.

And also:

• File:150210 U ISN324 DETAINEE WRITTEN SUBMISSION PUBLIC.pdf
• File:150212 U ISN324 Opening Statements of Detainees Representatives PUBLIC.pdf
• File:150303 U ISN324 PUBLIC SESSION PUBLIC.PDF
• File:150303 U ISN324 TRANSCRIPT OF DETAINEE SESSION PUBLIC.PDF
• File:150417 U ISN324 FINAL DETERMINATION PUBLIC.pdf

Yours sincerely, Magog the Ogre (talk) (contribs) 04:01, 25 July 2015 (UTC)

@Magog the Ogre: Hmmm. All six have the license tag {{PD-USGov-Military}} on them. Could you please explain, in more detail, the nature of your licensing concern? All six were prepared by US Government staff, for Periodic Review Boards. The officials who sit on these boards are also Federal employees. That makes this material PD, from its creation. Geo Swan (talk) 16:03, 25 July 2015 (UTC)

Please fix the wrong brackets inside information template and remove nld tags. Please use proper headers on description page. See my change to this file. --Denniss (talk) 16:09, 25 July 2015 (UTC)

•  Done Geo Swan (talk) 18:30, 25 July 2015 (UTC)

Category:Construction at One The Esplanade

Something is lost ;-) Wieralee (talk) 10:41, 4 August 2015 (UTC)

Discussion on my page

---

László (talk) 14:42, 8 August 2015 (UTC)

National Museum of the U.S. Navy

You seem to have an interest in pictures of ships, so here https://www.flickr.com/photos/127906254@N06/ is the National Museum of the U.S. Navy collection on Flickr with lots of PD images. Secondarywaltz (talk) 11:31, 12 August 2015 (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. 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:Convite -- para que gosta de pescar, mergulhar, sonhar, namorar... ficar perto de Deus..jpg

Yours sincerely, JCP (a.k.a. John Carlo Pagcaliwagan) 22:39, 24 August 2015 (UTC)

File:Bat! (3841200259).jpg

File:Bat! (3841200259).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 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!

Stas (talk) 19:02, 13 September 2015 (UTC)

Category:Rock_of_Ages,_Elora,_Ontario

Category:Rock_of_Ages,_Elora,_Ontario has been listed at Commons:Categories for discussion so that the community can discuss ways in which it should be changed. We would appreciate it if you could go to voice your opinion about this at its entry. If you created this category, please note that the fact that it has been proposed for discussion 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. If the category is up for deletion because it has been superseded, consider the notion that although the category may be deleted, your hard work (which we all greatly appreciate) lives on in the new category. In all cases, please do not take the category discussion personally. It is never intended as such. Thank you!

Themightyquill (talk) 14:09, 20 September 2015 (UTC)

File:Streetcars in congested traffic in Kansas City.jpg

File:Streetcars in congested traffic in Kansas City.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 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!

JuTa 20:31, 21 September 2015 (UTC)

Not Peter Street

Your uploads File:Pano on Peter Street 2015 09 23 (1) (21049073743).jpg, File:Pano on Peter Street 2015 09 23 (2) (21482256608).jpg and File:Pano on Peter Street 2015 09 23 (3) (21669848185).jpg are actually of Simcoe Street. Your back was to the RBC Centre and you were facing east. Additionally File:Pano on Front Street, 2015 09 23 (1) (21049133193).jpg was taken at the corner of Simcoe Street. I will leave you to rename them in your own style and add the proper Categories. Secondarywaltz (talk) 16:39, 24 September 2015 (UTC)

Featured Picture Nomination

Hello. I just wanted to let you know that the image Diphaglossa gayi, f, side, chile 2014-08-04-18.17.33 ZS PMax (14732584979).jpg, which was created or uploaded by you, has been nominated for featured picture status; have a look at the nomination page. Thank you and good luck! --Christian Ferrer (talk) 05:32, 21 October 2015 (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. 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:Casa Poporului, Romania's House of Parliament.jpg

Yours sincerely, INeverCry 08:10, 28 October 2015 (UTC)

File:Romanian Academy.jpg

File:Romanian Academy.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 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!

Jmabel ! talk 05:03, 8 November 2015 (UTC)

File:A Romanian Television station.jpg

File:A Romanian Television station.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 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!

Jmabel ! talk 17:55, 8 November 2015 (UTC)

File:Fostul CSP -- The old State Committee for Planning.jpg

File:Fostul CSP -- The old State Committee for Planning.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 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!

Jmabel ! talk 17:57, 8 November 2015 (UTC)

File:Bucuresti flats -c -- Victoriei Square, Bucharest, Romania.jpg

File:Bucuresti flats -c -- Victoriei Square, Bucharest, Romania.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 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!

Jmabel ! talk 18:03, 8 November 2015 (UTC)

File:Bucuresti flats -a.jpg

File:Bucuresti flats -a.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 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!

Jmabel ! talk 18:04, 8 November 2015 (UTC)

File:Blocks of flats in Bucurestii Noi, Bucharest, Romania -b.jpg

File:Blocks of flats in Bucurestii Noi, Bucharest, Romania -b.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 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!

Jmabel ! talk 18:05, 8 November 2015 (UTC)

Hello, Geo Swan. You have new messages at Jmabel's talk page. You may remove this notice at any time by removing the {{Talkback}} or {{Tb}} template.

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. 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:Tanks crossing Westminster Bridge on Peace Day -- 1919-07-19.jpg

Yours sincerely, -mattbuck (Talk) 09:10, 13 November 2015 (UTC)

License Review

To ensure there are not any future problems, I have tagged a couple of your recent uploads for LicenseReview. This simply means that an independent Reviewer will confirm the status of the File, at the time you uploaded it, just like Flickreview. There are not any problems. Secondarywaltz (talk) 20:01, 13 November 2015 (UTC)

• Thanks. Pixabay.com plans to only host PD images. I don't know whether it would be appropriate to add it to the list of sites flickrrreview trusts. I completely agree that the licenses of these images should be reviewed. Thanks for tagging them. Now that you looked it up, I'll add the tag when I upload additional images from that site. Cheers! Geo Swan (talk) 20:58, 13 November 2015 (UTC)

File:PCC Streetcars riding high at at Ashmont station..jpg

File:PCC Streetcars riding high at at Ashmont station..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 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!

Pi.1415926535 (talk) 17:27, 30 November 2015 (UTC)

Category:Nawn's_Yard

Category:Nawn's_Yard has been listed at Commons:Categories for discussion so that the community can discuss ways in which it should be changed. We would appreciate it if you could go to voice your opinion about this at its entry. If you created this category, please note that the fact that it has been proposed for discussion 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. If the category is up for deletion because it has been superseded, consider the notion that although the category may be deleted, your hard work (which we all greatly appreciate) lives on in the new category. In all cases, please do not take the category discussion personally. It is never intended as such. Thank you!

Pi.1415926535 (talk) 20:44, 2 December 2015 (UTC)

File:Coast-guard boat dec 2015.jpg

File:Coast-guard boat dec 2015.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 find Commons:Copyright rules useful. You can ask questions about Commons policies in Commons:Help desk. The file you added has been deleted. If you believe that the deletion was not in accordance with policy, you may request undeletion. Wikimedia Commons takes copyright violations very seriously and persistent violators will be blocked from editing.

 

Secondarywaltz (talk) 03:00, 9 December 2015 (UTC)

Copyright status: File:Ambassador bridge in Detroit, from Pixabay.jpg

This media may be deleted.

Thanks for uploading File:Ambassador bridge in Detroit, from Pixabay.jpg. I notice that the file page either doesn't contain enough information about the license or it contains contradictory information about the license, so the copyright status is unclear. If you created this file yourself, then you must provide a valid copyright tag. For example, you can tag it with {{self|GFDL|cc-by-sa-all}} to release it under the multi-license GFDL plus Creative Commons Attribution-ShareAlike All-version license or you can tag it with {{PD-self}} to release it into the public domain. (See Commons:Copyright tags for the full list of license tags that you can use.) If you did not create the file yourself or if it is a derivative of another work that is possibly subject to copyright protection, then you must specify where you found it (e.g. usually a link to the web page where you got it), you must provide proof that it has a license that is acceptable for Commons (e.g. usually a link to the terms of use for content from that page), and you must add an appropriate license tag. If you did not create the file yourself and the specific source and license information is not available on the web, you must obtain permission through the OTRS system and follow the procedure described there. Note that any unsourced or improperly licensed files will be deleted one week after they have been marked as lacking proper information, as described in criteria for speedy deletion. If you have uploaded other files, please confirm that you have provided the proper information for those files, too. If you have any questions about licenses please ask at Commons:Village pump/Copyright or see our help pages. Thank you.

Secondarywaltz (talk) 20:48, 10 December 2015 (UTC)

• All images from Pixabay are {{cc0}} Geo Swan (talk) 02:59, 11 December 2015 (UTC)

Files in Category:Duplicate Boston Transit Commission files

Files in Category:Duplicate Boston Transit Commission files 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 gallery, 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. 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!

Hey, I've created a deletion category for about 250 files that you uploaded a while back. They're all exact duplicates of previous uploads of yours; I think you may have run a script twice or something. (The original uploads won't be touched - they're all useful files). Please don't think I'm trying to harass you or anything; this is just technical maintenance that I came across the need for while uploading old BTC reports. Cheers, Pi.1415926535 (talk) 00:25, 20 December 2015 (UTC)

Copyright status: File:Early plans for the Flower class corvette.jpg

This media may be deleted.

Thanks for uploading File:Early plans for the Flower class corvette.jpg. I notice that the file page either doesn't contain enough information about the license or it contains contradictory information about the license, so the copyright status is unclear. If you created this file yourself, then you must provide a valid copyright tag. For example, you can tag it with {{self|GFDL|cc-by-sa-all}} to release it under the multi-license GFDL plus Creative Commons Attribution-ShareAlike All-version license or you can tag it with {{PD-self}} to release it into the public domain. (See Commons:Copyright tags for the full list of license tags that you can use.) If you did not create the file yourself or if it is a derivative of another work that is possibly subject to copyright protection, then you must specify where you found it (e.g. usually a link to the web page where you got it), you must provide proof that it has a license that is acceptable for Commons (e.g. usually a link to the terms of use for content from that page), and you must add an appropriate license tag. If you did not create the file yourself and the specific source and license information is not available on the web, you must obtain permission through the OTRS system and follow the procedure described there. Note that any unsourced or improperly licensed files will be deleted one week after they have been marked as lacking proper information, as described in criteria for speedy deletion. If you have uploaded other files, please confirm that you have provided the proper information for those files, too. If you have any questions about licenses please ask at Commons:Village pump/Copyright or see our help pages. Thank you.

Yours sincerely, Magog the Ogre (talk) (contribs) 05:26, 23 December 2015 (UTC)

• @Magog the Ogre: -- As the official plans for a Royal Naval vessel, shouldn't this image have been under crown copyright? It is my understanding that the crown copyright images fall into the public domain more quickly than images under a regular copyright, so this image should have been in the public domain for decades. Geo Swan (talk) 18:54, 25 December 2015 (UTC)

  Perhaps, but it still needs to be tagged. {{PD-UKGov}}. Magog the Ogre (talk) (contribs) 21:15, 25 December 2015 (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. 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:Pumpkin storm trooper.jpg

Yours sincerely, .     Jim . . . . (Jameslwoodward) (talk to me) 21:37, 27 December 2015 (UTC)

Wrong source attribution

You have tagged your recent uploads with Toronto Public Library (Template:TPL) when they are all obviously from the City of Toronto Archives and you should have used Template:COTA-image. Secondarywaltz (talk) 19:25, 6 January 2016 (UTC)

• I'll check that. Geo Swan (talk) 21:43, 6 January 2016 (UTC)

File:Taken by a passing by tuber.jpg

File:Taken by a passing by tuber.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 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!

Underwaterbuffalo (talk) 08:10, 12 January 2016 (UTC)

File:Guantanamo -- motivated seller!.jpg

File:Guantanamo -- motivated seller!.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 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!

Motopark (talk) 15:58, 1 February 2016 (UTC)

File:The Wire Issue14v18.pdf

File:The Wire Issue14v18.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 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!

Sealle (talk) 17:37, 7 February 2016 (UTC)

A double standard

You objected when I abstracted your reflection from one of your photos, but you seem to think it's acceptable to upload personal full face pictures of Jason Paris. There is not really any context to those images that is not covered by his others. Have you advised him about this? Secondarywaltz (talk) 16:01, 14 February 2016 (UTC)

• Since you raised this, I will advise him -- once I figure out which image(s) you are talking about.

No, I don't think uploading someone's full face self-portrait is a double standard, when I didn't want my (tiny) reflection cropped, and posted. Mr Paris seems to be an experienced uploader, who understands that a CC license release the image for re-use -- who made the conscious decision he was okay with that. I think his flickstream has multiple images of him. The (tiny) image you found of me, on the other hand, was so tiny I overlooked it, when I uploaded the image you cropped it from. Its appearance here was not due to me making a decision I was okay with it being published, it was due to my overlooking it when I published the much larger image.

I never meant to imply that you did anything wrong with cropping the image, and publishing it, naming me. If I didn't have a safety concern I probably would have found it flattering. I've received online threats, so, I think I was taking a sensible precaution.

Note: I acknowledge the license I applied to the image was unrevocable. When I asked for the image it was cropped from to be deleted, I should have done so calling upon the tradition that properly licensed images do get deleted, when the uploader or subject of an image offers a coherent reason for why they are requesting its deletion as a courtesy. It's been a couple of years now. I don't remember. Rather than go look it up, if you think I fell short of that acknowledgement, and you feel I should apologize for that, may I offer you that specific apology.

But, no, I honestly don't think this is an instance of a double standard.

Cheers! Geo Swan (talk) 22:41, 15 February 2016 (UTC)

Category:Beaver Island Harbor Light

I have reverted your changing this to a redirect. There are two lights on Beaver Island, at opposite ends of the island, about 11 miles apart. I don't see any reason why they should be in the same category.

I also removed your addition of Category:Lighthouses in Michigan from Category:Beaver Island Head Lighthouse as overcat -- two of the existing categories are children or grand-children of Category:Lighthouses in Michigan. .     Jim . . . . (Jameslwoodward) (talk to me) 15:30, 1 April 2016 (UTC)

File:Ferry Bouquet on the Great Lakes.jpg

You uploaded a picture of a ship with this name and then uploaded a new image - of a ship with a different name. I suspect this was a simple misnaming. Is there an easy way to untangle these? Rmhermen (talk) 04:16, 2 April 2016 (UTC)

•  Done thanks! Geo Swan (talk) 04:25, 2 April 2016 (UTC)

File:Santiago de Cuba (20361759644).jpg

File:Santiago de Cuba (20361759644).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 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!

2003:45:5C16:F601:1DE3:D973:C9E7:65A3 15:31, 12 April 2016 (UTC)

File:Louvre Pyramide HDR2 (7027649473).jpg

File:Louvre Pyramide HDR2 (7027649473).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 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!

Thesupermat (talk) 14:05, 25 April 2016 (UTC)

File:A pedestrian bridge in the Mirabad valley.jpg

File:A pedestrian bridge in the Mirabad valley.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 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!

Lowpassing (talk) 10:39, 20 May 2016 (UTC)

File:Australian and Afghan soldiers wait for US Black Hawks.jpg

File:Australian and Afghan soldiers wait for US Black Hawks.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 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!

Lowpassing (talk) 10:45, 20 May 2016 (UTC)

File:Soldiers disembark from a blackhawk.jpg

File:Soldiers disembark from a blackhawk.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 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!

Lowpassing (talk) 10:46, 20 May 2016 (UTC)

File:ISAF soldier and Afghan boy -a.jpg

File:ISAF soldier and Afghan boy -a.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 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!

Lowpassing (talk) 11:13, 20 May 2016 (UTC)

File:Crossing an irrigation canal in Oruzgan.jpg

File:Crossing an irrigation canal in Oruzgan.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 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!

Lowpassing (talk) 11:14, 20 May 2016 (UTC)

File:Children greet Soldiers in Tarin Kowt.jpg

File:Children greet Soldiers in Tarin Kowt.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 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!

124.168.233.233 14:02, 2 July 2016 (UTC)

Category move request

Hi Geo, I've removed your requested move template as with the greatest of respect no one's going to move over 5100+ images especially when it's a user category,
Your best bet is to install Help:Gadget-Cat-a-lot and basically move the category and images yourself, (Had there been something like 500 images I wouldn't have an issue but 51000 is a lot and I'm assuming the admins agree as admins who have been moving cats haven't touched this either),
Thanks and Happy editing/uploading, –Davey2010^Talk 18:20, 6 July 2016 (UTC)

Davey2010 Clarification please.

Computers are stupid, and there are a limited number of tasks they can do, without supervision. But moving files from one category to another falls among the limited number of tasks they can do, without supervision. It is precisely because there were a large number of files that I requested robot assistance.

I have been using catalot for years. Recently I started using flick2commons. It allows one to specify a category that applies to a batch of uploads, prior to the upload. But neither catalot, or any equivalent, is available, when using it. So, when one uses it, and you specify a slightly wrong spelling of a real category, or a redirect to a real category, that batch ends up in a non-existent directory, or a redirect that should be empty.

Us human should do what we are good at. Our robot slaves should assist us in the ways that help us. This is an instance where a robot slave could take care of a very onerous, robot task. Do you know how long it takes for a human to move 5,000 images? If you can move 3 per minute, you can move something like 200 per hour. 24 person hours.

Us humans are creative. We have judgment. A robot given too little supervision can really screw things up. A competent human, who knows what they are doing, should notice, pretty early, when they made a mistake.

I've uploaded thousands and thousands of images, and used hundreds of categories -- far too many for me to have remembered the exact spelling of every single one. Sadly, many category names are deeply counter-intuitive. So easing me of the burden of remembering trivial details, like the exact spelling of category names, seems to me to be an appropriate use of robot slaves. On my previous computer I had installed the clippings add-on, which remembered details like this, for me. But the browser on my new computer doesn't support it. So, I am reduced to guessing, or taking a long detour to double-check, The name of the category for my own images. Category:Photos by Geo Swan is the most obvious name, the most memorable, the most likely to free me of this particular cognitive burden.

You haven't offered a policy based reason, or technically based reason, why you declined my request. All you seem to be saying is that you don't think other administrators would help. If that is all you meant, are you really sure that is a good reason? Geo Swan (talk) 19:34, 6 July 2016 (UTC)

• I re-read your note. You seemed to be denigrating the importance of this request because is was a User category request. I google myself, occasionally. I do so because I have stalkers, not because I am vain. But I see that outsiders, third parties, do download and re-use my images, as per some examples I'll list. I don't maintain Category:Photographs by Geo Swan out of vanity. I do so because third parties who found one of my images useful may find others useful. I really hope you weren't trying to say that my request wasn't worth complying with, because it was only a User category request.

• Infuture if you want a bot to move them you'd need to visit User talk:CommonsDelinker/commands/Category moves (I've set it up so you won't have to do anything this time), The template you used as far as I know is for anyone except bots, No that's not what I'm saying at all and I shouldn't of said it as actually regardless of what the category is no one would ever move a category that contained over 5100+, Thanks, –Davey2010^Talk 20:48, 6 July 2016 (UTC)

Because third parties download and use images I took and uploaded, then a category grouping and listing images I took is useful in the same way free images taken by professional photographers are important. Geo Swan (talk) 20:38, 6 July 2016 (UTC)

1. http://www.thescopeatryerson.ca/en/thescope/news/837/The-Scope-News-February-29-2016.htm
2. http://www.canadianmanufacturing.com/financing/crosslinx-consortium-closes-5-3b-eglinton-crosstown-deal-151818/
3. http://outbreaknewstoday.com/toronto-patrons-of-big-carrot-organic-juice-bar-warned-of-possible-hepatitis-a-exposure-37290/
4. http://www.boomsbeat.com/articles/4037/20140515/a-look-into-the-histocial-massey-hall-photos.htm
5. http://www.babelplex.com/permit-required-confined-spaces-do-you-know-what-they-are/
6. http://www.bdcnetwork.com/construction-put-place-enjoyed-healthy-gains-2014
7. http://www.railwaypages.com/ontario-railway-station-museums
8. http://www.elijahlist.com/words/display_word.html?ID=15808
9. http://terremotos2014.blogspot.ca/2016/04/tercer-terremoto-cerca-del-antartico.html
10. http://www.travelin.pl/jezioro-athabaska-2
11. http://www.ehow.com/how_6170267_calculate-antipode.html

Copyright status: File:Commissioning the USCGC Winslow Griesser.jpg

This media may be deleted.

Thanks for uploading File:Commissioning the USCGC Winslow Griesser.jpg. I notice that the file page either doesn't contain enough information about the license or it contains contradictory information about the license, so the copyright status is unclear. If you created this file yourself, then you must provide a valid copyright tag. For example, you can tag it with {{self|GFDL|cc-by-sa-all}} to release it under the multi-license GFDL plus Creative Commons Attribution-ShareAlike All-version license or you can tag it with {{PD-self}} to release it into the public domain. (See Commons:Copyright tags for the full list of license tags that you can use.) If you did not create the file yourself or if it is a derivative of another work that is possibly subject to copyright protection, then you must specify where you found it (e.g. usually a link to the web page where you got it), you must provide proof that it has a license that is acceptable for Commons (e.g. usually a link to the terms of use for content from that page), and you must add an appropriate license tag. If you did not create the file yourself and the specific source and license information is not available on the web, you must obtain permission through the OTRS system and follow the procedure described there. Note that any unsourced or improperly licensed files will be deleted one week after they have been marked as lacking proper information, as described in criteria for speedy deletion. If you have uploaded other files, please confirm that you have provided the proper information for those files, too. If you have any questions about licenses please ask at Commons:Village pump/Copyright or see our help pages. Thank you.

No required license templates were detected at this file page. Please correct it, or if you have any questions please check my FAQ or contact me on my talk page. Yours sincerely, Jarekt (talk) 17:04, 14 July 2016 (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. 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:The Wire Issue-23v11 -a.pdf

And also:

• File:The Wire Issue-25v11.pdf
• File:The Wire Issue00v2.pdf
• File:The Wire Issue01v15.pdf
• File:The Wire Issue01v16.pdf
• File:The Wire Issue01v17.pdf
• File:The Wire Issue01v18.pdf
• File:The Wire Issue01v19.pdf
• File:The Wire Issue01v2.pdf
• File:The Wire Issue01v3.pdf
• File:The Wire Issue01v4.pdf
• File:The Wire Issue01v5.pdf
• File:The Wire Issue01v6.pdf
• File:The Wire Issue01v7.pdf
• File:The Wire Issue02v15.pdf
• File:The Wire Issue02v16.pdf
• File:The Wire Issue02v17.pdf
• File:The Wire Issue02v18.pdf
• File:The Wire Issue02v19.pdf
• File:The Wire Issue02v2.pdf
• File:The Wire Issue02v3.pdf
• File:The Wire Issue02v4.pdf
• File:The Wire Issue02v5.pdf
• File:The Wire Issue02v6.pdf
• File:The Wire Issue02v7.pdf
• File:The Wire Issue03v15.pdf
• File:The Wire Issue03v16.pdf
• File:The Wire Issue03v18.pdf
• File:The Wire Issue03v19.pdf
• File:The Wire Issue03v2.pdf
• File:The Wire Issue03v3.pdf
• File:The Wire Issue03v5.pdf
• File:The Wire Issue03v6.pdf
• File:The Wire Issue03v7.pdf
• File:The Wire Issue04v15.pdf
• File:The Wire Issue04v16.pdf
• File:The Wire Issue04v17.pdf
• File:The Wire Issue04v18.pdf
• File:The Wire Issue04v19.pdf
• File:The Wire Issue04v2.pdf
• File:The Wire Issue04v3.pdf
• File:The Wire Issue04v4.pdf
• File:The Wire Issue04v5.pdf
• File:The Wire Issue04v6.pdf
• File:The Wire Issue04v7.pdf
• File:The Wire Issue05v15.pdf
• File:The Wire Issue05v16.pdf
• File:The Wire Issue05v17.pdf
• File:The Wire Issue05v18.pdf
• File:The Wire Issue05v19.pdf
• File:The Wire Issue05v2.pdf
• File:The Wire Issue05v3.pdf
• File:The Wire Issue05v4.pdf
• File:The Wire Issue05v5.pdf
• File:The Wire Issue05v6.pdf
• File:The Wire Issue05v7.pdf
• File:The Wire Issue06v15.pdf
• File:The Wire Issue06v16.pdf
• File:The Wire Issue06v17.pdf
• File:The Wire Issue06v18.pdf
• File:The Wire Issue06v19.pdf
• File:The Wire Issue06v3.pdf
• File:The Wire Issue06v4.pdf
• File:The Wire Issue06v5.pdf
• File:The Wire Issue06v6.pdf
• File:The Wire Issue06v7.pdf
• File:The Wire Issue07v15.pdf
• File:The Wire Issue07v16.pdf
• File:The Wire Issue07v17.pdf
• File:The Wire Issue07v18.pdf
• File:The Wire Issue07v2.pdf
• File:The Wire Issue07v3.pdf
• File:The Wire Issue07v4.pdf
• File:The Wire Issue07v5.pdf
• File:The Wire Issue07v6.pdf
• File:The Wire Issue07v7.pdf
• File:The Wire Issue08v15.pdf
• File:The Wire Issue08v16.pdf
• File:The Wire Issue08v17.pdf
• File:The Wire Issue08v18.pdf
• File:The Wire Issue08v19.pdf
• File:The Wire Issue08v2.pdf
• File:The Wire Issue08v3.pdf
• File:The Wire Issue08v4.pdf
• File:The Wire Issue08v5.pdf
• File:The Wire Issue08v6.pdf
• File:The Wire Issue08v7.pdf
• File:The Wire Issue09v15.pdf
• File:The Wire Issue09v16.pdf
• File:The Wire Issue09v17.pdf
• File:The Wire Issue09v18.pdf
• File:The Wire Issue09v19.pdf
• File:The Wire Issue09v2.pdf
• File:The Wire Issue09v3.pdf
• File:The Wire Issue09v4.pdf
• File:The Wire Issue09v5.pdf
• File:The Wire Issue09v6.pdf
• File:The Wire Issue09v7.pdf
• File:The Wire Issue10v10.pdf
• File:The Wire Issue10v11.pdf
• File:The Wire Issue10v12.pdf
• File:The Wire Issue10v14.pdf
• File:The Wire Issue10v15.pdf
• File:The Wire Issue10v16.pdf
• File:The Wire Issue10v17.pdf
• File:The Wire Issue10v18.pdf
• File:The Wire Issue10v2.pdf
• File:The Wire Issue10v3.pdf
• File:The Wire Issue10v4.pdf
• File:The Wire Issue10v5.pdf
• File:The Wire Issue10v6.pdf
• File:The Wire Issue10v7.pdf
• File:The Wire Issue10v8.pdf
• File:The Wire Issue10v9.pdf
• File:The Wire Issue11v10.pdf
• File:The Wire Issue11v11.pdf
• File:The Wire Issue11v12.pdf
• File:The Wire Issue11v14.pdf
• File:The Wire Issue11v15.pdf
• File:The Wire Issue11v16.pdf
• File:The Wire Issue11v17.pdf
• File:The Wire Issue11v18.pdf
• File:The Wire Issue11v19.pdf
• File:The Wire Issue11v2.pdf
• File:The Wire Issue11v3.pdf
• File:The Wire Issue11v4.pdf
• File:The Wire Issue11v5.pdf
• File:The Wire Issue11v6.pdf
• File:The Wire Issue11v7.pdf
• File:The Wire Issue11v8.pdf
• File:The Wire Issue11v9.pdf
• File:The Wire Issue12v10.pdf
• File:The Wire Issue12v11.pdf
• File:The Wire Issue12v12.pdf
• File:The Wire Issue12v14.pdf
• File:The Wire Issue12v15.pdf
• File:The Wire Issue12v16.pdf
• File:The Wire Issue12v17.pdf
• File:The Wire Issue12v19.pdf
• File:The Wire Issue12v2.pdf
• File:The Wire Issue12v3.pdf
• File:The Wire Issue12v4.pdf
• File:The Wire Issue12v5.pdf
• File:The Wire Issue12v6.pdf
• File:The Wire Issue12v7.pdf
• File:The Wire Issue12v8.pdf
• File:The Wire Issue12v9.pdf
• File:The Wire Issue13v10.pdf
• File:The Wire Issue13v11.pdf
• File:The Wire Issue13v12.pdf
• File:The Wire Issue13v14.pdf
• File:The Wire Issue13v15.pdf
• File:The Wire Issue13v16.pdf
• File:The Wire Issue13v17.pdf
• File:The Wire Issue13v18.pdf
• File:The Wire Issue13v19.pdf
• File:The Wire Issue13v2.pdf
• File:The Wire Issue13v3.pdf
• File:The Wire Issue13v4.pdf
• File:The Wire Issue13v5.pdf
• File:The Wire Issue13v6.pdf
• File:The Wire Issue13v7.pdf
• File:The Wire Issue13v8.pdf
• File:The Wire Issue13v9.pdf
• File:The Wire Issue14v10.pdf
• File:The Wire Issue14v11.pdf
• File:The Wire Issue14v12.pdf
• File:The Wire Issue14v14.pdf
• File:The Wire Issue14v15.pdf
• File:The Wire Issue14v16.pdf
• File:The Wire Issue14v17.pdf
• File:The Wire Issue14v19.pdf
• File:The Wire Issue14v2.pdf
• File:The Wire Issue14v3.pdf
• File:The Wire Issue14v4.pdf
• File:The Wire Issue14v5.pdf
• File:The Wire Issue14v6.pdf
• File:The Wire Issue14v7.pdf
• File:The Wire Issue14v8.pdf
• File:The Wire Issue14v9.pdf
• File:The Wire Issue15v10.pdf
• File:The Wire Issue15v11.pdf
• File:The Wire Issue15v12.pdf
• File:The Wire Issue15v14.pdf
• File:The Wire Issue15v15.pdf
• File:The Wire Issue15v16.pdf
• File:The Wire Issue15v17.pdf
• File:The Wire Issue15v18.pdf
• File:The Wire Issue15v19.pdf
• File:The Wire Issue15v2.pdf
• File:The Wire Issue15v3.pdf
• File:The Wire Issue15v4.pdf
• File:The Wire Issue15v5.pdf
• File:The Wire Issue15v6.pdf
• File:The Wire Issue15v7.pdf
• File:The Wire Issue15v8.pdf
• File:The Wire Issue15v9.pdf
• File:The Wire Issue16v10.pdf
• File:The Wire Issue16v11.pdf
• File:The Wire Issue16v12.pdf
• File:The Wire Issue16v14.pdf
• File:The Wire Issue16v15.pdf
• File:The Wire Issue16v16.pdf
• File:The Wire Issue16v17.pdf
• File:The Wire Issue16v18.pdf
• File:The Wire Issue16v2.pdf
• File:The Wire Issue16v3.pdf
• File:The Wire Issue16v4.pdf
• File:The Wire Issue16v5.pdf
• File:The Wire Issue16v6.pdf
• File:The Wire Issue16v7.pdf
• File:The Wire Issue16v8.pdf
• File:The Wire Issue16v9.pdf
• File:The Wire Issue17v10.pdf
• File:The Wire Issue17v11.pdf
• File:The Wire Issue17v12.pdf
• File:The Wire Issue17v14.pdf
• File:The Wire Issue17v15.pdf
• File:The Wire Issue17v16.pdf
• File:The Wire Issue17v17.pdf
• File:The Wire Issue17v18.pdf
• File:The Wire Issue17v19.pdf
• File:The Wire Issue17v2.pdf
• File:The Wire Issue17v3.pdf
• File:The Wire Issue17v4.pdf
• File:The Wire Issue17v5.pdf
• File:The Wire Issue17v6.pdf
• File:The Wire Issue17v7.pdf
• File:The Wire Issue17v8.pdf
• File:The Wire Issue17v9.pdf
• File:The Wire Issue18v10.pdf
• File:The Wire Issue18v11.pdf
• File:The Wire Issue18v12.pdf
• File:The Wire Issue18v14.pdf
• File:The Wire Issue18v15.pdf
• File:The Wire Issue18v16.pdf
• File:The Wire Issue18v17.pdf
• File:The Wire Issue18v18.pdf
• File:The Wire Issue18v2.pdf
• File:The Wire Issue18v3.pdf
• File:The Wire Issue18v4.pdf
• File:The Wire Issue18v5.pdf
• File:The Wire Issue18v6.pdf
• File:The Wire Issue18v7.pdf
• File:The Wire Issue18v8.pdf
• File:The Wire Issue18v9.pdf
• File:The Wire Issue19v10.pdf
• File:The Wire Issue19v11.pdf
• File:The Wire Issue19v12.pdf
• File:The Wire Issue19v14.pdf
• File:The Wire Issue19v15.pdf
• File:The Wire Issue19v16.pdf
• File:The Wire Issue19v17.pdf
• File:The Wire Issue19v18.pdf
• File:The Wire Issue19v2.pdf
• File:The Wire Issue19v3.pdf
• File:The Wire Issue19v4.pdf
• File:The Wire Issue19v5.pdf
• File:The Wire Issue19v6.pdf
• File:The Wire Issue19v7.pdf
• File:The Wire Issue19v8.pdf
• File:The Wire Issue19v9.pdf
• File:The Wire Issue1v10.pdf
• File:The Wire Issue1v11.pdf
• File:The Wire Issue1v12.pdf
• File:The Wire Issue1v8.pdf
• File:The Wire Issue1v9.pdf
• File:The Wire Issue20v10.pdf
• File:The Wire Issue20v11.pdf
• File:The Wire Issue20v12.pdf
• File:The Wire Issue20v14.pdf
• File:The Wire Issue20v15.pdf
• File:The Wire Issue20v16.pdf
• File:The Wire Issue20v17.pdf
• File:The Wire Issue20v18.pdf
• File:The Wire Issue20v2.pdf
• File:The Wire Issue20v3.pdf
• File:The Wire Issue20v4.pdf
• File:The Wire Issue20v5.pdf
• File:The Wire Issue20v6.pdf
• File:The Wire Issue20v7.pdf
• File:The Wire Issue20v8.pdf
• File:The Wire Issue20v9.pdf
• File:The Wire Issue21v10.pdf
• File:The Wire Issue21v11.pdf
• File:The Wire Issue21v12.pdf
• File:The Wire Issue21v14.pdf
• File:The Wire Issue21v15.pdf
• File:The Wire Issue21v16.pdf
• File:The Wire Issue21v17.pdf
• File:The Wire Issue21v18.pdf
• File:The Wire Issue21v2.pdf
• File:The Wire Issue21v3.pdf
• File:The Wire Issue21v4.pdf
• File:The Wire Issue21v5.pdf
• File:The Wire Issue21v6.pdf
• File:The Wire Issue21v7.pdf
• File:The Wire Issue21v8.pdf
• File:The Wire Issue21v9.pdf
• File:The Wire Issue22v10.pdf
• File:The Wire Issue22v11.pdf
• File:The Wire Issue22v12.pdf
• File:The Wire Issue22v14.pdf
• File:The Wire Issue22v15.pdf
• File:The Wire Issue22v16.pdf
• File:The Wire Issue22v17.pdf
• File:The Wire Issue22v18.pdf
• File:The Wire Issue22v2.pdf
• File:The Wire Issue22v3.pdf
• File:The Wire Issue22v4.pdf
• File:The Wire Issue22v5.pdf
• File:The Wire Issue22v6.pdf
• File:The Wire Issue22v7.pdf
• File:The Wire Issue22v8.pdf
• File:The Wire Issue22v9.pdf
• File:The Wire Issue23v10.pdf
• File:The Wire Issue23v11.pdf
• File:The Wire Issue23v12.pdf
• File:The Wire Issue23v14.pdf
• File:The Wire Issue23v15.pdf
• File:The Wire Issue23v16.pdf
• File:The Wire Issue23v17.pdf
• File:The Wire Issue23v18.pdf
• File:The Wire Issue23v2.pdf
• File:The Wire Issue23v3.pdf
• File:The Wire Issue23v4.pdf
• File:The Wire Issue23v5.pdf
• File:The Wire Issue23v6.pdf
• File:The Wire Issue23v7.pdf
• File:The Wire Issue23v8.pdf
• File:The Wire Issue23v9.pdf
• File:The Wire Issue24v10.pdf
• File:The Wire Issue24v11.pdf
• File:The Wire Issue24v12.pdf
• File:The Wire Issue24v14.pdf
• File:The Wire Issue24v15.pdf
• File:The Wire Issue24v16.pdf
• File:The Wire Issue24v17.pdf
• File:The Wire Issue24v18.pdf
• File:The Wire Issue24v2.pdf
• File:The Wire Issue24v3.pdf
• File:The Wire Issue24v4.pdf
• File:The Wire Issue24v5.pdf
• File:The Wire Issue24v6.pdf
• File:The Wire Issue24v7.pdf
• File:The Wire Issue24v8.pdf
• File:The Wire Issue24v9.pdf
• File:The Wire Issue25v10.pdf
• File:The Wire Issue25v12.pdf
• File:The Wire Issue25v15.pdf
• File:The Wire Issue25v16.pdf
• File:The Wire Issue25v17.pdf
• File:The Wire Issue25v18.pdf
• File:The Wire Issue25v2.pdf
• File:The Wire Issue25v3.pdf
• File:The Wire Issue25v4.pdf
• File:The Wire Issue25v5.pdf
• File:The Wire Issue25v6.pdf
• File:The Wire Issue25v7.pdf
• File:The Wire Issue25v8.pdf
• File:The Wire Issue25v9.pdf
• File:The Wire Issue26v10.pdf
• File:The Wire Issue26v11.pdf
• File:The Wire Issue26v12.pdf
• File:The Wire Issue26v15.pdf
• File:The Wire Issue26v16.pdf
• File:The Wire Issue26v17.pdf
• File:The Wire Issue26v18.pdf
• File:The Wire Issue26v3.pdf
• File:The Wire Issue26v4.pdf
• File:The Wire Issue26v5.pdf
• File:The Wire Issue26v6.pdf
• File:The Wire Issue26v7.pdf
• File:The Wire Issue26v8.pdf
• File:The Wire Issue26v9.pdf
• File:The Wire Issue27v10.pdf
• File:The Wire Issue27v11.pdf
• File:The Wire Issue27v12.pdf
• File:The Wire Issue27v14.pdf
• File:The Wire Issue27v15.pdf
• File:The Wire Issue27v16.pdf
• File:The Wire Issue27v17.pdf
• File:The Wire Issue27v18.pdf
• File:The Wire Issue27v3.pdf
• File:The Wire Issue27v4.pdf
• File:The Wire Issue27v5.pdf
• File:The Wire Issue27v6.pdf
• File:The Wire Issue27v7.pdf
• File:The Wire Issue27v8.pdf
• File:The Wire Issue27v9.pdf
• File:The Wire Issue28v10.pdf
• File:The Wire Issue28v11.pdf
• File:The Wire Issue28v12.pdf
• File:The Wire Issue28v14.pdf
• File:The Wire Issue28v15.pdf
• File:The Wire Issue28v16.pdf
• File:The Wire Issue28v17.pdf
• File:The Wire Issue28v18.pdf
• File:The Wire Issue28v3.pdf
• File:The Wire Issue28v4.pdf
• File:The Wire Issue28v5.pdf
• File:The Wire Issue28v6.pdf
• File:The Wire Issue28v7.pdf
• File:The Wire Issue28v8.pdf
• File:The Wire Issue28v9.pdf
• File:The Wire Issue29v10.pdf
• File:The Wire Issue29v11.pdf
• File:The Wire Issue29v12.pdf
• File:The Wire Issue29v14.pdf
• File:The Wire Issue29v15.pdf
• File:The Wire Issue29v16.pdf
• File:The Wire Issue29v17.pdf
• File:The Wire Issue29v18.pdf
• File:The Wire Issue29v3.pdf
• File:The Wire Issue29v4.pdf
• File:The Wire Issue29v5.pdf
• File:The Wire Issue29v6.pdf
• File:The Wire Issue29v7.pdf
• File:The Wire Issue29v8.pdf
• File:The Wire Issue29v9.pdf
• File:The Wire Issue2v10.pdf
• File:The Wire Issue2v11.pdf
• File:The Wire Issue2v12.pdf
• File:The Wire Issue2v8.pdf
• File:The Wire Issue2v9.pdf
• File:The Wire Issue30v10.pdf
• File:The Wire Issue30v11.pdf
• File:The Wire Issue30v12.pdf
• File:The Wire Issue30v14.pdf
• File:The Wire Issue30v15.pdf
• File:The Wire Issue30v16.pdf
• File:The Wire Issue30v17.pdf
• File:The Wire Issue30v18.pdf
• File:The Wire Issue30v3.pdf
• File:The Wire Issue30v4.pdf
• File:The Wire Issue30v5.pdf
• File:The Wire Issue30v7.pdf
• File:The Wire Issue30v8.pdf
• File:The Wire Issue30v9.pdf
• File:The Wire Issue31v10.pdf
• File:The Wire Issue31v11.pdf
• File:The Wire Issue31v12.pdf
• File:The Wire Issue31v14.pdf
• File:The Wire Issue31v15.pdf
• File:The Wire Issue31v16.pdf
• File:The Wire Issue31v17.pdf
• File:The Wire Issue31v18.pdf
• File:The Wire Issue31v3.pdf
• File:The Wire Issue31v4.pdf
• File:The Wire Issue31v5.pdf
• File:The Wire Issue31v6.pdf
• File:The Wire Issue31v7.pdf
• File:The Wire Issue31v8.pdf
• File:The Wire Issue31v9.pdf
• File:The Wire Issue32v10.pdf
• File:The Wire Issue32v11.pdf
• File:The Wire Issue32v12.pdf
• File:The Wire Issue32v14.pdf
• File:The Wire Issue32v15.pdf
• File:The Wire Issue32v16.pdf
• File:The Wire Issue32v17.pdf
• File:The Wire Issue32v18.pdf
• File:The Wire Issue32v3.pdf
• File:The Wire Issue32v4.pdf
• File:The Wire Issue32v5.pdf
• File:The Wire Issue32v6.pdf
• File:The Wire Issue32v7.pdf
• File:The Wire Issue32v8.pdf
• File:The Wire Issue32v9.pdf
• File:The Wire Issue33v10.pdf
• File:The Wire Issue33v11.pdf
• File:The Wire Issue33v12.pdf
• File:The Wire Issue33v14.pdf
• File:The Wire Issue33v15.pdf
• File:The Wire Issue33v16.pdf
• File:The Wire Issue33v17.pdf
• File:The Wire Issue33v18.pdf
• File:The Wire Issue33v3.pdf
• File:The Wire Issue33v4.pdf
• File:The Wire Issue33v5.pdf
• File:The Wire Issue33v7.pdf
• File:The Wire Issue33v8.pdf
• File:The Wire Issue33v9.pdf
• File:The Wire Issue34v10.pdf
• File:The Wire Issue34v11.pdf
• File:The Wire Issue34v12.pdf
• File:The Wire Issue34v14.pdf
• File:The Wire Issue34v15.pdf
• File:The Wire Issue34v16.pdf
• File:The Wire Issue34v17.pdf
• File:The Wire Issue34v18.pdf
• File:The Wire Issue34v3.pdf
• File:The Wire Issue34v4.pdf
• File:The Wire Issue34v5.pdf
• File:The Wire Issue34v6.pdf
• File:The Wire Issue34v7.pdf
• File:The Wire Issue34v8.pdf
• File:The Wire Issue34v9.pdf
• File:The Wire Issue35v10.pdf
• File:The Wire Issue35v11.pdf
• File:The Wire Issue35v12.pdf
• File:The Wire Issue35v14.pdf
• File:The Wire Issue35v15.pdf
• File:The Wire Issue35v16.pdf
• File:The Wire Issue35v17.pdf
• File:The Wire Issue35v18.pdf
• File:The Wire Issue35v3.pdf
• File:The Wire Issue35v4.pdf
• File:The Wire Issue35v5.pdf
• File:The Wire Issue35v6.pdf
• File:The Wire Issue35v7.pdf
• File:The Wire Issue35v8.pdf
• File:The Wire Issue35v9.pdf
• File:The Wire Issue36v10.pdf
• File:The Wire Issue36v11.pdf
• File:The Wire Issue36v12.pdf
• File:The Wire Issue36v14.pdf
• File:The Wire Issue36v15.pdf
• File:The Wire Issue36v16.pdf
• File:The Wire Issue36v17.pdf
• File:The Wire Issue36v18.pdf
• File:The Wire Issue36v3.pdf
• File:The Wire Issue36v4.pdf
• File:The Wire Issue36v5.pdf
• File:The Wire Issue36v6.pdf
• File:The Wire Issue36v7.pdf
• File:The Wire Issue36v8.pdf
• File:The Wire Issue36v9.pdf
• File:The Wire Issue37v10.pdf
• File:The Wire Issue37v11.pdf
• File:The Wire Issue37v12.pdf
• File:The Wire Issue37v14.pdf
• File:The Wire Issue37v15.pdf
• File:The Wire Issue37v18.pdf
• File:The Wire Issue37v3.pdf
• File:The Wire Issue37v4.pdf
• File:The Wire Issue37v5.pdf
• File:The Wire Issue37v6.pdf
• File:The Wire Issue37v7.pdf
• File:The Wire Issue37v8.pdf
• File:The Wire Issue37v9.pdf
• File:The Wire Issue38v10.pdf
• File:The Wire Issue38v11.pdf
• File:The Wire Issue38v12.pdf
• File:The Wire Issue38v3.pdf
• File:The Wire Issue38v4.pdf
• File:The Wire Issue38v5.pdf
• File:The Wire Issue38v6.pdf
• File:The Wire Issue38v7.pdf
• File:The Wire Issue38v8.pdf
• File:The Wire Issue38v9.pdf
• File:The Wire Issue39v10.pdf
• File:The Wire Issue39v11.pdf
• File:The Wire Issue39v12.pdf
• File:The Wire Issue39v3.pdf
• File:The Wire Issue39v4.pdf
• File:The Wire Issue39v5.pdf
• File:The Wire Issue39v6.pdf
• File:The Wire Issue39v7.pdf
• File:The Wire Issue39v8.pdf
• File:The Wire Issue39v9.pdf
• File:The Wire Issue3v10.pdf
• File:The Wire Issue3v11.pdf
• File:The Wire Issue3v12.pdf
• File:The Wire Issue3v14.pdf
• File:The Wire Issue3v8.pdf
• File:The Wire Issue3v9.pdf
• File:The Wire Issue40v10.pdf
• File:The Wire Issue40v11.pdf
• File:The Wire Issue40v12.pdf
• File:The Wire Issue40v3.pdf
• File:The Wire Issue40v4.pdf
• File:The Wire Issue40v5.pdf
• File:The Wire Issue40v6.pdf
• File:The Wire Issue40v7.pdf
• File:The Wire Issue40v8.pdf
• File:The Wire Issue40v9.pdf
• File:The Wire Issue41v10.pdf
• File:The Wire Issue41v11.pdf
• File:The Wire Issue41v12.pdf
• File:The Wire Issue41v6.pdf
• File:The Wire Issue41v7.pdf
• File:The Wire Issue41v8.pdf
• File:The Wire Issue41v9.pdf
• File:The Wire Issue42v10.pdf
• File:The Wire Issue42v11.pdf
• File:The Wire Issue42v12.pdf
• File:The Wire Issue42v6.pdf
• File:The Wire Issue42v7.pdf
• File:The Wire Issue42v8.pdf
• File:The Wire Issue42v9.pdf
• File:The Wire Issue43v10.pdf
• File:The Wire Issue43v11.pdf
• File:The Wire Issue43v12.pdf
• File:The Wire Issue43v6.pdf
• File:The Wire Issue43v7.pdf
• File:The Wire Issue43v8.pdf
• File:The Wire Issue43v9.pdf
• File:The Wire Issue44v10.pdf
• File:The Wire Issue44v11.pdf
• File:The Wire Issue44v12.pdf
• File:The Wire Issue44v6.pdf
• File:The Wire Issue44v7.pdf
• File:The Wire Issue44v8.pdf
• File:The Wire Issue44v9.pdf
• File:The Wire Issue45v10.pdf
• File:The Wire Issue45v11.pdf
• File:The Wire Issue45v6.pdf
• File:The Wire Issue45v7.pdf
• File:The Wire Issue45v8.pdf
• File:The Wire Issue45v9.pdf
• File:The Wire Issue46v10.pdf
• File:The Wire Issue46v6.pdf
• File:The Wire Issue46v7.pdf
• File:The Wire Issue46v8.pdf
• File:The Wire Issue46v9.pdf
• File:The Wire Issue47v10.pdf
• File:The Wire Issue47v6.pdf
• File:The Wire Issue47v7.pdf
• File:The Wire Issue47v8.pdf
• File:The Wire Issue47v9.pdf
• File:The Wire Issue48v10.pdf
• File:The Wire Issue48v6.pdf
• File:The Wire Issue48v7.pdf
• File:The Wire Issue48v8.pdf
• File:The Wire Issue48v9.pdf
• File:The Wire Issue49v10.pdf
• File:The Wire Issue49v6.pdf
• File:The Wire Issue49v7.pdf
• File:The Wire Issue49v8.pdf
• File:The Wire Issue49v9.pdf
• File:The Wire Issue4v10.pdf
• File:The Wire Issue4v11.pdf
• File:The Wire Issue4v12.pdf
• File:The Wire Issue4v14.pdf
• File:The Wire Issue4v8.pdf
• File:The Wire Issue4v9.pdf
• File:The Wire Issue50v10.pdf
• File:The Wire Issue50v6.pdf
• File:The Wire Issue50v8.pdf
• File:The Wire Issue50v9.pdf
• File:The Wire Issue51v8.pdf
• File:The Wire Issue51v9.pdf
• File:The Wire Issue52v8.pdf
• File:The Wire Issue52v9.pdf
• File:The Wire Issue5v10.pdf
• File:The Wire Issue5v11.pdf
• File:The Wire Issue5v12.pdf
• File:The Wire Issue5v14.pdf
• File:The Wire Issue5v8.pdf
• File:The Wire Issue5v9.pdf
• File:The Wire Issue6v10.pdf
• File:The Wire Issue6v11.pdf
• File:The Wire Issue6v12.pdf
• File:The Wire Issue6v14.pdf
• File:The Wire Issue6v8.pdf
• File:The Wire Issue6v9.pdf
• File:The Wire Issue7v10.pdf
• File:The Wire Issue7v11.pdf
• File:The Wire Issue7v12.pdf
• File:The Wire Issue7v14.pdf
• File:The Wire Issue7v8.pdf
• File:The Wire Issue7v9.pdf
• File:The Wire Issue8v10.pdf
• File:The Wire Issue8v11.pdf
• File:The Wire Issue8v12.pdf
• File:The Wire Issue8v14.pdf
• File:The Wire Issue8v8.pdf
• File:The Wire Issue8v9.pdf
• File:The Wire Issue9v10.pdf
• File:The Wire Issue9v11.pdf
• File:The Wire Issue9v12.pdf
• File:The Wire Issue9v14.pdf
• File:The Wire Issue9v8.pdf
• File:The Wire Issue9v9.pdf
• File:The Wire Issue 01v13.pdf
• File:The Wire Issue 02v13.pdf
• File:The Wire Issue 03v13.pdf
• File:The Wire Issue 04v13.pdf
• File:The Wire Issue 05v13.pdf
• File:The Wire Issue 06v13.pdf
• File:The Wire Issue 07v13.pdf
• File:The Wire Issue 08v13.pdf
• File:The Wire Issue 09v13.pdf
• File:The Wire Issue 10v13.pdf
• File:The Wire Issue 11v13.pdf
• File:The Wire Issue 12v13.pdf
• File:The Wire Issue 13v13.pdf
• File:The Wire Issue 14v13.pdf
• File:The Wire Issue 15v13.pdf
• File:The Wire Issue 16v13.pdf
• File:The Wire Issue 17v13.pdf
• File:The Wire Issue 18v13.pdf
• File:The Wire Issue 19v13.pdf
• File:The Wire Issue 1v14.pdf
• File:The Wire Issue 20v13.pdf
• File:The Wire Issue 21v13.pdf
• File:The Wire Issue 22v13.pdf
• File:The Wire Issue 23v13.pdf
• File:The Wire Issue 24v13.pdf
• File:The Wire Issue 25v13.pdf
• File:The Wire Issue 26v13.pdf
• File:The Wire Issue 27v13.pdf
• File:The Wire Issue 28v13.pdf
• File:The Wire Issue 29v13.pdf
• File:The Wire Issue 2v14.pdf
• File:The Wire Issue 30v13.pdf
• File:The Wire Issue 31v13.pdf
• File:The Wire Issue 32v13.pdf
• File:The Wire Issue 33v13.pdf
• File:The Wire Issue 34v13.pdf
• File:The Wire Issue 35v13.pdf
• File:The Wire Issue 36v13.pdf
• File:The Wire Issue 37v13.pdf
• File:The Wire Issue 38v13.pdf
• File:The Wire Issue 39v13.pdf
• File:The Wire Issue 40v13.pdf
• File:The Wire Issue 41v13.pdf
• File:The Wire Issue 42v13.pdf
• File:The Wire Issue 43v13.pdf
• File:The Wire Issue 44v13.pdf
• File:The Wire Issue 45v13.pdf

Yours sincerely, Josve05a (talk) 02:05, 25 July 2016 (UTC)

Copyright status: File:Buoy tender USCGC Cypress at Guantanamo.jpg

This media may be deleted.

Thanks for uploading File:Buoy tender USCGC Cypress at Guantanamo.jpg. I notice that the file page either doesn't contain enough information about the license or it contains contradictory information about the license, so the copyright status is unclear. If you created this file yourself, then you must provide a valid copyright tag. For example, you can tag it with {{self|GFDL|cc-by-sa-all}} to release it under the multi-license GFDL plus Creative Commons Attribution-ShareAlike All-version license or you can tag it with {{PD-self}} to release it into the public domain. (See Commons:Copyright tags for the full list of license tags that you can use.) If you did not create the file yourself or if it is a derivative of another work that is possibly subject to copyright protection, then you must specify where you found it (e.g. usually a link to the web page where you got it), you must provide proof that it has a license that is acceptable for Commons (e.g. usually a link to the terms of use for content from that page), and you must add an appropriate license tag. If you did not create the file yourself and the specific source and license information is not available on the web, you must obtain permission through the OTRS system and follow the procedure described there. Note that any unsourced or improperly licensed files will be deleted one week after they have been marked as lacking proper information, as described in criteria for speedy deletion. If you have uploaded other files, please confirm that you have provided the proper information for those files, too. If you have any questions about licenses please ask at Commons:Village pump/Copyright or see our help pages. Thank you.

Yours sincerely, Magog the Ogre (talk) (contribs) 04:10, 11 August 2016 (UTC)

File:USS Matagorda after launching, 18 March 1941.jpg

File:USS Matagorda after launching, 18 March 1941.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 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!

Wikicology (talk) 10:45, 24 August 2016 (UTC)

File:USS Matagorda before launching, 18 March 1941.jpg

File:USS Matagorda before launching, 18 March 1941.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 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!

Wikicology (talk) 10:46, 24 August 2016 (UTC)

File:USS Matagorda being launched, 18 March 1941.jpg

File:USS Matagorda being launched, 18 March 1941.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 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!

Wikicology (talk) 10:47, 24 August 2016 (UTC)

File:USS Matagorda (AVP 22) -b.jpg

File:USS Matagorda (AVP 22) -b.jpg is considered to fulfill the criteria for speedy deletion and has been marked on its image description page. The following reason has been specified: This file is a duplicate of the following files: File:File:USS Matagorda AG-122 1942.jpg. If you believe the content does not meet the criteria for speedy deletion, you may request undeletion. 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.

Revent^talk 14:13, 24 August 2016 (UTC)

Copyright status: File:Scott Buschman and Walt Slater celebrate the commissioning of the USCGC Joseph Tezanos.jpg

This media may be deleted.

Thanks for uploading File:Scott Buschman and Walt Slater celebrate the commissioning of the USCGC Joseph Tezanos.jpg. I notice that the file page either doesn't contain enough information about the license or it contains contradictory information about the license, so the copyright status is unclear. If you created this file yourself, then you must provide a valid copyright tag. For example, you can tag it with {{self|GFDL|cc-by-sa-all}} to release it under the multi-license GFDL plus Creative Commons Attribution-ShareAlike All-version license or you can tag it with {{PD-self}} to release it into the public domain. (See Commons:Copyright tags for the full list of license tags that you can use.) If you did not create the file yourself or if it is a derivative of another work that is possibly subject to copyright protection, then you must specify where you found it (e.g. usually a link to the web page where you got it), you must provide proof that it has a license that is acceptable for Commons (e.g. usually a link to the terms of use for content from that page), and you must add an appropriate license tag. If you did not create the file yourself and the specific source and license information is not available on the web, you must obtain permission through the OTRS system and follow the procedure described there. Note that any unsourced or improperly licensed files will be deleted one week after they have been marked as lacking proper information, as described in criteria for speedy deletion. If you have uploaded other files, please confirm that you have provided the proper information for those files, too. If you have any questions about licenses please ask at Commons:Village pump/Copyright or see our help pages. Thank you.

Magog the Ogre (talk) (contribs) 04:56, 28 August 2016 (UTC)

File:Trackmobile (405962993).jpg

File:Trackmobile (405962993).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 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!

Kopiersperre (talk) 09:32, 5 September 2016 (UTC)

Category moves

Hi Geo, Bit random but actually came to say thanks for providing a well thought out reason on the category move request[5] - It's nice to see a request that has been well thought out, well researched and well explained instead of a half arsed which is the norm here, I liked it so much I've even included it in the move-reason box[6] which I've never done for anyone so there's a first for everything :),
Keep up the great work and keep up with the detailed reasons :), Happy editing, –Davey2010^Talk 03:21, 19 September 2016 (UTC)

File tagging File:Bernard Webber's daughter, Pattie Hamilton, stamps the keel of the vessel named after him -b.jpg

This media may be deleted.

Thanks for uploading File:Bernard Webber's daughter, Pattie Hamilton, stamps the keel of the vessel named after him -b.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 send an email with copy of a written permission to OTRS (permissions-commons@wikimedia.org). This also applies if you are the author yourself. Please see this page for more information on how to confirm permission, and Commons:Permission if you would like to understand why we ask for permission when uploading work that is not your own. Unless the permission information is given, the image may be deleted after seven days. Thank you.

 

shizhao (talk) 07:49, 19 September 2016 (UTC)

File source is not properly indicated: File:V Mail Poster WW2.jpg

This media may be deleted.

A file that you have uploaded to Wikimedia Commons, File:V Mail Poster WW2.jpg, is missing information about where it comes from or who created it, which is needed to verify its copyright status. Please edit the file description and add the missing information, or the file may be deleted. If you created the content yourself, enter {{own}} as the source. If you did not add a licensing template, you must add one. You may use, for example, {{self|GFDL|cc-by-sa-all}} or {{Cc-zero}} to release certain rights to your work. If someone else created the content, or if it is based on someone else's work, the source should be the address to the web page where you found it, the name and ISBN of the book you scanned it from, or similar. You should also name the author, provide verifiable information to show that the content is in the public domain or has been published under a free license by its author, and add an appropriate template identifying the public domain or licensing status, if you have not already done so. Please add the required information for this and other files you have uploaded before adding more files. If you need assistance, please ask at the help desk. Thank you!

Ellin Beltz (talk) 17:39, 20 September 2016 (UTC)

Copyright status: File:UK Border Force patrol vessel -a.jpg

This media may be deleted.

Thanks for uploading File:UK Border Force patrol vessel -a.jpg. I notice that the file page either doesn't contain enough information about the license or it contains contradictory information about the license, so the copyright status is unclear. If you created this file yourself, then you must provide a valid copyright tag. For example, you can tag it with {{self|GFDL|cc-by-sa-all}} to release it under the multi-license GFDL plus Creative Commons Attribution-ShareAlike All-version license or you can tag it with {{PD-self}} to release it into the public domain. (See Commons:Copyright tags for the full list of license tags that you can use.) If you did not create the file yourself or if it is a derivative of another work that is possibly subject to copyright protection, then you must specify where you found it (e.g. usually a link to the web page where you got it), you must provide proof that it has a license that is acceptable for Commons (e.g. usually a link to the terms of use for content from that page), and you must add an appropriate license tag. If you did not create the file yourself and the specific source and license information is not available on the web, you must obtain permission through the OTRS system and follow the procedure described there. Note that any unsourced or improperly licensed files will be deleted one week after they have been marked as lacking proper information, as described in criteria for speedy deletion. If you have uploaded other files, please confirm that you have provided the proper information for those files, too. If you have any questions about licenses please ask at Commons:Village pump/Copyright or see our help pages. Thank you.

No required license templates were detected at this file page. Please correct it, or if you have any questions please check my FAQ or contact me on my talk page. Yours sincerely, Jarekt (talk) 17:26, 28 September 2016 (UTC)

Copyright status: File:Knud Rasmussen in 2011 -a.jpg

This media may be deleted.

Thanks for uploading File:Knud Rasmussen in 2011 -a.jpg. I notice that the file page either doesn't contain enough information about the license or it contains contradictory information about the license, so the copyright status is unclear. If you created this file yourself, then you must provide a valid copyright tag. For example, you can tag it with {{self|GFDL|cc-by-sa-all}} to release it under the multi-license GFDL plus Creative Commons Attribution-ShareAlike All-version license or you can tag it with {{PD-self}} to release it into the public domain. (See Commons:Copyright tags for the full list of license tags that you can use.) If you did not create the file yourself or if it is a derivative of another work that is possibly subject to copyright protection, then you must specify where you found it (e.g. usually a link to the web page where you got it), you must provide proof that it has a license that is acceptable for Commons (e.g. usually a link to the terms of use for content from that page), and you must add an appropriate license tag. If you did not create the file yourself and the specific source and license information is not available on the web, you must obtain permission through the OTRS system and follow the procedure described there. Note that any unsourced or improperly licensed files will be deleted one week after they have been marked as lacking proper information, as described in criteria for speedy deletion. If you have uploaded other files, please confirm that you have provided the proper information for those files, too. If you have any questions about licenses please ask at Commons:Village pump/Copyright or see our help pages. Thank you.

Yours sincerely, Magog the Ogre (talk) (contribs) 03:24, 4 October 2016 (UTC)

url shorteners

Using url shorteners will fail on most occasions. They are spam targets and many are blacklisted. Always best to utilise a full url.  — billinghurst sDrewth 14:33, 16 October 2016 (UTC)

• Yeah? I don't knowingly use them. If you think you came across a specific instance where I did, then you found one that slipped past me. Geo Swan (talk) 14:39, 16 October 2016 (UTC)

File:Publicly filed CSRT records - ISN 00037, Abd Al Malik Abd Al Wahab.pdf

File:Publicly filed CSRT records - ISN 00037, Abd Al Malik Abd Al Wahab.pdf is considered to fulfill the criteria for speedy deletion and has been marked on its image description page. The following reason has been specified: This file is a duplicate of the following files: File:Publicly filed CSRT records 237-369.pdf. If you believe the content does not meet the criteria for speedy deletion, you may request undeletion. 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.

Revent^talk 08:55, 17 October 2016 (UTC)

File:Waterloo Cinema, Huddersfield (29431795434).jpg

File:Waterloo Cinema, Huddersfield (29431795434).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 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!

★ Poké⁹⁵ 08:44, 20 October 2016 (UTC)

Category:Guantanamo_captives'_documents_by_serial_number

Category:Guantanamo_captives'_documents_by_serial_number has been listed at Commons:Categories for discussion so that the community can discuss ways in which it should be changed. We would appreciate it if you could go to voice your opinion about this at its entry. If you created this category, please note that the fact that it has been proposed for discussion 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. If the category is up for deletion because it has been superseded, consider the notion that although the category may be deleted, your hard work (which we all greatly appreciate) lives on in the new category. In all cases, please do not take the category discussion personally. It is never intended as such. Thank you!

Auntof6 (talk) 21:34, 3 November 2016 (UTC)

File:Timbits in the USA -a.jpg

File:Timbits in the USA -a.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 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!

(t) Josve05a (c) 14:05, 8 November 2016 (UTC)

File:Construction, Queen's Quay, east of Yonge, 2014 05 20 (2) (14231269692).jpg

File:Construction, Queen's Quay, east of Yonge, 2014 05 20 (2) (14231269692).jpg is considered to fulfill the criteria for speedy deletion and has been marked on its image description page. The following reason has been specified: This file is a duplicate of the following files: File:Construction, Queen's Quay, east of Yonge, 2014 05 20 (2).jpg. If you believe the content does not meet the criteria for speedy deletion, you may request undeletion. 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.

Revent^talk 14:33, 10 November 2016 (UTC)

Your Flickr images

Just an FYI... I noticed, while looking at duplicates, that you have lots of uploads that are 'your own works', copied over 'by you' from Flickr, that you have an OTRS ticket confirming that you have released them to the PD, and that a lot of those images 'still' have the CC-BY-SA license and 'flickr review'. Since that's rather silly, I've running down the list of your uploads with 'flickreview' and no 'permissionOTRS', and changing them to {{PD-Self}}{{PermissionOTRS|id=2012092210003274|user=Revent}}. Hope that's fine. I'm leaving out the CC license, because it would end up being confusing, and, well, it's completely redundant to a PD work. Revent^talk 15:48, 10 November 2016 (UTC)

File:Car 68, Rochester Subway, via Rochester Municipal Archives.jpg

File:Car 68, Rochester Subway, via Rochester Municipal Archives.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 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!

   FDMS  4    21:16, 23 November 2016 (UTC)

Category:Files_from_HaloJim_from_Pixabay

Category:Files_from_HaloJim_from_Pixabay has been listed at Commons:Categories for discussion so that the community can discuss ways in which it should be changed. We would appreciate it if you could go to voice your opinion about this at its entry. If you created this category, please note that the fact that it has been proposed for discussion 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. If the category is up for deletion because it has been superseded, consider the notion that although the category may be deleted, your hard work (which we all greatly appreciate) lives on in the new category. In all cases, please do not take the category discussion personally. It is never intended as such. Thank you!

Speravir 04:43, 10 December 2016 (UTC)

In my reply at the discussion I did not say I thought that nominator Speravir's nomination unnecessarily wasted the time of everybody involved -- his, mine, and everyone who read the discussion. Geo Swan (talk) 10:45, 10 December 2016 (UTC)

Pixabay ID

The template {{Pixabay}} needs the file ID as required parameter, please read the template doc. But also without reading you should have noticed the remark inside the license tag, that is seen now for your latest uploads. — Speravir – 18:12, 13 December 2016 (UTC)

Category:Petrol_stations_in_British_Columbia

Category:Petrol_stations_in_British_Columbia has been listed at Commons:Categories for discussion so that the community can discuss ways in which it should be changed. We would appreciate it if you could go to voice your opinion about this at its entry. If you created this category, please note that the fact that it has been proposed for discussion 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. If the category is up for deletion because it has been superseded, consider the notion that although the category may be deleted, your hard work (which we all greatly appreciate) lives on in the new category. In all cases, please do not take the category discussion personally. It is never intended as such. Thank you!

Mindmatrix 21:52, 14 December 2016 (UTC)

Category:Petrol_stations_in_Alberta

Category:Petrol_stations_in_Alberta has been listed at Commons:Categories for discussion so that the community can discuss ways in which it should be changed. We would appreciate it if you could go to voice your opinion about this at its entry. If you created this category, please note that the fact that it has been proposed for discussion 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. If the category is up for deletion because it has been superseded, consider the notion that although the category may be deleted, your hard work (which we all greatly appreciate) lives on in the new category. In all cases, please do not take the category discussion personally. It is never intended as such. Thank you!

Mindmatrix 21:53, 14 December 2016 (UTC)

Copyright status: File:Descendants of Bailey Barco meet the crew of the USCGC Bailey Barco -a.jpg

This media may be deleted.

Thanks for uploading File:Descendants of Bailey Barco meet the crew of the USCGC Bailey Barco -a.jpg. I notice that the file page either doesn't contain enough information about the license or it contains contradictory information about the license, so the copyright status is unclear. If you created this file yourself, then you must provide a valid copyright tag. For example, you can tag it with {{self|GFDL|cc-by-sa-all}} to release it under the multi-license GFDL plus Creative Commons Attribution-ShareAlike All-version license or you can tag it with {{PD-self}} to release it into the public domain. (See Commons:Copyright tags for the full list of license tags that you can use.) If you did not create the file yourself or if it is a derivative of another work that is possibly subject to copyright protection, then you must specify where you found it (e.g. usually a link to the web page where you got it), you must provide proof that it has a license that is acceptable for Commons (e.g. usually a link to the terms of use for content from that page), and you must add an appropriate license tag. If you did not create the file yourself and the specific source and license information is not available on the web, you must obtain permission through the OTRS system and follow the procedure described there. Note that any unsourced or improperly licensed files will be deleted one week after they have been marked as lacking proper information, as described in criteria for speedy deletion. If you have uploaded other files, please confirm that you have provided the proper information for those files, too. If you have any questions about licenses please ask at Commons:Village pump/Copyright or see our help pages. Thank you.

Yours sincerely, Magog the Ogre (talk) (contribs) 05:37, 11 February 2017 (UTC)

Commons:VIRIN

Dear Geo Swan,

Any images from a US Federal government site is Public Domain as you know. Here are the specific licenses for US military sites under Virins for Commons. I will be away on Thursday. --Leoboudv (talk) 04:44, 16 February 2017 (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. 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:Sun-craft - Reykjavik bay (3443256114).jpg

Yours sincerely, Themightyquill (talk) 14:30, 19 February 2017 (UTC)

File:Model Tara, posing....jpg

File:Model Tara, posing....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 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) 11:48, 24 February 2017 (UTC)

File:AF7 Arctic USN.jpg

File:AF7 Arctic USN.jpg is considered to fulfill the criteria for speedy deletion and has been marked on its image description page. The following reason has been specified: This file is a duplicate of the following files: File:Arctic(AF7), formerly the Yambill. Storeship. Aerial, starboard bow, underway, 05-06-1924 - NARA - 520824.jpg. If you believe the content does not meet the criteria for speedy deletion, you may request undeletion. 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.

- Revent^talk 17:31, 1 March 2017 (UTC)

File:Eriko Hatsune (24096322835) (2).jpg

File:Eriko Hatsune (24096322835) (2).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 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!

Ellin Beltz (talk) 17:21, 13 March 2017 (UTC)

Copyright status: File:Locomotive pulling into Kitchener Station in 1939.png

This media may be deleted.

Thanks for uploading File:Locomotive pulling into Kitchener Station in 1939.png. I notice that the file page either doesn't contain enough information about the license or it contains contradictory information about the license, so the copyright status is unclear. If you created this file yourself, then you must provide a valid copyright tag. For example, you can tag it with {{self|GFDL|cc-by-sa-all}} to release it under the multi-license GFDL plus Creative Commons Attribution-ShareAlike All-version license or you can tag it with {{PD-self}} to release it into the public domain. (See Commons:Copyright tags for the full list of license tags that you can use.) If you did not create the file yourself or if it is a derivative of another work that is possibly subject to copyright protection, then you must specify where you found it (e.g. usually a link to the web page where you got it), you must provide proof that it has a license that is acceptable for Commons (e.g. usually a link to the terms of use for content from that page), and you must add an appropriate license tag. If you did not create the file yourself and the specific source and license information is not available on the web, you must obtain permission through the OTRS system and follow the procedure described there. Note that any unsourced or improperly licensed files will be deleted one week after they have been marked as lacking proper information, as described in criteria for speedy deletion. If you have uploaded other files, please confirm that you have provided the proper information for those files, too. If you have any questions about licenses please ask at Commons:Village pump/Copyright or see our help pages. Thank you.

Jcb (talk) 18:09, 15 March 2017 (UTC)

Snoqualmie / Burton

I know you usually know what you are doing but I don't get this at all. - Jmabel ! talk 00:13, 21 March 2017 (UTC)

• You are correct, I wasn't paying attention... Geo Swan (talk) 01:07, 21 March 2017 (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. 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:Wizard World 27 (6997592124).jpg

Yours sincerely, (t) Josve05a (c) 17:51, 25 March 2017 (UTC)

[[:]]

Dear Geo Swan,

how is this file related to United Way?--Tostman (talk) 16:00, 8 April 2017 (UTC)

Tostman the uploaded description says "United Way bus". Possibly merely rented by United Way... Geo Swan (talk) 23:22, 8 April 2017 (UTC)

UBus is the "United Highway Bus Company" not the "United Way". Simply a translation problem. I've reverted it. Secondarywaltz (talk) 23:37, 8 April 2017 (UTC)

TTC LRV categories

Is there any reason that we have both Category:TTC Bombardier light rail vehicles by year and Category:Bombardier LRV in Toronto by year? They seem to serve identical purposes. Pi.1415926535 (talk) 02:13, 19 April 2017 (UTC)

File:Niagara Falls (14113215289).jpg

File:Niagara Falls (14113215289).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 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!

P 1 9 9  ✉ 14:57, 19 April 2017 (UTC)

File:Niagara Falls (14113226128).jpg

File:Niagara Falls (14113226128).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 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!

P 1 9 9  ✉ 14:58, 19 April 2017 (UTC)

File:Niagara Falls (14113229150).jpg

File:Niagara Falls (14113229150).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 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!

P 1 9 9  ✉ 14:58, 19 April 2017 (UTC)

File:Distant view of construction at 88 Scott Street, 2017 04 19 -c (34157767455).jpg

File:Distant view of construction at 88 Scott Street, 2017 04 19 -c (34157767455).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 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!

Leoboudv (talk) 21:18, 21 April 2017 (UTC)

•  Done Geo Swan (talk) 21:31, 24 April 2017 (UTC)

File:SW corner of Parliament and Queen, formerly Marty Millionaire's, 2017 04 19 -c (34115855786).jpg

Public Domain Mark is not a license that acceptable on flickr. This image is tagged for deletion by the flickrbot. Please see the above DR request and change the license to Attribution Creative Commons, Attribution ShareAlike or public domain dedication and order a new flickrreview. Here is a DR where an image was deleted. Best Regards, --Leoboudv (talk) 21:27, 21 April 2017 (UTC)

•  Done Geo Swan (talk) 21:31, 24 April 2017 (UTC)

Image without license

File:Circus performance, at guantanamo -b.jpg

---

There seems to be a problem regarding the description and/or licensing of this particular file. It has been found that you've added in the image's description only a Template that's not a license and although it provides useful information about the image, it's not a valid license. Could you please resolve this problem, adding the license in the image linked above? You can edit the description page and change the text. Uploading a new version of the file does not change the description of the file. This page may give you more hints on which license to choose. Thank you.

This message was added automatically by MifterBot ^{(Talk • Contribs • Owner)}, if you need some help about it please read the text above again and follow the links in it, if you still need help ask at the → Commons:Help desk in any language you like to use. --MifterBot ^{(Talk • Contribs • Owner)} 20:37, 24 April 2017 (UTC)

File:Circus performance, at guantanamo -a.jpg

---

There seems to be a problem regarding the description and/or licensing of this particular file. It has been found that you've added in the image's description only a Template that's not a license and although it provides useful information about the image, it's not a valid license. Could you please resolve this problem, adding the license in the image linked above? You can edit the description page and change the text. Uploading a new version of the file does not change the description of the file. This page may give you more hints on which license to choose. Thank you.

This message was added automatically by MifterBot ^{(Talk • Contribs • Owner)}, if you need some help about it please read the text above again and follow the links in it, if you still need help ask at the → Commons:Help desk in any language you like to use. --MifterBot ^{(Talk • Contribs • Owner)} 20:38, 24 April 2017 (UTC)