log☇︎
143400+ entries in 0.74s
mircea_popescu: ima have diana_coman put the whole eulora crypto in vpatch form even if we're not yet advanced enough with the cleaning of codebase to use v properly.
asciilifeform: afaik there's nothing peculiar re the vdiff. lemme know why your parser barfed, phf , when you find out
mircea_popescu: well anyway, this'd be a great time to go through the slag, "items that didn't work list" see what other mpis are in there
phf: mircea_popescu: i briefly had it, but removed it due to lack of use (it also predates the sbcl rewrite, so it was particularly janky code)
asciilifeform: phf: if your thing wasn't able to parse it, i'd much like to know why
mircea_popescu: phf do you have roughly the equiv of a "feed paste in here" slit for it ?
asciilifeform: and it's a perfectly legit ( manually ground, from mpi, just like trb genesis was from 0.5.3 ) genesis.
mircea_popescu: maybe his thing didn't eat it for some reason. ☟︎
phf: oooh, well, that fixes that then
asciilifeform: tarball contains 2 files, the genesis, and sig
phf: or is it? i might've missed that part
phf: mpi-genesis.tar.gz is not a vpatch though
mircea_popescu: i had thought i saw a genesis too.
phf: but oftentimes when i post a patch something comes up anyway. like the recent mpi release by asciilifeform is a vpatch, but it lacks a genesis, which breaks all kinds of assumptions (e.g. the tree visualizer wouldn't work at all)
mircea_popescu: alright so then is this structure deemed seaworthy for a while ?
asciilifeform: this is not necessarily a bad thing
phf: correct, so far there's not been any editorializing. even dead vpatches live in their own patchset
mircea_popescu: so then, it's more like a sort of curated "Best of" blogposts eh ? you go around reading people's blogs like the editor of old science mags, going "plox put this in format for editorial"
asciilifeform: ( jurov's apparatus worx great. but it only introduces messages to the ml. )
phf: manual meaning that i see a vpatch in any random place, i post it (obviously it benefits me, more content etc.) ☟︎
phf: it is still manual process, and we've had a thread about it along the lines of "build it when there's need"
mircea_popescu: how is vtron currently fed, via email list thing jurov made ?
mircea_popescu: phf nothing wrong with that.
phf: well, that's fine by me, i think what happened is some other conversation got crossed over into what i was thinking. alf said you gotta publish, to which i responded with a very non committal "i'll think about it". but there were parts that i was thinking of publishing. specifically vpatch parser and presser both of which don't really on external tools, but accomplish the whole thing in memory. might be useful for further vtronics
mircea_popescu: so the desired interop with wp would look like what ?
mircea_popescu: and so the problem there was what ?
asciilifeform: and moar recently the db timings experiment
asciilifeform: the 'wires' thing
mircea_popescu: asciilifeform when was that last ?
mircea_popescu: asciilifeform how would you see it interoperate ? there's links in html, is more needed ?
asciilifeform: hey i still to this day use jurov's system, whenever submitting trb patch.
mircea_popescu: what exactly did happen ? phf wrote a fine v parser ; jurov sweated white hairs getting an email system into alf-tip-top shape only for it to not be used as soon as it was got to work...
mircea_popescu: he wrote it, let him run it, and not be discouraged by "not forthcoming" or w/e happened there.
mircea_popescu: why would you build something else instead of using the something that already is ?
asciilifeform: in this particular case, so that something else can be built from same parts
mircea_popescu: i'm not sure what the benefit of publishing would be. so what, someone else runs it or what.
phf: i'm not sure what publishing the whole thing entails, the only bit that i even considered is something along the lines of what trinque did with his irc bot
mircea_popescu: fine, so i read 'em when they were absent, woe unto me.
a111: Logged on 2017-11-15 17:59 phf: asciilifeform: no haven't published it, it's a big ball of mud that in the gran lisp machine tradition lives in TMSR package, along with log bot, log visualizer, log database, etc. so if there's interest in any specific parts i can extract them into library and publish, but i've not been planning on publishing the whole thing
mircea_popescu: now, which of these two didn't you have in mind with http://btcbase.org/log/2017-11-15#1739048 cuz i read both in there. ☝︎
mircea_popescu: neither of these are good outcomes.
mircea_popescu: there's two major management problems with publishing : one if it's done heathenly, like alf does it, pastes and whatnot ; the other is subjective, "i published it so it's no longer my thing".
mircea_popescu: don't resent it ; instead, let's examine what this "ima publish" entails.
phf: i resent the "sorta works" bit, i've been responsive with any feedback related to log and patch visualizer. i've not read todays log so maybe i missed how /patches fits into greater scheme of things
mircea_popescu: are you gonna start charging for it then ?
phf: mircea_popescu: no, publish meaning put relevant parts into patch visualizer, i otherwise haven't published anything. log/patch visualizer is presented as a service, as far as log is concerned the philosophy has been "write your own" and there's not been much interest in the v part until now
mircea_popescu: or did you just make to try and ruin the republic thereby, "here's an engine, it sorta works, im never making it work correctly haha and fuck you" ?
mircea_popescu: "i've not been planning on publishing the whole thing" << why not, are you planning to what, sell it ?
mircea_popescu: so that THIS also becomes an "unowned random bit of nothing" and we just sink into idocy ervery year a little deeper ?
asciilifeform: mircea_popescu: how's that
phf: mircea_popescu: it is (though there's an interruption in the chain that i need to regrind) that doesn't help me though, because it's the whole thing, rather than parts.
mircea_popescu: gah. i feel like in a spider web, every move to improvement resulting in worse shittifyication.
asciilifeform: the www viewer thing.
asciilifeform: aha, that's what it was called. the item which i suspect is 99% of what draws the heathens into 'git' etc
phf: like a kind of vpatch gitlab thing, ok i'll think where and how to slice
asciilifeform: but ideally yes whole thing
asciilifeform: phf: consider at the very least sawing off the code parser and entire set of items that pertain to www
phf: i think it might be worthwhile to publish for example vpatch parser and presser machinery though
phf: asciilifeform: no haven't published it, it's a big ball of mud that in the gran lisp machine tradition lives in TMSR package, along with log bot, log visualizer, log database, etc. so if there's interest in any specific parts i can extract them into library and publish, but i've not been planning on publishing the whole thing ☟︎
asciilifeform: aside from 1 nitpick, the charts overflow my screen
phf: basically the tree viewer is half baked and i'm not eating my own dog food here, so i'm relying on teh public to give me feedback ("phf fucking fix this fucking thing") which so far has not been forthcoming
asciilifeform: might be a considerable head start for item in this thread
mircea_popescu: phf i dunno, if there is slow to uptake.
asciilifeform: hey phf -- you ever published the v-viewer ?
a111: Logged on 2017-11-15 17:19 asciilifeform: this item calls for something like phf's v-viewer
phf: http://btcbase.org/log/2017-11-15#1738923 << the underutilized part of patches visualizer is the tree view, it shows what specific file will actually look like when pressed with a specific patch, e.g. http://btcbase.org/patches/programmable-versionstring/tree/bitcoin/src/crypter.cpp as you can see formatting is not particularly good, but it supports highlighting various languages including Ada. so given a normal v-based workflow (is there one?) can get ☝︎
mircea_popescu: (the a above may seem minor, but both apeloyee and some random noob yest ran into th eexact problem. only one survived it far we can tell.)
mircea_popescu: there's also c) where it helps the mind mature into something that'll eventually be able to usefully v, but that's a secret.
asciilifeform: eventually will have to sit down and write it, if no one else rises to it
asciilifeform: i'd even settle for a very low-tech, orcish thing, that lives as emacslisp and shits out a wp post .
mircea_popescu: the important points here are a) scheduling. if we're in the middle of a conversation, low ranking rando won't make any friends by dumping comments re paste. if you had the decency to put it on blog, he can leave you a comment, which you can read when you have the time. major efficiency boon for everyone.
asciilifeform: not afaik written tho.
asciilifeform: but yes such a thing is writable.
mircea_popescu: ok so then.
asciilifeform: it also has to have some notion of ada scope.
asciilifeform: but entirely possible to write.
asciilifeform: it has to parse the ada.
mircea_popescu: wp module to do that is one page long.
asciilifeform: this avoids breaking flow in the reader's head.
asciilifeform: references to code outside of the current page, oughta be automatic links
mircea_popescu: asciilifeform who is going to read anything but non-auto adnotations.
mircea_popescu: oh thank you mp, i see now what you had been trying to tell me for the past two hours because that's the sort of a mind i am. will fix now!
asciilifeform: does a good bit moar of the job, than pasting a txt ( into wp or otherwise ) and manually grunting to annotate.
mircea_popescu: http://trilema.com/2017/how-the-beastforumcom-private-messaging-function-became-a-paid-user-only-item/#selection-91.5-95.0 << hey mp, shouldn['t this 12 read 19 instead ?
asciilifeform: it's still a fail. but at least has the notion that routines are entities that oughta be pointable to.
mircea_popescu: it does none of the job.
asciilifeform: in the given hack, you can't. hence i said 'does half the job'
mircea_popescu: thing has no way to underline byte error from tester to author and you give it a passing grade ?
asciilifeform: ah you meant the actual c pointed-at, vs the definition
mircea_popescu: no. how do i link the c.
mircea_popescu: how do i do anything beyond "here's a doodle, click 80 times in inept trees of documents like it's 1980 all over again and steve jobs hasn't yet come to put into abject slavery all sorts of retarded academiacs who really thought they had something to say" ?
mircea_popescu: how do i adnotate the s ?
mircea_popescu: how do i fucking link the c ?
asciilifeform: it won't win artistic awards but does about half of the job
mircea_popescu: basically, looks like a tripod site. if i want to link you to the "c" in Read(s,c); what do i do ?
a111: Logged on 2013-12-03 23:49 ThickAsThieves`: It's hard to explain puns to kleptomaniacs because they always take things literally.
asciilifeform: it doesn't do the hierarchical or line-numbering thing tho
asciilifeform finally dug up link to what asciilifeform sees as state-of-the-art wwwtronic ada viewer : http://unzip-ada.sourceforge.net/za_html/index.htm ( they're auto-generated per project )
mircea_popescu: which is why it's even interesting to have one as an intellectual activity.
mircea_popescu: asciilifeform neh, because it's your fucking blog, reflecting what you know when you write it not what you come to find in writing it