07:08:47 <sech1> In C++, you can override default "new/delete/new[]/delete[]" operators which std::allocator uses
13:28:00 <m-relay> <l​m:matrix.baermail.fr> Is it known that on Windows the size of the DB reported by "get_info" is always 0 ?
13:28:01 <m-relay> <l​m:matrix.baermail.fr> https://github.com/monero-project/monero/issues/9513
13:34:52 <moneromooo> Just to make sure, this node isn't in restricted mode, right ?
13:35:12 <moneromooo> If it is not, then AFAIK it is not known.
13:47:23 <m-relay> <l​m:matrix.baermail.fr> to make it restricted you must pass the --restricted-rpc arg, right ?
13:47:25 <m-relay> <l​m:matrix.baermail.fr> The issue appears  without any args.
18:17:29 <m-relay> <j​effro256:monero.social> Pushed a PR that may or may not help
18:17:35 <m-relay> <j​effro256:monero.social> https://github.com/monero-project/monero/pull/9514
19:22:25 <saccharineboi> I'm working on an application that I wish to integrate Monero to. But I'm struggling to understand how one can go about it. As far as I understand there are two ways: 1) Assume that the user has installed the monero daemon and make requests to that daeomon from the application, and 2) re-implement the Monero wallet in my own application. Is this correct or is there something I'm missing?
19:24:26 <m-relay> <s​yntheticbird:monero.social> It highly depends what are your needs. Wallet and Nodes are two distinct things. I'm more inclined to believe you want to integrate monero transaction processing/wallet
19:24:58 <m-relay> <j​effro256:monero.social> Yeah what are you actually trying to do?
19:26:10 <saccharineboi> I only need the wallet functionality, e.g. view balance, send coins to someone, create/destroy wallets, etc.
19:26:29 <m-relay> <s​yntheticbird:monero.social> Then you have two options:
19:27:52 <m-relay> <s​yntheticbird:monero.social> 1. Make a fully fledged wallet in your application that implements tx scanning and all the logic behind. It will need to communicate to a monero daemon (aka monerod node aka monerod). This is hard.
19:27:53 <m-relay> <s​yntheticbird:monero.social> 2. Make use of monero-wallet-rpc. Which is basically a wallet daemon which you can communicate with through JSON-RPC.
19:32:00 <saccharineboi> If I go with 2), is it better security-wise to ship the monero-wallet-rpc alongside my app, or tell the user to install it themselves? (assume that the user is capable of installing it themselves)
19:33:35 <moneromooo> 1 is not hard if you just use wallet2.
19:33:47 <moneromooo> (which does all that tx scanning logic already)
19:36:56 <saccharineboi> Also if I'm not mistaken, I will have to implement the atomic swaps myself, as the RPC has no such calls
19:38:31 <m-relay> <s​yntheticbird:monero.social> moneromooo is right but just to be sure. what are you trying to do ***exactly*** ?
19:38:33 <m-relay> <j​effro256:monero.social> If you want atomic swap code for Monero, look at the Farcaster project or COMIT project
19:39:47 <saccharineboi> I got inspired by Mozilla Hubs and wanted to create a similar application where users can receive/send XMR
19:40:20 <saccharineboi> But in C++ (as opposed to Hubs, which runs on a browser, I think)
20:27:30 <selsta> j​effro256: invited you to an h1 issue, not sure how valid it is
21:11:34 <m-relay> <s​yntheticbird:monero.social> zamn. how many vulns are still hiding
21:15:14 <m-relay> <s​yntheticbird:monero.social> btw how can we see on github pulls that resolved vulnerabilities?
21:22:15 <m-relay> <j​effro256:monero.social> selsta: seems like a duplicate of an issue already in their other report, no?
21:22:35 <selsta> i'm not really sure what they are reporting
21:23:19 <m-relay> <j​effro256:monero.social> Maybe 0xfffc could make an flair for resolved vuln
21:23:45 <m-relay> <s​yntheticbird:monero.social> That would be very cool
21:24:46 <m-relay> <j​effro256:monero.social> Obviously, depending on the nature of the vulnerability, some fixes aren't going to be publicly flagged before merge and release
21:26:36 <m-relay> <s​yntheticbird:monero.social> Seems fair enough.