Show Idle (>14 d.) Chans


← 2023-02-18 | 2023-02-20 →
08:52 awt http://logs.bitdash.io/pest/2023-02-18#1023633 << please disgregard - this patch is suffering about 40% brain damage
08:52 bitbot Logged on 2023-02-18 11:21:46 awt[jonsykkel|deedbot|signpost]: cgra et al.: http://paste.deedbot.org/?id=UXKZ << patch to send ac only on launch/new key/address change for review
~ 50 minutes ~
09:42 mod6 hai
09:42 awt Lol was just going to comment - restarted and all the sudden getting a flood of getdatas from mod6
09:42 mod6 ok, sync'd. helo?
09:42 mod6 Updated to v9970, got the playback.
09:47 awt phf, asciilifeform, cgra: my station is currently on Blatta 9969. AC from my station should be very rare going forward.
09:48 awt Intersting "pheature" of this patch is that you can manually trigger an ac broadcast.
09:49 awt Would be great if someone with a flaky IP could test it.
~ 1 hours 1 minutes ~
10:50 cgra http://logs.bitdash.io/pest/2023-02-19#1023773 << somehow this isn't netchained to mod6's, but to prev awt's
10:50 bitbot Logged on 2023-02-19 09:42:31 awt: Lol was just going to comment - restarted and all the sudden getting a flood of getdatas from mod6
10:50 bitbot Logged on 2023-02-19 09:42:25 mod6[5]: hai
10:50 bitbot Logged on 2023-02-19 08:52:15 awt: http://logs.bitdash.io/pest/2023-02-18#1023633 << please disgregard - this patch is suffering about 40% brain damage
10:53 cgra none of awt's recent messages showing up in bitdash log are netchained to any of mod6's. perhaps a useful case for study. noticed because can't see any of mod6's messages yet. came online only recently
11:01 awt cgra: also interesting that this message was not displayed to my irc client: http://logs.bitdash.io/pest/2023-02-19#1023772
11:01 bitbot Logged on 2023-02-19 09:42:25 mod6[5]: hai
11:01 awt Possibly received before my irc client connected to my blatta station.
11:02 awt Incidentally my station is still fielding getdata requests from mod6.
~ 23 minutes ~
11:26 billymg !!ticker btc usd
11:26 deedbot $25,070
11:27 awt nice
11:27 * signpost curious whether BTC will crash with the stock market as recession drags on.
11:27 signpost would be nice to see some stonk money flee *into* BTC.
11:28 signpost also hilarious that SEC chairman said recently, to quote, "not your keys, not your crypto"
11:28 awt Very weird recession, anyway. Mostly tech/finance. Of course there isn't really a working class anymore which could lose any jobs.
11:29 signpost right
11:29 signpost and tech was way overbought on labor.
11:44 asciilifeform signpost: overbought on pumping dough through sv slaves to california landlords, at any rate
11:47 asciilifeform mod6: are you running an ancient blatta? try recent one
11:52 asciilifeform http://logs.bitdash.io/pest/2023-02-19#1023792 << sadly when 'flees', does so typically into papercoin, with ~0 effect on exchrate
11:52 bitbot Logged on 2023-02-19 11:27:51 signpost: would be nice to see some stonk money flee *into* BTC.
~ 40 minutes ~
12:32 phf mod6's packets didn't retranslate to me either
12:36 phf asciilifeform, found some lulz for you
12:36 phf was looking for lisp tcl stuff and found a project by a ru guy https://тхаб.рф/wiki/Яр_(язык_программирования)
12:38 phf and from there https://творецкий-дом.рф/
12:39 phf e.g. http://plana.mybb.ru/viewforum.php?id=60 Проект "Русскоязычный ассемблер"
12:40 phf ph.d. level entomology
12:41 phf `Среда программирования на "русском" Си' of course everything's on windows, full lul gems
12:42 phf 􏿽«Возможность писать код на кириллице с минимальным переключением между раскладками. К сожалению эту проблему победить полностью не получится, так как ч
12:42 phf 􏿽асть символов есть только на английской раскладке.»
12:42 phf «Нужна ли руссификация чисел? В Си при записи чисел используются также и буквы латинского алфавита.»
12:49 asciilifeform phf: lulzy, '90s nostalgic flavour.
12:49 * asciilifeform recalls ancient b00kz with cyrillicised pascal examples
12:52 asciilifeform http://logs.bitdash.io/pest/2023-02-19#1023808 << sumbody get this fella an ancien regime keyboard with r/l key !111
12:52 bitbot Logged on 2023-02-19 12:42:01 phf[awt|deedbot]: 􏿽«Возможность писать код на кириллице с минимальным переключением между раскладками. К сожалению эту проблему победить полностью не получится, так как ч
12:54 * asciilifeform has a yellowing '80s b00k re forth, by one of these 'delatinizers', lulzy
12:58 * asciilifeform wonders whether ru medicinal prescriptions are still written in bastardized latin. last knew -- they were
~ 1 hours 46 minutes ~
14:44 cgra http://logs.bitdash.io/pest/2023-01-17#1020639 << asciilifeform, to go back to this, there's one angle to consider: if command was hashed, it would eliminate a problem class of command ambiguity. if hashed, fiddling with command would require sending an entirely different message, which is then handled as a cross-ref malfo
14:44 bitbot Logged on 2023-01-17 06:29:52 cgra[jonsykkel]: ...or more like, a peer can send us anything anyway, cmd hashing won't help
14:44 cgra rm, broadcast chain pointing to direct, or vice versa. case of malform required to handle anyway. OTOH, currently is dedicated handling needed for case when different peers send different command for same message
14:49 asciilifeform cgra: can you think of a hypothetical 'demented peer mutates command' that wouldn't already result in insta-discard ?
14:50 asciilifeform i suppose could switch a broadcast to direct, and the peer to whom you send this will see mysteriously-unfindable antecedents
14:51 asciilifeform this'll only piss off yer 1 peer to whom you do this
14:51 asciilifeform ( and it'll only even get processed if he hasn't seen the net broadcast with that hash yet, lol )
14:52 asciilifeform in general, a broadcast msg with 'fiddled' command will only even be noticed by those who not received the original yet.
14:54 cgra handling algo = if in doubt, assume command which suits chain values best?
14:54 asciilifeform (if already received original -- its hash will be in the filter)
14:55 asciilifeform cgra: under what circumstances would 'in doubt' ?
14:56 asciilifeform if yer peer is sending you directs which contain broadcast antecedents, you'll be 'seeing red' and can ask him 'wtf, buggy client? plz fix'
14:57 asciilifeform ditto if peer is regularly emitting broadcasts with unfindable antecedents
14:58 asciilifeform both possible directions of this misbehaviour will result in folx 'seeing red' and can ask 'wtf', if not received satisfactory answr -- unpeer.
14:58 asciilifeform in neither case does it break anyffin, or allow a net inhabitant to gum up traffic, afaik
15:01 asciilifeform the 1 headache asciilifeform can presently think of , is that a joker could take a broadcast, mutate cmd to direct, and 'poison' peers who haven't received the original yet. so possibly oughta store cmd in the filter next to hash, and a match req's both.
15:03 asciilifeform aand you'd only need to look at it when processing a direct.
15:04 asciilifeform and can safely unpeer anybody found doing it.
15:05 asciilifeform ( ftr , pest philosophy is that peers could misbehave in arbitrary ways, but the only necessary thing is that it must be made obvious to station operator ~which peer~ is doing so )
15:07 asciilifeform e.g. nuffin prevents a peer from spamming a GB of liquishit to his net. but it'll happen precisely once, and then he finds himself w/out any peers )
~ 24 minutes ~
15:32 * cgra 's brain on a (permanent?) slow gear, i gotta give it some time, asciilifeform
~ 29 minutes ~
16:01 asciilifeform noprob
~ 2 hours 31 minutes ~
18:32 awt 9969 sig EXPERIMENTAL not-to-spec AC spam reduction patch
← 2023-02-18 | 2023-02-20 →