log☇︎
530 entries in 0.678s
mod6: and esthlos
trinque: esthlos: I'd rather let you perform whatever changes to this thing, so I can keep working with gentoo entrails.
trinque: esthlos: nobody here is using a 2.x gpg
asciilifeform: esthlos: you don't need to convert keys to switch from 2.x to 1.x
trinque: esthlos: there's also no sense in giving the thing a version number. the "version" is the patch the operator pressed to.
trinque: esthlos: http://btcbase.org/log/2018-05-18#1815256 << yo, what of this, and the other things addressed to you? ☝︎
a111: Logged on 2018-05-17 03:28 deedbot: http://blog.esthlos.com/esthlos-v-prerelease/ << esthlos - esthlos-v Prerelease
deedbot: http://blog.esthlos.com/esthlos-v-prerelease/ << esthlos - esthlos-v Prerelease ☟︎
ben_vulpes: esthlos: it is very useful to leave them around; the kb wasted in /tmp are negligible and useful in edge case failures
trinque: esthlos: how goes it?
ben_vulpes: esthlos: i made a gensym dir in /tmp, passed that to gpg for the workdir, and then various operations take a teardown key, defaulting to true which could be overriden to inspect keyring state should the operator so desire
ben_vulpes: esthlos: yeah, that's what i did and i think asciilifeform as well
trinque: esthlos: I don't think anyone demands you use precisely that name, if doing so results in more needless complexity than just picking another.
asciilifeform: esthlos: have you considered reading my original v ?
a111: Logged on 2018-05-09 18:36 hanbot: esthlos : your blog's comments are borkt (commenter sees 'Error: please fill the required fields (name, email).' despite entering fields), see the "edit" here for the fix http://thewhet.net/2017/10/a-compendium-of-possibly-helpful-stuffs-for-erecting-mircea-popescus-wordpress-with-nearly-free-speech-hosting/
hanbot: esthlos : your blog's comments are borkt (commenter sees 'Error: please fill the required fields (name, email).' despite entering fields), see the "edit" here for the fix http://thewhet.net/2017/10/a-compendium-of-possibly-helpful-stuffs-for-erecting-mircea-popescus-wordpress-with-nearly-free-speech-hosting/ ☟︎
deedbot: http://blog.esthlos.com/esthlos-v-version-2/ << esthlos - esthlos-v Version 2
deedbot: http://blog.esthlos.com/a-brief-overview-of-eucrypts-mpi-library/ << esthlos - A Brief Overview of Eucrypt's MPI Library
deedbot: http://blog.esthlos.com/mp-wp-setup/ << esthlos - Setting up mp-wp
deedbot: http://blog.esthlos.com/a-vtron/ << esthlos - A Vtron
asciilifeform: esthlos: i wrote to him and he actually showed up. but didn't stick, apparently he prefers the sad loner life
trinque: anyhow esthlos most folks here (I assume) slam their lisp code through a formatter at each return, or similar
asciilifeform: esthlos: is there a particular reason you stuffed it in a tgz, rather than to leave it web-readable ?
a111: Logged on 2018-05-08 15:47 ben_vulpes: also esthlos what's with the linefeeds and extreeeeemely wide codeformatting?
esthlos: http://blog.esthlos.com/esthlos-v-version-2/ << I'm using tabs as 4 spaces, and I see the code as <80 col. what's your set up?
trinque: esthlos: ah neato. I need to get you into the RSS list.
esthlos: trinque mircea_popescu phf ben_vulpes mircea_popescu et al: http://blog.esthlos.com/esthlos-v-version-2/
ben_vulpes: also esthlos what's with the linefeeds and extreeeeemely wide codeformatting? ☟︎
ben_vulpes: esthlos: also needs a build script to produce a binary for use outside of a LISP repl; my lisp v implementation ran afoul of this years ago. ~nobody would fire up a lisp repl to test the thing. this may be different today, but the fact remains that for this to make it into widespread use it's going to need to be callable from the linux cli.
ben_vulpes: esthlos: i would like to see it complain loudly if it finds a bad signature, not merely look for some good ones
ben_vulpes: esthlos: ^^
ben_vulpes: esthlos: seems your v doesn't take a head to which to press, but implicitly presses whatever comes out of the toposort; this is incorrect and the operator needs a lever there
ben_vulpes: esthlos: where do you want input? comments on a-vtron ?
trinque: did phf or other lispers have commentary on esthlos' item? ben_vulpes? asciilifeform?
trinque: esthlos: ah ok, thought run-program was coming from uiop. sounds like sbcl, cmucl, and ccl would be the desired targets.
deedbot: trinque rated esthlos 1 << lisp vtronicist
mircea_popescu: esthlos, people throwing their hands in despair over something [they thought] you said is always way the fuck preferable to people throwing up their hands in despair over something you did -- specifically because there's a lot more room to misinterpret what's said than what's done.
a111: Logged on 2018-05-03 01:15 mircea_popescu: esthlos, a) http://btcbase.org/log/2018-01-23#1774760 ; b) how does your item handle the original http://btcbase.org/log/2018-04-09#1794417 problem ?
esthlos: mircea_popescu: wrt http://btcbase.org/log/2018-05-03#1807632 << esthlos-v presses fine to vtools_vpatch_newline ☝︎
esthlos: trinque: updated file at http://files.esthlos.com/crypto/v_2/v.lisp , sig at http://files.esthlos.com/crypto/v_2/v.lisp.esthlos.sig
trinque: esthlos: so at least less to change about your v-tron right? though definitely *read* the others so you're more certain you understand what the thing is.
mircea_popescu: esthlos, what sort of barbarian, orcish, utterly insane and self-spiteful approach is this, whereby you set forth to do a thing without understanding the previous iterations of the thing you're doing ?!
ben_vulpes: esthlos: did you read mod6 or asciilifeform's v implementations before writing yours?
a111: Logged on 2018-05-06 23:21 esthlos: alright. What I don't understand, then, is mircea_popescu's response
a111: Logged on 2018-05-06 23:13 esthlos: if the new V defines the current state of the project as a single hash, then multiple parents (such as h, i, d, and j) becomes impossible
trinque: esthlos: if I thought you'd gone that far afield, I would've asked you to do all this instead of a simple cleanup of interfaces
mircea_popescu: esthlos> looking to cement understanding: with current V, file-level merges are impossible << huh ?
trinque: esthlos: you are misunderstanding it entirely
a111: Logged on 2018-01-23 14:28 mircea_popescu: esthlos it is not standard procedure ; the emerging consensus is to have a dedicated philosophy file which a) all patches must touch (by protocol) ; b) contains comments as to the patcher's state of mind and c) contains one line per patch uniquely identifying it, machine generated. the format's not fixed yet, but as phf is working on a new proper vdiff it's probably going to coalesce around a variant of whatever he uses.
a111: Logged on 2018-01-23 12:09 esthlos: to determine if b.vpatch descends from a.vpatch, my idea is to scan through b.vpatch and ensure that each ---(file,hash) matches some +++(file,hash) in a.vpatch. is this the standard procedure?
trinque: esthlos: that's incorrect, current V does not press all leaves
esthlos: esthlos-v doesn't touch on (a); I was indeed waiting for standardized philosophy file format. (b) I will test
a111: Logged on 2018-01-23 14:28 mircea_popescu: esthlos it is not standard procedure ; the emerging consensus is to have a dedicated philosophy file which a) all patches must touch (by protocol) ; b) contains comments as to the patcher's state of mind and c) contains one line per patch uniquely identifying it, machine generated. the format's not fixed yet, but as phf is working on a new proper vdiff it's probably going to coalesce around a variant of whatever he uses.
mircea_popescu: esthlos, a) http://btcbase.org/log/2018-01-23#1774760 ; b) how does your item handle the original http://btcbase.org/log/2018-04-09#1794417 problem ? ☝︎☝︎☟︎
esthlos: trinque: you can find my writeup at http://blog.esthlos.com/a-vtron/ . I recall you wanted to have the thing return sane data from ops instead of format barfage
a111: Logged on 2018-05-01 16:29 mircea_popescu: but we have esthlos waited on a fix, and then there's whatever you were waiting to publish. so i'm guessing it'd have to be one of you.
mircea_popescu: trinque, alright, then that's the plan here, you and esthlos come up with a v i can point people at when they have to publish ; you can test it by publishing whatever it was you were about to on it, and there we go.
trinque: mircea_popescu: I am entirely willing to help esthlos finish his V
mircea_popescu: mod6, there's no rush there, esthlos had 90% of a working lisp v, i expect it can be tweaked into a deliverable. can have ada v later on.
mircea_popescu: but we have esthlos waited on a fix, and then there's whatever you were waiting to publish. so i'm guessing it'd have to be one of you. ☟︎
mircea_popescu: esthlos, did you see the recent discussion re polardbeard's sad failure to participate ?
asciilifeform: esthlos: i recommend to take vtron and experiment with it until you grasp how it works, it will click in your head quickly
asciilifeform: esthlos: correct
asciilifeform: esthlos: picture if you substituted a different block for block#2 of bitcoin.
mircea_popescu: esthlos, it's very centrally how the v mechanism is intended to / works : you get to opt which patch trees to continue, much like in the case of bitcoin.
asciilifeform: esthlos: do you understand that v, deliberately and as a fundamental design choice, has no merging ?
mircea_popescu: esthlos, you wouldn't make it a patch on genesis unless you were trying to signal your disdain for diana_coman 's work so far.
asciilifeform: esthlos: when folx do as you described, it is called 'regrind' and is very labour-intensive, and is never done without a substantial reason
diana_coman: esthlos, there is no such thing as "crud never existed" ; we are not re-writing history here wtf
asciilifeform: esthlos: yer missing, i suspect , whole point of v
diana_coman: esthlos, well, it ultimately depends on your vpatch (what it does *exactly*), neh? chopping off some unused and moreover useless parts is valuable but a. it needs to be done making sure that nothing breaks b. mpi is and will still be a pile of shit
diana_coman: esthlos, eucrypt does not use this "secure" ; as per http://www.dianacoman.com/2017/12/28/eucrypt-chapter-3-miller-rabin-implementation/#selection-153.194-153.864
diana_coman: esthlos, no such thing as secure memory really
asciilifeform: esthlos: it was gonna, then barfed and abandoned mpi 4evah
asciilifeform: esthlos: imho absolutely not; i haven't built a linix box with swapping to disk enabled, in decade+ ( 'secure alloc' simply means 'marked unswappable' ) ☟︎
hanbot: esthlos: mazel tov, thanks for testing
esthlos: hanbot: said I'd get back to you: getting mp-wp running was relatively painless, most of my issues were with LAMP. I wrote down most of what I did here: http://blog.esthlos.com/mp-wp-setup/
mircea_popescu: (lisp v implementation by esthlos )
mircea_popescu: http://blog.esthlos.com/?p=7 btw
lobbes: esthlos I feel like danielpbarron just resolved a similar issue >> http://btcbase.org/log/2018-04-16#1800429 ☝︎
a111: Logged on 2018-04-15 22:25 phf: esthlos: mysqli appears to be a force pushed buggy replacement for original php mysql driver (the usual "deprecated!!1" tricks, while missing features and introducing creative bugs)
a111: Logged on 2018-04-15 22:28 esthlos: yes, it's the latest gentoo nonsense.
ben_vulpes: esthlos: 7.1.15 has mssql in addition! http://p.bvulpes.com/pastes/OxsNy/?raw=true
ben_vulpes: esthlos: i see mysql and msqli flags for dev-lang/php-7.1.15 and just the mysql flag for dev-lang/php-5.6.34
phf: esthlos: mysqli appears to be a force pushed buggy replacement for original php mysql driver (the usual "deprecated!!1" tricks, while missing features and introducing creative bugs) ☟︎
hanbot: http://thewhet.net << lastest post (mod_rewrite ergo links not yet live, or i'd link y'all directly) is mp-wp_genesis. esthlos and anyone else who was waiting on this is encouraged to test it out --setting up a test blog-within-a-blog is gonna be a royal pita and cause yet further delays, so please do try it out, lemme know how it goes.
deedbot: danielpbarron updated rating of esthlos from 3 to 2 << met for sushi
danielpbarron: !!rate esthlos 2 met for sushi
mimisbrunnr: Logged on 2018-03-25 12:31 esthlos: mircea_popescu: is there a list of supported html tags for comments on trilema?
mircea_popescu: dumping http://www.esthlos.com/images/gaussians.png here for the archival.
trinque: esthlos: I want to comment on your post, but cannot.
esthlos: Hi all, I developed a vtron, writeup here: http://www.esthlos.com/posts/2018/03/17.html . I know I need a comments mechanism: next project is to get mp-wp working
mircea_popescu: but just like we don't do the esthlos "o hai guise, i contribute half hour every third week between my radiomodelling hour and my watching cheerleader sports in the den" github dev model, we also don't do the "we'll underwrite your complexity under our brand" torvalds approach.
mircea_popescu: esthlos i don't get it, you're going to take a stab "at it" ie making a textfile, the sort that only carries any sort of weight or importance if a) you're somebody and b) you're doing something important, in between whenever your fiat job permits you a few hours here and there ? ☟︎
a111: Logged on 2018-01-23 14:28 mircea_popescu: esthlos it is not standard procedure ; the emerging consensus is to have a dedicated philosophy file which a) all patches must touch (by protocol) ; b) contains comments as to the patcher's state of mind and c) contains one line per patch uniquely identifying it, machine generated. the format's not fixed yet, but as phf is working on a new proper vdiff it's probably going to coalesce around a variant of whatever he uses.
a111: Logged on 2018-02-26 00:39 mircea_popescu: douchebag ? spyked ? esthlos ? ave1 ? mats ?
a111: Logged on 2018-02-26 00:39 mircea_popescu: douchebag ? spyked ? esthlos ? ave1 ? mats ?
a111: Logged on 2018-02-26 00:39 mircea_popescu: douchebag ? spyked ? esthlos ? ave1 ? mats ?
mircea_popescu: douchebag ? spyked ? esthlos ? ave1 ? mats ? ☟︎☟︎☟︎
mircea_popescu: esthlos it is not standard procedure ; the emerging consensus is to have a dedicated philosophy file which a) all patches must touch (by protocol) ; b) contains comments as to the patcher's state of mind and c) contains one line per patch uniquely identifying it, machine generated. the format's not fixed yet, but as phf is working on a new proper vdiff it's probably going to coalesce around a variant of whatever he uses. ☟︎☟︎☟︎