Show Idle (>14 d.) Chans
← 2021-11-23 | 2021-11-25 → ↓
09:14 jonsykkel packets from paused peers should be processed normally except messages not sent to operator?
↖
~ 52 minutes ~
10:06 cgra asciilifeform: in the pest timestamp footnote, i'd explicitly specify 1) the epoch and 2) the time unit.
↖
~ 50 minutes ~
10:56 punkman "You can already see this on ETH. Downturn => much higher demand for blockspace as all protocols must rebalance => much higher fees. Demand driven by MEV. A single oracle update could theoretically congest the entire chain."
10:57 punkman so bitcoin price goes down, eth (and other shitcoins) price goes down, all the "automated market makers" and "liquidity pools" must rebalance/move money around, blockchain gets congested, fees skyrocket
~ 2 hours ~
12:58 gregory5 http://logs.nosuchlabs.com/log/asciilifeform/2021-11-22#1067308 << the inventor of CSS, Hakon Lie, was also Norwegian.
↖
12:58 dulapbot Logged on 2021-11-22 21:18:03 asciilifeform: prior to jonsykkel showing up, could name 3 norwegians , all dead : ibsen, quisling, and naggum
12:58 gregory5 http://logs.nosuchlabs.com/log/asciilifeform/2021-11-23#1067381 << I was about to say the same thing.
12:58 dulapbot Logged on 2021-11-23 16:12:00 asciilifeform: thimbronion: a useful pheature for debug log may be to show by how much / in what dir. timestamp stale.
12:59 gregory5 asciilifeform: thimbronion: I had not known that sixty-four bit timestamps were a separate standard.
13:00 gregory5 I thought they were just thirty-two bit timestamps which were widened in order to avoid 2038 overflow.
↖
13:09 gregory5 how is the value of the sixty-four bit timestamp determined?
↖
~ 1 hours 21 minutes ~
14:31 asciilifeform http://logs.nosuchlabs.com/log/asciilifeform/2021-11-24#1067396 << lolno. reread that section : 'Temporarily disable all communication with the peer identified by HANDLE, without discarding any data.'
↖
14:31 dulapbot Logged on 2021-11-24 04:07:45 jonsykkel: packets from paused peers should be processed normally except messages not sent to operator?
14:31 asciilifeform what part of 'all' is unclear ?
14:31 asciilifeform http://logs.nosuchlabs.com/log/asciilifeform/2021-11-24#1067397 << this is a good point and will go in next ver.
14:31 dulapbot Logged on 2021-11-24 04:59:52 cgra: asciilifeform: in the pest timestamp footnote, i'd explicitly specify 1) the epoch and 2) the time unit.
14:31 asciilifeform http://logs.nosuchlabs.com/log/asciilifeform/2021-11-24#1067400 << at least as 'great' as quisling, lol!
14:31 dulapbot Logged on 2021-11-24 07:51:45 gregory5: http://logs.nosuchlabs.com/log/asciilifeform/2021-11-22#1067308 << the inventor of CSS, Hakon Lie, was also Norwegian.
14:32 asciilifeform http://logs.nosuchlabs.com/log/asciilifeform/2021-11-24#1067405 << correct
14:32 dulapbot Logged on 2021-11-24 07:53:41 gregory5: I thought they were just thirty-two bit timestamps which were widened in order to avoid 2038 overflow.
14:43 asciilifeform http://logs.nosuchlabs.com/log/asciilifeform/2021-11-24#1067406 << '64-bit unsigned fixed-point number, in seconds relative to 00:00:00 January 1, 1970, UTC'
↖ ↖
14:43 dulapbot Logged on 2021-11-24 08:02:58 gregory5: how is the value of the sixty-four bit timestamp determined?
14:43 asciilifeform $ticker btc usd
14:43 busybot Current BTC price in USD: $56146.47
14:43 asciilifeform !w poll
14:43 watchglass Polling 17 nodes...
14:43 watchglass 176.9.59.199:8333 : Could not connect! (Operator: jurov)
14:43 watchglass 185.85.38.54:8333 : Could not connect!
14:43 watchglass 84.16.46.130:8333 : Could not connect!
14:43 watchglass 213.109.238.156:8333 : Could not connect!
14:43 watchglass 185.163.46.29:8333 : Could not connect!
14:43 watchglass 54.39.156.171:8333 : (ns562940.ip-54-39-156.net) Alive: (0.111s) V=99999 (/therealbitcoin.org:0.9.99.99/) Jumpers=0x1 (TRB-Compat.) Blocks=711132
14:43 watchglass 205.134.172.27:8333 : Alive: (0.090s) V=99999 (/therealbitcoin.org:0.9.99.99/) Jumpers=0x1 (TRB-Compat.) Blocks=711132 (Operator: asciilifeform)
14:43 watchglass 205.134.172.6:8333 : (172-6.core.ai.net) Alive: (0.081s) V=99999 (/therealbitcoin.org:0.9.99.99/) Jumpers=0x1 (TRB-Compat.) Return Addr=0.0.0.0:8333 Blocks=711132
14:43 watchglass 205.134.172.4:8333 : (172-4.core.ai.net) Alive: (0.083s) V=70001 (/therealbitcoin.org:0.7.0.1/) Jumpers=0x1 (TRB-Compat.) Blocks=711132
14:43 watchglass 205.134.172.26:8333 : Alive: (0.081s) V=99999 (/therealbitcoin.org:0.9.99.99/) Jumpers=0x1 (TRB-Compat.) Return Addr=0.0.0.0:8333 Blocks=711132
14:43 watchglass 71.191.220.241:8333 : (pool-71-191-220-241.washdc.fios.verizon.net) Alive: (0.123s) V=99999 (/therealbitcoin.org:0.9.99.99/) Jumpers=0x1 (TRB-Compat.) Blocks=711132 (Operator: asciilifeform)
14:43 watchglass 205.134.172.28:8333 : Alive: (0.083s) V=99999 (/therealbitcoin.org:0.9.99.99/) Jumpers=0x1 (TRB-Compat.) Return Addr=0.0.0.0:8333 Blocks=711132 (Operator: whaack)
14:43 watchglass 208.94.240.42:8333 : Alive: (0.175s) V=99999 (/therealbitcoin.org:0.9.99.99/) Jumpers=0x1 (TRB-Compat.) Blocks=711132
14:43 watchglass 143.202.160.10:8333 : Alive: (0.244s) V=70001 (/therealbitcoin.org:0.7.0.1/) Jumpers=0x1 (TRB-Compat.) Blocks=711132
14:43 watchglass 54.38.94.63:8333 : (ns3140226.ip-54-38-94.eu) Alive: (0.256s) V=88888 (/therealbitcoin.org:0.8.88.88/) Jumpers=0x1 (TRB-Compat.) Blocks=711132
14:43 watchglass 103.36.92.112:8333 : (terebe.ns01.net) Alive: (0.643s) V=99999 (/therealbitcoin.org:0.9.99.99/) Jumpers=0x1 (TRB-Compat.) Blocks=711132
14:45 watchglass 192.151.158.26:8333 : Busy? (No answer in 100 sec.)
~ 20 minutes ~
15:05 cgra http://logs.nosuchlabs.com/log/asciilifeform/2021-11-24#1067416 << my uneducated assumption was pest timestamp is an integer. i'd specify the fixed-pointness and its bit division too in the footnote
↖
15:05 dulapbot Logged on 2021-11-24 09:36:46 asciilifeform: http://logs.nosuchlabs.com/log/asciilifeform/2021-11-24#1067406 << '64-bit unsigned fixed-point number, in seconds relative to 00:00:00 January 1, 1970, UTC'
15:10 gregory5 http://logs.nosuchlabs.com/log/asciilifeform/2021-11-24#1067416 << so the value isn't an integer? it is a "fixed point" number? how many points after the decimal place?
15:10 dulapbot Logged on 2021-11-24 09:36:46 asciilifeform: http://logs.nosuchlabs.com/log/asciilifeform/2021-11-24#1067406 << '64-bit unsigned fixed-point number, in seconds relative to 00:00:00 January 1, 1970, UTC'
15:11 gregory5 asciilifeform: currently, the value which I am sending is the thirty-two bit timestamp, but with four zeros added onto the end.
↖ ↖
15:11 gregory5 by "four zeros" I mean "four zero bytes."
15:12 cgra actually, isn't fixed-pointness or an integer just two different ways to look at the same thing, if you adjust the unit accordingly
15:13 gregory5 thimbronion: you might reconsider using Python's time.time()
↖
15:13 gregory5 according to the official manual: "The epoch is the point where the time starts, and is platform dependent."
15:26 cgra http://logs.nosuchlabs.com/log/asciilifeform/2021-11-24#1067443 << blatta message timestamps are integers, in 1-second units, note thimbronion gregory5
15:26 dulapbot Logged on 2021-11-24 10:04:51 gregory5: asciilifeform: currently, the value which I am sending is the thirty-two bit timestamp, but with four zeros added onto the end.
15:28 asciilifeform http://logs.nosuchlabs.com/log/asciilifeform/2021-11-24#1067439 << integer
15:28 dulapbot Logged on 2021-11-24 09:59:23 cgra: http://logs.nosuchlabs.com/log/asciilifeform/2021-11-24#1067416 << my uneducated assumption was pest timestamp is an integer. i'd specify the fixed-pointness and its bit division too in the footnote
15:29 asciilifeform dunno why i said 'fixed point' lol
15:29 asciilifeform it's an integer. as returned by current linux.
15:29 asciilifeform http://logs.nosuchlabs.com/log/asciilifeform/2021-11-24#1067443 << this is correct (unless you're suffering endianism issues)
15:29 dulapbot Logged on 2021-11-24 10:04:51 gregory5: asciilifeform: currently, the value which I am sending is the thirty-two bit timestamp, but with four zeros added onto the end.
15:30 * asciilifeform must bbl
~ 2 hours 51 minutes ~
18:22 thimbronion http://logs.nosuchlabs.com/log/asciilifeform/2021-11-24#1067446 <-> http://logs.nosuchlabs.com/log/asciilifeform/2021-11-23#1067384
18:22 dulapbot Logged on 2021-11-24 10:07:18 gregory5: thimbronion: you might reconsider using Python's time.time()
18:22 dulapbot Logged on 2021-11-23 16:14:25 thimbronion: asciilifeform: possibly blatta is doing that? message.timestamp = int(time.time())
18:23 thimbronion oh I see -- REconsider. Yeah reconsidering.
~ 27 minutes ~
18:51 thimbronion gregory5: for epoch time in seconds 1637779208, these are the bytes that blatta would put in the timestamp field: '08879e6100000000'
~ 55 minutes ~
19:46 cgra i thought unix timestamp had smaller than 1-second units, but i was apparently wrong (maybe too much personal oop/spackle stack history).
~ 17 minutes ~
20:03 asciilifeform pest timestamp wouldn't imho benefit from sub-second units anyway
20:03 asciilifeform its only purpose is to put a damper on replayism
~ 2 hours 8 minutes ~
22:12 jonsykkel http://logs.nosuchlabs.com/log/asciilifeform/2021-11-24#1067407 << right, this is what i thouht at first, but then if pause peer you will still probably receive hearsay from said peer if someone else in net relays his messages
↖
22:12 dulapbot Logged on 2021-11-24 09:24:41 asciilifeform: http://logs.nosuchlabs.com/log/asciilifeform/2021-11-24#1067396 << lolno. reread that section : 'Temporarily disable all communication with the peer identified by HANDLE, without discarding any data.'
22:13 jonsykkel also if unpause 20days later will be getdata city
↖
22:15 jonsykkel (unless aforementioned hearsay messages get added to peers chain?)
~ 50 minutes ~
23:06 jonsykkel purpose of pausing is simply to cut link to peer? should this be implemented as skiping over his keys when verifying incoming udp paket?
↖
23:17 asciilifeform http://logs.nosuchlabs.com/log/asciilifeform/2021-11-24#1067465 << you will. (if dun want to, is what 'gag' is for)
23:17 dulapbot Logged on 2021-11-24 17:06:08 jonsykkel: http://logs.nosuchlabs.com/log/asciilifeform/2021-11-24#1067407 << right, this is what i thouht at first, but then if pause peer you will still probably receive hearsay from said peer if someone else in net relays his messages
23:17 asciilifeform http://logs.nosuchlabs.com/log/asciilifeform/2021-11-24#1067467 << only if there was buncha items direct-messaged or hearsayed only via ~that~ peer
23:17 dulapbot Logged on 2021-11-24 17:07:21 jonsykkel: also if unpause 20days later will be getdata city
23:17 asciilifeform http://logs.nosuchlabs.com/log/asciilifeform/2021-11-24#1067469 << correct.
23:17 dulapbot Logged on 2021-11-24 17:59:52 jonsykkel: purpose of pausing is simply to cut link to peer? should this be implemented as skiping over his keys when verifying incoming udp paket?
23:18 asciilifeform ( when verifying and also when sending )
23:18 jonsykkel alright
23:20 * asciilifeform thinks: prolly oughta still store msgs from the gagged, to avoid infinite getdata wank re same
23:20 asciilifeform will go in next rev of spec if no one suggests a cleaner way.
← 2021-11-23 | 2021-11-25 → ↑

Random(asciilifeform) | Download hourly DB snapshot | Get Source Code

Theme: Light | Dark | System Default