3900+ entries in 0.281s
trinque: ascii_field: it has; in this case reconnected as
deedbot-- but could not auth
BingoBoingo: ascii_field: mebbe
deedbot is afraid of the gossipd similarity to usenet? Fears #b-a.tasteless?
mircea_popescu:
http://log.bitcoin-assets.com/?date=27-11-2015#1332526 << for the record/future and as best practice : mod6's style of doing these, with pastes etc is much better, because it allows later effort to build upon previous effort.
deedbot- is also not a bad venue to store this sort of thing, seeing how it's just code atm. "when i do so and so this is the bt resultant".
☝︎ BingoBoingo: jurov:
deedbot- didn't get the title update.
jurov: BingoBoingo:
deedbot- already did it
trinque: speaking of which, why the hell is
deedbot gone again
adlai was on the verge of daily [originally hourly, but that would probably get him negrated by
deedbot- itself] orderbook deeding, but then he realized the venture's futility
trinque: mircea_popescu: could just be freenode being a pain. I notice that
deedbot- will say on this end that "Remote host closed the connection" and on the
deedbot- end that he looks like he was disconnected by the server.
trinque: remote host certainly did not close the
deedbot connection...
assbot: You rated user trinque on 17-Oct-2014, with a rating of 3, and supplied these additional notes: Nice work on the
deedbot.
assbot: Logged on 12-11-2015 19:22:01; trinque: mircea_popescu: kakobrekla: the logs up to last month have been sent through
deedbot-
punkman:
deedbot must maintain copies of all bundles though
adlai: this is not, after all,
deedbot-fs...
trinque: adlai: to clarify, I took you to mean that
deedbot- ends up doing its own archiving, which is what it's doing as a 1-off for the logs
trinque: for now I think keep it simple, and then it could be revisited after I catch up on other
deedbot- work
trinque: mircea_popescu: kakobrekla: the logs up to last month have been sent through
deedbot-
☟︎ adlai: trinque: fwiw
deedbot- also seems to be using uncompressed addresses, perhaps a bug of the feature variety
trinque: mircea_popescu │ incidentally : should we
deedbot a version of the logs, in the manner of gpg source etc ? << certainly. does assbot perhaps dump what it has seen somewhere, kakobrekla? my logs would only go back so far.
mircea_popescu: incidentally : should we
deedbot a version of the logs, in the manner of gpg source etc ?
adlai: trinque: not criticising
deedbot-, saying that it's the answer to mircea_popescu's question
adlai: some dark and dystopian future, mpex trade submission will require
deedbot-style spending, for anti-ddos
trinque: I am quite backed up on things
deedbot- needs, but am aware of most of them
mircea_popescu: (kinda shameful how we omitted the entire
deedbot and btcalpha infrastructure from the things, becuase hey, fuck trinque and mike_c we got the stuff made so we no longer need it made so we can forget about it right ?
mircea_popescu: i would about 100x rather use a
deedbot-based system. and i don't think something like that is usable.
trinque:
deedbot-'s blockchain has caught up thanks to mircea_popescu's node
assbot: Logged on 04-11-2015 20:13:17; trinque: two things there: one I think I will begin looking into the connect vs addnode tangle this weekend, as it's affecting the proper functioning of the
deedbot-
trinque: two things there: one I think I will begin looking into the connect vs addnode tangle this weekend, as it's affecting the proper functioning of the
deedbot-
☟︎ trinque: asciilifeform: along the lines of the problems with your node,
deedbot- now routinely gets orphans and nothing else blasted at it from various IPs, and will at times not be able to reach the node mircea_popescu gave, though I am not presently certain why
trinque: mircea_popescu: in my logs,
deedbot's btcd eventually disconnected from 188.68.240.159 and began receiving orphan blocks again. after restarting it, it reconnected to your node and is receiving blocks normally again
trinque:
deedbot- is having a terrible time getting a node which will speak to him at the moment
felipelalli: trinque, do you know why my deed wasn't published yet in
deedbot.org? Thank you.
trinque: ben_vulpes | tonight we fuzz
deedbot-! << escuse
trinque: as for investing in
deedbot I don't see the angle
punkman: asciilifeform: well for
deedbot I hashed and checked for dupes
adlai:
deedbot put the hash in the blockchain, assbot put the content in the cloud, what more does a man need?
adlai: first time, it didn't deed at all; second time got notarized in block 380163, but doesn't show up on
deedbot.org
adlai: trinque:
deedbot.org is not showing the latest deed
trinque: got another
deedbot- hacking weekend coming up; we'll see what I bite off
mircea_popescu: <
deedbot-> [Qntra] 78 Months in Prison for Carl Mark Force IV << does he get any "guard" slaves to impregnate ?
davout: punkman: i looked at both, and trinque's script is also reporting a different address than the one i see on the
deedbot page
jurov: trinque there's supposedly a faq for
deedbot, where?