log☇︎
24500+ entries in 0.038s
mod6: that's what it does though, chews up ram
mod6: just let it run
mod6: yeah
mod6: sorry
mod6: f
mod6: http://pastebin.com/MswHdRyg
mod6: yeah. it ate that one of mine too. its hungry.
mod6: <+asciilifeform> mod6 check plz ? << i don't see anything in the mailing list
mod6: what header?
mod6: asciilifeform: sweet. what'd ya have to patch?
mod6: looks ok on that box
mod6: lemme see on this pcbsd box, its set to 1024x768
mod6: asciilifeform: what size display do you ya have? i checked it out with lynx too, looks pcool.
mod6: decimation: thanks!
mod6: asciilifeform: awe
mod6: has anyone else used PC-BSD?
mod6: *considering
mod6: BingoBoingo: werd. been consider switchin to hard-core mode.
mod6: Thanks, Sir.
mod6: danielpbarron!
mod6: does anyone like thebitcoin.foundation/banner.html ?
mod6: *gentlemen too :]
mod6: http://thebitcoin.foundation/build.sh.sig
mod6: http://thebitcoin.foundation/build.sh
mod6: would one of you gentlement verify it for me?
mod6: so i added the file direct to the website, along with the sig file
mod6: ok, so i sent the build.sh script in plaintext with a detached sig to the mailing and it just never showed up. lol
mod6: <+asciilifeform> what are we to do? pretend it's 1995 and post uuencoded turds ? << perfectly fine with me.
mod6: http://log1.bitcoin-assets.com/?date=26-10-2014#897503 << lol
mod6: yeah. weaksauce
mod6: you know, before I did any of that, i thought about doing a detached sig, but then i wondered if something really funky would happen, like it would get somehow added to the patch-list automagically, and it doesn't belong there either.
mod6 breaks more stuff
mod6: as it seems, gnupg did that nonsense.
mod6: actually, jurov, it's not the fault of the turdalator
mod6: im just gonna post the fuckin script to the website direct.
mod6 breaks random things
mod6: ^^^
mod6: jurov: check this out
mod6: ^----- the turdalator adds this dash on parse
mod6: - --verify chicken/bitcoin-asciilifeform.1.patch.sig
mod6: gpg --logger-file chicken.sig.log --homedir .gnupg \
mod6: anyway, so the script that i re-posted to the list wont work
mod6: wat
mod6: fuck
mod6: ok i re-sent with a new version number and "<modsix at gmail dot com>" written in by me.
mod6: one of these times, I gotta get mutt back going again
mod6: when i had mutt setup properly with my own mx it was pretty sweet because it would check sigs and everything automagically.
mod6 works on that
mod6: i'll send out a new copy.
mod6: ok cool, good catch ascii
mod6: if you could be so kind... just change the text to that and see if it verifies.
mod6: and then the turdalator changed it
mod6: so yeah, i signed "<modsix@gmail.com>"
mod6: i bet that the damn translation of my email address did it
mod6: oh i know what it is.
mod6: srsly?
mod6: i think he's trying to make a v6 addr
mod6: we're using v0.5.3.1
mod6: for now
mod6: We regret to inform you that your republic has termites. ☟︎
mod6: haha
mod6: so like: a]: v3 b]: v3.1 c]: v3.14 ... ?
mod6: decimation: i mean the pi versioning.
mod6: ah thx
mod6: LEL
mod6: decimation: they just outlawed sledding too
mod6: decimation: got a link to something about that, not seeing anything relevant
mod6 looks
mod6: any *last minute* requirements
mod6: we're getting close to wrapping up a first cut of this thing. so i want to nail down any changes before we get start to roll one.
mod6: err > 0.8
mod6: i was pretty set on v0.5.3.1 until ascii tells us that we might not be able to be talk to anything < 0.8 -- which to me seems weird.. because i've fully syncd a dozen times, and done send/receive np
mod6: anyway, i like the kalvin thing. but that'll have to be something to think about later.
mod6: overhaul required.
mod6: so... :/
mod6: (900000 = v0.90.0)
mod6: so my point here is, without a bigger overhaul to the versioning system; one would have to set 90000 to be v0.9.0, or 9000000 to be 9.0.0, but then what? because we should be counting down. and at some point, we'll cross the threshold of < 0.8
mod6: and im wondering, if we use kalvin, and start at 9000 (it'll result in v0.0.90-beta) how we can ensure that other nodes won't think we're on < 0.8
mod6: so currently, to set the version we must set this value: https://github.com/bitcoin/bitcoin/blob/v0.5.3/src/serialize.h#L63
mod6: i kinda like the notion.
mod6: ya, kalvin has been discussed too
mod6: so it seems to me, the most logical thing to call this is v0.5.3.1
mod6: <+asciilifeform> call it whatever name, but assigning a version equal to ancient phoundation release is foolish. << foolish because of nodes that wont talk with < 0.8, or foolish another reason? i've always detested version numbering because of "marketing"
mod6: that shouldn't be a huge problem. bbiab -- we can talk about that part a bit more.
mod6: :D
mod6: i'll have to pick one up when I get a chance...
mod6: thats awesome.
mod6: was i unvoiced?
mod6: ah.
mod6: $proxies
mod6: ben_vulpes: oh my bad. my eyes are bleary.
mod6: Cointrader exchange, etc? *shrug*
mod6: well then theres this: https://ca.linkedin.com/in/mitchelldemeter
mod6: oh nm.
mod6: maybe it's this guy: http://www.wired.com/2013/10/robocoin_here/
mod6: asciilifeform: regarding 'pogo': Cool!
mod6: with 128mb ram
mod6: im not going to continue this sync, unless requested. i think that's a decent demonstration
mod6: it easily lasted 12-14 hours. made it up to height=136572 ☟︎
mod6: it died finally.