mod6: asciilifeform: <+mod6> so... i've integrated asciilifeform's fix into a new patch that will replace the old one: http://dpaste.com/2KCXN8A.txt << <+mod6> ahh, and then there is this now -- when compiling with alf's fix incorporated: <+mod6> http://dpaste.com/1AVK5ZP.txt << any thoughts on how to fix0r this?

mod6: <+mod6> <+ben_vulpes> "gpg: WARNING: not a detached signature; file `buildroot-2015.05.tar.gz' was NOT verified!"? << i've just run this again myselfand logged output here: http://dpaste.com/0P2QXYG.txt I'm not sure how what you saw happened there. :/ << im wondering if this could be related to a GPG version thing or something? because the line of code that is executed here is this:

mod6: <+mircea_popescu> wait shouldn't shiva 2 be restated instead ? << this is probably a better. and its not even in the mirror at this point anyway.

mod6: <+mircea_popescu> so in this sense mod6 it has my imprimatur that bothering to grok it isn't a waste of your finite time. << yeah, agreed, Sir.

mod6: <+mircea_popescu> http://log.bitcoin-assets.com/?date=30-01-2016#1390077 << this is a bad idea inasmuch as it leaves my build process stranded, so i'll be stuck forever using current v and i suppose forever pressing 9996 then ? << yeah, i read your comments earlier on this. part of "battle-ready" to me means not only that it has lordship blessing, but it doesn't break any security paradigms that we m ☝︎

mod6: <+mircea_popescu> http://log.bitcoin-assets.com/?date=29-01-2016#1389489 << ok that's great. << this ~is~ a nice looking graph ☝︎

mod6: <+mircea_popescu> ftr mod6 : i ended up with two rotor.sh scripts, one under rotor the other under rotor/test2 << yeah, if all goes well, you should ~only~ need to just execute the build script -- if you have to execute either of the rotor.sh scripts, then something went wrong. ☟︎

mod6: <+mircea_popescu> You must install 'bc' on your build machine << ah, ok.

mod6: <+mircea_popescu> ah nm, it was the x86 flag << yeah.

mod6: <+mircea_popescu> try just korsgaard << i guess you could try this

mod6: <+mircea_popescu> hey mod6 how would you rate working with b-a vs working with job people ? are we just as enervating ye t? << this beats anything else I've ever encountered by a wide margin.

mod6: <+mircea_popescu> mod6 alrighty, seems it's teh consensus here. << ok lemme put this together, and will post in here for you guys to review, and people to test.

mod6: <+mircea_popescu> why can't it be populated by hand ? << how can you populate by hand while the script is running?

mod6: <+mircea_popescu> that'll be some pretty epic action movie. << haha, yah. oh well.

mod6: <+mircea_popescu> asciilifeform well, if there's no consensus, there's no consensus and there it goes. <+mircea_popescu> poor mod6 gets no week off! << ok so no consensus on the space/tabs issue at this time.

mod6: <+mircea_popescu> yeah cuz crazy argentines, they're like excited sheep in the airport. << haha, it was a big crowd. You picked me out pretty quick.

mod6: <+mircea_popescu> mod6 here's the problem with "Bitcoinos" : you will want it adapted for bitcoin needs, which necessarily means it won't be your tool of choice for doing almost anything else, which necessarily means maintaining it will be a pain in the ass. << agree. I think that what I'm getting at is maybe it ends up being like cisco ios.

mod6: <+mircea_popescu> mod6 so basically we can't use our convenient makefiles to build the pressed source ; openbsd people gotta finagle their own build chain to get the same source to compile and link ? << and further more, they'll never have the same build process like we want.

mod6: <+mircea_popescu> http://log.bitcoin-assets.com/?date=24-01-2016#1383446 << wait, explain this to me ? << the idea is that our makefiles, or whatever build scripts will utilize V to build inside of the rotor (a linux thing) - the source must be compatable with that. phf's openbsd scripts are not compatible with this. ☝︎☟︎

mod6: <+mircea_popescu> like it or not this is the level of scrutiny that patches have to face, even if it makes develoipment slow. << i very much agree with this methodology.

mod6: <+mircea_popescu> my one question, and not to mod6 in particular, is : can unsigned int nSize = ECDSA_size(pkey); be trusted to not fuck up the size ? << Just to touch back on this again - I'd like to see more of this. If you happen to be reading through the code, and there is a question, ask - let's discuss.

mod6: <+mircea_popescu> my one question, and not to mod6 in particular, is : can unsigned int nSize = ECDSA_size(pkey); be trusted to not fuck up the size ? << Not very "warm and fuzzy" on the openssl trust factor either. Would some tests or debugging help around this part?

mod6: <+mircea_popescu> or what, we discover dpaste auto-fucks-up the tabs anyway << im starting to wonder...

mod6: (13:52) <+mircea_popescu> asciilifeform http://dpaste.com/26VKRQG << second one

mod6: (13:43) <+mircea_popescu> mod6 http://dpaste.com/2CH23F5 << in the humble hope that it may serve. << first one

mod6: <+mod6> huh, dunno, guess i could try that. << failed to patch

mod6: <+mircea_popescu> mod6 really you shouldn't do this manually, just s/ /\t/ << lemme try with this. thx.

mod6: <+mircea_popescu> if only we had larger blocks. << srsly right?

mod6: <+mircea_popescu> Dec 22 17:01:42 <mircea_popescu>Iin other news, "blocks" : 182731, << same system is now "blocks" : 347914. << almost there!

mod6: <+mircea_popescu> hey, is this a documented openssl hole ? seems it could be useful. << found this, seems like the opposite tho: http://marc.info/?l=openssl-dev&m=122520520421616

mod6: <+mircea_popescu> anyone seen this wonder http://dpaste.com/1JNBGCX ? << scary huh

mod6: <+mircea_popescu> well, i do think to some degree your patch should be restated, but not in the sense of replacing it altogether << yeah, ok. i'll do some work here today / tonight, do a re-test and the hopefully get it to the ML before the week is out.

mod6: <+mircea_popescu> well, honestly, this wasn't intended as a release candidate, more like a commentary item << ok good deal. was kinda wondering if the forthcoming release patch should bundle this one in or not.

mod6: <+mircea_popescu> not a great fan of vchSig and bs myself, eother. << yeah, im not sure why the var name needs to delcare that it is a vector of chars.

mod6: <+mircea_popescu> specifically, imagine a future in which every line of code has 100 lines of commentary, much like the talmud (which is a VERY proper comparison) << I never thought of it this way.

mod6: <+mircea_popescu> asciilifeform http://dpaste.com/26VKRQG << re: There is no reason to test for both highS and lowS being set, because this is tested in init.cpp already, ... << For some reason I had it in my head that since this gets set in util.h/.cpp that both may become set at some point post execution if someone does something funny.

mod6: <+mircea_popescu> no fucking hunter in the history of hunting wore anything but green and olive drab << i wear blaze

mod6: <+mircea_popescu> what sanity checks are you ignoring you say ? << it was basically this, i was looking at in regards to bip66: https://github.com/bitcoin/bitcoin/pull/5713/files

mod6: <+mircea_popescu> hm ? <+mircea_popescu> deedbot- http://dpaste.com/0AEEMJB.txt <+mod6> January the 18th 2014

mod6: <+mircea_popescu> mod6 you wanna write the [implementation] part and i bitch at you ? seems a better approach than the reverse. << haha, ok. i probably wont get a start on this until later tonight tho. hope that's alright.

mod6: <+mod6> asciilifeform: hey, for a long time now I've been searching for the fix you provided to vdiff for debian/ubuntu; for some reason it barfs saying that there is an unmatched quote or something. ☟︎

mod6: <+mircea_popescu> http://log.bitcoin-assets.com/?date=16-01-2016#1373499 >> yes it should. << yup. the topological flow might be ever so slightly different when listed, but the resulting pressed tree must be exactly the same. ☝︎

mod6: <+mircea_popescu> jurov did the foundation ever spend anything, i forget. <+ben_vulpes> foundation spend << not to date << technically we have made one expenditure, paying jurov his yearly fee.

mod6: <+mircea_popescu> http://log.bitcoin-assets.com/?date=16-01-2016#1371963 << looks good to me ? << hey, thanks for taking a look! ☝︎

mod6: <+mod6> PeterL: Hey, glad you got it resolved! << should have put this in a later tell, sorry.

mod6: <+mircea_popescu> in general people should be able to make their own decision based on keys, rather than pile up on you to review neh ? << i don't see a problem with doing it this way.

mod6: <+mircea_popescu> how about you drink benzene and talk to the stove. << haha

mod6: <+mircea_popescu> "a tensor" << haha, i missed this

mod6: it just seems like stuff like this works well: <+mircea_popescu> For any smooth, simple closed positively oriented curve in a plane, if two functions are defined on any open region containing the area bounded by that curve, should those functions have continuous derivatives in the region then the integral over their sum is the integral over the region's integration of their differential.

mod6: <+mircea_popescu> pdf must die already omfg. << yes.

mod6: <+mircea_popescu> mod6 what'd be your definition/specificiation for the concept of sigil ? << by definition, for me its a cryptographic signature (embossment) of a given input.

mod6: <+mircea_popescu> heh, i suppose that's the strongest indictment for the soviets ever : can't fucking distinguish 50s from 80s looking at the pictures. << yeah, whenever i see these older pics, I can't tell if its 30 years ago or 60

mod6: <+mircea_popescu> mod6 but this manifest... wouldn't you say it's of the nature of the sigils ? << im not sure i understand this.

mod6: <+mircea_popescu> the manifest should live wherever the rotor.sh lives neh ? << I would argue that all of these scripts would live outside of bitcoin source V tree.

mod6: <+mircea_popescu> my personal ideal would be that ALL directories involved in this without exception are spawned as subdirs of whatever current dir the script ran in. << this makes sense. right now you end up with /.../rotor/ and ~/.wot, and ~/.seals iirc.

mod6: <+mircea_popescu> seriously mod6, VERY nice job with this. 19 yo can use it! << this

mod6: <+mircea_popescu> wut sarc << oh thought you had sarc tag on about the seals warning your 19yo got. :]

mod6: <+mircea_popescu> listen we really gotta pick one of these and stick to it. << will sort this out with the manifest/file-o-hashes

mod6: <+mircea_popescu> as it is i put .wot in /trb/.wot but the .seals are still up one level ;/ << noted.

mod6: <+mircea_popescu> mod6 as a purely aesthetic point, i hate that your v puts its files/dirs straight under ~. it would be much better if it made them under current dir. << alright

mod6: <+mircea_popescu> seriously mod6, VERY nice job with this. 19 yo can use it! << sarc?

mod6: <+mircea_popescu> if you check "at the end" now you have state. << do we want this?

mod6: <+mircea_popescu> i suppose should prolly call it fleet in being for historical reasons, but anywya. << gotcha

mod6: <+mircea_popescu> anyone in the foundation leadership familiar with the military strategy concept ? ben_vulpes mod6 ? << not in a very formal sense.

mod6: <+mircea_popescu> mod6 perhaps an announcement that the bitcoin foundation maintains and will continue to maintain a real bitcoin client, notwithstanding continued attacks from well known usg agents on the core values of sound money ? << sounds good, will write something up by EOD.