12800+ entries in 0.014s
mod6: jurov: will there be a monthly Treasury report coming through for The Bitcoin Foundation?
mod6: ben_vulpes: Sir, please weigh in here when you get a spare moment. ^
mod6: again, don't wanna speak for the man; however, don't think he has any at this point.
mod6: well, i don't wanna speak for ben_vulpes, but iirc he's read most of them if not all; maybe just didn't get around to signing for lack of time because of baby, and running company.
mod6: <+asciilifeform> not a vpatch, at ant rate. << fair distinction
mod6: yeah, ben has never signed anything.
mod6: alright. now we'll begin a testing cycle. when we're done with that, will sign and publish vpatch.
mod6: im also going to use this vpatch to tag the release and tie up the leafs.
mod6: my new vpatch, as we discussed lastnight works perfectly.
mod6: nevermind, im smoking crack
mod6: wow, that seems high.
mod6: mircea_popescu: to her credit indeed. poor lady.
mod6: i don't know for sure. maybe "hand full of blackcats" or something. small firecrackers.
mod6: it looked as if someone lit off a M80 in her hand.
mod6: mircea_popescu: your lady's hand looked ghastly. she should get to slap the first born of all of the industrial leaders in .ar.
mod6: when you think it's a good idea, we can add a project to tb0t if it seems prudent.
mod6: its a good dialogue though.
mod6: yah, totally a different ball of wax.
mod6: i apparently need to read your blog more, at least, on the specifics of lisp-cpu via verilog & fpga
mod6: the whole picture tho; need the whole picture
mod6: i'll have to reread all of this stuff; i have difficulty with a mental model of this. but i do follow the detail points.
mod6: asciilifeform: ah, ok.
mod6: i better reread all of this stuff :/
mod6: right. i think this whole topic is totally over my head these days.
mod6: and i suppose this makes it easier to swap out the station key and retain the royal key.
mod6: phf: ah, indeed then, we should rework it with what we've since discussed and rethought since 2015 or whenever, and see if a prototyping process can begin.
mod6: thanks mircea_popescu
mod6: more than anything, i just want to be able to contribue a bit better to these gossipd discussions - which will be a vital part of the infrastructure.
mod6: very much appreciated, and my apologies if the original is still on point.
mod6: i'd have to dig it up, but i thought there was a trilema that outlined the 'spec' back a while ago.
mod6: haha. indeed, hopefully will rid myself of these labors someday soon.
mod6: but, maybe the first step, to recognize Framedragger, is to update the spec. there has been much discussion about this, and maybe I'm having a hard time keeping all of the details in my head.
mod6: i don't want to disagree with what I just said here: <+mod6> a lot of new questions and discussions will arise once someone starts to prototype gossipd out.
mod6: <+asciilifeform> mod6: the correct pill is to decouple (at least from enemy's pov) gossip station keys from royal keys. << so to clairify this a bit, at least for myself, the gossipd node that I run and operate would verify transmissions sent to it with mod6-battlestation-key, but when I would actually go to send something out it would sign with mod6 "royal" or "personal" key?
☟︎ mod6: i need more coffee.
mod6: well, indeed, if it continues to be useful and oft used.
mod6: a lot of new questions and discussions will arise once someone starts to prototype gossipd out.
mod6: yeah, forgot about that. anyway, i appreciate interesting ideas.
mod6: oh wait, forgot about the wonky-fan
mod6: someday, when we have a tmsr cryptolib & rsa-o-matic, maybe we can starting building a gossipd prototype.
☟︎ mod6: V has a future. interesting to think about where it may go from here.
mod6: and mine can be used, 100% in the same way. im not even sure that i fully agree that mine should do what it does. you and I both, seperately have wrestled with this thought.
mod6: <+asciilifeform>
http://btcbase.org/log/2016-09-09#1538037 << lel what has mircea_popescu been drinking...? << It is an intersting thought; a distributed V, which rails against the complaints of "omfg another centralized piece of equipment!!11"
☝︎ mod6: <+mircea_popescu>
http://log.mkj.lt/trilema/20160909/#23 << yes mod6 but to clarify : "one button" refers to the situation where the user already has a trusted copy of V, and a .sig directory populated as per his taste. these are part of the definition of identity, and going forward can and should be assumed present. << Sounds fair. Thanks for outlining this.
mod6: interesting convo this am re: gossipd & v
mod6: Will have some more to report on in a few days. Salud!
mod6: Good news from lastnight: Was able to do some polishing and wrench turning to get the makefiles to utilize the pressed source in src/
mod6: ah, ok then. have a good night.
mod6: thanks Gentlemen. I'll keep polishing here. more to come, I'm sure.
mod6: for most people, not so.
mod6: for you and I, this is routine.
mod6: the setup of v; verify v; place everything where it needs to go, etc.
mod6: not a problem then.
mod6: ok. that's a minor consideration.
mod6: that's the easy part imho. the hard part is getting v, et. al., set up.
mod6: <+mircea_popescu> " then navigate to pressed dir, " << i mean. << ah, ok yeah one ~might~ be able to do that. not an expert on make tho.
mod6: which, seems to be the "pistols" way
mod6: well, one would still need to press everything out, which includes the source and makefiles in this case.
mod6: does this seem acceptable?
mod6: i'll see where i can get to with this new idea. however, a person would have to do this to build the entire thing: get v; verify v; put vpatches, seals, and keys in place; press; then navigate to pressed dir, then `make`.
☟︎ mod6: i could go on here.. but let's just say i didn't think it all the way through.
mod6: yeah, after discussing with myself in here mainly, i'm not in love with that solution either.
mod6: (working on that / testing it now)
mod6: anyway, i might be able to get it so that you press the tree, including the makefiles, and then just build.
mod6: well it's earliest implementation, was a clone of our build scripts, which, used V to pull and press the source.
mod6: <+mircea_popescu>
http://log.mkj.lt/trilema/20160908/#1160 << so basically we got v running twice ? << yeah, which wont do. after my monologue earlier, I have a hunch that I might be able to get it down to a single press.
mod6: asciilifeform: verified, thanks!
mod6: i've got: 72.83.9.184 listed on the foundation site. is it back up now with different ip alf?
mod6: Then let the makefiles do all the rest of the heavy lifting.
mod6: The simplest solution would be to perhaps have a deedified tarball of makefiles, much like trinque already has, get the deed, verifiy it, decode it, extract it, navigate to the make script and `make`.
mod6: This hypothetical solution, even if it does work, wouldn't make it a one-button-push solution. Why? A person would need to get V + V.sig, verify, create a .wot dir, sync the patches + seals, manually or automatically, press the tree, then navigate into the pressed tree, and then `make`.
mod6: Will try to work that out.
mod6: Well, if it could be done without having to move anything that is already in place (as far as bitcoin is concerned), then it might work out alright.
mod6: It would probably need some tweaks in there ... hmm.
mod6: Actually, I forgot, trinque already did that part. Makefile.rotor exists.