< da2ce7>
kanzure, is it possible for to fix the headers of the emails so that regular email clients show the original author? - Or could it be policy that people can put their name/nym at the end of the email. I find it a frustration to work out the author of many of the mails now.
< kanzure>
has this changed recently?
< achow101>
da2ce7: the original author is usually in the reply-to field
< achow101>
both gmail and protonmail show me "from: X via bitcoin-dev"
< da2ce7>
achow101, kanzure, I worked it out, my computer had a contact card for the mailing list and then just showing than instead of the real-name. :)
< da2ce7>
thankyou anyway.
< kanzure>
now that we have solved the email protocol, let's move on to coinjoin
< provoostenator>
Ok, this is new... I'm getting a 500 server error for #13937
< as1nc>
hello folks, beautiful day here in south of france, bitcoin is doing great, what else can we ask ? :) oh yeah, anyone has any tips on how I could guess what type of a addresses is used (p2sh, p2pkh..) given an xpub, ypub or zpub key ? is that even possible ?
< as1nc>
given an xpubkey, i would like to know the good derivation path i should use for that key, without having the user to specify it upfront
< BlueMatt>
anyone else get a 500 trying to open #13937?
< michagogo>
Hrm, weird, looks like I disconnected a week ago and half my channels didn't rejoin
< echeveria>
michagogo: +r
< michagogo>
Hm?
< harding>
michagogo: since the recent spam attacks about a month ago, a lot of channels now require being a registered user (+r). If you were disconnected and don't use SASL auth, you probably weren't registered with nickserv when you reconnected.
< michagogo>
Was there a problem with services a week ago? Because I ID with SASL...
< michagogo>
Anyway
< echeveria>
nickserv has also been funky and was rebooted a few times.
< michagogo>
I may be able to get back to gitian again soon - working on migrating my VM over to my new laptop 🎉
< phantomcircuit>
michagogo, services were broken and one of the servers decided to stop doing anything at all
< phantomcircuit>
(my connection to it got pongs but that's it)
< michagogo>
Heh
< michagogo>
In other news: It seems on Windows 10 the OS itself runs in a VM, so Virtualbox doesn't work because Hyper-V is already using the CPU's virtualization capabilities as a bare-metal hypervisor
< michagogo>
So I migrated the VM over to Hyper-V, converting from legacy to UEFI Secure Boot along the way
< michagogo>
And it seems it worked!
< michagogo>
(Apparently boot-repair doesn't like it when apt on the target system is configured to use localhost as a proxy)
< polydin>
echeveria, ok thanks i guess i can just check that out
< echeveria>
polydin: just hanging around here, there's often small tasks commented on
< polydin>
echeveria, sorry could you rephrase that last sentence, not clear to me?
< sipa>
polydin: it's useful to just hang out in this irc channel
< echeveria>
polydin: many times in this channel, people will have suggestions about things that don't make it into issues. there's frequent opportunities to get your teeth into the code.
< sipa>
also, getting familiar with the project, the source code, and its workflows takes time
< sipa>
having a specific project is a good way to get going, but getting proficient takes time
< polydin>
sipa, i know, i've honestly spent so much time reading the code but it seems like i'm better off just contributing to get into hte workflow
< polydin>
i will start off with the low hanging fruit and build up to a project, thank you so much for your help!
< echeveria>
polydin: you're invited to message me privately, or ask me on #bitcoin any questions you have about getting started.
< echeveria>
or here, but this channel isn't great for in depth discussion.
< polydin>
echeveria, thanks so much!
< polydin>
is this channel more for just updates about specific PRs and such?
< sipa>
polydin: no, this channel is about development of bitcoin core
< polydin>
ok got it, again thanks guys
< echeveria>
it's just meant to be somewhat low volume so people can kept up with the logs (I've made a point of reading the logs, even if I haven't been here), but not restricted to PR discussion.
< sipa>
if you have questions about the code, specific PRs, workflow, ... feel free to ask here
< sipa>
but not general discussion on bitcoin or usage
< echeveria>
or how to pronounce sipa's name.
< polydin>
lulz ok
< michagogo>
Ooh, 0.17 builds on bionic?
< michagogo>
Cool
< * michagogo>
runs make-base-vm and heads towards bed
< achow101>
michagogo: no guarantee that that's gonna work
< achow101>
supposedly kvm stil doesn't work, even with the new vm-builder
< michagogo>
Hmm?
< michagogo>
That doesn’t sound promising
< michagogo>
Though I’m using local
< michagogo>
lxc
< michagogo>
Wait, does gitian lxc still use vmbuilder and convert, or did it get changed to make it better?
< achow101>
I think it uses vmbuilder
< michagogo>
Crap
< achow101>
I could be wrong
< achow101>
you should keep an eye on your build though
< michagogo>
I’ll see later (tomorrow or something) if it worked
< michagogo>
It’s almost 2 am here
< michagogo>
achow101: nope, looks like I remembered correctly