< luke-jr> dongcarl: I started from nothing when I installed Gentoo on my new PC
< roconnor> luke-jr: like editting your boot sector with your BIOS?
< roconnor> I mean, presumably you started with some sort of bootable ISO image?
< luke-jr> roconnor: what BIOS?
< luke-jr> I cross-compiled a bootable USB stick from my old PC
< roconnor> okay. That's fair.
< roconnor> I'd rephrase that as I started from an older PC when I installed Gentoo ...
< luke-jr> roconnor: that's kind of already implied by inspecting any bootstrap with a hex editor even, not to mention the kernel hosting it etc
< roconnor> Oh course.
< roconnor> The difference is that stage0 is reproducable, but no one can get reproduce what you did.
< luke-jr> well, they could…
< roconnor> but they won't get the same .iso
< luke-jr> point is everyone should bootstrap for themselves
< luke-jr> or at the very least, not be cut off from doing so
< roconnor> Indeed I agree. There is nothing fundamental about Guix's binary starting blob. I'm moderately confident we could rebuild it on Gentoo or whatever.
< roconnor> I guess I should put in some effort at some point in time.
< roconnor> The build process should be described by their archine DSL. Ironcially if it were written in Nix, I would probably be able to read it.
< bitcoin-git> [bitcoin] fanquake opened pull request #21036: gitian: Bump descriptors to Focal for 22.0 (master...gitian_bump_22_0) https://github.com/bitcoin/bitcoin/pull/21036
< bitcoin-git> [bitcoin] practicalswift opened pull request #21037: fuzz: Avoid designated initialization (C++20) in fuzz tests (master...c++20-false-start) https://github.com/bitcoin/bitcoin/pull/21037
< michaelfolkson> For those interested in fuzzing research, this Telegram group seems to share some great content. It is run by a commercial group (Fuzzing Labs) so the occasional promotion etc but generally high quality https://t.me/fuzzinglabs
< bitcoin-git> [bitcoin] FndNur1Labs opened pull request #21038: Merge pull request #1 from bitcoin/master (master...master) https://github.com/bitcoin/bitcoin/pull/21038
< bitcoin-git> [bitcoin] MarcoFalke closed pull request #21038: Merge pull request #1 from bitcoin/master (master...master) https://github.com/bitcoin/bitcoin/pull/21038
< bitcoin-git> [gui] jonatack opened pull request #203: gui: display plain "Inbound" in peer details, add #162/#163 release notes (master...display-plain-inbound-and-add-release-notes) https://github.com/bitcoin-core/gui/pull/203
< bitcoin-git> [gui] jonatack closed pull request #201: gui: ensure inbound block relay peers have relevant services (master...inbound-block-relay) https://github.com/bitcoin-core/gui/pull/201
< jonatack> psa: github cli became a bit more usable with v1.5.0, adds ability to comment on issues and PRs, and displays top level review comments inline with regular comments (without any "158 hidden comments")
< bitcoin-git> [gui] jonatack reopened pull request #201: gui: ensure inbound block relay peers have relevant services (master...inbound-block-relay) https://github.com/bitcoin-core/gui/pull/201
< dr_orlovsky> Sorry if I missed something but do we already have taproot descriptor?
< sipa> no
< sipa> probably time to start looking into that
< dr_orlovsky> and the address format will be called `P2TR` or there is no definite decision yet?
< sipa> i've been calling it P2TR
< sipa> you can call it what you want, there is nothing official :)
< dr_orlovsky> I assume before there is BIP-350 there is no address format implementation yet (since we need bech32m first). Right?
< sipa> well bitcoin core (and several other software) accepts bech32 v1+ addresses for sending
< sipa> but hooefully nobody will start ceeating bech32 (instead of bech32m) receive addresses for taproot
< luke-jr> our 'uk' translations appear to be reverted to English in 0.21 fwiw :/
< sipa> someone thought it meant the united kingdom instead of ukrainian?
< luke-jr> (would prefer someone who knows something about the 'uk' language to confirm :P)
< luke-jr> maybe
< luke-jr> since we did just recently delete en_UK
< dr_orlovsky> luke-jr: I am Ukrainian :) Where to look?
< * hebasto> luke-jr: indeed, done in 93ce429f0e6ab6e09051fd947c898ecbbf907cd8
< luke-jr> I think you have to login/make acccount to actually go into the strings
< dr_orlovsky> luke-jr: Ok, I'm in. This is clearly not Ukranian but English. Ukrainian uses cyrilic alphabet and Russian is similar to it, so it is easy to see
< luke-jr> that's what I thought
< luke-jr> I wonder if I should just grab an older release and push it over the current one
< dr_orlovsky> 0.20.x and 0.19.x also had english strings
< dr_orlovsky> and I do not see other versions being translated, so literally nowhere to pull from
< luke-jr> I do have at least some real uk strings in Knots somehow XD
< luke-jr> dr_orlovsky: if it's not too much to ask, maybe it's best to just retranslate it? ;)
< luke-jr> or copy paste from there where applicable
< dr_orlovsky> The file in bitcoin repo is a correct translation. What is the master source: transifex or the repo?
< luke-jr> transifex
< luke-jr> dr_orlovsky: probably best if you deal with this, since you actually know what you're looking at ☺
< dr_orlovsky> so the task is to copy strings from bitcoin repo into transifex?
< luke-jr> dr_orlovsky: if appropriate; if they're crappy translations, feel free to make a new one
< dr_orlovsky> ok, git it. Will gradually work: a plenty of strings there...
< dr_orlovsky> *git -> got :)
< luke-jr> I'm sure there's missing translations too
< luke-jr> 'zu' affected too possibly