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