00:27:50 Fistful_of_AFK is now known as Fistful_of_LTC 04:26:20 PT Mono may be the best programming font of all time 04:26:36 even ugly template code looks pretty 06:46:20 http://www.quora.com/Distributed-Systems/What-does-a-career-in-distributed-systems-feel-like-In-terms-of-the-kind-of-programming-you-have-to-do-nature-of-bugs-or-issues-work-life-rhythms-etc/answer/Bram-Cohen?srid=CW&share=1 interesting comments 06:46:44 "Then I run into... how to put this... barriers to commercialization which don't apply to most products. 06:46:44 " 06:46:53 I think he means lobby money....... 16:31:31 hola. so I need to tell Gavin about a possibly-schizophrenic stalker that seems to be targeting him. does anyone have a real contact email for him they wouldn't mind giving me? (given the nature of the issue I'd prefer to tell him sooner rather than later) 16:55:43 anyone? 16:55:44 alright, whatever, I'll just use 16:55:44 gavinandresen@gmail.com 16:55:44 it *probably* isn't a real threat, after all 16:56:06 gwern has left #bitcoin-wizards 17:01:34 gweIs that somehow a non-real contact email? 17:01:47 :-/ 17:01:58 combination if the user leaving and lag eating keystrokes 19:38:44 Hi guys, any feedback on this idea would be appreciated: https://bitcointalk.org/index.php?topic=365392.msg3900881#msg3900881 21:15:08 chilero_ has left #bitcoin-wizards 21:42:08 andytoshi: maaku: phillipsjk gave an attack on multiparty CJs that either I hadn't considered or I considered and forgot. https://bitcointalk.org/index.php?topic=279249.msg3982242#msg3982242 21:44:01 adam3us: good criticism on the 32bit keyid on card 21:51:47 gmaxwell: thx, i'll check it out 21:52:07 and agreed, i am not going to distinguish between fee and donation 21:52:16 if people don't trust me, they can verify the transaction themself before signing 21:52:46 unfortunately "andrew stole all the fees" and "somebody put a ton of inputs in without paying a corresponding donation" will look the same.. 21:53:54 ah, that is essentially the phillipsjk attack 21:57:10 andytoshi: well it means that e.g. if two people pay extra fees because they want faster confirmation, you could be eating them anyways. 22:03:01 right 22:03:11 so i think, i'll do that always and be upfront about it :P 22:22:34 andytoshi: one somewhat annoying thing about the fee/donation stuff is that it makes it impossible to go from round inputs to round outputs. 22:23:39 andytoshi: hm. also, can you perhaps have some ajax reloader thing, and perhaps play a chime or popup an alert when its time to sign? 22:23:48 oh, sure 22:23:57 i guess i should whitelist my own domain on noscript.. :P 22:24:16 maybe just have it display a countdown... and when it hits zero. popup a window/play a beep. 22:24:41 I missed the testnet one I threw coins into earlier. :P 22:25:09 i think, i'll have the "there are XYZ seconds until whatever" displays count down everywhere, and i'll see about playing a beep 22:25:25 whenever i google for things like "how to play sound using javascript" the forum posts that come up are so sad... 22:26:05 fwiw, these never expire, you can F5 the 'sign.php?session=whatever' page for ever and ever 22:26:22 "Sorry, but this session has been invalidated. Probably there were not enough transactions to do a merge." 22:26:34 ah 22:27:00 that'll happen regardless of how closely you follow it, unless you submit multiple transactions yourself 22:27:10 maybe i should extend the window rather than invalidating transactions? 22:27:46 i don't want it to happen that somebody submits a transaction, nobody else does for a day or two, and then when finally people use the coinjoiner, it's got some forgotten transaction poisoning the pot 22:28:33 just document.write a tag... 22:29:02 yea, you don't really want a old transaction jamming it. 22:30:11 What you could do is split off the old pot and start a new pot. The old pot can still get more txn added, but only if someone gets directed to it by ID. 22:30:59 e.g. I could add a txn to the pot, and email you a link directly to the pot. and it fails because no one else adds... and 24 hours later you can add a coin to it, then it'll go into signing X time after. 22:32:05 yeah, that's a good idea, and it takes literally no code to implement.. 22:32:19 i just have to commend out the "set status = invalid" line in the cronjob :P 22:32:55 you might want to have it check if the inputs are unspent and set it to invalid if any of them are spent. 22:34:00 e.g. if I put a coin in, send you a link. Then you don't notice the email, and I give up and join another session .. and my coin is spent.. later when you load the link it won't invite you to add more coins to a dead one. 22:34:49 yeah, it should 22:35:14 there is code which does that before it switches to signing mode 22:35:20 (or even just: if a coin is spent, you remove it from the mix, and if the count goes to zero the mix is invalidated) 22:37:53 cool, done 22:38:22 i should also add code so that if outputs are spent during the signing phase, that also invalidates things 22:38:26 inputs* 22:41:53 just check on every load of the signing page, perhaps? 22:43:28 nah, the pageloads are handled by PHP, i'm trying to avoid doing any real work in there.. 22:44:36 i have a perl script which transitions to the next session, it does all the merging and validation checks 22:47:05 well, that's not true, when you submit a transaction PHP does a spot check 22:50:12 not critical, but checking there would save some time signing a doomed transaction. 22:55:45 i think i'll run the perl script every minute or two 22:56:05 it should really know how long a session is supposed to be alive.. 23:46:59 20.