log☇︎
449000+ entries in 0.259s
decimation: mats: it seems to be chroot with some device/pid/ipc space sharing
decimation: what about the days when su judge would consult telephone to moscow before ruling
asciilifeform: ru is on a 'dictatorship of the law' and 'property rights' kick
asciilifeform: among the most eager to slurp up the cock
decimation: asciilifeform: how are they gonna get an injunction against bookfi?
assbot: Introduction to Docker (and a bit more) at LSPE meetup Sunnyvale ... ( http://bit.ly/1ITv3kh )
mats: http://www.slideshare.net/jpetazzo/introduction-to-docker-and-a-bit-more-at-lspe-meetup-sunnyvale << according to this doc
assbot: Dutch universities start their Elsevier boycott plan | Univers ... ( http://bit.ly/1ITv2gh )
assbot: Elsevier Cracks Down on Pirated Scientific Articles | TorrentFreak ... ( http://bit.ly/1ITuXJs )
asciilifeform: http://torrentfreak.com/elsevier-cracks-down-on-pirated-scientific-articles-150609 << somehow missed this when it was 'news'
shinohai: For instance, this may have been a forerunner of BTCXT http://notquant.com/wp-content/uploads/2014/06/rube.gif
trinque: shinohai: yeah I used it on deedbot to make a final judgment
trinque: so probably loads to be done to that thing too
trinque: I would expect (as admittedly a casual in the kernel space) to find the same kinds of break-out flaws in docker and linux containers as are found all the time in xen
decimation: asciilifeform: maybe you can use systemd to boot it
trinque: assuming the hardware, kernel, distro, docker, distro, and your proggy are perfect, sure!
asciilifeform: gotta love the 's333k000r1ty benefitz' of running a blob of hipsterystrange as root
asciilifeform: ;;later tell mircea_popescu https://github.com/Rossem/RedditStorage << somebody liked your reddit-shitburial idea ☟︎
trinque: the docker daemon itself is this vast wad o' golang that runs as root ☟︎
trinque: whereas xen is a hypervisor, docker uses the linux containers thing, which effectively gives you multiple userspaces
trinque: yet another "lets try to layer tape upon the turd and hope that solves the underlying derp of the system"
asciilifeform: but not an arbitrary code exec thing
asciilifeform: decimation: that's not an escaper
decimation: asciilifeform: did you see the cache telegraphy escape?
asciilifeform: (not to be confused with the last such, which relied on a flawed emulation of pc floppy card. this one uses nic.)
asciilifeform: ^ contains a link to the original paper, for anyone unfamiliar.
assbot: A Few Thoughts on Cryptographic Engineering: Poker is hard, especially for cryptographers ... ( http://bit.ly/1ITruKY )
asciilifeform: decimation: that is only needed when one is verifying the 'fair' bit
decimation: I would think it would require examining the outcome of every player's bet
asciilifeform: but afaik this was never pursued by anyone.
asciilifeform: (see, for example, the 'millionaire protocol')
asciilifeform: now, it is not physically impossible to solve this problem
asciilifeform: iirc the satoshidice inventor offered a reward to anyone who might devise a means whereby he can prove that he doesn't do this
asciilifeform: whose only purpose is to be one of the 'provably fair' winners that day ☟︎
decimation: yeah, me neither, but sending the server seed seems like you are putting your balls on the chopping block
asciilifeform: one obvious observation, however, is that 'house' can never prove that it had not shared its seeds with a shill
asciilifeform doesn't care for either kind of dice game, cannot comment re: the appeal of 'provable' ones
asciilifeform: because go & prove that it is a physical whatever, rather than a house-always-wins source
asciilifeform: the whole 'provably fair' thing
decimation: lol why do they need to give seed
asciilifeform: iod, think hundreds of requests in under a second. The result of this is that he knew all the information required to corroborate the outcomes of his bets. He knew whether if he would win or lose, and could wager accordingly.'
asciilifeform: 'Part of the functionality of our site is that we have to give out decrypted server seeds (to assure users no bet manipulation has occurred) and put a new random seed in place, essentially trashing the old revealed seed. Hufflepuff found a way to “confuse” our server, and made it give out a decrypted server seed that was also an active seed. This was done by sending it more requests than it could handle in a small time per
assbot: Sniffing could provide autism test - BBC News ... ( http://bit.ly/1ITqaYA )
decimation: http://www.bbc.com/news/health-33362472 < "She told the BBC that "Children with autism didn't show this modulation at all - they took the same sniff for the smell of shampoo as they did for rotten fish." "They also showed that the more severe the symptoms of autism the longer the children inhaled the unpleasant smells. "
assbot: Breaking the house — Medium ... ( http://bit.ly/1ITq8zW )
assbot: Trust relationship from user DanyAlos to user assbot: Level 1: 0, Level 2: 0 via 0 connections. |http://www.btcalpha.com/wot/trust/?from=DanyAlos&to=assbot | http://www.btcalpha.com/wot/user/assbot/
asciilifeform: except i'm not sure why this requires GBytes of rubbish
decimation: except this feature could be integrated into bitcoind
decimation: okay, well that's essentially what electrum server does I guess
asciilifeform: query the cutout (said full node)
decimation: so need to query for my txns
asciilifeform: the full node is '-connect'ed to a public-facing node, yes
decimation: this goes to the ancient thread about what bitcoind should do
asciilifeform: decimation: neither side, properly speaking, ought to be 'public'
shinohai: I can't get electrum right for shit. I did a test tx using pywallet to import a privkey
decimation: essentially, querying the blockchain for my txns
decimation: account belongs on the public side?
asciilifeform: the bitcoind, in turn, needs to know how to 1) crap out a proper tx for it to sign 2) eat the result
asciilifeform: thing on the other side needs to know how to sign a tx
decimation: and send txns
decimation: how do I find txns for accounting in my wallet
decimation: okay, you have serial line connected to bitcoind
asciilifeform: what is the purpose of said replacement ?
asciilifeform: no thx
decimation: yeah I think so, not sure
asciilifeform: wtf is the point
decimation: it uses a tcp connection with a special block server I think
asciilifeform knows that one can 'theoretically' be turned into the other, but is not so much interested in the particulars as in the overall flavour of the design, as to whether it rejected networking to begin with
shinohai: mircea_popescu has already provided an ample amount of reading between logs and trilema xD
asciilifeform: or does it open ordinary sockets and expect a tcp stack ☟︎
asciilifeform: does it know how to communicate over a serial cable with a full node ?
decimation: asciilifeform: what is electrum other than 'wallet split from node'?
asciilifeform: other than that, 'take it or leave it'
asciilifeform: if mircea_popescu ever feels like saying any more on the subject, he can.
asciilifeform: and that's pretty much it
assbot: Logged on 23-10-2014 05:07:32; mircea_popescu: <asciilifeform> connected with serial cable << this from reading up on old mpex material ?
asciilifeform: and, possibly, that he did the Right Thing and sawed off wallet into a separate mechanism: http://log.bitcoin-assets.com/?date=23-10-2014#890284 ☝︎
asciilifeform: and that it uses the traditional blkxxxx format to keep said blocks in: http://log.bitcoin-assets.com//?date=30-06-2015#1182019 ☝︎
asciilifeform: which is what we, in particular, care about, for this purpose.
asciilifeform: all i can personally say about this is that it serves up (big fat surprise!) apparently correct blocks ☟︎
assbot: Logged on 24-06-2015 02:59:50; mircea_popescu: i dun think i ever said anything about that.
asciilifeform: for the specific purpose of running mpex
asciilifeform: shinohai: my understanding is that mircea_popescu, with the help of trusted phriendz unknown to us, did something quite like therealbitcoin, early on
shinohai ^ did not know that
asciilifeform: since, i think, 2011
shinohai: is there a node list i should consider?
asciilifeform: (most of which are, at present time, considered highly experimental and will not be making it into a release any time soon)
asciilifeform: shinohai: i must point out that it isn't 'mine', but therealbitcon's (in the face of ben_vulpes and mod6)
asciilifeform: meanwhile, in turdmeisterdom, http://bitcoinstats.com/irc/bitcoin-dev/logs/2015/07/03#l1435884599.0 ☟︎☟︎
assbot: Buildroot (busybox) - [PATCH 0/5] Support for musl based external toolchains ... ( http://bit.ly/1dADYyn )
asciilifeform: trinque: thing is, 'lispy' interpreters written in a hurry by students end up being all quite alike
trinque: seems damned javascript-y, though I know it preceded that
asciilifeform: more or less a throwback to very impoverished 1970s lisps
asciilifeform: elisp, incidentally, is a world-class turd
trinque: not that I use any of them
trinque: well, there are plenty of wads o' elisp that try to do that very thing
asciilifeform: trinque: mno. because it doesn't (except in the most minimal sense) try to handle unixisms ~from within~
trinque: no offense to mr laddel
trinque: asciilifeform: the thought actually was... "so emacs is a sort of masamune... lol!" ☟︎
trinque: I guess there's a whole lineage of things which ended up being called emacs