00:29 |
jonsykkel |
asciilifeform: i have 4 items on my list |
00:29 |
jonsykkel |
item1: "the Long Buffer is searched for the message's antecedents; if these cannot be located, a GetData request is issued" << still dont understand, if do this will send request for and display messges that have already been displayed in the case where: self or netchain dont match last seen && message with that self/net h |
00:29 |
jonsykkel |
ash was recvd >1h ago |
00:29 |
jonsykkel |
could very easily happen with netchains at least |
00:29 |
jonsykkel |
gotta always check verylong buffer (disk db) before sending getdata to be sure u arent requesting/displaiyng/storing same message twice, no? |
00:29 |
jonsykkel |
item2: if you follow 4.3.1 recipe as far as i can tell thers nothing to prevent duplicate packets (replayed identical packets, not same message from diff peers) in order buffer |
00:29 |
jonsykkel |
item3: info listed in 4.1.3 is not sufficient to determine Rbm in 4.3.3.2.2 |
00:29 |
jonsykkel |
item4: no mention of relaying for imediate messages in 4.3.3.1 |
| |
~ 4 hours 38 minutes ~ |
05:07 |
billymg |
$ticket btc usd |
05:07 |
billymg |
$ticker btc usd |
05:07 |
busybot |
Current BTC price in USD: $21417.28 |
| |
~ 10 hours 2 minutes ~ |
15:10 |
asciilifeform |
$ticket btc usd |
15:10 |
asciilifeform |
lol |
15:10 |
asciilifeform |
$ticker btc usd |
15:10 |
busybot |
Current BTC price in USD: $21233.1 |
15:12 |
asciilifeform |
jonsykkel: thx, will address all of your points. lemme know if find moar |
15:23 |
jonsykkel |
cool |
15:23 |
jonsykkel |
$ticket btc usd |
| |
~ 31 minutes ~ |
15:54 |
billymg |
i tried typing it quickly again and my index finger again defaulted to the more symmetrical word ending |
15:55 |
billymg |
anyway i just wanted the price to be $21,420.69 |
15:56 |
jonsykkel |
thats what i calculated to be optimal buying point also |
| |
~ 5 hours 4 minutes ~ |
21:00 |
shinohai |
I should charge half a bitcent for everyone that types `ticket` for that command from now on |
21:00 |
shinohai |
^___^ |
| |
~ 27 minutes ~ |
21:27 |
awt |
Ok so my previous theory as to why I was seeing repeat GETDATA requests was wrong. It turns out that the reason may be that not all GETDATA responses are making it into the long buffer. In any case I've found that by increasing getdata_requests_expiration_seconds to 10000 allows me to sync much more of the log without ge |
21:31 |
whaack |
test |
21:32 |
awt |
tting a dupe GETDATA request. |
21:32 |
awt |
whaack: I see you |
21:33 |
whaack |
what is the keyword for blatta commands? how do i run getdata? |
21:34 |
awt |
whaack: %at for example will list your address table |
21:34 |
awt |
You should be seeing GETDATA messages in your log if you have debug logging on. |
21:36 |
awt |
blatta GETDATA is still a bit buggy |
21:36 |
whaack_temp |
xpweird |
21:36 |
whaack |
weird |
21:36 |
whaack |
i can't see any messages in my irc |
21:37 |
whaack |
awt: oh i think the getdata was running by itself |
21:37 |
whaack |
and i just got spammed with so much that my buffer got messed up somehow |
21:39 |
awt |
let it flow |
| |
~ 1 hours 8 minutes ~ |
22:48 |
whaack |
awt: well, i think it sync'd |
22:49 |
whaack |
http://logs.bitdash.io/pest/2022-03-09#1004302 <--- this was the last msg i got |
22:49 |
bitbot |
Logged on 2022-03-09 21:14:07 PeterL[asciilifeform|billymg]: awt: is there somewhere a list of all the commands that blatta handles? |
23:00 |
whaack |
nvm, still getting replayed |
| |
~ 57 minutes ~ |
23:58 |
asciilifeform |
dulapbot log fulla replayliquishit again ftr. |