log☇︎
18100+ entries in 0.033s
mod6: shinohai: good to hear, thx for the update.
mod6: so here's a thing -- if I make a vpatch for this, one doesn't need to build with it either. but one could, and that should resolve the issue.
mod6: *it'd
mod6: but, i'd be nice to ship a bitcoinatron that actually bitcoinates without the weird shit. i'd like Mr. P. to be able to send coins without issues.
mod6: yeup, ofc.
mod6: ok, other than that?
mod6: is there a reason for only high-S ?
mod6: was thinking that. could just have a switch for "classic" mode where you get the 50/50 action on high/low, or only low-S.
mod6: so currently, the main thing im working on/looking at is a possible high/low-S vpatch
mod6: I just need to get to it. lol. lot on my plate. if anyone would like to start work on this with direction from me that'd be fine too. just let me know.
mod6: <+asciilifeform> http://log.bitcoin-assets.com/?date=14-01-2016#1369573 << is somebody gonna write a full 'v' treatise ? << i think what we need is basically like an RFC of the thing to explain the overall concepts and baseline functions. this way anyone can implement their own V without having to parse mine, yours, or bens, or whomever. ☝︎
mod6: but you don't hvae to know the subdir to make the sync work properly. you just put the root URL of the given mirror
mod6: well, it's really http://thebitcoin.foundation/v/
mod6: your latest two patches & corresponding seals were added.
mod6: <+asciilifeform> http://log.bitcoin-assets.com/?date=14-01-2016#1369542 << there was a v mirror ?!! wut? << the only mirror at this time is http://thebitcoin.foundation ☝︎
mod6: <+BingoBoingo> ty mod6 << np. good questions.
mod6: shinohai: see if you can get the same as me ^^ (see dpaste)
mod6: BingoBoingo: http://dpaste.com/1MP1W10.txt & for future ref.
mod6: im about to do this, just a sec.
mod6: then it should press all that come before it.
mod6: <+BingoBoingo> So if there are three heads I want I'd press 3 times << no should just be able to choose the last one in the flow output
mod6: just one press at a time. choose a new output dir to ensure clean press.
mod6: *press up
mod6: <+BingoBoingo> So do you press head, press other head, etc or something else << no, you can just up through a given vpatch in the flow.
mod6: you should be able to sync the whole thing now and get those ones as well.
mod6: ok those two latest patches and their corresponding seals from asciilifeform are in the mirror.
mod6: it does a single head.
mod6: were the new patches included in your 'flow' output?
mod6: i can throw those in there. just a moment
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: after this, you should be able to press out a new trb that includes the latest patches, then build from there.
mod6: you should be able to drop those patches into your patches directory for V, and then also put the seals in your seals dir -- once that's complete doing `./v.pl f` should show you a flow with those patches in there with 'asciilifeform' as the signatory.
mod6: <+BingoBoingo> The coolest latest stuff seems to have not sync'd << because the two latest ones haven't been read or tested by me yet.
mod6: <+pete_dushenski> mod6: you around ? << yup
mod6: indeed
mod6: asciilifeform takes off hat << oh no!
mod6: ;;later tell pete_dushenski hey, got your msg. hit me up when you're around.
mod6: hah
mod6: <+mircea_popescu> how about you drink benzene and talk to the stove. << haha
mod6: I guess this does actually effect us a bit -- i mean, lets say we wanna do some math modeling or expound upon some properties of something fourier whatever, and send it to the ML... now you gotta have it in ascii otherwise you can't sign it.
mod6: <+mircea_popescu> "a tensor" << haha, i missed this
mod6: something like that? im not really only saying verbal. im just saying, hey, lets practice safe ascii.
mod6: i dunno? sig = [T(e1)T(e2)T(e3)]
mod6: and then when it doesn't there's alway some short hand one could do without resorting to unicode or PS.
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: haha.
mod6: i like the idea that we could have a regular char set, like 127 bit ascii, and do everything from this. and if you need Sigma, its SIG, or LAMBDA, its LMA or Absolute Value, ABS.
mod6: would trade again
mod6: ikr, solid guy
mod6: ftr: im still laughing about kako's buddy who needed the condoms in thailand
mod6: hawtbutts.txt
mod6: i like ascii txt
mod6: !up ascii_butugychag
mod6: <+mircea_popescu> pdf must die already omfg. << yes.
mod6: ah, to me that's what i took 'sigil' to mean, 'a seal'. I may misunderstand the language.
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: http://log.bitcoin-assets.com/?date=11-01-2016#1366390 << I do have a usage guide and quick-start guide... but maybe more of whats needed is not a reference manual, but an overall concept paper. ☝︎
mod6: http://log.bitcoin-assets.com/?date=11-01-2016#1366283 << this is an interesting idea. ☝︎
mod6: asciilifeform: naw, i dont
mod6: was 83e2b80e96919cb0b0186ff8ba7225d25535ad722ec5e2343a3a5927ef85d735 sent by trb?
mod6: trinque - quite nice, Sir.
mod6: trinque: I pulled, verified and tested 'trb-mk.tar.gz' on my gentoo x86-64 machine. It built a static bitcoind for me! I fired it up, connects, pulls blocks. =]
mod6: nice
mod6: go, btc go!
mod6: np, glad to hear it :]
mod6: s/seemed to u tx/seemed to use tx/
mod6: punkman: yeah, without digging into the code yet, it certainly appears that way.
mod6: all of this 94 blocks after tx 9de6a04788
mod6: what's strange, at least to me, is why tx d8e60a097 seemed to u tx ebc5d7688 as its prev_hash instead of tx 09e82c06, which was accepted and added to block 391,657.
mod6: been trying to follow up with a whole bunch of things from here actually. including this tx thing from yesterday. i've been going through the raw txs and drawing diagrams myself.
mod6: no, i've never seen anything like that. have stopped R.I. (sometimes for weeks at a time) then restarted without issue, lots of times. just been following along in here. just was curious.
mod6: jurov: did you ever figure out anything with that segfault -- weather data corrupted or isolated to local changes to bitcoind for mempool investigation?
mod6: "his beard drops too many panties, move to defcon 4!"
mod6: i guess that's the "or else" part 'eh
mod6: <+punkman> hey, bitcoin is 7 year's old today << Happy Birthday! http://dpaste.com/08BNVKT.txt
mod6: hny davout
mod6: haha 'psychic height readers'
mod6: doesn't matter
mod6: its just a number, how can a name be relevant?
mod6: !up ascii_rear
mod6: gentoo clone
mod6: <+kakobrekla> buttnix << lel
mod6: feminism: our specialty
mod6: real subs like the cage!
mod6: or else what?
mod6: "get the fuck outta my mailbox or else!"
mod6: it's gonna be going away.
mod6: anyway, yeah, this is the build script that I created for testing the build of 'rotor', TEST2, and the static binary.
mod6: f
mod6: !up assbot
mod6: its just the guys key.
mod6: anyway, this is all changing anyway.
mod6: so that is checked independently of V. what V does is a whole separate ball of wax.
mod6: *buildroot
mod6: buiroot is not v-ifiable. so in the rotor+TEST2 build script it was decided (in here) that we should check the hashes and the signatures.
mod6: there is confusion here.
mod6: <+thestringpuller> will the signed files/patches need to be resigned everytime keys expire? << no. you'll notice that his fp is the same.
mod6: phf the deal here is that the build script tries to verify the pgp sig of buildroot -- which is a process outside of v, so a key needs to be imported directly into the gpg keyring.
mod6: just do this `gpg --recv-keys 0xAB07D806D2CE741FB886EE50B025BA8B59C36319`
mod6: once you've done that, you may wanna clean up and start the build over again.