100200+ entries in 0.822s

mircea_popescu: asciilifeform
i follow the theory of it, or else
i'd be covered in liver spots.
mod6:
I suppose that makes sense that parts could be re-written async ... ^ this right.
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:
i mean something peculiar. not of the thing itself, but of the effect it has on heads.
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"
mircea_popescu: mod6 "ideal Bitcoin", ie the 2nd thing.
i dunno just came up with it
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: 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.
davout: either way,
i'm going to bed, it's late here
mod6:
i need to make one for a d16
shinohai: Also BingoBoingo thanks for preserving the "Shapeshit" spelling as
I intended.
mod6: why was that so hard?
i think the example is maybe just not very well, um, explained?
i dunno
mod6: oooh,
i get this decision table now. if r1=4, r2=6, r3=3, then
i yield a final value of 2.
shinohai: After Birthday celebrations tomorrow
I shall drink no more for a while.
BingoBoingo: asciilifeform: sbp:
i recommend drinking less - srsly, it worked for some of the folks here... << That step 1
trinque:
I learned recently that the "inventor" of ruby is a japanese mormon
mod6:
i'll just write one up tonight.
i just tried to cheat a bit by using this one.
mod6:
i'll probably just re-write it in perl. sigh. fucking hate python.
mod6:
i guess it's just the same thing with more values, just was going to try to mod this guys shit to see if
I did it right so
i dont shoot myself in the face
mod6: cause really,
i don't care baout the d6,
i need to invent the table for d16
mod6:
i actually don't care /that/ much. im trying to wrap my brain around the truth table for the d6, with three rolls.
trinque: ah shit what was it,
I just did it
mod6: yeah.
i dunno anything about python, or even how to really run this thing properly.
mod6: best
I can seem to get is this:
mod6:
i need someone to help me turn this into something that works:
mircea_popescu: mod6 btw, dun ask to ask!
i dunno python that well, but mebbe if
i knew what you needed ?
mod6:
i was just pointing back to last weeks conversation about the nature of a coin. a float, 'tis not. :]
mircea_popescu: but yes
i think end of tunnel is right. by now we're discussing bitcents, it's pretty well pinned down.
davout: ok,
i'll go for checking the DB then
davout: but
i guess
i'd have to double check against the actual data
i have in the DB, might as well go and find the information there directly
mircea_popescu: Bet started:1 month 4 days ago (11-03-2016) <<
i think p
davout:
i can simply compare the minimum bet timestamp for each proposal with februart fouth
davout:
i see the end of the tunnel
davout: in other words, for every bet that was seeded after the jan. report
i owe you .1 btc
davout:
i did not say 'liability to bitbet', did
i?
mircea_popescu: davout> thing is
i can't simply do 0.1 btc * number of outstanding bets because some of the house bets expenses have *already* been accounted against the shareholders << how and where ?
davout: so basically my point is that while
i'm ok to add a bitbet liability to you for every bet that was seeded after the january report, every house bet that came before that was already paid for by the shareholders
davout: thing is
i can't simply do 0.1 btc * number of outstanding bets because some of the house bets expenses have *already* been accounted against the shareholders
davout: mircea_popescu: so
i'm in the process of updating the report
trinque:
I've yet to go back and make all the queries case insensitive
trinque:
I'll join the other one for now, but will probably get the above going this evening.
trinque: ah
I didn't release that code yet then
felipelalli:
I didn't mean to be rude,
I'm sorry. You can ask anything and
I'll asnwer, feel free! :)
felipelalli: this contract is fine to him (my counterpart "Rhama Bonitao").
I do not run any risk because
I get him service first. So, the worst scenario is if
I do not pay him, and he has a concrete proof that
I promised to pay him. It works,
I did it many times before.
mircea_popescu: well if you happen to read portuguese it is obvious from the deed he does so grasp it,
i thought.
mircea_popescu:
i sleep with women without giving them fingerprint tests!
felipelalli: shinohai, that's why
I asked what is going with "that" deedbot- :)
a111: Logged on 2016-04-14 16:00 trinque: phf:
I have not been collecting logs in postgresql because
I thought you were going to handle it
sbp: must dash for a bit—in case
I lack the +v upon my return, it has been a pleasure. thanks for the chat
sbp: it's the most Loper-like thing
I have seen outside of Loper
sbp: or vice versa,
I forget. maybe both
sbp: don't, you'll give me nightmares. worse ones,
I mean
sbp:
I dunno man. turtles all the way down, and
I don't trust any of them
sbp:
I suppose there's always the FPGA route
sbp: yeah, even if you took a batch and decapped all of them but one,
I suppose you wouldn't know for sure that that wasn't the exploited one.
I don't know if it's possible to make a chip that you can audit before it's running
sbp:
I could certainly accept uncompilable fexprs as being an expression of rubbish hardware though
sbp: Wand and Shutt kept arguing about whether Shutt's expansion even worked, and
I don't know the outcome of that. but let's say that Kernel (Shutt's language) does work—it's syntactically somewhat unwieldy. typing the fexprs to the arguments is very clean and easy to follow
mircea_popescu: or what exactly is the purpose here,
i dun rightly follow.
sbp: well, that is intended to be the compiler target of course. but
I haven't finished that yet
sbp: nope,
I started working on the bytecode stuff straight after that
sbp:
I saw something recently where they gave people a belt, and it buzzed in whichever direction was north, to give them haptic feedback as to cardinal directions. they seemed moderately annoyed to indifferent about the belt when wearing it,
I recall