log☇︎
232200+ entries in 1.92s
trinque: it aims to cause you to do certain things
ben_vulpes: what purposes are these
trinque: the thing is a political tool, and either does or does not acheive its desired effects
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.
trinque: but first the definition
trinque: otherwise yes, asciilifeform is right that if this doesn't matter, just have a thing that presses patches with hashes in the m
trinque: you do not trust the seal; you trust the identity
trinque: http://btcbase.org/log/2016-12-22#1587898 << this destroys the ~who~ of each seal, which matters ☝︎
asciilifeform: when we discuss in the logs, it can be many things, but not formal definition.
ben_vulpes: trinque: best i saw was that you want more than one seal and i'm content with one
asciilifeform: gotta write actual article trinque
asciilifeform: formal definitions don't live in the logs
trinque: were they not in the logs?
asciilifeform: trinque: if you'd like to take a stab at a formal definition, i promise to read
trinque: but I cannot see *why* they should other than "I just want to"
ben_vulpes: mod6: aha, privkey_tools descends from the low_s and testnet patches
trinque: if I am truthfully the only one present that sees parts of the hard definition of this thing falling off all the time I'll leave it there.
phf: ah, yeah i see. ok i'll keep funken one in experimental too, and move it to deprecated eventually
ben_vulpes: phf: thank you
mod6: with some minor tweaks
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.
trinque: ben_vulpes: what keys, you said you don't have them anywhere
asciilifeform goes and rereads mod6's thread
ben_vulpes: instigated the whole brouhaha
ben_vulpes: we just saw that in v.pl, did we not?
asciilifeform: that is, i know of no case where an unsealed, or invalidly sealed, or sealed by nonexistent pubkey, patch, would be pressed without the user having explicitly flipped the red cover and disabled the reactor coolant pump
ben_vulpes: i do not believe that mine did that.
trinque: how is this effective use of crypto at all?
ben_vulpes: trinque: all three implementations show which keys signed which patches in flow output.
phf: well, since collective reaction is "tis but a scratch" i have nothing else to say, and will happily await mircea_popescu's unrate ☟︎
trinque: presses the thing sealed because ambiguous somebody signed?
trinque: ben_vulpes: what does the thing do if not exit?
mod6: im just trying to minimize the warts a bit.
asciilifeform: i.e. the mechanism whereby you press a set for own consumption
mod6: phf: naw. even mircea_popescu has encouraged me to release it, even if it has warts.
asciilifeform: all of the 'bickening' seems to concern 'harem-v'
asciilifeform: i dun recall anyone, any time recently, disputing the functionality of the latter
phf: ben_vulpes: well, the point of V that has been celebrated is its ability to support a scientific dialog. you say something, i make a response, etc. this thread was literally about three different versions, one of them is stale, one of them is unreleased. there's not really an easy way to point to the line and say "oh this is what this does" etc. i claim that the source of this problem is fear. the genesis has to be perfect for all
mod6: that seems fine, and yes, less painful to me.
mod6: i like the idea that you've got 'mod6 & ben_vulpes' in your .wot, and that you hvae 69,000 sigs in your .seals dir, and only select out the ones that match the .wot.
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.
mod6: And I'm happy to embark on a genesis once we resolve these current problems and the testing and review by lords is complete.
mod6: i do want that traceibility from V, of my V.
asciilifeform: it was orcs blindly copying human tech
asciilifeform: sound had 0 to do with it
asciilifeform: trinque: https://upload.wikimedia.org/wikipedia/commons/thumb/1/10/Elektronika_MK_52_with_ERROR.jpg/400px-Elektronika_MK_52_with_ERROR.jpg << them ☟︎
ben_vulpes: r sounds like g to them or something ☟︎
trinque: real quick what the hell is eggog
a111: Logged on 2016-01-24 03:21 mircea_popescu: to put it in you'll have to sign it. if it turns out later to have a hole, people will negrate you.
ben_vulpes: http://btcbase.org/log/2016-01-24#1383818 << i believe some are laboring under the impression that eggog == hole ☝︎
mod6: and who knows, imho, there's no gigantic rush to make a genesis for v. especially when we're still trying to work out how it should work.
asciilifeform: cost of failure, sometimes you simply live with. i signed FUCKGOATS, and it is a 'sapper makes 1 mistake' item, it is not possible to repair the units if i had made a mistake.
mod6: creating a genesis is a different thing too; v create a genesis of v. which i did work out, but alas, as you are eluding to, i never published because was nervous that it hadn't been very well audited yet.
phf: well, last time i brought it up with mod6 he said something along the lines of "i'm not ready to sign, because it's still work in progress" ☟︎
ben_vulpes: phf: now tell me if that's sloth or fear
trinque: and fwiw phf I merely said "do not come to me asking about phf", recently. I did not say further.
phf: none of them are genesis + vpatch revisions.
mod6: mine is signed 69 times for sure.
trinque: but there is a place to do so, where there could be separation between the lab and the published-in-journal
asciilifeform: nobody proposed, iirc, to begin to publish unsigned turds, or to accept same off the net and press, etc
phf: ben_vulpes: this subthread since your response to my original statement is one example of what i'm talking about. in this case none of the v implementations are on btcbase, because nobody wants to sign own hacks, because the cost of failure is too high. ☟︎
trinque: my digestion of the notion of opposable signatures produces this output.
asciilifeform: this is quite true
trinque: V as conceived as a political weapon against the shitsucking github fuck does not work without the attribution the signatures provide
trinque: my objects can be better stated as an irritation that the political considerations here do not seem to be driving the conversation.
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?
asciilifeform: i ended up turning that into a warning, vs fatal, but it looks like i never posted this variant. ☟︎
asciilifeform: guess what, looks like the published version -- indeed did.
mod6: infact, i stole that error message.
mod6: i posit that it did indeed.
asciilifeform: iirc he a) fully understood how it behaves b) tendered no major objections
mod6: i'm happy to re-write/overhaul/whatever this thing.
mod6: but i'm trying to get down to brass tacks as much as possible.
mod6: now, we not want that behviour any longer. ☟︎
mod6: <+ben_vulpes> no, that's death() ing on a patch for which the system had valid seals, yours and mine. << this i dont agree with -- from a technical perspective. it looks to me that girl had "ascii and mod6" in .wot, and when it came across Mr. P.'s genesis .sig, it honked.
mod6: im <+ben_vulpes> just because mircea_popescu didn't complain about the failure at the time doesn't make it right. << maybe.
asciilifeform: ( the bug, as mircea_popescu iirc also pointed out, was in the direction of making his vtron ~stricter~, of forbidding entirely legit ops, so not catastrophic)
asciilifeform: trinque: are you thinking of mod6's minor bug , or of some other ☟︎
asciilifeform: i was addressing mod6's 'damn, why did i even try' lament
trinque: this squirming away from "why does the output not match the pages of ideology" is troubling.
ben_vulpes: that there are 3 implementations of v is an indicator of healthy amounts of risk taking.
asciilifeform: and much better for it to be amortized in expensive chairs, than in total lack of risk-taking
asciilifeform: phf: this is not wholly avoidable, imho, folx laugh at airplane chairs or surgical scalpels costing thousands of usd, but in some sense it is inevitable
phf: ben_vulpes: this was a general comment, but the cost of failure is so high, simple things have become needlessly complicated.
asciilifeform: ( recall, we had been trb-ing with exclusively signed patches since start of trb, but folx other than asciilifeform were having headache determining the correct order to apply in )
asciilifeform: mircea_popescu immediately realized what can be done with this knob and wrote, iirc , entire article re same
asciilifeform: then i decided that it could be useful to glue these ops together, so that variant-wot operation is possible.
asciilifeform: trinque: my original, unpublished vtron, only pressed (tracking the dependency flow), and user was expected to check the pgp sigs of the inputs, with bare hands, prior
trinque: but we can "just wante to press" because god's children
trinque: and what, I have to be drinking to see this? spent pages criticizing the horrible, accidental evolution of cat.
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?
deedbot: http://phuctor.nosuchlabs.com/gpgkey/E03B4EF8E133B56D2A25926C00E369EE3792631DC988331D73F46F8DA9570C04 << Recent Phuctorings. - Phuctored: 1579...5447 divides RSA Moduli belonging to '182.253.207.29 (ssh-rsa key from 182.253.207.29 (13-14 June 2016 extraction) for Phuctor import. Ask asciilifeform or framedragger on Freenode, or email fd at mkj dot lt) <ssh...lt>; ' (Unknown ID JK)
deedbot: http://phuctor.nosuchlabs.com/gpgkey/CBE0788A94B99B46A2AC2D42BBE157E14FCD5E21FB4C6B42AC319B2A978D89E3 << Recent Phuctorings. - Phuctored: 2486...1113 divides RSA Moduli belonging to '65.175.110.170 (ssh-rsa key from 65.175.110.170 (13-14 June 2016 extraction) for Phuctor import. Ask asciilifeform or framedragger on Freenode, or email fd at mkj dot lt) <ssh...lt>; ' (Unknown US MO)