4709 entries in 0.448s
mircea_popescu: hanbot please go through the foundation lists and
deedbot the various stuff in there.
trinque: I'll clear out what's currently uploaded when I have
deedbot join
trinque: +mircea_popescu | <trinque>
http://deedbot.org/ << there be deeds << cool. why are some repeated ? << test values; I published bundles with the same messages a few times while working
trinque:
deedbot.org is where it will be shortly
trinque: got the
deedbot blockchain up to date yesterday, haxed on the transaction creating guy
mircea_popescu: asciilifeform scoopbot's down,
deedbot not here, it's like microsoft over here.
mike_c: decimation:
http://stampd.io/ << someone made a silly-con valley-ized
deedbot << yeah, and you have to pay for it with.. paypal!
trinque: anyone have a fast node I can give
deedbot btcd? it's got about a month left of catching up
trinque: anyone have a high bandwidth node I can give to
deedbot to speed his ass up?
trinque: I switced the
deedbot blockchain to an ssd ebs volume
trinque: my btcd for
deedbot has been belching about orphan blocks for a day, ever since it got to about two days ago in the blockchain
trinque: mircea_popescu: this blockchain is for
deedbot mircea_popescu: punkman: ^ if the block the bundle tx ends up in disappears, I think best idea is to make new tx << no. there's exactly no reason for
deedbot to have block awareness. if the tx disappears, it should not notice.
trinque: I think I'll just give
deedbot an out to spend and when it's depleted it's done, insert another please
trinque settles in for a few hours of
deedbot hacking
trinque: mircea_popescu: with
deedbot? got hit with a bunch of irl work
mircea_popescu: trinque: I'm starting to itch for a sqlite+deturdolatedbitcoind experiment <<< wha happened to
deedbot ?
davout: trinque: do you intend to run a full client for
deedbot's needs?
trinque: what we came up with was just rolling forward from the transaction which funded
deedbot first and finding spendable outputs each time, then using one to stamp
trinque: talked with ben_vulpes last night about the
deedbot "publisher" service, which does the blockchain timestamping
mircea_popescu: <ben_vulpes> okay! i'm off for a few - going to hack on
deedbot with trinque nao < ?! lol
ben_vulpes: okay! i'm off for a few - going to hack on
deedbot with trinque nao
trinque reaches the top of the pile, switches to
deedbot dev
trinque: Apocalyptic | trinque, by the way how's
deedbot coming along ? << I have been tied up with work the past few days, but not much more to be done. a tweak on the hashing bit to re-hash when an invalid privkey is generated, then the check-confirmations-and-upload cron job.
Apocalyptic: trinque, by the way how's
deedbot coming along ?
BingoBoingo: Dunno why
deedbot would need a deed.py client though
BingoBoingo: trinque: If
Deedbot has a need for sounds...
Adlai: i wasn't bringing this up as "look at coinbase, they're doing something!", but as "maybe i can help your thing do its stuff better" (setting aside the bit about
deedbot doubling as a faucet, which works fine in the current method)
Adlai says,
deedbot can spend half as much coin and create zero as much pollution; if there's interest, he can review and sign the code doing it
trinque: punkman: did you just keep a local count of
deedbot's balance?
undata: that's the last thing
deedbot needs; I've got a free-ish weekend coming up too
undata: quick update before I dive into bezzeland biz, I bought
deedbot.org for deed bundles, and the thing's two cron jobs and some code cleanup from being ready
davout: if someone pops in here one day and says "o i can't pick up
deedbot's crumbs anymore" you have a problem somewhere
Apocalyptic: so you would not want
deedbot to take it back
davout: Apocalyptic: by
deedbot