00:53 |
awt |
Currently paging up through the logs on the desktop client. feels good. |
| |
~ 9 hours 44 minutes ~ |
10:38 |
billymg |
my ukr server is unreachable, network graph in hosting dashboard shows it's been down last 30 min or so, just opened a ticket |
10:38 |
awt |
billymg: nato probably took it out for not being gay enough |
10:38 |
billymg |
ah hey, back up |
10:38 |
billymg |
!. uptime |
10:38 |
bitbot |
billymg: time since my last reconnect : 0d 0h 4m |
10:39 |
billymg |
kek |
10:39 |
billymg |
cool thing about pest is those missed messages make it back to bitbot in the replay |
10:39 |
billymg |
though a bit out of order |
10:40 |
* |
billymg is not running latest blatta yet so could be due to that |
| |
~ 32 minutes ~ |
11:12 |
asciilifeform |
billymg: awt's new logotron seems to have the pill for this. |
11:12 |
bitbot |
Logged on 2023-06-19 10:35:31 awt: New station has a 'page' command, accessible via the json api, which should make it pretty straight forward to stand up a www log reader that reads directly from the pest log. |
11:15 |
billymg |
neato, looking forward to awt's blatta 2.0 |
| |
~ 2 hours 22 minutes ~ |
13:37 |
asciilifeform |
!!ticker btc usd |
13:37 |
deedbot |
$29,973 |
| |
~ 26 minutes ~ |
14:03 |
awt |
billymg: while debugging paging, I'm noticing that the system time for your bot and your personal station don't seem to be in sync. |
14:04 |
awt |
i.e. in the timestamp ordered log, your command is coming after the bot reply. |
| |
~ 50 minutes ~ |
14:54 |
billymg |
awt: they are in different timezones, bitbot is in EST and my station is in UTC, though it looks like my personal station's clock has drifted nearly 30 minutes |
14:55 |
billymg |
actually, not so much, more like 10 minutes |
15:01 |
billymg |
!. uptime |
15:01 |
bitbot |
billymg: time since my last reconnect : 0d 4h 26m |
15:12 |
awt |
!!ticker btc usd |
15:12 |
deedbot |
$30,125 |
| |
~ 1 hours 29 minutes ~ |
16:42 |
phf |
http://logs.nosuchlabs.com/log/pest/2023-06-22#1027630 << i didn't even think about it, i'm pretty sure i'm sending timestamps in local timezone, and i'm supposed to know better |
16:42 |
dulapbot |
Logged on 2023-06-22 14:52:56 billymg[asciilifeform]: awt: they are in different timezones, bitbot is in EST and my station is in UTC, though it looks like my personal station's clock has drifted nearly 30 minutes |
16:45 |
phf |
disregard, my pest.lisp does the right thing |
| |
~ 34 minutes ~ |
17:20 |
asciilifeform |
fwiw no timezonism in spec ( formulated as 'A Time consists of an Integer[8], obtained from a Pest station’s 64-bit monotonic epoch clock at the time of Message encoding; traditionally defined as: "a 64-bit unsigned fixed-point number, in seconds relative to 00:00:00 January 1, 1970, UTC".' ) |
17:22 |
* |
asciilifeform marvels that sumbody could be sending timezonized timestamps to a station whose zone != , and they still got received?! |
17:23 |
asciilifeform |
( phf's zone iirc equals asciilifeform's, but afaik nobody else's of the folx tuned in ) |
| |
↖ |
17:25 |
asciilifeform |
or , hm, billymg's observation was in re loggers, neh. so there could drift by however much |
17:25 |
* |
asciilifeform loox fwd to the abolition of the irc frontend |
17:25 |
awt |
Personally abolished - though station still mute |
17:27 |
awt |
No longer in full Helen Keller mode |
17:28 |
asciilifeform |
awt: nifty. ( would like to try it once 'both spreading and eating work'(tm) ) |
17:29 |
awt |
Also, sadly I'm coming to the conclusion I will need scrollbars. Thought pg up, pg down would be sufficient, but, gotta know if you're at the top or bottom or somewhere in the middle somehow. |
17:30 |
asciilifeform |
awt: could display sumthing like phf's dragons (e.g. 'fiat lux!' at top, 'nao' on bottom) but if you've gui, wainot scrollbar |
17:30 |
awt |
oh hmm |
17:31 |
awt |
I'm not witty enough to come up with indicators like that |
17:31 |
awt |
so let there be scrollbars |
| |
~ 5 hours 25 minutes ~ |
22:57 |
awt |
!!ticker btc usd |
22:57 |
deedbot |
$29,960 |