log
320 entries in 0.321s
asciilifeform: and hence prolly also is The Right Thing for other space-constrained applications, e.g. udptronic gossipd
asciilifeform: imho it's the Right Thing.
asciilifeform: diana_coman: btw the LSB/MSB/LMSB thing can be made slightly clearer / less-ctronic by actually making'em into 1-bit members of the record; gnat will do The Right Thing re padding
asciilifeform: currently i'm in a zugzwang in re the mmap lib : the http://p.bvulpes.com/pastes/extOl/?raw=true invocation form is The Right Thing, but it requires passing in a String for Path, which dun work without secondarystackism;
asciilifeform: let's reformulate this way : we want the ~net~ complexity of the orchestra to decrease. if we cannot yet decrease ~net~, the Right Thing is to at least refrain from adding, when possible.
asciilifeform: as by asciilifeform -- the pill which weighs the least, is the Right Thing, per http://btcbase.org/log/2018-10-25#1866148 , an absolute minimum , line for line, of os-specific liquishit, is the ticket. ☝︎
a111: Logged on 2018-10-15 00:25 phf: but you would never know, because in sbcl it generally does the right thing
phf: but you would never know, because in sbcl it generally does the right thing
asciilifeform: ( prolly The Right Thing then is to write own compat layers. for errything. but only 2 hands,sadly )
asciilifeform: this is the Right Thing, i.e. if you want a variant to exist, you gotta maintain it.
asciilifeform: it is painful, but prolly the Right Thing.
mircea_popescu: yes. but raider cannibal is much better than christian farmer. bacause raider-cannibal doesn't either think he's doing the right thing nor believe it's impossible to do something else.
mircea_popescu: the fundamental problem with "we'll permit cattle to have their usg.thing and we'll do the right thing" is that why exactly is usg getting the cheap and easy fruit ?
asciilifeform: ^ The Right Thing imho
asciilifeform: 'eink' is moar or less exactly The Right Thing for hypothetical 'thinking man's lappy'.
asciilifeform: and i'm beginning to suspect that it, or some variant thereof, is The Right Thing
asciilifeform: ~that~ is the Right Thing for cl packagetronics.
a111: Logged on 2018-09-27 17:54 asciilifeform: phf: imho your approach , i.e. dispensing with gnupatch, is The Right Thing, historically there was quite a bit of grief from gnupatch's habit of eagerly attempting to apply an invalid (by vtronic lights) but 'partially ok' by barbarian lights patch
asciilifeform: phf: imho your approach , i.e. dispensing with gnupatch, is The Right Thing, historically there was quite a bit of grief from gnupatch's habit of eagerly attempting to apply an invalid (by vtronic lights) but 'partially ok' by barbarian lights patch
asciilifeform: imho this is the Right Thing.
asciilifeform: diana_coman: somewhere i also have glue for unix signals support, so proggy can do the Right Thing when you ctrl-c, or kill, etc. but this i'll dust off later (or if somebody has a dire need)
a111: Logged on 2018-09-17 19:57 mircea_popescu: it seems to me to be the right thing here, "connect when you're you". otherwise, who are we talking to ?
mircea_popescu: it seems to me to be the right thing here, "connect when you're you". otherwise, who are we talking to ?
trinque: a teenager can do the right thing.
trinque: mod6: I figure giving them the same block times is the right thing, since it's entirely true (and useful to denote) that they were all added to manifest.txt at that time
a111: Logged on 2018-09-04 15:29 asciilifeform: now what i ~have~ wanted to bake, for years nao, is a box with ~2~ jacks, that tests rsa sigs on specially-defined packets at line speed, and drops all the ones that dun pass. this is imho the Right Thing, for entirely curing the disease in question.
asciilifeform: now what i ~have~ wanted to bake, for years nao, is a box with ~2~ jacks, that tests rsa sigs on specially-defined packets at line speed, and drops all the ones that dun pass. this is imho the Right Thing, for entirely curing the disease in question.
mod6: I can see that too, Sir. I just wanna make sure we're doing the Right Thing (tm).
Mocky: stepanov strikes me as guy trying to do the right thing for a library to be used by millions of programs, while also being resigned to the shityness of c++ and of average developer
asciilifeform: in very other noose, http://p.bvulpes.com/pastes/YETnd/?raw=true << this has been working for a while, and i see no harm in making it public; anyone can submit candidate factor to modulus, box will do The Right Thing depending on whether correct, etc
a111: Logged on 2018-08-14 17:07 asciilifeform: prolly the Right Thing would be to have the actual logtrons ( phf's, ben_vulpes's , Framedragger's if he were still alive , etc ) sync to one another as fallback
asciilifeform: prolly the Right Thing would be to have the actual logtrons ( phf's, ben_vulpes's , Framedragger's if he were still alive , etc ) sync to one another as fallback
asciilifeform: observe that you won't find asciilifeform posting tips an' tricks re winblowz terraforming. or anything re subj. the Right Thing to do with winblowz, is to flush it down toilet, and walk away.
a111: Logged on 2018-08-01 13:58 asciilifeform: i suspect an oddity with the linux tty subsystem. the Right Thing solution would be to find it. the alternative, ugly solution, is 1) 512 byte buffered reads 2) with timeout .
diana_coman: <asciilifeform> i suspect an oddity with the linux tty subsystem. the Right Thing solution would be to find it. the alternative, ugly solution, is 1) 512 byte buffered reads 2) with timeout . -> this is pretty much my current understanding as well
asciilifeform: i suspect an oddity with the linux tty subsystem. the Right Thing solution would be to find it. the alternative, ugly solution, is 1) 512 byte buffered reads 2) with timeout .
a111: Logged on 2018-07-18 01:07 asciilifeform: my only disagreement was re the notion that this is necessarily The Right Thing for erry proggy, as some sort of counter to 'rmsism'
asciilifeform: phf: it will require moar massage to actually produce a compact binary, and so i did not go with it; but it is still prolly The Right Thing long-term
asciilifeform: my only disagreement was re the notion that this is necessarily The Right Thing for erry proggy, as some sort of counter to 'rmsism'
asciilifeform: reproducible bins are The Right Thing, but it is impossible to explain ~why~ outside of the context of hand-auditability.
asciilifeform: imho dispensing with 'files as a unit' is The Right Thing, rather than complicated graph walkers. but i'ma not replay the trinque thread.
asciilifeform: ave1: this is The Right Thing, let glibc go to the bottom of the sea where it belongs.
asciilifeform: while imho this is not a 'let's do this right nao' scheme, it is prolly the Right Thing in re 'trb-i' block propagation. no moar 'block withholding' nonsense. no reason why trbi should not own ionosphere the same way mircea_popescu projected bitcoin will 'own' mains current generation capacity.
mircea_popescu: seems the ifdef approach to the problem is more in the vein of the kaballah+commentary (ie, the right thing) than in the vein of the xtian "translated scripture" + "megachurch", ie, idiocy.
asciilifeform: it is The Right Thing.
asciilifeform: phf: however it ends up defined, signing coad you could not possibly have run, and which -- given how c worx -- could contain literally ~anything~ -- can't possibly be The Right Thing
ben_vulpes: http://btcbase.org/log/2018-06-23#1829108 << the alternative, which would be a smaller patch, is a "setchangeaddr" RPC function. i'm leery of changing the call signatures of sendfrom and sendmany, but doing so might be The Right Thing nevertheless ☝︎
asciilifeform: and overall trinque's approach to kernels is The Right Thing (i.e. nail down the iron, and switch off modules)
asciilifeform: but the hero to actually do The Right Thing, never arose.
asciilifeform: mircea_popescu: this was always the Right Thing
asciilifeform: this is The Right Thing.
a111: Logged on 2018-06-11 15:46 asciilifeform: one interesting observation, is that the update mechanism lets you flash in arbitrary crapola into 'rw' section ( it simply won't jump to it if it doesn't pass rsa(sha256(payload)) ) . so theoretically could put a nop sled there, ending with jump into the magic half of unlock routine. and then expose the thing to beta/gamma, and perhaps in a few months it will Do The Right Thing
a111: Logged on 2018-06-11 15:46 asciilifeform: one interesting observation, is that the update mechanism lets you flash in arbitrary crapola into 'rw' section ( it simply won't jump to it if it doesn't pass rsa(sha256(payload)) ) . so theoretically could put a nop sled there, ending with jump into the magic half of unlock routine. and then expose the thing to beta/gamma, and perhaps in a few months it will Do The Right Thing
a111: Logged on 2018-06-11 15:46 asciilifeform: one interesting observation, is that the update mechanism lets you flash in arbitrary crapola into 'rw' section ( it simply won't jump to it if it doesn't pass rsa(sha256(payload)) ) . so theoretically could put a nop sled there, ending with jump into the magic half of unlock routine. and then expose the thing to beta/gamma, and perhaps in a few months it will Do The Right Thing
asciilifeform: one interesting observation, is that the update mechanism lets you flash in arbitrary crapola into 'rw' section ( it simply won't jump to it if it doesn't pass rsa(sha256(payload)) ) . so theoretically could put a nop sled there, ending with jump into the magic half of unlock routine. and then expose the thing to beta/gamma, and perhaps in a few months it will Do The Right Thing
asciilifeform: and mircea_popescu's pill, of limiting payload mass per shot, is prolly The Right Thing ( tho keep in mind that, given the erratic block production of typical shitfork, it will make for a quite slow and volatile dumping )
asciilifeform: ( ^ this permits decoupling of the front- and back- ends, theoretically 'anyone' can offer a valid factor for a particular modulus, and the db will Do The Right Thing . but currently only used in-house )
asciilifeform: also needs a central place to put '-j32' where it will be fed to ALL gcc & gnat invocations so that my 32-cpu box can do the Right Thing
a111: Logged on 2018-04-10 15:40 ben_vulpes: mircea_popescu: aok; i'm baffled as to why throwing a file to the running php process for evaluation would be so slow under apache but not nginx; but mod_php looks to be The Right Thing
ben_vulpes: mircea_popescu: aok; i'm baffled as to why throwing a file to the running php process for evaluation would be so slow under apache but not nginx; but mod_php looks to be The Right Thing
mod6: it used to be in my V 99994 i would just blindly press all of the leaves, but that's was rejected as not the right thing. but with the good changes that 99993 brings in, could let the user choose at press time. just food for thought.
phf: these kind of flags are set by ~xml~ files inside gnat's gprbuild support files, so there can be a general patch on gnat to do the right thing
phf: mod6: right, that's the right thing to do; for a longest time i was still pressing with the original v.py, but i suspect most people (except maybe ascii) use v.pl at this point
asciilifeform: it seems to me to be The Right Thing
asciilifeform: overclockism is an interesting subj and -- very heavily depending on the application ( i.e. is it cpu-bound ? or will you simply be making a hotter chip wait 800 cycles for each out-of-cache memory access instead of 500... ? ) can be The Right Thing. but i have nfi what use case mircea_popescu has in mind . ( mine was number-crunching, and i had specifically written the routine to fit in L0 . )
a111: Logged on 2018-02-05 14:36 asciilifeform: http://btcbase.org/log/2018-02-05#1781237 << why not make the default behaviour of the arrows 'go to the next/prev nonempty page'. imho that's The Right Thing.
asciilifeform: phf: i recall this; it is The Right Thing
asciilifeform: http://btcbase.org/log/2018-02-05#1781237 << why not make the default behaviour of the arrows 'go to the next/prev nonempty page'. imho that's The Right Thing. ☝︎
mircea_popescu: and i daresay that this is very much the right thing.
asciilifeform: mircea_popescu: edges into a 'causes and purposes' discussion, dunnit. even if trilema doesn't possibly use any such thing, conceivably it is still the Right Thing
asciilifeform: it costs like fine wine. but is the Right Thing.
asciilifeform: fwiw one can also define these like a barbarian, as x * 2 and x / 2 ; and gcc (last i saw) will Do The Right Thing and transform to a shift
asciilifeform: i suspect that his approach is in fat The Right Thing. making connect-time 'special' is every bit as dumb as making boot time special.
mod6: <+asciilifeform> to me it looks completely indefensible. <+asciilifeform> WHY should boot time be special ? << aha, to me your change there seems like the Right Thing
mod6: is this the right thing? http://btcbase.org/log/2018-01-21#1773562 ☝︎
deedbot: asciilifeform updated rating of danielpbarron from 2 to 3 << operates heathenbux-denominated FUCKGOATS dealership; trb experimenter; history of doing The Right Thing
asciilifeform: !!rate danielpbarron 3 operates heathenbux-denominated FUCKGOATS dealership; trb experimenter; history of doing The Right Thing
deedbot: asciilifeform updated rating of phf from 3 to 4 << ru lisper, bolixologist, philosopher ; http://btcbase.org/patches ; http://btcbase.org/log ; long history of consistently doing The Right Thing, inquire within
asciilifeform: !!rate phf 4 ru lisper, bolixologist, philosopher ; http://btcbase.org/patches ; http://btcbase.org/log ; long history of consistently doing The Right Thing, inquire within
deedbot: asciilifeform updated rating of BingoBoingo from 3 to 4 << long history of consistently doing The Right Thing; bisp expeditionary force; inquire within.
asciilifeform: !!rate BingoBoingo 4 long history of consistently doing The Right Thing; bisp expeditionary force; inquire within.
a111: Logged on 2018-01-20 15:53 mircea_popescu: this is not even a fair statement : if you notice such a call in your log fail, it is YOUR item that is broken. the assumption that you're pingbackable is in fact ~The Right Thing~.
mircea_popescu: this is not even a fair statement : if you notice such a call in your log fail, it is YOUR item that is broken. the assumption that you're pingbackable is in fact ~The Right Thing~.
mircea_popescu: there's a natural tendency to do the right thing that needs lengthy and elaborate stamping out before you get the full blown jwz.
asciilifeform: it's a variant. not currently convinced that it is The Right Thing.
a111: Logged on 2017-08-21 14:43 phf: i spent (mostly another whisperer and myself did) on getting vlm stable, and i'm unconvinced that some of the issues we encountered were purely "buggy vlm". there is, for example, a crash in floating point instruction that happens when you load document examiner on stock piratebay opengenera. i have no explanation for it still, because vlm code ~seems to do the right thing~. there are other similar instances
asciilifeform: apeloyee: trinqueian / mircea_popescuine vtron is arguably The Right Thing. my observation is that it may be a 50kg sword.
trinque: I'm confused; is "the right thing" the two bitcents?
asciilifeform: not yet done the necessary archaeological dig, to find whether d00d was on to The Right Thing or notquite.
mod6: the idea behind leaving the .gnupgtmp around after execution, is there because i wanted it to be there. not weather this is the Right Thing or not.
ben_vulpes: mod6: it's not a personal attack, i disagree that i agreed that v.pl was doing the Right Thing in leaving ~/.gnupgtmp hanging around
asciilifeform: mircea_popescu: imho 1 lf per para is The Right Thing ~in humanolade strictly~
asciilifeform: elaborately diddling logs is not The Right Thing. for one thing, it will cause logtrons to fall out of sync.
asciilifeform: that was a case when 'put in a comment to align vtronics and semantics' would have been The Right Thing
a111: Logged on 2017-12-26 23:02 mircea_popescu: http://btcbase.org/log/2017-12-26#1758790 << especially in the light of 1. move/rename 2. edit double-patch method this seems more and more like the right thing ; but then again what to do of regrinds ? regrind should ideally be "one patch out of many"
mircea_popescu: http://btcbase.org/log/2017-12-26#1758790 << especially in the light of 1. move/rename 2. edit double-patch method this seems more and more like the right thing ; but then again what to do of regrinds ? regrind should ideally be "one patch out of many" ☝︎
ben_vulpes: it may be that tracking hashes at the file level isn't the right thing, because with vdiff as implemented i can trivially generate a vpatch b while working from a press of a that nevertheless still only depends on genesis if a leaves files untouched and b touches those untouched files only
mircea_popescu: solid and patient improvements towards the right thing ; but preferably after db fix & client split as discussed.
mod6: Hmm. Ok, well, there *might be* a quick fix to this on my end -- not withstanding important original design flaws pointed out by asciilifeform above ^, seems that I have a possible idiotic thing in my toposort. Once removed, *appears* to do The Right Thing.
mircea_popescu: this'd require all file movements to be a separate patch, as you can't both move and edit in the same go. which imo is bonus the right thing