luigi1111: i really don't like the way the CCS of the Norwegian translation was handled. You approved the proposal assuring that "Whatever the reviewer needs to know to review the translation he can surely pick up quickly.". When i said that the translations need to be manually approved by the reviewer upvoting them on weblate for transparency and credits you said "he's not going to go to 600 pages and click

upvote.". i stated that that's how the localziation system works.

Today i see that all the strings have been approved by rehrar...

that sounds like a big "fuck you" to me

(the conversation i here: repo.getmonero.org/monero-project/c…posals/merge_requests/102#note_8432)

I mean, we have a localization process that everybody follow and took time to set up. Arbitrarely bypassing it without even a comment it's not cool.

I just asked him for help clicking upvote. I also did plenty of them

I didn't go through all of them, i only saw the "reviews" of rehrar. Still, that's not cool. A comment saying that you and rehrar were going to approve the strings in behalf of somebody else would have been appreciated

noted. Too late for that now obviously, but I'll note what happened on the request

Please leave a comment on the gitlab issue about it, also adding a name (nickname or whatever) of the original reviewer as well, so that i can credit him for the work.

Oh you already said said you are going to comment, i misunderstood the last part of your comment. Ignore the first part of mine. Thanks.

added name

Thanks

Luigi1111w: Somebody started the translation of the GUI in Vietnamese, i'll se how that proceeds then i'll PR Norwegian to the GUI. Are you already considering the CCS fulfilled or are you waiting to see it merged first? Because if the latter, i'm gonna open the PR for Norwegian first.

see it merged -> the new language (Norwegian)

I consider it fulfilled; can pr them together or whenever it makes sense

Alright

I do as core directs.

Like azombie.

A topic brought up in the research meeting (which has come up previously) is the impact of requiring separate tx pubkeys for all outputs, regardless of subaddress status

Mentioning it here to help discussion

^ Isthmus UkoeHB_ etc.

A very brief issue has been opened for discussion too: monero-project/research-lab #71

<woodser> #6332 introduces a base abstract_http_client to support WebAssembly but these tests fail with “AssertionError: {u’jsonrpc’: u'2.0', u’id’: u'0', u’error’: {u’message’: u’no connection to daemon’, u’code’: -38}}“: cold_signing, get_output_distribution, mining, multisig, proofs, transfer, txpool, wallet. I suspect it has something to do with the mock http-client.cpp but I’m kind of at a loss if anyone has

any ideas?