| 00:03 |
shinohai |
aha awt I should look into way to add ATH to bot |
| |
~ 1 hours 34 minutes ~ |
| 01:37 |
shinohai |
$ticker btc usd |
| 01:37 |
busybot |
Current BTC price in USD: $67411.4 |
| |
~ 12 hours 50 minutes ~ |
| 14:28 |
awt |
Test message for logger |
| 14:29 |
shinohai |
Good morning all! Logger appears to be down from my pov too. |
| |
↖ |
| 14:31 |
awt |
shinohai: I see above message in the log |
| 14:37 |
awt |
there he is |
| 14:37 |
shinohai |
\o/ |
| 14:38 |
billymg |
ok, strange that it wasn't working with --password field today |
| 14:38 |
billymg |
i did change the pass, maybe there's a char limit |
| 14:38 |
shinohai |
I am *still* unable to send you DM billymg |
| 14:38 |
billymg |
shinohai: likewise apparently |
| 14:38 |
awt |
I was about to try and get that working with weechat but haven't really messed with passwords yet |
| 14:39 |
billymg |
i also wasn't able to DM with PeterL yesterday, so far only with awt |
| 14:39 |
awt |
shinohai: just sent you a dm |
| 14:40 |
awt |
ok so dms working between me and shinohai as well |
| 14:42 |
shinohai |
I suspect perhaps a client setting on billymg 's end? Dunno ... |
| 14:42 |
billymg |
awt: a nicety for the commands such as /wot or /at would be to include a header line in the results, like "WOT (3):" followed by the results on the next lines |
| 14:43 |
awt |
billymg: yeah true. that would help. |
| 14:44 |
billymg |
shinohai: are you also able to DM with PeterL? |
| 14:44 |
awt |
billymg: one thing you could try is standing up the testnet using the included script and try dming between the configured local stations |
| 14:45 |
awt |
might eliminate your IRC client as part of the problem |
| 14:45 |
awt |
billymg: I was able to dm PeterL yesterday |
| 14:45 |
shinohai |
billymg: I *think* I sent PeterL DM but he hasn't sent me a key yet so dunno if I can |
| 14:45 |
billymg |
i don't see how it would be my client if i can send/receive DMs with you though |
| 14:45 |
awt |
no you can't dm w/out a key |
| 14:45 |
awt |
billymg: good point |
| 14:46 |
billymg |
perhaps i screwed up the keying for shinohai and PeterL |
| 14:46 |
awt |
billymg: that makes sense |
| 14:46 |
billymg |
awt: is there a way to check if "have key for given user" |
| 14:47 |
shinohai |
billymg: feel free to gpgram me what you have in your AT for me |
| 14:47 |
awt |
billymg: /wot <handle> |
| 14:47 |
billymg |
ok, i at least have keys for everyone in my wot |
| 14:48 |
billymg |
shinohai: will send so we can see if it's correct or not |
| 14:48 |
shinohai |
For billymg I haz key beginning with: `52NJcXUJ` |
| 14:48 |
billymg |
shinohai: hrm, same |
| 14:48 |
awt |
possibly some whitespace in they key? |
| 14:49 |
awt |
no that should cause some kind of exception |
| 14:49 |
billymg |
awt: doesn't look like it |
| 14:49 |
awt |
would be interesting to know if either of you see anything in your logs when the other tries to dm |
| 14:50 |
shinohai |
My logs: |
| 14:50 |
shinohai |
[127.0.0.1:46708] -> 'PRIVMSG billymg :test\r\n' |
| 14:50 |
shinohai |
sending message: :shinohai!root@127.0.0.1 PRIVMSG billymg :test |
| 14:51 |
awt |
Could probably improve that log message by including dest address |
| 14:52 |
billymg |
shinohai: where are you seeing those logs? |
| 14:52 |
billymg |
inside the logs table in sqlite db? |
| 14:53 |
shinohai |
billymg: I start my instance by piping to `|tee logfile.txt` |
| 14:53 |
shinohai |
(so I can run inside screen) |
| 14:53 |
awt |
billymg: start blatta with the --debug flag |
| 14:54 |
shinohai |
Full start command I'm using: |
| 14:54 |
shinohai |
`/usr/local/bin/python2.7 blatta --debug --port=7778 --address-table-path config.py | tee logfile.txt` |
| 14:55 |
billymg |
oh, --debug flag would be useful |
| 14:56 |
billymg |
what's the --address-table-path for> |
| 14:56 |
billymg |
? |
| 14:57 |
awt |
billymg: it's for testing. You can import a .py file with a list of peers |
| 14:57 |
billymg |
ok, gotcha |
| 14:58 |
awt |
interesting debugging challenges w/o persistent socket connections |
| 14:58 |
awt |
also w/o central server logs lol |
| 15:00 |
shinohai |
That's why I decided to write out my debug log to a file, so can go back and look over. |
| |
~ 1 hours ~ |
| 16:01 |
shinohai |
awt - what was your idea(s) for making the nicklist populate? I'm still mulling this problem. |
| |
~ 34 minutes ~ |
| 16:36 |
awt |
shinohai: best thing to do I can think of rn is send the client a fake /join message the first time a message is received from a given handle. Reset timer every time a new message is received, and send a /part when the timer expiers. Timeout can be configurable. |
| 16:37 |
awt |
This would work well with the rubbish solution asciilifeform mentioned in #asciilifeform earlier today for ephemeral ports timing out due to inactivity. |
| 16:37 |
shinohai |
Sounds proper. |
| 16:39 |
busybot_ |
test |
| 16:40 |
busybot_ |
well can connect via znc just fine. sadly bot will not connect to znc! :( |
| 16:53 |
shinohai |
$vwap |
| 16:53 |
busybot |
The 24-Hour VWAP for BTC is $ 67473.85 USD |
| 16:56 |
PeterL |
I am seeing stuff in the log that is not showing up here? |
| 17:05 |
shinohai |
PeterL: whatcha seeing? |
| 17:08 |
PeterL |
shinohai, could you send me a key? I would like to try out adding a key from somebody else |
| 17:09 |
shinohai |
kk PeterL will gpgram you over on dulapnet |
| 17:12 |
awt |
PeterL: which log? |
| 17:15 |
PeterL |
OK, added peer info for shinohai, should work? |
| 17:17 |
shinohai |
PeterL can send me ur AT info? Don't hafta gpgram I suppose, since no key a DM on dulapnet will work |
| |
~ 20 minutes ~ |
| 17:37 |
PeterL |
hmm, stuff I am saying is showing up in log, but I am not seeing anything from awt or shinohai that are in the log? |
| 17:38 |
shinohai |
weird and I just sent you DM PeterL |
| 17:38 |
shinohai |
lemme try sumthin here in a minute. |
| 17:41 |
awt |
PeterL: what are you looking for in the log? |
| 17:42 |
shinohai |
I added PeterL but getting `rejected black packet with bad signature for 1IRaEkAxKn7ltD<restofkey>` |
| 17:42 |
awt |
That just means there was a message from *someone* that didn't match that key |
| 17:43 |
awt |
right now blatta just goes tests the message against each key until it decrypts |
| 17:43 |
awt |
the only time you won't see that message is when the first key tried against the message happens to decrypt |
| 17:46 |
shinohai |
I think cause is PeterL just informed me I wasn't in his wot .... so still trying to see what's up there. |
| |
~ 19 minutes ~ |
| 18:06 |
awt |
shinohai: weird how you were able to get two asciilifeform handles in your wot, but it crashed for PeterL. |
| 18:07 |
shinohai |
ikr? |
| 18:08 |
shinohai |
And funny enuf 3 entries for asciilifeform *still there* - |
| 18:08 |
shinohai |
13:02:33 -- asciilifeform 71.191.220.241:55558 2021-11-08 17:49:27 |
| 18:08 |
shinohai |
13:02:33 -- asciilifeform 71.191.220.241:52405 2021-11-08 17:38:57 |
| 18:08 |
shinohai |
13:02:33 -- asciilifeform 71.191.220.241:13337 2021-11-08 17:22:57 |
| 18:08 |
shinohai |
2 being "ephemeral ports" I suppose |
| |
↖ |
| 18:14 |
awt |
at or wot? |
| 18:15 |
awt |
at is gonna have every different address/port combo for every handle in wot. |
| 18:15 |
shinohai |
ah ok |
| 18:15 |
shinohai |
yes in "wot" single entry |
| |
↖ |
| |
~ 1 hours 8 minutes ~ |
| 19:24 |
PeterL |
hi again. I nuked my db and restarted, not sure if I am connected to anybody? |
| 19:24 |
billymg |
i'm seeing your messages |
| 19:24 |
shinohai |
same I see ur messages |
| 19:26 |
PeterL |
oh, yay! |
| |
~ 2 hours 22 minutes ~ |
| 21:49 |
PeterL |
so my computer fan was running constantly with blatta going. I threw a time.sleep(0.1) into the server loop and now my fan is not coming on at all |
| 21:51 |
shinohai |
Weird, I have a shitty thinkpad im running on and haven't had fan come on or had abnormal cpu temps. |
| |
~ 17 minutes ~ |
| 22:08 |
billymg |
ah, yeah, top shows blatta at 100% for me too |
| 22:10 |
shinohai |
O.o |
| 22:17 |
shinohai |
aha PeterL's suggestion *did* make my instance stop showing 100% cpu use in top |
| 22:17 |
shinohai |
(though I noticed no lag or anything) |
| |
~ 32 minutes ~ |
| 22:50 |
awt |
lulz. yeah I guess a while loop with no sleep could be cpu intensive |
| 22:51 |
awt |
100% here too |
| 22:52 |
awt |
never noticed because I've never run it locally |