awt[asciilifeform]: asciilifeform: for multipart messages, how do we determine if there is some encoded content in it such as an image or file?
phf: http://logs.bitdash.io/pest/2023-05-15#1026119 << nobody knows on account of fundamental machinery not being figured out yet. the thinking is that something like signpost's luby implementation will be used for file transfer, at which point some kind "metadata" packet will be added
phf: to pest spec. bit since we don't know if luby will even work, and what will need to go into metadata, there's not been an attempt to add one yet
bitbot[asciilifeform]: Logged on 2023-05-15 01:16:19 awt: asciilifeform: for multipart messages, how do we determine if there is some encoded content in it such as an image or file?
phf: and there was strong opposition to my idea of having some content available inline in message log, so it looks like the more or less agree upon going forward approach is that there will be a metadata packet of a new type
signpost[asciilifeform] dragging dead code out of trb with clion atm.
signpost[asciilifeform]: my old patch that excises the wallet yields a lot of other dead code, and while this renders the thing not a reference implementation in a box, code that was snipped is still all there in the vtree, and I can at some point pull things like key generation and signing into their own utils. I took a run at that years ago, hav
signpost[asciilifeform]: e pieces around.
signpost[asciilifeform]: leaving everything in script.* and serialize.* alone for now though.
signpost[asciilifeform] took a look at current prb code, and the shit bolted to the side has shit bolted to the side.
signpost[asciilifeform]: will resume work on the fountain coder in a few weeks. I got the (currently posted) python impl about as fast as python's own parallelism limitations will permit. CL one oughta in principle have fewer limitations in this regard.
awt[asciilifeform]: signpost: what were the parallelism limitations you ran into?
awt[asciilifeform]: I'm using python 3 for my new station - has cool stuff like thread pools, futures.
asciilifeform: http://logs.bitdash.io/pest/2023-05-15#1026119 << for 'file', the notion was to luby. for lolcats, iirc no one yet suggested precisely how to mark'em ( would strongly prefer not to roll in the 'mime' traditional idiocy or anyffin like it. prolly best to have a single flag somewhere )
bitbot[asciilifeform]: Logged on 2023-05-15 01:16:19 awt: asciilifeform: for multipart messages, how do we determine if there is some encoded content in it such as an image or file?
asciilifeform: http://logs.bitdash.io/pest/2023-05-15#1026122 << luby 'works', the q afaik is 'whether the game is worth the candles' (vs regular old 'multipartism')
bitbot[asciilifeform]: Logged on 2023-05-15 09:19:16 phf[signpost]: to pest spec. bit since we don't know if luby will even work, and what will need to go into metadata, there's not been an attempt to add one yet
asciilifeform: http://logs.bitdash.io/pest/2023-05-15#1026131 << asciilifeform has a working py3 (for fpgaism) but iirc it is absent on standard dulap gentoo
bitbot[asciilifeform]: Logged on 2023-05-15 09:42:31 awt: I'm using python 3 for my new station - has cool stuff like thread pools, futures.
asciilifeform: http://logs.bitdash.io/pest/2023-05-15#1026125 << iirc the tricky bit (recall how mp choked on jfw's 'wallet') was how to pump info back outta trb to walletron (to update the latter with unspent outputs to yer addrs)
bitbot[asciilifeform]: Logged on 2023-05-15 09:32:23 signpost: my old patch that excises the wallet yields a lot of other dead code, and while this renders the thing not a reference implementation in a box, code that was snipped is still all there in the vtree, and I can at some point pull things like key generation and signing into their own ut
asciilifeform: http://logs.bitdash.io/pest/2023-05-15#1026124 << how much actually-dead coad was there (if not considering the wallet) ? (vs. merely commented-out historical lulz)
bitbot[asciilifeform]: Logged on 2023-05-15 09:30:52 signpost: dragging dead code out of trb with clion atm.
awt[asciilifeform]: http://logs.bitdash.io/pest/2023-05-15#1026123 << Ah I see so a metadata packet referencing the hash of a multipart message, for ex.?
bitbot[asciilifeform]: Logged on 2023-05-15 09:21:25 phf[4]: and there was strong opposition to my idea of having some content available inline in message log, so it looks like the more or less agree upon going forward approach is that there will be a metadata packet of a new type
phf: http://logs.bitdash.io/pest/2023-05-15#1026134 << i don't think it can be considered "works" until there's at least there's a workbench implementation of a complete roundtrip. send out a metadata packet, get counter party to recieve it, request hash against some kind of luby protocol, get file
bitbot[asciilifeform]: Logged on 2023-05-15 09:54:20 asciilifeform[6]: http://logs.bitdash.io/pest/2023-05-15#1026122 << luby 'works', the q afaik is 'whether the game is worth the candles' (vs regular old 'multipartism')
phf: whether or not it's worth the candles is not imho a theoretical question, gotta build a working prototype and see if it works in real world
unpx[asciilifeform]: Hello there, I hope everyone is good. Been implementing a lot of cryptographic primitives, but hadn't time to ponder on them too much, not as I wanted. Been unlearning programming in general and computers seems more hazardous than before.
unpx[asciilifeform]: Been torturing myself thinking where to put data in this monad-like life-style since server is far away and the only thing I trust is that it's safe enough to run simple and critical stuff, but cannot be a remote NAS.
asciilifeform: phf: asciilifeform agrees 100%, needs empirical tests
asciilifeform: unpx: thought you were making an algebratron a la macsyma ?
asciilifeform: unpx: s/monad/nomad or was it intended as a haskellism pun ?
unpx[asciilifeform]: typo
unpx[asciilifeform]: http://logs.bitdash.io/pest/2023-05-15#1026150 <<< I would like the algebratron to treat the abstract stuff as such, so for example, PollardRho for integers and elliptic curve differs just in the structure, not in the algorithm on cylic (sub)groups
bitbot[asciilifeform]: Logged on 2023-05-15 13:12:01 asciilifeform[6]: unpx: thought you were making an algebratron a la macsyma ?
unpx[asciilifeform]: But some structures arise from other structures, and this makes me feel in a OOP-ism
asciilifeform: unpx: possibly, but how much would the 'glue' (to express 1 in terms of the other, or both in terms of an underlying structure) weigh ?
asciilifeform: imho worth exploring, but historically this kinda thinking not always worked well
dulapbot: (trilema) 2014-10-09 asciilifeform: mircea_popescu: 10k line/250kb limit. if you overrun it you get shot << chuck moore (of 'forth' fame) seems kinda in favour of this. as am i. a kind of 'environmentalism' i've been advocating for many years (intellectual pollution doesn't blacken mere lungs. it makes everybody - stupider. measurably.)
asciilifeform: oop per se being a primo example