tmsr - Search: a

43500+ entries in 0.307s

asciilifeform: no good. first of all suppose there are 2 concurrent runs of the vtron ( say this is a cuntoo pressing itself ) ☟︎

mod6: i don't have a chance right this moment to do that, will look tho when i can

mod6: <+asciilifeform> mod6: an aborted run of vtron should not be able to put a caltrop for subsequent run to die on. this is imho elementary.

asciilifeform: let's quote ftr : 'Creates a temporary directory in the most secure manner possible. There are no race conditions in the directory’s creation. The directory is readable, writable, and searchable only by the creating user ID. The user of mkdtemp() is responsible for deleting the temporary directory and its contents when done with it.'

asciilifeform: however the external 'tempfile' item, made gensymtronic dirs. so this never became a headache.

a111: Logged on 2015-11-05 02:08 asciilifeform: -- a unique thing that never was and never will be again.

asciilifeform: mod6: an aborted run of vtron should not be able to put a caltrop for subsequent run to die on. this is imho elementary.

mod6: im pretty sure we all had this discussion once upon a time, and it's only doing now, what we agreed to do before. I can go and dig for that.

asciilifeform: esp if it gets in the way of a subsequent run

mod6: <+ben_vulpes> mod6: while you're in there can you get your vtron to cleanup its tmp gnupg directory when it catches a ctrl-c? << if you CTRL+C the thing, it really can't get rid of it. you're expected to clean this up on your own so the vtron doesn't remove something it wasn't suppoesd to.

asciilifeform: ever owned a rpn calc , ben_vulpes ? ☟︎

ben_vulpes: it does, this is my first encounter with a stack machine tho so thinking is proceeding slowly

asciilifeform: !A .0.0*#

asciilifeform: ( obviously was a paste artifact, from '%' case )

asciilifeform: !A .0.1*#

asciilifeform: and it survived nearly a week of asciilifeform rereading whole thing every day.

asciilifeform: there's a stray MustNotZero(Stack(SP)); in ffa_calc.

asciilifeform: !A .1.0*#

asciilifeform: ( have a gensym. there is no excuse ever to be hosed by a previous unsuccessful run. )

asciilifeform: but other unixland utils do not do this, so it is possibly a bridge too far to expect it of this one

asciilifeform: ideally a vtron oughta unhappen, to the extent possible, everything it did to the world, if it gets a ctrl-c

ben_vulpes: it is a minor thing that i occasionally trip over

ben_vulpes: mod6: while you're in there can you get your vtron to cleanup its tmp gnupg directory when it catches a ctrl-c?

asciilifeform at one time tried to read fare's blog, quickly barfed, d00d has a multitude of socialist-flavoured cockroaches in his crankcase

asciilifeform: ty for making and maintaining this vtron, mod6 . it is a good thing.

mod6: There are better error messages, or averting a silent fail that will also help here. I haven't gotten that far on that part yet.

mod6: yeah, i actually did add a 'check_required' routine that is semi-related to this. for instance, when that error happened, it was because some guy didn't have `sha512sum'. so the check_required subroutine will now run first, and check to ensure that a list of system biniaries are available before anything happens. and if not, exits.

asciilifeform: and 'wild chain found: ...' when there's a missing seal

asciilifeform: e.g. 'beheaded chain found: [list of patches]' when there is a patch with non-null parentage but parent is absent

mod6: I went through each one, looks to be doing the sane thing. I'm probably going to write it up in a little post that can be looked at, as opposed to trying to explain all of that in 3 lines of irc. ☟︎☟︎

mod6: not bad! i implemented the pill to calculate the press path from a given leaf. seems to be working pretty well. i ran all my automated tests, passed 50/54 without incident. Four of the tests are pretty complex test cases where we basically yank one of the vpatches out of the middle of a vtree, then test to ensure that we avoid that where required.

asciilifeform: could , in principle, be expanded into a scripting lang.

asciilifeform: that being said, gprbuild ( what ffa uses instead of gnumake ) seems to make very effective use of a kind of interpreted subset of ada

asciilifeform: i dun particularly relish pythonism, but proliferation of 'i wrote it on a napkin, on a train, while drunk' script langs, incl. elisp-style dynamicscope abortions, is imho harmful

shinohai: lisp works as a scripting language, neh

asciilifeform: it comes with the binariolade gnat. if you're using gcc gnat, will have to compile it, a little bit gnarly.

diana_coman: I'll have a look at gps then

asciilifeform: but then again why the everlivingfuck would i run with defaults on a ~configurable~ tool that i use 14+ hr/day )

diana_coman: yes, so you need emacs because slime; that sounds like a lot of snails already,lol

asciilifeform: http://btcbase.org/log/2018-01-05#1764882 << i'm quite tempted to give the archive another combing and make a sequel to my http://www.loper-os.org/?p=165 item ☝︎☟︎

asciilifeform admits that he does not particularly ~like~ emacs. it simply ended up a schelling point, like linux. but suffers from same type of problems.

asciilifeform: ( it has a superior grandfather, the actual bolix lispm. but no equiv on pc. )

diana_coman: as a side note, that's precisely why I did *not* adopt emacs in the end despite liking it quite a lot when met it at uni: it was VERY useful indeed but the sort of useful that was too close to addictive for my liking essentially

asciilifeform: back when i had a horizontal display, most of the time i had it column-split and emacs 'followmode' to flow proggy between them

diana_coman: I suppose I'm not much of a train basically

diana_coman: ah, should have been precise there: they don't make a difference for me at this stage; I can stick to 80 just as I can stick to 76 really

asciilifeform: they make a difference, diana_coman , those 4 chars. just like if you suggested to a railroad to take 4cm from the rail gauge.

asciilifeform: diana_coman: as a side effect, you get an easily formatted code-box for blogging, as in ffa.

asciilifeform would not insist that a vpatch ~itself~ oughta be 80col, as that would constrain the contents even further, to 76 or so

asciilifeform: ought to be printable on a drum printer

asciilifeform: diana_coman: not merely code, but everything that is in a vpatch

diana_coman: which is perfectly fine with me for code; it's still grating for comments and I'm not sure how this will resolve, it sort of pushes comments out of code (to a place where one can read them as text not as code-which-they-are-not) ☟︎

mircea_popescu: motherfucking mother of isis, the act of arraying buttons together in a guy is no design!

mircea_popescu: anyway, thinking about this whole "fsf was an attempt to *finally* bring about socialist utopia through a fettering of everyone's access to knowledge while open source was an attempt to nevermindthatjustkillM$already leading to java-for-browser because microsoft invented a c++ market etc" broad but really mostly correct summary, the one most striking aspect is that somehow the job of the modder (ie, guy that adds those snazzy

mircea_popescu: these letters from a time before empire-of-idiots was formalized and understood as such are about as fascinating as a child's experience from before it understood any mechanics at all.

mircea_popescu: "doom is inevitable, BTW. mankind will die out, planet earth will be vaporized when Sol goes nova, if not sooner, and then Common Lisp will have to acknowledge defeat to the unwavering hostility of the universe. for those of us who plan to become immortal, this is a serious concern." <<< 1999 naggum was apparently planning for immortality ?

mircea_popescu: diana_coman technically it's incorrect to say "6 bits will always be 1" ; it's the case that the first and the last bits of N are always 1 ; and a further number of bits are subtly affected (ie, biased) by the p, q masks.

mircea_popescu: no known pattern ; but no homogenity either. there's always an even count of integers in a given bitsize ; but not necessarily an even count of primes.

asciilifeform: would be neat to generate keys in bounded time. and know primality for a fact. BUT i dun have, yet, such a pill.

asciilifeform: mno. you have same 2044 or whatnot. just takes you longer. and with m-r , also chance to step on a mine.

mircea_popescu: asciilifeform you have a different problem : even if "no bit of input is more influential than other" i STILL want to put in no less than 2045 bits of input ; AND get out no MORE! than 2048 bit long prime.

asciilifeform: nor do i expect to see a solution.

a111: Logged on 2018-01-05 00:12 asciilifeform: right, 'engineer' is more a psychological term to asciilifeform , rather like rpg character class, than diploma.

asciilifeform: there is pointedly NOT a safe constructor known.

asciilifeform: ( but not having it yet -- asciilifeform cannot say for a fact. )

asciilifeform: specifically that a proof of uniformity for an apeloyee-style primeconstructor mechanism, is in nearer reach than a runnable-on-2048b-ints aks.

asciilifeform: the sheer wtf, srsly, consider the folx who imagine they are somehow cryptoizing on a machine with no trng

asciilifeform: i mean ffs, koch dun even leave a knob to get ~key~ entropy trngistically.

mircea_popescu: "oh, 2 is a great witness for odd composites" "so would have been any other even number" "yes but... umm..."

mircea_popescu: i'm dealing with "four rounds of m-r and a 5th fixed with 2, so as to fix the cone of blindness" bs and you want me to care about the 2047th bit ?

mircea_popescu: yes well, we're looking at ~10 second m-r run per item, so like half a day to produce a pair of primes.

mircea_popescu: 110 x 110 and 111 x 111 BOTH result in a 1yyy

mircea_popescu: the ONLY way to make sure the top bit of a product is set, is to have BOTH top bits in BOTH factors set.

a111: Logged on 2018-01-04 21:16 phf: a forced popup that warns you that you're sending to http from https, but there's no about:config to disable the popup. 9 years of "ffs put a boolean in configs, you fucks"

mircea_popescu: (and there was some idiot sheila from down below years ago ; i recall lulzing in the logs as to how this wonder will drive rapist to a) probe and b) beat into a squirming, faceless mess any bitch dumb enough to go around with it)

asciilifeform: mircea_popescu: subj is a type of boobytrap, vs freud's

mircea_popescu: note to journahos of the future : include a plain statement of the above fact in your opening salvo or else.

asciilifeform: oh it's simply a painfully small cpld is all

a111: Logged on 2018-01-04 20:10 BingoBoingo: In other news from the price is right department: "The personal information of more than a billion Indians stored in the world's largest biometric database can be bought online for less than $8, according to an investigation by an Indian newspaper."

mircea_popescu: http://btcbase.org/log/2018-01-04#1764246 << this is a very apt commentary on the value of 1bn orcs piled up together. ☝︎

a111: Logged on 2018-01-04 20:10 asciilifeform: ( likbez : all you need for the mythical holy grail, 'fast iron rsa', is a very large-bitnessed adder-cum-barrelshifter and a few storage registers that can be programmatically shuffled between. )

phf: mircea_popescu: 80col is such an old holiwar you're risking myself or ascii moving in a backyard and building defensive possitions, like those boys they bring from iraq do. "son, you can come out now, we showed those no break somsabeaches"

asciilifeform recently reread 'tigerfibel', really a megaclassic of technical writing for all time ☟︎

asciilifeform: the germans had a grammar, for shorthand of orders

mircea_popescu: we need a named item grammar.

ben_vulpes: http://btc.yt/lxr/satoshi/source/src/bitcoinrpc.cpp?v=makefiles#1848 << and fuck you if you want to make a command with a name more than 1char longer than "walletpassphrasechange"

mircea_popescu: this is not even a bad argument. fixwidth speeds scan for code for sure.

phf: c had a somewhat right idea with ident :p you feed a proggy in, it force formats it for you

mircea_popescu: only a coupla kb.

mircea_popescu will link here http://trilema.com/2017/how-the-beastforumcom-private-messaging-function-became-a-paid-user-only-item/#selection-83.0-83.18 because heh.

phf: so a dangle like that is an indicator. in fact a dangle like that usually exists in programs that don't 80 column. but sometimes a dangle like that might just be necessary

a111: Logged on 2018-01-04 23:45 phf: in a proper program 80 col is an indicator of s/n, density and all kinds of lateral properties, that can be communicated between professionals, because you can know ahead of time, what you're dealing with by shape, and have a rough estimate for the token count

phf: mircea_popescu: you don't necessarily need to introduce a break, http://btcbase.org/log/2018-01-04#1764371 ☝︎

phf: well, luckily mp doesn't produce v patches, so this a non-issue

phf: might need a screenshot, i'm not seeing that on my machine (or possibly also being dense)

mircea_popescu: http://btcbase.org/log/2018-01-04#1764226 << either that or "either you produce a naked female employee on her knees right this second, or else your fucktarded shenanigans just cost you a 580% salary increase for being a bunch of repugnant scum" ☝︎

mircea_popescu: phf a 120 col line will contain a number of words distriburted around 23.7 ; this means your spaces being elastic works to some degree. i will hold up trilema as an example of this, would you say elastic spaces are not working for it ?

phf: when you eliminate hyphenation as a concern, you're just left with elastic spaces, but you don't have those in monospace plain text. you just have full sized spaces, but their granularity is so high as to be almost useless

mircea_popescu: the rules for adding multiple xn together are more complex than straight addition, but not complex enough to manage a positive out of negatives.

mircea_popescu: anyway, re the naggum quote above : a better statement would be to say that every problem comes with an iq functional which could be approximated as a (x-fiq)^3 + b(x-fiq) ; the a, b and fiq are parameters of the problem, the x is where the solver's iq goes. if his iq is lower than the fiq required by the problem, his "work" comes out negative.