13:19:59 Hey everybody, we (Haveno) set a bounty on https://github.com/monero-project/monero/issues/7731. Resolve the issue to claim the bounty! Details in the issue, but let us know if there are questions. 13:37:13 A bit confused haha 13:37:23 wasn't visible to everyone on IRC 13:37:39 But you could see it on IRC? 13:37:46 Yes because I'm OP 13:37:54 Ah 13:38:07 oh, i thought it was some bridge weirdness. Thanks binaryFate 13:38:21 heh binaryFate is the bridge we needed :D 13:38:38 same for you right now sethsimmons btw, but I gave you voice so starting from "A bit confused..." everyone could read 13:38:42 why are my messages not relayed to freenode tho? This matrix accoutn is grouped with my registered freenode user 13:38:55 Unfortunately monero-guard is down atm, so no automatic voicing 13:39:02 Guess it's manual voicing here 13:39:10 ah i see, i thought that was solved. 13:39:23 ErCiccione1: it is relayed, because I can read them. But the channel is moderated so only OP can see messages of unvoiced people 13:39:32 And "ErCiccione1" wasn't voiced 13:39:39 Can you fix me in #monero and #monero-markets? I don't think people can see me there either ATM. 13:39:51 yeah now i got it. 13:40:06 sethsimmons: say something in each to try? 13:40:40 Done 13:40:45 ErCiccione1: but it doesn't show [m] so your messages don't seem to be coming from matrix? 13:41:01 The [m] is just the default, it can be removed (like for me 13:41:11 * The [m] is just the default, it can be removed (like for me) 13:41:31 oh ok, makes sense then 13:42:08 beside that, my matrix user is linked to my freenode user. So my irc account is not a dummy freenode account created by matrix (which have the standard [m]) 13:42:13 Not all channels is voice-restricted, we keep it on monero-dev because of higher expected S/N ratio 13:43:36 ErCiccione1: normally monero-guard auto-voice people but it's down, so I'm not sure how the persistence of your "voice" can be. I'm also generally very confused about bridges and cross-network permissions :) 13:45:03 I registered ErCiccione and ErCiccione1 on the same account, so in theory if one is voiced the other one should be too, but it depends by how monero-guard works 13:45:22 and yeah permissions are messed up now with the spam protections, at least on matrix side 13:46:41 voice is per channel. Monero-guard is down, so nothing automatic right now 14:18:36 Inge-: yes with additional settings, not always 14:18:54 I just voiced you btw, since everyone couldn't see your question :) 14:39:24 needinfo: unfortunately the github repo and comments etc is protected to previous contributors only, yes due to spam 15:49:55 thx 16:02:30 Ok so about the multi destination uri request, is it okay to make changes directly to the existing function or should I make a new make_uri_multi (or whatever name) function with a separate api endpoint? I just don’t want to break anything people are already using 16:04:34 Adding to the existing seems best since it seems like a simple generalization of the current case. 16:04:59 Kinda depends on how the format changes though. 16:07:29 Ok cool, it shouldn’t be anything too disruptive 17:03:38 hey, any opinions for a format to make and parse payment uris with multiple destinations and amounts? https://github.com/monero-project/monero/issues/7731 17:03:44 it's probably not too compressible but I guess it could be smaller than json using keys 17:23:39 Do we know who made the original format spec ? 17:24:03 In any case, it'd be nice if it was backward compatible. 17:24:31 ie, passing one address/amount with the new rules yields an URI that old rules parse correctly. 17:31:02 .merge+ 7735 7736 17:31:02 Added 17:31:23 ^ adding boost compatibility fix early to fix compilation on some systems 17:43:20 what if it looked like this: monero:46BeWrHpwXmHDpDEUmZBWZfoQpdc6HaERCNmx1pEYL2rAcuwufPN9rXHHtyUA4QVy66qeFQkn6sfK8aHYjA3jk3o1Bv16em,46BeWrHpwXmHDpDEUmZBWZfoQpdc6HaERCNmx1pEYL2rAcuwufPN9rXHHtyUA4QVy66qeFQkn6sfK8aHYjA3jk3o1Bv16em?tx_amount=239.39014,123.55423&tx_description=donation,example 17:43:38 where commas separate duplicate kinds of data 17:43:55 or is there a better convention to follow? 17:45:00 if there's no commas then just follow original convention when parsing 17:45:15 Sounds good to me if nothing better can be found. 17:45:49 If you do intend on duplicating tx_description too, then , wooyuld have to be escaped in the actual text. 17:47:50 Oh right thanks