| 01:05 |
jonsykkel |
ignore paket is 428byte Message field full of rngolade? |
| |
~ 55 minutes ~ |
| 02:01 |
asciilifeform |
jonsykkel: well to be pedantic, is simply a packet where command==0xff. but recommended to fill it up with rngolade, yes |
| 02:03 |
jonsykkel |
i see |
| |
~ 14 hours 43 minutes ~ |
| 16:46 |
asciilifeform |
$ticker btc usd |
| 16:46 |
busybot |
Current BTC price in USD: $57823.15 |
| 16:46 |
asciilifeform |
!w poll |
| 16:46 |
watchglass |
Polling 17 nodes... |
| 16:46 |
watchglass |
176.9.59.199:8333 : Could not connect! (Operator: jurov) |
| 16:46 |
watchglass |
185.85.38.54:8333 : Could not connect! |
| 16:46 |
watchglass |
84.16.46.130:8333 : Could not connect! |
| 16:46 |
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=710586 |
| 16:46 |
watchglass |
185.163.46.29:8333 : Could not connect! |
| 16:46 |
watchglass |
213.109.238.156:8333 : Could not connect! |
| 16:46 |
watchglass |
205.134.172.4:8333 : (172-4.core.ai.net) Alive: (0.082s) V=70001 (/therealbitcoin.org:0.7.0.1/) Jumpers=0x1 (TRB-Compat.) Blocks=710586 |
| 16:46 |
watchglass |
205.134.172.26:8333 : Alive: (0.084s) V=99999 (/therealbitcoin.org:0.9.99.99/) Jumpers=0x1 (TRB-Compat.) Return Addr=0.0.0.0:8333 Blocks=710586 |
| 16:46 |
watchglass |
71.191.220.241:8333 : (pool-71-191-220-241.washdc.fios.verizon.net) Alive: (0.154s) V=99999 (/therealbitcoin.org:0.9.99.99/) Jumpers=0x1 (TRB-Compat.) Blocks=710586 (Operator: asciilifeform) |
| 16:46 |
watchglass |
205.134.172.27:8333 : Alive: (0.145s) V=99999 (/therealbitcoin.org:0.9.99.99/) Jumpers=0x1 (TRB-Compat.) Blocks=710586 (Operator: asciilifeform) |
| 16:46 |
watchglass |
54.39.156.171:8333 : (ns562940.ip-54-39-156.net) Alive: (0.172s) V=99999 (/therealbitcoin.org:0.9.99.99/) Jumpers=0x1 (TRB-Compat.) Blocks=710586 |
| 16:46 |
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=710586 (Operator: whaack) |
| 16:46 |
watchglass |
208.94.240.42:8333 : Alive: (0.164s) V=99999 (/therealbitcoin.org:0.9.99.99/) Jumpers=0x1 (TRB-Compat.) Blocks=710586 |
| 16:46 |
watchglass |
143.202.160.10:8333 : Alive: (0.244s) V=70001 (/therealbitcoin.org:0.7.0.1/) Jumpers=0x1 (TRB-Compat.) Blocks=710586 |
| 16:46 |
watchglass |
54.38.94.63:8333 : (ns3140226.ip-54-38-94.eu) Alive: (0.325s) V=88888 (/therealbitcoin.org:0.8.88.88/) Jumpers=0x1 (TRB-Compat.) Blocks=710586 |
| 16:46 |
watchglass |
103.36.92.112:8333 : (terebe.ns01.net) Alive: (0.585s) V=99999 (/therealbitcoin.org:0.9.99.99/) Jumpers=0x1 (TRB-Compat.) Blocks=710586 |
| 16:48 |
watchglass |
192.151.158.26:8333 : Busy? (No answer in 100 sec.) |
| 16:52 |
asciilifeform |
bonechewer: http://www.loper-os.org/?p=3969#comment-20006 |
| 16:56 |
asciilifeform |
thimbronion et al ^ |
| 17:06 |
signpost |
yeah, I'd recommend that syncs of the entire history happen via a bulk mechanism, e.g. a lubytorrent |
| 17:07 |
* |
signpost can imagine a situation where say 20 friendlies all collaborate (without needing to coordinate) to send me the chat history |
| 17:08 |
signpost |
one beautiful aspect of onlinecodes is they allow the friendlies to just start spewing generated check-blocks without communicating about who will start where. |
| |
↖ |
| 17:08 |
signpost |
this results in a pretty damned efficient transfer too. |
| 17:16 |
signpost |
can easily imagine a protocol for this where the recipient still has strictly finite and known amounts of data to receive per interval, e.g. 1) plz send me up to C check blocks generated from message blocks between hash H1 and H2, 2) friendlies all reply with a proposed transfer of a fixed number of check blocks generated from blocks within H1->H2, 3) receiving station confirms |
| 17:16 |
signpost |
proposed transfers and receives each stream into a fixed-length buffer it allocated, 4) receiving station decodes check blocks to message blocks on disk 5) receiving station either is satisfied or requests another batch of check blocks from friends. |
| 17:16 |
* |
signpost has particulars to work out, but rough sketch. |
| |
~ 1 hours 35 minutes ~ |
| 18:52 |
signpost |
http://logs.nosuchlabs.com/log/asciilifeform/2021-11-14#1065635 << I'm probably going to bite the same bullet over here, feh. |
| 18:52 |
dulapbot |
Logged on 2021-11-14 11:48:09 asciilifeform: fwiw earlier this yr asciilifeform grudgingly went to 5.11.3 (in torture room strictly, on account of this) , built a-ok w/ gcc 4.9. |
| |
~ 3 hours 30 minutes ~ |
| 22:22 |
asciilifeform |
http://logs.nosuchlabs.com/log/asciilifeform/2021-11-20#1066924 << at this pt signpost is prolly better read re lubyisms than asciilifeform , but all the variations on the theme i know of require agreement on the exact item being 'torrented' (if you will) for this kind of cooperation |
| 22:22 |
dulapbot |
Logged on 2021-11-20 12:08:09 signpost: one beautiful aspect of onlinecodes is they allow the friendlies to just start spewing generated check-blocks without communicating about who will start where. |
| 22:23 |
asciilifeform |
i.e. bitwise agreement, 'we're all sharing wikilicks.tar.gz and hash of it is H'. rather than 'we each have a log history with possibly 10% missing, each in different spot' |
| |
↖ |
| 22:24 |
asciilifeform |
if signpost knows of a lubyistic algo for the latter, would be interesting to hear it tho |
| 22:25 |
asciilifeform |
the other observation is that when dealing w/ broadcasts, yer dealing with 'extended' wot, with potentially varying degrees of 'friendliness', and not always known apriori. |
| 22:26 |
asciilifeform |
lubyisms are unbeatable when you know the hash of the warezball you want to get, and perhaps even a subtree of chunk hashes |
| 22:26 |
asciilifeform |
i.e. for trb blox would be a++ |
| 22:27 |
asciilifeform |
for 'swiss cheese' afaik not so much |
| 22:28 |
asciilifeform |
bonechewer: http://www.loper-os.org/?p=3969#comment-20008 |