← | Results 16501 ... 16750 found in all logged channels for 'f:diana' | →
(trilema) diana_coman: asciilifeform, read also next para as in any case there isn't much point to not do M-R if you do it at all
(trilema) diana_coman: that way I can at least see it, thanks for clarifying, jurov
(trilema) diana_coman: ah, so that's the part that was missing: there is no interest for an online interface
(trilema) diana_coman: sure, log in is a liability,fine; so no login, but it doesn't follow no online
(trilema) diana_coman: but then simply change the interface, following existing non-liability model; what am I missing?
(trilema) diana_coman: so to put this straight: are you saying that the model you describe (proxies directly wired to the order processing backed) would be a liability for CoinBr or what?
(trilema) diana_coman: it's anyway a realtime-without-guarantees afaik: it eats your order online, sure, but it processes it when it gets to it
(trilema) diana_coman: I got that part; my surprise was re why is "accepting gpg-signed orders online" a problem for coinbr given the working model of mpex
(trilema) diana_coman: jurov, admittedly I never used CoinBr so don't know much of its previous online presence but I always thought "online" for such a thing meant mpex-style i.e. anyway gpg-based , no?
(trilema) diana_coman: asciilifeform, I don't know if anyone asked - I've stated it in the blogpost in clear just the same
(trilema) diana_coman: yay, m-r on ffa; now I'll really have to schedule ffa feast during breaks from work, lol
(trilema) diana_coman: asciilifeform, authors seem to be with some Uni in London still so probably reachable, yes; but it's still an email first anyway, you know?
(trilema) diana_coman: http://btcbase.org/log/2019-01-27#1890343 -> a paper with actual content, ha! though I rather doubt the authors' statement that "the need for careful distinction between non-adversarial (or random) and adversarial primality testing is of course well understood in the cryptographic research community."
(trilema) diana_coman: anyways, I'm not pushing this strongly as "this is how I actually think it was" - as I said previously, I don't think I know enough to have much to say either way
(trilema) diana_coman: I suppose the argument is that they still were the same thing i.e. that the fineness & precision differences were not so crucial as to make the result essentially something else; I can see it as such and fwiw that'd have been the default way to see it - if not for all the experience of "things that people call X and supposedly is made out of same things as X but different in implementation"
(trilema) diana_coman: Mocky_, congrats; I guess.
(trilema) diana_coman: mircea_popescu, perhaps re clocks though I keep thinking that the cheap ones were as clocks as current smartphones are computers
(trilema) diana_coman: ahaha, I refrained from commenting because I thought "uhm, I have NO idea exactly HOW were those watches broken" but my first thought was that they were likely unpredictably broken i.e. each will show ~random hour rather than "time with x error"
(trilema) diana_coman: ugh; asciilifeform honestly, please walk through my working
(trilema) diana_coman: no hurry; if I have a mistake in there I certainly want to know
(trilema) diana_coman: unless I have a mistake in there
(trilema) diana_coman: that is my proof that always y= n-1 for a= n-1
(trilema) diana_coman: o.o "such that r is odd"
(trilema) diana_coman: alternatively: do you see a whole in my previous maffs?
(trilema) diana_coman: asciilifeform, ? mind working me through that? I might be thick here
(trilema) diana_coman: hm; it always says "prime" though by definition so I'm not sure *what* information is missed when you exclude it
(trilema) diana_coman: what information does it give?
(trilema) diana_coman: it is a leggit witness, yes; do you mean that it's not counted as it should be?
(trilema) diana_coman: asciilifeform, specific?
(trilema) diana_coman: http://btcbase.org/log/2019-01-25#1889973 -> didn't rummage as too late yest but woke up this morning with this: when a= n-1 step 2.2 aka y=a^r mod n becomes y= (n-1)^r mod n; using for instance binomial expansion you have (n-1)^r = n^r + rC1*n^(r-1)*(-1)+rC2*n^(r-2)*(-1)^2+....+rC(r-1)*n*(-1)^(r-1)+(-1)^r; since the whole thing was "mod n", of all those terms you are in fact left with only the last one, aka y = (-1)^r mod n ; r is odd so
(trilema) diana_coman: that's (-1) mod n so y= n-1 and then there's nothing to do at step 2.3
(trilema) diana_coman: asciilifeform, I even remember I did go with pen and paper precisely through this but I'd need to rummage through the old papers to find it again, ugh
(trilema) diana_coman: right, I'm looking at it
(trilema) diana_coman: i.e. which exact para in the book or wherever are you puzzled about
(trilema) diana_coman: asciilifeform, can you point me exactly to what you mean re n-2?
(trilema) diana_coman: hm, not off the top of my head
(trilema) diana_coman: well yes; but I was struck by why this particular thing to latch on; perhaps "easiest" and the approved anti-whatever or something but anyways
(trilema) diana_coman: certainly, but that was precisely what they kept "avoiding" at all costs; e.g. http://ossasepia.com/2018/12/10/my-talk-of-bitcoin-at-reading-uni/#selection-213.0-213.61 and their strongly-dearly held idea that "contracts can't be broken" pretty much
(trilema) diana_coman: perhaps a combination of "I'd much rather NOT have this responsibility so passing it to some abstract group/network HAS to be great" and "all people are ~same and X is a crook therefore all people are crooks therefore can't trust someone"
(trilema) diana_coman: this "trustless" echoes some students' insistence that it's "better to not have to trust someone" - I couldn't quite get to the root of it
(trilema) diana_coman: atm hands full so indeed, won't be able to do anything about it anyway
(trilema) diana_coman: anyways, I'll go and dig into the comms protocol some more
(trilema) diana_coman went and re-read the thread
(trilema) diana_coman: I suppose you can at least try and check whether standalone static might cure it, though still weird
(trilema) diana_coman: it sounds very weird
(trilema) diana_coman: but so uhm, it builds with a main fine but it fails if you try to build it as a lib - why?
(trilema) diana_coman: hm; earlier I used "standalone" as "standalone lib" because there is such a thing: it means precisely that it includes ada run-time
(trilema) diana_coman: asciilifeform, what do you mean by "build as standalone"?
(trilema) diana_coman: no, not needed (or not *yet*)
(trilema) diana_coman: hm, I did not have to look into this specifically
(trilema) diana_coman: what was the mmap headache?
(trilema) diana_coman: it was more of a confusion/mess rather than real problem as such
(trilema) diana_coman: if encapsulated too then it has to be dynamic but if not "encapsulated" then it can be static (and you need to link the ada libs with main proggy too)
(trilema) diana_coman: basically "standalone" lib includes the init and exposes it
(trilema) diana_coman: both ways work fine
(trilema) diana_coman: well yes, it has to: if separate lib (either static or dynamic) it'll have to call libnameinit otherwise the adainit
(trilema) diana_coman: pretty much all ways tried and can be done
(trilema) diana_coman: yes! I can link it static, I can link it dynamically, I can even build it all as a monolithic piece
(trilema) diana_coman: re client/server: client is ALSO cpp+ada at the very least
(trilema) diana_coman: for about 3 months per year I like it; then I want about 3 months per year of hot sun too; and preferably also 3 months of autumn at least; kind of tall order nowadays
(trilema) diana_coman: even nice, huge, fluffy snowflakes, quite winter-like for once
(trilema) diana_coman: asciilifeform, kind of both ends at the same time because it's a communication protocol so..
(trilema) diana_coman: aaaand in unrelated news: it's SNOWING! ha! england will soon stop to a halt for there is 1mm of snow on the ground!
(trilema) diana_coman: quite; anyways, now that I have on eulora server c,cpp and ada together, it's a whole new level of madness
(trilema) diana_coman: but I'm not even sure it's that really - more a sort of anti-tool in that it unloads complexity on the user to deal with rather than anything
(trilema) diana_coman: myeah, at best it doesn't ...scale
(trilema) diana_coman: empirically-known then ; to account for the theoretical possibility
(trilema) diana_coman: C/CPP also known as "half a million"
(trilema) diana_coman: http://btcbase.org/log/2019-01-21#1888880 -> this reminds me of "after first 10 languages or so, ALL the rest are really easy to learn" lol
(trilema) diana_coman: so at least you don't get surprises when you need to use them
(trilema) diana_coman: I suppose it might be worth adding some automated daily check at least connects? gives time of day/whatever? for unused units
(trilema) diana_coman: I guess it's hard to tell whether it wasn't rotten at that time already; for some reason (what?!) worse than the others aka not just the drive
(trilema) diana_coman: so at first new drive it required several power cycles but then it seemed fine?
(trilema) diana_coman: did this one die with a sad drive too or was it changed before it really died on it?
(trilema) diana_coman: yes, I'm scratching here at anything at all; not much I can see otherwise
(trilema) diana_coman: or was it even possible to figure out what required it / what was the underlying issue?
(trilema) diana_coman: is that repeated power cycle something that was encountered before?
(trilema) diana_coman: did this RK died while being unused ? a log search for it shows only something in August last year - new master img deployed http://btcbase.org/log/2018-08-08#1840376
(trilema) diana_coman: trinque, is deedbot down?
(trilema) diana_coman: fine with me
(trilema) diana_coman: just not the git
(trilema) diana_coman: funnily enough it seems I even DID port over jurov's page too anyway, lolz; it was just the uy1 down thing
(trilema) diana_coman: basically we don't have a windows maintainer anymore; and yes, last parts in there were ~2016
(trilema) diana_coman: yes, it is uy1 being down
(trilema) diana_coman: ? it responds here?
(trilema) diana_coman: mircea_popescu, neah, it's that part that I did not move over to the html server because it wasn't up to date really
(trilema) diana_coman: wasn't that with old versions/unmaintained ?
(trilema) diana_coman: thanks! one of those days I'll get around to write-up the jam stuff for linking the lib with the client too ; at any rate, the linking seems sorted for now - it's Ada code for all the pieces that is missing
(trilema) diana_coman: at the very least, dubious messages if/when it gets them
(trilema) diana_coman: bot is in dire need of proper logging and once the new protocol is in place I can see the client itself needing to log stuff
(trilema) diana_coman: shinohai, an Ada lib for client-side logging would be quite useful
(trilema) diana_coman: asciilifeform, http://btcbase.org/log/2019-01-13#1886623 -> automate 1st stages of reach out at a very minimum, run it, analyse it
(trilema) diana_coman: myeah, that "into the black in two months" seems to me weird here; the trouble is not even "in two months" but at all; because it has been way more than 2 months and if it keeps going as is, I doubt 10 months would make a difference
(trilema) diana_coman: not to mention that it sounds to me that you'll potentially lose precisely those customers you want
(trilema) diana_coman: trinque, for s.mg it's less straightforward and it's not even just a matter of backups only; at any rate, it's at best "starvation mode" so I don't see how it really gets pizarro out of trouble; so far it's not even clear that *price* is the trouble re converting really; is it?
(trilema) diana_coman: trinque, my personal one no
(trilema) diana_coman: BingoBoingo, is your colocation price not competitive?
(trilema) diana_coman: and I still don't know how many...
(trilema) diana_coman: BingoBoingo, did you talk to your tech about automating any part of that?
(trilema) diana_coman: what is the duration of this update cycle or what is it exactly?
(trilema) diana_coman: if not ONE unlikely then..another! lol
(trilema) diana_coman: mircea_popescu, on a side note, that iii footnote is funny now "and while it is entirely possible someone strikes a multi-BTC jackpot, it is not altogether very likely"
(trilema) diana_coman: ugh, why is pizarro's tech finding out this only now!
(trilema) diana_coman: yes! I was basically waiting for something like that as a minimum re promised writeup review
(trilema) diana_coman: and for that matter what is in the pipe to add more to that db , anyway?
(trilema) diana_coman: BingoBoingo, but how *many* accounts did you message out of how many in the db, over what time, what filter(s) did you use and with what results?
(trilema) diana_coman: and in any case it'd be at best avoiding the problem rather than solving it so more agony down the line in all likelihood
(trilema) diana_coman: could pizarro even get in the green just by reducing the pipe? sharing rack sounds more like killing pizarro by definition
(trilema) diana_coman: I fail to find also a continuation to http://btcbase.org/log/2019-01-05#1884838 - > was there some discussion on this going forwards?
(trilema) diana_coman: how do you see that working before pizarro starves?
(trilema) diana_coman: mircea_popescu, re size it's actually going from ~95k current size of static standalone lib to ~800k size of same thing but "encapsulated"
(trilema) diana_coman: BingoBoingo, I re-read now that post with the idea in mind that it's meant to be the "fleshed out" version - it reads like a reasonable summary but I still fail to see the fleshed out plans going forward and esp re "try to drink the ocean" ; I followed the links and noticed the posts but I still get the impression those are only a few and/or manually done, is that correct?
(trilema) diana_coman: I still think it's a mess basically and I wrote it there like that with bullet points precisely because I know I will keep tripping over this so at least I know where to go to ...
(trilema) diana_coman: mircea_popescu, that's shinohai
(trilema) diana_coman: BingoBoingo, specifically and a bit of follow-up on trinque's point above: pizarroisp.net/2019/01/ has this tiny paragraph starting with "action items" - was/is that fleshed out anywhere?
(trilema) diana_coman: at any rate, the q was exactly that: a q for clarification; not finding fault
(trilema) diana_coman: mircea_popescu, hmm basically a client can end up "making an account" with Eve and not even knowing it/getting then stuck/receiving unexpected messages at next attempt with legitimate server; I'm sure a client can basically recover/notice in the end but it pushes a bit more complexity on client
(trilema) diana_coman: BingoBoingo, no select script on pizarro's blog?
(trilema) diana_coman: mod6, the V check post looks good; maybe move to the new blog your older posts on http://mod6.net/blog.html and update the link at http://mod6.net/ ?
(trilema) diana_coman: http://btcbase.org/log/2019-01-13#1886446 -> this made me jump at first to check on S.MG's servers with Pizarro; BingoBoingo please make those announcements clear from the start as to what services precisely are/have been affected
(trilema) diana_coman: ^ for answering the previous confusion in http://btcbase.org/log/2019-01-11#1886337
(trilema) diana_coman: asciilifeform, I know, no worries at all! onth I'm not going to *sit* stuck, no - digging at it
(trilema) diana_coman: so that'd be at least the "encapsulated" part explained
(trilema) diana_coman: so far I can tell that the static lib has the huge disadvantage that one needs then to link with it everything but the kitchen sink to bring in all it needs from ada runtime
(trilema) diana_coman: http://btcbase.org/log/2019-01-11#1886349 -> better spent on ffa, surely; thanks for the offer anyway though!
(trilema) diana_coman goes to read some more and test even more
(trilema) diana_coman: so far it certainly feels like bleeding, dunno about edge
(trilema) diana_coman: because in the docs it's claimed that non-ada main should be with the encapsulated-lib version, ugh
(trilema) diana_coman: asciilifeform, yes, but is the one generated for static lib the same? or wtf is with the encapsulated-shit then?
(trilema) diana_coman: but now I'm confused on whether *that* is enough or not (standalone thingie claims it takes care of everything needed for elaboration, correctly)
(trilema) diana_coman: http://btcbase.org/log/2019-01-09#1886075 -> on additional digging, static lib apparently does have libnameinit so yest I was looking for the wrong thing
(trilema) diana_coman: possibly; at the end of the day it's a choice and one can have gcd implemented one way or another, as long as the choice made is clearly stated on the tin
(trilema) diana_coman: i.e. why would you check a gcd for not being 0 since it should never be 0
(trilema) diana_coman: well, because technically gcd is never 0, right?
(trilema) diana_coman: I suppose only in some silly situation such as "let's take 2 numbers from user; compute gcd and then proceed to divide and print results"
(trilema) diana_coman: other than that the "reason" I can see is that otherwise in principle you need an additional check each time you call gcd (i.e. to make sure you don't step even if once in a blue moon) on this particular rake
(trilema) diana_coman: is the performance penalty significant?
(trilema) diana_coman: mathematically it does grate, yes
(trilema) diana_coman: myeah, that's not in itself a reason to not do it (if anything, it's the opposite really, given the usual "what everybody does"
(trilema) diana_coman: asciilifeform, hm, I can't say that I have a very clear idea of ALL potential implications but atm I don't see some specific downside to that; I suppose the alternative would be to raise an error on gcd(0,0)?
(trilema) diana_coman: client did build previously on gentoo so yes, I'd expect it builds on cuntoo as well really
(trilema) diana_coman: oh hey asciilifeform , that looks good!
(trilema) diana_coman: myeah, that's part of the thing: as it is, it is at least tested that people managed to compile the whole thing on different platforms
(trilema) diana_coman: and yes, I'd much rather use gnatmake for the whole pile of shit but atm the idea was to focus on a *different* part of the shit, since there are so many and I'm only one
(trilema) diana_coman: asciilifeform, I suppose www.perforce.com/documentation/jam-documentation will explain that in triplicate
(trilema) diana_coman: yes, a ton of ugh
(trilema) diana_coman: for all my hate of them, atm they...build the whole mess of plugins and whatnots so sweeping them aside would take some effort, not insignificant
(trilema) diana_coman: yet another tool that "makes building simple" don't you know; eulora's client has a WHOLE pile of scripts on top of jam on top of autotools and all that
(trilema) diana_coman: if there was more need for hating jam, it's there
(trilema) diana_coman: ffs jamfile shit: I did not have a space between lib name and ; so it...silently ignored it and ate my time grrrr
(trilema) diana_coman: ave1, it's not burning right now, no
(trilema) diana_coman: I suppose I can further look at what gprbuild does for standalone libs and then force it into what I want but ...
(trilema) diana_coman: I'll have another look at any rate, can't hurt
(trilema) diana_coman: ave1, hm, I did look in there when I made the first go aka I compiled step by step the whole thing; but I don't recollect any real alternative to the standalone lib if one wants to pack the code really
(trilema) diana_coman: http://btcbase.org/log/2019-01-09#1886159 -> well yes, trying to "dupe" the rules can't be anything other than trying to corrupt the thing back into what-we-know (and possibly like or not but at least are used to it)
(trilema) diana_coman: http://btcbase.org/log/2019-01-09#1886104 -> I seem to have missed this; ave1, did you find a way to expose the adainit for static libs?
(trilema) diana_coman: asciilifeform, yes, it's the tasking re http://btcbase.org/log/2019-01-09#1886099
(trilema) diana_coman: i.e. have it as a procedure, exposed and accessible from cpp
(trilema) diana_coman: as it is specific to ada, a non-ada main has no idea (nor does it care) about it and therefore won't do it automatically; the only way to have it done is to call explicitly the "init" procedure for the Ada unit that is to be used; and the only way to *have* such an init procedure seems to be the standalone lib thing
(trilema) diana_coman: a sort of "getting everything ready" for the program to run
(trilema) diana_coman: re ada elaboration since apparently it's not summarised in the logs as such: it's basically the code that runs *before* the main program starts and what it does is broadly initializing variables that the main program may expect to be able to access (e.g. "global" or in libs that are used) and running the "main" code (aka between begin and end of a package as opposed to that in procedures/functions) from units that are used
(trilema) diana_coman: the log is our days' own encyclopedia really
(trilema) diana_coman: or at least none that I'm aware of
(trilema) diana_coman: i.e. if you want to call ada from something-else main then you don't really have any choice that works other than this
(trilema) diana_coman: no; the "way" to do that is meant to be precisely this standalone thingie
(trilema) diana_coman: mircea_popescu, no, it's an ada thing, nothing to do with cpp precisely
(trilema) diana_coman: my trajectory in hitting walls on this was precisely that: make it static -> surprise, no adainit exported/included, checked the .a file and everything, went nuts; make it dynamic -> ugh, need -lgnat and whatnot; rtfm again and again, there is this calo-magar
(trilema) diana_coman: onth a static lib does not have the elaboration...
(trilema) diana_coman: it has a donkey-horse as far as I can tell: a dynamic lib does not include all the code it requires so you'll need to further link /distribute stuff
(trilema) diana_coman: the encapsulated part means it depends only on static libs at least (or so I read in the docs...)
(trilema) diana_coman: basically the only way available to make a non-ada-main do the ada elaboration
(trilema) diana_coman: with the standalone encapsulated dynamic lib approach, I got it to work
(trilema) diana_coman: (those are needed to do the elaboration in ada so can't do without them either)
(trilema) diana_coman: can't make it static because then it doesn't link in the adainit, adafinal
(trilema) diana_coman: in other eulora-client headaches: to get the cpp client to use my ada lib (that I want to keep separate! away from cpp swamp!), it seems I need to make my lib "standalone encapsulated dynamic"
(trilema) diana_coman: mircea_popescu, quite; I read it as "tripping over oneself in desperation to signalsignalsignal agreement^n"
(trilema) diana_coman: that "unanimously agree" is cherry on top
(trilema) diana_coman: sadly it seems I'm not
(trilema) diana_coman: myeah, all sorts of practical restrictions to consider here; I just wanted to make sure I'm not overlooking some available option before weighing them
(trilema) diana_coman: ugh, I was rather hoping I was just thick and not getting it
(trilema) diana_coman: mainly because the whole thing is anyway only one thread of the mess as it were; but yes, reentrant should work too
(trilema) diana_coman: in the vein of "fork in cpp and from that thread call Ada proc that then spawns tasks"?
(trilema) diana_coman: asciilifeform, the concrete mess is this: smg_comms is in Ada, has sender and receiver task types so one can create those as needed, perfect; onth eulora client is this ball of CPP mess and it's unclear to me if it can even be made to use smg comms as it is or what
(trilema) diana_coman: does anybody know whether/how can I use Ada task types from C/CPP code? afaik from GNAT docs there isn't a way to export task types as such
(trilema) diana_coman goes back to chopping client "code"
(trilema) diana_coman: well, if they don't, they'll find out quickly :|
(trilema) diana_coman: well, I hardly see how you can *stop* people from using it directly or why exactly; and the endian + div0 don't sound like a huge layer anyway
(trilema) diana_coman: will keep in mind, ref the log when I get there; and definitely come and shout at asciilifeform when/if I get stuck on something related to this
(trilema) diana_coman: asciilifeform, first I do need to finish getting the ffa in, so that will still take quite a while; other than that, it's more a matter of "as time permits" and as mircea_popescu says it's not top priority; that being said yes, I'd like to do it and see some timings and comparison for myself
(trilema) diana_coman: why do you need the passport *first*? (i.e. not just get one after whatever hoops are in ro, living there for x years etc)
(trilema) diana_coman: mircea_popescu, that's precisely why I asked for concrete sum because the way I see it...he has it
(trilema) diana_coman: well yes, but specifically: how much would be "enough"?
(trilema) diana_coman: asciilifeform, sometimes I wonder what exactly do you think you need/don't have to move to Romania or wherever else you consider it to be "paradise, can now do just ffa/trb/..."
(trilema) diana_coman: mircea_popescu, exactly
(trilema) diana_coman: well, don't get flattened please, there's already waay more work than active hands as it is
(trilema) diana_coman: asciilifeform, re m-r: I implemented it using mpi as per http://ossasepia.com/2017/12/28/eucrypt-chapter-3-miller-rabin-implementation/ ; ofc I'd rather use ffa ct-time implementation but it's not a sticking point per se i.e. I can switch my implementation from relying on mpi to relying on ffa, no?
(trilema) diana_coman: basically there is no reason NOT TO
(trilema) diana_coman: asciilifeform, thing is: from eucrypt and eulora pov, mpi is used for "big num arithmetics" only so I CAN in fact switch to ffa even without ct-time miller-rabin esp if ffa turns out to be...faster than mpi
(trilema) diana_coman waves and catches up on logs
(trilema) diana_coman: and yes, I'm eating up ffa with an eye on "maybe I can finally get rid of MPI!!"
(trilema) diana_coman: asciilifeform, what it's good for is at least ...for contrast!
(trilema) diana_coman: I'm all for the talk, certainly
(trilema) diana_coman: fwiw I can't say I saw a surprise so far in any of the april announcements; at most more of a difference of degree at times (i.e. the expected direction/action but to a larger/smaller degree)
(trilema) diana_coman: np, worth a dig anyway
(trilema) diana_coman: http://btcbase.org/log/2019-01-04#1884512 -> last published paper seems to be from 1985, uni reading's website mentions him as part of "combinatorics @ Reading" but "retired"
(trilema) diana_coman: http://btcbase.org/log/2019-01-03#1884247 -right, jurov has it; it was my own stale IP in hosts on that machine
(trilema) diana_coman: heh, talked in parallel there; I know and that's why I did not mention it at all at first; it was just because you asked for as much nitpick as possible, so now it's at least said
(trilema) diana_coman: re nitpick: in my code I tend to keep to XS'First..XS'First+X'Length but it does make it ugly & long
(trilema) diana_coman: asciilifeform, yes, it was rather basic stuff but the fact is that I read Knuth ~10 years ago so refresh was long due
(trilema) diana_coman: if nitpick at all, the one thing that consistently nags at me (though for which I can't make up my mind as to actual solution) is the implicit reliance on indices to be in fact starting from 1 when copying stuff e.g. http://btcbase.org/patches/ffa_ch7_turbo_egyptians.kv#L187
(trilema) diana_coman: ftr I had to refresh a bit on Knuth Vol 2 at some point but I don't see that as a minus at all
(trilema) diana_coman: the trouble is that "sharp edges" are quite often operator-shaped as it were
(trilema) diana_coman: cool; one day I'll make it to ch14b too, lol
(trilema) diana_coman: actually rather curious why doesn't apeloyee sign what he reads
(trilema) diana_coman: apeloyee beat me to the cut; nothing else so far
(trilema) diana_coman: ch8 was esp easy :P
(trilema) diana_coman: asciilifeform, phf updated with my sigs for FFA ch7 and ch8: http://ossasepia.com/reference-code-shelf/#selection-627.0-665.43
(trilema) diana_coman: np; and yes, I know how/why .kv
(trilema) diana_coman: well, it's meant as replacement not as alternative so I don't see why would one keep the sha patches; onth replacement in place aka no name change doesn't break anything either
(trilema) diana_coman: asciilifeform, you broke all your links on your www to FFA code on btcbase when you changed the name of vpatches because of keccak vs sha: e.g. btcbase.org/patches/ffa_ch7_turbo_egyptians/tree/ffa/ffacalc/cmdline.ads#L42 in Ch8 404s now because no ".kv"
(trilema) diana_coman: I was under the impression it moved
(trilema) diana_coman: trinque, how's it going with getting the Cuntoo .vpatch in fixed shape?
(trilema) diana_coman: ahahah, the intro there sounds like the typical school composition
(trilema) diana_coman: happy new year!
(trilema) diana_coman: legitimate(f(rum),household)!
(trilema) diana_coman: billymg, looks good; perhaps mirror the whole mp-wp tree somewhere as you seem to be working on mp-wp?
(trilema) diana_coman: basically you're spoiling good rum over there!
(trilema) diana_coman: ah, "good" in the sense of amount
(trilema) diana_coman: Mocky, I'd expect nothing really moves at this time of the year really; but anyway, for my curiosity: what gives then if "good interest" but no job?
(trilema) diana_coman: fwiw I like very much that "pedantic" there
(trilema) diana_coman: sadly though no amount of slow is any guarantee of perfection still
← | →
Download hourly DB snapshot | Get Source Code