1300+ entries in 0.713s
decimation: yeah the ds3231 has the same
spec for time performance
decimation: my reading of the
spec sheet is that combined aging and temperature stability (assuming 0-40C) would be about 8.5 ppm
decimation: asciilifeform: www.ebay.com/itm/INBOARD-RTC-DS3232-Real-Time-Clock-and-Temperature-Sensor-I2C-BUS-PIC-AVR-ARM-/120841157983 < hi-
spec part
decimation: well, if that's a hard
spec, and 'launch into space' is a hard
spec, the project is a failure
decimation: well, if that were a hard
spec I would agree, need txco or ocxo
mats: trinque:
spec calls for displaying stats, which would probably require caching because pgsql reads from disk otherwise
decimation: now, as I pointed out with midnightmagic, it strikes me as backwards to develop a replacement before describing a
spec decimation: his code sucks, I don't deny, but it's the closest thing to a
spec that we have
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.
decimation: well, it seems to me that there ought to be a definable
spec between "talk to peers" and "maintain database of blocks"
pete_dushenski: asciilifeform: the ibmpc buildroot sounds like a
spec for the 'trilema jobs board'
mircea_popescu: that's all i care to know : what portion of the
spec is not implemented correctly.
trinque: reason being, should you specifically define it, you may find there is no existing device that meets the
spec 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)
ascii_field: afaik it works great for 1+2 and therefore meets
spec mircea_popescu: (i have trouble recalling that whole
spec, which is one of the things that are fucking wrong with it)
decimation: yeah, they don't put that in the
spec, but who knows. if the supply is really efficient, it ought not generate much heat
mircea_popescu: mxtm we check implementations to make sure they're conformant to
spec.
assbot: Logged on 14-05-2015 16:14:04; jurov: i hope gossipd
spec has a part concerning this. otherwise it will be inevitably bolted on in some ugly haphazard fashion
jurov: i hope gossipd
spec has a part concerning this. otherwise it will be inevitably bolted on in some ugly haphazard fashion
☟︎ mircea_popescu: it seems like your browser supplies it somehow ? the source has no class
spec.
assbot: Logged on 11-05-2015 17:41:50; ascii_field: from standpoint of boobytraps, an example of 'worth writing home about' would be a machine 1) with pedantically open
spec, to transistor level 2) with provisions for tandemming with implementations of same by other, foreign makers
ascii_field: from standpoint of boobytraps, an example of 'worth writing home about' would be a machine 1) with pedantically open
spec, to transistor level 2) with provisions for tandemming with implementations of same by other, foreign makers
☟︎ ascii_field: from
spec sheet: 800MHz sparc-like; sata-2; 12 ddr3 ecc dimm slots; various standard i/o (e.g., pci-e, GbE;) and, most interestingly, built-in fpga for 2d interconnect into clusters by directly linking bus (202 G/s claimed.)
mod6: i was apologizing for the
spec dump.
davout: aha, not sure i ever actually *read* that
spec, is it trilema'd?
danielpbarron: you could do that, but the
spec is for it to have all necessary stuff contained in the unit itself
mircea_popescu: and this is also a fine entry point for explaining to management noobs the meta point of why exactly a theoretical approach doesn't ever work. yes, you could read the tcp/ip
spec and look for holes. those are the holes in the tcp/ip
spec, not the holes in tcp/ip.
trinque: tonight I'm going to work on it belching the deed URLs into chan when published, and I think that about wraps up the
spec mats: Fun fact: the BLE (Bluetooth Low Energy)
spec provides three key exchange mechanisms, two of the three which do not provide any passive eavesdropping protection
Pierre_Rochard: davout: I floated the idea last year - I’ve used a lot of different accounting software and never been satisfied - none of them use acccounting theory as the
spec BingoBoingo: <trinque> obviously, and so you're going to have every soldier cast the metal for his own gun? << Unreasonabru, but Officers outfitting their soldiers to the Officer's chosen
spec has ample historical precedent
BingoBoingo: mircea_popescu: Kludgy and bolted on to original
spec jurov: $10 is already a premium for that
spec williamdunne: mircea_popescu: I'll draw up a full
spec and be sure that I can do it (in terms of time) and show that to you. Good starting point?
williamdunne: Ah sorry, well it depends. Obviously its a pretty lose
spec but I'd probably go for something that has all the basic functionality built on a probably ASP stack, rather than doing anything too fancy with pretty colours everywhere
mircea_popescu: williamdunne actually i was gonna write a
spec, soi i guess brb
ascii_lander: and l0l, i don't even remember how to program any more (at least in the traditional sense where someone gives you a
spec & pays)
trinque: Citizenfive: read the
spec?
mircea_popescu: still testing to see what'll be minimum rec
spec, but anyway.
mircea_popescu: "Writing an empty stub is an extremely bad practice and should only be done in desperation, because at the urbit level it produces a system event log that is nonrepeatable, or at least noncompliant with the nock
spec. Discrepancies propagate rapidly in any kind of replay. You should be able to turn off all jets and get the same result. This is not practical, but it is practical if you disable everything but a few ba
nubbins` generally doesn't do design work on open-ended
spec mircea_popescu: asciilifeform basically, "the protocols of the elders of zion" is not an isolated product, much like the
spec of dust that has a light shone on just right isn't the only
spec available in the area.
jurov: ssl
spec is too complicated, hence inevitably buggy implementations
mircea_popescu: but if you imagine there's any room in the
spec of this thing for the end user to fiddle with it you're ourgiht nuts.
BingoBoingo yet to try .foundation build as
spec'd, mostly has moar weird in his plan pipeline
nubbins`: 30MB/s writes if it's up to
spec ascii_field: but can be inferred from the port layout and the chipset in the
spec sheet.
nubbins`: doing work on
spec where it has to pass through a single arbiter is /daft/
nubbins`: doign work on
spec is fucking nuts
Adlai: testing individual components to confirm that they meet
spec, soldering them onto the pcb
mircea_popescu: ah. the
spec doesn't change by the implementation yo. the other way around.
PeterL: trinque: the "social contract" of bitcoin is the "
spec" as laid out by satoshi in the white paper
nubbins`: i.e. places where there's wiggle room in the
spec, one zigs where the other zags
mircea_popescu: mod6 if you write a
spec or something ima read it, for whatever good that's gonna do
decimation: asciilifeform: I assume you saw the sudden freakout over hilariously weak crypto implemented by
spec in SSL?
gabriel_laddel: Not as easy as it sounds. Life is finite, as exemplified by MP not reading Al's experiment
spec, and Al not being MP
mats: as if Text Secure is usable, has a
spec or docs like opengpg, as if mailpile doesn't shell out to a gpg binary
thestringpuller: Adlai: drafting them to
spec is difficult sometimes. Like coming up with a good statement of work, or an SLA
BingoBoingo: <asciilifeform> since we're on the subject, could someone enlighten me re: how 'tinder' does anything once the counterparties meet in the flesh? << Not in its
spec. Hands this off to wetware
mod6: ok. no problem. just trying to get it down to a
spec decimation: there's another angle to the 'open source cad' thing: autocad refuses to release the
spec for their full-feature 'save' files