assbot: Woman says she is a cat trapped in the wrong body - she hisses at dogs, hates water and claims she can even see better at night - Telegraph ... ( http://bit.ly/1PKiW2x )
shinohai: http://www.telegraph.co.uk/news/newstopics/howaboutthat/12127067/woman-says-she-is-a-cat-trapped-in-the-wrong-body.html <<< maybe she's single guys!
mod6: hanbot: alrighty, thanks. sometimes if I don't hear anything, i just assume the worst. heheh.
mircea_popescu: http://funcall.blogspot.com.ar/2009/03/not-lisp-again.html << actually this is splendid, as a narrative. esp the part about derivatives.
hanbot: not really. i've been fucking around trying to get bash to save public key block to file without detritus, giving up for now and just copypasting. i'll letcha know if it goes wrong, thanks for the cleanup note.
mod6: if you tried to build with this script, and something went wrong, which im pretty sure that it did, you need to blow everythign away (aside from your .wot dir and your keyring of course - have back ups! /me looks at people who blew away their keys) and start over.
mod6: <+mircea_popescu> ah nm, it was the x86 flag << yeah.
ascii_butugychag: the life of whoredom!111
ascii_butugychag: (the thing that looks like arse cheeks was originally a dfa)
mod6: # Required Public Keys to add to your PGP Keyring. These are used to verify V, rotor, buildroot, and trinque's patch:
mircea_popescu: mod6 it's no good because it still doesn't explain WHERE they should go. it's ambiguous between .wot and keyring\
mod6: as soon as i get through the end of this month, a renewed emphasis will be put on ditching this script, and getting to a finished place with trinque's makefiles that'll hopefully be easier to understand.
phf: (all this v talk past few days, i decided to sit down and grok, so Writin My Own V (tm)(c) at the moment)
kakobrekla: it brings me some satisfaction im not the only one confused
phf: having multiple hunks in a patch modify several files at the same time creates a harder transition constraint then simple antecedent/descendent pairing, so i'm thinking it's probably safe to construct a graph in terms of transitions rather then purely a/d. the end result should be the same
mircea_popescu: ah nm, it was the x86 flag
mircea_popescu: kakobrekla iirc it was the bdb locks thing fix ?
mod6: kako: http://therealbitcoin.org/ml/btc-dev/attachments/20150808/rotor-db-configure-fix_a955ba9174ccb17790dc9d7c1e2a61794a1c803d.patch
phf: mircea_popescu: anyway, i was speaking of how things are right now in v.py/v.pl. a hunk touches a file, hunks are grouped thematically (i.e. by a single unit of meaning) in a patch. a pairing of antecedent/descendent creates a graph and in combination with topo logical sort produces a press order
kakobrekla: what is the 'special patch'?
mircea_popescu: im sorry, other stuff. and i typo'ed verify.
mircea_popescu: maybe actually explicit the "Some stuff"
mod6: I'll change the comment, standby.
mircea_popescu: + # You need to have these keys in your gpg keyring to vertify V, trinque's special patch, buildroot, and other stuff.
mod6: to verify V, trinque's special patch, buildroot, and other stuff.
mod6: these are public keys that you need in your keyring
hanbot: oh so i don't actually need korsgaard's key in the .wot dir
phf: v is used to press the source only, but there's a bunch of shit happening outside of v, including verifying some third party package signed by this korsgaard guy
mircea_popescu: mod6 no but she needs to name the file something
mircea_popescu: for that matter the level of abstraction displayed justifies the use of MAYBE three files, otherwhise it really looks like the guy wrote the whole thing on one scroll so to speak.
mircea_popescu: i don't think you can find anyone who both read bitcoin source and thinks the file split is sane.
mircea_popescu: phf well yes but using v as an ideal object vs using v as applied to the world's most patently deranged pile of cathair and wet noodles.
ascii_butugychag: the reason why i once suggested breaking up all patches into atomic patchons is that right now we have a stricter than necessary dependency flow
ascii_butugychag: phf: the idea is that those are semantically related
phf: i think it's relevant, but i need to reflect how. fwiw right now there's a bunch of vpatches that modify multiple files at the same time
mircea_popescu: that situation may occur, and it is a signal that the way code is split into files is broken and needs fixing, i guess.
phf: i remember ascii suggesting that perhaps we should stick to one hunk per patch, but that's not the case right with existing patches. if z thematically needs to touch two different files (a and b), then both modifications are inside a single patch
mircea_popescu: this remains true even if we go from a, b being files to them being blocks, or themes, or other reasonable division.
phf: so we have files a, b and patches x, y, z. x is genesis. y is a->a'. z is a'->a" b->b'. the way v connects the graph is x-y x-z y-z, i.e. patches that have hunks that share state for a file in before and after are connected. it is explicitly not a transition graph, which would be x-y y-z (since you can't apply z on top of x without first applying y)?
mod6: and upon a few others successfully building, trinque, can you work your magic with deedbot and place that guy in there so its like deedbot.org/build-bitcoind-v99996K.sh or whatever?
mod6: thanks danielpbarron -- hey please give this a try if you can. I figured that you might be a good one to simplify the steps and up date the wiki as soon as we get some confirmation that all is good with the script
assbot: Logged on 29-01-2016 19:13:35; mod6: you just need to create a .wot dir and place keys in there, then (in the same directory do this): `./build-bitcoind-v99996.sh`
thestringpuller: you've watched the animaniacs
mircea_popescu: actually, there's a cartoon of all thiongs that best illustrates what a blackboard is as a device of thought. lemme see if i can fish it out\
ascii_butugychag: i really wish they came in full man size
mircea_popescu: it's mathematical alright, just i guess unsatisfying for a wholly unrelated biological cue
ascii_butugychag: i still remember the whanging headaches i got just from sitting in front row
mircea_popescu: lower perceived resistence of the medium ?
ascii_butugychag: mircea_popescu: who said they didn't
ascii_butugychag: but i find that there is something palpably... unmathematical, about 'whiteboards'
mircea_popescu: they're not terribru. better colors.
mircea_popescu: ah, mno, gotta be one to see the curricula :D
mircea_popescu: hey, best part of physics lab was the blackboard imo
ascii_butugychag: i can only do that here because no math in the chan
mircea_popescu: just like their unruly, ill behaved irl counter... parts.
mircea_popescu: how so ? they pop in at any time
ascii_butugychag: these - behave.
mircea_popescu: consider the epic failuire of private messages to gather import or relevance in the trb and you;'ll have a fine illustration of why multiband is retarded.
ascii_butugychag: yes but the fundamental debate is about how to interpret.
ascii_butugychag: there is also 'what follows is N bits which will behave AS BITS' or 'what follows is M bits which are launch code.'
mircea_popescu: the discussion is whether you're an educated sort of dude with collapsed bands, or a barbarian needing "multiple" but somehow magically not infinity-many bands
mircea_popescu: ascii_butugychag would you stop trying to be cute. in band signalling is the only fucking signalling there is, until you invent telepathy.
phf: i remember there was a pretty big stink when firefox was magic sequencing xml files as rss feeds years ago
ascii_butugychag: somehow this magic ended up in the html.
ben_vulpes: ascii_butugychag: unless it's the magic bits to dump the launch codes back down the pipe
ascii_butugychag: in-band signalling (i.e. 'this magic sequence of characters anywhere in the text launches the rockets') suxxxx.
mircea_popescu: it pays to re-read the classics.
mircea_popescu: "This is one of those things that seem true for those who have gotten spoiled by the windowing environment. The reason this can't be considered true is that at some point, you have to specify (or get down to) a ModelOfComputation, and the one most programmers use is simply different than LISP which is very different since it has no definition of MachineTypes?. See ConfusedComputerScience."
mircea_popescu: http://c2.com/cgi/wiki?GreenspunsTenthRuleOfProgramming << check out the lulz, incidentally.
mircea_popescu: just continuing down the road.
mircea_popescu: We see the Slashdot community as a vibrant community made up of industry professionals and enthusiasts that are extremely passionate about tech, tech news and discussion, many of which have been active and engaged for over a decade, he added.
mircea_popescu: Well, Im not sure I completely agree that Slashdot is less vital these days or has lost its luster, he replied. It serves millions of unique viewers each month, which we think is pretty significant.
mircea_popescu: Our plans for Slashdot include supporting the mission of Slashdots slogan, news for nerds, stuff that matters,' he said. The site has millions of loyal users that visit and engage on the site each month, and we want to do the things necessary to keep Slashdot positioned as the best technology-centric news and discussion site on the web. We do not plan any radical changes, and will keep the opinions of th
ascii_butugychag: the whole shit soup toolchain needs to die
mircea_popescu: Slashdot Media, which owns the popular websites SourceForge and Slashdot, has been sold to SourceForge Media, LLC, a subsidiary of web publisher BIZX, LLC << o check it out, moar spam.
mircea_popescu: whoa mom, check me out, i made it through yet another day of these here kiloline logs!
assbot: Logged on 29-01-2016 15:38:47; ascii_butugychag: i suppose this is when i restate my rage at the idiocy of gnudiff
mircea_popescu: http://log.bitcoin-assets.com/?date=29-01-2016#1388421 << of course nothing would prevent us at this stage to take either gnudiff or any shell diff, gut it, make it into proper vdiff and forget they ever existed.
assbot: Logged on 29-01-2016 15:08:20; thestringpuller: the problem here is I doubt satoshi had any idea how visa and traditional payment systems scaled in comparison to bitcoin.
mircea_popescu: http://log.bitcoin-assets.com/?date=29-01-2016#1388410 << or that satoshi said a bunch of dumb shit, a fact both obvious to the naked eye and plainly admitted by the repentant perpetrator himself.
trinque: yep, I have a ticket open to have an SSD put in my new box,b ut am awaiting response from the (disappointing) new DC
mircea_popescu: well other than get bogged down in / give a shit about inept nonsense being thrown their way.
ben_vulpes: their blog has even gone to spamseed
mircea_popescu: they failed to do anything with that advantage tho
ben_vulpes: http://cascadianhacker.com/blog/2014/08/28_conformal-are-the-real-bitcoin-core-devs.html
mircea_popescu: right. back in the day it was actually more promising
ben_vulpes: it looked better than prb back in the day
mircea_popescu: o wait, the java one one or w/e it was ?
ascii_butugychag: trinque: how come you're using heathen bitcoinatron, again ?
mircea_popescu: wasn't the case pre-gates, say.
mircea_popescu: ascii_butugychag i just meant they've been living in a particular half-world for a while now.
assbot: Logged on 29-01-2016 14:55:07; trinque: there is a kiss of death for btcd which halts it in its tracks, does not crash.
mircea_popescu: what, no pagelong paranthesises ?
mod6: trinque shinohai ben_vulpes polarbeard & anyone else who wants to test the new V & buildscript [v99996]: http://dpaste.com/2WQCDKX.txt
assbot: Logged on 29-01-2016 14:42:20; PeterL: are chinese miners some sort of unit that all must act together?
mircea_popescu: http://log.bitcoin-assets.com/?date=29-01-2016#1388381 << dude writing that formed his ideas about the world watching cheap tv entertainment. "chinese" is this sole guy, very polite, slanty eyes.
ascii_butugychag: the one about what jobs you were willing to take when you were a consultant
assbot: Logged on 29-01-2016 14:41:47; BingoBoingo: In other feelings https://bitcointalk.org/index.php?topic=1343716.msg13712823#msg13712823
mircea_popescu: http://log.bitcoin-assets.com/?date=29-01-2016#1388379 << lmao that is pretty much the picture-perfect image of what makes any lawyer retch.
hanbot: mod6> the one I just posted? << yeah
mircea_popescu: ascii_butugychag you know, "thinking of the work this means".
assbot: Logged on 29-01-2016 19:02:40; mircea_popescu: ascii_butugychag this harkens back to such a more lovely time in the computer lab.
mod6: the one I just posted?
mod6: you just need to create a .wot dir and place keys in there, then (in the same directory do this): `./build-bitcoind-v99996.sh`
mircea_popescu: all the shit you boys do just to get to pretend like you don't need any adhd meds.
ben_vulpes: and deserves more of a place in the lgos.
ben_vulpes: it is the hole through which distraction slips in and focus dribbles out.
ben_vulpes: the fifteen second interruption has mega cognitive costs.
mircea_popescu: like any other intellectual endeavour to date.
ben_vulpes: just wait the thirty seconds randomly five times per event, having a spare on hand will never pay off.
mircea_popescu: that what female enslavement is all about in the first place.
mircea_popescu: hey, the whole thing's predicated on productive waste.
ben_vulpes: but the w4ste!
mircea_popescu: have a girl on the side to reload 'em
ben_vulpes: spur* of the moment exercise.
ben_vulpes: programming similarly is not a supur of the moment.
ben_vulpes: you'd probably snap the thing in half
mircea_popescu: in other spuriously articulated news, http://41.media.tumblr.com/dd1de06b21cc8b41a66decb40820dda3/tumblr_nwspbs40Ru1uo6eclo1_1280.jpg
assbot: Logged on 29-01-2016 16:35:23; mircea_popescu: actually that's the first time someone brought a cogent, well thought out objection to the classic "programmers wanna play and so ruin productivity spending moe time on tools than the tools save" thing
mircea_popescu: ascii_butugychag this harkens back to such a more lovely time in the computer lab.
ascii_butugychag: i originally did not publish the thing that is now shiva because i was not comfortable with asking friends to read 5,000 lines of tinyscheme.
ascii_butugychag: the overall idea i am trying to teach is that anybody changing a line of trb ought to be mindful of the work this creates for others
mircea_popescu: well i'm not willing to stake on that, because what the fuck do you know we'll discover. but at least as an expected ideal, yeah.
ascii_butugychag: i see nothing wrong with cleaning up classical error handlers, etc, so long as it is done in line with the flow principle described earlier.
mircea_popescu: anyway, re the other point : even if scheme does in the end become an integral part of sane error management a) his work is very important for providing the structure that'll illuminate that and b) will prolly be mostly reused strings in different wrapping anyway.
ascii_butugychag: (i.e. part 1 can be mechanically-litmused: 'this only adds the ts genesis material')
ascii_butugychag: for thematic unity
ascii_butugychag: mircea_popescu: note how i cut the shiva patch in 2
polarbeard: usually there is a lot of blind trust involved
mircea_popescu: i'm slowly discovering what an IMMENSE help to debugging and code maintenance this thematic unity thing is, incidentally.
pete_dushenski: danielpbarron: you're the best :D
mircea_popescu: specifically because "majority is better than minority in every practical way" except the one way that actually matters, which the majority is never willing to confront.
mircea_popescu: and this is how bitcoin will continue to kick the teeth in of any sort of fiat, no matter how superficially bitcoinized.
mircea_popescu: THIS is how bitcoin, the "minority coin" par excellence, kicked fiat's teeth in.
mircea_popescu: thestringpuller minority coins may be "worse in every practical way", but they are BETTER in the only way that matters : minority doesn't inflate, majority does.
mircea_popescu: the best way forward, imo, is to restructure it as 1) one large patch consisting of nothing but the return fixes and some smaller patches doing the rest of the stuff built on top of that.
thestringpuller: "And minoritycoins will be worth much less than majoritycoins, because they are worse in every practical way. They take longer to confirm, fewer people accept them for payment, they are protected by less hash power, and they are much more difficult to transact safely." << Not if majority coin is sunk early on and money flees to minority coin. What "actual" economists is this d00d hanging out with that "vetted his scaling propos
polarbeard: punkman: yes, the rube-goldberg pipe was inteded to be used as a nohup'd tail on debug.log
ascii_butugychag: mircea_popescu: one of the items i have in mind for shivafication is sane event logging
thestringpuller: In other DERP, gavin apparently didn't read the hard fork missile crisis: http://gavinandresen.ninja/minority-branches
mircea_popescu: the point is that people running bitcoind have a whole array of measures, which mostly work as cat logfile | mess
polarbeard: for the priority
punkman: polarbeard: the thing usually runs as a daemon
mircea_popescu: yes, if you just dump into console i'm going to have to pipe the program throuygh a bunch of different greps
mircea_popescu: note however you should dump to file not to console. because otherwise mess of tee's
mircea_popescu: note that the only way i got my apparently very controversial /s /t patch to even be considered was showing how it could be machined.
polarbeard: also I thought you can dump to console and grep until we reach consensus on how we want to do the actual log splitting and filtering
mircea_popescu: ascii_butugychag has a good rule of thumb there.
ascii_butugychag: so i can ask the same question, line after line, for a whole patch
mircea_popescu: polarbeard yeah, you get the right idea, but seriously, making a single patch consisting of JUST -return error +return error is the right way
ascii_butugychag: 1 kind of thing - must be together
polarbeard: mircea_popescu: the patch ended up being a bit verbose, yep, but it made sense to me fixing the messages as I was adding metadata, that's why I didn't add filtering, to not add actual logic to an already pretty big patch
mircea_popescu: there's a lot of stuff in there that will necessarily result in a huge patch (the guy is stuck, willy-nilly, doing a lot of
ascii_butugychag: mircea_popescu: it bothered me that polarbeard apparently does not yet fully grasp that every line he writes is a unit of ~work~ for other people to do.
ascii_butugychag: but then i plugged it in...
mircea_popescu: . i'm with ben_v (and apparently ascii too) in that it's really best practice to make patches small and issue-focused. it's not just a matter of review, it's to ease future rebasing and so on. as antidesign it may seem to you personally on the basis of workflow, this is one of those things where individual has to take a small step back to allow society altogether to exist.
mircea_popescu: . i'm with punkman in that if you're going to prefix in that much detail, there's going to have to be some sort of filtering scheme. i'm not with him that flags are the solution, it just seems an ad-hoc hack unix did that got carried forward. i'm still partial to my multi-logfiles idea, fwiw. altogether a lot more thought must be put into "how to structure" this, but sadly it depends on a fully specified bitcoin, so it
ascii_butugychag: pete_dushenski: supposedly there is an x11 patch to make it go
ascii_butugychag: pete_dushenski: rat9 suxx, you can have mine for the cost of postage
mircea_popescu: just, in a metaprogramming sense that did not exist prior to V putting light on the issue.
assbot: Logged on 29-01-2016 16:06:03; thestringpuller: how you gonna sell a mouse for 60 bucks
mircea_popescu: so in full terms, i would say that again, including both in the same patch is both premature optimization and a kludge.
phf: a way to indicate (a->a' b->b') would normally be to include them both in a single patch. i think that's how it's done now
mircea_popescu: because people didn't make both y and z first level nodes of x, people are indicating that whether you know why or not, you need a->a' for b->b'.
mircea_popescu: phf nothing in the physical situation as you describe it indicates that. nevertheless, the implicit meaning in how the topo sort owrks is that you need a to a' for b to b' to be meaningful. this could be because one is .h and the other .cpp, fopr instance, or becauise other stuff is coming later or for any other reason
mircea_popescu: http://log.bitcoin-assets.com/?date=29-01-2016#1388324 <<< the end point, of course, whether is obvious or not, is to fix the half-assed braindamage that are the coin scripts.
phf: so in the above example x y z are distinct patches, their effect is to take files through states, a, a', a". so if a patch takes a->a', then it needs a in genesis. if a patch takes a'->a" then it needs genesis and a->a' patch. i was trying to indicate that y and z modify two separate files, i'm trying to see what is there that indicates that state (a' b') is desirable over (a' b)
mircea_popescu: im sorry, i mean : if you didn't need y, then y should have been z'.
mircea_popescu: if you didn't need Z then y should have been x'
assbot: Logged on 29-01-2016 14:29:59; PeterL: my node is syncing, seemed to be getting tons of junk. I restarted it, using -addnode with the nodes from the wiki, seems to be going good again.
punkman: phf, my "shortest path" algo is to recursively find all antecedents of the patch I want to press. it's useful.
phf: if i have files a b and patches x y z, x is genesis, y does a->a', z does b->b', topo sort x z y. if i were to ask for y press, i also get z, whether i need it or not. conversly if i press z, i don't get y.
assbot: Logged on 29-01-2016 14:36:41; BingoBoingo: And the lolz roll on https://i.imgur.com/Q2X24B7.png
mircea_popescu: that came in a few different flavours historically, and amusingly all unaware of their communion and unadressing it.
mircea_popescu: (or even WHETHER it actually works. hence all the - equally unexamined and inept - prb derpage about "blessed" chains)
mircea_popescu: it DOES work for bitcoin (in blockchain terms it's "longest chain"), but altogether it's not clear WHY it works
mircea_popescu: the shortest path thing is not only premature optimization but also a very mangled sort of heuristic.
mircea_popescu: and so... nobody could have foreseen all the way to chad.
mircea_popescu: you can't switch back. once you've decided to take the hardwood floor and light your stove with it, you can't then decide to take stove ash and make a floor.
mircea_popescu: BingoBoingo ironically, consider the historical aspect. vc's strategic mistake to NOT submit early and well ensured that they don't have a voice at the one time it'd have mattered. now they're getting locked out of bitcoin, which means computing, and what'll mit do, switch back to scheme because THAT is what junior devs will need to get jobs ?
phf: i'm confused about how v presses. i thought it was along the shortest path, but it actually does topological sort and then works with resulting list. so if my topo is a b d c f and i ask to press c, then i get a b d c?
gribble: The operation succeeded.
ascii_butugychag: (if you have the patience, watch the films, even, they are interesting in a number of ways incl. historically)
ascii_butugychag: BingoBoingo: once you understand how scheme's tail call optimization works, you are well on your way to actually grasping the thing
ascii_butugychag: also it will need some means of restarting it if the repl is hosed
ascii_butugychag: adlai: to me it simply means 'i don't have to leave my editor and FUCK NO I AM NEVER pasting code into a motherfucking shell 10000000 time a day'
adlai: ascii_butugychag: sure, i'm taking slime-the-~idea~ and trying to "take away everything that doesn't look like an elephant"
adlai: the subset of "all slime functionality", which do seem to me relevant for shiva, are the repl (history, presentations), the fancy-inspector (designed for CLOS objects, might be neutered+mutated deal with C++), and perhaps sldb
ascii_butugychag: was trying to describe the ~idea~ to n00bz.
adlai: slime is a massive turd, most of which is totally irrelevant for shiva (unless bitcoin-os is planned to serve as yet another example of Greenspun's 10th)
adlai: slime's repl and inspector contribs are the most relevant bits
ascii_butugychag: phf: precisely what i did. see the code.
phf: is the approach to spin up thread/socket on trb side? current "telnet" could be extended to swank protocol
phf: there are slime backends for schemes, the one for mit/scheme locs 800, but probably includes inspect and support for restarts, which are not needed for poc
ascii_butugychag: (sussman and abelson were the creators of scheme, authors of sicp, and taught the course)
ascii_butugychag: marking the permanent end of mit
ascii_butugychag: he wrote a formal letter of surrender to the rot
adlai: ascii_butugychag: might be smoother sailing to start off from comint-mode and work upwards, rather than trying to fit slime onto so different a backend
assbot: Logged on 29-01-2016 11:31:05; punkman: ideally turdatron would press all the possible HEADs and let us see them in lxr
adlai: maybe they didn't use the words 'fungible' and 'cog', but it was justified as what junior devs need to pass interviews
adlai: this was literally their justification
mircea_popescu: look at the statues, entirely different people.
mircea_popescu: this is like saying that the nignog "egyptians" abolishing the pyramids is "something they created"
mircea_popescu: not "they".
mircea_popescu: (different field, but same principle - you to this day can't beat literature as read at oxford cca 1880ish, just like you can't really beat it from mit cca 1960. the latter branch is obvious here, but the former'd be just as obvious in a literature-powered ba)
ascii_butugychag: adlai: 'a slime' in the sense of plugging an emacs session straight into the interpreter, with 'eval-region', 'eval current sexpr', as well as separate pane with repl, etc.
mod6: thats the one 'eh. thx guise.
ascii_butugychag: sicp is THE b00k.
adlai: ascii_butugychag: yes, i've been following along quietly. not sure what you mean by "a slime", literally interpreted this is rather meaningless as most of the swank-backends is highly CL specific stuff... i guess you mean a less literal interpretation :)
adlai: mod6: you're already making lisp jokes, even if you don't get them yet!
ascii_butugychag: mod6: fortunately it is the world's simplest, possibly, usable language
mod6: i've gotta take a crash course in scheme very quickly or I won't be able to make heads or tails out of these code submissions. eek!
gribble: The operation succeeded.
ascii_butugychag: (this is mentioned obliquely in the shiva.cpp commments)
mircea_popescu: in other sexpr news, http://36.media.tumblr.com/d4910e319712ed64e6a0d1be330bb652/tumblr_nva2x0Ofxa1uxo5jwo1_1280.jpg
mircea_popescu: <ascii_butugychag> ideally a vtron ought to be able to apply ANY well-defined operation << quite this, tho we might have to get there in steps.
punkman: ascii_butugychag: how would we shorten the retabbing?
mod6: as far as comments in the vpatch that are mearly just for archaeological or annotative purposes, i think something could be done here especially when we get our own diff/patch.
ascii_butugychag: shave half of face, submit patch, shave other half, etc
mircea_popescu: yeah, there is that.
mircea_popescu: you do a miserable job of comments, btw. the thing with "only four bit state" has its disadvantages.
mod6: not to worry about your signed genesis tho - i gardened it out. the mirror just has the right one.
BingoBoingo: <ascii_butugychag> thestringpuller: sacrifice a goat to satan << It's heretic apple, gotta sacrifice satan to a goat since woz is gone.
ascii_butugychag: but in point of fact, the v-chain aspect prevents a mistake from catastrophically breaking the world