log☇︎
198600+ entries in 0.067s
asciilifeform: mircea_popescu: the 8chan users are collectively worth what ?
asciilifeform: mircea_popescu: entirely different animals. there are folks using tor exits who -really- ought to know better.
asciilifeform: mega-l0l!
asciilifeform: ers for which no block is stored on disk, which earlier versions won't support.'
asciilifeform: 'Because release 0.10.0 and later makes use of headers-first synchronization and parallel block download (see further), the block files and databases are not backwards-compatible with pre-0.10 versions of Bitcoin Core or other software. Blocks will be stored on disk out of order (in the order they are received, really), which makes it incompatible with some tools or other programs... The block index database will now hold head
asciilifeform: ok this is pure gold:
asciilifeform: the very notion that there is any 'detection of malicious exits' worth half a sparrow's fart in the wind, or could be, is lunacy
asciilifeform: 1,001 variations on this theme possible.
asciilifeform: no automated inspection bot will notice the malicious exit then.
asciilifeform: and only begins to mitm -after captcha solved-
asciilifeform: (coming from known exits)
asciilifeform: say, it watches for the 'captcha' that google virtually always throws at tor users
asciilifeform: and when human operator is nearly certain
asciilifeform: likewise, it is trivial to construct an exit node which only doctors traffic on very specific and rare occasions
asciilifeform: and i have never seen anyone attempt to answer it.
asciilifeform: it's a rather obvious question
asciilifeform: (question pertains to exit nodes, naturally)
asciilifeform: shinohai: since you did link it... here's a mega-question for 'tor' enthusiasts. what's to stop a 'malicious' (diddles traffic) node from routing its circuits -back into tor-, and having some other exit end up looking like the guilty party ?
asciilifeform: and apple bug tip hotline, lol
asciilifeform: it isn't publicly known, afaik. and, my not being in their wot, how would i possibly know of it until now.
asciilifeform: http://log.bitcoin-assets.com/?date=06-06-2015#1156029 << probably diddled by request of jp in connection with investigation of 'aum' or the 1,001 other similar weirdo orgs there ☝︎
asciilifeform brb, food
asciilifeform: but i believe that i have explained the basics.
asciilifeform: the restless folks are also invited to visit #b-a (or my personal mailbox, gpg plz.)
asciilifeform: meanwhile looking at other manufacturing houses aiming to compete with mf.
asciilifeform: after these in fact come back, in working order, we carry on with step 2.
asciilifeform: currently waiting to see what they will say re: the cause of the five dud rng.
asciilifeform: it is useful data if i can expect at least one working board in the batch.
asciilifeform: think of it as venus mission. the probe is allowed to burn, yes, but needs to transmit some useful data before burns up.
asciilifeform: the actual problem is that the sapper gets to err two or three times, at best
asciilifeform: 1k dollars doesn't need help, it comes out of my own piggy.
asciilifeform: l0l no.
asciilifeform: that's the thing, buying 1000 units from mf is suicidally stupid
asciilifeform puts this on list to ask
asciilifeform: i asked the www, l0l
asciilifeform: iirc - only it.
asciilifeform: visa.
asciilifeform: aha.
asciilifeform: the big deal is that we're dangerously undercapitalized.
asciilifeform: btc is 'after-the-war-money' for me
asciilifeform: mircea_popescu: see above re: btc
asciilifeform: aha.
asciilifeform does not often do 'serious thought'
asciilifeform: this takes serious thought.
asciilifeform: this isn't lethal, but it does call for certain revisions in mainboard design. presently, i have reopened it, adding test points. and considering splitting mainboard in two, even. (also for testability)
asciilifeform: if the rng batch is any indication of general quality of the vendor.
asciilifeform: i mean that we have a pad defect rate of about 15 percent.
asciilifeform: sum away.
asciilifeform: the above essentially sums to 'the problems of poverty'
asciilifeform: mircea_popescu: aha there you are
asciilifeform: as it is, half the time it sees 4294967297 and - naturally - stops there ☟︎
asciilifeform: http://log.bitcoin-assets.com/?date=06-06-2015#1155850 << not quite. it's a mill of sorts, and it could be made to grind finer grain with minimal effort. ☝︎
asciilifeform: ?
asciilifeform: e.g., -imagine- i pull the trigger and am out of several 10e3 usd. i now have half a dozen complete units. none of them function. what have i learned? that i am retarded? or that there is a solder void beneath a different decoupling capacitor on each board, summing up to a dud in each case but indistinguishable with my instruments
asciilifeform: it has to be unambiguous.
asciilifeform: the defect rate is of concern because of the impossibility of -immediately and conclusively- establishing WHICH when i get the crate.
asciilifeform: if it is on account of some imperfection in the design, however minute - different matter ☟︎
asciilifeform: if i get a crate of duds on account of manufacturing defect, that's one thing, they take it back, try to fix. this costs months of added delay, but can live with
asciilifeform: among other things, it means that the first batch of cardano HAS TO work.
asciilifeform: undred and seventy-seven times, cut once' attitude.
asciilifeform: i must point out, for what is probably the seventh or eighth time, that i have no safe means of selling any bitcoin whatsoever while i live in usa. (selling for paper money, theoretically possible and suicidally dangerous, does precisely nothing to offset ANY of my living OR engineering expenses.) THEREFORE entire operation is financed from my fiat salary. this imposes certain constraints, and a 'measure seven-thousand seven-h
asciilifeform: ;;later tell mircea_popescu http://log.bitcoin-assets.com/?date=06-06-2015#1155855 << this was covered in an earlier broadcast. considering that these things will cost several hundred usd -each- to produce at mf, i would like to establish that they can produce even -one- defect-free unit of that board size and pad count. thus far, the defect rate suggests that they could not. ☝︎
asciilifeform: http://nosuchlabs.com/gpgkey/1758FA2FCC3CF671FF4BDB219AD583C50AB7E90AEAF7DBF7818E33745883F700
asciilifeform: mega-book ^
asciilifeform: http://www.burnsideinstitute.com/robot_book/robots.html << with english transl.
asciilifeform: !up Bingo_bar
asciilifeform astonished
asciilifeform: (williamdunne? was there a scoopbot thing under testing?)
asciilifeform: in other news, http://nosuchlabs.com/gpgkey/641F87E0A992064EB7CD91BC6CC7203AD8D83FFABA7C6724A698A23F61C0C1E8
asciilifeform wanders off to contemplate this
asciilifeform: likewise, each unknown is stamped with a date of last gcd-ing, as well as sha512 of the mass product at the time this was done.
asciilifeform: the mechanics of a correct phuctor are, roughly: thing keeps track of keys, rsa moduli within, as existing phuctor does; but instead of flagging 'phuctored' moduli, we keep table of known factors (associated with respective unknowns, which, in turn, may be yet-unphuctored moduli -or- fragments previously created by successful phuctorings)
asciilifeform: as it is, the gigantic turds yielded by the current gcd finds will not break apart
asciilifeform: mircea_popescu ^^^^^^ ☟︎
asciilifeform: (if composite per rabin-miller)
asciilifeform just woke up to the fact that he was a fool when originally wrote phuctor. a phuctored modulus must fragment into factors, each of which is in turn subject to all future attempts at phuctoring
asciilifeform: all else follows from this.
asciilifeform: williamdunne: fundamentally - the idiot polling
asciilifeform: l0l
asciilifeform: as in, we take everything post-1990 or so and shoot it. then start over.
asciilifeform: williamdunne: a proper internet
asciilifeform: williamdunne: no
asciilifeform: (and this is entirely aside from the idiocy of how servers get polled continuously, etc)
asciilifeform: was just pointing out the braindamage of the whole concept of rss
asciilifeform: wouldn't want scoopbot to choke on it
asciilifeform: it doesn't matter. just pointing out that the thing follows literally none of the prescribed assumptions
asciilifeform: immediately.
asciilifeform: it is entirely possible for same key to be 'new' twice in succession.
asciilifeform: rss provided no sane way to handle this.
asciilifeform: thing is, it is actually possible for the same phuctor url to be new twice.
asciilifeform: and stores forever ?
asciilifeform: what determines 'new' ?
asciilifeform: hence why i attempted it
asciilifeform: i recall that mircea_popescu asked for a real-time phuctor ticker.
asciilifeform: williamdunne: the dates are entirely unusable. see thread
asciilifeform: kakobrekla: can the rss thing be made to work as expected in the form of a #b-a bot ? or too b0rk3d
asciilifeform: mircea_popescu: earlier link to freshly phucked key
asciilifeform: aaand we are now at precisely 40 phucked moduli.
asciilifeform: mircea_popescu: this is the second or perhaps third instance thus far that i have found so far of someone who -will- be spoken to using phucked key if anyone ever bothers to speak to him
asciilifeform: so no sample of undiddled modulus for this key is known.