This is an archive of past discussions. Do not edit the contents of this page. If you wish to start a new discussion or revive an old one, please do so on the current talk page.
Hi. I requested an administrator to overwrite a protected file, and I was told to show a consensus. Two things: Is there really necesary a consensus when there is a clear misrepresentation of the Honduras flag?, as shown by the large number of pictures I presented in the talk page. And 2) Where am I supossed to look for consensus? Can I ask for support here? -Kes47 (?) 01:26, 28 September 2018 (UTC) — Preceding unsigned comment added by Kes47 (talk • contribs) 01:26, 28 September 2018 (UTC)
The relevant consensus would probably be either (1) users from Honduras or (2) people who have participated on this page in the past. The best would be if whoever originally uploaded with the current color agreed that what you want to do is an improvement. - Jmabel ! talk04:50, 28 September 2018 (UTC)
See this official photo from Honduran Government, showing Hernandez with ceremonial flag and sash. Secretary Tillerson Hosts Honduran President Juan Orlando Hernandez at the State Department (33420471702) The colours (cerulean blue) in the official photo are the same as on this visit to the State Department. faded version of same colour. See this version. Flag on Wikipedia page Our version on the Wikipedia home page is not much different. It's a different blue from the other ex-FRCA countries. We should stick with what we have, and delete the others. - Broichmore (talk) 09:14, 28 September 2018 (UTC)
yeah, surprised the fair use image has not been deleted for the living person. need to go take a CC image of the living person, but since Shankbone has retired, not much hope of that, unless she appears at Comicon. the attempts to recruit photo stringers or pay stipends have failed, so the photos of living people suck.[2] Slowking4 § Sander.v.Ginkel's revenge02:01, 30 September 2018 (UTC)
Or go out & start taking pictures of important people. It's not like Shankbone is the only Wikimedian ever to do this. - Jmabel ! talk02:38, 30 September 2018 (UTC)
Over 1000 is a lot. Not all that many people do over 1000 photos altogether. But I've certainly done over 100, and people aren't the main thing I photograph. User:Jmabel/People shows some of my work in this respect; it's by no means exhaustive. - Jmabel ! talk00:16, 1 October 2018 (UTC)
well, he set a high bar. it was only 3 years until someone surpassed his 2912. quantified imperfectly with [3] since don't have subject stats. and yeah, easier to get "unmoved" monuments. given the over 10000 photo requests of people, it will take such an effort. (and real number is much larger) [4]. but not much sustained effort, other than the one off EU parliament photos.[5], [6] Slowking4 § Sander.v.Ginkel's revenge00:53, 1 October 2018 (UTC)
September 30
Misattributed works
The statue is a Rodin, but not the painting
All of these are described, implausibly, as works by Auguste Rodin. I presume they are works by his contemporaries that were in an exhibit with his work. The uploader/photographer didn't respond to a query on his talk page. Does anyone know whose these each are? - Jmabel ! talk07:12, 30 September 2018 (UTC)
I've corrected the (Spanish-language) descriptions & the categories on the 5 of these that are now identified. A maintenance category would be welcome, but I leave that to someone else to set up. - Jmabel ! talk00:33, 1 October 2018 (UTC)
Latest tech news from the Wikimedia technical community. Please tell other users about these changes. Not all changes will affect you. Translations are available.
Recent changes
Ordinary pages can no longer be loaded as javascript. You could do this using ?action=raw&ctype=text/javascript in the URL. Only fully protected pages in the MediaWiki: namespace or user javascript subpages can be loaded as javascript now. This is for better security. [7][8]
Problems
New and updated translations from will not reach the wikis for a while. You can still translate messages on translatewiki.net. The Wikimedia wikis will be updated with the new translations later. This is because of work on the translation system. [9][10]
Changes later this week
The new version of MediaWiki will be on test wikis and MediaWiki.org from 2 October. It will be on non-Wikipedia wikis and some Wikipedias from 3 October. It will be on all wikis from 4 October (calendar).
Meetings
You can join the technical advice meeting on IRC. During the meeting, volunteer developers can ask for advice. The meeting will be on 3 October at 15:00 (UTC). See how to join.
You can join the meeting with the Wikimedia Foundation Search Platform team. The meeting will be on 3 October at 15:00 UTC. See how to join if you want to know how the search function works or have questions.
Future changes
Because of a data centre test you will be able to read but not edit the wikis for up to an hour on 10 October. This will start at 14:00 (UTC). You might lose edits if you try to save during this time. The time when you can't edit might be shorter than an hour. You can read more about this.
Results from global Wikimedia survey 2018 are published
Hello! A few months ago the Wikimedia Foundation invited contributors to take a survey about your experiences on Wikipedia.
The report is now published on Meta-Wiki!
We asked contributors 170 questions across many different topics like diversity, harassment, paid editing, Wikimedia events and many others.
Read the report or watch the presentation, which is available only in English.
Add your thoughts and comments to the report talk page.
Feel free to share the report on Wikipedia/Wikimedia or on your favorite social media. Thanks! --EGalvez (WMF)20:21, 1 October 2018 (UTC)
Cc-by-all
{{Cc-by-all}} - In all languages, there is copyleft in the template-text, that don't exist (the only conditions are to attribute the author and the license), how could I change this in all languages, if I couldn't speak all languages? Habitator terrae (talk) 13:41, 1 October 2018 (UTC)
As soon as an OTRS agent concludes that the permission is valid, they will take care of undeletion. The ticket is open, so it will be handled one day or another. Jcb (talk) 20:46, 1 October 2018 (UTC)
Jcb, the article is in the DYK queue. It would be helpful not to have to wait a few months (currently 142 days) for readers to be able to see this portrait. The owners gave it a CC-BY-4.0 license on September 7. -SusanLesch (talk) 20:58, 1 October 2018 (UTC)
It would be helpful if you would not expect that your ticket is somehow more important than all the other waiting tickets. Also next time if you want to talk to me, go to my user talk page instead. Jcb (talk) 21:04, 1 October 2018 (UTC)
it would be helpful, if you did not blame the uploader for your broken OTRS process. the fact that a new article with a DYK, which means main page exposure, will not have an image that it very well could, tends to reflect poorly on commons, i.e. does not play well with others. that is a good topic for this page. Slowking4 § Sander.v.Ginkel's revenge14:51, 2 October 2018 (UTC)
Fire Dancing performer, Medieval Festival of Itri (Italy)
NAT's (street performer), performing rope act to earn hard money to feed her family, on the occasion of rathyatra festival in Ahmedabad, Gujarat, India.
Is there any one? I've just rejected a renaming request (see history in File:متحف التاريخ الطبيعي 8.jpg) as, IMHO, it was not ambiguous, just imprecise and the request involved the change from Arabic to English, but the requester (@Russian Rocky: ) keeps on pushing for the rename. Is there any procedure to discuss a specific file rename request? Thanks --Discastotalk08:13, 3 October 2018 (UTC)
I've been contemplating for a while that I might do a big photo run around my part of town using the Commons app, but one thing that always puts me off is that there's many nonexistent places tagged as needing photos. In my city in particular, someone has done a big Wikidata dump of former theatres - many of which were demolished a century ago (and many of those lacking any information at all in Google) - so long ago that without supplementary information it's not even possible to definitively pinpoint the exact site (because street numbering can change in 100 years). Is there a way of removing these from the Commons app, or is it doomed to just have hundreds of these sitting around for eternity? The Drover's Wife (talk) 09:34, 3 October 2018 (UTC)
I believe there has been some discussion of marking places for which a new photo is not possible, but I'm not sure anyone is working on that. Can someone comment more knowledgeably? - Jmabel ! talk16:22, 3 October 2018 (UTC)
Google Image Search and Wikimedia
Hi there,
Can someone experienced confirm my query: I have a number of unique images I will be uploading, my question is regarding google image search. I can see a lot of the wikimedia communities images appear on google images.1. Does this happen to all wikimedia images and is the process 2. what is the timeframe for them being added to google images search? Can you specify which images appear in google image search? thanks Vfusco1 (talk) 09:49, 3 October 2018 (UTC)
Structured data - IRC office hours tomorrow, 4 October
A reminder that the Structured Data team will be hold in an IRC office hour Thursday (tomorrow), 4 October, from 17:00-18:00 UTC in #wikimedia-office. Links to date and time conversion, as well as a way to participate on IRC without a client, are available on Meta. I'll post a followup reminder here tomorrow about an hour before we begin. Keegan (WMF) (talk) 19:59, 3 October 2018 (UTC)
The Wikimedia Foundation are testing its secondary data center. This will make sure that Wikipedia and the other Wikimedia wikis can stay online even after a disaster.
They switched all traffic to the secondary data center 12 September 2018.
On Wednesday, 10 October 2018, they will switch back to the primary data center.
Unfortunately, because of some limitations in MediaWiki, all editing must stop while we switch.
You will be able to read, but not edit, all wikis for a short period of time.
You will not be able to edit for up to an hour on Wednesday, 10 October. The test will start a bit after 14:00 UTC (15:00 BST, 16:00 CEST, 10:00 EDT, 07:00 PDT, 23:00 JST). If you try to edit or save during these times, you will see an error message.
Hi, I would like to ask somebody more experienced. Is the figure 2 in this PDF free? I would say so as the author, Frederik Johnstrup died in 1894 and the work was published in 1877. Or did I miss something which do not allow me to upload these old images of Askja to Commons? Thanks in advance for help and best regards --Chmee2 (talk) 20:01, 4 October 2018 (UTC)
@Chmee2: The site is paywalled (or, at least, university-walled) so I can't see the particular image, but if the author of the image died in 1894 and the work was published in 1877, and this publication is presenting you with a faithful reproduction of their 2-dimensional work, then it's public domain and can be uploaded here. (If, on the other hand, the image in question is a sculpture or some other 3-dimensional work of art, and someone in modern times took a photograph of that 3-dimensional work of art and published it, then the photograph is subject to copyright.) --B (talk) 20:24, 4 October 2018 (UTC)
Hi! In the sidebar (Main page, community portal, Tools, In Wikipedia,...), several interproject links are displayed.
The "In Wikipedia" section is OK (linking every language edition of Wikipedia corresponding to a Commons category), but the section "In other projects" is linking only "Wikisource in English", "Wikivoyage in English", ... (...) ...regardless the language selected by user in the interface.
@B: Thanks but... no, they don't. They are now displayed in Japanese characters but... redirect to en.wikisource, en.wikivoyage,... and so on. :( Strakhov (talk) 21:21, 4 October 2018 (UTC)
@Strakhov: Interesting. I tried it and it links to ja for me. Is this the link you are trying or am I looking in the wrong place? --B (talk) 08:19, 5 October 2018 (UTC)
Interesting. From looking at the CSS, I think the data is coming from the wikibase extension, which is pulling its data from Wikidata. But how to fix any of that is over my head. --B (talk) 12:02, 5 October 2018 (UTC)
What do you mean by "mirror image"? Are you suggesting some action? It is from an external source, which is fine because that source has assigned it a free license. BMacZero (talk) 16:58, 2 October 2018 (UTC)
Flipped along the vertical axis, probably (per en:Mirror image and [11]). If anyone wants to upload the "correct" orientation as a derivative of this one, they're perfectly free to do so, but it's not a pressing issue. clpo13(talk)17:08, 2 October 2018 (UTC)
Can Commons host original art projects/contests for other categories not before thought of? Like in the categories of cartography? -Inowen (talk) 02:45, 5 October 2018 (UTC)
Can someone clue me in to where I can find the images that are considered the best of Commons. I want to highlight these in the next issue of the Signpost on the English Wikipedia. Thanks ahead of time. Best Regards, Barbara (WVS) (talk) 18:45, 7 October 2018 (UTC)
Ah, I just found Category:Boarding houses a level down. Techincally, the two terms are not identical: a "boarding house" provides meals, a "rooming house" doesn't. I don't mind conflating them, but I am adding a redirect. - Jmabel ! talk20:56, 8 October 2018 (UTC)
Latest tech news from the Wikimedia technical community. Please tell other users about these changes. Not all changes will affect you. Translations are available.
There was a problem when you copied and pasted from a table with the visual editor. It could add href where it shouldn't be. This has now been fixed. [13]
Changes later this week
Because of a data centre test you will be able to read but not edit the wikis for up to an hour on 10 October. This will start at 14:00 (UTC). You might lose edits if you try to save during this time. The time when you can't edit might be shorter than an hour. You can read more about this.
Because of the data centre test there will be no new version of MediaWiki this week. Changes for this week will come next week instead.
Meetings
You can join the technical advice meeting on IRC. During the meeting, volunteer developers can ask for advice. The meeting will be on 10 October at 15:00 (UTC). See how to join.
I've taken some pictures of Mariana (Cuenca). I've seen that category:Mariana redirects to Mariana (Minas Gerais). So far, there was only one Mariana in Commons, but there will soon be a second one. I don't know how to fix category:Mariana as to reflect such event. B25es (talk) 06:02, 9 October 2018 (UTC)
My understanding of how wikis treat nudity is generally that it is only included under circumstances where understanding content would be more difficult without the nudity. If this was just on someone's user page, sure, I say whatever.
But I went to the Main Page today and saw a topless female model on the very top of the page, clear in sight, huge image, I was pretty shocked. It would be different if someone specifically searched for this picture, or maybe an article about female breasts on Wikipedia, and found it that way. But when you have nudity shining bright on the front page of your site, don't you think that's a bit too much?! What about grade-school kids at school who search this site for educational usage, maybe to find free images for a project, and are greeted with this image? Some would immediately think "I didn't know this was a porn site!" If anything, something like this may scare lurkers away from the site more than it draws lurkers in.
Not to mention the fact that this is seemingly featured because of the quality of the picture being equivalent to the superficial attractiveness of the model.
yeah, thanks for the soft porn everyone. and edit warring to maimtain this in the queue. if you want to know why commons has a low reputation, and why english will not allow links, this would be why. Slowking4 § Sander.v.Ginkel's revenge20:04, 27 September 2018 (UTC)
Out of curiosity: Are there any established guidelines/policy about this? Or, how does Commons/WP define what not to show, regarding nudity? 2.247.241.11121:48, 27 September 2018 (UTC)
That merely says "we don't delete images just because they have naked people in them", not "artistic nudes with zero encyclopediac value belong on our front page." Pi.1415926535 (talk) 22:15, 27 September 2018 (UTC)
We don't have a guideline against it, either. Anyone seriously upset about this should get involved in COM:POTD or propose a change in policy instead of objecting after everything is said and done. clpo13(talk)22:27, 27 September 2018 (UTC)
absolutely not interested in that soul-crushing ego gratification process- the bias of the existing gatekeepers is quite clear, with no indication of willingness to change. not interested in another round of policy "let's make more rules to stop us from hurting ourselves" just stop. Slowking4 § Sander.v.Ginkel's revenge11:43, 30 September 2018 (UTC)
No, it says Commons will not censor or remove media that users find objectionable or offensive (emphasis added). The "or" makes a big difference. GMGtalk22:35, 27 September 2018 (UTC)
Nudes don't often show up on the front page, but every time it happens, I have to wonder how many upset about it would be equally offended by Titian's Venus of Urbino or a similar piece of notable art? "Soft porn" indeed. clpo13(talk)22:19, 27 September 2018 (UTC)
It seems a lot like one side is saying "we shouldn't have these" and the other is saying "we have no policy that disallows them". The obvious answer would be to start a centralized discussion about whether these are appropriate, and change policy. GMGtalk23:11, 27 September 2018 (UTC)
I'm more interested in the opinion of the puritans who object to the nudity rather than the perceived lack of educational value. Yes, Venus of Urbino is an encyclopedic painting, but would those who are clutching their pearls over the referenced photo be just as disturbed by Titian's painting on the front page? Scratch that, I know they would. clpo13(talk)23:26, 27 September 2018 (UTC)
I hate to be a bit confrontational, but comments to this effect always crop up every time this issue is raised. It would be more useful if you could comment on the OP's specific criticisms than their lack or excess of morality. I agree with the OP that many internet users who navigate to Commons would probably be startled to see this image on the front page. The PotD is there to draw visitors in with the impressive quality of the photo displayed, but I think in this case the content probably causes this image to do the opposite for many visitors. BMacZero (talk) 00:18, 28 September 2018 (UTC)
Also, I didn't see any comments in the FP discussion you linked that rejected the image because it contains nudity. Most of them are concerned with the quality of the digitization. BMacZero (talk) 00:18, 28 September 2018 (UTC)
OP's main concern seems to amount to "omg tits", but as I said earlier, if they don't want this to happen again (and really, it doesn't happen that often), they should get involved in discussions to change things. I understand the objections, and while I don't agree with them (and wonder what else people might want to keep off the main page because it might offend somebody somewhere), I'm open to participating in proposals to amend the existing guidelines in some way that minimizes the surprise to those unfamiliar with Commons.
Also, the comments on the FP discussion weren't all that bad, I admit, but LogX supported it [t]hough the picture is showing the sensational art and Amandajm complained about too many nudes making the Main Page look like Page 3. clpo13(talk)00:42, 28 September 2018 (UTC)
I dunno. I'm not really even arguing that it's appropriate. I'm just arguing that there's no policy based reason to forbid it. Make a consensus based reason to forbid it and I'll argue the other side. GMGtalk00:44, 28 September 2018 (UTC)
GreenMeansGo, COM:NOTCENSORED is a guideline on hosting media, not on what we as a community choose to display on the main page, or on other forums here. People who visit Commons have no control over what they see on the main page, and reasonable people would assume it is appropriately curated rather than chosen to shock or offend. There are situations where viewing such material in a public, work or school environment would result in personal attack, job loss, or even criminal prosecution. Dismissing these concerns as "puritans" or "omg tits" reflects a very narrow self centred world-view where the only valid position is that of a frat boy in his bedroom. Displaying such images on the main page demonstrates about as much maturity as getting a tattoo just to show your mum how independent-minded you are. Btw, the purpose of FPC is not to select images for the main page. That the main page team select their images from the FP pool is their choice, and they aren't obliged to select all images that get promoted. "Just because you can, doesn't mean you should". Quite a few people on Commons have yet to learn that lesson in life. -- Colin (talk) 14:44, 1 October 2018 (UTC)
Umm...Colin, no offense, but the "omg tits" bit wasn't my comment. It was from clpo13. Mine is simply that the closest thing to a relevant policy is NOTCENSORED, and while a number of editors have expressed views similar to your own about the appropriateness of such content, there is as yet no consensus based reason to forbid it. If enough people feel strongly about it, then they should see such a broad consensus, and I'm happy to defer to it once achieved. GMGtalk14:49, 1 October 2018 (UTC)
User:GreenMeansGo ah I didn't notice the other signature, so thought the whole paragraph was yours. Anyway, you replied that NOTCENSORED was relevant and it really really isn't. But should anyone create a VP discussion about what kinds of image we should show on the main page, you can bet there will be 100 "NOTCENSORED" votes from folk who haven't the first clue what censorship actually is. I don't suppose we can expect kids who get their news from Facebook to understand that the editors of a publication (such as the main page, or a newspaper) are only free when they can both chose what to include and what not to include. -- Colin (talk) 15:13, 1 October 2018 (UTC)
I mean.. CENSOR is a policy that specifically applies to SCOPE. But NOTCENSORED is part of the guideline NOT, and not part of SCOPE. If NOTCENSORED applies to blurring genitalia within the context of a single image (also not an issue of keep/delete), I don't see an obvious reason why it would not equally apply to content hosted on galleries or on the main page, barring consensus against that interpretation. GMGtalk15:20, 1 October 2018 (UTC)
If we want to have a policy of not displaying NSFW media (assuming bosses and coworkers can include a mix of fundamentalists opposed to nudity and images of Mohammed) on the main page, a proposal for it should be on COM:VPP, not right here. — Jeff G. ツ please ping or talk to me15:01, 1 October 2018 (UTC)
Why do these discussions always fall down to labelling people puritans and "fundamentalists opposed to nudity and images of Mohammed". Look, there is a difference between the perfectly legal right have a wank with your laptop in your bedroom and looking at the stuff with your trousers down and fist pumping away on the train. Most grown ups appreciate there is a time and a place and that freedom means giving people control over what they watch and when. By sticking sensitive images on the main page, you are actually removing people's freedoms, and saying "you will accept my values and my choices right now". That's quite oppressive. -- Colin (talk) 15:13, 1 October 2018 (UTC)
Hi, The laughing stock here are the people complaining when they see a woman's tit on Commons Main Page. Would a man's tit be OK? And who obviously never show up on POTD. Well, blame yourself... Regards, Yann (talk) 16:25, 1 October 2018 (UTC)
Honestly, this isn't a "laughing" matter. We are only having this conversation because there are about three women on Commons, and this sort of thing does nothing to change that. If we had a good proportion of grown-up professional-minded female users, you'd all be slapped round the head with an "objectification" wet fish. Yann, your argument about participating at POTD is completely irrelevant and a rather lame way of reacting to criticism. -- Colin (talk) 15:09, 2 October 2018 (UTC)
yes, commons is a cesspool, with no technical barriers to entry, just cultural ones. better to laugh than cry. but if you want to know why commons is a laughing stock: "Well, blame yourself... Regards," i take it, you agree there should be a code of conduct, and standard of practice? Slowking4 § Sander.v.Ginkel's revenge17:02, 5 October 2018 (UTC)
@Tuvalkin: 50 million uploaded files, while certainly significant, appears to include deleted or old versions of files. I will be more excited when {{NUMBEROFARTICLES}} lists 50 million files and galleries (it currently stands at 106,818,975). — Jeff G. ツ please ping or talk to me12:26, 7 October 2018 (UTC)
@Jeff G.: I was refering to {{NUMBEROFFILES}}, which seems to have hit 50 M for the first time around one hour ago. Does it include deleted files? I’d say it does not, or should not. Maybe file redirects are included? Not sure. As for {{NUMBEROFARTICLES}}, I didn’t even consider it because it includes Commnos’ galleries, which are mostly garbage. -- Tuválkin✉✇12:48, 7 October 2018 (UTC)
I don’t think so: I noticed something like 50 000 162 when I started this thread, at 11:53 UTC, and this image was uploaded at 13:06 UTC. Of course deletions means that any given number is crossed several times upon uploading, but I think just before 11:53 UTC was when the 50M mark was crossed for the first time. -- Tuválkin✉✇10:07, 11 October 2018 (UTC)
I was thinking about that, too, since Jeff G. reported above 49 M and change. There should be one file page for each file counted with {{NUMBEROFFILES}} and yet we’re a few hundered thousand short: not only 111,028,043 minus 106,818,975 (516 348 as of this datestamp) but also minus the number of Galleries. I suspect it could be file page redirects counting as files, but a better opinion is sought. -- Tuválkin✉✇18:28, 7 October 2018 (UTC)
Let me plug in here this bit of wiki text I add to my uploads’ descriptions:
| other_fields={{Information_field |name=1st uploaded as the|value={{subst:formatnum:{{subst:#expr:{{subst:formatnum:{{subst:NUMBEROFFILES}}|R}}+1}}}}<sup>th</sup> file in Wikimedia Commons}}
I really think it is important to celebrate an important milestone. 50 Million free images is a VERY important milestone. Is there anyone who can suggest a likely nr 50M? Otherwise I will take the leopard eating an antilope, suggested above, as an image "near to 50M". Vysotsky (talk) 19:36, 11 October 2018 (UTC)
I don't understand, you say Wikipedia and Wikidata, so you do not take it from Commons? ℺ Gone Postal (〠✉✍⏿) 05:28, 12 October 2018 (UTC)
October 12
jpegcrop producing errors in imgs
I've been using jpegcrop for years, but recently I've found that when I crop an img, the cropped version does not display properly. I recently replaced the img on my user page, tried cropping it, and again there's a problem. (E.g. in the windows folder on my laptop, instead of a thumbnail of the img, as w the original, there's just a generic 'jpg' icon for the cropped version, and MaxView 2.8 displays a black screen if I open it.)
Just to see what would happen, I uploaded it to Commons anyway. (Linked here.) It displays fine in preview. I put it on my user page, and that displays fine as well, with it reduced in size. But if I click on it to see it in full res, I see an icon for a broken file. If instead I choose full-res under the preview options, I get the error message 'This image "[URL]" cannot be displayed because it contains errors.' (I'm using FF.) But any of the smaller versions display correctly.
I updated jpegcrop (2015 to current 2017 version), and it's still happening, so presumably not a bug on their end. The moth is quite a large img, but it happens w small ones too. Any idea what I'm doing wrong? Thanks Kwamikagami (talk) 03:38, 12 October 2018 (UTC)
Huh. Just playing around, I tried viewing it at reduced size in MaxView, to see if I'd get the behaviour here, but still a black screen. (I needed to use finger commands on the touch pad, because the scaling menu was greyed out.) Then at 200% and it displayed correctly. Then the scaling menu started working, and I can now view it at any scale. Closed it, tried opening again, black screen, now can't get it to display again.
jpegcrop is such a simple program that I can't imagine what I could be doing differently than what I used to do when I used to get it to work. Kwamikagami (talk) 04:33, 12 October 2018 (UTC)
@Kwamikagami: File a bug. It is probably due to some metadata issue, because otherwise the data itself would be lost and could not be recoverable by resizing. But after a quick look with a hex editor, I am unable to find the exact problem. ℺ Gone Postal (〠✉✍⏿) 05:26, 12 October 2018 (UTC)
Do you mean at jpegclub.org? I don't see anyplace to file a bug. But I did find an email address. I'll try that. [Nope, address no longer good.]
The problem appears to be with jpegcrop and not with Commons, so you'd need to contact them. Btw, running the file through exiftran -i -a -g also fixes it. ℺ Gone Postal (〠✉✍⏿) 07:38, 12 October 2018 (UTC)
Also, when I open your file with GPicView I get the error "Suspension is not allowed here", but I have no idea what it means… what is being suspended? ℺ Gone Postal (〠✉✍⏿) 07:40, 12 October 2018 (UTC)
Thanks. Submitted my info and your comments on their contact page, but that doesn't seem to be working either, just stalling out. Kwamikagami (talk) 09:42, 12 October 2018 (UTC)
Maybe it's abandonware? I use jpegtran for such things it can losslessly rotate and nearlosslessly crop (it doesn't lose quality on the parts you are not cropping out). Maybe you can give that a try. ℺ Gone Postal (〠✉✍⏿) 09:58, 12 October 2018 (UTC)
Maybe. I messaged IJG at infai.org, so maybe they'll have something to say. The fact that jpegcrop was updated for 2 years after the problem occurred suggests that it isn't just an abandonware problem. I'll take a look at jpegtran, thanks. Kwamikagami (talk) 10:27, 12 October 2018 (UTC)
JFTR it behaves similarly on my iMac. Clicking the “Original file” link gets me a solid black image in Safari. The downloaded file shows a correct icon on my desktop, but Preview displays the image as mostly black, with what looks like a couple of weirdly fractured text-windows (not Mac-like, with dark grey title bars) near the right-hand side. Neither Photoshop nor GIMP will open it, saying respectively “Could not complete your request because reading arithmetic coded JPEG files is not implemented” and “Sorry, there are legal restrictions on arithmetic coding.” I’ve seen the former message from Photoshop before (IIRC from a JPEG 2000 image created by a panorama-stitcher), but in that case GIMP had no problem opening it.—Odysseus1479 (talk) 22:48, 12 October 2018 (UTC)
Major change on how fieldescription pages will work
Where do you read that the wikitext will disappear? As far as I understand, this is really just about how old revisions are being displayed. You can still edit the current version of the wikitext as usual, you just won't be able to go back to an old version and click on "edit" there any more. --El Grafo (talk) 12:55, 12 October 2018 (UTC)
I just now detected this problem: in Category:Ruth Ozeki a redlink category appears: Category:Ruth (given name)(given name). This as-yet uncreated category has been populated with 192 (!) pages. There also exists a properly named category, Category:Ruth (given name), populated with 203 pages. I suspect the misnamed category is generated and populated by the Template:Wikidata infobox or something similar, because I've just started seeing it (I've returned to editing in the Commons after a long break). I sincerely hope this is a glitch that can be fixed at its source and won't require manual intervention! Kindly advise how to proceed. -- Cheers, Deborahjay (talk) 12:57, 12 October 2018 (UTC)
@Mike Peel: , thank you - I'll see about following through in Wikidata by adding the statement P1889 ("different from"). It seems from your explanation that my difficulty is a lack of familiarity with identical labels being differentiated in their description fields (e.g. multiple items for the label Ruth). -- Deborahjay (talk) 13:21, 12 October 2018 (UTC)
October 13
Retouched files
This was uploaded without the original. Yeah, thanks.
I'm thinking about a proposal to require users to upload images (that they didn't create) before retouching along with their retouch work. This wouldn't apply to own work, so a photographer wouldn't be forced to upload raw images.
Maria Alvarez Tubau is not the only victim. Compare File:Sudheer at South-Indian-International-Movie-Awards-6.jpg (in case of red link) with the original. This is not how you remove a watermark. I've also seen historical paintings being color-adjusted without a retouch template or the original being uploaded. You'd never find out unless you visit the source. Assuming the source is still available. If the source disappears, we'll think for the rest of our lives that some historical figure was painted like a Smurf. Some exceptions would be needed, own work and editing an image to remove derivative works before uploading here for example should always be allowed. - Alexis Jazzping plz02:04, 13 October 2018 (UTC)
I do not know how I feel about requiring it. In general contributions should be encouraged, making them intentionally harder makes first contributions less and less likely. I see quite a few individuals here who contribute in good faith and then get speedy-deleted/warned/shouted-at because they have violated some policy agreement that they were not even aware of. But when it comes to suggestions, I would actually go further and suggest that even in cases of DW a person uploads entire work, then crops with overwrite and then files a Deletion Request for the first version. The laws on what is and what is not DW change, and copyrights expire, so in the end we will be able to undelete that version, but not if it has disappeared. ℺ Gone Postal (〠✉✍⏿) 06:49, 13 October 2018 (UTC)
Good points. In this case, users shouldn't be shouted at, just informed. Only if they downright refuse to upload the unprocessed image would they be shouted at. For DW, technically I agree, but I fear it will put additional strain on admins for cases that often may not even be relevant. File:Kuno Becker y Verónica Jaspeado hablan sobre "Cars 3".jpg for example, the full background is DW but we're not even interested in that. - Alexis Jazzping plz18:51, 13 October 2018 (UTC)
Mass cache purging
As part of a CfD where I changed a license template used in ~30,000 pages, I'm looking to purge the cache of all images in a category (to see what remains in the former category). Is there any automated way to purge the cache of all images in a category? Pi.1415926535 (talk) 23:15, 13 October 2018 (UTC)
because the word "English" is always capitalized in English. Using {{language|en|en}} does not correct the problem. But when I use the same template structure here, I get
You should not actually have to use {{Language}}, as it is already called by the language parameter in {{Book}}; a simple |language=fr is enough. However, the way the parameter is encoded, prevents defining multiple languages. Someone already brought up the issue with multilanguage books on the template TP in 2016, but has not received any reply since. --HyperGaruda (talk) 05:03, 14 October 2018 (UTC)
This logo had a wrong licence. This is not a Free Art License, but a "classic" video game logo. This logo has been released by Ubisoft at E3 2011 and it has been shown on a french video gamle website june 7, 2011 [14]. The file have been uploaded the same day here at Commons website.
I think the texture logo is above threshold of originality. And copyright olders are Nadeo/Ubisoft (game developper/game publisher).
Cab someone start a deletion request ? I'm sorry i have got no time at all to do this.
Pressing 'Nominate for deletion' link on the right when viewing the image actually takes less time than leaving a comment here explaining that you do not have time to do that. ℺ Gone Postal (〠✉ • ✍⏿) 20:27, 13 October 2018 (UTC)
Don't you think if you did it would have took even less time to write this. funny. I don't see any deletion button.
So now, do what you want with this thing. I did the job. I don't contribute anymore to Commons project, other than upload files i need. And if it's all you can do or answer, it's all good, keep this file, i don't care with this. --Archimëa (talk) 06:19, 15 October 2018 (UTC)
I have no opinion on this file. If you do not see a link "Nominate for deletion" then you can take the time to learn how to use your browser. Go to any page on Commons, press Ctrl+F (on most browsers) and type "Nominate for deletion", the browser will actually find it for you. ℺ Gone Postal (〠✉ • ✍⏿) 06:59, 15 October 2018 (UTC)
Hi folks, this is Europe writing. We have this strange category Category:History of the European Union by year that includes images from far before the EC was founded. IMHO we should restrict the use of this category and its subcategories to a defined starting point (foundation of the EC, eventually one of its predecessors) and also restrict the images per country only after a country joined the EC (and needless to say: only till a country left the EC). other opinions? --Herzi Pinki (talk) 01:32, 8 October 2018 (UTC)
Support, but leave {{Category redirect}} behind, because many people accidentally place files there, so without the redirect it will be a constant battle against well intending contributors. ℺ Gone Postal (〠✉✍⏿) 06:00, 8 October 2018 (UTC)
I agree basically with what User:Martin H. already said in 2010: The whole category and all its subcategories don't make sense as they are now, since the overwhelming majority of the media in there are not about the history of the European Union. --Reinhard Müller (talk) 22:23, 8 October 2018 (UTC)
I read that discussion that was closed due to missing engagement (with the decision to delete those categories and keep them because of harmlessness), I agree that something has to be done also for the time a state is in the EC and the EC is in modus operandi. Two different points, while my primary pledge was to delete by-year categories for years there wasn't such a thing as EC, maybe we should reopen the CfD for the later years. --Herzi Pinki (talk) 22:40, 8 October 2018 (UTC)
I agree that it's two different points. However, a decision about the overall category might make a discussion about the pre-EU years obsolete, if for example it's decided to delete these categories alltogether. Anyway, I'm fine with either way of continuing. --Reinhard Müller (talk) 07:07, 9 October 2018 (UTC)
I agree to do what Herzi Pinki proposed, regardless of there will be later - or not - decisions to other points, because of its not clear, if or when that will be. Many greetings --Wilhelm Zimmerling PAR (talk) 06:55, 16 October 2018 (UTC)
Flickr images where the Wikimedia user is the Flickr user?
Occasionally, a Commons or Wikipedia user uploads an image here and they give a flickr URL for it. They clearly state here that they are one in the same with the flickr user, their username matches the flickr user name, etc, and they have completely convinced us that they are the same person. But whereas they picked a free license here, they uploaded it to flickr as "all rights reserved". Is there an SOP for how to handle such images? Do we simply not put a {{Flickrreview}} template on it at all? --B (talk) 01:58, 12 October 2018 (UTC)
if they uploaded with a free license here, why review at all? just to drive up deletion totals? need to document why you might think the uploader is not the photographer - for that is your only deletion rationale, not some vindictive off wiki reason. Slowking4 § Sander.v.Ginkel's revenge02:43, 12 October 2018 (UTC)
Yeah, we certainly shouldn't be deleting images where we are completely convinced in some fashion that the flickr user = the Wikipedian (OTRS, long-time established user, self-identifies on their flickr page as the Wikipedian, etc). It would be nice if there was something that we could use to indicate "yes, this flickr page doesn't match what is here, but we know because xyz that this uploader is the flickr user and so we don't care". --B (talk) 03:20, 12 October 2018 (UTC)
well, it is not that we don't care, it is we have a nuanced view of the messy reality of licenses on the web. you could put on a maintenance category "different license elsewhere on web," but i'm sure some would view that as a "license review" prod, just like contradictory exif. expecting one consistent license on each image is unrealistic. forcing uploaders to change licenses elsewhere, by deletion here is a vindictive way to "promote free culture", bound to be counter-productive. Slowking4 § Sander.v.Ginkel's revenge04:02, 12 October 2018 (UTC)
@B: In case of "self-identifies on their flickr page as the Wikipedian" or OTRS, {{Licensereview}} should work. But this supposed Flickr issue isn't a Flickr issue. For example, Commons:Deletion requests/File:Blue winged leafbird.jpg. Trusted user with thousands of photos, upload tagged with PD-self in 2006 (when that was common and acceptable), yet we are looking at a DR. Because.. I don't have a fucking clue. We're looking at a DR. That's a fact. As I said, it depends on the admin. - Alexis Jazzping plz19:58, 12 October 2018 (UTC)
i have a clue: some here want to destroy what they cannot create; they do not play well with others, and are enabled; because no one wants to invest the emotional labor, to get a professional standard of practice; hence the perpetual clown car. we do not have a license quality improvement process, because some are incapable of collaboration. Slowking4 § Sander.v.Ginkel's revenge04:02, 14 October 2018 (UTC)
@Alexis Jazz: If someone just tags it as {{PD}} or {{GFDL}}, then there is no claim of authorship at all. We don't know if they are saying "I made this and proclaim it to be {PD, GFDL}", "I found this on some website which proclaims it to be {PD, GFDL}", or "everything on the internet is public domain, right?" But PD-self is an affirmative claim of authorship. Obviously that claim can be challenged if it seems unlikely (no EXIF data, lots of copyvios, professional-quality image and no other uploads, found elsewhere on the internet prior to it being uploaded here), but it is a claim of authorship that should be sufficient barring evidence to the contrary. So I don't understand this DR at all. --B (talk) 12:16, 15 October 2018 (UTC)
Based on how I handle similar issues for Geograph images, I'd make the source {{Own}}, remove any licence review template, and add a link to indicate that the same image is also available on Flickr. For Geograph we have {{Also geograph}} for that last part: I don't know if an equivalent exists for Flickr. --bjh21 (talk) 19:19, 12 October 2018 (UTC)
Latest tech news from the Wikimedia technical community. Please tell other users about these changes. Not all changes will affect you. Translations are available.
Problems
Some pages, edits and users disappeared for a short while after the server switch. Missing content and users was fixed within a day. Some preferences and other things might take a few more days to fix. [15]
Wikis are updated with new and updated translations from translatewiki.net again. This will happen once a week. The developers are working on fixing the problem so we can have translation updates more often again. [16]
Changes later this week
When you create an abuse filter that prevents edits you can now write a specific error message for it. Before this all abuse filters that prevented edits had the same error message. [17]
The new version of MediaWiki will be on test wikis and MediaWiki.org from 16 October. It will be on non-Wikipedia wikis and some Wikipedias from 17 October. It will be on all wikis from 18 October (calendar).
Meetings
There will be no more meetings with the Editing team. This is because not enough Wikimedians were interested. To tell developers which bugs you think are the most important you can use Phabricator as normal. [18]
You can join the technical advice meeting on IRC. During the meeting, volunteer developers can ask for advice. The meeting will be on 17 October at 15:00 (UTC). See how to join.
Hi Jmabel. When I made Category:Bleacheries I probably didn't detected the already existing Category:Bleach works. Or maybe I got fooled by its somewhat misleading categories. As far as I see the content of both categories is same (with the exception of a quarry). I think they can be merged. -- Ies (talk) 05:33, 14 October 2018 (UTC)
Acc. to Wiktionary a bleachery (plural bleacheries) is a place or an establishment where bleaching is done. And here is a reference: en:Fall River Bleachery.
And is that definition of a bleachery in any way different from a bleach works? Because that is exactly how I would have defined that. - Jmabel ! talk03:53, 15 October 2018 (UTC)
There seems no difference between them. However, online and in my books I can't find any definition of "bleach work" and hardly any reference for it. "Bleachery" seems the commonly used term and "bleach work" just a locally preferred synonym for it. Anyhow, both categories contain images of establishments where bleaching is done and therefore should be merged. In my opinion the content of Category:Bleach works should be moved to Category:Bleacheries. Any reasoned objections? -- Ies (talk) 15:40, 15 October 2018 (UTC)
In expressions of the form a (commodity) works, “works” is invariably plural; here it’s a mainly-UK term for a factory. So I’m not surprised it couldn’t be found in the singular, and it might not appear at all in American sources.—Odysseus1479 (talk) 20:12, 16 October 2018 (UTC)
Community policy for 3D object uploads (request from WMF Legal)
Commons,
We at Foundation Legal would like to request that the community make a policy regarding 3D files, in particular addressing how weapons and other people’s inventions might be handled, and perhaps more generally addressing what types of files you all would accept of these file formats.
Uploads of STL files were turned on early in 2018. Right now, 3D files make up a small number of uploads, so we think this is a good time to address some of the issues that these files can present proactively, rather than waiting for a problem to occur. The thing that made us think about this topic is the recent news about the Defense Distributed case in which the owner of plans for a 3D gun has been making heavy efforts to try and get them online. The STL format probably isn’t great for this, but we don’t know what sorts of things someone might try to upload. Even lower resolution files could have information for making some types of weapons or perhaps certain parts of weapons that do not require high resolution imagery that are prohibited by law, or for making objects covered by someone else’s patent.
The Defense Distributed case might also lead lawmakers in the United States to introduce new bills about 3D printed weapons. There’s a chance this will lead to further restrictions on the types of content platforms like Wikimedia can host. The recent passage of FOSTA (amending CDA 230) and general interest in additional internet regulations in the United States also make this possibility more likely. A proactive policy on Commons would be a good way to show how user-driven content policies can address problems online much faster and better than legislation.
We think it would save the Foundation and the community some significant headache to address this now before a problem occurs. This is because the issues with 3D files fall into a narrow category of intellectual property and criminal laws that are not covered by either the DMCA or Section 230, which could mean that if a problem occurs, the Foundation would have to intervene (or even turn off the feature in a particularly bad situation) before a community policy could be made.
We’ve offered some information and background on our wikilegal page about 3D files that might be helpful, and are appreciative of any review you’re all able to do in this area.
To some extent Commons already has a policy, namely Commons:Non-copyright restrictions. That policy already acknowledges while, in general, Commons considers non-copyright restrictions to not be grounds for deletion of works from Commons, certain works will nonetheless be illegal for Commons to host. A very brief mention of patents is already at that page, but no specific mention of 3D printing of the objects depicted in 3D files possibly infringing on patents and definitely no mention of 3D printable weapons. It seems reasonable that we should, at the very least:
Add new non-copyright restriction tags for 3D files depicting objects that if they were 3D printed might be considered patent infringement or weapons manufacturing. The tags might perhaps be {{3D Patented}} (along the lines of {{Trademarked}}) and {{3D Weapon}} (along the lines of {{Personality rights}}).
This would allow us to begin to track such files and respond to evolving Commons policy for 3D files (or, if necessary, respond to changes in US law in this area). We should be careful to word any policy in this area to be confined to 3D file types, as freely licensed photos and illustrations depicting patented objects or weapons are very unlikely to be subject to the same restrictions. It sounds like the WMF is encouraging Commons to do more than this (i.e. craft an explicit policy along the lines of Commons:Photographs of identifiable people), but I think we should at least start with the two items I mention above (assuming there aren't any objections to recognizing that 3D files might be subject to new forms of non-copyright restriction not currently mentioned in Commons policy). —RP88 (talk) 19:16, 16 October 2018 (UTC)
Appropriate method of requesting edits to the live MOTD
Today's MOTD had an ungrammatical caption. I proposed an edit request at Template_talk:Motd/2018-10-16_(en), since Talk:Main Page suggests going to the equivalent page for a POTD problem, but it took about 10 hours for the request to be noticed by an administrator. Given that this sort of error should ideally be fixed significantly faster, what is the correct course of action for reporting an error with MOTD, and could something suitable be stated in the header of Talk:Main Page? GKFXtalk22:12, 16 October 2018 (UTC)
Photos of Anne Gamble Kennedy and Matthew Washington Kennedy
Is there any supervisor of volunteers with whom I can discuss these photos? As I have stated repeatedly, I am the sole heir of the Kennedy Estate, and as such, the owner of the copyrights of these photos. Anne Gamble Kennedy and Matthew Kennedy are deceased, and their photos date back to the 1940s. I have submitted their Last Will and Testament as proof. — Preceding unsigned comment added by Nina07011960 (talk • contribs) 21:02, 16 October 2018 (UTC)
@Nina07011960: You can write to permissions-commonswikimedia.org; however, I remind you that the subject of a photo does not normally hold a copyright, the photographer does. - Jmabel ! talk23:25, 16 October 2018 (UTC)
This file contains the mirrored Nazi symbol, and the number of tiles in it is also an abbreviation for the year, in which the bad part of German history begins, but there is no warning for users in Germany. --92.216.162.1505:40, 17 October 2018 (UTC)
There may be some sort of issue with German (or other European) laws here, but certainly in the Japanese context there is approximately zero chance that this has any relation to Nazism. - Jmabel ! talk15:54, 17 October 2018 (UTC)
Moving image dropdown problem?
I tried to move an image today but when clicking 'select a reason' the dropdown did not appear... it just repeated 'select a reason' highlighted in blue. I experimented with a couple of other files but the same thing happened. Is there an anomaly or is it just me!? (I tried purging and re-loading). Cheers. Eagleash (talk) 11:02, 17 October 2018 (UTC)
There are two "move" options. The first one is just to move the image. There is no any dropdown menu for selecting the reason. The second "move" option is actually to request a move but not to move anything and it has a dropdown menu for selecting the reason. (It works fine for me.) I suppose that you are asking about the latter as you are not a filemover? Ruslik (talk) 20:21, 17 October 2018 (UTC)
Yes the second method. I tried it a few times during the day, with the same result but not after about 18:00 (UTC). However, I just tried it again and whatever was wrong... it's fine now. Thanks. Eagleash (talk) 22:27, 17 October 2018 (UTC)
Is it possible for another volunteer or someone from the Foundation to usurp the tool? Helper is essential when transferring files from projects where you don't speak the language. GMGtalk15:41, 18 October 2018 (UTC)
I sent them 25 DMCA notices for images in this set, and should hear from them within a week. There would be nothing unusual about bundling copyright complaints, and affected users could be notified and opt in if they want. The question is whether or not it is worth the effort. I suppose this boils down to three questions: Is this commercial use, how much money do they owe for it, and do they have it? But I guess the answer to the last question is no. Watchduck (quack) 20:04, 18 October 2018 (UTC)
From a couple of searches on random heraldic terms it appears they’ve also misappropriated some of Sodacan’s work. While I’m of the opinion that generic, traditional heraldic devices (and standard compositions thereof) should not be subject to copyright, I believe that artists with a distinctive style deserve attribution.—Odysseus1479 (talk) 03:48, 19 October 2018 (UTC)
@Stranger195: There's 95KB of junk tacked on to the file, probably compressed media. Can't say much else about it, but I doubt your phone produces files like this out of the box. What model phone do you have and what app do you use to take pictures? - Alexis Jazzping plz12:50, 18 October 2018 (UTC)
How to convince others to licence without non-commercial?
When trying to obtain photos on a platform, answering a query as to why Wiki has to reject licences including non-commericial, I wrote:
"Wikipedia has been forced to create strict policies on licences by court cases it has lost, that made Wikipedia responsible for misuse by third parties. I do not know the details. It tries to convince users with objections against its ban on non-commercial use conditions with this cartoon: https://upload.wikimedia.org/wikipedia/commons/5/5f/BD-propagande-2_en.jpg"
The unexpected response was:
"Ah: so it is OK for wiki to make a small profit from our pictures, by selling them cheap.
Now all we need to know is what "inexpensive" means in terms of books and CDs, and how many billion copies they will sell ..."
Hi, Non-commercial licenses prevent reuse in most cases. A blog with advertising, a book sold in a bookshop, a documentary on TV, etc., all these require a commercial license, even if the primary objective of the publication is educational. So practically, a license which allows reuse for commercial purpose is needed in almost every case. Regards, Yann (talk) 09:20, 16 October 2018 (UTC)
That cartoon is really dire and should be deleted. There is some info on what "non commercial" means at CC FAQ and CC FAQ Mix and Defining Noncommercial and NonCommercial interpretation. I don't think court cases are a factor at all. The point of Wikipedia and Commons are to be "free content" projects where the work (text, image, video, etc) can be freely reused by anyone for any purpose. As Yann notes, a surprising number of situations are commercial-use. I think that as a photographer you have to ask what you are trying to achieve with your photography. If you are trying to make a living from it, by selling images, then the images you feel have commercial value should of course not be given away with a free licence. Perhaps still there are images you've made that you don't see yourself making money from but have sufficient educational value that Wikipedia or others might find them useful. But an awful lot of photographers do it as a hobby and are not dependent on selling images to pay their mortgage. I say then that if you are not planning to make money from your photo, what harm does it do if someone else does? Far better to let others use and enjoy your photos for the biggest audience. And normal "(c) All rights reserved" means your photos cannot be used by anyone else for 70 years after you die. So unless you become a famous wealthy photographer with lawyers to manage your estate when dead, all you've done is ensure virtually nobody will use and enjoy your photos till the next century! Which is such a waste. Lastly, having a CC licence doesn't eliminate the chance of being paid for your work. There are companies who may want to use your image in a way that they don't want to have to provide even minimal attribution and licence details, and are willing to pay. -- Colin (talk) 10:34, 16 October 2018 (UTC)
"Ah: so it is OK for wiki to make a small profit from our pictures, by selling them cheap. Technically yes. But as a non-profit, Wikimedia Foundation is they're legally obligated to spend any profit fully to support their stated purpose by, for instance, purchasing access deals from pay-to-read journals for some elite class of editors, updating and maintaining their servers, hiring lawyers to sort out the sort of legal jumbles that arise in such a huge co-operation of volunteers (and vandals) from the world over, hiring developers to maintain and improve the software the sites operate on, etc etc.
More importantly, trying to sell any content or media published in Wikimedia Foundation projects--like Commons photos or Wikipedia articles--is like selling salt water by the sea. A lesson in supply and demand. The supply is endless and available for free for anyone that can access the Net. To create demand you'd really have to add value--like hard cover books for people who really, really dislike reading on screens. Not much of a market potential there if you ask me. Releasing any rights on intellectual property is irrevocable, so Wikimedia Foundation cannot restrict the licensing on their published content--they don't own it, it's free now and forever--they're just providing some sites and systems people can use to find them. Even if the Foundation was put down tomorrow and the sites went permanently down--anyone would be free to publish the stuff on mirror sites. As a matter of fact, there already are multiple sites that mirror Wikipedia letter-to-letter.
Furthermore, I'd like to point out that non-commercial licensed media cannot be used in things like educational pamphlets, print-outs for workshops or courses, USB drive books or any other knowledge distribution if the publisher needs to accept any sort of payment from distributors or end users to help cover costs or prevent the Free Stuff Syndrome. Not just here where Internet is pm everywhere and charities to help out disadvantaged people have plenty of wealth around them to ask donations from. But in developing countries where conflict, remoteness, extreme wealth disparity, political issues, and sparser infrastructure can make spreading of knowledge a real challenge and demand stuff like print materials, fuel, fees... By releasing without non-commercial, the media can be used by the locals to educate their neighbors and countrymen without restricting their options for supporting the operation financially. --Pitke (talk) 11:30, 16 October 2018 (UTC)
i would not waste time trying to convince; rather, work with the willing. i am sympathetic to the use of NC, when you have re-users not attributing SA images, and sending collection letters to photographers who donate images to the public domain, but you are not going to convince people whose pecuniary interest is to collect fees. we lost that battle. Slowking4 § Sander.v.Ginkel's revenge13:39, 17 October 2018 (UTC)
People ask a reasonable question "Why do I have to avoid -NC if Wikipedia is not commercial?" They deserve a better answer than that Wikipedia might sell the content on DVD or a book. Wikipedia killed off Encarta, the last encyclopaedia on a DVD, and Encyclopædia Britannica's last print edition was 2010. Wikipedia doesn't even publish content any more than MS Windows publishes an operating system. If you follow the photography forums, especially US ones, there is a mindset where absolute amateurs are desperate to watermark their Flickr or 500px photos just in case someone in Hong Kong sticks it on a calendar and makes a dollar from their work. Both Wikipedia and Commons are Free Content projects, and that concept deserves an better explanation. The software world went through the same confusion, distrust and eventually reached understanding and acceptance. -- Colin (talk) 12:52, 18 October 2018 (UTC)
we do not have better explanations because it is ideology, not reason. barriers to sharing, assume you believe in a sharing economy and scholarship. for those who believe in commerce and pay to play models, the sharing ideology is a non-starter. we do not have good reasons to favor SA and not NC, it is an ideological choice. reasonable people very well could have chosen to have NC on commons.
in addition, "They deserve a better answer" and they will not get it. "Free Content projects, and that concept deserves an better explanation." reasonable people could be Open, but not here. no need for explanations, when you can block people. Slowking4 § Sander.v.Ginkel's revenge21:11, 19 October 2018 (UTC)
Sorry, I accidentally removed an edit here and can't undo it now because the section has been altered. Feel free to re-add what I removed, and sorry again for the inconvenience. --Rosenzweigτ21:14, 19 October 2018 (UTC)
I know no one will care, but I still just need to express my frustration after carefully picking the best available photos from a large bunch (horrible lighting and lousy camera, but I can't do much about that, it's either that or nothing), then trying to carefully document a series of photos during the upload so all the main information would be in the description, in the filename, and categories (which of the seven musicians standing in a row is which?) - only to get an error message that the file names are too long and no, they can't be automatically shortened, I can't get a chance to rename them, nah, all my work is just scrapped and will have to start over because someone who wrote the uploader didn't give a jimmy about the other people's work. Well, I'll try to recall which ones I chose, throw in some general description and shut the browser because, honestly, if no one else cares, neither will I. I know Commons is hopelessly broken, so why do I keep coming back? I have no idea. --Ehitaja (talk) 20:54, 17 October 2018 (UTC)
I'm not claiming to care, but what upload method did you use? Both the Upload Wizard and the old Upload form seem to fail gracefully when presented with a stupidly long filename, preserving all the other data I've entered. --bjh21 (talk) 21:24, 17 October 2018 (UTC)
With further testing, I've found that the Upload Wizard fails slightly messily if I actually try to submit an image with a 250-character filename. I can click "Back" and then "Next" and all my metadata are still there, but there's no indication that some of my files were uploaded successfully. I'll see if I can work out where to report this. --bjh21 (talk) 21:37, 17 October 2018 (UTC)
TBH, it would be sensible if the standard upload wizard gave a warning to users when they are trying to enter more than, say, 5 or 6 images that they may want to save their work in small batches. Browser failures are common and can be very frustrating, let alone unpredictable server failures etc. Alternatively, the wizard might provide a helpful link to COM:Upload tools so that newbies are aware that other methods exist. --Fæ (talk) 22:00, 17 October 2018 (UTC)
@Ehitaja: I feel your pain, but I hope you can make a lesson out of this: When uploading to Commons, use Special:Upload, Commons:VicuñaUploader, or Commons:Pattypan — not Special:UploadWizard: that is hopelessly broken. As for no one caring about your predicament, that’s an unfair and untrue aspersion, although, even with all my admiration and support for people caring about categorization and documentation and other forms of curation, even of photos with horrible lighting from lousy cameras, you did lost me at long filenames.
As a general advice for anyone in this same situation, though, I’ll say it doesn’t have to be all done in one go while uploading: First, name your files offline, in your own computer, with the names they will have in Commons, then upload everything caring only for an acceptable license and adding each file to a single bundle cat which can be even a red cat, and then, once it’s uploaded, do all your curation as regular wiki editing, on the files in that cat.
No to draw out the discussion, I'd still quickly explain my personal reasoning behind long filenames. Pictures uploaded to Commons tend to have a lot of adventures on the Internet where, quite often, nobody bothers with metadata. I can resign to letting go of my authorship, any kind of attribution and licensing (yeah, it's important but there ain't much hope to change the humanity), but I still consider metadata relevant (e.g., who is on the photo, when and where). The best chance at attaching metadata to the photo as fast as possible is writing it in the filename. Most people who reuse the photos in traditional or social media won't bother renaming them (filenames come along by default, licenses etc won't, and humans are lazy), so there's a better chance that they use the descriptions given in the filename, not inventing some general crap. The chances aren't big but it's something, at least. Also, it is much more comfy to use a photo in the wikitext when its name already says everything and you won't have to check whether you wanted Someguy12345678.jpg or Someguy12345679.jpg --Ehitaja (talk) 09:58, 19 October 2018 (UTC)
As with many "simple" questions, "how to name a file" is far more complex to do well on this project than it first appears. You may find it helpful to browse through some of the project pages at User:Fæ/Project_list as many of the projects have specific naming and template mapping schemesjust for that project. In general it's good to have a maximum of 200 characters (which approaches the limit which varies by character set) and for readability aim for fewer than 100. The scheme should go left to right from the specific to general; the most used cases being <title> + <unique identity>. However filename is not a good way to present metadata - if you are worried about metadata always persisting with the image, you should investigate how to use EXIF data on the file and how to manipulate that with offline tools before uploading to Commons. Embedding data this way will make it possible for you to track reuse elsewhere, even if the filename or file page text is lost by the reuser.
An old but interesting example is User:Fæ/Projects/Xeno-canto, from when MP3 files were not hosted on Commons, so I re-encoded the audio to ogg format and fed as much metadata as possible into the recoding in a similar way to EXIF data which sits as an invisible "header" to the file. Consequently if a user downloads and reuses a file like Haemorhous mexicanus - House Finch XC99546.ogg, their audio player should be able to display the original source URL, author, date, location and more. Unless they deliberately recode the file, this metadata will stay with the file wherever it goes. --Fæ (talk) 11:23, 19 October 2018 (UTC)
Could someone more experienced than me verify the licence of this video, please? On the source page there is no licence specified under "show more" link/button. --jdxRe:06:06, 21 October 2018 (UTC)
Is Zoomviewer down for some reason, or disabled and I'm out of the loop ? It's been a few weeks i've tried to use this tool (flash and non-flash) to check different high res images on commons, and I just cannot access to it, on any browser. Most of the time the loading fails with the message "No response from server iipsrv.fcgi" ([this map] for ex). Does anyone know what is happening with this pretty convenient tool, and how to fix it ? --Louis H. G. (talk) 12:49, 21 October 2018 (UTC)
It may be a trivial question, but I can't find the answer in the policy pages. Is it allowed to have a user account that is not linked to a single person but belongs to a group of people? Specifically, there is a group of people organizing Wiki Loves Monuments in a given country, and they would like to have a joint account for making technical edits related to this competition (sort and categorize photos, greet new participants, etc.) Such an account won't be used for uploads, policy discussions, and similar activities. This will be stated clearly on the user page. Would it be fine, or not? --Alexander (talk) 16:03, 17 October 2018 (UTC)
I believe the answer is "technically no", it's forbidden by the TOU, but Commons has allowed them occasionally anyway. GMGtalk16:12, 17 October 2018 (UTC)
The TOU states You are responsible for safeguarding your own password and should never disclose it to any third party. Presumably, any shared account would also have a shared password. Therefore TOU violation. GMGtalk17:11, 17 October 2018 (UTC)
I admit that I hadn't spotted that rule, but it doesn't prevent shared accounts. Even if "you" in the TOU can't be plural, one could use OAuth to grant API access, or have a proxy that handled authentication, or simply have one person log in multiple browser profiles with "Keep me logged in" ticked. On the other hand, I agree with Fæ below that this is probably not a good idea even if it's permitted. --bjh21 (talk) 21:08, 17 October 2018 (UTC)
Avoid it please. It's easy enough to set up a series of grouped accounts like "Alan (WLF 2018)", "Alice (WLF 2018)" and "retire" the special purpose accounts when you are done with them. If something goes wrong, such as one user appearing to disrupt the project, then there is no individual accountability for the actions taken by a multi-user account. Putting aside the non-accountability in a sockpuppetry case, it becomes impossible to, say, mass revert damage without mass reverting similar changes (or uploads) in the same period from other users. --Fæ (talk) 16:51, 17 October 2018 (UTC)
I started uploading audio recordings of bat calls with geo location added. Now this reads on the file description page:
"Camera location: ..." (or "Kameraposition: ..." in German), see e.g. File:Chirps151018-22NR.mp3. Looks and sounds strange, would there be a way to adapt this text to the specific content type? --Burkhard (talk) 11:01, 21 October 2018 (UTC)
We use term "Camera Location" to differentiate from many other locations one might have, like "Object location", "Depicted place", "Place of discovery", "Place of creation". It would be hard to be more general without needing much longer name, as we might need something like "Digitization coordinates" or 'Digitization location". Even "Point of view location" would be wrong. Now we could add something sound specific and add a flag to the template to alert us that this is "Sound file", or notice that the template is added to a file containing sound. --Jarekt (talk) 12:40, 22 October 2018 (UTC)
While thinking about it, what about uploaded oszillogram or spectrogram representations of audio content (coming soon)? From the file type (png, svg, etc.) it still could be a photograph. As an alternative to automatic file type detection an optional parameter "type=<type>" could be understood by the location template, e.g.
Probably because it is a PNG image embedded in an SVG file. The original version seems to be OK, i.e. pure vector graphics. --jdxRe:15:00, 21 October 2018 (UTC)
@DCB: conduct like this led at least one user to long-term blocks, and in my opinion is not better than overt vandalism. If you worry about a vector image (for some legal reason, or else), then nominate it for deletion. If you have a PNG version of such image which can serve as a replacement or you deem useful for another reason, then upload it as PNG. Don’t overwrite vector images with raster images. Incnis Mrsi (talk) 15:20, 21 October 2018 (UTC)
Hi, We had a copyright workshop this week-end in Bangalore, India, sponsored by the Centre for Internet and Society - Access to Knowledge, with 15 participants, 6 staff from CIS-A2K, and 3 guests. It was a very lively and successful event. Participants are committed to be involved in Wikimedia Commons in various ways (translations, contributing content, help reviewing files, facilitating OTRS permissions, etc.).
Seeing the demands, it was decided to create a online training course. The objective is to enable people to contribute to Commons with a better knowledge of copyright and Commons policies. Curriculum and details are to be decided over the next weeks. Any comment and suggestion are welcome. Regards, Yann (talk) 11:12, 22 October 2018 (UTC)
This is not the first time I see this as a deletion rationale. We should stop eliminating usable images because "there are better pictures available". Because those "better pictures" may well end up getting deleted later as copyvio. At that point, we will have no pictures, because nobody will remember there used to be other slightly less appealing images. For example:
Well, yeah, File:Vanessa Anne Hudgens, HSM2.jpg by Eryn Johnstone (dead link) looks better. The copyright status is not really clear though. No metadata because the uploader couldn't be bothered to upload the original, image disappeared from Flickr, no idea what this was cropped from.. for all we know it's a still from a DVD or a scan from a magazine. And if that's proven some day, it'll be gone.
While we may not run out of Vanessa Hudgens photos entirely anytime soon, what exactly is it that we achieve with deletions like these? - Alexis Jazzping plz18:51, 22 October 2018 (UTC)
If half the time spent writing this was spent on looking further into the copyright status of images from the same time period, it would become quickly apparent that swirley18's series of photos were not transferred using the original resolution or metadata. If you would be so kind to name one reason why you would prefer File:Mehugeons.jpg or its crop over one of swirley's photos, I'd greatly appreciate it. On a side note, if I wanted to get nitpicky File:Mehugeons.jpg was uploaded by the subject of the image, not the author. So that's a false claim of own work. Jon Kolbert (talk) 19:11, 22 October 2018 (UTC)
swirley18's photos have metadata, but were somehow transferred without. But that's not the issue.
"If you would be so kind to name one reason why you would prefer File:Mehugeons.jpg or its crop over one of swirley's photos, I'd greatly appreciate it."
Most of swirley18's photos are not sharp or Vanessa has her eyes closed. Which particular image from swirley18 is better than File:Mehugeons.jpg? Your nitpicky argument is the only valid argument in this particular case. - Alexis Jazzping plz19:33, 22 October 2018 (UTC)
"If half the time spent writing this was spent on looking further into the copyright status of images" - no, if half the time spent deleting other peoples images were spent on getting better images of living people, rather than farming flickr, then this might be a real image repository, until then it is merely a battleground for trolls. Slowking4 § Sander.v.Ginkel's revenge23:56, 22 October 2018 (UTC)
Jon Kolbert, a full body shot is no replacement for a shot of her face. Both photos are educationally useful, swirley18's photo shows her on stage but is useless if you want to see her face. One does not replace the other. That photo on stage would never be used for an infobox unless it was as a last resort. - Alexis Jazzping plz00:36, 23 October 2018 (UTC)
Art Institute of Chicago
The Art Institute of Chicago (cat) has just relaunched its website in a new design.
Apparently it now includes 44,313 images, now made available CC0, and in higher resolution than previously accessible. [21], powered by a IIIF service.
Not sure how still in-copyright images are being indicated, but some of this may be worth an upload.
Latest tech news from the Wikimedia technical community. Please tell other users about these changes. Not all changes will affect you. Translations are available.
Changes later this week
The new version of MediaWiki will be on test wikis and MediaWiki.org from 23 October. It will be on non-Wikipedia wikis and some Wikipedias from 24 October. It will be on all wikis from 25 October (calendar).
Meetings
You can join the technical advice meeting on IRC. During the meeting, volunteer developers can ask for advice. The meeting will be on 24 October at 15:00 (UTC). See how to join.
Future changes
The Community Wishlist Survey begins on 29 October. The survey decides what the Community Tech team will work on. You can post proposals from 29 October to 11 November. You can vote on proposals from 16 November to 30 November.
Do we have a policy specifically prohibiting sockpuppetry? I can't find anything; there's no link at Commons:SPI, for example, and that page has a note saying It is forbidden to use multiple undisclosed accounts in an abusive way. Such accounts will be blocked. Seems to me that it would help to have something of a sockpuppetry policy, even if it's as simple as saying "en:WP:SOCK is now our sockpuppetry policy" or making the two-sentence note on COM:SPI the entire policy. It's a common-sense concept, at least for anyone familiar with other WMF projects, so I don't think we ought to put effort into writing a policy, but since many other projects have policies on the subject, it would be helpful to designate something as our equivalent. Nyttend (talk) 22:07, 15 October 2018 (UTC)
Sockpuppetry, by definition, is the use of multiple undisclosed accounts in an abusive way. Indeed, alternative accounts are not disallowed; sockpuppetry is the abusive use of alternative/multiple accounts. The SPI quote alone is a prohibition and COM:BLOCK has the explicit reason "Abusing multiple accounts to mislead, deceive, disrupt, distort consensus or to evade blocks or other sanctions." Sockpuppetry is not allowed by policy (COM:BLOCK), and that has been, and is, the current practice. What about the current handling of socks needs to be changed? What actual problem needs to be resolved here? Эlcobbolatalk22:24, 15 October 2018 (UTC)
I would say that Western uses definitely should, the thing is that the swastika as the symbol is used by many other cultures as well, should they all be marked? ℺ Gone Postal (〠✉ • ✍⏿) 18:13, 18 October 2018 (UTC)
The operative term here is "Nazi swastikas". Obviously, a Japanese or Navajo swastika is an entirely different matter. - Jmabel ! talk18:23, 18 October 2018 (UTC)
The template {{Swastika}} only applies to files from Germany and has no legal value in any other country. Reason: The Federal Constitutional Court of Germany has no jurisdiction in any other country. Even photo's made by German troops during WW2, that are now in (for example) the Netherlands National Archives, are not subject to German law. Besides the absence of German jurisdiction, the Netherlands government after WW2 adapted a law on enemy property, which includes photo's by German troops, confiscating and nationalizing enemy property. And I am sure many other formerly occupied countries did the same. Also there is a thing called freedom of expression and freedom of press. These also apply to Wikimedia Commons, which is subject to U.S. jurisdiction. Nonetheless anyone should be careful on how and when to apply Nazi symbols, taking into account the feelings of many people towards these symbols. --oSeveno (talk) 11:13, 22 October 2018 (UTC)
The template {{Swastika}} exists to warn users that use of the image has some limitations in Germany and other countries. That's unrelated with where the original image is stored.--Pere prlpz (talk) 18:18, 23 October 2018 (UTC)
Jmabel, I agree that all historic images containing Nazi swastikas should be tagged with {{Swastika}} to alert people that in some countries like Germany, Poland and several others there are legal restrictions on how you might use that image. --Jarekt (talk) 12:58, 22 October 2018 (UTC)
Today I recognized this strange shortcut (redirect)[22] and I'm a long time user here on Commons. My first thought was a link template to Meta (like m:Template) as there are corresponding cross-wiki templates. And indeed the first intention of this was exactly this, but later this shortcut was usurped by (a) french user(s), because there is a corresponding template on FrWiki for fr:Template:Modèle (of course not exists here). Long story short, my intention is a deletion of this shortcut template as it breaks some Commons rules (which would lead to chaos if every language would occupy his own shortcut names). But before I would get some meanings to this on a wider crowd, because (it is a bit special) it is not young and it is included around 5000 times. -- User: Perhelion20:04, 20 October 2018 (UTC)
I never liked a single letter templates as I can never remember them, so replace and delete sounds like a good idea. Also {{T}} soulds like the same thing as {{Tl}}, so I wonder why do we have both? --Jarekt (talk) 12:52, 22 October 2018 (UTC)
I looked around some more. UK view from Schiphol Iceland 1.jpg shows Aboyne and the river Dee. In UK view from Schiphol Iceland 2.jpg you can see Stonehaven in the center and Aberdeen in the upper part of the picture. UK view from Schiphol Iceland 3.jpg also depicts Aberdeen with the river Dee flowing into the sea. Hope this helps ː) Cookies4ever (talk) 01:27, 25 October 2018 (UTC)
I upload a lot of airplane shots as well. What I find most helpful is flightaware.com. Find the exact flight you were on, and then export the track to Google Earth. Use the exif time on the photo, to see exactly where you took the photo. It might get a bit tricky if the camera time zone is different, but you get the idea. :) Rehman07:47, 25 October 2018 (UTC)
If you can locate one of the images exactly, then you can estimate the location of the others by using the first photo as yor reference point and calculating the distance from that photos using the time difference between between the photos and the aircraft speed (typically 900 km/h for a jet aircraft or 600 km/h for a turbo-prop aircraft flying at normal altitude). Martinvl (talk) 09:48, 25 October 2018 (UTC)
October 25
font
Hi, i want to upload a svg file (i will use object-to-path, so not scalable) using a font which is free to use for "Personal" usage but not commercial. Can i upload such SVG file? According to this & this, yes. Can someone confirm please? --আফতাবুজ্জামান (talk) 23:05, 24 October 2018 (UTC)
I have some post cards wich are not yet PD, but will be in time. Is there some way to upload those images and parc them until the release date? Often after examination and discussion it is determined that a file is not PD until X. It is then deleted and is automaticaly undeleted at X. Quite often it is only after an upload and examination and discussions by others that the dating and author is established. The post card was posted in 1939 under the trademark Loïc. Research found that the author is Laurent-Nel who died in 1960. Archives départemental de la Manche. I dont know if I will still be living in 2030.Smiley.toerist (talk) 12:33, 26 October 2018 (UTC)
Hi, You could upload them and then ask for deletion, adding a "Undelete in 20xx" category in the deletion request. Regards, Yann (talk) 13:01, 26 October 2018 (UTC)
"One major difference between Wikimedia Commons and every other Wikimedia project is that not only are redirects essentially useless, they’re also annoying as [redacted]. Now this wouldn’t as annoying if the MediaWiki Upload Wizard would ignore them… but it doesn’t, nor does it actually warn users about the fact that they just selected a category that directs to another category. However ignoring redirects would create its own problems altogether as the redirect would make more sense or is the same name as its equivalent page in the English Wikipedia so without these redirects many users wouldn’t even be able to find the pages they're looking for. However we don’t want the wizard telling users “you shall not pass”.
So the solution is actually simple, let’s say a user types in “Turkish museums” in the MediaWiki Upload Wizard they should be automatically redirected to “Museums in Turkey”, currently only a bot 🤖 does it but then the files still end up in the redirect category first. Now redirects are very handy if they are utilised correctly, someone typing “Museums of Turkey” might not know that it's “Museums in Turkey”. Now visualise this, the uploader types in “Turkish museums” in the upload form, they press “enter” and suddenly the correct “Museums in Turkey” is selected. This way category redirects could be useful rather than a mere hindrance. This is similar to what Hot-cat does today, it simply adds "the correct" category when a user wrote the redirect."
Is there a more direct method that I can contact the developers of the MediaWiki Upload Wizard? As this isn't really a policy proposal and apparently technical users don't frequent the help desk either I actually have come to realise that it's quite difficult to get an immediate hold on the developers of the MediaWiki Upload Wizard. Is there a reason why Hot-cat can immediately add the correct category when you type in a redirect while the Upload Wizard can't? --Donald Trung 『徵國單』 (No Fake News 💬) (WikiProject Numismatics 💴) (Articles 📚) 05:49, 19 October 2018 (UTC)
Why did you redact yourself? Just say annoying as hell if you don't want to say fuck. Hell used to be a swear word.. but no more really.
HotCat is a gadget. AFAIK it doesn't run on the Wikimedia servers, it completely runs on your computer. So it can go around and figure out which categories are actually redirects and fix them. UL technically could do the same, but it's probably not desireable from a technical point of view. It would make more sense if the Mediawiki software would take this into account when requesting matching categories. - Alexis Jazzping plz13:43, 19 October 2018 (UTC)
I think that the Wikimedia Commons Mobile app from Google Play already does that, I remember it actually being a lot more useful in picking categories than the MediaWiki Upload Wizard, I'm just curious as to why the developers of this tool haven't really updated it to make it more user-friendly. There's a large update to how mobile browsers view Wikimedia projects in the works which finally improve the editing environment for mobile users but Wikimedia Commons (at least upload-wise) always seems like an afterthought for the developers, both the volunteer ones and the paid ones. Redirects on Wikimedia Commons in their current state are pretty much useless despite them actually having a lot of potential, I can see them making the project a lot easier to navigate for non-English speakers however creating non-English redirects now would probably be more confusing to those people rather than guiding.
This specifically concerns the following two images:
File
Uploaded
Created
License
Comments
2015
1920-1930
PD-Old
Uploaded by a Wikimedian in a small-scale batch upload of related images, probably out of personal interest.
2018
1920-1940
cc-by-sa 4.0
Uploaded as part of a collaboration between the photo's parent institute and Wikimedia. Contains a lot more metadata, both description-wise and as exif.
Usually when I identify duplicates, I simply tag the most recent of the two for deletion/redirection. However, in this case it would mean deleting (or merging) the more "official" version, leaving the older as the main file. And then there is the issue of different licenses. What do I do now? --HyperGaruda (talk) 18:57, 24 October 2018 (UTC)
If it is really PD-Old then it can not be cc-by-sa 4.0 - the license is invalid. So, I do not see any problem with licences. Ruslik (talk) 20:09, 24 October 2018 (UTC)
The second version gives a date range of 1920-1940. If it was taken in 1940, and it's not PD in the USA due to URAA, the license would be useful. --ghouston (talk) 22:01, 24 October 2018 (UTC)
The source website says 1930, so maybe the 1940 is generic to the entire batch, but 1930 may also give URAA problems. People who don't trust PD-Art may also appreciate the license. --ghouston (talk) 22:09, 24 October 2018 (UTC)
As long as you merge all info & add the relevant redirect, it's not actually that important which file is kept. One of the main reasons we normally keep the older is so that someone doesn't get dubious "credit" for uploading photos we already have, but if there is a strong reason to the contrary for a particular photo, then that's not so big an issue. - Jmabel ! talk23:11, 24 October 2018 (UTC)
Ah, the photo should be pd-EU-anonymous in the Netherlands as made by an governmenteal organisation (air photographic service of Department of Defense) more than 70 years ago. I would say, merge with keeping the richer exif-version and apply dual license tag pd-eu-anonymous can be used in the Europe, while the CC_BY_SA can be used in the US. --Hannolans (talk) 07:28, 25 October 2018 (UTC)
NB: the date should be acoording to the page of the image 'Datering van 1920 Precisie eind Circa Datering tot 1930', so 1920-1930 --Hannolans (talk) 07:30, 25 October 2018 (UTC)
do not merge duplicate. as you see in this case, you can delete metadata. if you crosslink in other versions, then we can migrate any uses to the best one. and old superseded images are useful commons history. Slowking4 § Sander.v.Ginkel's revenge11:10, 26 October 2018 (UTC)
Thanks. I do wonder though whether PD-anon-70-EU really applies: the image is a military photograph and while it may have been created in the 1920s, I doubt it was also published at that time due to security reasons. Then again, I could not find anything about its publication history. --HyperGaruda (talk) 04:31, 27 October 2018 (UTC)
I have had this afternoon three times after creating a category that when trying to make links to Wikipedia pages I got the error "Fout: $1. Either provide the items "ids" or pairs of "sites and "titles" for corresponding page". That explanation does not help me to know what to do. I now added the old way of linking [[en: page title]] and on the Wikipedia page {{Commonscat|name of the category in Commons}}. What to do? Wouter (talk) 15:51, 27 October 2018 (UTC)
Can do with some help with this one.
The history as far as I can make out. User:Ansar Ahmad Bhatti seems to have joined Wikimedia on the 15th September 2018 according to the User's Talk page. Also according to the Talk page, on the 18th September, the User's file File:Ansar Ahmad Bhatti.jpg received a DR for being out of scope. On the 25th September 2018, the file was deleted by Admin Jcb.
On the 24th October User Jon Kolbert added a very friendly warning to the Talk page reminding the User that Wikimedia was not a personal photo album and therefore the User's images were subject to deletion. It was not clear what images were being referred to.
If we now turn to the User's Contrib page. On the 25th October the User added a image File:Ansar Ahmad Bhatti.jpg.
This agrees withe file's History page. There is little else on the Contribs page
Now from the above am I right to assume that this User is uploading a file of the sane name despite it being deleted at least once possibly twice for being out of scope? What else could explain the above. — Preceding unsigned comment added by Headlock0225 (talk • contribs) 20:32, 27 October 2018 (UTC)
@Headlock0225: Signing your posts on talk pages is required and it is a Commons guideline to sign your posts on deletion requests, undeletion requests, and noticeboards. To do so, simply add four tildes (~~~~) at the end of your comments. Your user name or IP address (if you are not logged in) and a timestamp will then automatically be added when you save your comment. Signing your comments helps people to find out who said something and provides them with a link to your user/talk page (for further discussion). Thank you. — Jeff G. ツ please ping or talk to me10:51, 28 October 2018 (UTC)
Can I withdraw PD status from files I've uploaded?
Hi. A serious question and one which I hope I won't get shot down for in flames. I have some images on here which I've created and uploaded, and marked as PD. Now I've come to the realisation that I actually don't want them as PD - and since PD by itself is not a license, it gives the item as a "gift", do I have the implicit right to withdraw PD from anything I've uploaded and reclaim copyright over the image, possibly even relicensing them as CC-BY-SA rather than a flat out "do what the **** you like with it" tag? Thanks. DaneGeld (talk) 00:40, 28 October 2018 (UTC)
Hi,
Usually, this is accepted for recent files, i.e. uploading during last week. But you didn't upload any file recently. Regards, Yann (talk) 03:52, 28 October 2018 (UTC)
If you release something into PD, it will legally stay there forever. You are not the copyright owner anymore and therefore can not issue any licenses. We can, of course, delete your PD images from Commons but legally this will change nothing. They will be still in PD. You can only hope that nobody noticed that you had released them in the public domain. Ruslik (talk) 18:15, 28 October 2018 (UTC)
Thanks, Strakhov. For 13 hours all Wikidata-mediated instances of the name "Ali" were replaced by this nonsense, injected by an IP, affecting not only Commons but most (all) versions of Wikipedia. -- Tuválkin✉✇13:35, 27 October 2018 (UTC)
Much “better”. There’s a fortunate paradox about vandalism, that high-impact edits will be swiftly noticed (like this one) while low-impact ones (if it affected a less widely used language) will stay on longer — making all kinds of vandalism equally worrisome. Additionally in this case we have Wikidata making it easier for a vandal to slip in (weaker anti-vandalism defense) and harder for editors to fix it once spotted (opaque transclusions, cumbersome interface — cp. this). -- Tuválkin✉✇13:25, 29 October 2018 (UTC)
Second time you link that thread in this thread. I'm not a wikidata-blind-believer and I've advocated for a more controlled use in wikipedia infoboxes, but I tell you ...fixing this thing was not hard to me. In fact... it was pretty easy. And I'm pretty far from being a "code god" [sic]. Strakhov (talk) 14:06, 29 October 2018 (UTC)
Remember when I said that Wikidata is an overrated GIGO machine? With a dumbed-down, gamified interface that widens the chasm between professional code gods and pedestrian casual contributers, salting the middle ground (the so called power users) where the wiki tree first set its roots? That it’s furthermore a bug-ridden greenhose flower, good for presentations and bogus beta testing but unable to withstand real-life situations in real time? Well I meant cases like this and now this one. How many more? -- Tuválkin✉✇13:35, 27 October 2018 (UTC)
Latest tech news from the Wikimedia technical community. Please tell other users about these changes. Not all changes will affect you. Translations are available.
Recent changes
You can post proposals for the Community Wishlist Survey. The survey decides what the Community Tech team will work on. You can post proposals until 11 November. You can vote on proposals from 16 November to 30 November.
The wikis now have a content security policy report. This means that you might get a warning in your javascript console when you load external resources in your user scripts. For security reasons it is recommended that you don't do this. It might not be possible to load external resources in your scripts in the future. [23]
Problems
Your watchlist can show which changes you have already seen. This did not work for a few days. It has been fixed. [24]
Changes later this week
The new version of MediaWiki will be on test wikis and MediaWiki.org from 30 October. It will be on non-Wikipedia wikis and some Wikipedias from 31 October. It will be on all wikis from 1 November (calendar).
The 2006 wikitext editor is no longer available. It will be removed from Special:Preferences. It has not been the standard editor for a long time. It was replaced by the 2010 wikitext editor. [25][26]
Meetings
You can join the technical advice meeting on IRC. During the meeting, volunteer developers can ask for advice. The meeting will be on 31 October at 15:00 (UTC). See how to join.
Hi. I'm planning to propose some sort of limited w:en:MuseScore integration with MediaWiki at the Community Wishlist Survey, since (a) there don't seem to be a lot of correctly licensed recordings of public domain music which are newer than 95 years; (b) MIDI can already be uploaded to Commons but can't be playedcan only be played through the Score extension 07:32, 26 October 2018 (UTC), so this isn't really unprecedented; (c) MuseScore generally has better playback and editing than the Score extension (in my opinion); (d) allowing MuseScore files to be uploaded to Commons would have general positive effects for other MuseScore users and musicians; (e) Commons and Wikipedia would get to benefit from the OpenScore project's development as well as the sheet music at musescore.com (well, depending on the license and how obviously non-copyvio it is).
The specific things that would probably be requested would be
(definitely) allowing Commons uploads of .mscz and .mscx files
(probably) allowing the sheet music and/or audio of the files to be displayed (as PDF and OGG respectively) when used with normal file syntax
(maybe) creation of standard template files for MuseScore files, such as a file for displaying a one-line snippet of sheet music
@Tuvalkin: MIDI doesn't have any features with regards to actual presentation, AFAIK, which is where MuseScore would have an advantage (since it's primarily supposed to be a scorewriter). LilyPond, of course, can already render scores in MediaWiki, but it lacks a graphical interface. Jc86035 (talk) 07:32, 26 October 2018 (UTC)
The Community Wishlist Survey. Please help translate to your language.
Hey everyone,
The Community Wishlist Survey is the process when the Wikimedia communities decide what the Wikimedia Foundation Community Tech should work on over the next year.
The Community Tech team is focused on tools for experienced Wikimedia editors. You can post technical proposals from now until 11 November. The communities will vote on the proposals between 16 November and 30 November. You can read more on the wishlist survey page.
P.S. Your account name in your sig on this post is weird, nobody puts "User:" as their account name. --Fæ (talk) 11:59, 30 October 2018 (UTC)
Hang on, those custom boxes are clickable, and you can click on them to both read and make a proposal. Yeah, that's not a standard way of doing these things and a "make a proposal by clicking here" would help. --Fæ (talk) 12:10, 30 October 2018 (UTC)
The User: thing is a simple copy'n'paste error (if I sign using ~~~~ it'll be signed by the bot delivering the message, not the person actually writing it) I failed to catch.
OK, I've added a short note just above the categories, as a temporary solution if nothing else. Thanks for pointing it out. /Johan (WMF) (talk) 13:09, 30 October 2018 (UTC)
Uploading a 1 MB file no longer possible with home 264/64 common home connections
Upload Wizard and older forms unusable with ADSL 256/64 (64k upload speed), and a 1MB .jpg . Invariably times out after a while, telling you to retry. Staff: please use more realistic timeout settings! Thank you! Jidanni (talk) 18:25, 31 October 2018 (UTC)
.jpg)
The statue is a Rodin, but not the painting
The new version of MediaWiki will be on test wikis and MediaWiki.org from 2 October. It will be on non-Wikipedia wikis and some Wikipedias from 3 October. It will be on all wikis from 4 October (calendar).
You can join the technical advice meeting on IRC. During the meeting, volunteer developers can ask for advice. The meeting will be on 3 October at 15:00 (UTC). See how to join.
.jpg)
Done, please see File:Zoe Quinn selfie in her car in 2014.jpg. — Jeff G. ツ please ping or talk to me 11:42, 6 October 2018 (UTC),_Vohimana_reserve,_Madagascar_(cropped).jpg)
Comment, Why not just create {{Please-do-not-overwrite-permanent-version (external)}} right now? ℺ Gone Postal (〠 ✉ • ✍ ⏿) 20:41, 13 October 2018 (UTC)
Support creation of such a template. ℺ Gone Postal (〠 ✉ • ✍ ⏿) 07:01, 15 October 2018 (UTC)
wikimedia.org; however, I remind you that the subject of a photo does not normally hold a copyright, the photographer does. - Jmabel ! talk 23:25, 16 October 2018 (UTC)
Agree with Fæ. --Jarekt (talk) 13:02, 22 October 2018 (UTC)
looks horribly pixeled when downscaled. Why's that? Too high resolution? --Redeemer (talk) 11:20, 21 October 2018 (UTC)
_de_Alphonse_de_Neuville.jpg){kind=link}
.jpeg){kind=link}
.jpg){kind=link}
_devorando_un_ant%C3%ADlope,_parque_nacional_Kruger,_Sud%C3%A1frica,_2018-07-26,_DD_06.jpg){kind=link}
![[19]](https://en.wikipedia.org/wiki/File:Matthew_Washington_Kennedy,_classical_pianist,_director_of_the_Fisk_Jubilee_Singers.jpg){kind=link}
![[20]](https://commons.wikimedia.org/wiki/File:Anne_Gamble_Portrait_by_Aaron_Douglas.jpg){kind=link}
.jpg){kind=link}
