User talk:Zhuyifei1999/Archive 30

From Wikimedia Commons, the free media repository
Jump to navigation Jump to search

15:59, 25 September 2017 (UTC)

I hope this is the correct contact method for your bot. It is incorrectly marking images with 'no infobox' when there are. Your bot is not recognising infoboxes. Ex: Image:Crookes Cemetery - Chapel 01-05-06.jpg. Captain Scarlet (talk) 08:47, 1 September 2017 (UTC)

@Captain Scarlet: Where is the infobox template on that page? I don't see one. --Zhuyifei1999 (talk) 15:13, 1 September 2017 (UTC)
I didn't say infobox template. There is an infobox on the example, not that infobox. Your bot's continuing to mark infoboxed media with the missing infobox tag, can it be stopped? eg: [6], there is an infobox. Captain Scarlet (talk) 10:24, 29 September 2017 (UTC)
I'm sorry, but using custom infoboxes are not endorsed by standard practice. Using standard infobox templates has many benefits, such as for Commons:Machine-readable data, standard css classes for user customization, and mobile-adjusted font sizes. Using any non-standard infobox template will not be recognized as "infobox" by the bot. You may want to transclude a standard infobox template within your custom infobox template. --Zhuyifei1999 (talk) 13:52, 29 September 2017 (UTC)

23:25, 2 October 2017 (UTC)

Did you ever get this working again? Sorry, just I do want to come back to work with Gallica images, but if there isn't a way to get them... Adam Cuerden (talk) 15:36, 3 October 2017 (UTC)

Sorry, but I am currently, and in the near future, unable to allocate any time on this project. I think, not 100% certain, Revent and Yann was investigating on some alternatives a while back, so you may want to ask them. --Zhuyifei1999 (talk) 17:57, 3 October 2017 (UTC)
Right-o. No worries. Adam Cuerden (talk) 20:59, 3 October 2017 (UTC)

Is the flickrbot marking images a bit slowly in the past day? I notice there are 250+ flickr images needing review. Some are images like this that were tagged for review 1 day ago by Flock...so I marked this one. I assume its just temporary. Just thought its strange that itr marks maybe 15-20 images at one hour and then 1-2 images in the next hour or two, --Leoboudv (talk) 09:47, 8 October 2017 (UTC)

In the log:
[2017-10-08 16:16:13] Exception reviewing image File:Langham Place Atrium night view 2015.jpg
Traceback (most recent call last):
  File "/data/project/yifeibot/o/toolserver/bryan/flickr/bots/flickreviewr.py", line 434, in <module>
    fr.run()
  File "/data/project/yifeibot/o/toolserver/bryan/flickr/bots/flickreviewr.py", line 91, in run
    review_result, data = self.review(image)
  File "/data/project/yifeibot/o/toolserver/bryan/flickr/bots/flickreviewr.py", line 199, in review
    hires = self.upload_hires(image.name, size, flickr_image)
  File "/data/project/yifeibot/o/toolserver/bryan/flickr/bots/flickreviewr.py", line 359, in upload_hires
    'Replacing image by its original image from Flickr', ignore = True)
  File "/data/project/yifeibot/o/toolserver/bryan/flickr/shared/mwclient/client.py", line 530, in upload
    data = self.raw_call('api', postdata, files)
  File "/data/project/yifeibot/o/toolserver/bryan/flickr/shared/mwclient/client.py", line 285, in raw_call
    stream.raise_for_status()
  File "/data/project/yifeibot/.local/lib/python2.7/site-packages/requests/models.py", line 937, in raise_for_status
    raise HTTPError(http_error_msg, response=self)
requests.exceptions.HTTPError: 413 Client Error: Request Entity Too Large for url: https://commons.wikimedia.org/w/api.php
Could you upload the original version for File:Langham Place Atrium night view 2015.jpg? It seems too large (100MB+) for non-chunked uploads, and the bot does not seem to support chunked uploading. --Zhuyifei1999 (talk) 16:19, 8 October 2017 (UTC)

14:21, 9 October 2017 (UTC)

Hi,

in the last days I have uploaded several JPEG images which were unmodified images directly out of my Sony RX100 and which then have been cropped by User:Embedded Data Bot with the message "This file contains embedded data:...". See, e.g., File:Gairloch_02.jpg. Naturally, I asked myself what I had done wrong and went to the Bot description page, where I only saw one line explaining that the bot detects embedded data and reacts accordingly. When I clicked further through the links on the Bot description page I read about file sharers misusing files and speedy deletion tags, which only increased my fear that I had done something wrong inadvertently. Only after wading through several of the links on the Bot page did I put together the theory that there are probably some cameras, my camera being one of them, which produce two JPEGs in one file and that the bot simply deletes the second one to save space. Is my interpretation correct? If so, I would suggest adding some more information to the bot description to, firstly, explain why the bot does what it does and, secondly, assuage the fears of camera JPEG uploaders like me. I would suggest something like the following:

There have been several situations where people misused certain file formats, like JPEGs, by putting embedded data at the end of the file which does not belong there. Furthermore, there are some digital cameras which record two versions of the same image in one JPEG file, also using embedded data, where the second version is redundant and bloats the JPEG. This bot attempts to detect embedded data and act accordingly, limited to file deletion in the cases where a misuse is probable, overwrite with truncated file, e.g. in the cases where a redundant second image is contained in a JPEG, and adding {{Embedded data}} for human verification. See also users with access to the bot.

Spike (talk) 22:29, 9 October 2017 (UTC)

@Spike: The intent is not to save space, but anti-abuse. We are constantly receiving files containing malicious / abusive embedded data. There are cases where only additional images are found, which the bot just re-uploads a truncated file, but it is not easily do-able to check if the embedded image is the same as the visible image, and therefore we cannot just say 'the file is okay'; re-uploads ensures if the embedded part are in fact malicious / abusive, any admin can easily delete the original version and keep the visible part.
There are also many cases where the embedded part cannot be identified (a recent example). For those cases, a speedy deletion tag {{Embedded data}} is added.
In any case, you are free to edit the bot's userpage. --Zhuyifei1999 (talk) 00:37, 10 October 2017 (UTC)

Google Art Project

Hello! Previously could download images using this program: http://gigafineart.herokuapp.com/gcidownload But now it does not work. A big request, teach me how to download in manual mode. Please provide detailed instructions on this example: https://www.google.com/culturalinstitute/beta/asset/friedrich-der-große/zAG2oXnnMYo6fA?ms=%7B%22x%22%3A0.5%2C%22y%22%3A0.5%2C%22z % 22% 3A8.958443957362226% 2C% 22size% 22% 3A% 7B% 22width% 22% 3A2.6305276072989403% 2C% 22height% 22% 3A1.2374999999999994% 7D% 7D

Thank you in advance--IgorSokol (talk) 16:04, 12 October 2017 (UTC)

I do not know how gigafineart works, nor I have any idea about its maintainer. I can, however, try to download it with some code I wrote a long time ago, but I am unable to allocate any time to make it a public tool. --Zhuyifei1999 (talk) 16:09, 12 October 2017 (UTC)
File:Friedrich der Große - Johann Georg Ziesenis - Google Cultural Institute.jpg --Zhuyifei1999 (talk) 16:58, 12 October 2017 (UTC)
@IgorSokol: For some reason the old script can no longer find the crop data (and I have no time to debug) and used autocrop. Could you crop it to 6312x8470 px? --Zhuyifei1999 (talk) 17:20, 12 October 2017 (UTC)

Thank you very much for the photo. But I asked you, teach me, to download images yourself. Need detailed instructions. If it is possible, I would be extremely grateful. I need to get a few dozen images from this resource--IgorSokol (talk) 18:40, 12 October 2017 (UTC)

Sorry, but I cannot, until far future when I or someone else get the code be production-ready. The script is around 700 lines of unpublished python and javascript code. I can, however, upload one or two images a day (due to limited time) if you want to give me a list of images to upload. --Zhuyifei1999 (talk) 18:53, 12 October 2017 (UTC)

Thank you very much for your willingness to help. I will send you a list in the letter--IgorSokol (talk) 19:25, 12 October 2017 (UTC)

This DR

If you understand how Flinfo works, perhaps you can give a brief reply in this DR. Best, --Leoboudv (talk) 09:06, 13 October 2017 (UTC)

I don't think I have any ideas, sorry. --Zhuyifei1999 (talk) 05:05, 14 October 2017 (UTC)

Embbedded Bot

Hi, Is the bot making incorrect edit summaries or failing to do an action? See Page history section of Special:Undelete/File:Jdsñkņñĺok.jpg It says "Protection against re-creation", which clearly it didn't do, as it was recreated twice more. Ronhjones  (Talk) 18:40, 15 October 2017 (UTC)

@Ronhjones: Those protections have an expiry of one minute, for purely technical reasons. I wouldn't want people to abuse this bot to apply long term semi-protections to arbitrary files. --Zhuyifei1999 (talk) 18:50, 15 October 2017 (UTC)
OK, I was just curious, the bot has done some excellent work in stopping the abuse. Ronhjones  (Talk) 19:16, 15 October 2017 (UTC)

15:31, 16 October 2017 (UTC)

1234

hallo — Preceding unsigned comment added by Aisshab (talk • contribs) 00:36, 29 October 2017 (UTC)

18:18, 23 October 2017 (UTC)

Structured Commons newsletter, October 25, 2017

Welcome to the newsletter for Structured Data on Wikimedia Commons! You can update your subscription to the newsletter. Do inform others who you think will want to be involved in the project!

Community updates
Things to do / input and feedback requests
Presentations / Press / Events
Audience at Structured Commons design discussion, Wikimania 2017
Team updates
The Structured Commons team at Wikimania 2017

Two new people have been hired for the Structured Data on Commons team. We are now complete! :-)

  • Ramsey Isler is the new Product Manager of the Multimedia team.
  • Pamela Drouin was hired as User Interface Designer. She works at the Multimedia team as well, and her work will focus on the Structured Commons project.
Partners and allies
  • We are still welcoming (more) staff from GLAMs (Galleries, Libraries, Archives and Museums) to become part of our long-term focus group (phabricator task T174134). You will be kept in the loop of the project, and receive regular small surveys and requests for feedback. Get in touch with Sandra if you're interested - your input in helping to shape this project is highly valued!
Research

Design research is ongoing.

  • Jonathan Morgan and Niharika Ved have held interviews with various GLAM staff about their batch upload workflows and will finish and report on these in this quarter. (phabricator task T159495)
  • At this moment, there is also an online survey for GLAM staff, Wikimedians in Residence, and GLAM volunteers who upload media collections to Wikimedia Commons. The results will be used to understand how we can improve this experience. (phabricator task T175188)
  • Upcoming: interviews with Wikimedia volunteers who curate media on Commons (including tool developers), talking about activities and workflows. (phabricator task T175185)
Development

In Autumn 2017, the Structured Commons development team works on the following major tasks (see also the quarterly goals for the team):

  • Getting Multi-Content Revisions sufficiently ready, so that the Multimedia and Search Platform teams can start using it to test and prototype things.
  • Determine metrics and metrics baseline for Commons (phabricator task T174519).
  • The multimedia team at WMF is gaining expertise in Wikibase, and unblocking further development for Structured Commons, by completing the MediaInfo extension for Wikibase.
Stay up to date!

Warmly, your community liaison, SandraF (WMF) (talk)

Message sent by MediaWiki message delivery - 14:27, 25 October 2017 (UTC)