600+ entries in 0.162s
mircea_popescu: asciilifeform, i realise now i didn't even
spec the bot correctly, it's supposed to multiline if multi links
mp_en_viaje: shrysr, nfi why it doesn't work on your machine. indeed the solution should be browser independent. maybe they broke the
spec ?
ave1: btw, I do like lisp and going through the
spec.
mp_en_viaje: as to the multiline thing, i recall my trying to
spec a multi-line selector with framedragger just prior his disappearance. iirc he got it working, maybe lift that ?
mp_en_viaje: in continuing sads : /me attempted to
spec the server side php job ; and it can be done, roughly, there exist primitives for, eg, "insert this after nth word and that after mth word". however : a) this interferes with the footnotes, because footnotes exist as z (( b)) and not as displayed on page ; and b) there's no good way to # and ? at the same time because of the way trilema handles title-urls.
BingoBoingo: jurov: The problem I find myself in at this time, is that the time to
spec the auction that way is when opening it.
diana_coman: I don't even recall exactly but basically took their
spec too seriously
a111: Logged on 2019-04-23 23:09 asciilifeform: incidentally, even a very brief look at the 1801 item confirms the troof of
http://btcbase.org/log/2019-02-14#1896836 -- thing defo aint a 'and here is where the ameri-crystal does x' , it's a quite 'fits-in-head' object , very evidently produced from page-long
spec of the orig instruction set
mp_en_viaje: anyway -- in fairness the "space is magic char" thing very much comes from html
spec itself.
Mocky:
http://btcbase.org/log/2019-05-03#1910995 << no. The proposed
spec results in a linear chain, the tip of which is the only place where the next vpatch could go without a schism/civil war. On your own computer you can press wherever you want in the chain (or have private branches w/e), but in public you can only release further vpaches based on the same tip of the chain that everyone has. this is defacto consensus.
☝︎ diana_coman: re run: does this mean that currently this is the de-facto "pizarro-iron amd" preferred
spec ?
diana_coman: asciilifeform: ok; can you point me please to
spec of the machine as I don't fully have it in-head?
a111: Logged on 2019-04-01 14:08 asciilifeform: in other noose, asciilifeform nao has what appears to be full pinout, timing, bus sequence, register, init magic, interrupts, etc.
spec for bolix 'ivory' (won't, presently, say from where, unless source wants to be cited, plox to write in. )
a111: Logged on 2019-04-17 18:33 asciilifeform: meanwhile, in february, chinese
'gowin semiconductor co' cloned ice40. but if anyone thought this means 'open
spec', guess again, only worx with their 'YunYuan' closed shitware toolchain.
PeterL: <+asciilifeform> 0 in usa meet
spec, unless i suppose you go to the mountains << I dunno about that, there are plenty of clean air parks around where I live
BingoBoingo: Well, don't recruit in engineering. I never
spec'd that. Go for nutrition, early childhood education, etc.
mircea_popescu: asciilifeform i can live with telling people "raise your stack limit for your file is large" ; i have a lot more trouble sleeping at night if i tell people "raise your stack limit for some idiots made a broken
spec we did not fix."
mircea_popescu: making sure this latter case never happens requires a little bit of needlework. the original implementations tried to keep close to the original
spec, for basically naive and unexamined
http://btcbase.org/log/2019-01-02#1883944 reasons. as it turns out, this was the wrong cut.
☝︎ BingoBoingo: Forgot to
spec socketed RAM. I haven't even seen socketed chip teases
mircea_popescu: "He said that they have also contacted the GNU Arch maintainer about adding GPG signing. Though it may take some time to develop, the addition of GPG signing to commits would be a welcome feature. " << see, because we
http://btcbase.org/log/2018-01-24#1775402 over his failure to bring gribble up to
spec.
☝︎ Mocky: so not optimal, maybe even laughable, but yet has a model and as
spec that is not self contradictory
Mocky: there are explicit and implicit semantics, but if you read the
spec, you know what you'll get. multiple threads setting a value on the same variable never create garbage
BingoBoingo: On the other hand there is also the case where, when the datacenter is ready to be paid again, a flurry of undersized payments is likely to lead them to WTF. Further the local liquidity hits a bigger buy/sell spread with the volume the datacenter's monthly requirements demand (And then there are the consequences if third party fails to pay the datacenter to
spec).
mircea_popescu: nevertheless, the
spec is as described, with t2400, 31 W.
mircea_popescu: BingoBoingo but yes, i guess if you put it out there i have no choice but to spell it out : of ~fucking course~ the carpenter "sticks his file in there". it's a sales gimmick, like the new york electrician pointing out to people they gotta pay him a billion to "bring the buildingto
spec" because "otherwise he has to report them" because "otherwise he loses his own license". because we're supposed to not notice the whole mob-e
mircea_popescu: and this is a fundamental assumption baked into the udp
spec etc.
mircea_popescu: so, i hear from cto the comms
spec's mostly implemented. now, we're at the point where we wanna make a rsa and a serpent sender.
mircea_popescu: honestly, the engine needs a rewrite anyway. and the rewrite needs our svg/html
spec. and so following.
mircea_popescu: main problem of historical / archeological work is to discern the coincidence from the item. (is this
spec of dust or is it portion of priceless artefact ???)
danielpbarron: the poker bot
spec includes seeds from each individual player. would that make it ok, or still bad?
mircea_popescu: but i mean... you don't even have the
spec against which to check this "works" ?
phf: i was very much insulated from open sores lisp with acl, just sort of assumed that they were all basically the same. turns out that common lisp world is a cargo cult. for when
spec was never supposed to be and all be all: it was a _thin_ common ground of a variety of rich lisp ecosystem. writing _just_ to
spec is an exercise in frustration..
mircea_popescu: asciilifeform kinda the point of the design/
spec yeah. BingoBoingo heh.
billymg: yeah, and not surprising considering they update the "
spec" every coupla months
a111: Logged on 2018-11-13 21:19 mircea_popescu:
http://btcbase.org/log/2018-11-13#1871787 << afaik his lisptron works to
spec, and ~only exists~ because everyone harped poetic about how great lisp "would be", only to predictably return to more brackish "we use python" once someone actually made something that'd need such a wonder as the inexistent lisp machine.
mircea_popescu:
http://btcbase.org/log/2018-11-13#1871787 << afaik his lisptron works to
spec, and ~only exists~ because everyone harped poetic about how great lisp "would be", only to predictably return to more brackish "we use python" once someone actually made something that'd need such a wonder as the inexistent lisp machine.
☝︎☟︎ mircea_popescu: but he installed me a deluge on his cuntoo on my server to
spec and a job very well done indeed.
mircea_popescu: this is actually a pretty good
spec for a... well basically a "compiler for web" as opposed to "compiler for machine"
mircea_popescu: note that eg the eulora
spec (low value item anyway) has MANY keys.
BingoBoingo: Produce product to
spec within insaneland limits
mircea_popescu: note that it's not even illegal to blank the manifest or w/e. impolite, yes, but the
spec allows.
mircea_popescu: iirc other than new voice model, a "flush addy" was also in deedbot upgrade
spec.
mircea_popescu: well now i'm reading through all dis, what can do. phf's four months at work resulted in same many months of rot, now we don't recall the
spec, log is long, life is short, so on an' so forth.
diana_coman: as one might tell, I'm looking into using CRC in smg.comms as per latest
spec