User talk:Rillke/Discuss/2019

Active discussions
← previous page2019→ next page
Babel user information
en-2 This user has intermediate knowledge of English.
de-3 Dieser Benutzer beherrscht Deutsch auf hohem Niveau.
fr-1 Cet utilisateur dispose de connaissances de base en français.
Users by language

T



User:Rillke/SVGedit.js / User:Rillke/MwJSBot.jsEdit

Your User:Rillke/SVGedit.js / User:Rillke/MwJSBot.js thing for SVG file editing behaves in a somewhat annoying manner, since it apparently inserts a pre-canned generic message into the upload summary, and does not require users to provide any indication of the nature and purpose of their edits to an SVG file. This probably will not found to be acceptable in the long term... AnonMoos (talk) 14:30, 8 July 2019 (UTC)

AnonMoos, thanks for raising this concern. Are users mandated supplying an edit summary when using the upload form for overriding a file? Can you please start a discussion on User talk:Rillke/SVGedit.js? Thank you. -- Rillke(q?) 21:43, 8 July 2019 (UTC)
It can be annoying when a user uploads a new edited file version without supplying any indication of the purpose or nature of their edits. I was already annoyed with User talk:大诺史 with respect to File:Coat of arms of South Yemen (1967-1970).svg and and File:Coat of arms of South Yemen (1970-1990).svg... AnonMoos (talk) 06:32, 9 July 2019 (UTC)
Can you please add your suggestion for a mandatory edit summary on User talk:Rillke/SVGedit.js? Thank you. -- Rillke(q?) 09:36, 9 July 2019 (UTC)
I basically know nothing about Javascript, and do not have Javascript turned on for all websites in my browser, and do not feel qualified to comment about any technical aspects -- however, I do know about UPLOAD SUMMARY best practices on Wikimedia Commons (Note: not quite the same thing as an edit summary, though your tool may slightly blur the distinction between the two). As the author of the tool, you can presumably take any comments made here into account... See near the bottom of User talk:Sarang right now for some quasi-technical comments. AnonMoos (talk) 19:36, 9 July 2019 (UTC)
Thanks for sharing the reason for your hesitation. No technical understanding is required to comment on how a particular script should work or pointing to issues with it. That's also why the scripts point to themselves in their edit summary. It's about keeping discussion and changes together and allow other people who are watching the script but not my talk page to comment. I'd rather avoid doing changes to scripts seemingly out of the blue. -- Rillke(q?) 22:55, 10 July 2019 (UTC)

┌─────────────────────────────────┘

✓ Done -- Rillke(q?) 10:19, 27 July 2019 (UTC)

User:CommonsMaintenanceBot/autopatrolled candidates.jsonEdit

Hey Rillke,

The bot no longer updates this. Can this be fixed? 1989 (talk) 20:41, 13 July 2019 (UTC)

The bot takes the data from https://tools.wmflabs.org/expose-data/jsonapi.php?action=autopatrolled_candidates - however expose-data seems to be broken then. -- Rillke(q?) 22:13, 13 July 2019 (UTC)
✓ Done. Bot needs to be unblocked. -- Rillke(q?) 12:13, 28 July 2019 (UTC)

MediaWiki:Gadget-markAdmins-data.js brokenEdit

Hello. It appears the group "Image-reviewers" has been renamed to "image-reviewers". Can you please fix that in your script? Thx. --Krd 16:24, 15 July 2019 (UTC)

Maybe next week. I didn't change anything of its code recently. -- Rillke(q?) 18:59, 15 July 2019 (UTC)
✓ Done Krd, Didym Please unblock. -- Rillke(q?) 12:06, 28 July 2019 (UTC)
Please replace Image-reviewer with image-reviewer in MediaWiki:Gadget-markAdmins.js and also in these user scripts. Thanks! -- Rillke(q?) 12:27, 28 July 2019 (UTC)


And why does User talk:CommonsMaintenanceBot link to User talk:Rillke/Discuss/2016? --Krd 16:26, 15 July 2019 (UTC)
Probably to avoid a double-redirect. -- Rillke(q?) 18:59, 15 July 2019 (UTC)

MediaWiki:Gadget-markAdmins-data.jsEdit

Der Bot dreht im Moment völlig durch, daher war vorläufig eine Sperre notwendig. --Didym (talk) 16:29, 15 July 2019 (UTC)

Das hat er auch schon als die OTRS Benutzergruppe umbenannt wurde. Wer nennt nur Benutzergruppen um ... -- Rillke(q?) 19:06, 15 July 2019 (UTC)
Hast du den Bot mitterweile wieder soweit unter Kontrolle, dass ich die Sperre aufheben kann? Notfalls vorerst ohne die Aktualisierung der Liste, aber wenigstens die anderen Aufgaben sollten wieder weiterlaufen können. --Didym (talk) 19:32, 16 July 2019 (UTC)
Nein :-( Habe diese Woche zahlende Kunden. Nächste Woche schneide ich eine Scheibe Freizeit ab. -- Rillke(q?) 21:30, 16 July 2019 (UTC)
Der CommonsMaintenanceBot sollte jetzt wieder problemlos laufen. Bitte entsperren. -- Rillke(q?) 12:15, 28 July 2019 (UTC)
Bitte ersetze Image-reviewer mit image-reviewer in MediaWiki:Gadget-markAdmins.js und ebenso in diesen Benutzerscripten. Danke! -- Rillke(q?) 12:28, 28 July 2019 (UTC)
✓ Done --Didym (talk) 13:28, 28 July 2019 (UTC)

┌─────────────────────────────────┘
Didym, vielen Dank. Könntest du auch noch diese Änderung anwenden? Es hat sich gezeigt, dass es einen Bug im Script gibt: Wenn eine Gruppe nicht anzeigen lässt (z.B. per User/common.js), dann werden alle Gruppen, die ein Benutzer hat und erst nach der versteckten Gruppe gelesen werden nicht gezeigt. -- Rillke(q?) 16:38, 28 July 2019 (UTC)

User:CommonsMaintenanceBot/autopatrolled candidates.jsonEdit

Hi, I don't know who places names in this botfile, but user:Lidewij C J. (id:262263) does not belong there. I think a dutch moderator who had some differences in the past with Lidewij C J. on NL-Wikipedia, put this user on that list. Who controls this? There is no reason this person needs to be patrollerd here. Regards, - Richardkiwi (talk) (talk) 23:07, 5 August 2019 (UTC)

Hi Richardkiwi, you are absolutely right that the list contains some users who shouldn't be auto-patrolled. It servers administrators to better find the needle in the haystack, because it is otherwise not easy to find users who do not participate in discussions and work in fancy topics. Administrators then individually assess whether a user might be trusted having their own edits patrolled. The patrol backlog is usually overwhelming. There are currently 392248+ unpatrolled edits. This in turn means that we can either decide to let edits go unpatrolled entirely or grant user groups to users.
The list states the criteria it is created from and offers links to view - besides others - global account information and the right log. Feel free to edit the description of Commons:Requests_for_rights/possible_autopatrolled_candidates, if you feel you should mention that appearing on this list doesn't automatically makes good candidates; that individual assessment is required. -- Rillke(q?) 05:37, 6 August 2019 (UTC)

VFCEdit

Can I add a custom option to tag files for speedy for criteria (F10 / G10) similar to Help:QuickDelete? 1989 (talk) 18:08, 6 August 2019 (UTC)

It is possible but undocumented (and therefore not well supported; might break at any time). One would have to observe the vFC event on $(document), and if it says 'installed', insert elements on mdUserTags, mdFileTags, mdOpt and mdCommandsExec. The interesting code for that is MediaWiki:Gadget-VisualFileChange.js/core.js. If you really want to do this, either figure out yourself or please provide me with:
  1. An edit summary on the file description page and on the uploader's talk page
  2. The templates to insert to the file description page and at the user's talk page.
Otherwise it might be just easier to select "prepend text, notify uploaders", fill it in correctly and safe as a profile. -- Rillke(q?) 22:53, 6 August 2019 (UTC)
Here's the info. 1989 (talk) 15:06, 8 August 2019 (UTC)

Chunk upload not workingEdit

Hi, we are trying to upload new version with Chunk upload tool. We successfully uploaded File:शिल्पकार चरित्रकोश खंड ५ - कृषी, पशुसंवर्धन.pdf in the series of volumes. But after this upload, from 1 August 2019 we are not able to upload new versions of following files -

The error showing - Stashfailed:This file did not pass file verification
Kindly help us to resolve the issue and guide on further steps. @Yann: for info. Regards, --सुबोध कुलकर्णी (talk) 05:51, 20 August 2019 (UTC)

@सुबोध कुलकर्णी: Hi,
Are the files available somewhere else, so we can test? If not, you can upload them to https://archive.org/ Regards, Yann (talk) 07:06, 20 August 2019 (UTC)
@Yann:, one of the volume in the series is uploded by copyright holder on Internet Archive here. I request you to test the same and guide us in further process. --सुबोध कुलकर्णी (talk) 08:00, 23 August 2019 (UTC)
@सुबोध कुलकर्णी: File is here: File:शिल्पकार चरित्रकोश खंड १ - इतिहास.pdf. Regards, Yann (talk) 08:13, 23 August 2019 (UTC)
Thanks @Yann:. How should we proceed for further uploads? Is chunk upload working now or shall we upload remaining 5 volumes to IA? --सुबोध कुलकर्णी (talk) 08:58, 23 August 2019 (UTC)
@सुबोध कुलकर्णी: I am not sure what is the problem. Are you sure you use the right format? There are PDF and JPEG files listed above. And I thought you wanted to use the DjVu format. Regards, Yann (talk) 10:38, 23 August 2019 (UTC)
@Yann:, we want to use pdf format only. The jpg files were uploaded by mistake. The publishing house, who holds the copyright has uploaded two more volumes on archive. First one is here and second is here. Please do the needful. Thanks again.--सुबोध कुलकर्णी (talk) 11:58, 23 August 2019 (UTC)
Hi, I uploaded the second one, but I can't upload the first one. It is a big file (473 MB), and I get errors repeatedly (I tried at least 10 times). I reported the bug. Regards, Yann (talk) 20:38, 23 August 2019 (UTC)
@सुबोध कुलकर्णी: For the last one, Urbanecm suggests to upload it via Help:Server-side_upload (see phab:T231119#5437922). Regards, Yann (talk) 14:59, 26 August 2019 (UTC)
The last file is uploaded now. Regards, Yann (talk) 16:05, 26 August 2019 (UTC)
@Yann, Martin Urbanec:, thanks for help in uploads. We tried IA upload tool also, but failed. We need to resolve these issues. The copyright holder Hindustan Prakashan Sanstha wants to re-license another 4 volumes, which will be uploaded on IA here as before. Kindly help us bringing the same on Commons. Thanks again, --सुबोध कुलकर्णी (talk) 07:18, 28 August 2019 (UTC)
I would be happy to do so, may I ask you to send me direct links to the files (either directly to the PDFs [preferred] or to the file description page at IA) once they are uploaded? You can do so by posting them here and pinging me (as I don't have your talk page in my watchlist), by sending me a message to my talk page, or by creating a request in Wikimedia Phabricator. Also, regardless which way you'll choose, please indicate a) filenames you want to have it under on Commons b) whether existing files are expected at the destination you indicate, to ensure I won't overwrite anything unintentionally. Thank you! --Martin Urbanec (talk) 07:48, 28 August 2019 (UTC)
@Yann, Martin Urbanec:, thanks for help. Two more volumes are uploaded on IA. The Volume 3 is to be uploaded as new version of File:शिल्पकार चरित्रकोश खंड ३ – विज्ञान, तंत्रज्ञान, शिक्षण.pdf. The Volume 6 is to be uploaded as new version of File:शिल्पकार चरित्रकोश खंड ६ – दृश्यकला.jpg. Kind request to help in upload of the same. The remaining volume 2 in the series will be uploaded soon. Regards, --सुबोध कुलकर्णी (talk) 05:52, 30 August 2019 (UTC)
✓ Done both. Yann (talk) 06:38, 30 August 2019 (UTC)
Thanks. @Yann, Jayantanth:. Please process the OTRS for all these volumes. Only one file (File:शिल्पकार चरित्रकोश - खंड ४ - न्यायपालिका, प्रशासन, संरक्षण.pdf) from this set is cleared. The ticket - [Ticket# 2019072510006855] is same for all the other volumes. @कोकणकन्या:, please note. Regards,--सुबोध कुलकर्णी (talk) 07:53, 30 August 2019 (UTC)
@सुबोध कुलकर्णी: The publisher should send a mail with a list of all books, and some quite of proof that the sender is legally authorised to release these books under a free license. An ID document and a list of on a letterhead paper would work, signed and stamped by an authorized representative of the publisher. Regards, Yann (talk) 08:41, 30 August 2019 (UTC)
@Yann, Jayantanth:,Thanks. As far as I know, they have sent this. I shall communicate this to publisher and ask them to send the docs again.--सुबोध कुलकर्णी (talk) 11:47, 30 August 2019 (UTC)

┌─────────────────────────────────────────────────────┘
@सुबोध कुलकर्णी: Actually no (at least not in this ticket). Only one book is listed, and the permission comes from a Gmail address. Regards, Yann (talk) 11:57, 30 August 2019 (UTC)

@Yann, Jayantanth:, I just asked them to send everything afresh again. You will receive the same in few hours. Btw there are two tickets regarding this case - Ticket:2019072510006855 and Ticket:2019072510006846. --सुबोध कुलकर्णी (talk) 12:01, 30 August 2019 (UTC)
Ah, that's confusing. I merged all 3 tickets into one: ticket:2019072510006846. Regards, Yann (talk) 12:25, 30 August 2019 (UTC)
I hope, the matter will be resolved once you get the mail from them. They received two tickets separately each for declaration mail & authorisation mail to permissions. So, there is no confusion regarding these 7 uploads. The upload of first file, i.e File:शिल्पकार चरित्रकोश - खंड ४ - न्यायपालिका, प्रशासन, संरक्षण.pdf(Ticket #2019060610003485) is separate issue already resolved. --सुबोध कुलकर्णी (talk) 12:48, 30 August 2019 (UTC)
Yes, but since the permission comes from the same person, and concerns the same type of material, it is better to keep them together to understand the context. Regards, Yann (talk) 12:58, 30 August 2019 (UTC)
Agreed. You might have received the mail with all required proofs. Please go through and let us know anything more to be done.--सुबोध कुलकर्णी (talk) 13:02, 30 August 2019 (UTC)
✓ Done Everything is OK. Yann (talk) 13:21, 30 August 2019 (UTC)
Thanks, grateful for your guidance and help at every stage.--सुबोध कुलकर्णी (talk) 13:48, 30 August 2019 (UTC)
@Yann, Martin Urbanec:, request for help in uploading to Commons, the last volume uploaded by publisher on IA. The Volume 2 is to be uploaded as new version ofFile:शिल्पकार चरित्रकोश खंड २ – साहित्य.pdf under the same OTRS ticket. regards, --सुबोध कुलकर्णी (talk) 15:32, 30 August 2019 (UTC)
upload_by_url failed like before. I reported this in the same bug. Regards, Yann (talk) 16:37, 30 August 2019 (UTC)
@Yann, Martin Urbanec: Yes, I also tried several times. Then pinged both of you for help. thanks--सुबोध कुलकर्णी (talk) 02:14, 31 August 2019 (UTC)
See [1]. It appears to worked, despite showing an error, and at unexpected filename. --Martin Urbanec (talk) 16:23, 1 September 2019 (UTC)
@Yann, Martin Urbanec:, the file name is correct. The file is shown in category, but if you click on the link it is giving some MediaWiki internal error. Please look into it.--सुबोध कुलकर्णी (talk) 12:03, 2 September 2019 (UTC)
Yes, it is looked at. See phab:T231276. Regards, Yann (talk) 12:49, 2 September 2019 (UTC)
@Yann, Martin Urbanec:, thanks for cooperation. It seems, the issue is resolved. Check once. --सुबोध कुलकर्णी (talk) 16:06, 10 September 2019 (UTC)

CommonsMaintenanceBot opt-outEdit

Hi! Kannst du vielleicht eine Opt-Out-Möglichkeit zum Validation-Teil des CommonsMaintenanceBot hinzufügen, die mich nicht zwingt, eine projektspezifische Benutzerseite anzulegen (d. h., die mir erlaubt, die von Meta eingebundene Version zu behalten)? Zwei Vorschläge: nach Category:Users opting out validation spam nicht nur auf der Benutzerseite, sondern auf der Benutzerdiskussionsseite suchen; und/oder ein spezieller Kommentar im Skript, z. B. /* {{ValidationOptOut}} */. (Die Skript-spezifische Variante wäre mir lieber, denn im Moment ist der Bot nur für ein bestimmtes meiner Skripte nutzlos.) --Lucas Werkmeister (talk) 11:05, 24 August 2019 (UTC)

Hallo Lucas Werkmeister, du kannst nun <span style="display:none">cmb-opt-out</span> o.ä. auf deiner Meta-Benutzerseite parken, um dem Bot zu sagen, dass er dir keine Berichte mehr über Code-Probleme im Nutzernamensraum schicken möge. Der Bot holt sich die Info per action=render von der Meta-Benutzerseite und schaut, ob das Ergebnis den Sub-String cmb-opt-out enthält. -- Rillke(q?) 11:51, 19 October 2019 (UTC)
@Rillke: klingt super, danke! Aber in der Zwischenzeit wurde das Userscript, um das es bei mir ging, schon zu einem Gadget gemacht, daher brauche ich die Funktion im Moment nicht mehr :) --Lucas Werkmeister (talk) 22:28, 27 October 2019 (UTC)

Wiki Loves Monuments 2019 - BrasilEdit

WLM - BR.pdf

Saudações. Você está recebendo esta mensagem porque, em outro ano, participou da competição fotográfica Wiki Loves Monuments. Escrevo em nome do grupo organizador do Wiki Loves Monuments deste ano para convidá-lo/convidá-la a participar de novo!

O Wiki Loves Monuments é o maior concurso fotográfico do mundo. Permite ampliar o conhecimento global sobre o Brasil, mostrando a riqueza cultural e histórica do país. Neste ano, ampliamos enormemente as listas de monumentos a serem registrados e isso ajuda na difusão da diversidade brasileira.

Participe do Wiki Loves Monuments 2019 - Brasil e ganhe prêmios! Serão premiadas as melhores fotografias e também aqueles e aquelas que mais contribuirem com registros fotográficos diversos do patrimônio cultural e histórico brasileiro. Leia as instruções com cuidado!

De novo, obrigado por participar do Wiki Loves Monuments e melhorar o conhecimento livre disponível na internet! Se tiver dúvidas, não hesite em entrar em contato!—Teles «Talk to me ˱C L @ S˲»22:00, 4 September 2019 (UTC)

Wiki Loves Monuments France 2019Edit

Bonjour,

Le concours Wiki Loves Monuments France est de retour et ouvert jusqu'à 31 septembre ! Déjà 8314 photos ont été importés cette année, vous aussi rejoignez le concours !

Le concours concerne tous les monuments présents dans la base Mérimée (qu'ils soient classés, inscrits ou simplement classés). De l'imposant château aux ruines industrielles, de la chapelle au coin de la rue aux mégalithes en forêt, c'est un impressionnant patrimoine qui attend d'être photographié et documenté. Où que vous soyez il y a des monuments autour de chez vous. Enfin, vous pouvez mettre en ligne autant de photos que vous le souhaitez de ces monuments. Pour information, le règlement est disponible sur le site du concours. Nous attendons vos photos avec impatience !

Les plus belles photos seront sélectionnées par un jury national composé d'amateurs et de professionnels, de contributeurs à Wikimedia Commons et d'acteurs du patrimoine. Un jury international sélectionnera ensuite des meilleures photographies mondiales.

Si vous avez des questions, l'équipe organisatrice se fera un plaisir d'y répondre.

P.S. : vous recevez ce message parce que vous avez participé au concours Wiki Loves Monuments en France les années précédentes. Si vous avez déjà ou si ne pouvez pas participer au concours cette année, faites passer le message autour de vous pour que de nouveaux et nouvelles photographes rejoignent l'aventure !

Bonne journée,

Sarah Krichen WMFr et Nicolas Vigneron, pour l'équipe de Wiki Loves Monuments France, 14:51, 12 September 2019 (UTC)

SVG checker downEdit

@Rillke: validator.nu is apparently giving "504 Gateway Time-out" response. validator.w3.org is working fine though. You may wish to update your script. Masum Reza📞 21:00, 27 September 2019 (UTC)

Nevermind. It's working fine at the moment. Masum Reza📞 22:29, 29 September 2019 (UTC)
For some reason, I mistook you with the creator of SVGchecker script. Sorry. Masum Reza📞 21:54, 10 October 2019 (UTC)

Can't save SVG after editingEdit

@Rillke: So I was editing a SVG, then tried to save it. But for some reason, SVG is not saving and a dialog is appearing and tells me that token parameter must be set. Maybe the csrf token is missing. Just edit a svg and try to save it. This should reproduce the problem. Masum Reza📞 21:54, 10 October 2019 (UTC)

@Rillke: Do something about this man. I have put an edit request on User talk:Rillke/MwJSBot.js. Masum Reza📞 18:13, 13 October 2019 (UTC)

script createRedirects.jsEdit

Hello The above script does not appear to be working. When I look at importScript('User:Rillke/createRedirects.js') on my page at Wikispecies it shows as a redlink. Hopefully you can help. Best regards Andyboorman (talk) 09:52, 11 October 2019 (UTC)

@Andyboorman: The importScript method doesn't work for scripts located in other wikis. You should use mw.loader.load or similar method to load scripts from other wikis. Masum Reza📞 18:31, 13 October 2019 (UTC)
@Masumrezarock100: Thanks for the info. ImportScript used to work up to a couple of days ago. Andyboorman (talk) 19:27, 13 October 2019 (UTC)
Huh. Could you provide a link to your personal JS file where you are importing this script? Masum Reza📞 19:34, 13 October 2019 (UTC)


COM:AN/BEdit

বাংলা | Deutsch | English | español | français | magyar | italiano | македонски | മലയാളം | मराठी | Nederlands | português | русский | sicilianu | svenska | Tagalog | +/−


Gtk-dialog-info.svg
Hello. This message is being sent to inform you that there is currently a discussion at Commons:Administrators' noticeboard/Blocks and protections#User:CommonsMaintenanceBot/wgCopyUploadsDomains.json. - Alexis Jazz ping plz 03:16, 17 October 2019 (UTC). Thank you.
Only just noticed you are the maintainer. I assumed it would be Magnus, who generally isn't reachable. - Alexis Jazz ping plz 03:17, 17 October 2019 (UTC)
I'll see what I can do. CMB currently faces other issues as well. Quite surprising that a webservice simply quits. It isn't supposed to do that. It's only PHP it has to serve, nothing custom. -- Rillke(q?) 07:58, 19 October 2019 (UTC)

editTokenEdit

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

Regards, Ahmadtalk 21:23, 17 October 2019 (UTC)

It is not deprecated, it has been removed from core. It was deprecated three years ago. I am surprised that you still use it. Masum Reza📞 21:27, 17 October 2019 (UTC)
Thanks for the notification. I am going to replace the instances, however I have no time for maintenance of those scripts in general. Feel free to fork. -- Rillke(q?) 08:00, 19 October 2019 (UTC)

Chunked upload on other projectsEdit

How involved would it be to adapt User:Rillke/bigChunkedUpload.js for use on a different project?

At English Wikisource we sometimes have a need to upload large files locally, typically PDF or DjVu book scans for works that are not public domain in the country of origin. And since UploadWizard is only available on Commons, that leaves—AFAICT—a script like bigChunkedUpload.js as the only option short of artificially reducing quality to get below the 100MB upload limit. --Xover (talk) 06:56, 22 October 2019 (UTC)

User_talk:Rillke/bigChunkedUpload.js#Global_or_foreign_wiki_installation describes how to install globally. However, last time I tried the script, it was broken. However, I would be glad if someone would unbreak it in case it doesn't work and help maintaining it. -- Rillke(q?) 21:43, 22 October 2019 (UTC)
Oh, there are docs for it? *blush* Sorry, I was looking in the wrong place entirely (was expecting it under User: not User_talk:) and when I failed to find it just assumed that there were no docs.
In any case, I'll try to just import it over on enWS and see how it works. Not sure I'd be much help fixing any issues since this chunked upload stuff just looks like black magic to me, but I'll certainly try.
Incidentally, phab:T94562 linked from the docs seems to be closed as resolved now. Not sure anybody ever verified that the change actually fixed the problem, but based solely on what's documented in T94562 the root cause should be fixed. --Xover (talk) 06:05, 23 October 2019 (UTC)

SVGedit funktioniert nicht!Edit

Hallo Rillke, ich wollte heute dein Skript User talk:Rillke/SVGedit.js verwenden und habe es gemäß der Beschreibung unter User:Chem Sim 2001/common.js eingefügt. Ich weiß nicht, was ich da falsch mache. Ich sehe keinerlei Veränderungen in meinem Interface und kann auch die SVG-Dateien nicht so wie erwartet bearbeiten! Hoffe du kannst mir helfen! Viele Grüße, Chem Sim 2001 (disc) 20:17, 31 October 2019 (UTC)

Es ist mit dem letzten MediaWiki Update kaputt gegangen. Der Grund ist unter MediaWiki talk:Gadget-editDropdown.js#Broken erklärt. Es wird sicher irgendwann wieder funktionieren. Schau nächste Woche nochmal vorbei. -- Rillke(q?) 10:40, 1 November 2019 (UTC)
Hallo Rillke, vielen Dank für deine Antwort. Des bedeutet, dass es irgendwann (vermutlich nächste Woche) wieder automatisch funktioniert, ohne das du etwas fixen musst? Chem Sim 2001 (disc) 10:46, 1 November 2019 (UTC)
Chem Sim 2001 Naja, hoffentlich findet sich ein Admin, der es repariert. Alternativ kannst du auf den Monobook-Skin umsteigen. Dort müssten irgendwo die Buttons erscheinen. -- Rillke(q?) 10:54, 1 November 2019 (UTC)
Okay, vielen Dank. Ich denke, ich werde zunächst einmal abwarten und schauen, was sich so ergibt. Besten Dank schonmal für die Hilfe! Chem Sim 2001 (disc) 11:06, 1 November 2019 (UTC)

Ah, und schon funktioniert es wieder, wie auch viele andere Skripte von anderen Benutzern! Chem Sim 2001 (disc) 17:59, 1 November 2019 (UTC)

Important message for file moversEdit

Commons File mover.svg

A community discussion has been closed where the consensus was to grant all file movers the suppressredirect user right. This will allow file movers to not leave behind a redirect when moving files and instead automatically have the original file name deleted. Policy never requires you to suppress the redirect, suppression of redirects is entirely optional.

Possible acceptable uses of this ability:

  • To move recently uploaded files with an obvious error in the file name where that error would not be a reasonable redirect. For example: moving "Sheep in a tree.jpg" to "Squirrel in a tree.jpg" when the image does in fact depict a squirrel.
  • To perform file name swaps.
  • When the original file name contains vandalism. (File renaming criterion #5)

Please note, this ability should be used only in certain circumstances and only if you are absolutely sure that it is not going to break the display of the file on any project. Redirects should never be suppressed if the file is in use on any project. When in doubt, leave a redirect. If you forget to suppress the redirect in case of file name vandalism or you are not fully certain if the original file name is actually vandalism, leave a redirect and tag the redirect for speedy deletion per G2.

The malicious or reckless breaking of file links via the suppressredirect user right is considered an abuse of the file mover right and is grounds for immediate revocation of that right. This message serves as both a notice that you have this right and as an official warning. Questions regarding this right should be directed to administrators. --Majora (talk) 21:36, 7 November 2019 (UTC)

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

Hello,

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

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

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

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

Thank you!

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

Commons:Bureaucrats' noticeboardEdit

A discussion regarding your bot is underway at Commons:Bureaucrats' noticeboard. Do you oppose your bot being flagged as a bot? If not, would you also be willing to modify your bot to flag the edit as it uses node.js? ~riley (talk) 20:00, 29 November 2019 (UTC)

Thank you. I replied there. -- Rillke(q?) 14:39, 8 December 2019 (UTC)

2020Edit

CMBEdit

I’ve blocked the bot as its currently malfunctioning. See their user contributions. 1989 (talk) 03:14, 9 January 2020 (UTC)

Shared global state across runs. At any time, if the list update becomes slower than run frequency the result duplicates (instead of clear set update wait clear set update, it becomes clear wait clear set update set update). Shall I try fix it before rillke answers? I'm not JS-N so my fix will probably be ugly. --Zhuyifei1999 (talk) 09:23, 9 January 2020 (UTC)

User:Rillke/gallery-sort.jsEdit

Hello, do you know if your script still works fine. I already used it successfully in the past, but this year, when I try using the script to sort the images of Commons:Picture of the Year/2019/Candidates, it don't works. When I click on "commit edits" it says "Processing", but never process. Hav you an idea please? Christian Ferrer (talk) 05:40, 26 January 2020 (UTC)

@Christian Ferrer: (talk page stalker) Special:Diff/390063602 --Zhuyifei1999 (talk) 15:26, 26 January 2020 (UTC)
Thanks you, it seems to work now. Christian Ferrer (talk) 18:03, 26 January 2020 (UTC)

Übersetzungsbenachrichtigung: Commons:Wiki Loves FolkloreEdit

Hallo Rillke,

du erhältst diese E-Mail, da du dich als Übersetzer für Deutsch bei Wikimedia Commons registriert hast.

Die Seite Commons:Wiki Loves Folklore ist zum Übersetzen vorhanden. Du kannst sie hier übersetzen:

Übersetzungspriorität dieser Seite: hoch.


Deine Hilfe bei der Übersetzung wird sehr geschätzt. Übersetzer wie du helfen dabei, dass Wikimedia Commons eine wirklich mehrsprachige Gemeinschaft ist.

Du kannst deine Einstellungen zu Benachrichtigungen ändern.

Vielen Dank, die Übersetzungskoordinatoren von Wikimedia Commons‎, 06:40, 27 January 2020 (UTC)

Inactivity toolEdit

Hello. This tool seems to be out of order. Could you please fix it? Thanks 4nn1l2 (talk) 02:01, 29 January 2020 (UTC)

bigChunkedUploadEdit

Hello, I keep getting something like this:

 Hi, Gone Postal! Thank you for testing version 0.0.1 of User:Rillke/bigChunkedUpload.js.
 00000: 1/224> in progress Upload: 0%
 00001: 1/224> Server error 0 after uploading chunk: 
 Response: 
 00009: 1/224> upload in progress Upload: 0%
 00009: 1/224> Server error 0 after uploading chunk: 
 Response: 
 00017: 1/224> upload in progress Upload: 0%
 00018: 1/224> Server error 0 after uploading chunk: 
 Response: 
 00026: 1/224> upload in progress Upload: 0%
 00026: 1/224> Server error 0 after uploading chunk: 
 Response: 
 00034: 1/224> upload in progress Upload: 0%
 00034: 1/224> Server error 0 after uploading chunk: 
 Response: 
 00042: 1/224> upload in progress Upload: 0%
 00043: 1/224> Server error 0 after uploading chunk:

Are you aware of that or is this new? ℺ Gone Postal ( ) 08:26, 2 February 2020 (UTC)

  • Hello, I am still getting this same error. Should I report it somewhere else? Is it a known thing that will not be fixed? ℺ Gone Postal ( ) 10:53, 27 February 2020 (UTC)

Cases per 100 000 is more interesting than total numberEdit

Thank you for nice plots such as File:COVID-19_Outbreak_Cases_in_Sweden_by_Number.svg. However, the number of people living in different Swedish regions differs a lot. Would it be possible for you to show cumulative incidence rate as number of cases per 100 000 instead? See data source, column 2. Also, different countries measure the number of cases very differently. Number of dead may be more reliable measure in the future, but is luckily still too low too give a stable result for small regions. Tomastvivlaren (talk) 14:26, 23 March 2020 (UTC)

Tomastvivlaren, I'm not responsible for the plots. You can see the person who uploaded the file in the User column of the File history table. -- Rillke(q?) 18:10, 19 May 2020 (UTC)

User Research - Looking for volunteersEdit

Hello @Rillke:

For a current research project we are looking for active community members in Wikipedia, Wikidata and Wikimedia Commons who are interested in filling out a survey and participating in an interview. The aim of the research is to identify opportunities for participation and access for new volunteers in the Wikimedia projects. For this purpose we would like to learn from the experiences of the already active community members and find out success factors for participation in the projects. Participation includes filling out a preliminary survey, a self-study and an interview.

If you are interested in participating, simply fill out this survey. The participants in the interviews will be selected on the basis of the answers in order to be able to consider as many different perspectives as possible.

All selected interview partners will receive a book or photo voucher of 25 euros as a thank you.

Feel free to forward this call to other people you think might share interesting experiences about Commons. If you have any questions you can of course contact me or check the project page :) On the Project Page you can also find more information.

Regards --Merle von Wittich (WMDE) (talk) 10:30, 17 June 2020 (UTC)

Validieren Optimieren von SVGs Pros and ConsEdit

Es gibt von dir ein alte Aussage:

"I see no benefit at all in scrubbing. It neither does it make the SVG easier readable (by humans) nor do we need to reduce size or similar since our SVG renderer converts them to a PNG thumb and caches the PNG. I'd say: "Never change a running system", especially if it isn't required. Making invalid SVG valid or removing references to raster images that don't exist is ok but this isn't the case here."

Die vermutlich etwas Fallbezogen war. Jedenfalls wird das Zitat von "Be..anyone" verwendet um Dateien zu validieren zu dürfen: Commons:Deletion_requests/File:Copyright-problem.svg.

Ich habe eine detalierte Essay von wann/wie man validieren soll/kann/darf auf User:JoKalliauer/Optimization geschrieben. Hierbei spreche ich mich im wesentlichen gegen Overwriting existing files ausschließlich um zu Validieren aus. Und das obwohl ich einen SVGWorkaroundBot habe der vermutlich >95% der invaliden Dateien validieren könnte. User:JoKalliauer/Optimization#invalid_elements_that_should_be_kept zählt einige invalide Elemente auf die auch bei einem reupload (aus anderen Gründen) nicht validiert werden sollten.

Du hast vl. den größeren Weitblick, deshalb würde ich dich bitten, dass du dir User:JoKalliauer/Optimization anschaust, insbesondere User:JoKalliauer/Optimization#Optimizing_SVGs_that_are_already_uploaded.

 — Johannes Kalliauer - Talk | Contributions 09:21, 27 June 2020 (UTC)

Sky WhirlEdit

 
Sky Whirl has been listed at Commons:Deletion requests so that the community can discuss whether it should be kept or not. We would appreciate it if you could go to voice your opinion about this at its entry.

If you created this gallery, please note that the fact that it has been proposed for deletion does not necessarily mean that we do not value your kind contribution. It simply means that one person believes that there is some specific problem with it.

Please remember to respond to and – if appropriate – contradict the arguments supporting deletion. Arguments which focus on the nominator will not affect the result of the nomination. Thank you!

Closeapple (talk) 23:10, 24 July 2020 (UTC)

Any chance to get the Uploads bot back?Edit

Thank you --Sailko (talk) 12:51, 26 August 2020 (UTC)

Opt out not working for botEdit

I made the appropriate edit to opt out of your notifications for User:CommonsMaintenanceBot but it doesn't seem to be working. Can you advise what I've done wrong at meta:User:Jon_(WMF) ?Jon (WMF) (talk) 04:30, 14 September 2020 (UTC)

Return to the user page of "Rillke/Discuss/2019".