Show Idle (>14 d.) Chans
← 2022-12-29 | 2022-12-31 → ↓
asciilifeform: $ticker btc usd
busybot: Current BTC price in USD: $16522.07
busybot: The 24-Hour VWAP for BTC is $ 16547.90 USD
phf: did we get too cocky muskbros?
asciilifeform admits that he dunget the ref (aside from possibly the '21 episode where musk&co carried out the latest 'lift exchrate in a plane, then drop it out' ..?)
phf: that joke is too dumb for me to explain
phf: i've added multibroadcast, so now my packets are near-realtime. on the other i will probably no longer gain any new insight into udp reliability
phf: i no longer need to rage over my packets occasionally getting stuck in awt's nursery for 15 minutes
phf: http://logs.bitdash.io/pest/2022-10-30#1014626 << is this your latest lisp source/test combo? also is there a third file, where it's an interface poc. ii'll tease it out from tests, but…
bitbot[asciilifeform]: Logged on 2022-10-30 03:07:03 signpost: http://paste.deedbot.org/?id=kAql << and tests
phf: and to further clarify, it's an implementation of `Luby, M. (n.d.). LT codes. The 43rd Annual IEEE Symposium on Foundations of Computer Science, 2002.` without any further extensions?
signpost[asciilifeform]: nah, it's not luby's erasure code. it's the one in the paper I link in this post
signpost[asciilifeform]: I've updated the python one quite a bit past where the lisp one currently is. will be posting a subsequent vpatch shortly, which implements file transfer over udp socket, rather than just a toy impl of the encoding/decoding
signpost[asciilifeform]: the lisp one's a toy encoder/decoder atop bit-vectors without any send/receive yet, but expresses the algorithm correctly.
signpost[asciilifeform]: also would benefit from multiple encode/decode threads. there's zero coordination needed in the encoder to parallelize. in python I'm just calling fork() to do it, since what state is shared is read-only (and decisions on which message blocks to use as inputs to produce a check block are pseudorandom).
signpost[asciilifeform]: parallelizing the decoder will be slightly more work, since there's shared mutable state there between workers.
signpost[asciilifeform]: can't recall if I had sbcl's atomics in that WIP lisp paste already, but figured these will be useful for that.
signpost[asciilifeform]: anyway paper's pretty straightforward, happy to answer any questions about the draft implementations.
phf: ah shit i'm 2/3 implementing luby
signpost[asciilifeform]: iirc that had worse complexity than "online codes".
phf: complexity in what sense?
signpost[phf]: "This paper is written in terms of a new algorithm called on-line codes [7]. Luby has recently published an algorithm called LTcodes, which is similar to on-line codes, but suffers from O(n lo
signpost[asciilifeform]: g n) running time, as compared to linear time for on-line codes
signpost[busybot]: one of the two linked from blog
phf: ah ty
signpost[asciilifeform]: yw, the "bigdown" paper is what excited me about this algo most.
signpost[busybot]: intersting not just for "decentralized torrent" but also "achieve wide distribution of this byte-array under heavy ddos"
signpost[busybot]: or jammed radio. oughta work for extremely lossy channels as well as marginally lossy, just with lower (but predictable) bandwidth
signpost[asciilifeform]: or asciilifeform's "noise-floor" radio of old threads.
phf: http://logs.nosuchlabs.com/log/pest/2022-12-30#1020024 << are you packing your blocks in pest-like packets?
dulapbot: Logged on 2022-12-30 19:42:59 signpost[asciilifeform]: I've updated the python one quite a bit past where the lisp one currently is. will be posting a subsequent vpatch shortly, which implements file transfer over udp socket, rather than just a toy impl of the encoding/decoding
signpost[asciilifeform]: yup, of ~400byte
phf: with the common prelude? nonce, bounces, version, command, black encoded?
signpost[asciilifeform]: haven't included any of the pest protocol details here. thought is this oc-packet rides inside a kind of direct message.
phf: right, i guess if you're hacking it into an existing implementation, you just need to provide 428 bytes of message, and e.g. blatta will take care of container
signpost[asciilifeform]: yup, that was the thought. next step get it welded into blatta and be able to request hash-identified payload from my peers, have them confirm they have it, then request an oc-stream of particular parameters that I supply (which control the fault-tolerance and difficulty of encode/decode)
signpost[asciilifeform] bbl, tiny hellspawn in gastric distress
signpost[asciilifeform]: beloved hellspawn, of course
signpost[asciilifeform]: one other thing to mention is that I can learn about the lossiness between myself and my peers by the delta between what I asked for and what I ended up needing from them, in terms of packet count
signpost[asciilifeform]: got more than needed, channels less lossy than you thought, can adjust down. got less, more.
phf[asciilifeform]: you could just slice it into blatta to send an infinite stream of blocks of some easter egg payload to all your peers at a low frequency, give it a random command id.
phf: i assume online codes share similar properties to luby, you can generate infinite numbers of blocks to do a constant broadcast
phf: an independent reconstruction of easter egg payload will be a poc
phf: reason is that i'm thinking the bureaucracy around http://logs.bitdash.io/pest/2022-12-30#1019983 3 might put a needless delay on experimentation
bitbot[asciilifeform]: Logged on 2022-12-30 20:09:35 signpost: yup, that was the thought. next step get it welded into blatta and be able to request hash-identified payload from my peers, have them confirm they have it, then request an oc-stream of particular parameters that I supply (which control the fault-tolerance and difficulty of encode/de
signpost[asciilifeform]: http://logs.bitdash.io/pest/2022-12-30#1019989 << yep, that was the justification they gave for the terrible name for the algo, that it's capable of "online" encoding ad infinitum
bitbot[asciilifeform]: Logged on 2022-12-30 20:14:19 phf[deedbot|awt]: i assume online codes share similar properties to luby, you can generate infinite numbers of blocks to do a constant broadcast
bitbot[asciilifeform]: Logged on 2022-12-30 20:13:00 phf[awt]: you could just slice it into blatta to send an infinite stream of blocks of some easter egg payload to all your peers at a low frequency, give it a random command id.
phf: http://glyf.org/screenshots/luby-success.png successful decode of the second coming by yeats
phf: signpost, what's the prng you ended up using?
← 2022-12-29 | 2022-12-31 → ↑
Random(pest) | Download hourly DB snapshot | Get Source Code