asciilifeform: 'Calculate the priority of the new IP to see if we should drop it immediately (normal) or kick one of the other peers out to make room for it.' -- are you a plebe, or a loyal servant of the crown
asciilifeform: 'CIPGroupData... A group of logically related IP addresses. Useful for banning or deprioritising sources of abusive traffic/DoS attacks.' << that would be, presumably, us.
asciilifeform: translated for humans, means 'if you wanna talk, prove you're a leaf node running hearnia. and don't pretend to be infrastructural node, we know who they are already and i don't recall selling you a license'
asciilifeform: 'Future... ...Design a protocol to let user wallets gain priority by proving ownership of coin age, as they tend to have short lived connections and roam around different IPs, but we still want to serve them ahead of long term idling connections.' << lulzy. hearn would have all nodes run hotwallet to 'prove coin age'
asciilifeform: hanbot: you will, yes. but it is not a build, presently. only a set of patches re-created with vdiff and signed - currently by myself only.
asciilifeform: anyone who doesn't care for the 'entomology' here - can safely skip whole shebang.
asciilifeform: (thing is full of screen caps of hearn & gavin and their code, doing their thing.)
asciilifeform: mircea_popescu: and a more-or-less accurate (for a non-#b-a denizen) outline of events re: same.
asciilifeform: mircea_popescu: it has snapshots of choice hearnias, with commentary
asciilifeform: hanbot: it will, possibly, supercede these if and when ben_vulpes, mod6, et al, agree that my current approach is correct.
asciilifeform: hanbot: in its present condition, it supercedes nothing at all, except for the laborious 'here's where to get all the patches and how they depend on each other' docs
asciilifeform: orchestra consists of precisely the same patches which made it into rel1 and those which are being considered by mod6 and ben_vulpes for inclusion in rel2
asciilifeform: most folks cram it into the payload, yes.
asciilifeform: (offtopic: perhaps the single most asinine aspect of gpg signature as-we-have-it is the lack of a clearly delineated space to write ~why~ you are signing something.)
asciilifeform: when tested against what is produced in this recipe, now or 100 years from now.
asciilifeform: if everyone's output is the same, the sigs will be valid!
asciilifeform: otherwise, friends, go and verify, and sign the output!
asciilifeform: if anyone does not understand why i did this, or, alternatively, believes that this ought to have been done in some other way - please speak.