← | Results 17001 ... 17250 found in all logged channels for 'f:diana' | →
(trilema) diana_coman: ftr that is from running the cuntoo script on a different machine - apparently I managed to find a configuration that breaks it; I'll have to see what exactly is the difference that breaks it
(trilema) diana_coman: I just left a tcpdump running and it seems to have gotten 428k of those over 2 months
(trilema) diana_coman: anyway, trinque your script is actually doing the right thing as far as I can tell for now
(trilema) diana_coman: http://btcbase.org/log/2018-12-09#1879168 - it seems it's actually the ..vdiff that is borked on that laptop, ugh; I'll have to look into it and sort that out first
(trilema) diana_coman: but speedup option is actually good to know anyway
(trilema) diana_coman: it's more that I'll be away in a few hours anyway and then it's night here so it may as well just run fully until tomorrow morning
(trilema) diana_coman: will do and report back when it finishes - probably I get to see it in ~12 hours from now though
(trilema) diana_coman: I'll re-run it with that, no problem
(trilema) diana_coman: trinque, yes, I seem to have a bootable drive at the end of it but empty .vpatch file; where exactly should I add the -x?
(trilema) diana_coman: ah, ah, I get it now; makes sense
(trilema) diana_coman: also, why does it try to write to read-only stuff on /dev/sda or what am I failing to understand there?
(trilema) diana_coman: so I think it wasn't just a warning really
(trilema) diana_coman: trinque, it didn't stop but it ended with an empty "a" and "b" hence .vpatch
(trilema) diana_coman: trinque, running the cuntoo script as root on Gentoo laptop with ./bootstrap.sh -k config/4.9.95-apu2 -d /dev/sdb where the laptop's own system is on /dev/sda and that /dev/sdb is an external drive connected via USB; all the partitioning+compilations seem to work fine but at the end the make_portage_tree script fails for lack of stuff and looking a bit higher up in the output I get this: http://p.bvulpes.com/pastes/Mbkqu/?raw=true
(trilema) diana_coman: other than that it looks fine to me
(trilema) diana_coman: what, is qntra not tracked by feedbot?
(trilema) diana_coman can picture asciilifeform's chicken-holding out of c101pa and similar
(trilema) diana_coman: asciilifeform, you know, that sounds like good-old commie style: it's banned, but local police will close eyes for so long as x
(trilema) diana_coman: I got to know my great-grandmother and she lived in the countryside, in the plains too (where it gets scorching hot in the summer and bitterly cold in winter)
(trilema) diana_coman: phf, I saw it! repeatedly even
(trilema) diana_coman: not as if there's no choice of fur hats; those remind me of the old one in which my great-grandmother kept newly hatched chicken to keep them warm, lol
(trilema) diana_coman: well fur fine but...why *those*, lol
(trilema) diana_coman: also for different asciilifeform -care: www.vidra-orastie.com/caciuli/caciuli-rusesti
(trilema) diana_coman: and what, do you have problem getting sprats??
(trilema) diana_coman: milk and sprats, such care; where's the caviar :p
(trilema) diana_coman: phf, thanks!
(trilema) diana_coman: happy birthday asciilifeform !
(trilema) diana_coman: hm, if it's indeed the tmp thing, it might be worth a try to press vtools to current leaf (i.e. vtools_tempfile_standalone or _notmp) and see if that cures it; my archive contains pressed vtools to ksum patch only, not further
(trilema) diana_coman: lobbes, never seen that before but it seems related to gnat version?
(trilema) diana_coman: http://btcbase.org/log/2018-10-08#1859582 -> following up on this, the presentation will happen next Monday (10th December), 4.15pm GMT; it's one hour only so I'm not that sure there will be enough time to get online at the end of it but who knows, maybe some students will actually get it and even... do something with it
(trilema) diana_coman: aha, that was my understanding of it
(trilema) diana_coman: that's fine, note that my feedback is given as I read them so without actual knowledge of what happens later/where exactly they are used
(trilema) diana_coman: asciilifeform, it's not about exhaustive list of ways-to-break, certainly not
(trilema) diana_coman: aha; imho this sort of thing would be great added to the comments there
(trilema) diana_coman: yes, feed it one, whether cascading or not; the point is: what is the meaning of overflow in exactly for a shift op?
(trilema) diana_coman: it doesn't provide it, no
(trilema) diana_coman: i.e. if one shifts right by 2 bits but provides an overflow of 8 bits than 6 of them get simply or-ed, it's not like they get pushed in
(trilema) diana_coman: asciilifeform, the only thing re ch3 that I keep circling because not entirely clear why so is the "overflow in means *or* on word"
(trilema) diana_coman just ate ffa 3, will sign
(trilema) diana_coman: although ofc it's more like Koch's 1mn loc ~always
(trilema) diana_coman: asciilifeform, and the loc is not the whole story either; I'd much rather read *your* 1000 loc than Koch's 100 loc
(trilema) diana_coman: http://btcbase.org/log/2018-11-28#1875644 -> so wanting to be a lord while at the same time needing someone to use a whip on you already?
(trilema) diana_coman: asciilifeform, no; possibly having started with Pascal in highschool & the "one programming language per week" crazy uni year of choice -> "stronger stomach", if anything
(trilema) diana_coman: asciilifeform, I don't remember any barf bag of my own!
(trilema) diana_coman: asciilifeform, correct re 1 disk; for the rest I'll have to decide but first step has to be testing trinque's new item locally anyway
(trilema) diana_coman: asciilifeform, smg's test machine is running proto-cuntoo so it's not just any gentoo really
(trilema) diana_coman: the test before the test; well, yes, I'll have to
(trilema) diana_coman: aha; (tbh it seemed like that but I was being optimistic for once); so atm I'd need to basically nuke s.mg's test machine to move it on to cuntoo
(trilema) diana_coman: trinque, that looks great; if I understand correctly, the archive there contains the means to a. install cuntoo b. make the genesis of cuntoo/portage that could in principle be used to move an existing gentoo to cuntoo; is this correct?
(trilema) diana_coman: the selection thing? I have it but on posts, not on main
(trilema) diana_coman: asciilifeform, ?
(trilema) diana_coman: so it ..did not take all that long in fact?
(trilema) diana_coman: asciilifeform, I only skimmed the last chapter so Peh's output makes at least some sense but I still need to work my way through all the previous chapters; and time is limited as always...
(trilema) diana_coman: it apparently took feedbot 2 minutes though to spill a first bunch of the comments after the subscribe, lol
(trilema) diana_coman: wb spyked ; feedbot looks good - I sent it pm to subscribe to http://trilema.com/2018/euloras-communication-protocol-restated/feed/ and it apparently got it (bonus, it correctly said I was already subscribed when I poked it the 2nd time with the same thing)
(trilema) diana_coman: possibly the same "how can you live without a smartphone???"
(trilema) diana_coman: phf, thanks!
(trilema) diana_coman: asciilifeform, ^
(trilema) diana_coman: phf, thanks!
(trilema) diana_coman: when I say I can't comment I mean it barfs with "incorrect captcha" while the captcha thing says it's shut down so no word to enter
(trilema) diana_coman: ugh, asciilifeform I can't seem to be able to comment on your blog? (and fwiw it's also a pain because it won't work with ip in hosts only, I have to access it from toilet-pc)
(trilema) diana_coman: I can certainly see the temptation; I'd say there is still time to chew on this, as it's not yet burning
(trilema) diana_coman: mircea_popescu, fixed-length strings get rid of all sorts of ugh pretty much everywhere; this being said, I can't quite tell what we need as filenames and recall that they include the path - I think that's the main reason why it will still be variable
(trilema) diana_coman: awww, did the duckling see it?
(trilema) diana_coman: mod6, as asciilifeform says, essentially it's preferred to keep same; for ref, logs discussion http://btcbase.org/log/2018-09-19#1851864
(trilema) diana_coman: I can't quite tell for sure what she means by worry i.e. if empty loop or not
(trilema) diana_coman: I'm scratching my head more at the "how I was surviving without a smart phone and much longer could I live like this." + notebook maps etc but I suppose I'm essentially already too old to fully grasp the phone attachment thing
(trilema) diana_coman hears asciilifefore singing don't worry, be happy
(trilema) diana_coman: thanks trinque !
(trilema) diana_coman: trinque, yes please
(trilema) diana_coman: hm, does this need to be in here? I tried in pm and it says it failed
(trilema) diana_coman: but yes, I should set it
(trilema) diana_coman: mircea_popescu, I tend to check it anyway for ref
(trilema) diana_coman: fwiw re trinque's troubles with singapore vm - I never had trouble so far with connection or anything else from Singapore though mine is not virtual anything
(trilema) diana_coman: onth it makes easier to avoid the mess since it's all at one time, can't quite complain
(trilema) diana_coman: sure, not asked; the point was that there was someone to coordinate/think that so it got done; now there isn't, they do what they want rite, so...it's not done
(trilema) diana_coman: mircea_popescu, aha; and I wouldn't be surprised if clasa muncitoare resented them for it
(trilema) diana_coman: asciilifeform, I finally saw proper gridlock last year on the outskirts of Bucharest because 1. former village is now colony of office drones so gotta get to/from work at same time 2. "road" was still former village ulita pretty much 3. they were also ..."working" aka half of it was blocked anyway
(trilema) diana_coman: what they are anyway, until/unless you cement the API
(trilema) diana_coman: bvt> http://btcbase.org/log/2018-11-19#1873650 << well, if i do common part (api) first, then diverging system-specific branches, i still could add new functionality on top of *each* of these branches. i don't like this option. -> perhaps unsurprisingly, the part that one doesn't like is however actually correct i.e. yes, you'll have to maintain the two separately if they are separate; hence my original "they are 2 trees" - because that's
(trilema) diana_coman: asciilifeform, read on, not as if recommended for the task, no
(trilema) diana_coman: asciilifeform, in my understanding he wanted to cement "common api" hence possibly root since that's the only common part for the 2 trees, hence "regrind" if new (because not in root etc)
(trilema) diana_coman: keeping the trees in sync is probably cheaper than regrinding the whole thing anyway; and if /when it's not, then...regrind it as a single tree and that's that
(trilema) diana_coman: so if you are not sure, I'd even keep the trees separately, I still don't quite see the problem with this (the benefit being that it doesn't force you to decide NOW on something you don't yet ...know)
(trilema) diana_coman: regrinds are not evil or anything of the sort but they do have a cost ; and if you get others to sign your patches, the cost increases since you lose the original signatures basically
(trilema) diana_coman: bvt, precisely because it can't be fully clear in advance I'd suggest to choose the more flexible v-structure rather than something with set in stone requirements (such as API as root of the v tree sort of thing); this is NOT to say or guarantee you won't regrind but simply to not make ~surely needed
(trilema) diana_coman: anyway, the purpose of V is not to force something onto the user
(trilema) diana_coman: the only case in which such a thing makes sense is if it's already a fixed /known /set in stone set
(trilema) diana_coman: basically it's just a way to cause yourself trouble, I wouldn't recommend
(trilema) diana_coman: bvt, from experience I can tell you that "complete from day one" is not likely to ever happen
(trilema) diana_coman: bvt, that sounds like you want to start then the tree with ..the API? otherwise at any rate, the user CAN use the same API with whatever provides it, no?
(trilema) diana_coman: bvt, while I don't see a big problem per se with an empty genesis, the question for your specific situation is why glue together 2 trees if they diverge right from the start anyway?
(trilema) diana_coman: phf, I wanted to sign your vtools patches but I realised that they are using sha so I don't really know: do you plan to regrind them with keccak?
(trilema) diana_coman: jurov, BingoBoingo confirmed, I can see them; thanks!
(trilema) diana_coman: http://btcbase.org/log/2018-11-18#1873291 - noted and added to the list though it might still take some time to get up to speed with ffa again
(trilema) diana_coman: I think they call it myanmar nowadays
(trilema) diana_coman: !!v 65ABB72AB2D8B63CFE994544EDAD678B77EE127DBD9C3ECCAA2458C22842C326
(trilema) diana_coman: BingoBoingo, invoice me via deedbot then
(trilema) diana_coman: BingoBoingo, let me know how you prefer to settle
(trilema) diana_coman: I can't begin to imagine what was the design idea there "oh, ALL does not mean categories because you might want to just re-categorize all your writing" or what
(trilema) diana_coman: and re the wp backup from dashboard specifically, the one time when I used it on old blog it turned out to be shit because although it said "backup ALL" it failed to actually backup /restore the categories too...
(trilema) diana_coman: BingoBoingo, fwiw all my backups are basically scripts+cron
(trilema) diana_coman: http://btcbase.org/log/2018-11-15#1872324 -> by comparison to the rest, yes, I "like" it too.
(trilema) diana_coman will go afk too
(trilema) diana_coman: my understanding was that nobody actually LIKES oaep all that much but it's (again! another one of those!) the thing we have (as opposed to the thing we might wish for)
(trilema) diana_coman: problems are never in short supply, certainly
(trilema) diana_coman: meanwhile the oaep got sorted better as part of smg comms really (i.e. only ada calling c, no back and forth dance and that gets rid of a LOT of confusion)
(trilema) diana_coman: but it might still take a while to get back to it
(trilema) diana_coman will come and complain loudly if confused
(trilema) diana_coman: the table with FFA patches looks great; I'll look into carving again some space to re-start on it
(trilema) diana_coman waves to asciilifeform
(trilema) diana_coman: mod6, re comment, it seems it got lost, I could not find it anywhere so not in queue nor anything
(trilema) diana_coman: anyway, if anyone wants to maintain the full & detailed manual, I will happily sign their .vpatch with it,sure
(trilema) diana_coman: onth I kept the quick guide and updated it to point users to a. use the bloody help of V as it's quite useful as it is! b. ask if they get stuck, wtf
(trilema) diana_coman: the out of date also refers to the fact that meanwhile V has a broader scope really than trb code
(trilema) diana_coman: if you notice, I said out of date at 3rd vpatch, NOT before; and yes, 2nd vpatch includes them precisely because they are at that point still perfectly fine
(trilema) diana_coman: mod6, I meant out of date wrt to my vpatch i.e. keccak hashes
(trilema) diana_coman: hopefully this is now finally clearly set for future maintenance of any sort, but let me know if there is any other trouble you see with it
(trilema) diana_coman: and yes, my test went precisely on this path: get the .zip first and then use that to press the vpatches and then check results + whether they are the very same
(trilema) diana_coman: and done: the updated .vpatch files and starter_v.zip + sigs are all up; I've checked them on my RK; genesis is the same and result is identical to V-2017; the result of 99993 .vpatch is identical to V-2018; the result of keccak_vtools vpatch is to update BOTH docs and code; re docs, I've nuked the user manual as I won't maintain it and it's becoming confusing due to being out of date; I've updated the quick_guide however, mainly for 1st t
(trilema) diana_coman: ime users really; re .zip file: the v in there is precisely what one gets by pressing my v_keccak_vtools.vpatch
(trilema) diana_coman: so to keep this fully aligned, I'll regrind the last 2 patches so that the docs changes are carried over as well; as a result: genesis = http://thebitcoin.foundation/v/V-20170317.tar.gz; 1st patch => http://thebitcoin.foundation/v/V-20180222.tar.gz; 2nd patch => using vtools & keccak instead of sha
(trilema) diana_coman: right, doing the diff with the archived versions at http://thebitcoin.foundation/v/ yields: my genesis is precisely http://thebitcoin.foundation/v/V-20170317.tar.gz; the version 3 aka after applying the .vpatch http://ossasepia.com/vpatches/v_mod6_99993.vpatch does bring in the code modifications of http://thebitcoin.foundation/v/V-20180222.tar.gz, but not the docs changes
(trilema) diana_coman: mod6, I don't see any comment from you on my blog, what happened? (re http://btcbase.org/log/2018-11-14#1872143 )
(trilema) diana_coman: if anything, I suppose I could have gotten the genesis with an earlier version
(trilema) diana_coman: fwiw the keccak-version of v (i.e. pressing the tree I published all the way to its leaf) IS the corrected one re pressing order ; later today I'll do a diff with precisely the versions mod6 has at http://thebitcoin.foundation/v/ but going by version number I really don't see what "old version" are you saying
(trilema) diana_coman: http://btcbase.org/log/2018-11-14#1872169 -> as ^ ; now I'm not sure if anyone actually look at the 2nd vpatch and hence it really is an old version that's there or just got hang up on the fact that I kept to preserve some history and hence genesis+vpatch to version 3
(trilema) diana_coman: the genesis IS on 99994K yes, the next vpatch upgrades it to 99993K and only THEN my own vpatch changes it to use Keccak and vtools
(trilema) diana_coman: mod6, I've put the vpatch, neh?
(trilema) diana_coman: or symlink I suppose, whatever rocks your boat
(trilema) diana_coman: true, it expects it to be in PATH
(trilema) diana_coman: I've tested it quickly on my Rockchip itself and I couldn't spot any trouble, but let me know if you find any problems with it
(trilema) diana_coman: mircea_popescu, it's part and parcel of the promised write-up http://btcbase.org/log/2018-11-13#1871705
(trilema) diana_coman: ave1, nice! I'll add it to my list to give it a spin
(trilema) diana_coman: as the lithuanian-estonian-russian said "they've always been great, what!"
(trilema) diana_coman: hey, old riga sprats are great here too!
(trilema) diana_coman: fwiw I actually patched v.pl to use phf's vtools and it works absolutely fine; I guess I'll write-it up and publish the whole thing later today if nobody else does it
(trilema) diana_coman: bvt, that sounds good!
(trilema) diana_coman: !Xbid 1007 150mn
(trilema) diana_coman: aha; in any case, it's better written there so next person stumbling into this precise issue can be pointed at it and not waste any time at all
(trilema) diana_coman: I suppose it's the gcc >4.9 that made it eat up the whole part as "html"
(trilema) diana_coman: bvt, a recovered full version of the comment: http://p.bvulpes.com/pastes/d9iWn/?raw=true
(trilema) diana_coman: and ugh, bvt , your wp ate part of my comment! there was more between "used by gcc 4.9" and " they want. " wtf
(trilema) diana_coman: anyway, trinque, would you add bvt's blog to deedbot's feed please?
(trilema) diana_coman: bvt, that is a known issue with gcc version really
(trilema) diana_coman: pretty much that: if it's so ugly that you can't handle it sanely, then either fix it or, failing that, use Ada's Streams since that's what they are for anyway.
(trilema) diana_coman: its*; gah, my spelling is atrocious lately
(trilema) diana_coman: right; I meant in it's current use of "default, everywhere"
(trilema) diana_coman: streams start looking increasingly to me like an abstraction born out of "I *have to deal* with those insane inputs so ..."
(trilema) diana_coman: ah, I see it; I did look and I saw you used both but I couldn't confidently identify the decision as to where one and where the other
(trilema) diana_coman: asciilifeform, where?
(trilema) diana_coman: perhaps if the structures and protocol were way hairier than they there, the gains would be worth it - but in such case I'm not sure it wouldn't point to a need to simplify rather than a need for streams or some such
(trilema) diana_coman: re are still all those parts that are anyway no concern of upper layers (e.g. crc, padding) so there is still some part that has to walk the thing component-by-component anyway. The more I look at it, the more I get the impression that the idea of "serialize in 1 statement the whole stuff" is not worth pushing beyond simple types (i.e. yes, serialize in one line unsigned_32 but not the whole content of one message)
(trilema) diana_coman: http://btcbase.org/log/2018-11-10#1870705 -> the more I think of this, the less I see the case for it: essentially I don't think the serialization part should really be that important that it forces upstream to deal with fixed-size records only sort of thing. Also, for the case at hand, it's basically unclear that the gain is worth it anyway: yes, fixed-size (i.e. max-size) record means one can do the serialization of that directly but the
(trilema) diana_coman: so perhaps I get the *why* but I don't buy it for a communication protocol, just why to "not know"
(trilema) diana_coman: hence try because you ..don't know in which byte order it is
(trilema) diana_coman: I suppose the idea there was to *not* specify byte order at all
(trilema) diana_coman: I also don't get why to do that really, hence current code that doesn't do it, no; (what it does is to simply check if local machine is big endian in which case it flips octets of anything on more than 1 octet)
(trilema) diana_coman: I suppose this http://btcbase.org/log/2018-11-10#1870622 is linked to http://btcbase.org/log/2018-09-14#1850462 but I fail to see/recall some agreement that "we now first try as it is, then if it fails, try flipped"
(trilema) diana_coman: http://btcbase.org/log/2018-11-10#1870659 - as far as I can tell it's actually a WordPress "feature" where it converts text smileys to graphic images (the 8) is "cool") ; I disabled it now from Settings->Writing, if anyone else runs into this shit
(trilema) diana_coman: mircea_popescu, myeah, whether there IS a problem really or not quite
(trilema) diana_coman: yes, that's what I had in mind; and I think it does solve the problem because it effectively fixes the size, yes
(trilema) diana_coman: the only other option is to say it's always nmax*...
(trilema) diana_coman: if it is described as a variable length i.e. n* ... then it's variable, what can I do
(trilema) diana_coman: but the issue was re what follows
(trilema) diana_coman: in implementation it gets defined as such although it still gets represented on 8 bits because thus specified; logically speaking it shouldn't be on 8 bits to represent ...40 max so yes, it makes sense to say, pack
(trilema) diana_coman: that in itself doesn't solve the issue
(trilema) diana_coman: if you have however n and then max and then whatever then sure, yes
(trilema) diana_coman: it's not going to fit "max", is it?
(trilema) diana_coman: if you have n and then n*x and then something else
(trilema) diana_coman: uhm, maybe I don't get what you mean then
(trilema) diana_coman: so that the "not meaningful" is essentially padding
(trilema) diana_coman: i.e. it should be the last thing in the message
(trilema) diana_coman: this is what I had in mind; it helps but: diana_coman> in which case fine, it can perhaps even work like that for most messages except stuff that has max>message size and/or stuff that has meaningful data *after* this variable part
(trilema) diana_coman: in which case fine, it can perhaps even work like that for most messages except stuff that has max>message size and/or stuff that has meaningful data *after* this variable part
(trilema) diana_coman: basically the only way is that: put always max and just write somewhere how much of that is actually meaningful
(trilema) diana_coman: for the other I really don't see how exactly to have at the same time flexible size (specifying n and then n* IS flexible size) AND record'write
(trilema) diana_coman: for one thing the solution as implemented is perfectly fine; sure, not a one-line record'write or something like that but not a terrible thing either
(trilema) diana_coman: mircea_popescu, the problem (if there is one) is not space in itself for sure
(trilema) diana_coman: it isn't a "8-bit value"
(trilema) diana_coman: at implementation time that is how I define the counter for keyset for instance
(trilema) diana_coman: well, that IS what I said though, lol
(trilema) diana_coman: I'm not sure what would the bitwise thing buy exactly?
(trilema) diana_coman: http://btcbase.org/log/2018-11-10#1870616 - I don't think the structure in itself is problematic; I think it's simply the serialize-in-one-go that doesn't mix well with any flexibility at all
(trilema) diana_coman: http://btcbase.org/log/2018-11-10#1870620 -nitpick away! I actually DID consider that and I decided it's not really fitting because think of it: if I make it enumeration that *also* means you can actually go succ and prev which however isn't something that makes sense for message types; it's not like they are an actual ordered thing
(trilema) diana_coman: my understanding of the "smart phone" label was in the vein of "smarter than user" so rather accurate, yes
(trilema) diana_coman: well, shouldn't be hard to find next time I'm in Ro really
(trilema) diana_coman: asciilifeform, it seems to me the guy is Bucharest-based, no?
(trilema) diana_coman: I suppose the " Anyway, e-mail is the communication tool that I am most comfortable with." might be quite common for thinking people that aren't all that young anymore either
(trilema) diana_coman: that sounds like the "we can haz dinastyyy 2"
(trilema) diana_coman: heh, at least it's not Ioann
(trilema) diana_coman: asciilifeform, I'd suspect the Ioan is simply because of church slavonic, yes
(trilema) diana_coman: mircea_popescu, hm, I knew also the approach odd/even generations i.e. same name as grandfather rather than father; onth closer home it was meant to be more like same name as godfather but whatevers
(trilema) diana_coman: quite! and unfortunately I'll still have the works in the sewer in parallel for quite a while
(trilema) diana_coman: so yes, Ada spoils one basically
(trilema) diana_coman: fwiw those past few days I had to get back to some C/CPP code and there was this funny moment where I read some code adding 2 vars of different types and my mind went instantly eeeek
(trilema) diana_coman: asciilifeform, I honestly don't feel any pain re pointerism as I don't miss it AT ALL
(trilema) diana_coman: I'll play a bit with those unchecked unions too though, I hadn't looked at them
(trilema) diana_coman: in this particular case the unchecked conversion still makes more sense to me
(trilema) diana_coman: I still can't quite see the reason to make a stream in order to write a known-size record to a known-size array of octets though
(trilema) diana_coman: that's the thing: wherever I turned re serialization it kept pushing the streams, hence my earlier "it seems I have to use streams,eurgh"
(trilema) diana_coman: hm, I kept thinking for some reason that there was a 3rd way (i.e. NOT streams and not unchecked) but I just did not see it; I'll have a look at the unchecked unions
(trilema) diana_coman: or what, just unchecked on the whole thing?
(trilema) diana_coman: asciilifeform, how can I serialize the record into an array of octets? I keep thinking there's something obvious that I just don't get
(trilema) diana_coman: http://btcbase.org/log/2018-10-16#1863219 -> whine! I get the record neat representation part in Ada (or so I think). Re serialization though my current understanding is that I *have to* use ...Streams; is this even correct?
(trilema) diana_coman: asciilifeform, as long as one has replacement in case it's needed...; for the other part though, there is also the in-wot thing, not like "anyone can bid"
(trilema) diana_coman: re auction bot: the way this sort of thing worked in eulora is basically by agreement; afaik there is no untoast button (nor do I see how it would make sense really)
(trilema) diana_coman: http://btcbase.org/log/2018-11-06#1869977 -> oh hey, that looks very useful indeed, thanks!
(trilema) diana_coman: hm, weird; now I'm really curious if you get the same complaint with asciilifeform's ffa (or my smg comms for that matter)
(trilema) diana_coman: bvt, is that adacore's gnat?
(trilema) diana_coman: I just checked and I can confirm too: that restriction is fine here while using Ada.Sequential_IO
(trilema) diana_coman: http://btcbase.org/log/2018-11-05#1869503 -> and done; asciilifeform and anyone else requiring strictly 80 cols - I've updated the post with a .vpatch to read the keys from file and thus keep them out of the fully-80-cols-now code itself: http://ossasepia.com/2018/11/04/smg-comms-chapter-6-packing-and-unpacking-rsa/#selection-157.0-159.591
(trilema) diana_coman: wounded knee!
(trilema) diana_coman: lol, I never quite understood wtf it is with US that they can't even come up with new names for places or what
(trilema) diana_coman: mircea_popescu, that sounds close to "and then goat ate the wolf"
(trilema) diana_coman: ahahhaha, that's a lousy wolf
(trilema) diana_coman: http://btcbase.org/log/2018-11-05#1869406 -> the way I read this was that arab did not consider that as appointment, more like audience granted -perhaps, if allah finds time for it - to lowlife sort of thing
(trilema) diana_coman: http://btcbase.org/log/2018-11-04#1869273 - a config file seems the better choice, yes; I'll add it to the list to move the keys to a config file and update the tests to read from config file; that should actually meet asciilifeform's requirements too since the code will not contain the >80cols lines (although the config files will, of course)
(trilema) diana_coman: sounds more like a study in "how unearned wealth can screw you up" basically
(trilema) diana_coman: Mocky, hm, I thought it was "trust Allah but tie camel", apparently they lost the 2nd part?
(trilema) diana_coman: it still seems at best silly to manually split strings that one would than have to merge if they want to use as such somewhere else
← | →
Download hourly DB snapshot | Get Source Code