awt[asciilifeform]: Pretty cool watching the log view get updated in realtime during an initial sync.
    
    awt[asciilifeform]: !!ticker btc usd
    
    deedbot[asciilifeform]: $30,118
    
    awt[asciilifeform]: First round of syncing got me back to: http://logs.bitdash.io/pest/2021-11-16#1000669
    
    bitbot[asciilifeform]: Logged on 2021-11-16 13:25:16 PeterL: hey everybody
    
    awt[asciilifeform]: If I reset the failed GetDatas I could probably get more.
    
    signpost[asciilifeform]: !!ticker btc usd
    
    deedbot[asciilifeform]: $31,129
    
    phf: http://logs.nosuchlabs.com/log/pest/2023-06-23#1027659 << i think the correct method is to trigger a cluster of getdatas on a periodic schedule, maybe keeping track of their counts/failures. so you start by spooling a moving window of getdatas into the past, eventually settling on
    
    dulapbot: Logged on 2023-06-23 10:36:06 awt[asciilifeform]: If I reset the failed GetDatas I could probably get more.
    
    phf: infrequent getdatas for packets that never returned
    
    asciilifeform suspects that in all but pathological cases ( msg sent by ancient buggy pestrons ) getdata will return in <1s
    
    asciilifeform: for broadcasts, that is
    
    asciilifeform: ( for directs, may have to wait until the pertinent peer is online, if he's cold )
    
    asciilifeform could be wrong tho, will be interesting to see what awt finds re the failed getdatas -- do they ever succeed on retry ? (i.e. is it worth to have the moving parts phf was referring to)
    
    asciilifeform: then again when using questionable modem, 'sliding' getdata oughta win
    
    asciilifeform: so scratch all of above, lol
    
    awt[asciilifeform]: Can confirm that they succeed on retry.  Resetting attempts to 0 after initial sync putters out results in more responses.  This is afaict due to blatta getting overloaded.  (Shouldn't happen with multithreaded station)
    
    awt[asciilifeform]: Current approach is perhaps similar to "sliding window".  Turns out to be expanding sliding window tho.
    
    awt[asciilifeform]: Also, currently only connected to 1 station.  Should see better results when connected to multiple.
    
    awt[asciilifeform]: "multi-process approach"
    
    awt[asciilifeform]: phf: I'm running into issues displaying one of your messages.  I these two characters: \udbff\udffd - they seem to be "surrogate pair codepoints used by UTF-16".  Any idea how these originated or should be dealt with?  They're also a possibly byproduct of my hack to remove multipart data from messages marked as non-multipa
    
    awt[asciilifeform]: rt.
    
    awt_akris[asciilifeform]: test
    
    awt_akris[asciilifeform]: This time without the newline
    
    awt_akris[asciilifeform]: !!ticker btc usd
    
    deedbot[asciilifeform]: $30,881
    
    asciilifeform: http://logs.bitdash.io/pest/2023-06-23#1027265 << iirc phf had implemented the prev. version of asciilifeform's 'pre-draft', where these chars marked multipart text msgs ( later, per phf's suggestion, asciilifeform revised spec to make'em their own msg type )
    
    bitbot[asciilifeform]: Logged on 2023-06-23 15:46:25 awt: phf: I'm running into issues displaying one of your messages.  I these two characters: \udbff\udffd - they seem to be "surrogate pair codepoints used by UTF-16".  Any idea how these originated or should be dealt with?  They're also a possibly byproduct of my hack to remove multipart data
    
    asciilifeform had picked those particular uniturds, having determined that they don't seem to produce catastrophic effects in afaik any existing displayer
    
    asciilifeform: ( nor occur 'naturally' in any extant text likely to be pasted )
    
    
    
    dulapbot: Logged on 2022-11-28 11:06:10 phf[asciilifeform]: unfortunately until there's a great switchover, can't really do multipart reliably, since it'll spit noise into log
    
    asciilifeform: ( but! oddly not == to what awt saw in the messages tho, so possibly red herring?? )
    
    asciilifeform evidently not correctly recalled the uniturd he had used
    
    signpost[asciilifeform]: https://zerohedge.com/geopolitical/wagner-chief-declares-full-coup-against-russian-defense-ministry << wild, did the west flip prigozhin
    
    asciilifeform: signpost: 'everyone has his price'
    
    signpost[asciilifeform]: guess so eh.
    
    signpost[asciilifeform]: guy has serious pills and booze physiognomy
    
    asciilifeform: eh, that's just ordinary 'orc >40' lol
    
    
    
    asciilifeform: re upstack, see also.
    
    awt_akris[asciilifeform]: tk widgets are practically useless.  Can't even sent the font inside a Listbox.
    
    awt_akris[asciilifeform]: everything must be a Text
    
    signpost[asciilifeform]: this magical teletype box is vanity anyway. we must return to the quill.
    
    awt[asciilifeform] strokes remarkable2
    
    signpost[asciilifeform] has also, fantastic device.
    
    awt[asciilifeform]: been using to to reference the pest spec quite a bit