41600+ entries in 0.851s
mircea_popescu: kakobrekla i don'
t rightly understand what this midway solution actually is. so if l1 is empty, then how is l2 defined. and if l1 isn'
t empty then... what ?
mircea_popescu: i'm about as interested in participating in democracy of any kind or description as you can imagine. #b-a existed to any degree and in any sense for as long as it wasn'
t that. it can go back to being #okcupid or whatever the fuck else the "power of the people" warrants.
assbot: Logged on 23-03-2016 23:35:36; mircea_popescu: i dunno, but the fact remains this nonsense can'
t continue, if for no reason then because i won'
t be any part of the most recent attempt of fiat world to reclaim the republic. so for the sake of variety, let's go with : kakobrekla, you willing to take nubbins off the l1 ?
mircea_popescu: i dunno, but the fact remains this nonsense can'
t continue, if for no reason then because i won'
t be any part of the most recent attempt of fiat world to reclaim the republic. so for the sake of variety, let's go with : kakobrekla, you willing to take nubbins off the l1 ?
☟︎ mircea_popescu: mk, so upon consideration, the issue here is that me nulling the logs is at best a stopgap, and no sort of long term or tenable solution. there's certainly no sense in me continuing to pour words into a bag i won'
t read the logs of, wtf.
jurov: mrottenkolber: it's fine, as long as this won'
t cause V to take up complexity from git
jurov: i just can'
t run business that way
punkman: nubbins`: i actually didn'
t realize mp owned assbot << I thought kakobrekla owned assbot
nubbins`: don'
t get me wrong, holding mp's feet to the fire is a good lel
fluffypony: nubbins`: I've added you to my Official 2016
T-shirt Printer List
nubbins`: whether he comes, goes, ignores me, shuts down his companies, erases his little lords list, w/e. don'
t care.
nubbins`: i actually didn'
t realize mp owned assbot
jurov: we're not splitting,for most people here this discussion isn'
t enough to get nuclear
jurov: trinque you aren'
t at least rubbed the wrong way by mp's approach?
trinque: I couldn'
t agree more with that.
jurov: and i actually mentioned the "good faith" question like 3 times in two days. and i don'
t like to repeat myself. were not for hanbot, it would be well safely buried in the logs by now.
mircea_popescu: that doesn'
t result in better security, but does result in more complex rabinic arguments down the road.
mircea_popescu: yes but you can'
t simply be argued out of a position then come back with it two hours later.
danielpbarron: sure it doesn'
t fit in with your retro-actively claiming the double payment was actually a partial early payment of other bets..
jurov: well, then i utterly don'
t get it
danielpbarron: no reason it shouldn'
t be. the above proposition fixes a non-problem
PeterL: is it really that much bigger than the current version? don'
t they already do all payout in one txn?
PeterL: jurov, wouldn'
t it be easier, rather than doing two transactions (sweep, then distribute) to just do a single? (bets are used to pay winnings, the 1%fee to a bbet company address)
assbot: Logged on 23-03-2016 18:59:09; davout: asciilifeform: do you agree that, if the 17 btc mp sent a second time aren'
t billed to bbet, it follows that this second transaction can'
t come in deduction of bbet liabilities to bettors/addresses?
assbot: Logged on 23-03-2016 19:12:27; nubbins`: doesn'
t put enough forethought / planning into things
davout: jurov: aren'
t gas and ether two different things?
nubbins`: doesn'
t put enough forethought / planning into things
☟︎ davout: trinque: see previous comment, approval was usually expressed after the fact, until it didn'
t davout: asciilifeform: if claims are against addresses you can'
t assign intentions to them!
davout: asciilifeform: do you agree that, if the 17 btc mp sent a second time aren'
t billed to bbet, it follows that this second transaction can'
t come in deduction of bbet liabilities to bettors/addresses?
☟︎ nubbins`: trinque your argument is: the public doesn'
t get to lambast those who do poor business?
davout: jurov: X is a slippery slope isn'
t a valid argument for anything
nubbins`: asciilifeform so why didn'
t bbet monitor payout addresses, and cancel any payments to wallets which received funds from any source after bet resolution?
nubbins`: you don'
t get to claim a third party handing me cash as your own payment.
PeterL: nubbins` what if MP was travelling when bet resolves, pays somebody to send txn to bet winners, do those payments not count because they don'
t come directly from bbet wallet?
nubbins`: you can'
t analogize what happened to what didn'
t happen
assbot: Logged on 23-03-2016 12:29:04; asciilifeform: and yes, they had no obligation to send it back, etc. but if they had, there would be no reactor fire, and a still-operating bbet. that isn'
t about to be auctioned off to spammerz.
davout: so it won'
t be an issue will it?
mircea_popescu: i recommend blindness, because i fucking well aren'
t going to be supplying all the candles now required or in the future needed to look in all possible or conceivable dark crevices ; nor do i see who ever could.
mircea_popescu: that wasn'
t a wound, it was on the contrary, the closing of a gap
mircea_popescu: the cold truth of the matter being, of course, that bitcoin's an imponerable that obviously can'
t be cut. but when you, the sleeping butterfly that dreams himself lao tzi, in your dream believe to have cut into it,
mircea_popescu: is the man who doesn'
t drive across town to buy milk a dime a gallon cheaper a communist ?
mircea_popescu: atm i can'
t see that it is and dunno how to completely argue it isn'
t.
assbot: Logged on 23-03-2016 14:06:24; mircea_popescu: anyway, take it from a software design perspective. you are proposing to change the stateless parser (bet accepted) -> (bet resolved) -> (bet paid out) into a stateful and undefined (bet accepted) -> (bet resolved) -> (???) -> (some thing paid according to some rules you can'
t know)
mircea_popescu: man and woman also suck equally, one has the children the other doesn'
t.
mircea_popescu: bitcoin addresses aren'
t acceptable proof of identity (such as for instance through that "signing" kludge) specifically for this reason.
nubbins`: asciilifeform the 13.37 haircut is baked into the deal, i don'
t think any other haircuts are?
mircea_popescu: asciilifeform not the issue. the issue is, can you assume or can'
t you assume. and the result is you can'
t assume.
assbot: Logged on 23-03-2016 12:03:12; BingoBoingo: Aha, I knew it would happen, but I didn'
t know it would happen this early. The reciever is now burdened with CHOICE.
solrodar: didn'
t those ideas come from your sense of justice, equity or whatever you call it?
mircea_popescu: fine, if you must : your question is not even a question in that it doesn'
t make any sense.
mircea_popescu: davout it worked, that time, but i wouldn'
t rely on it!
nubbins`: <+solrodar>since the sender never intended to transfer ownership to that person <<< mp didn'
t intend to transfer ownership of the coins involved in a tx that he sent?
solrodar: mircea_popescu: the bettors entered a contract with bitbet, then you, acting on bitbet's behalf, paid them too much by mistake. Even if there's no property in bitcoin, doesn'
t the existence of that contract allow you to introduce an argument of unjust enrichment?
mircea_popescu: anyway, take it from a software design perspective. you are proposing to change the stateless parser (bet accepted) -> (bet resolved) -> (bet paid out) into a stateful and undefined (bet accepted) -> (bet resolved) -> (???) -> (some thing paid according to some rules you can'
t know)
☟︎ davout: mircea_popescu: you haven'
t provided any support for the notion of "a fellow" that you introduced, or did i miss it?
solrodar: mircea_popescu: aren'
t you the one that always argues that there are no people, only keys? In which case there's nothing wrong with recovering money from keys. If the key is controlled by multiple people, that's their problem.
mircea_popescu: which is, seal things in the past in such a way they aren'
t revisable in the future.