00:13 |
vex |
asciilifeform, it'll all be over soon. maintaining control over the design process is a good thing to do |
00:14 |
vex |
I cvoulda told you you needed more wirespace for free. |
00:15 |
vex |
nooone ever listens to me tho. I'm wrong half of the time by design |
| |
~ 1 hours 2 minutes ~ |
01:18 |
vex |
https://www.youtube.com/watch?v=mrZRURcb1cM |
01:20 |
vex |
hanbot is still lost |
01:21 |
vex |
someone go give her a hug |
01:24 |
vex |
noone in costa rica is daddy enough |
01:32 |
vex |
youtube.com/watch?v=mrZRURcb1cM |
| |
~ 3 hours 58 minutes ~ |
05:30 |
gregorynyssa |
asciilifeform: what programming-language features are necessary to handle large codebases? how does Ada address this problem? |
| |
↖ ↖ |
05:31 |
gregorynyssa |
I remember reading Robert Harper's articles back in college about how Haskell's type-classes are not good for modularity. |
05:34 |
gregorynyssa |
are CLOS and Metaobject Protocol still worth learning in this day and age? |
| |
~ 37 minutes ~ |
06:12 |
adlai|text |
gregorynyssa: why would they not be!? |
| |
~ 3 hours 44 minutes ~ |
09:56 |
asciilifeform |
gregorynyssa: clos -- yes, mop -- strictly if you find it interesting ( asciilifeform admits, never used the latter in anger, as it didn't quite work 100% on sbcl when last tried ) |
09:59 |
asciilifeform |
http://logs.nosuchlabs.com/log/asciilifeform/2022-07-25#1112212 << proper package support, for one thing. ( and e.g. ada's 'generic' package thing is useful, see example. ) but see also oblig. naggum : what do you have that threatens to 'be large code base' ? (maybe wait until the problem actually |
| |
↖ |
09:59 |
asciilifeform |
happens to you?) |
09:59 |
dulapbot |
Logged on 2022-07-25 05:30:40 gregorynyssa: asciilifeform: what programming-language features are necessary to handle large codebases? how does Ada address this problem? |
10:12 |
gregorynyssa |
asciilifeform: the problem has already happened to me. |
10:17 |
gregorynyssa |
thanks for explaining though. |
| |
~ 32 minutes ~ |
10:50 |
asciilifeform |
gregorynyssa: what, from your pov, is 'large coad' ? |
| |
~ 1 hours 36 minutes ~ |
12:26 |
gregorynyssa |
Emacs, for one. |
12:37 |
asciilifeform |
emacs is imho as 'great' an example as e.g. mswin |
| |
~ 8 hours 49 minutes ~ |
21:26 |
jonsykkel |
am i correct in my understanding that ading infrastructure for piping bigass multiGB files over pest while retaining replay protection is planned? |
21:27 |
jonsykkel |
if so, how will this work, given that dedup bufer must fit in memory |
| |
~ 47 minutes ~ |
22:14 |
asciilifeform |
jonsykkel: there's no particular reason to dedupe warez fragments by looking in the db (or ever placing'em there to start with) |
| |
↖ |
22:16 |
asciilifeform |
jonsykkel: in luby-style scheme, btw, there's not really such a thing as a dupe, erry frag is of the form x1^x2^...^xn where x_i are chunks of the payload; erry x_i recv'd gives you some bits of info until you converge on the payload in its entirety |
22:17 |
asciilifeform |
and given that you aint rebroadcasting'em, there's no particular reason to try to filter, other than to reject stales (which may be replays thrown at your station by dr.evil) |
22:18 |
jonsykkel |
will it not then be possible to interfere with a transfer by replaying old fragments from a different warez? unless "currently transfering warez" hash is included in every packet or somthign |
22:18 |
asciilifeform |
jonsykkel: they still have timestamp (and still signed/ciphered using $peer's key like erry other msg) |
22:19 |
jonsykkel |
asciilifeform: right, but in the case where passes stale check cuz not old enuf |
22:19 |
asciilifeform |
simply won't be chained ( chaining of any kind makes 0 sense for luby frags ) |
22:20 |
asciilifeform |
jonsykkel: signpost did not yet post his scheme, but asciilifeform assumed that transfer would begin with e.g. a series of (chained) msgs giving hashes of, say, 1MB slices. then transfer 1 at a time |
| |
↖ |
22:21 |
asciilifeform |
after all slices accounted for, transfer is considered complete |
22:22 |
asciilifeform |
each luby msg would include hash of the slice it is a frag of. thereby dr.evil piping in chunks of previous transfers would do 0 |
| |
↖ |
22:22 |
jonsykkel |
alright, makes sense |
22:23 |
asciilifeform |
the ideal values for the constants will need to be determined empirically |
22:23 |
asciilifeform |
but in all cases replays of e.g. 20min old frags would do 0 other than waste bw |
22:24 |
asciilifeform |
(dr.evil can only replay authentic chunks that have been previously sent) |
22:26 |
jonsykkel |
indeed |