110100+ entries in 0.716s

mod6: trinque: hmm. yah,
i had to like use that tool, do a rescan and a restart, and then it was in there. but yea, that back port, if sane, would be best.
trinque: mod6:
I did a rescan but don't see my key as part of the default "account".
I'll fiddle with the wallet.dat a bit more, then take a look at backporting that importprivkey
mircea_popescu:
i bought things so small you could carry them inside your nostril.
mircea_popescu: it's inconceivable without seeing it. like 20 sq feet affair that was maybe five foot tall, you had to go in two fucking steps. and then the actual shop, down a steep flight of stairs, another 30 sqft or so
i guess.
mircea_popescu: so
i've just been shopping in the tiniest shop
i have ever seen.
ascii_butugychag:
i don't think
i will ~ever~ recommend tinyscheme on a box which carries live-fire coin.
phf: if
i have a gpgme key instance, is there some way to patch its trust level?
trinque: ben_vulpes: first
I'm getting deed txns going by using the trb wallet;
I don't want to have to wait for an implementation of eatrawtx to resume deeds
assbot:
I was fired after a stranger sent photos of my private text messages to my employer — Ask a Manager ... (
http://bit.ly/1nNPSLr )
felipelalli: BingoBoingo, not all of them are my "friends". Actually
I want to identify the bad actors in the community.
I could implement an automatic -1 from me for who install the exe version!! lol
trinque: eh
I knew that ball of duct tape and twine wasn't going to last
felipelalli:
I am going to my swimming lesson now. Thanks for the obvious comments that
I was expecting.
I tried to hide from you, but you got me! outch!
danielpbarron: thestringpuller,
i got into it with a fairly popular girly about "nice guys" and sexual dominance or something; turns out
i think we were agreeing with eachother without realizing it
☟︎ felipelalli: and
I am ashamed to trying to help the lazy people! But it is being fun.
felipelalli: danielpbarron, good question. Because if
I don't,
I feel too lonely? :D
felipelalli: the exe
I generated with a tool inside a VM
ascii_butugychag: no. but
i was curious what felipelalli was thinking when he produced this.
felipelalli: ascii_butugychag,
I didn't ask you to use it, didn't
I?
felipelalli: ascii_butugychag, yes. my first idea was make this 100% web, but the IRC let me crazy. So
I had just two dawns to implement it,
I choose the cheapest for my good will and the win version is because they demanded it
felipelalli: jurov, they are learning the importance of the thing, at least,
I hope. They are learning the importance to make solid contracts and verify the people reputation.
danielpbarron: let me see if
i can make one of those funny metaphores out of this: "that's like a cock that can get you pregnant, but you can't have sex with it"
☟︎ felipelalli: jurov,
I understand. But it is being very useful so far in Brazilian community. Actually the app can sign messages (not verify it yet)
jurov: felipelalli:
i can see, but...user that doesn't know how to make a signature or talk to gribble don't have anything to do in otc
mod6: kewl.
i seem to recall having to do a -rescan afterward but
i could be wrong
trinque:
I've got my key imported (via pywallet into wallet.dat)
trinque: jurov: nah, deedbot is still jammed until
I get trb to send the next bundle
mod6:
i read trb logs every day. who doesn't?
phf:
i was trying to see if could look up the corresponding vpatch by decoding the sig's hash, and then assoc into a precomputed map of vpatch hashes. unfortunately openpgp concats the sig header to the payload, so can't precompute :/
PeterL: ascii_butugychag> as that would require the hash of (-b) and (c') to be equal << is it looking at the hash of the pressed value, which should be the same, or the hash of the patches themselves, which
I understand are quite different?
punkman: ascii_butugychag: right,
I guess good time to remind people
ascii_butugychag: and
i officially consider regrinds a thing to be avoided if at all physically possible
☟︎ mod6: then if all is good,
i'll roll up another publication of the whole thing & call it v99995
PeterL: if you have patches a->b->c and you decide to get rid of b, you should end up with a->b->c->(-b), not with a->c' (where c' is reground c without b patch) , do
I understand correct?
☟︎ mod6:
I'll probably just send the patch to the ML to recruit people to help me test over the next two weeks.
ascii_butugychag:
i mean hey, it's ~my~ history of bug-crapping that is being whitewashed over, so
i shouldn't complain... but still
mod6:
i dunno either now, that was a giant pain in the ass.
ascii_butugychag: what
i am expecting to see in a correct press is for the trees to be IDENTICAL
mod6:
i guess that makes sense you wanted to see it that way -
i thought the first way just because that way there ~is~ a diff to look at. but maybe this is better.
polarbeard:
I completely see unique names are a must, but if you don't replace you'll keep mistakes in the tree?
jurov:
i agree, let's have unique names
jurov:
i am sooooo in favot of adding another hurdle to turdatron!!!
polarbeard:
I mean a timestamp in the filename author_patch_thing_$(date +%s).vpatch
ascii_butugychag: and
i have no intention of asking people to use a patched pgptron simply so they can use v
polarbeard: for the rate that patches get built
I think it will be fine
jurov: punkman
i said that, there were screams it's not vtronic
ascii_butugychag: the trees, as
i understand, ought to be ~the same~ after each scenario
jurov: sha1 because
i wanted to track files by contents and sha1 was at hand
ascii_butugychag:
i wanted to see a diff of my tree (pvs, and my pvs fix, and shiva, and the shiva fix) vs yours (where the patches and their bugfixes were agglomerated)
mod6: <+ascii_butugychag> the two trees, diffed. <<
i believe this is what
I have and what you're looking for, is it not?
polarbeard: jurov: sha would be large and annoying, date +%s would be enough
I think
mod6:
i did vdiff of the pressed out stuff.
ascii_butugychag:
i wanted a diff of a) the result of applying my original patches b) the result of applying yours
mod6: please explain again so
i can get this completed.
polarbeard: well names are for humans,
I think humans is what jurov is concerned with
polarbeard: yep, but
I didn't know such thing existed
polarbeard:
I'll definitely have to checkout gcov itself first
PeterL: ascii_butugychag>
http://log.bitcoin-assets.com/?date=03-02-2016#1395141 << when americans stuff ballot box, they like to set it up as 'dark horse candidate' <<
I wouldn't call Cruz a dark horse, there are just so many candidates he must have been overlooked, we didn't get bets for huckabee, santorum, fiorina, christie, etc, either
☝︎ phf: can probably add something like lxr, but
i need a better idea of how they do c++ parsing/indexing
ascii_butugychag: incidentally,
i found that a blackholed node won't respond to rpc
ascii_butugychag: but thing is,
i specifically am interested in what the thing is doing when it is ~unable to produce log~
ascii_butugychag: mircea_popescu: sorta why
i'd rather plot externally than grep
thestringpuller: ascii_butugychag says "LISP is you friend" so
I'll give it a try.
thestringpuller:
i thought tail -f debug.log was the only way to see what was actually going on
ascii_butugychag: is so that we can get to a place where there is NEVER a situation of '
i wonder wtf the node is doing'
ascii_butugychag: what
i do know is that -connect nodes within my walls do not ever blackhole.
mircea_popescu:
i dunno what it is,
i've never seen it before trb myself, nor a really good one since.
ascii_butugychag:
i can say at this point that it is not a network issue as such
mircea_popescu: oddly enough
i don't get blackholed nearly as often as you do o.O
mircea_popescu: last time
i did it it went flawlessly. the time before that,
i took three tries because
i fucked up twice.