log☇︎
500+ entries in 0.003s
mp_en_viaje: shocking, i suppose, but in the end, it's what we've got.
mp_en_viaje: what i'll do is, come the 15th ima sweep the address into one of the web wallets and pay the fellows from there (at their own risk).
mp_en_viaje: jfw, thanks, but i don't intend to stretch it that far.
jfw: mp_en_viaje: would you like to schedule a continuation on the wallet effort (on which I've quite appreciated your role) once I've got my V ducks in a row? I can offer the same time Tuesday.
jfw: re GNAT, it occurs to me the better question is not "what does mp_en_viaje have handy" but "what am I going to test and require of the user and support by explaining at whatever level necessary?" Which is not a question for mp_en_viaje at all as stated.
jfw: I mean, I could easily say "use this gpg command and look for this message to verify, then if that succeeds run this patch command", I tested all that, it will work, but I don't perceive it to solve the problem at hand.
jfw: eh, well perl for that matter too if I'm listing all that.
jfw: mp_en_viaje: since it looks like I've some zipper debt to catch up on here, I'll ask - do you have GNAT available on the system you intend to press on? Because that's an indirect dependency here, but I think I can avoid it if need be.
diana_coman: I think it states quite clearly what it presses to; is that not enough for what you need?
jfw: diana_coman: I'm going by the first three comments there, starting from spyked, http://ossasepia.com/2019/11/10/v-tree-and-v-starter-v2/#comment-7012
jfw: I'm digging for a known working zipper-opening guide, I know diana_coman has one.
mp_en_viaje: i guess it became fashionable in grenwich village at some point, just a pile of indistinct rags and "sit anywhere" -- but i confess i never sat. i always left.
mp_en_viaje: i'm willing to pay a visit, but... can i have like... a chair ? because no, "sit anywhere" isn't really an equivalent
mp_en_viaje: invented whatever, iirc i just recognized the importance of shit other people came up with. but more's the point : you sit there "ready for sex" but you don't know where your zipper is or how it opens ? "any way!!!" ? wtf how are we to satisfyingly copulate here ?
jfw: That I'm misusing the tool you invented and haven't fully tested a better process?
mp_en_viaje: i'm not specifically trying to be an asshole here, even though i apparently manage splendidly regardless. do you see what might make a different me throw up his hands at this juncture ?
jfw: I confess I mostly run 'patch' by hand, but v.pl modified for keccak or any other supporting same should work.
jfw: hey, I preserved as much of the history as I could
mp_en_viaje: i dunno why more people don't read more code. i swear to god usg-sponsored "comedy" is nowhere near as funny.
mp_en_viaje: alright. so then it's really gscm and gbw-signer that i want, the first being what, your hand-rolled mathlib ?
jfw: er I mean, the absolute view point is interesting, which I guess is that ...the sybil case is not interesting?
mp_en_viaje: see, this is what i mean above : you take a very absolute view, which happens to be inadequate. "how is the secure machine to know" is not an interesting problem in the absolute sense you contemplate it.
jfw: mp_en_viaje: yes. I don't think I'm confused in the suggested way: can't information be public but still sensitive to tampering?
jfw: diana_coman: not as I'd conceived it but seems that's what we're trying to determine
mp_en_viaje: in other words, i think your premises, not here, but in general, your ~manner of thinking~ is broken, in that you confuse very unlike things.
mp_en_viaje: jfw, there's nothing to trust. what am i trusting ? that indeed address x holds y ? this isn't the sort of thing that requires trust
ossabot: Logged on 2020-03-07 18:56:30 jfw: Moving on though: http://logs.ossasepia.com/log/trilema/2020-03-07#1959066 - I'm honored; was spinning a bit on "but what if it fucks up and zaps more coin than I've ever laid hands on??" but yeah, can't wait for another life, it's about time
mp_en_viaje: i thought the pile was established already ; or else what is the gasp in http://logs.ossasepia.com/log/trilema/2020-03-07#1959145 ?
jfw: The main fusing as far as I see is that it can't even be established what your pile of coin is without trusting at least one online machine
mp_en_viaje: anyway, thanks for going through it with me ; i hope the exercise might've been informative to you as well.
mp_en_viaje: well, if they're fused at the hip so to speak, i don't think it would.
jfw: Alright. What I have is a program that could be included on a secure machine built now, with which to do that computation, and a companion program that can suggest what you might use for its inputs given an online machine.
mp_en_viaje: if this reduces to "you must do your computation on a machine wtih a node running" i am not interested -- it's definitely no different, and self-evidently mroe expensive than using a -- say -- web wallet.
mp_en_viaje: well i dunno. let's see, again. what i'd like to do is produce a broadcastable tx such as to pay the fellows in question out of the pile of coin i have.
jfw: I suppose I'm the one making assumptions then. Should I have started a node up by seeking again to establish which pieces you needed?
mp_en_viaje: i went by your list, i'm not making assumptions here
jfw: ah, sure; but I'm perhaps lost at where you're seeing the node as part of the secure system, because yeah, not so secure if net-connected.
mp_en_viaje: that's okay, not like it's your job. but your offline wallet is ~maybe~ problematic, especially if i'm correct in not comprehending how is it supposed to actually do any useful work for a secure system.
jfw: It does in that I see a typo finder would be useful; I fall short in not having one to offer now.
mp_en_viaje: it provides me, for instance, the knowledge that among the things that need fixing in an "eventual pgp implementation" such as will never likely be, a typo finder'd be quite useful. i even know HOW useful, by practical, real, lived measure.
mp_en_viaje: i'm not saying whether this is reasonable or not, but it is, in its context, justified as described. it's part of something, it lives somewhere.
mp_en_viaje: by extension from this -- and i am not mincing words when i say CULTURAL TRADITION -- i expected our adventure today would be rather similar, "this is the thing for the red machine, and these are the things you'll have to type in it : privkey, txid, txcount, so on".
mp_en_viaje: now, i didn't do this because "i absolutely needed to", obviously. i chose to do it, for instance to keep my harem in good shape, and informed, connected to the world such as it is, immersed in reality as it were. i believe in such things.
mp_en_viaje: the ~reason~ they were there was that now and again i'd break out the red machine, which is an actual machine, and a slavegirl would sit in front of it, and type, by her pretty little hand, meaningless strings, from the black machinery connected to y'all and everything else.
mp_en_viaje: i dunno if you've noticed, but irrespective : at some point while i was travelling, there were half-hour-ish delays introduced in various processes, such as me upping myself. i even mentioned these in the logs specifically now and again.
mp_en_viaje: i mean... i dunno how to put it, you can do the job of producing raw tx by awk and bc in command line, and i don't mean lineS, i mean one fucking line, though it may run long.
ossabot: Logged on 2020-03-09 22:26:10 jfw: mp_en_viaje: do you have a specific goal in mind for Thursday's wallet work? Do you also want to use the online part (I would imagine so but could technically be done without)? If so, note that it takes about a day to scan the present blockchain once fed the address(es) of interest, and requires a TRB node. If you wish to also send the rawtx using it, as would be most proper, we'll also need that
jfw: mp_en_viaje: you had specifically referenced the signer part, but sure, and that's why I followed up with http://logs.ossasepia.com/log/trilema/2020-03-09#1959219
ossabot: Logged on 2020-03-07 18:59:37 jfw: Can I assume you have an x86_64 unixlike with gcc for the install?
mp_en_viaje: so it'd be fair to rewrite http://logs.ossasepia.com/log/trilema/2020-03-07#1959149 rather as "can i assume you have an x86_64 unixlike with no less than 64GB RAM, at least 1 TB HDD that must be SSD, at least two cores and, gcc. v, trb, curl etc, of which trb'd best be up to date" ?
jfw: right you are... I did assume the V part, huh. gbw-node requires less resources than bitcoind itself, but does require bitcoind.
jfw: mp_en_viaje: I didn't think there was such a thing established, indeed, hence the question
ossabot: Logged on 2020-03-07 18:59:37 jfw: Can I assume you have an x86_64 unixlike with gcc for the install?
mp_en_viaje: jfw, http://logs.ossasepia.com/log/trilema/2020-03-07#1959149 << was this more a "can i assume you have a complete republican computer, as per the [not yet written, let alone become part of common culutre] recipe" ?
jfw: I haven't got an intro article out yet (sorry diana_coman) but genesis for the parts are at http://fixpoint.welshcomputing.com/v/ : gscm, gbw-signer, gbw-node.
jfw: mp_en_viaje: I'm available should you still wish to have a look at the wallet.
dorion: I see.
diana_coman: dorion: ah, initially it was I guess because of blender; but meanwhile blender will not get to do much/be supported anyway.
dorion: diana_coman ok. ty, I asked because it was mentioned in your notes, albeit with skepticism.
ossabot: Logged on 2020-03-10 21:26:33 mp_en_viaje: this is of course my problem ; you can do it elsewhere cheaper / better / whatever, i'm the last dood to get in the way of any such a thing.
jfw: http://logs.ossasepia.com/log/trilema/2020-03-10#1959363 - I *thought* there was something deeper being said in this thread that I wasn't grasping.
ossabot: (ossasepia) 2020-03-12 dorion: just gave the latest article a second read. seems like he's saying, "you all could be men, but for whatever reason you're not and I've had enough of the retardation to interact with it further. perhaps me walking away is what's needed to wake you up."
dorion: http://logs.ossasepia.com/log/ossasepia/2020-03-12#1020639 - I wrote that in #o cause I thought, "voice will be lost in here any moment now." but then I thought, "maybe that's the immaturity you have to kill to begin with."
dorion: trinque ftr I very much appreciate what you're conveying in your series which is why I want to both talk about and see it continue. I'm not ignoring it, but I'm also not ignoring the mandate to support the implicit clients. how much are you taking the latter into consideration in what you're building ?
ossabot: Logged on 2020-03-12 00:19:33 trinque: but anyway. I wasn't describing an item I wish I had. I was describing an item I'm building.
ossabot: Logged on 2020-03-12 00:37:25 trinque: I propose you delete that list, and you write another. In the new list, write down only the items that will get the machine to boot, and allow the user to edit and rebuild the OS.
dorion: http://logs.ossasepia.com/log/trilema/2020-03-12#1959478 - gales linux covers that today. I don't doubt it can be slimmed substantially. nevertheless, the take away from the first thread was it ain't enough.
dorion: http://logs.ossasepia.com/log/trilema/2020-03-12#1959473 - I'll be the first to admit the tree can improve and my ability to improve it can improve. I erred on publishing and being clear it was a draft cause it had been delayed long enough.
dorion: http://logs.ossasepia.com/log/trilema/2020-03-11#1959469 - can I assume you've read http://trilema.com/2019/the-tmsr-os-implicit-clients/ ? Eulora is right there.
trinque: I propose you delete that list, and you write another. In the new list, write down only the items that will get the machine to boot, and allow the user to edit and rebuild the OS.
trinque: but anyway. I wasn't describing an item I wish I had. I was describing an item I'm building.
trinque: the "big dream" approach does not work, which is why I started simply, and proceeded outward.
trinque: this is a wall of hubris, my friend, and sorta flies in the face of what I was trying to convey with the series.
dorion: http://logs.ossasepia.com/log/trilema/2020-03-11#1959436 - I've been working on a list of what's needed. Here's the very rough draft of what I have so far.
jfw: I haven't actually tried mdev so I'm not quite at "makedev can be dropped" but I'm certainly open to it.
dorion: please correct me if I'm missing something, but how do you draw "pretty opposed" from the above ?
dorion: jfw can correct me if I'm wrong but I don't think he knew busybox includes runit. since he was already used to using daemontools and daemontools is the predecessor to runit anyways he went with that.
ossabot: (trinque) 2020-01-24 jfw: trinque: I was ignorant of mdev, looks like just the thing!
ossabot: Logged on 2020-03-11 02:01:59 trinque: dorion: yes, I haven't had time to complete the final post, but last I checked y'all were pretty opposed to using busybox-only for the userland.
jfw: it's impossible to keep track" to quote its init.c. One thing I take from this is one's not likely to get a good sense of the code quality of a given part from a random sampling of the overall tree.
jfw: that's 1). 2) what do you mean by "busybox-only" - because far as I know you can't possibly mean exactly that, it doesn't have an mkfs or make for example, let alone a compiler. Do you mean, "system which selects components outside busybox only if busybox $version does not contain them"? I'll note that busybox is an amalgam of code from a variety of sources and, ahem, "Adjusted by so many folks,
jfw: trinque: I'm also tardy on jumping back into the OS fray, for one thing my wallet project has dragged out way longer than I naively expected, but I look forward to doing so shortly. But in hopes of advancing the discussion a bit: is there a particular merit to busybox-1.31.1 ? For all I know it's an entirely different thing from the older one I've been looking at and we'll need some common basis
trinque: I'll point out again for the logs that my picking busybox wasn't just "whatever, it's small, and it's all there"
trinque: dorion: yes, I haven't had time to complete the final post, but last I checked y'all were pretty opposed to using busybox-only for the userland.
ericbot: Logged on 2020-03-11 01:03:20 lobbes: I just incremented the old one from the stanlogger
lobbes: http://logs.ericbenevides.com/log/trilema/2020-03-11#1959403 << as an aside for log posterity, I mis-stated this: the version number represents the block height at the time of the vpatch
lobbes: k. And I guess just let me know whenever / however you wanna try to get that t.com > t.net update process going. I'll try to find time where needed
lobbes: mp_en_viaje: okay, sounds like a plan then. So, I guess for my part I'll go back and see what I can do about a sane history-backfill process.
mp_en_viaje: honestly i think what i'll go for will be : (using trilema.com for current trilema and trilema.net for pizdi's box), hve a mysql server run on both, have t.com update both rather than just its own, and have it read the day's logs at some point tomorrow. this way people can use t.net for any purpose except write a comment.
lobbes: hm, I am not familiar with federated tables myself. I'd need to look into them a bit.
mp_en_viaje: now that said, i'm still thinking about how the fuck to get mp-wp working on two machines best.
lobbes: yeah, I was misunderstanding your process there
ossabot: Logged on 2020-03-10 19:08:58 lobbes: Instead, I figure why don't I just cut out 2,3,4,5 and instead I just alter my 1) to pull logs from my Postgres database in the same format of your input into your backfill process (which has already been proven to function to spec)?
mp_en_viaje: http://logs.ossasepia.com/log/trilema/2020-03-10#1959355 << but the format i use is as you can see, mysql insert statements, one line per day.
lobbes: it seemed simple: instead of eating IRC lines live just eat lines from Postgres. But you know, looking back I used way too many middleman steps
lobbes: that's what I tried to do last time; ended up faffing about. I'm a little hesitant to try again but I guess I'll need to at some point
lobbes: ah shit, I must've missed that. Well easy enough to remove in any case
lobbes: mp_en_viaje: I don't think it'll record line changes. Though I honestly did not test if it would break it
lobbes: I just incremented the old one from the stanlogger
pizdi: lobbes: I am MP-WP bot version 598170.