16:51:36 <xmrpow> Is the xmrig dev here on irc?
16:55:14 <asymptotically> xmrpow: no but he replies quickly to emails and github issues
17:09:33 <sech1> xmrpow what's up?
17:10:56 <sech1> you can create github issue or ask u/XMRig on reddit or ask me here
17:16:18 <xmrpow> sech1: Problem already solved ;)
17:37:15 <tevador> https://github.com/monero-project/monero/issues/6674
17:38:05 <tevador> I don't think it's high priority issue, more of an what-if evaluation
17:41:51 <hyc> pretty major change to ecosystem. basically all client/server/exhcnage software
17:42:01 <hyc> nothing would be left untouched
17:43:12 <tevador> the old format would still be supported, that's a no-brainer
17:43:25 <hyc> irrelevant
17:43:41 <hyc> if not enough sites support the new format, you can't use it when you want to
17:44:40 <hyc> it has to be a forced upgrade, like a hardfork, but even more far-reaching
17:45:02 <tevador> it could be a soft-fork
17:45:17 <rbrunner> Uh, if I ever saw an uphill battle in cryptocurrencies, I think that would be it
17:46:01 <tevador> fwiw I don't think it's worth it, but I spent enough time on it to warrant posting it
17:47:36 <hyc> might as well adopt emoji encoding
17:47:53 <hyc> more bits per character, shorter addresses
17:48:28 <selsta> let’s see how that works for Tari
17:48:40 <selsta> it’s probably appealing to the “younger” generation
17:48:42 <hyc> frankly it would bug the shit out of me
17:49:04 <tevador> that can't possibly work
17:49:06 <hyc> is there OCR software for emoji?
17:49:13 <selsta> tevador: why?
17:50:12 <tevador> because □□□□□□□□□□□□□□□□□□□□□□□□
17:51:25 <selsta> Tari has emoji addresses with hex encoding as fallback
17:51:27 <hyc> lol
17:51:47 <hyc> hex, so only 4bits per character. quite lengthy
17:53:08 <hyc> we should xmit addresses simply as a position, Nth digit of pi onward.
17:53:40 <tevador> addresses could also be bitmaps, probably 32x32 would be enough
17:54:23 <hyc> how do you type those in on a CLI?
17:55:36 <tevador> [0,0] black, [0,1] white etc.
17:55:42 <tevador> lol
17:55:48 <sech1> no need to change address format
17:55:58 <sech1> no one would write it down anyway
17:56:08 <sech1> QR codes are irrelevant
17:56:14 <sech1> decade from now some new tech will arise
17:56:57 <hyc> for quick scanning like a QR code sure you could use an RGB bitmap
17:57:27 <hyc> put a calibration stripe next to it
17:57:43 <tevador> or... just use the actual QR code
17:57:53 <tevador> which has built in ECC
17:58:01 <selsta> QR codes are quite used in the ecosystem and I also added support for it in CLI :D
17:58:07 <selsta> but not merged yet
17:59:43 <selsta> would appreciate review of someone who is familiar with windows utf8 encoding: https://github.com/monero-project/monero/pull/6488
18:00:24 <hyc> using ANSI block characters?
18:02:40 <sech1> selsta why do you single out "L" in PRINT_UTF8?
18:02:51 <selsta> hyc: unicode I think
18:02:58 <sech1> it's a C++ standard for unicode strings, not like it's going to change at all
18:03:11 <sech1> L"some unicode string"
18:03:40 <selsta> I do cout on linux / mac and wcout on Windows
18:03:47 <selsta> and wcout requires L afaik
18:03:58 <hyc> why don't the others require L ?
18:04:24 <sech1> Maybe do #define PRINT_UTF8(pre, x) std::wcout << L ## x
18:04:24 <sech1>  for Windows ???
18:04:39 <sech1> without pre
18:04:47 <sech1> or macro concatenation doesn't work this way?
18:04:52 <tevador> that won't work with std::endl
18:04:53 <selsta> sech1: that wouldn’t work with endl
18:04:56 <selsta> yea
18:05:45 <hyc> I would also define macros for WTEXTON() WTEXTOFF() (no-ops on non-Win32) as well as WEOL()
18:05:51 <hyc> and get rid of all the other inline ifdefs
18:06:17 <selsta> ok
18:09:37 <selsta> what’s the best way to do noop in C++?
18:09:49 <selsta> seen multiple suggestions on Google
18:10:00 <tevador> #define NOOP(x)
18:13:42 <hyc> yeah just an empty #define
18:15:29 <selsta> ty, updated the PR
18:19:44 <moneromooo> #define  NOOP(x) ((void)0)
18:20:00 <moneromooo> Or #define NOOP(x) do {} while(0)
18:20:14 <selsta> yea that’s what I have seen on Google, is there a reason to do this over just empty define?
18:20:15 <moneromooo> Because you just want to add a ; at the end lexically.
18:20:41 <moneromooo> The do while also helps with two if.
18:22:04 <hyc> not needed in this use case
18:23:04 <hyc> but yes, the do-while is needed if the macro may be in an if clause
18:26:50 <hyc> ^ whenever you want the thing inside {} to behave as a single statement
18:28:18 <tevador> not needed here, if (condition) ; is valid C++
18:29:43 <tevador> do { ... } while(0) is only needed if you want to put more than 1 statement in the macro