log☇︎
450500+ entries in 0.285s
trinque: shinohai: I noticed that as well
shinohai: There is a slight spelling error in this document: http://thebitcoin.foundation/declaration.txt ☟︎
shinohai: I have only seen the Comcast guy 2 times in 5 years in this place I live.
shinohai: Nah he was probably being defensive because he was afraid they would find his My Little Pony playset or something.
cazalla: don't you ever touch a white man's modem
assbot: Portland man arrested for violent tantrum after seeing Comcast worker in bedroom | OregonLive.com ... ( http://bit.ly/1U5wi8U )
cazalla: and even if you don't buy it or try to limit it, well intentioned friends and family try to load you up with all manner of shit
assbot: Logged on 30-06-2015 16:24:21; ben_vulpes: and i'm being dramatic about the plastics, there's a many-in-one stroller thing that a relative mentioned getting for us
cazalla: http://log.bitcoin-assets.com/?date=30-06-2015#1181836 <<< the plastic shit is everywhere :\ ☝︎
ascii_field: mircea_popescu: if you have any other nodes of this kind, consider posting the hash
trinque: neh I like micro-terrorism... there it stays
trinque tries to come up with a more fitting euphemistic propaganda term
trinque: someday soon they're going to start calling this kind of shit something as stupid as "micro-terrorism"
trinque: While Google’s efforts to solve this problem are admirable, it’s still troubling that it happened at all. As Alciné wrote on Twitter, “I understand HOW this happens; the problem is moreso on the WHY.” << oh for fuck's sake
BingoBoingo: Google, not the Rebel Flag is the real racist http://www.slate.com/blogs/future_tense/2015/06/30/google_s_image_recognition_software_returns_some_surprisingly_racist_results.html
ascii_field: nothing to do with bdb
ascii_field: why shouldn't they match ?
ascii_field: mp_strange was on the 'stator' build
mircea_popescu: odd, they really shouldn't match
mircea_popescu: maybe this is half-deterministic somehow ? did you make them on the same build ?
ascii_field: 'mp_strange' is the data set discussed earlier
mitzip: BingoBoingo: thanks I feel the same way :)
ascii_field: mircea_popescu: consider preserving the turd for dissection
mircea_popescu: yeh the problem's later, 310kish
ascii_field: for what it's worth, all the blocks i got from mircea_popescu are successfully eaten by my 0.5.4 ☟︎
mircea_popescu: yes i know. talking bout my own problem here!
ascii_field: that's sorta the whole point of bitcoin
ascii_field: so it is conceivable that yours barfed on an orphaned (in the original sense) block
mircea_popescu: i have never seen blknnnn of the same size even, forget the same contents
ascii_field: all 16MB of them
mircea_popescu: ah, those don't help, obv every client makes its own blockchain set
mircea_popescu: anyway, i've been digging into all sorts of strange re this since 3 days ago, what's a bucket more.
ascii_field: at any rate, i posted checksums of what i personally got over the wire, earlier.
mircea_popescu: apparently the "damaged in transit" thing happens o.O
ascii_field: mircea_popescu: http://btc.yt/lxr/satoshi/source/src/db.cpp#0041 << in classic 0.5.3. naturally i haven't the faintest clue re: yours
mircea_popescu: terminate called after throwing an instance of 'DbException' << teh sound of unhappy. i'll be doing shasums for the rest of the day by the looks of it.
ascii_field: has the 'prefix network number' bullshit
ascii_field: BingoBoingo: entirely not the same
BingoBoingo just be running horribru underpowered machines for this task
BingoBoingo: Apparently 'cat' is fine too https://bitcoin.stackexchange.com/questions/10381/creating-my-own-bootstrap-dat
ascii_field: from 0 to maxheight
ascii_field: mno, hours total
BingoBoingo: Well, once I got into 2013 and months crawled into taking days per any speed up wasn't much noticable
assbot: [ANN] Bitcoin blockchain data torrent ... ( http://bit.ly/1IqK8Ow )
ascii_field: on account of not having the hours-long bastard block doldrums
ascii_field: and i beg to differ that direct arse-to-mouth of blocks 'doesn't speed sync'
BingoBoingo: I think garzick had a script somewhere I'll did
BingoBoingo: Bootstrap.dat did what it was supposed to on v0.8.6 though, didn
BingoBoingo spent some time dicking around with it when did OpenBSD 0.7.2 -ish build
mircea_popescu: afaik this ^ is correct
BingoBoingo: <jurov> ascii_field probably isn't aware that exactly the same thing as dumpblock output is the phoundation's bootstrap.dat << As far as I'm aware the "bootstrap.dat" never got implemented in a way that worked beyond the first 2GB of blockchain on pre-v0.8 clients
mircea_popescu: i would have inquired whether front facing fanny or rear facing fanny, but i was pressed for time sadly.
mircea_popescu: in even further news, overheard in the street like an hour ago : "mommy, mommy! is it a good sign when your fanny itches ?" ☟︎
mircea_popescu is going to get top the logs just as soon as he's done hammering the seeder into shape
ascii_field: but many good things
mircea_popescu: somehow i suspect its more common than kk
mircea_popescu: incidentally, i wonder how many times in the history of linux one has issued the command ;;
ascii_field: but now one can single-step the sync, and remove just about all nondeterminism
ascii_field: and i never imagined i was the first to ever dump blocks - i think just about everybody had some 3rd party script thing to do it with
assbot: [ANN] Bitcoin blockchain data torrent ... ( http://bit.ly/1IqIah6 )
jurov: https://bitcointalk.org/index.php?topic=145386.0 lol and they managed to obsolete it already
assbot: [BETA] Bitcoin blockchain torrent ... ( http://bit.ly/1IqI8pi )
ascii_field: i mean, the blocks were in there to begin with
jurov: would be interesting to compare them
jurov: ascii_field probably isn't aware that exactly the same thing as dumpblock output is the phoundation's bootstrap.dat
ascii_field: jurov missed all the good stuff, l0l
ascii_field: (if this wasn't clear, this is a node running without a net connection at all)
ascii_field: (actual mass of these, without ~anything~ extra)
ascii_field: the raw blocks 0...217336 sum to 5.3GB.
ascii_field: unless somebody else wants to..
ascii_field: later this week (still gotta do my broadcast tonight...) will throw this into 'gnuplot'
ascii_field: and saving output thereof
ascii_field: presently, while i'm doing entirely other things, it it running pmap -XX <pid> after each eat
ascii_field: in other nyooz, 'dumpblock' for the sums.txt.gz mircea_popescu set 0..n and subsequent 'eatblock' in brand-new stator - works ☟︎☟︎
mod6: well, i still had the build directory anyway. a list of patches & checksums is at the same URL nao: http://thebitcoin.foundation/doxygen/v0_5_3_1-wPatchesApplied/v0531-wPatchesApplied.txt
BingoBoingo: Stator on shittop sync'd to 200 kiloblocks
mod6: I did it like that because the list of patch names is far too long. makes it look kinda ridiculous in the header
ascii_field: shinohai: in all cases, the canonical code is the original pedigreed and signed 0.5.3 and the sequence of signed patches which add up to a release
mod6: huh? no, im laughing because when I swapped the doxygens around (LR, to TB) i nuked the file that showed the patches included.
ascii_field: shinohai: that thing is intended only for eyeballs/study
assbot: USB Typewriter ~ ... ( http://bit.ly/1Kr1gVX )
trinque goes to forage for coffee
ascii_field: FUCK 3d-printed faux typewriter case, screen one has to squint at, and 'cloud'
ascii_field: and before anyone links to the barfalicious 'hemingwriter' thing - just don't. please.
ascii_field: now it gathers dust - keyboard has three or so keys that flip the thing into jp mode, and they 'get pressed' constantly (on account of how cramped the thing is)
ascii_field: trinque: i've been looking for something that fits that description - while not being a piece of shit - for a decade
trinque: neat. that thing's exactly what I've meant about a device which is only for editing buffers of text.
ascii_field: 'I plan to start using the machine again because its keyboard is superior to any other laptop that I've owned and it boots far faster than any other laptop that I've owned.'
ascii_field: ' the NEC still wins over most portable computers of any time for the quality of its keyboard. This is a machine for typing on, and producing content, not for consuming content... Even now, nearly 30 years after production, it still works perfectly. The larger capacity modern rechargeable AA cells means that four of these will keep it running for weeks. Astonishing battery life compared with modern devices.' ☟︎
mod6: **NOTICE** I'll be updating the graphs in this: http://thebitcoin.foundation/v0_5_3_1-wPatchesApplied/ in about the next ~15 minutes. So if there's a hiccup, just wait a minute or six.
mod6: perfect, thanks!
mod6: <+mod6> plz clearsign your email, and attach a detached signature of the patch file << along with the patch itself i might add!
Jautenim: sure! i was puzzled too, thought that'd be enough
mod6: danielpbarron: yeah, i saw that. i thought that'd be enough. but maybe something else is up? anyway, you can send to me. I'll review, etc.
mod6: some detals on that are here: http://thebitcoin.foundation/ml/btc-dev/2014-December/000022.html
mod6: plz clearsign your email, and attach a detached signature of the patch file
mod6: ah, i don't think you're in assbot's L2. Sorry if I wasted your time. Just send the patch to me: modsix@gmail.com ☟︎
pete_dushenski: ^name that car, kidz !
ascii_field: srsly my turds aren't 'gospel', publish corrections/repaintings/etc
ben_vulpes: and flip-cover for eatblock because state of running bitcoinator is mutated by its use, while the dumpblock does not mutate and so does not need a flag?