phf: i thought at mgu they just self-embalm, как завещал тов ленин

phf: i just assume that knuth stays in millenarian maths, periodically comming out to talk about generative Organ music

phf: in any case that's, so far, the best option i found for keeping the evils of c at a slight distance. at least interested parties can read and inspect the code, without skipping tricky parts

phf: it doesn't necessarily has to be particularly intrusive, i've looked at some of his "hacks", and they are very lightly annotated, but the partitioning still makes more sense that the direct flow of a c file

phf: i like that the end result can be wholly signed and produces a spiffy dvi for printing

phf: i.e. system calls only?

phf: not the best examples, i agree :>

phf: it's a tried and true strategy, original javascript has been done that way. i recently learned that that's the way dot-net garbage collector was written

phf: i'm pretty bad a dijkstra programming, i need to see the system behave to reason clearly about it, and c is not it. besides the translation is the tirvial part

phf: as far as lisp, yeah, not practical for deployment, but i started getting bogged down in trivial serialization questions, before i understand clearly how the whole system is supposed to work. once i get the spec as is up, i want to start working through those comments to modify it into a udp lower level system. in any case lisp is better option for gossip prototype, because the spec is so open ended

phf: asciilifeform: gpgme doesn't exactly "calls out", it talks to gpg via a text protocol, but i agree with your overall point. gossip has a fixed set of crypto operations, that can be abstracted, until you finish your crypto state machine gizmo.

phf: support of gpgme. the bindings come standard with gpgme release, but what's there was not updated since 2008. officially artifex is still working on that, but i take it nobody's heard from him in a while?

phf: i have some code for gossipd, i'm going to by the spec that's published on trilema, rather then follow up conversation about udp and first packet validation. i wrote enough in c to be able to prime gpg machinery and send packets over the wire (which basically coveres things that i wasn't sure how to do before i started), then i switched to common lisp to get a prototype up. what came out of that so far is updated bindings for lisp

phf: which brings me to the point that i have folders for all but "make new hardware" item in that list of b-a scope in various states of disarray, and it would be great if there was some prioritization, like it was the case with eulora "oh we need this done, you do it". ☟︎

phf: mircea_popescu: sorry about not picking up mushrooms, right after i finished the port, i did a move to DC area, and then, after few days, left for a trade show, which i just came back from. i started working on a text only client for eulora, but i didn't get far enough to claim my items with it.