log☇︎
20000+ entries in 0.209s
asciilifeform: http://btcbase.org/log/2017-07-12#1681720 << unfortunately-- wrong; sure does pay. hence the few thou. sybils currently masquerading as btc nodes ☝︎
BingoBoingo: <mircea_popescu> dba variously as usg's very own honeypot for cypher-dorks. << AHA, dedicated Thermos sodomizer
trinque: as it stands I'm already the host for the trb deps.
mod6: As far as production hardware, not sure how we could vet such an environment. But maybe I can just think on this a bit.
mircea_popescu: dba variously as usg's very own honeypot for cypher-dorks.
mircea_popescu: asciilifeform yes, as a practical matter. i was just discussing the "must have buffer" theoretical point.
asciilifeform: as i understand, this doesn't test entropy
asciilifeform: mircea_popescu: b, as i understand, isn't even physically possible without a buffer
mircea_popescu: a is also twice as strong, because obviously b will flip on average half the bits it sets. but is this ACTUALLY half ? ie, how do yo umeasure unrandomness ? b is much more strongly patterned than a.
mircea_popescu: as alf points out, a is "better" in the sense v-n debiaser kills b, if this is a better. unclear.
asciilifeform: the possibly paradoxical answer, afaik, is there does not actually exist such a thing as good entropy. only bad and worse.
shinohai: or cocktail as case may be
mircea_popescu: they -- also do 0 if not used as prescribed
mircea_popescu: as in, balance it according to a calculation, rather than according t oa feeling.
mircea_popescu: then we feed it into entropy-dependent processes (say the rabin miller test, as discussed yest) and see what comes out.
a111: Logged on 2017-07-10 19:50 mircea_popescu: which incidentally brings us to a very workable and very useful tmsr definition of entropy quality : take a FG string. flip a number of consecutive bits to 1. the result is your entropy quality, such as 100/1mb if you flipped 100 bits.
mircea_popescu: ben_vulpes here's a high pay grade question for you : of the two models of "controlled de-entropy" i spawned in a week, specifically a) count of randomly placed flipped bits, as in the discussion with you re that and b) string of randomly initiated, n bit long SET bits, as discussed in http://btcbase.org/log/2017-07-10#1681268 which does the bitcoin foundation regard as a better candidate for standardization as "the republic' ☝︎
mircea_popescu: "As recently as earlier today, the Fake News empire turned idiot son Donald Junior's gullibility with respect to a phishing scheme1 into their latest headline of the day which they will use to sell loyal consumers of their fiction product on the "certain end" of the 8 year Trumpreich in spite of all the actual evidence running to the contrary of their narrative supported instead by a complete lack of evidence."
BingoBoingo: In other news: Fake news attacking idiot son (Donald Jr.) for trying to impress father because shut out of campaign as an idiot
deedbot: http://qntra.net/2017/07/credibility-of-us-universities-falling-as-desire-for-great-again-takes-lead-in-culture-war/ << Qntra - Credibility Of US Universities Falling As Desire For "Great Again" Takes Lead In "Culture War"
mod6: i haven't gone all the way through the W_Mul yet, but just unrolling it as said.
mircea_popescu: just as should be. first spec code then optimized code
asciilifeform: upstack, ffa wants to double as a 'how to rsa' 'b00k' , i.e. at every point tradeoff was made for clarity rather than speed.
mircea_popescu: moreover, if you do fixed as described, you CAN so unroll, if you do or if you don't.
asciilifeform: seems like it works - almost astonishingly - as printed on the box...
mircea_popescu: ~same as the relation between pointer and its content, "better hope programmer didn't fuck up ; and also it usually blows up if he did so there's that"
mircea_popescu: i am sitting here wondering if this is "getting rid" as in, rid or rid as in, hid.
asciilifeform: in much the same way as 'in' parameters (in ada procedures)
mod6: i've read, so far seems ok -- i've got to wrap my mind around the second ("high loop") as I did before.
asciilifeform: incidentally, (imaginary) prize to the first d00d who understands why this had to be rewritten with the loops indexing from 0 .. L-1, rather than, e.g., for i in X'Range ... as formerly
asciilifeform: so may as well get head start.
mircea_popescu: which incidentally brings us to a very workable and very useful tmsr definition of entropy quality : take a FG string. flip a number of consecutive bits to 1. the result is your entropy quality, such as 100/1mb if you flipped 100 bits. ☟︎
asciilifeform: i can think of other considerations, as in the thread with the exponents
asciilifeform: incidentally, mircea_popescu's argument could just as readily be made re 4096 vs 2048 etc
mircea_popescu: yes, but i mean as the middle of distribution
a111: Logged on 2017-06-29 19:57 asciilifeform: in other noose ! nao we have comba's algo multiplier as basecase in karatsuba (currently threshold 8 words) , and http://btcbase.org/log/2017-06-21#1673165 becomes now 7.5sec
BingoBoingo: "Rooney Mara’s character, grieving the death of her lover (Casey Affleck), returns home to find a pie left in her kitchen by a sympathetic friend or neighbor. As the bedsheet-clad ghost of her beloved looks on, Mara’s character, known only as M, unwraps the pie, sinks to the kitchen floor, and devours almost the entire thing in a five-minute, uninterrupted sequence before suddenly dashing to a nearby bathroom to throw up." << Films W
mircea_popescu: http notably gets this half-right : there's no such thing as an error message the server ever expects to see from a client, such as i dunno, "this page has porn on it, unacceptable, send me another version" or whatever.
mircea_popescu: but the problem becomes really complex when you consider "bitcoin block index" is as of right now "positive integer under 474974", and won't stay that way for long.
phf: it was an example of what "byte packing protocol" is. designing proper byte packing protocol is left as an exercise to the reader
mircea_popescu: for the curious : yes, i also have this problem in speech, especially when discussing complicated things with complicated women, and the solution THERE is the sort and short rule. which in relevant part says here that "(1 #.(+ 1 1) 3)" could NEVER be interpreted as "(+ 1 1)" because "(+ 1 1)" was a shorter statement of that and it wasn't used.
phf: mircea_popescu: well, sexp ~is~ code, primarily it's for writing your programs, not ~storing~ data. there's no such thing as sexp internally
mircea_popescu: phf and the reason for this is that it tries to take it as code.
asciilifeform: mircea_popescu: it never caught on for large machines, i will leave the reason for this as an exercise for reader
mircea_popescu: but i can say you not merely should, but absolutely must. the cornerstone of wire protocol is a firm, protocol-derived guarantee of there being no such thing as bad data.
mircea_popescu: everything sucks where there can be such a thing as "this is the table of possible inputs and these are the three that set it on fire".
mircea_popescu: the very possiblity of even having such a thing as "broken data", by eg naming your kid "-- DROP table students;" is why i agree with the sql sucks sentiment.
phf: (common lisp sexps are backed by a full blown reader, with multiple non-trivial dispatch macros, so for example '(1 #.(+ 1 1) 3) is a valid sexps that's read as '(1 2 3), i.e. (+ 1 1) is evaluated at read time. there's a dispatch for structs, like #S(FOO :A 1 :B 2) results in a structure foo with two slots a and b set to 1 and 2 respectively, but there's no corresponding constructor for classes. there's a reader for arrays, but that one doesn't let you
phf: same as you would do it locally. it's a transparent rpc, not a specified one. so either the operator does manual discovery, or you define a discovery convention. (and then there's middle ground, where you use standard tooling, like code to list packages and symbols to do discovery for you)
mircea_popescu: also, there's not so much darker gypsy association. one of mah first youthful loves was this blonde horseriding gypsy girl from the danube delta. hot as hell, and about as dark as hillary clinton.
phf: well, one thing that ascii said "don't operate at a byte level", might also be the reason why lisp version is slower. bit vectors are stores as octet arrays, so tweaking single bit pulls a whole octet, does bit twiddling on it, and then puts it back. presumably can be sped up if one were to figure out how to work over an octet at a time
phf: presumably as asciilifeform keeps implying you could rewrite mp's fhf in some closed form that does account for these issues, but..
mircea_popescu: somehow peeps got the idea it's "unfair", like little kids playing a game, to use computers in certain ways that expose them for being mere machines, rather than your girlfriend. such as making them do things like fhf.
mircea_popescu: anyway, i'm very much convinced that the various "oh, it's the same thing really" bad choices hash designers and implementers make, very much typified by the above "machine word so as to '''elegantly''' avoid these problems" very much plays into nsa needs. it's again that same old convenience that makes the usg usg.
mircea_popescu: what "bitcoin nodes" currently do is a very shitty attempt at just this. and they are as autonomous as you are conical, also because they fail to correctly implement this.
phf: http://btcbase.org/log/2017-07-08#1680544 << nope, in fact my "optimized" one i.e. the version where cmucl doesn't complain about unknown types with (speed 3) (safety 0), is about twice as slow as Go version. i'm curious why that would be the case, but haven't had a chance to investigate. ☝︎
mircea_popescu: trinque amusingly, candi does sort-of this, as a prototype of it.
BingoBoingo: " Huel‏ @gethuel Jun 19 A new concept in food - 100% vegan with protein, fatty acids, fiber and 27 essential vitamins and minerals​." << Poor naming. "Huel" is mostly known to USians as the name of the fat pickpocket on some "prestige" tv show.
trinque: "connect" too, is not quite right, as it would be a superior model for me to huck a request to you, which ~maybe~ you get, and which ~maybe~ you drop on the floor at wire speed, and maybe you huck me something back, if you want.
a111: Logged on 2017-07-09 00:27 sina: http://btcbase.org/log/2017-07-08#1680865 << is it not such a task as serialization/deserialization? using such as http://www.cliki.net/serialization?
mircea_popescu: at least it's conceptually a thing, as opposed to "here's some data, and here's some half-tagging, and here's some half-code with it"
asciilifeform: http://btcbase.org/log/2017-07-08#1680868 << recall that the variation was not as simple as 'this one here has 8bit byte but this one - 11, but each one simply represents a 2**n-1 range of uint' ☝︎
a111: Logged on 2017-07-09 00:27 sina: http://btcbase.org/log/2017-07-08#1680865 << is it not such a task as serialization/deserialization? using such as http://www.cliki.net/serialization?
sina: http://btcbase.org/log/2017-07-08#1680865 << is it not such a task as serialization/deserialization? using such as http://www.cliki.net/serialization? ☝︎☟︎☟︎
asciilifeform: ( and probably could not be in the standard, such things as, e.g., width of the machine word, were not universal constants )
trinque: I'd say folks yes, use sqlite because they did not reason the program out completely before beginning to write code, but they often use postgresql as a messaging platform, RPC, or what have you
trinque: what it lacks (at least as part of the CLOS standard, afaik) is a standard for how one CLOS program shares objects and methods with another, whether on same box or across the network. ☟︎
a111: Logged on 2017-07-08 07:21 sina: I dunno much about lisp, but I think lisp handles this better in the sense you write state into the "lisp machine" and can flush that entire state out to disk and read it therefrom as well?
mircea_popescu: wait, he's trying to turn the horde of aging "trynna make it as a pimp" blacks into good consumers with credit cards ?
a111: Logged on 2017-07-08 10:54 sina: wasn't as bad as I thought it'd be
sina: wasn't as bad as I thought it'd be ☟︎
sina: as I guessed :P
sina: I dunno much about lisp, but I think lisp handles this better in the sense you write state into the "lisp machine" and can flush that entire state out to disk and read it therefrom as well? ☟︎
sina: one interesting thing is that I thought there would be some databases implemented as flat files, but I can't seem to find any
mircea_popescu: this is fine, as a general notion, but what is it based on ?
sina: I just doubt I can impl, e.g. transactions as well as sqlite guy
sina: if its a matter of moving a key from keys/available/???.key => keys/assigned/name_of_peer_assigned.key ...or symlinking as you mention
sina: with the privkey as the contents of the file
mircea_popescu: be that as it may.
asciilifeform: i'm already on record as having described, in agonizing detail, why it is a monumental waste of time, but if mircea_popescu et al not convinced -- welcome to 'piss on electric fence'
a111: Logged on 2017-03-20 17:00 asciilifeform: http://btcbase.org/log/2017-03-20#1629256 << even reiser is almost certainly waste of time, general-purpose fs is very sharply the opposite of what we want, they are all optimized for mutability (can delete/rename/resize/etc) and fast reads at the expense of slow entity creation, as well as carrying out silent rebalances/defrags/etc.
asciilifeform: http://btcbase.org/log/2017-07-08#1680565 << it stalled at the discovery that 1) performance is abysmal 2) for wholly fundamental reasons ( of shit-poor rewritable data structures forced by 'generic fs' shape ) 3) all extant fs would have to be patched regardless to remove idiot node caps, and may as well write proper db from scratch that is bitcoin-shaped 5) asciilifeform then wrote the latter, in ada, and put on shelf, to pick up a ☝︎
mircea_popescu: such as, we';re discussing cunts, but oohohohohobviously not rly.
mod6: and as far as pete_dushenski or whomevers quest to write a log digest or whatever, it never happened. the foundation briefly considered a role for gathering up trb related parts, but that was set aside in exchange for tb0t
ben_vulpes: hodang hexdump does this as well
a111: Logged on 2017-07-08 02:01 mircea_popescu: certainly above qs could have been asked just as well by a noob, and vague "large threads" reference dun help him any.
a111: Logged on 2017-07-08 01:13 phf: pretty sure asciilifeform is actively ignoring the whole initiative, with only periodic pounces. as opposed to his older strategy of annihilating the whole thing upfront. must be getting old
mod6: as a way to teach it to myself, i've been poking around with a v impl.
mircea_popescu: sina you can implement your whatever as a binary tree, leverage the directory structure, and simply check if there's a file / write it.
mircea_popescu: this idea working as intended then.
mircea_popescu: as opposed to what, death ?
mircea_popescu: certainly above qs could have been asked just as well by a noob, and vague "large threads" reference dun help him any. ☟︎
phf: that's a tricky request, but the tenets are around shitlangs differentiation, "fits in head", v as a way of releasing code, what it means to own a piece of technology. there's a handful of threads that had definitive conclusions, that i consider tenets (i think the word should be in quotes to indicate that while not true tenets, violating them will require reopening large threads)
phf: or perhaps now that he has successfully served as the main driving force behind the tenets of tmsr technology and ensured that they are collectively accepted, he doesn't need to reaffirm them as much. but i also have wonder if the tenets have as much of a galvanizing effect now that we mostly had a chance to observe both their positive and negative effects?
mircea_popescu: you have a theory as to why ?
phf: pretty sure asciilifeform is actively ignoring the whole initiative, with only periodic pounces. as opposed to his older strategy of annihilating the whole thing upfront. must be getting old ☟︎
mircea_popescu also, as young tyke, thought "wtf breadboard, useless shit takes more time to set up than it's worth new". then touched 120V a coupla times and grew wiser.
mircea_popescu: it allows you support to set out all your shit and connect it as you want, and measure and decide how to package it.
mircea_popescu: even as a prototyping item.
mircea_popescu: sina go make a drop-in flatfile db replacement, so people can drop it in right now. there's a market, such as people who aren't happy mp-wp pulls in mysql.