log☇︎
3800+ entries in 0.008s
mod6: thanks for your input. perhaps, the grass-roots thing is the way to go. ``talk to people''.
mod6: wb.
mod6: anyway, was a thought. I'd like to perhaps continue this line of thinking though ; figuring out ways to help drive some signups.
mod6: i kinda suspect the same thing.
mod6: Was anyone else at DC10, 11 or 12?
mod6: Maybe something we can look at next year.
mod6: Ah, ok, so they ~do~ have a vendors area at Defcon now. But the registration period for defcon 26 closed April 1st.
mod6: !!up pipp8
mod6: mornin
mod6: maybe it's different now. i'll see what I can find out.
mod6: mircea_popescu: well, after thinking about it a bit, I don't remember seen "booths" like I was thinking of there. was at least 15 years ago though.
mod6: bbl
mod6: anyway, was just a thought to getting the pizarro name out there a bit.
mod6: <+mircea_popescu> mod6 isn;t las vegas actually closer to you ? << naw, but doesn't matter. im sure that they wouldn't let us set up a booth anyway.
mod6: ben_vulpes: you wanna go to def^H^H^Hfedcon and set up a pizarro booth?
mod6: *whistling*
mod6: A Ft. Meade summer night, pantsuits passing by; listening to the taps of stingrayyyyyy.
mod6: I follow the republic log, down through all the sarc; listening to the lords exchaaange.
mod6: 'pleasure'
mod6: mas o menos
mod6: duh
mod6: It's clearly stated on the Washington monument: ``Im reich ist vergnugen verboten!''
mod6: ahh
mod6: waitin for the furnature?
mod6: mornin'
mod6: Ladies and Gentlemen of the Republic, if anyone has any updates or changes to the list of Advertised Republican Nodes, please let me know as soon as possible. Thanks in advance.
mod6: cool
mod6: ah, not too bad! need coffee, just catching up on the log.
mod6: mornin
mod6 does the head drop
mod6: cd
mod6: ah, interesting point re patch name
mod6: hmm. maybe not required in a technical sense. but i'd like it all to hang together, and be proper. for posterity.
mod6: maybe a necessary one, however.
mod6: because if so, then we need a new trb genesis. which doesn't effect v in anyway, just another pita for trb.
mod6: should it be a part of a proper genesis?
mod6: ah, then nothing i can think of. don't know what i was on about there.
mod6: it's just a flat file that resides in the project, ya?
mod6 thinks
mod6: Perhaps we need to 1: Formally adopt the manifest spec proposed by trinque, 2: build a V that supports it.
mod6: I read this all a while back when posted, liked it, will think on it some more -- but off hand, can't think of anything we might be missing.
mod6: we'll cross that bridge when we come to it. but first and foremost, the manifest items seems alright to me; "$blockCount $patchTitle $patchAuthor $comment".
mod6: then perhaps all the things that are still not folded in can be in a second release, or just folded in without release.
mod6: I can delcare the v054 release with a manifest of my own ala: To declare a "release", an author's GNS pointer for a project would point to his selected manifest.
mod6: opting to regrind the entire tree, and whatever other vpatches that need to be folded in that currently are not.
mod6: i see ben's point, but i'd rather trb one whole thing, instead of a 'before manifest' and 'after manifest'.
mod6: alright, gents, I'll have to dig into all of this sometime.
mod6: ben_vulpes: im trying to look at the big picture. the manifest spec is a part of that, ya.
mod6: is his lisp version of V to become the new defacto thing that has manifest capabilities?
mod6: anyway, I guess I'll have to put this on the conveyor and work through all of this.
mod6: Step two of the guide says "Ensure at least one of the following is installed:" "sbcl" or "ccl"
mod6: the "latest client" linked in the article: http://blog.esthlos.com/esthlos-v-genesis-or-who-presses-the-pressor/ ☟︎
mod6: so this is all in lisp. is it going to be simple for n00bs to get lisp installed and to run V?
mod6: everything documented and blessed.
mod6: that said, everything must be pretty much "firmly" in place with V rules, manifest, naming conventions, what have you, before I wanna move on that.
mod6: i'll regrind the whole trb tree. however, I think if we -must- do this, we should only do it one time. and i really don't even want to do it at all.
mod6: he's probably got some worthwhile changes
mod6: unf unf
mod6: good q's.
mod6: np, Sir!
mod6: well, there's also some syntactical problems, here's the fixes: http://p.bvulpes.com/pastes/TI85U/?raw=true
mod6: so that might need to be fixed.
mod6: which also leads me to see that in your code, you're attempting to use an iterator to loop over a map<string, string> , and add the keys to argKeys. but you never did set the iterator to mapArgs.begin()
mod6: for example: http://p.bvulpes.com/pastes/mFY19/?raw=true
mod6: you could do it with an iterator too, but that's not quite as clean.
mod6: prolly simplest way is like: http://p.bvulpes.com/pastes/i68ww/?raw=true
mod6: i'll take a look here in a sec.
mod6: oh, ok.
mod6: thanks for the script mircea_popescu! ☟︎
mod6: nice pics alf
mod6 reads scrollback
mod6: Rim-Jobs: Now, On-Demand and with Enthusiasm
mod6: hey cool, BingoBoingo !
mod6: ah, well, let's hope the docs get signed today then
mod6: and i see no reason not to include it in main vtree.
mod6: for sure. indeed, bug fix.
mod6: I might not get to it this week, probably sometime in early july, but I'm going to roll in your aggression vpatch to the foundation patch set as well.
mod6: Gonna be a busy week. Got a lot to accomplish with pizarro & foundation.
mod6: heheh, bout the same.
mod6: how goes today?
mod6: mornin'
mod6: haha
mod6: I'll call these guys and get them to throw in a ~new~ SSD for me this time. Or will just pay out, and find new service.
mod6: <+asciilifeform> mod6: by all indications you have a box with iron problem. in your place i'd get a fresh set of iron, rather than sinking sweat into interpreting randomly flipped bits as 'bug' << yeah for sure, it certainly could be related to the disk issue. I don't really think it's a 'bug' or anything.
mod6: <+asciilifeform> http://btcbase.org/log/2018-06-23#1829030 << hey mod6 is this the same box as in the last coupla similar threads, with the questionable hdd ? << yup, same item. will post more about it later for sure. ☝︎
mod6: *nod*, lesson learned.
mod6: but backing up the chain is a good idea. i actually have backups more recent than that, but from other trbs, not this specific one.
mod6: ah. perhaps ya.
mod6: anyway, will try it. (it's from january)
mod6: i have a backed up index, but its from long ago.
mod6: i'll probably just turn all of this into a blog post.
mod6: should take 10 days.
mod6: i think i'm just gonna cutblock all the blk*.dat files, and eatblock 'em.
mod6: yeah, ensure that if something like this happens to you, you do not kill it -- instead firewall it off. wait until all connections drop.
mod6: this ip from the nodes list: 208.94.240.42
mod6: will need to probably resync the whole thing.
mod6: anyway, now the db is corrupt.
mod6: thing was stuck, flooded with connections, not keeping up, wouldn't respond to any rpc calls. this going on for hours and hours. finally i just killed it. i probably instead should have just firewalled off 8333 instead. ☟︎☟︎
mod6: i broke my trb blockchain.
mod6: k