log☇︎
309400+ entries in 0.191s
mod6: not that its useful, just was curious if anyone else saw it
mod6: played with it for an evening or something. this was like right around the time of the contest.
mod6: I think it would encrypt a string. Then decrypt it, but it wouldn't/couldn't take any different input. haha.
mod6: It was abomitable, though.
mod6: I got it to work, kinda sorta.
mod6: anyway, did anyone else rip off that guys Perl CS implementation from his university paper and get it to work?
mod6: Next friday checkpoint at the latest. Even if it's just a quick update.
mod6: I'll start putting this together, let's check back in on where I'm at say, mid-next week.
mod6: I think this is a good stopping point for today probably. Plenty of food for thought. Getting the list together is a small enough chunk to get us started.
BingoBoingo: in case of fire, and during the last drill (my building is only four stories for fucks sake) an obese coworker was out of breath and had to stop half-way with a huge line of people behind her - if this was a real emergency, I'm sorry, but I'm gunna gunt punt that woman to ensure everyone can make it out alive." https://archive.is/7ObHD
BingoBoingo: Iterlude from the mines: "During the 9/11 attacks, more people died than should have because the obese people in the buildings could not move down 20 flights of stairs as fast as needed. FACT. Obese people moving slow (as fast as they can) in a burning building stairwell absolutely can cause people to not make it out alive. This is the most triggering one for me. I'm one of those people who volunteered in my office to help people escape
mod6: This is something that ben and I can put together.
mircea_popescu: impossible to organize activity otherwise ; or for that matter to maintain any semblance of discipline or morale.
mod6: <+mircea_popescu> i guess one good move, and very foundation-like, would be to make lists of what we want, both for cB [cleanning Bitcoin] and iB [ideal Bitcoin] << ok so this is a start.
mircea_popescu: anyway, making a list of all the things seems paramount
asciilifeform: then i went off into my pit to produce a cstron.
asciilifeform: we settled, iirc, that whoever shows up with ~working~ widget, gets the prize.
mod6: oh, thought that you got the 10 BTC?
asciilifeform: because it is not time.
asciilifeform: mod6: i must point out that i was not paid
mircea_popescu: of course, the discussion re cipher composition is herein included by reference.
mircea_popescu: i don't know there's a better alternative than cs.
asciilifeform: (the utter inefficacy of all of the padding schemes, hence cs)
asciilifeform: there is the one thing.
mircea_popescu: i don't think there's anything wrong with proper, full rsa (as opposed to the neutered version implemented by pgp)
asciilifeform: would help also to nail down the exact cryptomechanics of a viable 'iB'
mircea_popescu: something beyond the very summary skeletons discussed in chat prior and even further summarized above.
mircea_popescu: i guess one good move, and very foundation-like, would be to make lists of what we want, both for cB [cleanning Bitcoin] and iB [ideal Bitcoin]
mod6: anyway, this seems to make some stategic sense to me.
mircea_popescu: and as the idiots keep investing themselves, no matter how ineptly, they'll eventually build a shitpile large enough, i suspect.
asciilifeform: i recall this. it is rather like 'cruiser aurora', bottom - is of cement
mircea_popescu: asciilifeform mpb is creaking at the seams.
mircea_popescu: if we are in a position to say "we don't want a fork - but if you do, THIS fork will prevaly, no matter what you do, because it actually is the tech schelling point" then that's the end of that.
asciilifeform: my understanding is that this role, to the extent it was filled by anything, was previously filled by mpb.
mod6: So, we build a new battleship, and keep it in port. This will make 'em bleed through the purse.
mircea_popescu: mod6 like i pointed out to davout in the middle of that heated discussion re how things work, this is one of those things that deal with the negative of "works"
asciilifeform: (not all are interesting to all folks)
asciilifeform: and did not bother to describe all of them here
asciilifeform: in the past i referred to such items as 'parachute'
mod6: yeah, i think so.
mircea_popescu: mod6 you follow the logic here ?
mircea_popescu: so in this sense, active development of an iB is actually useful beyond its use.
asciilifeform: sorta the 19th c. variant of the specificity-of-diddling thing.
mircea_popescu: it's a basic approach to leveraging local superiority into actual total value.
mircea_popescu: \this can end up costing, by the end of the war, way the fuck more than their battleships were wortjh in the first place.
mircea_popescu: they have to keep accounting for your potential activities. hence the "in being" part.
mircea_popescu: instead, you keep your battleship in port. this ties down the enemy, and they can't go about doing their shit normally
mircea_popescu: you have created this situation when the enemy has one... relatively infinitely large battleship.
mod6: "In naval warfare, a "fleet in being" is a naval force that extends a controlling influence without ever leaving port."
mircea_popescu: ok, it's a concept from maritime strategy, that meanwhile took over mainstream. the idea is that if you have one big battleship, and the enemy has three, you are ill advised to go into battle. because if you sink two, and they sink yours
mod6: yeah, i read about this before.
mod6: Then, i think my initial still holds. Short term C releated work, if it can even be done in time. And meanwhile, new icecream replacing dogshit.
asciilifeform: the one risk is that folks might get carried away with the 'belts and suspenders' and write some very slow code (where there are type predicated on everything, etc.)
mircea_popescu: practice is always its own thing tho. we see.
mircea_popescu: asciilifeform i follow the theory of it, or else i'd be covered in liver spots.
mod6: sort of like we were talkin about with Scheme, etc. ☟︎
asciilifeform: mircea_popescu: considering that ada uses no peculiar ('functional') abstractions, and is pretty much a c with 'bdsm'-restrictive pointer mechanics and hard bounds checking - the nock thing is not in the mix
mod6: I suppose that makes sense that parts could be re-written async ... ^ this right.
mircea_popescu: and then gradually push shit out.
mircea_popescu: mod6 that was the major point , that they are miscible. very rarely you get so lucky, that you can add icecream to shit,
mircea_popescu: the haskellweight of a project, how likely it is to suck brains and ideas into a black hole of nock.
mod6: Ok, so i had to re-read all of that so im finally caught up here.. i didn't even consider interleaving ada with C really. i dunno why, i was just thinking it would just be its own separate deal.
mircea_popescu: of that particular kind. yes.
asciilifeform: ah you were thinking of complexity collapse.
asciilifeform: it builds to a traditional binary, like any other gcc.
mircea_popescu: i mean something peculiar. not of the thing itself, but of the effect it has on heads.
asciilifeform: there isn't, note, a haskellian runtime in the thing
asciilifeform: mircea_popescu: what'd that look like ?
mircea_popescu: of course the less nifty thing is that whether this entire pile actually works or collapses under its own haskellweight is an unknown.
asciilifeform: the nifty thing is that ada standard specifies own scheduler.
asciilifeform: next thing will be to port my rtlink nic driver to ada (with minimum of asm)
mircea_popescu: with any luck, all the way to verilog.
mircea_popescu: so yeah, ada is certainly a good thing in that pot.
mircea_popescu: what, whne you were raving about ada the specified, what did you think i read, exactly this, "oh, he hopes and wills to make the whole chain"
asciilifeform: objective is to let go of the whole shitstack.
mircea_popescu: what the fuck else was the incentive there.
asciilifeform: console i/o to serial (emulated, presently)
mircea_popescu: asciilifeform to no one's surprise.
mircea_popescu: mod6 "ideal Bitcoin", ie the 2nd thing. i dunno just came up with it
mircea_popescu: there's also - a good db. and other things. a list should prolly be made.
mircea_popescu: anyway, back to the iB : there's a number of very valuable ideas, at least in my eyes, that discussion throughout has brought out. yes the sha thing discussed on trilema ; also - ada, linked into the c, and slowly driving out the c, much in the way the vermin try to drive out say x11 or rsa etc.
asciilifeform: but we could go on re this forever.
asciilifeform: ah that rat.
mircea_popescu: there's a reason why the sort of guy that can't pass the simplest test of manhood, that pons asinorum known as the prisoner's dilemma is known as a rat.
mircea_popescu: for this reason tho.
mircea_popescu: (yes asciilifeform, "captive by local minima" is not the definition of adulthood, or of civilisation. it is the definition of rat.)
mircea_popescu: in the sense that the incentives of the vermin are modified by its projection. vermin being definitionally captive subject to incentive potential.
mircea_popescu: in this sense, a good iB in back pocket as you say plays the strategic role of "fleet in being", in that it protects the old shit from too violent a crisis.
mircea_popescu: the other's very practical : every halving is a difficult time for bitcoin. it's a more or less homeostatic structure, which means that with some periodicity will go into crisis. you don't know what crisis will rupture a vessel and give it an aneurism, but it is indubitable that the quality of alternative on offer is the best measure of its lfie expectancy.
mircea_popescu: well, there's two classes of arguments pro iB that i can readily see. one's very fundamental : the code is shit, the "grandfather pistols" thing will only go so far, it is by its nature finite in utility. eventually the trhing will have to be redone well. it is, after all, a misuded prototype.
mod6: as Ada. We've all kicked it around a bunch about the lang, and I'm not sure we're all sold on Ada. But seems like a step in the correct direction overall.
mod6: so i guess there are short term and long term initiatives: Short term (for this summer, 12 weeks from now) it might suit us well to have a SHA3 bitcoin in our back pocket. And with some mapped/planned out work there, would still be a long shot, but possible, I suppose. Long term (1+ year or more?), concurrently there could be work towards an actual hardfork with an ideal bitcoin written in something, such
mircea_popescu: but you know, i think blind enthusiasm has carried us about as far as it will ; moreover, everything has its time and place.
mircea_popescu: the other point, whatever may be decided on the previous point, is to make some sort of roadmap or even ideally graph of parts and then see who can do what and so on
mircea_popescu: so one thing is you know, to come to some sort of decision on what to do there. strategy-wise, as it were.
mod6: But starting might just be half the battle. We'd have to go through a process of perhaps identifiying first, where to swap out SHA2-256 for SHA3-512. (whatever needs to be included, what structures and fields need to be lengthened, etc)
mircea_popescu: mod6 well one major question to be decided is : obviously there's the project of cleaning up extant bitcoin code ; by the discussion re july of forks, there's also the proposal to start a separate project to make an "ideal bitcoin". this proposal wasn't ever seriously discussed and i dunno that it ever was actually accepted as such.
mod6: I personally have hardly even begun to look at what/where/how these code changes would need to take place in the current cod.
mod6: If we basically just tagged bitcoin in V as is today, then we could possibly start working on the implementation of the prereqs above.
mod6: Anyway, so i was re-reading through http://trilema.com/2016/the-necessary-prerequisite-for-any-change-to-the-bitcoin-protocol/