00:30:15 <Torr> Hey selsta 
00:30:17 <Torr> Are u around?
00:30:52 <selsta> yes
00:31:12 <Torr> U might have interest in this patch from Alpine: https://git.alpinelinux.org/aports/patch/testing/monero/system-miniupnpc.patch?id=1f4e538f405c920db57eb7371adc9304c015dfb0
00:31:40 <selsta> did you test my patch?
00:31:44 <Torr> Yup
00:31:50 <Torr> Building right now.
00:32:07 <selsta> ok, yea the linked patch looks a bit more complicated
00:32:15 <selsta> and assumes an old monero version
00:32:40 <selsta> I tested all build combinations, including static and everything seems to work fine so should be good to merge.
00:33:32 <Torr> I saw ur latest commits, the ci required some tweaking too, eh.
00:34:28 <selsta> no, I'm just using CI to test all possible combinations
00:35:40 <Torr> I see
00:36:57 <Torr> Micro$oft may prohibit mining on their servers, but they didn't count on crypto compilation XD
00:37:48 <selsta> if they would prohibit compiling the whole service would make no sense :D
00:38:13 <Torr> When do they make sense?
00:39:18 <Catcream> can't you just disable upnp via cmake? 
00:39:31 <Catcream> if that's causing some error i mean 
00:41:59 <selsta> it is a required dependency currently, would require some code changes to disable
00:42:32 <Catcream> ah okay 
00:43:11 <Catcream> having it REQUIRED seems weird, given that monero works just fine without upnp 
00:43:18 <Catcream> could probably try hacking on it some day 
00:47:20 <selsta> since it is vendored it is assumed to exist
00:47:29 <selsta> should be easy to make it optional
00:50:37 <Catcream> yeah
00:51:26 <Catcream> currently the only blocker for monero into gentoo are all the bundled deps, though I understand why you'd want to gurantee the same behaviour for nodes
00:57:41 <Torr> Oops, the build failed: http://ix.io/47OE
01:01:35 <Torr> I have that file at </usr/include/miniupnpc/miniupnpc.h>, will try a patch to remove one "minipnpc" dir from that include.
01:04:05 <selsta> that's annoying
01:06:53 <selsta> I've seen it in the git history that the header can be in different places
01:07:27 <selsta> it worked on macOS and Ubuntu for me, but seems arch puts it in a different plac 
01:08:29 <Torr> A simple '#ifdef' can take care of this.
01:08:44 <Torr> Just not sure about the variable name.
01:12:01 <Catcream> __has_include too, though its a little ugly
02:13:56 <Mochi101> Almost 35 hours in.... 10600 blocks left
02:31:48 <Torr> Mochi101: Are u syncing through a proxy?
02:32:09 <Mochi101> No, windows.
02:32:14 <selsta> and slow SSD
02:32:29 <Mochi101> selsta, it wasn't slow when I bought it. :P
02:32:36 <selsta> when did you buy it?
02:32:44 <Mochi101> Like 3-4 years ago.
02:37:44 <Torr> Ssds don't last long anyways.
02:38:28 <Torr> Beware data loss, when they fail, there's no recovery.
03:20:17 <Torr> selsta: I wrote this extra patch to build: http://ix.io/47OZ
03:20:58 <Torr> Then u just invoke cmake with '-D CMAKE_CXX_FLAGS="$CMAKE_CXX_FLAGS -DSINGLE_LEVEL_MINIUPNPC_IMPORT=1"', and it builds fine.
03:25:02 <selsta> Torr: trying something else currently
03:28:10 <Torr> Btw, Python is not mentioned on the Readme's dep list, but it's required. What do I put on the "Purpose" column of the deps table?
03:28:35 <selsta> hmm what error do you get without python?
03:29:01 <Torr> Something with "PYTHON_PROVIDER not found".
03:29:26 <Torr> Wait, I'll run the build again without it.
03:38:15 <Torr> Ahhh, I see. It's for tests: http://ix.io/47P3
03:38:46 <Torr> Needs the '-D BUILD_TESTS=ON' to fail.
03:45:46 <Torr> A Readme fix: http://ix.io/47P6
03:46:07 <Torr> Lol, top contributor.
03:46:25 <Torr> Am leaving now.
03:46:42 <Torr> See ya folks
06:58:23 <Mochi101> selsta, looks like the patch made it a bit worse for me. 39 hours and 30 minutes
15:40:44 <selsta> Mochi101: would need more testing with different hardware and config
15:41:09 <selsta> and if it is better secured against corruption on windows
15:42:43 <hyc> did you sync to the exact same height each time?
15:43:21 <selsta> he synced 1500 blocks more this time
15:44:10 <selsta> which might be half an hour or more
15:44:26 <hyc> only about 1hr15min difference
15:44:35 <hyc> seems to me to mean ~no difference
15:45:14 <hyc> so the only question is did it improve reliability
15:56:39 <hyc> selsta: actually reviewing the LMDB patch, it only affects --db-sync-mode=safe
15:57:43 <selsta> still useful for us, a lot of windows users use sync mode safe
16:25:45 <Mochi101> selsta, yeah... It's one data point.
16:26:20 <selsta> Mochi101: it only is relevant for db sync mode safe
16:26:33 <selsta> which is not set by default
16:28:22 <hyc> in fact you should set it to exactly that --db-sync-mode=safe with no further options
16:28:39 <hyc> i.e., not something like --db-sync-mode=safe:sync or whatnot
16:31:28 <hyc> (actually it doesn't matter; if you set "safe" any further options are ignored)
17:10:05 <hyc> I don't suppose you're willing to time it once more, using safe mode?
17:10:17 <hyc> Mochi101: ?
17:22:40 <Mochi101> Sure hyc
17:22:48 <Mochi101> I'll start it in a bit here
17:36:29 <Mochi101> Starting patched monerod with --db-sync-mode=safe now hyc 
17:37:02 <Mochi101> rip my ssd
17:43:38 <hyc> lol yeah, we're being a bit merciless here
17:58:00 <Mochi101> No worries.
17:58:24 <Mochi101> One day XMR will moon and I will buy all the SSDs.
18:00:28 <nioc> !tip Mochi101 1 2TB PCIe 5.0 SSD
18:00:48 <Mochi101> nice, thanks
18:39:38 <froggles> You know what I want more than monero mooning? Monero to have a stable price with common retailers accepting it
18:41:00 <Mochi101> froggles, monero.style always accepts XMR at 1 XMR = 1 XMR
18:41:11 <Mochi101> such stable
19:14:28 <tvx> luigi
19:17:22 <tvx> auriemma?
19:20:35 <gingeropolous> hrm. maybe next time there should be some sorta splash banner on getmonero.org n days leading up to a network upgrade
19:20:51 <Mochi101> ++ gingeropolous 
19:21:25 <Mochi101> Could even have one now for the next month saying that Monero recently underwent an upgrade...
19:21:42 <gingeropolous> prolly shoulda put something on xmrchain as well. ah well
19:22:49 <Mochi101> Is the tx pusher included in the onion explorer gingeropolous, or is that custom?
19:23:24 <Mochi101> tx checker and pusher for online pushing of transactions,
19:23:31 <Mochi101> nvm... I see it's included
19:23:39 <Mochi101> I've been meaning to try this.
19:49:15 <selsta> gingeropolous: we had this splash banner last time
19:49:45 <Guest26> hi there, can someone explain this to me please. i saw the ringrize increased from 11 to 16 but i can still send my monero after 10 confirmations, is it not 15 confirmations now?
19:50:08 <selsta> Guest26: confirmations are unrelated to ring size
19:51:01 <Guest26> thanks for that, why not just increase it to 100 ring size then? to be very secure
19:51:57 <Guest26> if i send my transaction through the cli client, can i choose my own ring size to be 100?
19:53:49 <selsta> no
19:54:14 <selsta> larger ring size means larger transactions and longer verification time
19:58:19 <Guest26> how would be a longer verification time, since a block is solved every two minutes, it would be confirmed in the same amount of time?
20:00:02 <selsta> I don't have numbers but it would not be sustainable. We will get higher ring sizes with Seraphis: https://www.getmonero.org/2021/12/22/what-is-seraphis.html
20:00:37 <moneromooo> Who cares if the price of bread goes up 10x, you'll still be paid every month, so you'll get more money on the same schedule.
20:03:25 <nioc> in addition to a splash banner we might try running ads   
20:03:30 <nioc> maybe during the super bowl
20:03:40 <selsta> ccs it
20:04:34 <nioc> ok
20:05:16 <Mochi101> Facebook ads.
20:05:47 <nioc> our head of marketing ^^
20:05:52 <moneromooo> I reckon on the next April 1st, we run ads for cake wallet on our website. Then on the second people say "what, there always were cake ads on the monero site, no ?"
20:06:12 <moneromooo> And then we spend the next 363 days banging heads on the wall...
20:54:47 <gingeropolous> last time, like the one that just happened?
20:55:08 <gingeropolous> or the one before that. 
20:55:40 <selsta> the one before
20:56:36 <gingeropolous> ah. well, maybe we can use seth's checklist as a template for next time... lemme find that repo
20:56:45 <gingeropolous> or was it a PR or an issue somewhere
20:57:35 <gingeropolous> oh it was there
20:57:39 <gingeropolous> https://github.com/monero-project/meta/issues/690
20:57:58 <gingeropolous> it has a check next to it
22:07:22 <duso> In FreeBSD, if I pkg remove monero-cli to install the ports 18.0 version, will it delete the blockchain forcing me to try and sync the entire blockchain again?
22:09:14 <duso> I have tried pkg delete -n monero-cli for a dry run to see but it does not give much information on what exactly the uninstallation script would be executing
22:09:55 <duso> but it does say that only 88 MB would be freed.
22:10:36 <duso> BTW, I finally managed to finish syncing the blockchain last night *\o/*
22:36:31 <Mochi101> 7 hours in and 65% done hyc