02:32 |
signpost |
punkman: https://pdos.csail.mit.edu/~petar/papers/maymounkov-bigdown.pdf << highly recommended reading |
| |
↖ |
02:33 |
signpost |
once you're talking about blasts of more than a single item, questions like "wat do when I lose something" come in, and imho the linked item points to a much better approach than reimplementing tcp shittily |
| |
↖ |
02:33 |
* |
signpost has a WIP item that may bolt nicely to thimbronion's before long, in py |
| |
↖ |
02:35 |
signpost |
one lovely consequence of the encoding stream is that, for items multiple peers have, multiple peers can start spraying blocks at you, and you'll reap the benefit of the parallelism without them coordinating with each other on what to send you. |
02:35 |
* |
signpost recs as many folks as are interested in this to read the paper, and then the more math-heavy one. |
02:35 |
* |
asciilifeform not fond of multipacket answers to a 1-packet question, for the simple reason where 'am i expecting this packet?' gotta be O(1) resolvable |
| |
↖ |
02:35 |
dulapbot |
Logged on 2021-10-01 14:12:28 asciilifeform: punkman: sadly asciilifeform not had time to write this section ! and doesn't know when will. intention was 1 hash per msg tho, to make easier calculation of the cpu cost of processing a valid packet. |
02:37 |
asciilifeform |
signpost: imho lubyism is a++ for pest-style known-peers net, as the need to separately authenticate the frags falls away (i.e. can generally trust that a direct peer is not sending garbage frag) |
02:37 |
asciilifeform |
for warez application -- perfect |
02:38 |
signpost |
exactly. I'm saying punkman does not need this for base-layer pest, and pointing to where it has an application. |
02:38 |
asciilifeform |
(for chat, not really needed, but simple to bolt on as a command code) |
02:38 |
asciilifeform |
aha |
| |
~ 2 hours 54 minutes ~ |
05:32 |
punkman |
http://logs.nosuchlabs.com/log/asciilifeform/2021-10-03#1060616 << if some packets are lost, we would simply send more getdata requests. |
05:32 |
dulapbot |
Logged on 2021-10-03 22:33:25 signpost: once you're talking about blasts of more than a single item, questions like "wat do when I lose something" come in, and imho the linked item points to a much better approach than reimplementing tcp shittily |
05:35 |
punkman |
http://logs.nosuchlabs.com/log/asciilifeform/2021-10-03#1060620 << if peer gets request to fill 5k message gap, could decide to only send 10 or 50, and requester will eventually send more getdata requests |
| |
↖ |
05:35 |
dulapbot |
Logged on 2021-10-03 22:35:27 asciilifeform: not fond of multipacket answers to a 1-packet question, for the simple reason where 'am i expecting this packet?' gotta be O(1) resolvable |
05:36 |
punkman |
it does add unwanted complexity, will concede the point |
| |
~ 2 hours 3 minutes ~ |
07:39 |
punkman |
in other complexities, what about compressing messages? would help avoid splitting of ~500 byte irc messages into 2 pest messages. Relevant: https://github.com/facebook/zstd#the-case-for-small-data-compression |
| |
↖ |
| |
~ 6 hours 19 minutes ~ |
13:59 |
signpost |
pest seems like a thing to implement as simply as possible, then see what problems one actually has |
| |
~ 38 minutes ~ |
14:37 |
asciilifeform |
^ |
14:39 |
asciilifeform |
http://logs.nosuchlabs.com/log/asciilifeform/2021-10-04#1060632 << imho this is an absolutely terrible idea. introduced 'over9000' gnarly moving parts, for dubious gain. (i dunthink there has ever existed a compressor w/out vulns. at the very least, the basic 'zip bomb' afflicts them all. and go and try to calculate, w/out burning cpu, how much it costs to unzip a compressed turd..) |
14:39 |
dulapbot |
Logged on 2021-10-04 03:39:49 punkman: in other complexities, what about compressing messages? would help avoid splitting of ~500 byte irc messages into 2 pest messages. Relevant: https://github.com/facebook/zstd#the-case-for-small-data-compression |
14:39 |
asciilifeform |
*introduces |
14:40 |
asciilifeform |
http://logs.nosuchlabs.com/log/asciilifeform/2021-10-04#1060629 << i'd really NOT like to re-create what imho is the single most dysfunctional aspect of trb, in pest... |
14:40 |
dulapbot |
Logged on 2021-10-04 01:35:59 punkman: http://logs.nosuchlabs.com/log/asciilifeform/2021-10-03#1060620 << if peer gets request to fill 5k message gap, could decide to only send 10 or 50, and requester will eventually send more getdata requests |
14:41 |
asciilifeform |
$ticker btc usd |
14:41 |
busybot |
Current BTC price in USD: $47682.26 |
14:41 |
asciilifeform |
!w poll |
14:41 |
watchglass |
Polling 17 nodes... |
14:41 |
watchglass |
185.85.38.54:8333 : Could not connect! |
14:41 |
watchglass |
84.16.46.130:8333 : Could not connect! |
14:41 |
watchglass |
185.163.46.29:8333 : Could not connect! |
14:41 |
watchglass |
54.39.156.171:8333 : (ns562940.ip-54-39-156.net) Alive: (0.112s) V=99999 (/therealbitcoin.org:0.9.99.99/) Jumpers=0x1 (TRB-Compat.) Blocks=703521 |
14:41 |
watchglass |
205.134.172.6:8333 : (172-6.core.ai.net) Alive: (0.141s) V=99999 (/therealbitcoin.org:0.9.99.99/) Jumpers=0x1 (TRB-Compat.) Return Addr=0.0.0.0:8333 Blocks=703521 |
14:41 |
watchglass |
205.134.172.26:8333 : Alive: (0.158s) V=99999 (/therealbitcoin.org:0.9.99.99/) Jumpers=0x1 (TRB-Compat.) Return Addr=0.0.0.0:8333 Blocks=703521 |
14:41 |
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=703521 |
14:41 |
watchglass |
208.94.240.42:8333 : Alive: (0.220s) V=99999 (/therealbitcoin.org:0.9.99.99/) Jumpers=0x1 (TRB-Compat.) Blocks=703521 |
14:42 |
watchglass |
213.109.238.156:8333 : Alive: (0.403s) V=99999 (/therealbitcoin.org:0.9.99.99/) Jumpers=0x1 (TRB-Compat.) Blocks=703521 |
14:42 |
watchglass |
143.202.160.10:8333 : Alive: (0.838s) V=70001 (/therealbitcoin.org:0.7.0.1/) Jumpers=0x1 (TRB-Compat.) Blocks=703521 |
14:42 |
watchglass |
205.134.172.27:8333 : Alive: (0.246s) V=99999 (/therealbitcoin.org:0.9.99.99/) Jumpers=0x1 (TRB-Compat.) Blocks=703521 (Operator: asciilifeform) |
14:42 |
watchglass |
205.134.172.28:8333 : Alive: (0.199s) V=99999 (/therealbitcoin.org:0.9.99.99/) Jumpers=0x1 (TRB-Compat.) Return Addr=0.0.0.0:8333 Blocks=703521 (Operator: whaack) |
14:42 |
watchglass |
103.36.92.112:8333 : (terebe.ns01.net) Alive: (0.562s) V=99999 (/therealbitcoin.org:0.9.99.99/) Jumpers=0x1 (TRB-Compat.) Blocks=703520 |
14:42 |
watchglass |
71.191.220.241:8333 : Violated BTC Protocol: Bad header length! (Operator: asciilifeform) |
14:42 |
watchglass |
54.38.94.63:8333 : Violated BTC Protocol: Bad header length! |
14:42 |
watchglass |
176.9.59.199:8333 : Violated BTC Protocol: Bad header length! (Operator: jurov) |
14:43 |
asciilifeform |
!w probe 71.191.220.241 8333 |
14:43 |
watchglass |
192.151.158.26:8333 : Busy? (No answer in 100 sec.) |
14:44 |
watchglass |
71.191.220.241:8333 : Violated BTC Protocol: Bad header length! |
14:44 |
asciilifeform |
!w probe 71.191.220.241 8333 |
14:45 |
watchglass |
71.191.220.241:8333 : (pool-71-191-220-241.washdc.fios.verizon.net) Alive: (0.918s) V=99999 (/therealbitcoin.org:0.9.99.99/) Jumpers=0x1 (TRB-Compat.) Blocks=703522 |
| |
~ 1 hours 52 minutes ~ |
16:37 |
thimbronion |
http://logs.nosuchlabs.com/log/asciilifeform/2021-10-03#1060597 << Not sure yet but possibly the issue is that alcuin is sending UDP packets from "ephemeral" ports. Still looking into how to configure the source address/port. |
16:37 |
dulapbot |
Logged on 2021-10-03 12:37:21 thimbronion: punkman: the issue I'm seeing now is the port I get from recvfrom doesn't match the port bound to on the remote host. I suspect it's some local port. |
| |
~ 2 hours 55 minutes ~ |
19:32 |
jonsykkel |
whats the reason for seprate signing and cipher keys? |
| |
~ 17 minutes ~ |
19:50 |
asciilifeform |
jonsykkel: why would you use the same key for both ?!! |
19:51 |
* |
asciilifeform didn't think this needed an explanation, but apparently it does... |
19:51 |
jonsykkel |
well im retarded |
19:51 |
jonsykkel |
this needs to be taken into account |
19:52 |
asciilifeform |
jonsykkel: if you give enemy outputs F1(P, K) and F2(P, K), where P is plaintext, K is a key, and F1/F2 are some functions, he can sometimes solve an equation and obtain P, or K, or both. |
19:54 |
jonsykkel |
ah i see |
19:54 |
asciilifeform |
by using same key and same plaintext in two different functions (in this case, hypothetically, hmac and serpent) you weaken both. |
19:54 |
asciilifeform |
is not trivial to demonstrate the concrete 'how', for given scheme; but easy to show that you've given the enemy info he has 0 business having |
19:55 |
asciilifeform |
(and would not have if you used K1 and K2, K1!=K2) |
19:55 |
jonsykkel |
makes sense |
19:55 |
asciilifeform |
aite |
19:55 |
jonsykkel |
ty |
| |
~ 1 hours 43 minutes ~ |
21:38 |
verisimilitude |
http://logs.nosuchlabs.com/log/asciilifeform/2021-09-29#1060025 I forgot to mention days ago, it's so nice to be able to natively understand the Latin fragments I'm coming across. |
21:38 |
dulapbot |
Logged on 2021-09-29 04:25:00 gregory5: dpb: was your church split off from another, or was it based on an ab-initio Scriptural reading (like Charles Taze Russell)? |
21:42 |
verisimilitude |
http://logs.nosuchlabs.com/log/asciilifeform/2021-10-01#1060407 We see how useful a factory is when it's missing small but necessary components, signpost. |
21:42 |
dulapbot |
Logged on 2021-10-01 12:39:52 signpost: jokes with his wife that he's just a jar of cum with legs; she's a whole human factory. |
21:43 |
verisimilitude |
I've a valid complaint about Pest now. |
21:43 |
verisimilitude |
I won't bother finding the old message. |
21:45 |
verisimilitude |
I want to design a Pest implementation which stores all messages in a log; how am I to store the hearsay information; it seems this information is only revealed in the hypothetical IRC gateway; there shouldn't be information generated which can't later be regenerated. |
| |
↖ |
21:47 |
verisimilitude |
If I only store red packets, even copies, I can't do this. |
| |
~ 23 minutes ~ |
22:10 |
asciilifeform |
verisimilitude: you simply store the messages, along with count of relayers. |
22:12 |
verisimilitude |
That was my first thought, and it rounded the stored message size to 512, but the identities are also important. |
22:13 |
asciilifeform |
verisimilitude: why do you want to store (outside of your personal irc console logs) info that doesn't need to be relayed to any pest peers ? |
22:13 |
asciilifeform |
if 'i want to store errything! which hits me' -- your irc client already does this. |
22:14 |
verisimilitude |
I want to have the entire conversation as a proper data structure which can be examined. |
22:14 |
verisimilitude |
I don't intend to use an IRC client for Pest, recall. |
22:15 |
asciilifeform |
verisimilitude: i've no objections, but also don't see why this has to be in pest spec |
22:15 |
asciilifeform |
(which is about basics req'd for interoperability b/w stations, arguably) |
22:15 |
verisimilitude |
I'm voicing a concern before it becomes irreperable. |
22:15 |
asciilifeform |
verisimilitude: why would it become irreparable ? |
22:15 |
verisimilitude |
I'm voicing a concern before it becomes too difficult to change in the face of later changes. |
22:16 |
asciilifeform |
can always go 'this thing being thrown away? let's save it' |
22:16 |
verisimilitude |
Sure, but that's not as clean as it could, and perhaps should, be. |
22:17 |
verisimilitude |
I'm also, of course, trying to help with Pest, by looking for problems. |
22:17 |
* |
asciilifeform appreciates |
22:18 |
asciilifeform |
verisimilitude: note, i dun disagree re 'save the relayers' etc. -- simply would prefer to avoid bloating the spec (and i fear is already excessive as it is) |
22:18 |
verisimilitude |
That compression idea earlier was laughable. |
22:18 |
asciilifeform |
seems that errybody has some pet pheature he'd like. but remember that it's a spec, it does not magically make the proggy appear.. |
22:18 |
verisimilitude |
``Look at what Facebook uses!'' |
22:19 |
asciilifeform |
nfi if was joke or wat. |
22:19 |
verisimilitude |
On that note, this Facebook DNS shitshow is amusing. |
22:19 |
asciilifeform |
imho rather obvious that you DON'T want lzw etc in this thing, lol |
| |
↖ |
22:20 |
asciilifeform |
compression aint simply a 'no' but a 'lolno' per asciilifeform . |
22:20 |
shinohai |
Will "lolno" be in the spec? |
22:20 |
* |
shinohai can hope ..... |
22:21 |
verisimilitude |
Well, I wouldn't call it a ``pet feature''; it's a valid concern, to be careful about what is being thrown away. |