Show Idle (>14 d.) Chans


← 2021-11-25 | 2021-11-27 →
verisimilitude: I agree on mocking the dead, asciilifeform.
verisimilitude: If I happen to die first, feel free to mock me, but I don't believe that will happen.
signpost: verisimilitude: why wait til then?
signpost: (jk)
asciilifeform: http://logs.nosuchlabs.com/log/asciilifeform/2021-11-25#1067603 << currently it's rate-limited by your isp, and nic (and whatever os-level throttles downstream). multiply that by 1h and get the min. buffer size.
dulapbot: Logged on 2021-11-25 17:46:12 jonsykkel: how to determine size of dedup bufer unless theres a rate limit on communication?
jonsykkel: but that will be 30gb
asciilifeform: jonsykkel: only if yer actually anticipating 30gb/hr of valid msgs. see also.
jonsykkel: ah, missed this part
asciilifeform puts note for himself to update 1.2.7.4 with mention of buf. mem in addition to cycles.
jonsykkel: so you just drop packets if peer starts spamming, then drop peer when notice
asciilifeform: jonsykkel: automatic detection of bw hogs aint part of the spec, tho prolly oughta be part of a pheature-complete adult implementation of pest
jonsykkel: i see
asciilifeform aimed to limit spec largely to items req'd for station-to-station compat.
jonsykkel: makes sense
asciilifeform: i.e. protocol that stations gotta agree on or cannot interop
asciilifeform: $ticker btc usd
busybot: Current BTC price in USD: $54457.14
asciilifeform: cheap!1111
asciilifeform: !w poll
watchglass: Polling 17 nodes...
watchglass: 205.134.172.27:8333 : Could not connect! (Operator: asciilifeform)
watchglass: 176.9.59.199:8333 : Could not connect! (Operator: jurov)
watchglass: 185.85.38.54:8333 : Could not connect!
watchglass: 84.16.46.130:8333 : Could not connect!
watchglass: 185.163.46.29:8333 : Could not connect!
watchglass: 213.109.238.156:8333 : Could not connect!
watchglass: 205.134.172.26:8333 : Alive: (0.081s) V=99999 (/therealbitcoin.org:0.9.99.99/) Jumpers=0x1 (TRB-Compat.) Return Addr=0.0.0.0:8333 Blocks=711399
watchglass: 205.134.172.6:8333 : (172-6.core.ai.net) Alive: (0.083s) V=99999 (/therealbitcoin.org:0.9.99.99/) Jumpers=0x1 (TRB-Compat.) Return Addr=0.0.0.0:8333 Blocks=711399
watchglass: 71.191.220.241:8333 : (pool-71-191-220-241.washdc.fios.verizon.net) Alive: (0.090s) V=99999 (/therealbitcoin.org:0.9.99.99/) Jumpers=0x1 (TRB-Compat.) Blocks=711399 (Operator: asciilifeform)
watchglass: 54.39.156.171:8333 : (ns562940.ip-54-39-156.net) Alive: (0.115s) V=99999 (/therealbitcoin.org:0.9.99.99/) Jumpers=0x1 (TRB-Compat.) Blocks=711397
watchglass: 205.134.172.4:8333 : (172-4.core.ai.net) Alive: (0.089s) V=70001 (/therealbitcoin.org:0.7.0.1/) Jumpers=0x1 (TRB-Compat.) Blocks=711399
watchglass: 205.134.172.28:8333 : Alive: (0.083s) V=99999 (/therealbitcoin.org:0.9.99.99/) Jumpers=0x1 (TRB-Compat.) Return Addr=0.0.0.0:8333 Blocks=711399 (Operator: whaack)
watchglass: 208.94.240.42:8333 : Alive: (0.175s) V=99999 (/therealbitcoin.org:0.9.99.99/) Jumpers=0x1 (TRB-Compat.) Blocks=711399
watchglass: 143.202.160.10:8333 : Alive: (0.184s) V=70001 (/therealbitcoin.org:0.7.0.1/) Jumpers=0x1 (TRB-Compat.) Blocks=711399
watchglass: 54.38.94.63:8333 : (ns3140226.ip-54-38-94.eu) Alive: (0.257s) V=88888 (/therealbitcoin.org:0.8.88.88/) Jumpers=0x1 (TRB-Compat.) Blocks=711399
watchglass: 103.36.92.112:8333 : (terebe.ns01.net) Alive: (0.671s) V=99999 (/therealbitcoin.org:0.9.99.99/) Jumpers=0x1 (TRB-Compat.) Blocks=711399
asciilifeform: oh hm did .27 finally oom? (cgra were you testing a new poison arrow?)
asciilifeform will look at it laters
jonsykkel: speaking of interop, thimbronion i can communicate with blatta, but only if i send whole irc command like this 16:32 < jonsykkel> :jonsykkel PRIVMSG #pest :hi
jonsykkel: otherwise it crashes
watchglass: 192.151.158.26:8333 : Busy? (No answer in 100 sec.)
jonsykkel: also, does "little endian no exceptions" extend to sha256 also?
asciilifeform: jonsykkel: why wouldn't it ?
jonsykkel: dont know
jonsykkel: "off the shelf" sha256s will not give correct result then, maybe there should be warning
asciilifeform: jonsykkel: erry sha256 i've seen to date uses little-endian order
asciilifeform: (internally, that is. the hash itself is not endianism-sensitive)
jonsykkel: ye i meant when serialize it
jonsykkel: hash correct but wrong packet
asciilifeform: jonsykkel: afaik the existing impls. ( in particular, thimbronion's ) do The Right Thing there.
jonsykkel: pretty sure mine does the wrong thing and it speaks to thimbronions impl
asciilifeform: jonsykkel: i rec to write a detailed illustration of where.
asciilifeform will read; sadly not has time to dig in properly atm
jonsykkel: of where?
asciilifeform: where wrong thing
jonsykkel: ok, sure
asciilifeform: jonsykkel: ty
thimbronion: jonsykkel: blatta expects the full raw irc command in the message body
jonsykkel: seems so yes, question is why
jonsykkel: temporary thing?
thimbronion: jonsykkel: what do you expect to be in the body?
jonsykkel: just the text part of the message is what i would expect
thimbronion: jonsykkel: how would your irc client interpret that?
jonsykkel: thimbronion: your pestron would prefix the stuff before it sends it to irc client
jonsykkel: unless ive severely misunderstood the spec
thimbronion: jonsykkel: can you point me to the place in the spec you're referring to?
jonsykkel: thimbronion: 4.1.2. broadcast message - 324 byte text field in message thing
thimbronion: jonsykkel: hm not seeing what you mean
cgra: http://logs.nosuchlabs.com/log/asciilifeform/2021-11-26#1067642 << did throw coupla, yesterday or day before. kept sctratching head why didn't kill it... i doubt my poison was this slow
dulapbot: Logged on 2021-11-26 10:31:36 asciilifeform: oh hm did .27 finally oom? (cgra were you testing a new poison arrow?)
jonsykkel: thimbronion:
jonsykkel: irc client A sends to pestron B ":jonsykkel PRIVMSG #pest :hi"
jonsykkel: pestron B sends "hi" to his peer pestron C
jonsykkel: pestron C sends ":jonsykkel PRIVMSG #pest :hi" to irc client D
jonsykkel: this is how i imagine its meant to work, irc stuff only being a way to communicate with your own pestron locally
cgra: asciilifeform: the specific mixture here was receive buffer filled with fabricated getheaders messages
asciilifeform: cgra: neato, plox to post recipe. i'ma restart the noad later today (hands quite full just nao)
cgra: asciilifeform: recipe upcoming in the oom summary
asciilifeform: cgra: ty!
dulapbot: Logged on 2021-11-26 11:37:39 jonsykkel: this is how i imagine its meant to work, irc stuff only being a way to communicate with your own pestron locally
cgra: asciilifeform: when you get to ig, and if logs indicate, try and check whether node's last breath was about ~57MB getheaders responses or something else
asciilifeform: cgra: will do
punkman: pest station shouldn't be sending "PRIVMSG" to other station, that's between operator's IRC client and station's IRC hole
thimbronion: well shit. looks like I've got some changes to make.
dulapbot: Logged on 2021-11-26 11:37:39 jonsykkel: this is how i imagine its meant to work, irc stuff only being a way to communicate with your own pestron locally
asciilifeform: strings like 'PRIVMSG' only travel b/w irc client and its pestron.
asciilifeform: they should not appear in msg payloads or anywhere in the red packet.
jonsykkel: asciilifeform: dunno if this illustrates but what i meant is that i dont think people by default think about sha256 result as 256bit number with a endianess, seems to be treated like a string of bytes by ppl and code in my experience anyway
jonsykkel: jon@pc:~$ echo -n "<pest message N>" | sha256
jonsykkel: 10868f6678aaafec47ad5c08208e8d6d37877214f502038a9b3a9451c74202ea
jonsykkel: am i to understand 0xEA byte goes first (lowest address) in selfchain field of message N+1?
jonsykkel: and same with hmac
punkman: jonsykkel: good question. As I understand it, when speaking of endianness you also gotta think of multi-byte words
punkman: so if I was to send you a string of bytes, doesn't make much sense to reorder anything. if I'm sending you 64bit words, then we gotta agree on endianness
punkman: example from go std lib, it only reorders int16/int32/int64 types, string of uint8 just passes through
punkman: looking at my packet structure, I only have timestamps as uint64, everything else is either uint8 or array of uint8
punkman: so I guess we must specify if hashes are 32 bytes or 4 64bit words
asciilifeform: punkman: lol, 1 of these ? had nfi there were such chumpatrons still inbiz
dulapbot: (trilema) 2014-10-28 asciilifeform: unrelated: https://archive.org/details/HowToStartYourOwnCountry << a little riot of a book. no-bullshit guide to (failed) attempts at ab initio sovereignty. (i met the author in person, incidentally. fun fella.)
asciilifeform: ( for thrd-completeness, oblig mp wank re above )
dulapbot: (trilema) 2014-10-28 mircea_popescu: re the "how to start your own country" thing, the opening model is so fucking braindamaged it curls my hairs.
punkman: I doubt Ghislaine is on same level as the "sovereign" scammers
punkman: https://twitter.com/Trial_Tracker will be of interest to fans
← 2021-11-25 | 2021-11-27 →