3400+ entries in 0.094s
ben_vulpes: how does
phuctor know the key's been revoked?
mircea_popescu: phf yes, but a fine approach to answering "what is the basis of alf's value as an engineer" is pointing out that he runs
phuctor on the
phuctor box, which fails to cost 5k/mo.
phf: well, a more practical approach would be to adapt
phuctor c part to a postgresql loadable module interface. in which case you he will eliminate the cross-boundary overhead (serialize/deserialize over the "wire").
mircea_popescu: you're not addressing the idea. currently you use a pile of c code you labeled for purely personal reasons "a db" to store some data for you, and another pile, you labeled
phuctor, to bernstein and do other things on the db-stored data. because the interface is the bottleneck, it then becomes clear you must merge this. one way is to merge by lifting the db code and putting it into
phuctor, making it you know, its own db like
mircea_popescu: wich is why fs sql is contemplated for bitcoin, not really for
phuctor's woes.