log☇︎
27300+ entries in 0.17s
mircea_popescu: asciilifeform so did i! point in case : http://btcbase.org/log/2018-08-28#1845190 so far, they haven't! ☝︎
asciilifeform: mod6: i dun like to discourage folx, esp. mircea_popescu's pupil, who is evidently pouring sweat into the job. but i expected the items would get better with time, and imho so far they haven't ☟︎
mod6: asciilifeform: yeah, i've been trying to keep up with bimbo.club
asciilifeform: i did not say anyffing re 'trinque is upgrading to 486DX2 for alf', but it prolly merits a mention also.
asciilifeform: unrelatedly, am i the only one who reads these, http://btcbase.org/log/2018-09-19#1851562 ? some of these have atrocious mistakes, e.g. 'flashing the uboot with the dram from vendor did not do anything detectable' << rom, not 'dram', lol ☝︎
asciilifeform: phf: plox to correct me if i'm wrong here
a111: Logged on 2018-09-19 14:42 mod6: Before we embark on an entire regrind of the trb-vtree to use keccac, I think we just need a major release version of a "defacto" vtron that supports both SHA512 (for other legacy projects) and keccac. Sounds like phf's might fit the bill, but want to ensure that when the Foundation tackles this problem, it's on very stable footing.
BingoBoingo: Pull the invoice off of the Amazon orders page and get it to me. I want to show the fuckers the line for the import tax deposit.
BingoBoingo: asciilifeform: Well, I am still waiting on a birthday card from February sent through the post ☟︎
asciilifeform: if new vtron allows mechanical preservation of ~continuity~ , i.e. i can determine mechanically that a reground tree is in fact same as the old but-for-the-hashes, then all is ok. but if not, this'd be essentially same as throwing past 3rs of historicity away. ☟︎☟︎
asciilifeform: diana_coman: i like the new v format, but i also very strongly wish to avoid coming to resemble the urbit people, with their 'aah we restarted the universe for the 7th time' ☟︎
asciilifeform: BingoBoingo: i suspect that lulazon simply pockets that 62.18, and the orcs never see it; or alternatively, an orc pockets, off-record, and then pretends 'was 1 of 2 max free imports'
asciilifeform: betcha if i'd mailed'em wrapped in old newspaper in a standard letter envelope, you'd already have'em, and we could be fiddybux richer. ☟︎
asciilifeform: wtf is even the point of lulazon collecting it, if result is exactly same as if i mailed the crate myself
BingoBoingo: I was under the impression that there is a limit of 3 tax free imports under $200, which should not be relevant considering there's an import deposit
asciilifeform: BingoBoingo: lemme know how it goes. this is 1st time i hear of any such thing re 'can only have 2 imports'
asciilifeform: but will note, the situation where i gotta keep multiple vtrons around, one for this-here, one for that-there, ( ftr i've been using my orig since aug '15 ) is imho suboptimal.
asciilifeform: diana_coman: entirely fair point. i simply dun have the new one in my workflow yet, is all
asciilifeform: i dun even disagree with mircea_popescu's 'if it's still alive, it oughta be reground' item. but at the very least oughta be able to read the old trees with new tool and determine that somebody's regrind is actually bit-identical to the original, without burning several days per instance
diana_coman: fwiw I was talking strictly of *new* stuff for now; notice that I did *not* regrind eucrypt either - that can wait; new stuff however should use keccak imo
mod6: Before we embark on an entire regrind of the trb-vtree to use keccac, I think we just need a major release version of a "defacto" vtron that supports both SHA512 (for other legacy projects) and keccac. Sounds like phf's might fit the bill, but want to ensure that when the Foundation tackles this problem, it's on very stable footing. ☟︎
mod6: To me, I'd like to see just one trb-vtree, one set of patches. And if that means moving to keccac, then we will, and that'll be the only set of vpatches that The Foundation will distribute. (Otherwise I think it's too confusing, and time consuming to publish future vpatches in both.)
asciilifeform: unless of course both inside ~same~ nat ( i.e. on 1 lan )
asciilifeform: i also suspect that results will differ when 1 box is behind a konsoomer nat thing, vs. when both ends are 'adult' (naked ipv4)
diana_coman: once it's ready, I'll publish it anyway and I don't see any reason why one couldn't run it anywhere they want it, ofc
asciilifeform: ( and i'd like to try from here, also )
diana_coman: anyways, will wait for mircea_popescu to weigh in on this too; atm I still need to set up the main stuff and then those are params to adjust/set as required
asciilifeform: i suspect that the experiment could expose backbone diddlage..
diana_coman: not a bad idea at all; at it's simplest I was thinking simply serial numbering the payloads and logging on both sides since putting together the 2 logs afterwards is straightforward, 1-line thing
asciilifeform: diana_coman: the way i'd do the size shuffle, is to use a kindergarten prng (e.g. mersenne) for repeatable sequence, and put ~in~ the packets, a serial num. then simply record what comes out. ☟︎
asciilifeform: you would have to make small change tho, to make it report size, mine does not ( only 'valid' , i.e. full size, or 'invalid' )
diana_coman: atm I'm just playing around with generic to wrap my head around it! lol; but receiver can haz max size and then report, no?
diana_coman: asciilifeform, yes, atm I'm looking at it for the test harness, for which I think it fits great (since I wouldn't want to go writing 1-65535 explicitly if I can help it)
asciilifeform: did i also somehow sleep through this
asciilifeform: would also like to have (but afaik we dun have?) a mechanical converter from old to new, so that all i gotta do is re-seal
asciilifeform: i'm not averse to regrinding things, vtron that understands 2 types of hash inside 1 tree is prolly too much to ask for; but at the very least i gotta be able to distinguish old form from new by file ext., for own workflow.
diana_coman: I can fully see the point to that, certainly
diana_coman: asciilifeform, I can see the point given how often I went already "oh, this is /not is keccak/sha"
diana_coman: asciilifeform, not full as far as I'm aware; there is http://trinque.org/2018/06/02/v-manifest-specification/ re manifest
diana_coman: possibly because I did not yet fully digest the new one (or not as well as old one)
asciilifeform: but why not as convenient, i meant
diana_coman: I pressed only the keccak branch of phf's
asciilifeform: i thought phf's was backwards-compat?
diana_coman: and I actually have both on for now, hence yeah, I just pressed your patch with old V
diana_coman: asciilifeform, I know that pain, honestly; I still trip over this change and I wouldn't even say that I have as convenient a workflow with new tooling as I had with old
diana_coman: cool; I was just surprised + trying to understand what is going on
asciilifeform: again i had and have 0 objection to the format, or would have said.
a111: Logged on 2018-07-08 00:14 asciilifeform: i expect that errybody currently tuned in, will use keccak.
asciilifeform: diana_coman: i'm satisfied that your keccak worx
asciilifeform: diana_coman: i'm not averse to regrinding , if diana_coman already switched ( i managed to sleep through this , somehow, but yes looks like you're in the new format )
diana_coman: the issue at hand is more simply that being sha means it will have to go through regrind at some point and so I'm not very keen on adding to it patches just to have what to regrind later; but maybe that's just me
a111: Logged on 2018-07-06 23:15 phf: considering the slow adoption of the keccak approach and also a large number of existing sha512 patches, i'm planning on doing a regrind where i merge the keccak and the sha branches together, so that vpatch/vdiff can produce both hashes on a switch, until further notice.
diana_coman: I wouldn't expect there is such a thread, no; at any rate, last discussion on this I think starts here: http://btcbase.org/log/2018-07-06#1832406 ☝︎
diana_coman: asciilifeform, I don't get it: are you saying you need mircea_popescu to officially declare it something or the other or what?
asciilifeform: diana_coman: but to answer the orig q -- i have nuffin against the new format; but not switched yet.
asciilifeform: diana_coman: and if there was a moment in the l0gz where mircea_popescu proclaimed 'hey this is out of beta, errybody plox to retire the classical vtrons' -- i missed it? plox to link.
asciilifeform: diana_coman: believe or not, i still havent switched to phf's .
diana_coman: asciilifeform, since your udp genesis is using the sha hashes + a "history" file I'm not sure: do you have something against the move to keccak + standard manifest file for v-trees?
Mocky: yes, doesn't apply to visa on arrival which i'll be using. but if i want to stay past 60 days need some sort of business sponsor or hotel sponsor. and if use sponsor, their failure to file paperwork will prevent you from leaving
Mocky: i'm a noob to international travel, but the whole exit visa thing seems super sketchy to me
a111: Logged on 2018-09-01 17:06 mircea_popescu: i figure... you get what 2 ? 3 ? months there until the first save point, see if it can be done or can't be done ?
asciilifeform: Mocky: way back ? i thought yours was a 1way
Mocky: on the way back I'll have 3 hrs in madrid and 3 in miami
BingoBoingo: <Mocky> got my flight booked. will be on layover at heathrow for 15hrs on oct 8th << I don't feel so bad about the 45 minutes I ended up with in Panama now
Mocky: never been to London before, but from what i hear, can practice my arabic with half the population
asciilifeform: or possib this was one of those degenerate harems that morphed into a sort of harvard, i.e. institution that popped its tether to whatever original ground it stood on
asciilifeform: i have nfi how this passed 'qa' for 'harem'. but i suppose 'in the great birdlessness, my arse is a nightingale'
mod6: lol, i remember these, that one lady looks like Jay Leno.
asciilifeform: http://www.xubux.com/upload/000/u1/013/4781adf0.jpg << i def saw this, in a b00k, must be
asciilifeform: for another gen or 2, i'd imagine yes
asciilifeform: btw how do i say копошиться in ro
mircea_popescu: "if my typo fix contains a typo" i mean
mircea_popescu: this way i fucking hear if my typo is typo'd.
asciilifeform: ave1 was asking re scenario where 'say i make pdp11.c for yer lib, and you changed the ada trunk, naowat'
a111: Logged on 2018-09-18 18:19 asciilifeform: this is the inevitable cost of v, you gotta weigh 'i can fix this typo, but 5 people will need to either regrind or abandon my tree'
asciilifeform: btw one of the items i have in the deep freezers, is a trb with block db ripped out, replaced with (half-finished, sadly) ada mmap thing
asciilifeform: prior to all of this i had gargantuan makefiles, that called out to various shellisms that turned out to flake on e.g. bsd
mircea_popescu: i think there's three previous instances on the whole net of "i dun miss gnumake"
asciilifeform: gprbuild is spiffy, incidentally. i dun miss gnumake at all.
mircea_popescu: i dun see a problem with that bit, either.
asciilifeform: currently i only use it to toggle debugflag vs adult build, and that's prolly the beginning and end of the valid use case imho
asciilifeform: mircea_popescu: right, i dunlikeit
mircea_popescu: http://btcbase.org/log/2018-09-18#1851358 << imo this is a very stupid way to go about it ; first and foremost for the reason given (why am i signing ifdefs i do not run) but there's also others. ☝︎
a111: Logged on 2018-09-18 18:09 ave1: I don't know about the different v-trees for this, I'll have to think about it
asciilifeform: ah i misread
asciilifeform: certainly nao is ( currently under conversion to a sort of discount bagdad, as i understand )
asciilifeform: i have nfi how, but it all evaporated. and mircea_popescu's hypothesis as as good as any.
asciilifeform: ftp, i can see, telnet, but -- why this.
asciilifeform: ftr i never grasped why irc is a tcp item to begin with. it aint as if the messages outweigh the available bucket.
asciilifeform: and this is one of the few i know of
asciilifeform: typically i'm reluctant to open the hood on things that aint broken, tho
asciilifeform: i'm using an ancient gtk1 thing for irc on this box, and loathe to pry open its rusted hood
asciilifeform: i.e. 'harem matter'
mircea_popescu: nobody sane, i mean.
asciilifeform: i cut off the tcpism, cleaned up, turned into 'udp' lib
asciilifeform: mircea_popescu: funnily enuff, the proggy for which i originally wrote the thing , was one
a111: Logged on 2018-09-18 18:03 ave1: I was working towards having different modules on top of a common base to support tcp / unix sockets etc. but I think your idea is way better, asciilifeform http://btcbase.org/log/2018-09-18#1851315
mircea_popescu: http://btcbase.org/log/2018-09-18#1851334 << i also can't think of a thing that would legitimately need/want to use both tcp and udp as a toplevel thing. ☝︎
asciilifeform: mircea_popescu: lol, i assumed was typo from 'wraiths'
a111: Logged on 2018-09-18 16:52 lobbes: Detailed update on step 3) referenced within: I have finished designing/building out/testing the underlying table and field structure (I ended up migrating the underlying db to postgres in lieu of sqlite, and so far am glad I did). Right now I am in the thick of the re-tooling of my old coad. Still looks to be on-track for Oct 31st delivery, but I will keep folx updated