Matches for spec, 583 total results Sorted by newest | relevance
Thu Jul 09 01:34:18 UTC 2015 <decimation> well, if that were a hard spec I would agree, need txco or ocxo
Tue Jul 07 02:21:34 UTC 2015 <mats> trinque: spec calls for displaying stats, which would probably require caching because pgsql reads from disk otherwise
Sun Jul 05 02:40:25 UTC 2015 <decimation> now, as I pointed out with midnightmagic, it strikes me as backwards to develop a replacement before describing a spec
Sat Jul 04 06:17:40 UTC 2015 <decimation> ideally, writing a damn spec first
Sat Jul 04 06:16:59 UTC 2015 <decimation> his code sucks, I don't deny, but it's the closest thing to a spec that we have
Thu Jul 02 21:27:42 UTC 2015 <decimation> ^ from source package (.spec)
Wed Jul 01 17:48:51 UTC 2015 <mircea_popescu> because we live in the best possible world built on top of !!!science!!! so nothing is ever sold by any sort of spec.
Wed Jul 01 16:06:16 UTC 2015 <mircea_popescu> http://log.bitcoin-assets.com/?date=30-06-2015#1181585 << there is something in the entire "cutting off nose to spite your own face" thing. absent this, the pissant has no incentive to uinderstand it is a tiny spec, and may even pretend itself equal to every other asshole out there.
Sun Jun 28 04:48:42 UTC 2015 <asciilifeform> and anything purporting to be a human-readable spec is necessarily incomplete
Sun Jun 28 04:48:26 UTC 2015 <asciilifeform> decimation: unless i seriously misunderstood mircea_popescu, not only is the reference client the permanent spec, but so are the turdependencies
Sun Jun 28 04:47:32 UTC 2015 <decimation> well, it seems to me that there ought to be a definable spec between "talk to peers" and "maintain database of blocks"
Sat Jun 27 21:17:37 UTC 2015 <pete_dushenski> asciilifeform: the ibmpc buildroot sounds like a spec for the 'trilema jobs board'
Thu Jun 25 17:34:01 UTC 2015 <kakobrekla> but thats china spec
Sun Jun 21 17:32:12 UTC 2015 <asciilifeform> mod6: lowest level of the bitcoin spec - order in which fields go in message, their contents, etc
Fri Jun 12 21:51:47 UTC 2015 <mircea_popescu> that's all i care to know : what portion of the spec is not implemented correctly.
Fri Jun 12 20:59:59 UTC 2015 <ascii_field> decimation: where's the 100% open spec ?
Sat Jun 06 14:55:00 UTC 2015 <mircea_popescu> you spec an order of boards meanwhile to be ~1k
Fri Jun 05 05:26:15 UTC 2015 <trinque> reason being, should you specifically define it, you may find there is no existing device that meets the spec
Wed Jun 03 13:48:37 UTC 2015 <mats> fun fact: creators of the BLE spec published it with known vulnerabilities, e.g: "None of the pairing methods provide protection against a passive eavedropper during the pairing process as predictable or easily established values for TK are used." (BLE Core 4.0, Vol.3, p604)
Sun May 31 12:23:34 UTC 2015 <mircea_popescu> http://log.bitcoin-assets.com/?date=31-05-2015#1148879 << this is a complicated problem, in part because the spec isn't terribru good.