Show Idle (> d.) Chans
← | Results 11251 ... 11500 found in trilema for 'f:ben' | →
ben_vulpes: mircea_popescu: yeah i figured, it's why he has it now
ben_vulpes: also nfi how this fits into your agricultural fanfic
ben_vulpes: BingoBoingo: dunno if you heard but praxair and linde are merging
ben_vulpes: and this can only be done by calculating the dag and then indicating who signed which patches.
ben_vulpes: but if it doesn't show me which patches are lacking sigs, that strikes me as a bug.
ben_vulpes: mod6: may construct his flow and press list in his v impl however he wants
ben_vulpes: that we print it as a list is an unfortunate accident.
ben_vulpes: fact remains that the dag can be constructed without reference to the wot.
ben_vulpes: wot filters what may be pressed.
ben_vulpes: flow is simply the directed acyclic graph of patches, and is *not* predicated on wot contents.
ben_vulpes: as asciilifeform's original and mine did.
ben_vulpes: the antecedent chain can be constructed without ever needing to refer to the signing of patches, and imho should show all patches in the flow, alongside which keys signed them and if none then marked as wild
ben_vulpes: "flow" refers to the antecedent chain, nothing else.
ben_vulpes: pressable being operative word there.
ben_vulpes: they should still appear in the flow but marked as wild.
ben_vulpes: well, hang on. if patches with no sigs are omitted from flow, they won't show up as WILD in the flow, correct?
ben_vulpes: i think this is 'implementation detail'.
ben_vulpes: (and in the absence of a WILD boolean, asciilifeform's pain-receptor-switch)
ben_vulpes: provided the implementation fails if any patch in the flow has *no* signatures from keys in .wot, that sounds right.
ben_vulpes: i'm changing diapers over here, it's a wonder that even asciilifeform can make sense of what i'm saying.
ben_vulpes: anytime trinque
ben_vulpes: let's rewind: what does trinque miss when v finds a seal for a vpatch for which it doesn't find a key and proceeds merrily, provided it does find *a* seal for the patch that corresponds to a key in .wot?
ben_vulpes: that did not parse over here
ben_vulpes: lol "it's purpose is to cause"
ben_vulpes: these things?
ben_vulpes: what purposes are these
ben_vulpes: i will motherfucking *not* shuffle both patches/* and .wot/* around when i want to press. this is stupid and carves off a whole space of adjacent possible.
ben_vulpes: i get the impression i disastrously fail to understand your point, trinque .
ben_vulpes: i reserve the right to hold onto gavins patches and never press them by use of .wot.
ben_vulpes: of course it does, that's what .wot is for.
ben_vulpes: one can have either "die on discovery of seal for which wot lacks key" or "wot variant press"
ben_vulpes: trinque: best i saw was that you want more than one seal and i'm content with one
ben_vulpes: trinque: please say what hard definitions are lost.
ben_vulpes: mod6: aha, privkey_tools descends from the low_s and testnet patches
ben_vulpes: phf: thank you
ben_vulpes: error, really. making a null set joke.
ben_vulpes: and sure, if .wot is the empty set, return true ;)
ben_vulpes: trinque: if all vpatches from genesis to HEAD carry a signature corresponding to a key in .wot, v presses. that signatures exist in .seals for people i don't choose to put the key for into .wot should not matter.
ben_vulpes: instigated the whole brouhaha
ben_vulpes: we just saw that in v.pl, did we not?
ben_vulpes: i do not believe that mine did that.
ben_vulpes: asciilifeform: 'press if no signature is found'?
ben_vulpes: trinque: all three implementations show which keys signed which patches in flow output.
ben_vulpes: i hold that exiting on discovery of a seal with no corresponding key in .wot puts an unnecessary burden on the operator to maintain system state.
ben_vulpes: we digress
ben_vulpes: completely misremembering ru alphabet lessons, apparently.
ben_vulpes: phf: i'm just wrong
ben_vulpes: scuse me
ben_vulpes: r sounds like g to them or something
ben_vulpes: russification of 'error'
ben_vulpes: http://btcbase.org/log/2016-01-24#1383818 << i believe some are laboring under the impression that eggog == hole
ben_vulpes: phf: now tell me if that's sloth or fear
ben_vulpes: with 'not battlefield ready' all over it, but nevertheless.
ben_vulpes: phf: asciilifeform signed his, iirc i signed mine
ben_vulpes: and argument ad that's how it was done does not carry
ben_vulpes: then i object to it now.
ben_vulpes: then wot-variant presses were never possible with the originally released v?
ben_vulpes: asciilifeform: did your v exit when finding signatures without matching keys? i do not recall.
ben_vulpes: which i wrote before putting down a single line of code.
ben_vulpes: could be argued out of 2)
ben_vulpes: 1) is incorrect imho and 2) also incorrect imho
ben_vulpes: 2) death()-ing on signatures for which a key does not exist in .wot
ben_vulpes: 1) pressing vpatches absent signatures matching keys in .wot
ben_vulpes: these are separate issues
ben_vulpes: trinque: i don't follow either
ben_vulpes: that there are 3 implementations of v is an indicator of healthy amounts of risk taking.
ben_vulpes: phf: elaborate on pbf link?
ben_vulpes: phf: ty
ben_vulpes: phf: can i get http://therealbitcoin.org/ml/btc-dev/2016-November/000241.html in the experimental patchset in your viewer?
ben_vulpes: trinque: augh no please no
ben_vulpes: just because mircea_popescu didn't complain about the failure at the time doesn't make it right.
ben_vulpes: no, that's death() ing on a patch for which the system had valid seals, yours and mine.
ben_vulpes: mod6: nobody is trolling
ben_vulpes: and yes, this implies an o(n^2) worst case process in (or (map 'boolean (lambda (sig) (verify 'some_patch.vpatch' sig)))
ben_vulpes: i'm pretty sure the design as described above is correct. the way i imagined this working in steady state is for patches and .seals to accumulate all of the patches and signatures thereof a user'd seen over all of history, and then the contents of .wot used to filter the patches and press used to pick a head.
ben_vulpes: so long as there is at least one signature for which v can import a corresponding key, that patch should press.
ben_vulpes: mircea_popescu: yes
ben_vulpes: wot is a /filter/ on signature dir.
ben_vulpes: imho v should not barf when patch and seal exist but key does not in wot
ben_vulpes: asciilifeform: and .git idem but let's not.
ben_vulpes: asciilifeform: to be fair, .wot, .seals and patches apparently constitutes 'hidden state' today.
ben_vulpes: nono, .wot governs.
ben_vulpes: if by "mircea_popescu" you mean "only mircea_popescu's key in .wot"
ben_vulpes: *signatures* i actually mean to say
ben_vulpes: beyond patches, that is.
ben_vulpes: asciilifeform: i dun recall mine doing any verification
ben_vulpes: ftr i do not want to bin v.pl
ben_vulpes: the other thing is separate and not precisely a problem, i mean to say.
ben_vulpes: no, this is separate and not exactly a problem anyways.
ben_vulpes: software review takes *months* if not *years* around here. part and parcel of the deficit spending and how the humans choose to allocate their time.
ben_vulpes: http://btcbase.org/log/2016-12-21#1587516 << actually /i/ found it, and only when for personal lols i told it to do a thing that it shouldn't have
ben_vulpes: anyways the notion that anyone on facebook is anything other than a non-player character is hysterical on the face
ben_vulpes: "catholics did it!"
ben_vulpes: ahaha first line even mentions facebook
ben_vulpes: !#s enumerating badness
ben_vulpes: https://twitter.com/JedWheeler << low dough calolxit twittering
ben_vulpes: my patience for wwwtronic fiddling is rapidly eroding
ben_vulpes: in which the inadequacies of wget for archiving an apache server become apparent or something
ben_vulpes: i had a full transmission swap done on the civic for less
ben_vulpes: do you also pay for oil changes at the dealership?
ben_vulpes: pete_dushenski: 2k? for a /starter/?
ben_vulpes: now for my next riddle, what solstice gift do you get a woman who already has a baby and doesn't want another yet?
ben_vulpes: right on
ben_vulpes: also you know who opened the door, what's with the passive voice
ben_vulpes: BingoBoingo: 'relieved'
ben_vulpes waits for "omfg whats wrong with you americans, none of those tits were even on girls"
ben_vulpes: lotsa rape and titties
ben_vulpes mutters westworld again
ben_vulpes: oh hey whaddayaknow, getmemorypool eventually returned
ben_vulpes: is anyone aware of a 'muxing' 'dashboard' for staying abreast of several different clients' opinions of network state?
ben_vulpes: and i don't recall it well enough to find. alas.
ben_vulpes: asciilifeform: do you recall and could you cite a line where you talk about folx using ersatz clients, forking and 'fools'?
ben_vulpes: kinda think that a bitcoin client is journeyman republican project
ben_vulpes: asciilifeform: i've ruminated on this as well before
ben_vulpes: all of a sudden i want to collect data on how long trb takes to return from a simple getinfo call, per your above protocol
ben_vulpes: i may also need to adjust my log rotator, 1 gig of bitcoind logs is...not actually that much history.
ben_vulpes may look sometime
ben_vulpes: oh blackholing propagates naturally?
ben_vulpes: mircea_popescu: archive.is is paywalled
ben_vulpes: (impossible to differentiate!)
ben_vulpes: (or -- processing block)
ben_vulpes: and how
ben_vulpes: what 'makes'
ben_vulpes: during which the node is ~entirely unresponsive
ben_vulpes: mod6: no, the thing where either a shitty network client or some joker opens sockets and lets them expire, eating 60 seconds of the loop through each peer to service
ben_vulpes: i don't expect to be able to make an rpc call while the node is looping through its list of peers and get 'the right' peer shat out
ben_vulpes: asciilifeform: i mean when the node is running through 'accepted connection' 'socket no message in first 60 seconds'
ben_vulpes: when in blackhole mode
ben_vulpes: might be interesting to patch trb to dump relevant connection's self-identification string
ben_vulpes: but i mean blackholing as artifact of some other poorly written client, instead of script opening sockets to trb nodes
ben_vulpes: sure, trb shoulda been aborted
ben_vulpes: i doubt itll show up on solipnet
ben_vulpes: didnt think so
ben_vulpes: is there intuition about whether blackholes are attacks or retarded clients?
ben_vulpes: http://btcbase.org/log/2016-12-20#1586533 << 'coracle', my battlefield node
ben_vulpes: http://btcbase.org/log/2016-12-19#1586383 << http://wotpaste.cascadianhacker.com/pastes/XDTr8/?raw=true ; note that i use the wrong command `getmempool' (line 8587), and that my rpc command of `getmemorypool' doesn't show up at all in the log, but some thirty seconds after the bogus `getmempool' the blackhole symptoms kick in
ben_vulpes: masquerading as science, good grief.
ben_vulpes: which puts anyone involved with Nature specifically and US 'STEM' in general in line for the noose
ben_vulpes: (potential) crime 3: 'study' appears to entirely omit 'control group'
ben_vulpes: crime 2: isn't this actually evidence that poor hispanics drug their kids more than anything else?
ben_vulpes: crime 1: n = 43 (i am /so/ impressed)
ben_vulpes: not that STEM even is salvageable from the imperial ruins, riddled with nsa stoolies like koch, overfitters like mann and the entirety of 'social sciences'
ben_vulpes: "we just can't handle the notion of a space where some people's suckitude is actually a barrier to their self-identification as 'a part of a thing'"
ben_vulpes: also holy shit what lolz the meatwot doth provide: http://stemtosteam.org/
ben_vulpes: https://freenode.net/news/PSA-brief-update-infra << 'sekuridee measures have been instigated!' oh good thanks exactly what i want, a riot in the dc
ben_vulpes: asciilifeform: will
ben_vulpes: either that or blackhole?
ben_vulpes: i think that i just crashed my node asking for the memory pool.
ben_vulpes: entirely unrelatedly to anything else, does trb's `getmemorypool' actually work?
ben_vulpes: asciilifeform: checkpoints.cpp really grates
ben_vulpes: i recall now
ben_vulpes: aight so i can drop checkpoints.cpp then?
ben_vulpes: davout: no, ancient one
ben_vulpes: davout: this is the 'sybil' thread, yes?
ben_vulpes off again, chiral train operation
ben_vulpes: more frequently i just regenerate my tags file.
ben_vulpes: asciilifeform: i too, on occasion.
ben_vulpes: not only is there state smattered everywhere but it's inscrutably altered by who even knows what when
ben_vulpes: also god bless cpp, i want to know where "mapBlockIndex" is defined have to grep the fucking codebase
ben_vulpes: and the checkpoints are at the root of that by my read.
ben_vulpes: but that the thing won't lan-mine is abhorrent imho
ben_vulpes: perhaps, though, 'grandfathers pistols' problem rears its head here.
ben_vulpes: i do not see this 'win' as bugful.
ben_vulpes: aha tru
ben_vulpes: also this 'win' is baked into how the blockchain works.
ben_vulpes: what rules are these that they might not win?
ben_vulpes: 'cold equations'
ben_vulpes: asciilifeform: if martians produce longest chain with greatest difficulty i think by the rules of the game they own bitcoin
ben_vulpes: asciilifeform: i disembark this train shortly, but yes lets
ben_vulpes: isn't that sanity check "show me a block with a higher diff and lineage back to the genesis block"?
ben_vulpes: one man's obvious is another man's obscure rathole broken by shitgnomes
ben_vulpes: thing is broken in very obvious way, news in year 3
ben_vulpes: embarassing as it is that i'm only now finding that trb doesn't solipsistically mine, i did determine that it validates the whole chain.
ben_vulpes: asciilifeform: mine too
ben_vulpes: yeah i hadn't seen one. doesn't mean it doesn't exist.
ben_vulpes: so there's no 'at block XXX use iAmRetardedBlockValidator'?
ben_vulpes: mircea_popescu: and the rules were changed to permit these busted transactions?
ben_vulpes: because 'new' validation rules?
ben_vulpes: http://btcbase.org/log/2016-12-19#1585810 << asciilifeform didn't you do a whole run of eatblock? 'deterministic sync'?
ben_vulpes off. pants; train
ben_vulpes: asciilifeform: actually do you think stuffing entire www-dir behind webserver > gzipped ball?
ben_vulpes: asciilifeform: if you'd like a copy i can get you a link later today
ben_vulpes: thanks, tmux
ben_vulpes: if anyone wants copies, you know where to write. the recipe, however, is tres simple: wget -mpr www-cgi>
ben_vulpes: http://btcbase.org/log/2016-12-07#1579351 << i have archived everything on that www-cgi endpoint now
ben_vulpes: subj of homework
ben_vulpes: so sqlator q1 is feasible but whatever, don't count on it.
ben_vulpes: i just demoted the entirety of my todo list in favor of this mining thing, which is actually a subtask on a thing for mod6
ben_vulpes: stop committing me to things
ben_vulpes: produced blocks that it wouldn't validate itself? throw me a bone here
ben_vulpes: k thx
ben_vulpes: mircea_popescu: what was the root of this fork?
ben_vulpes: still no mining, and my nose points at the initialblock check
ben_vulpes: i acquiesed to the inanity and made 2 nodes happen
ben_vulpes: yeah we did this
ben_vulpes: http://btcbase.org/log/2016-12-19#1585630 << and specifically, i believe isInitialBlockDownload
ben_vulpes: asciilifeform: how is 'palaver'?
ben_vulpes bbl for real this time
ben_vulpes: neat idea
ben_vulpes: miner should work just fine without a tx in mempool wtf
ben_vulpes will read miner source for the site of this brilliance
ben_vulpes bbl, child has self-aborted nap
ben_vulpes: true nuff
ben_vulpes: no then he sent some somewhere?
ben_vulpes: first hundred and seventy only paid out to satoshi iirc.
ben_vulpes: blocks.
ben_vulpes: first hundred and seventy went fine
ben_vulpes: getgenerate returns true, but fGenerateBitcoins is 0 at boot
ben_vulpes: a recently compiled bitcoin node, running in its own directory, booted as `LC_ALL=C ./bitcoin -datadir=<local_data_directory> -debug -printtoconsole -gen'
ben_vulpes: can be stuffed in cli
ben_vulpes: in bitcoin.conf?
ben_vulpes: asciilifeform: genesis only
ben_vulpes: asciilifeform: 'getinfo' is telling me '0 hashes per sec', which is troubling
ben_vulpes: BingoBoingo: noshit.png
ben_vulpes: asciilifeform: when booting anode in 'solipsistic test network' mode with gen=1 and genproclimit=some reasonable fraction of local cores, i should see a few cores go to 100% utilization immediately, no?
ben_vulpes: which is particularly amusing, as this stamped material is designed to line up perfectly for the whole run
ben_vulpes: and maybe 2 boards out of the whole 150' house length per row are matched at the ends
ben_vulpes: so the vinyl, stamped-with-wood-grain siding showed up and was applied to the house
ben_vulpes: omg may i relate how bad a job next door is doing
ben_vulpes: with the new monstrosity abutting the property line next door, i think i've finally bumped carport up on the list of shit to build
ben_vulpes: fwiw, i find car-swearing-time doubles as excellent design/thinking time.
ben_vulpes: theorems to prove, belts to change...
ben_vulpes: "this dress took me thirty minutes and ten years to make"
ben_vulpes: mig engines are for 'fun'
ben_vulpes: asciilifeform: capital equipment is not for 'fun'
← | →
Random(trilema) | Download hourly DB snapshot | Get Source Code