1200+ entries in 0.585s
mircea_popescu: davout i don't mean it as an attack or anything. and the question of exploring the negative is open now and will remain open until
spec.
PeterL: and "the code is the
spec", so the
spec says first txn see overrides any later (regardless of fees)
PeterL: there is no
spec, they can order transactions in whichever way they want
mod6: we should probably discuss solutions, write a
spec of new bitcoin, then implement new bitcoin
PeterL: wasn't the bitcoin foundation going to produce a protocol
spec at some point, or is that on the list after the reference implementation is more developed?
phf: it's basically a self contained, and very readable
spec of the language
pete_dushenski: what 50-100k. it costs 50x that much to
spec a space pen.
punkman: a wallet
spec might be nice to have
jurov: but otherwise it does not allow radio frequencies in (when built to
spec)
kakobrekla: fully automated build script < code as
spec mircea_popescu: that is not hte protocol, that is the
spec of one implemen tation among many
mircea_popescu: asciilifeform some sillyness about how some derp prankcalled an unnamed silicon manufacturer, pretended to be a secret agency so secret not even the name is known, asked for a
spec on an unspecified cpu packaging other than "it must be just like irl ones" and received a 100k firm bid on the phone as long as he provides "his ip"
mircea_popescu: how biased the otp needs to be is part of the crc
spec, for instance "every 8th bit may be a 1" etc.
mircea_popescu: "We will make a
spec for a perfectly standardized, $2500, cryogenically-cooled
ascii_butugychag: btw between that thread and now i went and read the keccak
spec adlai: lemme put it another way... somewhere in the ANSI
spec are probably one, two, or even three ~hundred~ symbols which the weaponized bitcoind-os does not need in its guts. define-setf-expander? define-method-combination? where do you draw the line?
gabriel_laddel: mircea_popescu: have you tried reading the OpenGL
spec?
trinque: mircea_popescu: your comment about symbolics murdering the competition and saying "here is the
spec" for example.
phf: bringing this into char discussion makes no sense whatsoever because
spec explicitly says you can't
phf: you can't make any statements about chars using eq. eq is a special beast used to test ~von neumann~ identity. and all the comments in the
spec are related to that. sometimes (eq 1 1) but (eq 123123 123123) is not
mircea_popescu: nothing wrong with "fuck you, you're childrten, go away. this is the
spec."
mod6: that's root, you techincally can put that after any tld and it will work as long as it conforms to the
spec punkman: problem is how do you make a
spec out of 1mil lines of C
assbot: Logged on 05-12-2015 04:25:09; mircea_popescu: the
spec accounts for this, that there should be a hook there. otherwise i fully expect most people will just use the standard dictionary if they ever use the mode at all.
mircea_popescu: the
spec accounts for this, that there should be a hook there. otherwise i fully expect most people will just use the standard dictionary if they ever use the mode at all.
☟︎ assbot: Logged on 19-11-2015 19:49:28; phf: punkman: it's really experimental technology. ~giant~ multilevel
spec, implemented by a handful of enthusiasts. only worthwhile if you're prepared to spend large fraction of your time on improving and debugging the gui code itself.
phf: punkman: it's really experimental technology. ~giant~ multilevel
spec, implemented by a handful of enthusiasts. only worthwhile if you're prepared to spend large fraction of your time on improving and debugging the gui code itself.
☟︎ trinque: I implemented the straightforward
spec mircea_popescu made
mircea_popescu: incidentally, the only case where a "source is the
spec" could be excused, is properly written knuth c.
phf: as far as lisp, yeah, not practical for deployment, but i started getting bogged down in trivial serialization questions, before i understand clearly how the whole system is supposed to work. once i get the
spec as is up, i want to start working through those comments to modify it into a udp lower level system. in any case lisp is better option for gossip prototype, because the
spec is so open ended
phf: i have some code for gossipd, i'm going to by the
spec that's published on trilema, rather then follow up conversation about udp and first packet validation. i wrote enough in c to be able to prime gpg machinery and send packets over the wire (which basically coveres things that i wasn't sure how to do before i started), then i switched to common lisp to get a prototype up. what came out of that so far is updated bindings for lisp
phf: thestringpuller: it wasn't actually forced. started as a final project in william arbaugh's (the guy who did the smooth handover wireless implementation at umd) class, where we were writing a malloc for the teaching os as a final project, only three mallocs came anywhere near the
spec, since mine was one of them i had the opportunity to say that the whole thing was a sham "shit code written by retards", etc. and that you can have orders
jurov: and in any other cases where you don't have to choose exact glyph printed, you can ignore 99% of unicode
spec ascii_field: what would a mircea_popescu-
spec definition look like ?
BingoBoingo: Could probably
spec jpeg, png, and animated gif as fine, .gifv and .tiff are spammy
pete_dushenski: so... you can
spec a 'microshit surface pro 4' with 1tb hd, 16gb ram, intel i7 for... $2`700 !
pete_dushenski: pope poverty-
spec isn't exactly breaking the mold here.
mircea_popescu: if someone new to low level stuff is eager to do some useful
spec work, feel free to examine this issue.
mircea_popescu: "Taylor Gerring @TaylorGerring · Sep 17 Taylor Gerring retweeted Vitalik Buterin The benefit of #Ethereum being defined by a
spec, not an implementation "
mircea_popescu:
http://log.bitcoin-assets.com/?date=15-09-2015#1275370 << o hey, we actually get to that. anyway, it's not so terribly different from how rome was a "nation". various actual nations in various states of digestion, also in various states of dependency, and an originator preserved in name only. the original latins were a tiny
spec also.
☝︎ BingoBoingo: Easy comparatively, IF level of cleanroom isn't
spec'd
BingoBoingo: How can one even pretend to have a hypertext
spec or its substitute without citing <em>Vannevar Bush</em>
pete_dushenski: garzik re 'bip100' reddit convo : This is mostly pre-feedback, transcribing the discussion documentation into a technical specification. The doc &
spec & code will evolve from here, based on community feedback and testing."
phf: but there's a pathname
spec that lets your implementation answer that question for you
mats: i also have yet to decide how to solve the np-complete problems in the
spec ascii_field: portable mass
spec / gas chromatograph for volatiles - yes
phf: g the wrong RSA key." message format
spec explains "First 2 bytes of the Message Digest inside the RSA-encrypted integer, to help us figure out if we used the right RSA key to check the signature."
punkman: ascii_field: do you have an outline/
spec for v? I could give you a hand with that
mircea_popescu: ascii_field get out. by the time oil was a central commodity to civilisation for fifty years, it was trivial to get an engine deployed to
spec. TO
SPEC!!!11
mircea_popescu: help the guy draw the
spec document and then let him do it, free a hand
mircea_popescu: the "use specified card,
spec = p[ast" is sustainable.
mircea_popescu: chetty no. the "use specified card,
spec=future" thing is braindamaged. nobody has cards from the future.
trinque: mike_c | really? hm.
spec is lazy. << yup, everything in the browser has the squish of trying to be maximally permissive
mike_c: really? hm.
spec is lazy.
trinque: mike_c: not required by the
spec assbot: Logged on 19-07-2015 19:46:27; asciilifeform: again, it wasn't in mircea_popescu's
spec mircea_popescu: i dun see how they do anything. either they maintain compliance with tcp/ip
spec as is, in which case they do nothing
Luke-Jr: decimation: Bitcoin's rules by nature are defined by the actual software people are using. If a "
spec" disagrees with those de facto rules, the "
spec" is wrong.
Luke-Jr: decimation: because people might interpret it as a
spec decimation: I mean a
spec that desribes the behaviour of the entire codebase
Luke-Jr: decimation: what? BIP 66 has been a
spec since January
decimation: Luke-Jr: this whole line of action strikes me as backwards. why not produce a
spec before forcing changes from the de-facto standard?
mircea_popescu: the us doesn't even have a fgucking missile
spec sheet.