--- Log opened Sat Mar 30 00:00:12 2013
09:51 < HM> there's a discrepency in the rpc implementation
09:51 < HM> HTTP not authorized returns HTTP/1.0
09:51 < HM> all the requests are HTTP/1.1
09:51 < HM> not that it really matters, since it's not a real http server
09:52 < HM> fixable though
20:45 < jrmithdobbs> why wont startcom issue me a cert with STOPUSINGTHEFUCKINGCNFORVALIDATION as the cn and proper subjectAltNames set?
20:45 < jrmithdobbs> damn it
20:46 < jrmithdobbs> wanted to try and break stuff using the public pki but need a ca who follows the letter and not the spirit ;p
23:37 < realazthat> sipa: ping
23:38 < sipa> pong
23:39 < realazthat> is there somewhere I can set this up so you can see the results
23:39 < realazthat> like a machine with bitcoind
23:39 < realazthat> (I'm just starting on the actual display of data)
23:43 < sipa> realazthat: post a screenshot? :)
23:43 < realazthat> well its just simple data for now
23:43 < realazthat> what features of blockexplorer do you want me to replicate
23:44 < realazthat> for now I started with the "Most recently mined blocks in the bitcoin block chain" table
23:44 < sipa> i think a block-view that lists transactions, and a transaction-view that shows inputs/outputs of a transaction would be nice
23:45 < realazthat> ok, I'll continue with that
23:48 < sipa> a block-view that needs to request all inputs of all transactions would be quite slow i think, so maybe have that optional
23:49 < realazthat> well it can link to them
23:49 < realazthat> hmm, I'll see how slow it is
23:49 < realazthat> it is indeed slow to do many requests atm, because I am dumping the i/o
23:50 < realazthat> but if I stop that, I'll see how fast/slow it is
23:50 < realazthat> if its a local bitcoind, it might not be so slow
23:50 < realazthat> if it isn't local, then yeah its prolly gonna be slow
23:50 < realazthat> I have my bitcoind running on a lan atm
23:51 < sipa> right, but to compute for example the fee of a transaction, you need its inputs
23:52 < realazthat> ah
23:52 < realazthat> so that multiplies the amount of things you need by a lot
23:53 < sipa> yes, that's why i'd suggest not computing that by default for a block
23:53 < sipa> but for example have a button "show fees and inputs"
23:53 < sipa> that fetches the expensive version
23:53 < realazthat> yeah ok, I'll see
23:53 < realazthat> lots of design wiggle room here, and I'm not 100% sure of the rpc API yet
23:54 < sipa> hmm?
23:54 < realazthat> for example,
23:54 < realazthat> I could cache that in a db
23:54 < sipa> i wouldn't do that; at least not initially
23:54 < realazthat> or, delay that field in the table, and have it fetched
23:54 < realazthat> yeah, I am trying to KISS
23:55 < realazthat> so if its hard, for now I'll just leave it out
23:55 < realazthat> wrt API, for example, I don't know how to compute block size
23:55 < realazthat> which is listed in the blockchain.info's table for last k blocks
23:56 < sipa> i wouldn't mind adding that to the getblock RPC call, if it isn't there already
23:56 < realazthat> also, did you notice, block 228851 took > 1hr to compute >OO<
23:56 < realazthat> is that common?
23:56 < sipa> yes
23:56 < realazthat> ok, a lottery with a lot of deviation :D
23:56 < sipa> standard deviation is 10 minutes
23:56 < sipa> but it's not normally distributed
23:57 < realazthat> ok
23:57 < realazthat> also, I am not gonna work on making it fancy at all for now
23:57 < realazthat> no CSS etc.
23:57 < sipa> ACK
23:57 < realazthat> just basically tables of data
--- Log closed Sun Mar 31 00:00:13 2013