10:18:08 This conversation should be in -translations, but i don't think anybody from core is there, so i'm writing here, since we started the conversation here. 10:18:25 The situation is more complex than i had hoped 10:18:47 they didn't only suggest and confirm their own translations, they also accepted translations of other people. 10:19:15 That means we have potentially legit translations submitted that got accepted and mixed with the non legit ones. 10:21:34 I have to take a look at each language for each project involved (GUI, CLI, monero-site), but doesn't look good. i cannot roll back, because we would lose legit translations; i cannot simply revert commits because they also confirmed what looks to be legit translations and we would lose them. 10:22:28 That's an annoying potato 10:23:37 i'll post an update later on 12:52:06 Is losing legit ones a problem since people who made them can presumably submit them again ? 12:54:16 It is. Because they did a mix of confirming their own and confirming other people's translations. We have to track every change one by one and check which one was from a reliable contributor and got confirmed and which was from the scammers and got confirmed as well. Weblate has no own tools to revert changes made by malicious users. 12:54:49 i'm still checking and writing stuff down as i speak, i'll post something here soon 13:37:47 So. I locked their accounts. in 2 of the 4 proposals they started translating before it was merged. In one case they started right after and in the last case they had not started yet (Italian). In only one case one of the user simply accepted the translations made by the other guy, in all other cases they were smarter and confirmed other people's suggestions or spreaded the work between each other to make it look 13:37:47 legit. 13:39:01 i cannot get much info about the users but they have all used linux and the same version of firefox or/and chrome 13:39:44 I can manually revert all their strings. it will be boring, it will take a bit of time, but it's not a huge deal. I'm thinking about what to do with the legit suggestions that got accepted by the scammers. 13:40:21 I may ask to trusted members of the localization workgroup to take a look and rewrite their suggestions or review the accepted ones. 13:42:30 This could take some time, what does core think about using a small part of the general fund to give a small reward to the translators who will be willing to review and fix? I have to take a look at how many strings need to be checked by translators first (i'll know when i'll start reverting), but if it's a good amount of time 1 or 2 XMR could make easier to find contributors 13:42:35 luigi1111 rehrar ^ 13:45:13 has anybody had any contact with the translators/scammers yet? I know they wrote in -community today, but i joined only now and i have no voice there yet 13:48:30 for the records, the total affected strings are 891, spreaded mostly across GUI and getmonero 13:49:12 it sucks that there's no easy way to revert a bunch of malicious changes 13:49:24 does weblate have a bounty program where maybe we could give the developers a couple of moneroj to add that? 13:49:29 (for when it happens next time) 13:51:33 binaryFate also. I'm ok with paying a nominal amount 13:53:10 does weblate have a bounty program where maybe we could give the developers a couple of moneroj to add that? -> asymptotically: actually, yes. https://github.com/WeblateOrg/weblate/issues/3040. They are on bountysource 13:53:54 You can put bounties on issues to make the dev work on them 14:10:51 Alright. i can start reverting the strings, but maybe we should have a word with these people first 14:16:33 rehrar i see you tried to contact them, did they answer? 14:36:36 .merge+ 1260 14:36:36 Added 15:01:34 So, at least one of the people claim they use deepl and then fixed the generated translation. That doesn't seem to be the case, since the translations seem to be copy pasted from deepl. 15:04:03 "We were thinking that once the website is online we would fix everything that is out of context." <- this one ends it for me 15:04:39 luigi1111 rehrar: did core take a decision about what to do with the suspended CCS? i will start reverting once i know something 15:24:31 one of the translators for french deny they used deepl or another machine translator. I just checked a random string and doesn't seem to be machine generated. selsta, do you have some examples of machine-generated translations for french? 15:31:55 The strings for french i'm looking at don't seem to be generated by deepl. Did anybody else run the strings on deepl? rehrar maybe? 15:32:28 Can be that they are actually a group of people and some of them are simply morons 15:55:32 French and Dutch seem to be legit (at least not generated using with deepl or google translate), but some Dutch translations look weird and i'm not sure they make sense. I think we need some known native speaker to take a look and give an opinion. 15:55:57 if somebody have a trusted french translator, please let me know. i'll contact the contributors i know 17:16:47 According to a trusted dutch translator the Dutch translations seem to be legit. Maybe done with a machine translator first, but then corrected and adapted. Which wouldn't be an issue if the translation is good (and that seems to be the case) 17:17:03 I also asked a trusted german speaker to review the strings. They are definitely generated by deepl and then tweaked here and there. They also ignored all the instructions, glossaries and translation memory. So yeah, their work should be rejected. 17:17:18 i'm already in contact with a french translator that will take a look soon and will let me know 17:35:33 Can look again, but both French and Dutch were definitely DeepL 17:38:28 ErCiccione[m]: https://usercontent.irccloud-cdn.com/file/iHAmOESa/Screenshot%202020-12-01%20at%2018.38.20.png 17:38:37 this is 1 to 1 DeepL translation 17:38:56 not a single character is different 17:43:07 Yes. I think some of them used deepl or other machine translations as a base, and then tweaked them if necessary. The dutch translator i asked to take a look made a deep check and found some translations that a machine translation would have missed or translated different 17:43:22 I did not find a single translation that was deepl with 1 or 2 words changed something 17:43:24 we can ask another native speaker to take a look if we want another opinion 17:44:03 I gave the Translator this link: https://translate.getmonero.org/translate/getmonero/monero-site/nl/?offset=1&q=changed_by%3ARodrigoKLX&sort_by=-priority%2Cposition&checksum= 17:44:52 This what they wrote me just now after another check: "just did a google translate check , google actually did build the sentence better then our guy. I'm pretty sure, it's not machine translated" 17:45:14 Dutch is also DeepL 17:45:16 not google translator 17:45:33 so he should check with DeepL and not Google Translator 17:45:46 yeah. They tried first deepl and now they are checking google translator 17:46:15 With french, it is always deeplL with sometimes 1 or 2 words changed 17:46:28 so they can’t claim they did not use DeppL 17:48:01 So the translator should at least be honest about it 17:48:06 they probably did use a machine translator at first or some other tools and then tweaked it to make it smooth. I'm still waiting for the opinion of the trusted french translator 17:48:30 so they can’t claim they did not use DeppL <- some of them confirmed they used deepl as base, somebody else used their local tools 17:50:33 https://usercontent.irccloud-cdn.com/file/12P4rmU7/Screenshot%202020-12-01%20at%2018.49.58.png 17:50:43 again such a long text with not a single word different from DeepL 17:51:53 We don't know about french yet. I only got feedbacks for german and dutch at the moment 17:56:32 https://usercontent.irccloud-cdn.com/file/VGDKJLRV/Screenshot%202020-12-01%20at%2018.56.23.png 17:56:36 undecided what to do yet. if they are clearly bad faith we'll delete 17:56:55 all deeplL translated with triptych manually getting replaced from translation 17:57:03 either way new rules are in order 17:57:23 they all ur using machine translations and never disclosed that 17:58:21 Luigi1111: i'll post updates when i know something. New rules will be appreciated. 17:59:32 Selsta: yes they are, but that itself is not a problem. But german for example is sloppy at best if we assume good faith. 18:00:08 The german one is a straight up scam anyway. 18:00:13 Talking about the other languages. 18:03:31 Yeah 18:04:25 Anyway, IMO it would be BS to pay for machine translations if it does not get disclosed ahead. A lot of contributors that don’t get paid put way more effort into the translations. 18:04:43 And Dutch, French and also Greek are clearly machine translated with 1 or 2 words changed here and there. 18:06:04 thanks for working on straightening this out. we'll get the new rule ironed out before accepting any more translation proposals 18:09:05 selsta: imo it doesn't matter how the translation is done, as long as it is of high quality. At least one of them use good tools locally, so at least some of them know what they are doing. 18:09:38 Who used good tools locally? 18:09:47 luigi1111: ok. Let me know if you want my opini 18:09:55 on on somethinf 18:12:23 selsta: rodrigoklx, one of the two dutch translators 18:13:56 I'm away till the weekend so might not get done right away. but anyway the translations in ideas will not get moved until after 19:07:13 ErCiccione[m]: I did talk with the greek guy and the Italian guy. Just a moment let me get to a computer and I'll say what I found. It's a deeper mystery. 19:35:46 ok. Sorry for the delay. 19:36:27 So basically, the greek guy says he doesn't know any of the other guys except for the Italian guy (staff guy). The others he doesn't know. After speaking with staff a bit, I think he's somewhat likely to be legit. 19:36:46 Did he admit to using Google translate? 19:37:05 greek guy? no. Italian guy didn't start translating yet. 19:37:28 He clearly does use Google Translate with one or two words changed here and there. 19:37:32 Though because of the abundance of Italian speakers we have, including in this room, Italian seemed like one of the least likely to sneak through 19:37:37 the Greek guy? 19:37:41 yes 19:38:34 It's getting too complicated for me to remember who did use what and who didn't. We need a spreadsheet. :P Or maybe just something here, like: 19:38:41 Greek: Google Translate + small changes 19:38:45 Italian: Not started 19:38:55 German: DeepL. Complete trash. 19:39:21 Dutch and French are DeepL with some words changed too 19:39:23 Dutch: Machine translated + small changes 19:39:30 French: DeepL + small changes 19:39:47 so really, none of these are legit then, huh? 21:09:50 rehrar: I think - for the Italian - he used DeepL too. There're some weird words that are totally out of context in past translations work he posted on Gitlab. 21:10:34 SerHack: great thinking. You looked at his prior work for the other orgs? 21:10:41 Yeesh. I wonder if we should let those people know. 21:10:58 rehrar: yes. 21:11:18 these people are definitely all connected. A group of people that have decided to band together and go around to different projects or something 21:11:28 extract as much value as possible, and hop away 22:11:46 luigi1111: As far as I'm concerned, I'm ok with paying pallpark discussed (1-2 XMR) to volunteers who can sanitize the translation mess 22:12:03 From General Fund. 22:21:29 cool 22:30:39 I was wondering how I can help. Yet, i as a volunteer i prefer not to he paid. Is this a good first issue to jump into? 22:30:54 * I was wondering how I can help. Yet, i as a volunteer i prefer not to be paid. Is this a good first issue to jump into? 22:55:29 jump into clarkkozak[m], jump into 22:57:02 how can I help? Some like some copy and pasting previous git commits, no?