1323 entries in 0.628s
BingoBoingo: OpenPGP may be what the
spec is called now, but GPG seems to be the only implementation that matters.
bgupta: mircea_popescu: discussed previously? In IRC or elsewhere? (My issue with current implementations, is the key lengths they support are too short, but the latest version of the
spec seems to address that)
bgupta: Only issue I see with opengpg/gpg smartcards is that although the latest
spec supports 4096bit keys, the current shipping devices don't..
BingoBoingo: Fuck this is why Bitcoin needs a mother fucking
Spec.
jborkl: "KNC support just emailed me back saying that 440 ghash (what 50btc reports), 900 watts from the wall, and chip temps of 65-72c in a 58F room are 'within
spec'...Not awesome."
Duffer1: ya i saw that, they're really taking mining
spec scam to a whole 'nother level
fractal_: the unit must be > 400Gh, and < 400W.. the unit did not meet this performance
spec fractal: mp: if bitfury sehipped more hardware, they changed the
spec, and the bet was a yes..... you've contradicted yourself.
fractal: heres another bullshit sentence -- "credibly show their sample ASIC chip working to specification" what is the specification? what is the timestamp of the
spec? what if Labcoin changes
spec during the bet?
fractal: it failed to meet that
spec ozbot: BitBet - Hashfast will deliver ASIC devices to
spec before November 1st
Neil: Closest I've seen to a
spec is the wiki, and that's full of holes and exceedingly vague in places
Anduck: jurov: the "will ship their 25ghash and 400gash units in time".. if there wasn't any 400 ghash units ordered in the first orders... but it's been proven that it can be built (why wouldn't it be possible? just attach the cards) and it will meet the
spec Anduck: since it's proven that 400gh unit will meet the
spec fractal: Anduck: No, its not. The bet says nothing of a KIT. it says a mining unit. Somehing that is a single prodcut attacted..... 2 seperate products adding up to more then 400Gh mean that the manufacturer missed performance
spec for that unit
kleeck: Yes. What I'm seeing is the classic, "Oh come on, we all knew the intended bet!" Which isn't a sound defense. The debate must center around the words used to describe the bet. If the product is a "mining unit" and meets the
spec in the bet, then Anduck is correct, else fractal is correct.
kleeck: Are the assembled kits meeting
spec once made into a mining unit?
kleeck: So, they are getting kits instead of completed devices and those devices are meeting
spec?
fractal: Anduck: Shipping additonal hardware because the company missed
spec does not mean that there is a 400Gh UNIT
fractal: i'm trying to look at all the angles here. from what i read on the forums, it seems like punin himself has admitted it will miss
spec numbers.... i guess he can lose the 10BTC, probably making 1000's w/ bitfury
Diablo-D3: came out with ver 4 of the SD
spec kakobrekla: who knows how many times will they change
spec Diablo-D3: bobbabad: instead they're written against the
spec, and the
spec sucks
ThickAsThieves: hiding and reposting ask walls that were
spec'd in the IPO
mircea_popescu: i guess i made a confusing
spec originally in that i didn't correctly separate things for ppl.
ThickAsThieves: is this black edging some kind of shadow on the crest box or something, or just an awkward way to make your original
spec not wrong ;)
jurov: imho,
spec and scalability plan
ThickAsThieves: (Gavin Andresen) I don’t foresee us formally creating a
spec within the next year … actually really at all. There are so many things to work on, I would rather spend time actually developing the code than creating a
spec.
ThickAsThieves: What is your opinion of libbitcoin, and are there plans to create a formal
spec for Bitcoin?
sikbwoy: looking for marking making opportunities on emerging BTC exchanges
spec ASICMINER options
dub: which is, of course, no
spec dub: obviously for any future bets the
spec those order holders agreed to last week applies
dub: inhies: fwiw the advertised specs wrt that bet are obviously the initial
spec BFL released when they took their first order
inhies: kakobrekla: you said theres a
spec for assbot. is there some way i could parse the trade data and send it to assbot ?
benkay: is bitcoind team actively working on a
spec?
kakobrekla: 18:58.28 ( @marco ) it is looking like we will help getting the
spec in order once development slows down a little
kakobrekla: 18:57.58 ( @marco ) bitcoind is the
spec essentially
kakobrekla: 18:57.57 ( @jy-p ) if you check out the godoc and comments, btcwire encodes a lot of the
spec-related info
kakobrekla: 18:57.32 ( kakobrekl ) do you have any
spec written? im asking because bitcoind does not
benkay: whaddaya mean by got
spec?
davout: if we don't have a proper
spec by 1.0 i'm out :-)
mircea_popescu: dub lol basically bfl has found the way to prevent being humiliated by nondelivery bets : create
spec confusion.
mircea_popescu: inhies rthey hadn't changed their
spec midmarch yet had they ?
mod6: eventually they'll get us that
spec and some more dev's will be off to the races on their own client
kakobrekla: MJR_ but he paid a lot more than preorders for half the
spec?
Bugpowder: maybe democracy is harder to construct than a
spec bubble
Diablo-D3: the original scrypt
spec doesnt allow the sizes Im talking about
Diablo-D3: mircea_popescu: there will be a
spec, yes.
mircea_popescu: Diablo-D3 if you actually take satoshi's stuff, write A
SPEC and then have some implementations
mircea_popescu: doesn't matter.
spec at the time of the bet being created counts.
eyes: the
spec on BFL has changed since the bet was made
KRS1337: does btc drive ltc or something or is this
spec Bugpowder_: let's be serious here. People are so desperate to get in on something 'cheap' that might explode in price, they are driving up another
spec bubble in litecoin
mircea_popescu: the current troop is really sinking their future by not doing
spec work now, while they still can
mircea_popescu: and then finally when 1.0 is released that's after a
spec has been made
mircea_popescu: and of the 5 they're not really getting 100%, and the chips dont work to
spec.
mircea_popescu: Chaang-Noi ya dude, totally. the fact that they failed to meet
spec is something that makes me jelly.
mircea_popescu: midnightmagic wwithout having talked to the man, it is my impression he basically wrote a
spec and then hacked together a mcguyver implementation he didn't think much of
mircea_popescu: "So please, lets just admit we aren't up to
spec and have never been up to
spec, and focus on getting there instead of pretending that "the world is after all perfect, if requiring a little adjustment" is a bastion of software engineering."
jurov: midnightmagic you think writing
spec from code is work for mokyes?
midnightmagic: Then do it. Do the work that the devs can't or won't, and build the
spec.
jurov: yes,
spec+compliance tests. personal performance is tangential
mircea_popescu: they try to maintain the client above the
spec. this shall not stand.
jurov: no proof. just that 0day happens independently from
spec mircea_popescu:
spec stands to code in the same relationship contract stands to trade.
mod6: So, what I'm saying is, I think it's a really good thing to create a
spec, and then everyone can punch eachother in the nuts over it until its perfect. This is the way to go.
mircea_popescu: then once we have
spec they can fix their fucked codebase and release a proper client
jurov: and who will do the
spec? have any allies to do it together?
benkay: you mentioned something about the dev team starting work on a
spec?
BingoBongo: There's the long fight over what the
spec is, and then theres the awkward grace period until the
spec forces people to leave the old code controlled version (unless crisis compells it earlier)