asciilifeform: part of the http://btcbase.org/log/2017-12-21#1756115 process is that they're phasing in 'force people to run heartb^H^H^H^H^H^sasl to merely connect' item. ☝︎

asciilifeform: but nao we're talking about a day or three of work.

asciilifeform: znc proxy would cure, i suspect

asciilifeform: what was it, 6667

asciilifeform: trinque's default

asciilifeform: which presently leaves asciilifeform with no place to put the bot ( i won't keep it on zoolag, uncloaked irc-to-fleanode results in massive shitfloods routinely )

asciilifeform: evidently world's largest, fastest spam isp, whod'vethunkit!11, is banned even on fleanode. ☟︎

asciilifeform: but quite certainly -- from aws.

asciilifeform: maybe also from zimbabwe , who the fuck knows

asciilifeform: nao how would i know if ~only~ from there

asciilifeform: and it happens regardless of which *.fleanode box the lottotron gives you

asciilifeform: result is, e.g., NOTICE: hitchcock.freenode.net pehbot "*** Notice -- You need to identify via SASL to use this server"

asciilifeform: in other noose, asciilifeform discovered that it is impossible to use trinque's bot on fleanode if connecting from a shitazon session:

asciilifeform: ben_vulpes: some of the bread eaten in blockade-era leningrad , was, i suspect, a serious step ahead of 'starbucks'.

asciilifeform: http://btcbase.org/log/2017-12-24#1758167 << ro was like this. to the point that even nao neither asciilifeform nor his pet can bring themselves to eat at american 'coffee' shops any moar. at all. ☝︎☟︎

asciilifeform: ( it in fact is : http://btc.yt/lxr/satoshi/source/src/db.cpp?%21v=makefiles#0840 . but really oughta link directly imho )

asciilifeform: rather than 'who the hell knows if this is even still around' item

asciilifeform: ben_vulpes: plox to link to mod6's latest spear-tip ?

asciilifeform bbl,meat

asciilifeform: btw , ftr , sha512(ch4_official_solution.txt) = 6878eec821232031b43b28f955971388d33262531c4205eff6be5e8e0244a2e092556623b9daff54058b781dc9eafc91bf8099c29ef1fd21602eccc18e63c8f1 .

asciilifeform: !~later tell phf plox post your puzzle-hash as comment in ch4 ☟︎

asciilifeform: single-threaded, locking gossip, is a sad thing tho.

asciilifeform: elementarily.

asciilifeform: and not 10min

asciilifeform: q is why 'eventually' is a week, 2 weeks

asciilifeform: ( if i know of a nextblock, and i'm peering with mircea_popescu , and he doesn't, or vice-versa -- the boxes oughta share )

asciilifeform: it ought not to be possible under the game rules

asciilifeform: *blockheight

asciilifeform: incidentally, this is a pretty sad situation, if even 1 of us has a node at block B, but everybody else somehow floundering at B-k, for some positive k

asciilifeform: yes expensive.

asciilifeform: vs what, paper cups ?

asciilifeform: notably i have no way of knowing.

asciilifeform: aah

asciilifeform: where's the tip of the spear ?

asciilifeform: funnily enuff, the absolute all-time champ at never-lagging in asciilifeform's house of horrors is... an ancient (circa 2013..?) prb !! e.g. currently at 500849

asciilifeform: 'os' without redirectable output , belongs in the oven.

asciilifeform: the 'find and open debug.log somewhere' is a winblowzism.

asciilifeform: yea i can't think of any reason whynot.

asciilifeform: it must remain useful when printing to stdio

asciilifeform: i can't speak for others, but asciilifeform often ( almost always, in fact ) runs trb during tests, in pure userland, making use of 0 systemwide loggings )

asciilifeform: trinque: i suspect that we already had this thread

asciilifeform: and from where only rubbish comes.

asciilifeform: i'd like to get a sense for where blocks come from.

asciilifeform: what i'd like to see is 'was it from a trb?'

asciilifeform: that already printed ( the latter , in classical trb, mutilated )

asciilifeform: ( also in the log )

asciilifeform: right up there with 'from-where-i-got-ACCEPTED-block'

asciilifeform: ^ useful

asciilifeform: it'll be, what, 4-5 lines.

asciilifeform: ben_vulpes: consider making a patch ?

asciilifeform: i'ma thinking already about next level of possible 'aggression' : namely to pushgetblocks() at ALL running peers, if >20min pass, say, without a new block received

asciilifeform: it isn't even impossible that there's only been 1 block in past 2hrs, say

asciilifeform: ben_vulpes: aa see i was making a http://btcbase.org/log/2017-12-24#1757976 . ☝︎

asciilifeform: anyway , worx, now all i need is to think of how to properly cut the output so as not to straddle message breaks...

asciilifeform: only then, had to unsheath eyes.

asciilifeform: no eyes involved, i pressed and used trinque's original usage.txt and got barf

asciilifeform rewound to trinque's original, which in fact worx.

asciilifeform: you changed 'channel' slot in ircbot class to 'channels', but never bothered to change the corresponding line in make-ircbot !! ben_vulpes ) ☟︎

asciilifeform: ( how the fuck did it ever work , ben_vulpes ?? )

asciilifeform: oooh i think i see why. ben_vulpes's 'multiple-channels' patch mutilated it

asciilifeform: !~later tell trinque http://wotpaste.cascadianhacker.com/pastes/nxnWA/?raw=true << or for that matter anybody else using trinque-bot -- any idea what gives ? i followed the example in the readme...

asciilifeform: 'blockchain'ism is simply a very expensive means of approximating a solution to this problem.

asciilifeform: ( if you ~could~ get a 'fixed star' , all sorts of marvels not found in nature become possible, e.g. http://btcbase.org/log/2017-03-02#1621087 ) ☝︎

asciilifeform: there is not, nor could there be, a fixed-star for existence proofs. even classical blockchain has the obvious limitations ( discussed numerously, see l0gz )

asciilifeform: how could it prove to anyone else.

asciilifeform: it proves only to him, naturally

asciilifeform: sorta like what archaeologists do already.

asciilifeform: 1 way, would be by going to his own cellar and fetching optical disk where he has ~his~ mpi

asciilifeform: nah, there's a time parameter

asciilifeform: consider, what do you do in your wot housekeeping ~today~ to people who habitually sign P ~and~ ~P

asciilifeform: or do i miss something

asciilifeform: what does signature even mean, if folx habitually sign both P and ~P

asciilifeform: ok..

asciilifeform: process of elimination?

asciilifeform: dun tell me we gotta have the ring signatures thread again

asciilifeform: ok..

asciilifeform: maybe i'm thick, but i dun see the algo 'between the lines' here

asciilifeform: if mircea_popescu has thought of a meaning for it that doesn't 'a participating entity can recognize work done by itself as opposed to work done by others' -- i'm all ears

asciilifeform: which is retarded.

asciilifeform: could, but then you get http://btcbase.org/log/2017-12-02#1745524 . ☝︎

asciilifeform: and yes.

asciilifeform: ( asciilifeform's answer is 'first you pillage , ~then~ you burn, fughetabout it for the time being, have an algo for the basic mechanics that makes sense, first ! )

asciilifeform: well e.g. ben_vulpes asked, http://btcbase.org/log/2017-12-19#1754135 ☝︎

asciilifeform: ( for some reason everybody always asks 'how'll you pass out the coins', but this is orthogonal problem! )

asciilifeform: this is exactly the picture asciilifeform drew last yr, aha.

asciilifeform: aaa

asciilifeform: mircea_popescu: plox to elaborate re 'as large as will be'

asciilifeform: indeed

asciilifeform: it ain't a substitute for the cut-up, no.

asciilifeform: as in , stand up new node in 1wk, instead of 3-4 months.

asciilifeform: not quite cosmetic, this. potentially massive speedup .

asciilifeform: because there's a possibility of speeding sync 100-200x... ( the obvious way. if block sha512's, or keccak's, etc. to a checksum-cum-heighposition that is signed by node owner's l1 -- then ACCEPT )

asciilifeform: hey mircea_popescu , was http://btcbase.org/log/2017-03-07#1623064 q ever resolved ? ☝︎

asciilifeform: ( ... at least until operation 'X' , i.e. mod-exp, is defined ! )

asciilifeform: ( i recommend bolting the width in place to 256 , to keep lines short )

asciilifeform: and i'll add that if somebody other than asciilifeform feels like doing this operation, i will take off my hat

asciilifeform: now only remains to plug it in

asciilifeform: nothing, took me a minute or so to recall that indeed it is posted

asciilifeform: !~later tell trinque what do you recommend for a talking-in-chan bot-tron ? i'd like to hook up 'ffacalc'... ☟︎

asciilifeform: ... it is equally conceivable that the thing is a pure win, and dun need to become a knob. we'll see.