asciilifeform: don't be the fisherman who, say, 'i washed my hands after shitting and that day caught no fish, i think i'ma not ever again wash hands' etc.
asciilifeform: i get it, in the 'organic' system that is a live p2p net, proper controlled experiments are quite impossible. this however does NOT mean that one oughta freely give in to urge to climb back up the tree, becoming a monkey again, and think in voodoo criteria. even if the circumstances heavily encourage this , by failing to reward rational thought ( see mircea_popescu's thread with the italian fishermen !! , http://btcbase.org/log/2017-
asciilifeform: so that questions like 'did it even have net access for that week', to 'has it ASKED anyone for the next block, or just sat there with mouth open? ' and 'did anyone ANSWER, when asked, or just shat forth mempool crapola and bastards 50 blox ahead' can be answered.
asciilifeform: if, alternatively, it meant 'my block height hasn't moved for a week', again should be specific, SAY that, and post yer log
asciilifeform: ... and also say what happened when you try and plug yer node into this or that 'un-behind' one.
asciilifeform: if what is meant is 'i looked on shitchain.info and saw a higher number than from my getinfo' should SAY that.
asciilifeform: ben_vulpes et al : i think it is worth elaborating what it means when saying 'my node is behind N blox'. what it means, if spoken properly, is that you know of some node, somewhere, that appears to have moarblox than yours. focus should be on 'did my node ask it for nextblock? what, if anything, did it answer? why ?' rather than the quite uselessly unspecific 'mah nodez are behind!111'☟︎
asciilifeform: as for nodes at the 'tip', the path of chinesium through layers of prb is a lottery, and i suspect that attempting to measure the effect of a trb patch on said behaviour is doomed to astrologize over noise
asciilifeform: the old behaviour was indefensibly insane, wtf, why is boot time 'special', for fuck's sake.
asciilifeform: if it dun have a trb genesis, proving to proverbial martian that it really does have classical 0.5.3 pedigree, goes from trivial to monumentallypainful
asciilifeform: but this is reaching into the fantastic.
asciilifeform: or, on other end of the possible, a vtron that somehow understands that a call of foo necessarily depends on the patch that birthed foo... and requires disambiguation only if >1 foo exists in the tree☟︎
asciilifeform: picture a kind of 'multiverse ada', where you dun call foo(bar), but instead foo:somepatchid(bar:somepatchid) etc, explicitly conforming to 'multiversism'...☟︎
asciilifeform: and especially this one, v that understands entity introductions / uses, semantic linkage aligned with v-flow ... i'd like to see it
asciilifeform: i'd like to encourage trinque to put some of his 'crackpot' algos 'to paper', as articles. the hypertext thing was interesting imho, for instance, and so was earlier trinque pill for 'mining is a bug', and possibly other occasions. dun be afraid to write down conjectures, trinque , gauss did☟︎
asciilifeform: trinque: if you have concrete algo to align these -- i'm all ears
asciilifeform: semantic linkage in prog lang oughta align with v. not vice versa.
asciilifeform: trinque: i'd go as far as to say that what you're observing is a defect in cpp, not v.
asciilifeform: ( btw is there an engl. equiv of that term ? i'd like to learn it )
asciilifeform: hence 'coarse error of pilotage' in re shiva
asciilifeform: and yes every patch oughta stand as a leaf, pressable to .
asciilifeform: trinque: it is only a problem if people do it unthinkingly, without understanding when to, when not to, and why
asciilifeform: trinque: i actually put a good bit of thought into the vtronic shape of ffa, while rewriting it ( current-day ffa , observe, is a rewrite, largely by hand, of the previous )
asciilifeform: ffa is, among other things, an experiment with minimizing theugly.
asciilifeform: http://btcbase.org/log/2017-12-27#1758907 << the reason engineering is even possible , is that it is not necessary to open ~every~ box. sometimes can form quite accurate picture without spending whole life opening boxes, eating every rotten egg top to bottom etc☝︎
asciilifeform: http://btcbase.org/log/2017-12-26#1758681 << if there existed anything like a market in (reasonably recent) miners -- they'd already be installed at the plant, in place of those gigantic resistors . ( and iirc there was a mircea_popescu thread, involving e.g. fish ponds )☝︎
asciilifeform: ben_vulpes: ( trinque ? ) what ~concrete~ operation on trb tree did v-as-it-nao-exists keep you from easily carrying out ? i'd like to see ?
asciilifeform: what is with this eagerness to pointlessly blunt the knife. i dunget it !
asciilifeform: i ~like~ that it is clear what parts of a whole were changed, and what -- left alone.
asciilifeform: ( i.e. it is already inescapably linear. asciilifeform half-expected that the kakoschism would produce a long-playing split of the trb universe, but neverhappened. not every possible thing, happens... )
asciilifeform: http://btcbase.org/log/2017-12-26#1758779 << i see e.g. trb tree, as the frayed end of a rope. in long term, observe, the loose ends that dun get built on -- fade away, like orphan chains. btc is actually more or less same kind of system. but iirc we had this thread.☝︎☟︎
asciilifeform: i would like everybody who is itching to change the way v fundamentally works, to sit down and think about why we ain't using 'git' etc.
asciilifeform: i should not need to look for a meta-document (with own sig, presumably) to know which group of patchons constitutes e.g. 'asciilifeform_dns_thermonyukyoolar_kleansing' .
asciilifeform: http://btcbase.org/log/2017-12-26#1758781 << this only oughta be done in 2 situations -- 'releases' , as discussed by mod6 et al ; and to avoid fuckuppy as seen in orig shiva patch, where there was a logical dependence , but not a vtronic one , b/w shiva-part1 and -part2☝︎
asciilifeform: a v user is expected to do ~almost all~ of his manipulations, via manual file management.
asciilifeform: which, in the whole picture, does not come close to topping the list of the hardest labours of a trb experimenter
asciilifeform: but you can replicate same effect by pressing by the press rules, and then copying by hand.
asciilifeform: ( it was , naturally, by having , at least in the early history, the tree from which each of the 'sibling' patches was produced, on account of having produced'em ) .
asciilifeform: http://btcbase.org/log/2017-12-26#1758788 >> 'The founder also promised that in addition to the common practice of crediting BTC holders with equivalent balances of the new coin (B2X), they would also receive “a proportional number of Satoshi Nakamoto’s Bitcoins as a reward for their commitment to progress.”' << lol!!☝︎
asciilifeform: let's say every homo redditus alive -- suddenly interested. then WHAT? what's gained, other than a great mass of meat that now gotta be put somewhere far from the reactor rods☟︎
asciilifeform: http://btcbase.org/log/2017-12-26#1758834 << it is not clear to me why the current scheme ( leaving aside the idiocies of unix diff/patch, in particular the file moves thing ) is not satisfactory. i dun subscribe to the 'force beauty through mechanism' school of thought. it is the job of the patch author to make it behave acceptably in the target vtree, ~before~ releasing. and failures are of the author, not of the mechanicals.☝︎
asciilifeform: i suspect that not 1 could follow, e.g., the apeloyee noise floor thread.
asciilifeform: the problem with voice pirates, any and all who have ever at any point lived, is that they are reddit.
asciilifeform: the usg polizei prioritize the voice pirates, because they compete directly with the usg 'music' monopoly
asciilifeform: but observation is that plenty of folx are, i suspect, already 'pirating'
asciilifeform: http://btcbase.org/log/2017-12-26#1758839 << asciilifeform did a bit of survey of the sw spectrum ( where he lives , but also elsewhere, via helpful public toilet ip-streamed receivers. ) plenty of digital ???? in'ere. incl. in places where none 'ought', Officially, to be. but 1) could just as easily be usg 2) it's all, definitionally, carriered signal, or asciilifeform would never have learned of it☝︎
asciilifeform: in other lulz, https://archive.is/Q0fc5 >> 'Thousands of government papers detailing some of the most controversial episodes in 20th-century British history have vanished after civil servants removed them from the country’s National Archives and then reported them as lost.'
asciilifeform notices massive shitflood, turns out: front page of lamernews again
asciilifeform: if yer a nobody, and you were to show up with a ~serious~ 0day : you have 1000x chance of getting 'weev'-ed, rather than paid .
asciilifeform: the 3 or 4 people on the planet who can actually SELL 0days , knowing they'll be paid 1) know who they are 2) wouldn't even cough and spit for a mere 500 , esp if paid in taxolade 3) don't deal with 'uber' et al, or any 'responsible-disclosure'-pushing usg.tentacle , not for promises of three kingdoms and five princesses
asciilifeform: also why wouldja 1) help hitler 2) for $ 500 3) that you'd have to suffer from down's syndrome to actually believe will be paid ...?☟︎☟︎
asciilifeform: 'If you invest any time and effort into HackerOne Bug Bounties, HackerOne does not honor their minimum bug bounty guarantee, and will not go to bat for you if you have a dispute with one of their well-placed vendors such as Uber.' << noshit.jpg
asciilifeform: also Believe Moar PGtronic sc4mz0rz...
asciilifeform: s the same token I keep getting, no matter how many times I log in and out of my account using the Surface app' << lel
asciilifeform: 'I put together a Python-based client that can talk to Uber’s backends, to start harvesting OAuth2 tokens for entropy analysis and to see if there are any issues with their PRNG. What’s weird though is that the OAuth2 token doesn’t ever change, and I can’t find anything in the Uber developer documentation that deals with token expiration; literally the same token I was issued when I first created my Uber account for testing i
