Show Idle (>14 d.) Chans
← 2023-07-17 | 2023-07-19 → ↓
jonsykkel[asciilifeform]: u gota run serpent_init on the 32byte key to expand it
jonsykkel[asciilifeform]: serpent_init(bufer_of_528_bytes,cipher_key,SERPENT_KEYSIZE)
jonsykkel[asciilifeform]: then use that for cipher funcs
awt_akris[asciilifeform]: jonsykkel: ty. updated. decrypted using both pure python and c serpent and got the same result.
asciilifeform: http://logs.bitdash.io/pest/2023-07-17#1028453 << strange; yer at entry does periodically update
bitbot[asciilifeform]: Logged on 2023-07-17 23:01:03 awt_akris[awt|signpost]: asciilifeform: I manually added you at the IP and port I have you at on my other station but I'm not seeing a response to PROD messages going to your station.
asciilifeform: i.e. packets are going
asciilifeform: last update ~9h ago
dulapbot: Logged on 2023-07-13 14:50:16 asciilifeform: not baked proper vpatch yet for this thing, but will
dulapbot: Logged on 2023-06-09 12:43:19 unpx[asciilifeform]: So I guess we are all in a UNIX-like system because it is the most hackable we can have right now without becomeing a system programmer
dulapbot: Logged on 2023-07-06 19:06:02 unpx[asciilifeform]: Or at least guide people so they can write they own tools to do all of that the way they want
unpx[asciilifeform]: 788][dreaming] a minimalistic self-maintained software stack
unpx[asciilifeform]: no vpatch for compiled docs*
unpx[asciilifeform]: [...] we are still dreaming a minimalistic self-maintained software stack.
dulapbot: Logged on 2023-03-30 16:44:45 unpx[asciilifeform]: PeterL, asciilifeform: indeed, but what then? I may have a comfy machine for working and then a machine for specific bank/gov stuff, but then what would you have in that work machine? wget, lynx port, Konqueror, Pale Moon? Or would you reduce documents to TXT and forget HTML rendering?
asciilifeform: unpx: 'if wishes were horses' then neither lynx, nor konkeror, etc. but rather sumthing entirely new and bolixlike, with buncha modular, reusable routines rather than standalone 'apps'
unpx[asciilifeform]: Indeed, the whole "IDE" should be aware
unpx[asciilifeform]: Moreover, I'm still looking for such a design solution that manages both documentation and code and tie the two together
dulapbot: Logged on 2023-05-18 16:37:31 unpx[asciilifeform]: But I cannot see tools that care about both, they are more about the phase one rather then the phase two.
signpost[asciilifeform]: manages in what sense?
unpx[asciilifeform]: I cannot find the discussion about connecting pdf documents to vpatches, signpost
asciilifeform: unpx: vpatches are intended to (borrowing the gpl folxs' terminology) concern 'the form of the document preferred for modification'
asciilifeform: so, not pdf, but e.g. its latex src, for instance
signpost[asciilifeform]: yeah, same goes for codegen like the automake cruft currently preserved on pentacle's dissection table.
unpx[asciilifeform]: Yeah, but I recall a discussion where a certain vpatch was mapped to a certain documentation version
signpost[asciilifeform]: generated srcs should in principle not be in there either.
signpost[asciilifeform]: derived items of w/e kind
unpx[asciilifeform]: Probably phf drew a graph
signpost[asciilifeform]: leaving aside for a moment that if you need codegen you're probably already in a bad place.
unpx[asciilifeform]: >markdown docs
unpx[asciilifeform]: something something dependency.png
dulapbot: Logged on 2023-03-25 21:46:41 jonsykkel[asciilifeform]: example http://zzz.st/up/olNWGD1z/example.png
unpx[asciilifeform]: Will ponder a bit with phf tools too
awt_akris[asciilifeform]: Alright now running with jonsykkel's serpent (calling it c_serpent). CPU usage looking good.
awt_akris[asciilifeform]: Also flushing the toilet is not resulting in poo in the freezer.
asciilifeform: awt_akris: a++
asciilifeform still puzzled wai direct peering not worx. given that some packets are getting through
awt_akris[asciilifeform]: asciilifeform: this is the prod I'm sending you that's not getting a reply: http://paste.deedbot.org/?id=nr9x
asciilifeform: awt_akris: indeed not appears in log here
asciilifeform: awt_akris: hmm wai same ip ( asciilifeform's) on both sides of the quoted line ?
awt_akris[asciilifeform]: I am behind a nat here, but everyone else is replying so maybe not my nat.
asciilifeform: did log notation change from blatta's ?
signpost[asciilifeform]: lol, think how quickly you can unpack the groceries when you line 'em up JUST SO
signpost[asciilifeform]: oh god, impaled the cat with a pineapple
asciilifeform: signpost: hm?
signpost[asciilifeform]: bad joke about reading into a struct
awt_akris[asciilifeform]: asciilifeform: first IP is the address the prod is being sent to. second IP is the last known address of the intended recipient.
asciilifeform: a! got it
awt_akris[asciilifeform]: signpost: not sure which struct you're referring to. Desperately want to get the joke.
signpost[asciilifeform]: slow on the draw
awt_akris[asciilifeform]: asciilifeform: double checked the key and seems right. On blatta, it is possible to accidentally add spaces to the key when entering it.
asciilifeform: key defo right (or wouldn't be seeing at updates here, neh)
awt_akris[asciilifeform]: What address do you have for me?
signpost[asciilifeform]: awt_akris: it's common to point a struct pointer directly at where you recv'd a packet to chunk into fields
signpost[asciilifeform]: making a joke about how this goes wrong with field misalignment
asciilifeform: awt_akris: 99.14.101.191:1024
signpost[asciilifeform]: it was funnier in my head
awt_akris[asciilifeform]: asciilifeform: yep that's correct.
awt_akris[asciilifeform]: signpost: speaking of impaling cats, should be a lot easier to integrate ocpy now that I've got a working example going with c_serpent.
signpost[asciilifeform]: turd's pretty slow still, but it's a starting point
signpost[asciilifeform]: c one's fast but unfinished
asciilifeform: will also work a++ in asciilifeform's (sadly stalled atm) cpp pestron, come to think of it
signpost[asciilifeform]: still might be worthwhile to try the thing out with ocpy
awt_akris[asciilifeform]: signpost: sorry I was referring to the c version. Can't remember what it's called.
awt_akris[asciilifeform]: oh lol ok makes sense.
signpost[asciilifeform] did some work on it yesterday evening, probably not too far off
unpx[asciilifeform] doesn't know if asciilifeform and signpost understood what I did mean here by ``manages both documentation and code'' http://logs.nosuchlabs.com/log/pest/2023-07-18#1028928
dulapbot: Logged on 2023-07-18 13:03:29 unpx[asciilifeform]: aye, it was jonsykkel
awt_akris[asciilifeform]: asciilifeform: which is better? Annoy operators whose clock has drifted back, or use the time the message was received at as the timestamp to order messages by when displaying them? Or something else?
unpx[asciilifeform]: http://logs.nosuchlabs.com/log/pest/2023-07-18#1028926 <<< w/o proper tools to render it, markdown is not worth `compiling' to html, since you then need a browser
dulapbot: Logged on 2023-07-18 12:55:57 unpx[asciilifeform]: >markdown docs
awt_akris[asciilifeform]: IIRC ntp is not a desirable dependency.
awt_akris[asciilifeform]: I'm finding frequent instances of out of sync clocks and it does disrupt log reading during a hot thread.
signpost[asciilifeform]: why not order by netchain with a recursive query? (leaving aside indexing or w/e to speed up, might not be needed)
signpost[asciilifeform]: imho the ordering I care about is the one the speaker intended, resolving ties in w/e sensible way.
awt_akris[asciilifeform]: signpost: the goal is ultimately to order by netchain - currently blatta's handling of netchain is unspeakably broken, so until we have a reliably contiguous netchain, gotta order by timestamp...
awt_akris[asciilifeform]: With what I have right now, I could attempt to use netchain as a heuristic when timestamp < netchain tip's timestamp. Even so, the spec disallows such messages - technically akris should be discarding them.
asciilifeform: http://logs.bitdash.io/pest/2023-07-18#1028527 << track the deltas (while warning operator) and estimate 'troo' time by weighted pull of peers with historically low drift.
bitbot[asciilifeform]: Logged on 2023-07-18 16:09:56 awt_akris[awt|signpost]: asciilifeform: which is better? Annoy operators whose clock has drifted back, or use the time the message was received at as the timestamp to order messages by when displaying them? Or something else?
asciilifeform: ( if they're all drifting by a ~constant, the br0ken 1 is.. you )
asciilifeform: the original conceit, however, was that pestrons only need to be 'city tower bell' accurate (i.e. +/- 15m) to work reliably.
asciilifeform: ( vs. e.g. ntpism )
asciilifeform: conceivably can sync with sundial.
asciilifeform: 'worx 100% with sundial time' was explicit goal of asciilifeform's orig design.
asciilifeform: sundial being the only apolitical clock avail. on planet3.
signpost[asciilifeform] has long wanted to do an optical clock which recalibrates using the night sky
awt_akris[asciilifeform]: http://logs.bitdash.io/pest/2023-07-18#1028539 << On this pestnet, this heuristic could turn out to be an "insanity check"
bitbot[asciilifeform]: Logged on 2023-07-18 17:50:28 asciilifeform[5]: ( if they're all drifting by a ~constant, the br0ken 1 is.. you )
awt_akris[asciilifeform]: asciilifeform's clock consistently matches my own, fwiw.
asciilifeform: iirc mine synced from router which syncs from isp which from hitler
awt_akris[asciilifeform]: Testing out using recieved_at - "worx" but would not work well during initial sync when received at could be years off from the packet timestamp.
awt_akris[asciilifeform]: Testing out using recieved_at - "worx" but would not work well during initial sync when received at could be years off from the packet timestamp.
awt_akris[asciilifeform]: Not a dupe ^ an exception was preventing the message from displaying and I sent it twice.
awt_akris[asciilifeform]: nm can just use originator timestamp for getdata responses.
← 2023-07-17 | 2023-07-19 → ↑
Random(pest) | Download hourly DB snapshot | Get Source Code