< Arvidt>
Congrats for Release! Where can one see how many Onion Nodes are there? bitnodes leaderboard does only show _26_ ?
< sipa>
Arvidt: there is no authorative source
< Arvidt>
Yes I know
< sipa>
so i'm afraid the only correct answer is "nobody knows" - various sites may try to index them, but that's always going to be approximate
< Arvidt>
Bitnodes knows 9 thousand nodes, strange it knows only 26 onion nodes
< sipa>
my crawler knows a few 1000
< luke-jr>
quite possible for onions to not be listening either, in which case glwt :P
< luke-jr>
sipa: only torV2 tho, right?
< sipa>
luke-jr: yes
< luke-jr>
my crawler has only been doing tor for like a month and it sees 4012 :o
< bitcoin-git>
[bitcoin] fanquake opened pull request #20938: Fix linking against -latomic when building for riscv (master...fix_riscv_atomic_usage) https://github.com/bitcoin/bitcoin/pull/20938
< bitcoin-git>
[bitcoin] fanquake opened pull request #20939: build: fix RELOC_SECTION security check for bitcoin-util (master...fix_bitcoin_util_reloc_section) https://github.com/bitcoin/bitcoin/pull/20939
< aj>
fanquake: nice
< fanquake>
aj: now that's solved I guess I'm free to go watch the cricket
< sipa>
the sport or the insect?
< luke-jr>
insect sounds more interesting
< sipa>
agree.
< fanquake>
😢 This game will only go for the next 5 days
< sipa>
crickets live that long?
< fanquake>
I'll try find one and let you know
< sipa>
haha
< luke-jr>
XD
< * luke-jr>
remembers the time a Japanese bitcoiner visited him and we went shooting guns out back for the lulz
< bitcoin-git>
[bitcoin] ajtowns opened pull request #20942: [refactor] Move some net_processing globals into PeerManagerImpl (master...202101-netproc-anti-globalisation-pt1) https://github.com/bitcoin/bitcoin/pull/20942
< jonatack>
seeing my first 0.21.0 (ipv4) peer
< elichai2>
sipa: sweet :)
< elichai2>
(I'm writing a go implementation for muhash, but I'll try to use their big.Int from the standard library for the modular inversion, see how fast is that before i try safegcd or other algs)
< wumpus>
it's always the same, the problem isn't the CI failure but that the output is completely useless for fixing what the problem is, and to be honest i'm kind of tired of updating two sites in the first place
< wumpus>
anyhow, easiest would be to delete the changelog and make it a link to bitcoincore.org's, once that is merged of course
< sipa>
yeah
< MarcoFalke>
* 1651:88: ERROR: Tag datadir invalid
< wumpus>
MarcoFalke: thanks, yeah that could be it... the annoying thing is that the line numbers are from a generated html file (the only way to produce it locally is to install exactly the same set of ruby scripts and dependencies)
< wumpus>
also it only gives one error at a time and the CI runs for almost an hour
< wumpus>
(which is absurd for checking a website, but there you go)
< MarcoFalke>
yeah, travis :(
< wumpus>
bitcoin-core-dev@lists.linuxfoundation.org is now finally, officially, an announcement-only list
< sipa>
yay
< wumpus>
nkuttler: 0.21.0 release post is up
< nkuttler>
yay \o/
< achow101>
talisein: currently no. #19651 implements that
< luke-jr>
achow101: even just a one-time reminder after creation might help, but something to keep track of backup outdatedness and warn the user regularly would also be nice
< achow101>
luke-jr: outdatedness may be hard to determine
< luke-jr>
could just increment a counter per change, and reset to 0 on backup?
< jonatack>
luke-jr: that does seem a good idea, if workable
< jonatack>
(the concept)
< achow101>
I think a lot of people backup by copying the wallet.dat file rather than using the explicit backup wallet stuff
< achow101>
which in that case we wouldn't know when a backup was made
< luke-jr>
that can lead to corruption
< luke-jr>
bad idea regardless
< luke-jr>
they need the reminder too :P
< achow101>
an idea being bad hasn't stopped people from doing it :/
< achow101>
but reminders would be nice. I guess it would also help to push people to do it the right way
< luke-jr>
but at least this way they would investigate why they got a notice ;)
< luke-jr>
and fix their backups
< sipa>
the application explicitly telling you "You should make a backup, click here to do so!" likely encourages them to do it the right way
< luke-jr>
yes
< jonatack>
+1
< achow101>
luke-jr: can you open a brainstorming issue for this?
< achow101>
in terms of other stuff for 22.0, I'd like the coin selection changes to go in