Show Idle (>14 d.) Chans
← 2022-07-10 | 2022-07-12 → ↓
awt[asciilifeform]: crtdaydreams: I just released a patch that fixes %unpeer
crtdaydreams[asciilifeform]: awt I see that, I'm just trying to figure out what's happening, that's what killed shinohai's station the other day if it does it again it's more than just %unpeer
awt[asciilifeform]: crtdaydreams: I get it it's just that I already tested unpeer several times tonight
signpost[asciilifeform]: awt: patched with 9974
signpost[asciilifeform]: yup seems ok now
crtdaydreams[asciilifeform]: awt righto. I ought to set up testing w/ blatta myself and try and replicate it
crtdaydreams[asciilifeform]: I'll have a go tonight, gtg for now
crtdaydreams[asciilifeform]: PeterL: may I ask for my sites rss to be added to scoopbot please?
PeterL[asciilifeform]: crtdaydreams: sure, what is the feed?
crtdaydreams[asciilifeform]: PeterL: 0xcdd.com/rss.xml
PeterL[asciilifeform]: OK, I'll get that added in just a bit
PeterL[asciilifeform]: hmm, it looks like I already added your site a while ago
crtdaydreams[asciilifeform]: PeterL oh oki, all good, I haven't uploaded in yonks but will probably be throwing something up soon
PeterL[asciilifeform]: although, looks like the bot is down at the moment.
PeterL[asciilifeform]: gave it a kick, back up again.
phf[asciilifeform|asciilifeform]: http://logs.nosuchlabs.com/log/pest/2022-07-10#1009277 << let me belaborate on this point for a second. an unreliable or otherwise mobile node might go down for arbitrary periods of time. when it comes back, afaiu right now the only form of communication it can do is ignore packet, to establish proper AT, and then wait for
dulapbot: Logged on 2022-07-10 23:27:16 asciilifeform: maybe misunderstood the q tho. is phf's notion that ~all~ msgs oughta be 'pulled' rather than pushed? why on earth wouldja do that ?
phf[asciilifeform]: broadcast OR prod to figure out what's missing. question is, why, when a mobile node comes back, not allow it to ask for packets forward? i'm not saying that this needs to be done, but more like what's the justification for doing a poll in this case, instead of pull?
PeterL[asciilifeform]: isn't that what prod does?
PeterL[asciilifeform]: IIUC, the response to a prod message will include the latest nethash, so once you get that you just use getdata until you work back to your lastest message
phf[asciilifeform]: ah see i misunderstand prod. i thought that it's periodically sent by the counterparty, and it contains latest hash, which you then can check against your packets, and do a request. so in other words you connect and wait for a periodic prod to come in, rather than initiate prod.
phf[asciilifeform]: *misunderstood
PeterL[asciilifeform]: prod and getdata will each generate a single line of response, if you just say 'give me everything after ##' then you could get a response of unlimited size
asciilifeform: PeterL: correct
phf[asciilifeform]: or you could put an N on a request, and at get most N packets. as of right now you're at parity, 5mb of data requires 5mb of request
phf[asciilifeform]: asciilifeform: at this point of practical pestronics you have to be pretty careful about what you respond to :> e.g. your "PeterL: correct" confirms two different messages on bitdash and on nosuchlabs
phf[asciilifeform]: pestronic proof of work, you want 5mb of data! you send 5mb of request!
asciilifeform: http://logs.bitdash.io/pest/2022-07-11#1009136 << this lul existed in fleanode era fwiw. but good point
bitbot[asciilifeform]: Logged on 2022-07-11 11:29:15 phf[billymg]: asciilifeform: at this point of practical pestronics you have to be pretty careful about what you respond to :> e.g. your "PeterL: correct" confirms two different messages on bitdash and on nosuchlabs
asciilifeform: http://logs.bitdash.io/pest/2022-07-11#1009135 << asciilifeform dun like 'ddos amplifiers' (even given that we have message expirations and deduplication), imho oughta know exact mass of what yer asking for in advance
bitbot[asciilifeform]: Logged on 2022-07-11 11:25:14 phf[billymg]: or you could put an N on a request, and at get most N packets. as of right now you're at parity, 5mb of data requires 5mb of request
phf[asciilifeform]: http://logs.bitdash.io/pest/2022-07-11#1009140 << why wouldn't you know exact mass in my example? you ask for n packets you get n packets. or you mean just in general that trading 1 packet for n packets is that?
bitbot[asciilifeform]: Logged on 2022-07-11 12:14:53 asciilifeform[billymg]: http://logs.bitdash.io/pest/2022-07-11#1009135 << asciilifeform dun like 'ddos amplifiers' (even given that we have message expirations and deduplication), imho oughta know exact mass of what yer asking for in advance
asciilifeform: phf: the latter
asciilifeform: poses a problem if replayed ( and yes, theoretically deduplication prevents, but in practice implementing the spec has not been trivial for the folx attempting... arguably asciilifeform's sin, for failing to make it trivial to implement )
asciilifeform: the other thing, phf : the logic whereby getdata responses bypass the timestamp expiration filter requires knowing the hash of expected msg ~in advance~
asciilifeform: which is incompat. with 'send me N'
asciilifeform: wb whaack
asciilifeform recognizes that the spec loox to readers like a chaotic spew, but in fact actually did attempt to think it through as a logical whole
signpost[asciilifeform]: hm, can't see phf now.
signpost[asciilifeform]: oh wait, yes I can.
asciilifeform: wb signpost
signpost[asciilifeform]: howdy asciilifeform
signpost[asciilifeform]: for some reason still not exchanging packets with ya directly.
asciilifeform: hm asciilifeform's at entry for signpost is stamped 6 jul
signpost[asciilifeform]: mind trying 66.69.38.97:7778 ?
signpost[asciilifeform]: cool, looks like worx now
asciilifeform: odd that it didn't update automagically
signpost[asciilifeform]: I apparently had an old entry for you in my own AT.
signpost[asciilifeform]: or incorrect in either case
phf[asciilifeform]: http://logs.bitdash.io/pest/2022-07-11#1009150 << there was no implication of that, but you know just because thought through doesn't mean thought through well. in this particular case the question was philosophical, because clearly that decision was intentional
bitbot[asciilifeform]: Logged on 2022-07-11 12:30:38 asciilifeform[billymg]: recognizes that the spec loox to readers like a chaotic spew, but in fact actually did attempt to think it through as a logical whole
asciilifeform: phf: encouraged to point out seemingly nonsensical moving parts tho, there's no guarantee that the thing is in fact properly reduced
asciilifeform: asciilifeform not had , unfortunately, much time to return to the chalkboard & refine
whaack[asciilifeform]: hm yeah i can't see phf
whaack[asciilifeform]: my chat just has a different order than bitdash.io
signpost[asciilifeform]: schrodinger's phf
phf[asciilifeform]: i'm connected at different times through asciilifeform or awt, because i can't multichat yet :>
phf[asciilifeform]: any criticism is with respective relays!
asciilifeform: a, phf still shooting single-action via slime eh
phf[asciilifeform]: at this point the slime part i have least objection to :D once (br"... became muscle memory…
awt[asciilifeform]: phf is vietcong, sniping the pest patrol one by one
asciilifeform: ... bolt-action pestron lol
asciilifeform: cheap&angry
signpost[asciilifeform]: solves asciilifeform's multi-line paste gripe, so already ahead of weechat.
signpost[asciilifeform]: hey billymg, the links in your log that point to ossasepia for trilema logs no longer work.
signpost[asciilifeform] looks forward to linking messages by message hash.
bitbot[asciilifeform]: Logged on 2022-07-10 23:42:22 crtdaydreams[signpost]: and billymg; http://paste.deedbot.org/?id=6gfd peering info
billymg[asciilifeform]: signpost: do you mean log links that start in logs.ossasepia.com/log/trilema?
billymg[asciilifeform]: if that's what you meant i wasn't able to do "ilog tunneling" with ossabot links because her logger at one point got out of sync with dulapbot
billymg[asciilifeform]: same with eric's
signpost[asciilifeform]: yeah, I clicked one that went nowhere on her site.
billymg[asciilifeform] needs to disable this feature for bitbot/dulapbot when in #pest, but the way it's currently implemented is by bot, not chan
signpost[asciilifeform]: not a big deal
signpost[asciilifeform]: solves itself when folks quote lines by message hash in the future.
signpost[asciilifeform]: hey awt, what do you have in your AT for billymg?
asciilifeform: signpost: indeed does, but q was re historical logs. afaik there aint any clean solution (other than asciilifeform's 'solution', where declared own log 'canonical' and invited folx to send in whatever's missing)
billymg[asciilifeform]: signpost: yeah i brought that up recently also, and then went to look for the previous thread (because i remembered it being discussed before)
bitbot[asciilifeform]: Logged on 2022-06-20 16:33:35 billymg: asciilifeform: regarding syncing of line indices between logotrons, what if we added a field containing the hash of speaker (minus hearsay), chan, timestamp, payload to the db?
bitbot[asciilifeform]: (ossasepia) 2020-04-20 diana_coman: in other things, since I am looking again at the annoying issue with log lines and numbers and whatnots - my current thinking is to ditch that source of trouble entirely and simply use hashes for each line to identify it uniquel
signpost[asciilifeform]: yeah, somebody'd have to retroactively munge harder identifiers into historic log
signpost[asciilifeform]: but this getting harder is part of the history, not a big deal imho
signpost[asciilifeform]: some historian can sit down and solve if they feel motivated.
asciilifeform: signpost: so long as the archived line is actually in there somewhere, you can find it, in a pinch, via text search
asciilifeform: the only historic chan that aint in asciilifeform's db at all is #o, where at one pt bot was unceremoniously kicked and asciilifeform went 'wai log them if they dun want'
asciilifeform: err, #e
asciilifeform: #o is in
awt[asciilifeform]: signpost: billymg 205.134.172.29:7778 2022-07-11 11:10:53.076080
awt[asciilifeform]: billymg: 9975, 9974 might be interesting to you - fixed a bug where %unpeer deleted random keys
signpost[asciilifeform]: wonder if that's the issue, that maybe my key got nuked on billmg's end
awt[asciilifeform]: could have been at least at some point
billymg[asciilifeform]: signpost: i've got a key for you still
billymg[asciilifeform]: starting in 'DHq'
awt[asciilifeform]: billymg: are you seeing this key using the %wot command?
signpost[asciilifeform]: those bytes of the key are now leaked to the internets, lol
billymg[asciilifeform]: did i miss something where commands changed from /command to %command?
signpost[asciilifeform]: slash still works apparently; I'm using it
signpost[asciilifeform]: with weechat's setting to send unknown commands
billymg[asciilifeform]: yeah, that's why i was confused
billymg[asciilifeform]: awt: shows same key whether via /wot signpost or %wot signpost
awt[asciilifeform]: I left slash in because why not
awt[asciilifeform]: billymg: ok just wanted to make sure they peer_id for the key was associated with the correct peer and that there aren't multiple floating about in the db.
signpost[asciilifeform]: I typically move to another buffer to issue sensitive commands, lest I accidentally fart a whole key to the wrong one.
awt[asciilifeform]: it's bound to happen
asciilifeform: signpost: asciilifeform found only 1 'final solution' for the 'missile codes into wrong buffer' problem -- separate boxes / kvm
jonsykkel[asciilifeform]: wat if ur kvm fails and sends codes to wrong box
asciilifeform: jonsykkel: what if yer ceiling fails and drops yer roof on you, similarly
asciilifeform: (suspect, moar likely)
jonsykkel[asciilifeform]: i gotta get that ceiling fixd up asap
phf[asciilifeform]: don't know why i think that it makes sense to write custom binary parser every time..
PeterL[asciilifeform]: you just need to install a second ceiling under the first one to catch it if it happens to fall down
signpost[asciilifeform]: awt: ^ oughta be usable now. seems like it gets stuck.
signpost[asciilifeform]: might be a bug on the deedbot side, not sure. I'm at some point going to get a pest station feeding directly into its postgres db to remove complication.
signpost[asciilifeform] leaves deedbot logs up for now.
trbexplorer[asciilifeform]: whaack: time since my last reconnect : 2d 22h 42m
whaack[asciilifeform]: !e view-height
trbexplorer[asciilifeform]: whaack: time since my last reconnect : 2d 22h 44m
whaack[asciilifeform]: signpost: doesn't look like it's just deedbot that gets stuck.
trbexplorer[asciilifeform]: block_height: 744613
trbexplorer[asciilifeform]: mins_since_last_block: -2
bitbot[asciilifeform]: billymg: time since my last reconnect : 8d 1h 48m
whaack[asciilifeform]: it often seems as if my bot wants one more message before it sends a reply
shinohai[asciilifeform] now reminded he needs to update bot station
busybot[asciilifeform]: The bot has been up for: 22 days 3 hours 50 minutes and 11 seconds
billymg[asciilifeform]: ok, one more time
crawlerbot[asciilifeform]: billymg: last reconnect: 1m ago; last restart: 1m ago
billymg[asciilifeform]: in working on this i updated the crawlerbot pairing for billymg, forgot to revert
bitbot[asciilifeform]: Logged on 2022-07-09 12:02:30 billymg: i have it on my todo list to move my pest station to a local box, possibly that'll fix some of the lingering issues (not being able to peer with some people, join/part)
whaack[asciilifeform]: !c net-summary
crawlerbot[asciilifeform]: Bitcoin Network (IPv4 Nodes Active Within the Last 48 hours) Global: 7343; TRB-Compatible: 29; TRB: 15
crawlerbot[asciilifeform]: TRB-Compatible by Country: United States: 7; Germany: 4; Romania: 3; Singapore: 3; Brazil: 1; Canada: 1; Italy: 1; Algeria: 1; France: 1; Andorra: 1; Sweden: 1; United Kingdom: 1; Belgium: 1; Ukraine: 1; Spain: 1; Bulgaria: 1;
crawlerbot[asciilifeform]: TRB by Country: United States: 9; Canada: 1; Romania: 1; Lithuania: 1; France: 1; New Zealand: 1; Norway: 1;
billymg[asciilifeform]: that's an all time high for TRB nodes (since the crawler started keeping track of the stat)
billymg[asciilifeform]: !c trb-status
crawlerbot[asciilifeform]: 75.106.222.93 (Alive), h=744612, v=99999, United States - peers: 267 - last probed: 29m ago
crawlerbot[asciilifeform]: 205.134.172.4 (Alive), h=744612, v=70001, United States - peers: 70 - last probed: 30m ago
crawlerbot[asciilifeform]: 85.164.243.42 (Alive), h=744612, v=99999, Norway - peers: 68 - last probed: 31m ago
crawlerbot[asciilifeform]: 185.254.196.12 (Alive), h=312191, v=99999, United States - peers: 26 - last probed: 30m ago
crawlerbot[asciilifeform]: 54.39.156.171 (Alive), h=744612, v=99999, Canada - peers: 66 - last probed: 30m ago
crawlerbot[asciilifeform]: 208.94.240.42 (Alive), h=744612, v=99999, United States - peers: 44 - last probed: 30m ago
crawlerbot[asciilifeform]: 94.176.238.102 (Busy? (No answer in 15 sec.)), h=744609, v=99999, Lithuania - peers: 24 - last probed: 30m ago
crawlerbot[asciilifeform]: 205.134.172.6 (Busy? (No answer in 15 sec.)), h=744343, v=99999, United States - peers: 34 - last probed: 30m ago
crawlerbot[asciilifeform]: 205.134.172.28 (Alive), h=744612, v=99999, United States - peers: 15 - last probed: 30m ago
crawlerbot[asciilifeform]: 71.114.46.117 (Alive), h=744612, v=99999, United States - peers: 39 - last probed: 32m ago
crawlerbot[asciilifeform]: 82.79.58.192 (Alive), h=744612, v=99999, Romania - peers: 53 - last probed: 30m ago
crawlerbot[asciilifeform]: 54.38.94.63 (Alive), h=744612, v=88888, France - peers: 68 - last probed: 30m ago
crawlerbot[asciilifeform]: 205.134.172.26 (Alive), h=744612, v=99999, United States - peers: 32 - last probed: 30m ago
crawlerbot[asciilifeform]: 103.6.212.28 (Alive), h=743581, v=99999, New Zealand - peers: 15 - last probed: 29m ago
crawlerbot[asciilifeform]: 205.134.172.27 (Alive), h=744612, v=99999, United States - peers: 4 - last probed: 30m ago
signpost[asciilifeform]: $ticker btc usd
busybot[asciilifeform]: Current BTC price in USD: $19919.9
signpost[asciilifeform]: sub-20k corn again
shinohai[asciilifeform]: evenin' signpost o/
awt[asciilifeform]: whaack: for some reason bots seem often to be behind.
awt[asciilifeform]: pestbot: ping
awt[asciilifeform]: whaack: for some reason pestbot is usually up to date
awt[asciilifeform]: Something about being connected to only one other station. Not sure what's going on though.
shinohai[asciilifeform]: awt ... latency issue?
shinohai[asciilifeform]: (Mine only connected to me but lately have noticed a bit of delay)
awt[asciilifeform]: shinohai: depends on what you mean by latency
awt[asciilifeform]: In any case, the current set of bots we have don't really care about history. The order buffer for them is really just an annoyance.
awt[asciilifeform]: for bots, setting order_buffer_check_seconds and order_buffer_expiration_seconds to like 10 should speed things up quite a bit.
phf[asciilifeform]: broadcast pkt using new packet parser/generator (take 4, maybe without selfchain?)
phf[asciilifeform]: broadcast pkt using new packet parser/generator (take 3)
asciilifeform: phf: neato
asciilifeform loox fwd to reading phf's wunderwaffe
phf[asciilifeform]: it's pretty gnarly, but that's by design
phf[asciilifeform]: la la la, test noise
← 2022-07-10 | 2022-07-12 → ↑
Random(pest) | Download hourly DB snapshot | Get Source Code