| 02:01 |
cgra |
http://logs.bitdash.io/pest/2023-01-16#1020615 << np and ty |
| 02:01 |
bitbot |
Logged on 2023-01-16 19:20:38 phf[deedbot|awt]: http://logs.bitdash.io/pest/2023-01-16#1020613 << something came up, so i had to run away, apologies; but i'd like to address this thread extensively, so i'll have to come back to it tomorrow |
| 02:06 |
cgra |
http://logs.bitdash.io/pest/2023-01-16#1020619 << makes sense (to a limit, my deeper fpga/electronics understanding on an n-year todo list) |
| 02:06 |
bitbot |
Logged on 2023-01-16 19:56:31 asciilifeform[4]: ... where a field that is or isn't used is simply set of 'wires', whereas if you allow a 'thing to be in different places' you gotta mux |
| 02:10 |
cgra |
http://logs.bitdash.io/pest/2023-01-16#1020626 << ah ok, i prolly will keep misunderstanding things similarly, until complete spec digestion... |
| 02:10 |
bitbot |
Logged on 2023-01-16 20:09:46 asciilifeform[5]: version in particular not belongs in msg hash any more than bounce does. ( is intented to be version of the pestron sending the msg in all cases. rather than descriptive of the particular msg per se ) |
| |
~ 18 minutes ~ |
| 02:29 |
cgra |
http://logs.bitdash.io/pest/2023-01-16#1020622 << i meant in hearsay context. a command in messages from my l2+ may have changed in hands of my l1. ... actually, may not be any different from hearsay being completely suspect anyway, and wouldn't matter if command hashed or not |
| 02:29 |
bitbot |
Logged on 2023-01-16 20:06:37 asciilifeform[jonsykkel|awt|deedbot]: http://logs.bitdash.io/pest/2023-01-16#1020613 << recall that cmd and version are covered by the seal and thereby just as authenticable to $peer as the rest of packet |
| |
~ 4 hours ~ |
| 06:29 |
cgra |
...or more like, a peer can send us anything anyway, cmd hashing won't help |
| |
↖ |
| |
~ 4 hours 42 minutes ~ |
| 11:12 |
asciilifeform |
cgra: entirely correct |
| |
~ 1 hours 18 minutes ~ |
| 12:31 |
* |
asciilifeform mentioned this before, but a key principle of pestronics as he sees it is that a peer ~can~ send arbitrary nonsense, but 1) this oughta minimally affect station operation with respect to other peers 2) it must always be possible to easily determine ~which~ peer is misbehaving (following which, ask him wtf, and if n |
| 12:31 |
asciilifeform |
... and if not helps -- unpeer) |
| 12:33 |
asciilifeform |
this aint strictly about protocol-level misbehaviour, either, but extends to 'bob problem'(tm) & similar issues with hearsay |
| 12:36 |
asciilifeform |
e.g. if asciilifeform peers with bob who peers with charlie who connected rng to his terminal and floods the net, it aint unreasonable for asciilifeform's peers to ask him to have stern talking-to with bob, and if not helps, unpeer |
| 12:37 |
asciilifeform |
( and in the meantime 'we're setting PCUT of 0 on you until you get the flooder outta yer l2' ) |
| |
~ 7 hours 2 minutes ~ |
| 19:40 |
phf |
signpost, did you ever release your online codes python version? |
| |
↖ |