00:25:11 <selsta> jeffro256[m]: did you see https://www.doxygen.nl/manual/config.html#cfg_extract_anon_nspaces ?
00:28:14 <jeffro256[m]> I looked at that page and didn't see it ! I'll def check it out thanks
00:28:36 <selsta> though default should be NO
00:29:07 <jeffro256[m]> yeah someone changed it down the line so I'm git blaming it rn
00:30:06 <jeffro256[m]> IMO I've spent about 40 minutes combing though anonymous namespaces and there's not really much worth documenting
00:30:38 <jeffro256[m]> the unit_test folder is really bad about spamming the docs w anonymous namespaces also
00:31:52 <jeffro256[m]> Looks like it was changed as a tiny sliver of a huge overhaul like 6 years ago, I vote it revert that specific change
00:32:29 <jeffro256[m]> I'll open a PR in a lil bit
00:37:45 <jeffro256[m]> Ahhh, that's better
04:42:01 <mj-xmr[m]> I will be away for 2 weeks and probably won't be able to install Element on my laptop properly. You can ping me on GitHub if there's need.
04:52:29 <kinghat[m]> if you really need it, element web == element desktop.
05:02:36 <mj-xmr[m]> I'll try. Thanks.
06:48:08 <moneroextremist[> <mj-xmr[m]> "I will be away for 2 weeks and..." <- `you can use the web version of element like im doing. web version of element is super convenient when u dont wanna download the client on ur computer
07:52:13 <mj-xmr[m]> OK, thanks to both of you. It seems to have worked fine :)
10:44:49 <ErCiccione> What about a meeting? We used to have weekly meetings during hf times
11:16:43 <sech1> Meeting this weekend would be nice. We still have a few PRs not merged
12:11:51 <spirobel[m]> just to double check: the https://www.getmonero.org/resources/developer-guides/wallet-rpc.html#get_spend_proof spendproof does contain neither receiving address, nor amount, right? just proofing that a certain transaction was made by the one providing the spend proof?
12:12:11 <spirobel[m]> s/get_spend_proof/get\_spend\_proof/, s/proofing/proving/
13:50:07 <reeemuru[m]> <spirobel[m]> "just to double check: the https:..." <- is that a question? the `check_spend_proof` example below shows that the only thing in the response is a boolean value of whether or not it is valid
13:52:49 <reeemuru[m]> you are not getting the correct response?
14:01:45 <spirobel[m]> <reeemuru[m]> "you are not getting the correct..." <- I am just trying to make sure I understand correctly what it does. Does the signature contain any other information besides the fact that the sender made the transaction? what I am getting at: amount and destination address is still unknown to someone just seeing the outputs of get_spend_proof? 
14:03:05 <spirobel[m]> I have the same question for get_tx_proof: the amount is still unknown to the one seeing the information that get_tx_proof is outputing, right? The only difference to get_spend_proof is that the destionation address is part of the proof, correct?
14:05:08 <spirobel[m]> but I saw that check_tx_proof also includes the amount: 
14:05:12 * spirobel[m] uploaded an image: (162KiB) < https://libera.ems.host/_matrix/media/r0/download/matrix.org/ntJCieyhcGvwMOnIgmSEykti/image.png >
14:05:18 <reeemuru[m]> tx proof has amt when validating
14:05:19 <reeemuru[m]> spend proof does not
14:06:21 <spirobel[m]> thanks. This was the information I was looking for. 🙂
14:07:48 <reeemuru[m]> i guess an example use case is spend proof can validate a donation was done where amt doesnt matter
14:07:48 <reeemuru[m]> but tx proof could validate payment threshold where amt is required 
14:07:48 <reeemuru[m]> sry if that is vague example
14:08:42 <reeemuru[m]> spirobel[m]: np
14:09:57 <spirobel[m]> > <@reeemuru:matrix.org> i guess an example use case is spend proof can validate a donation was done where amt doesnt matter
14:09:57 <spirobel[m]> > but tx proof could validate payment threshold where amt is required 
14:09:57 <spirobel[m]> > sry if that is vague example
14:09:57 <spirobel[m]> haha this is the example I was thinking about lol I think it would be nice to verify donors but without the amounts visible to the public
14:11:27 <reeemuru[m]> sounds good, proofs are cool. you can do something login with valid proof amt too
14:12:34 <spirobel[m]> reeemuru[m]: yes I also want to do this. But I will only send the tx_proof initially and later fall back to spend_proof because I read that tx_keys might be lost.
14:12:43 <spirobel[m]> (I am working on a browser wallet)
14:54:44 * monerobull[m] uploaded an image: (142KiB) < https://libera.ems.host/_matrix/media/r0/download/matrix.org/WcUanJASkhLKpKzDziTXMBFu/Screenshot_20220429-165412.png >
14:55:18 <monerobull[m]> I don't think this is how it's supposed to go
14:59:36 <spirobel[m]> I think posting private messages without consent is childish and has no space in monero, especially not the dev channel. Maybe the beef channel would be more appropriate. 
15:00:28 <monerobull[m]> I think it's childish to hunt down the matrix of someone who down voted your ccs proposal
15:00:57 <monerobull[m]> And ask if its because i have a problem against them personally and if i even understand the purpose of the css system
15:01:16 <monerobull[m]> Instead of just addressing things publicly in the proposal, where it belongs
15:05:42 <spirobel[m]> seems like you have a personal problem after all, otherwise we would see a more professional, pragmatic reaction and not such emotional outbursts. 
15:06:52 <UkoeHB> off topic guys
15:10:05 <monerobull[m]> Sorry
15:11:13 <monerobull[m]> Not to you spirobel. I still very much believe I'm in the right to expose your bullshit.
17:53:06 <jeffro256[m]> @selsta Did you ever change your mind on https://github.com/monero-project/monero/pull/8226?
17:53:16 <jeffro256[m]> If not I'll close it
18:29:38 <selsta> I'll check if it produces any merge conflicts
18:56:11 <selsta> .merges
18:56:11 <xmr-pr> Merge queue empty
19:24:33 <binaryFate> binaries for v0.17.3.2 (CLI & GUI) are now available at getmonero.org
19:39:07 <selsta> sech1: is the optimized keccak good to merge or do you want another review?
19:39:58 <sech1> I think hyc reviewed it, but didn't click buttons on github
19:40:01 <sech1> should be good
19:41:01 <sech1> I also will make a PR that adds more tests to view tags
19:41:13 <sech1> because p2pool can generate transactions with much more than 16 outputs
19:45:55 <selsta> .merge+ 8220 8226 8235 8262 8278 8279
19:45:55 <xmr-pr> Added
19:46:01 <selsta> more unit tests are always good :P
19:46:45 <sech1> yes, current tests miss the case when there are more than 127 outputs and varint encoding kicks in
19:46:55 <sech1> *more than 128 outputs