asciilifeform: thimbronion: is there currently a means to stfu replays >x min. old ?
asciilifeform: thimbronion: atm firehose of ancient replay straight into dulapbot's log
asciilifeform: i'ma unplug the pestnet dulapbot nao, cuz this is getting ridiculous.
thimbronion: asciilifeform: no there is no way to ignore replays >x min. old atm.
asciilifeform: aite. guess there's no way to stand up a usable logger from scratch atm
asciilifeform: the other q is wai did it drown on this vomit only ~today~ and not yest.
thimbronion: Why not sync first, then plug in?
asciilifeform: oughta have drowned immed
asciilifeform: thimbronion: i left the pestron to sync, but seems to have stopped getdata'ing after bot dropped
asciilifeform: ( dun seem like current blatta operates correctly if no console ? )
asciilifeform sadly must attend to meat chores; will bbl
thimbronion: shinohai: are you absolutely certain your bot is running the latest version? I deleted the pestbot db and started a sync from scratch. Already past all the uniturds with no crashes. Also I noticed you went offline when I sent some uniturds this morning.
shinohai: thimbronion: Just repressed and restarted both stations, maybe first press failed? Dunno but didn't die this time seeing unicode.
thimbronion: shinohai: good to hear.
thimbronion: http://logs.nosuchlabs.com/log/asciilifeform/2022-06-19#1107594 << try not to repress your stations too much or they might rebel.
dulapbot: Logged on 2022-06-19 14:44:26 shinohai: thimbronion: Just repressed and restarted both stations, maybe first press failed? Dunno but didn't die this time seeing unicode.
shinohai: lol
shinohai: Me: "Bitch do what I say!" Station: "No daddy, PLEASE!"
thimbronion: http://logs.nosuchlabs.com/log/asciilifeform/2022-06-19#1107586 << This is not true according to the experiment I ran this morning. Started up station with empty log table. After receiving one message, it synced fully in about 15 min. I then started pestbot which connected to the station and responded instantly to the first command.
dulapbot: Logged on 2022-06-19 12:52:20 asciilifeform: aite. guess there's no way to stand up a usable logger from scratch atm
phf: can someone explain the mechanism behind the naming in http://logs.nosuchlabs.com/log/pest/2022-06-19#1000562 i assume the [xx|xx|xx] is hearsay going through xx, but why would it go through asciilifeform three times?
dulapbot: (pest) 2022-06-19 busybot[asciilifeform|asciilifeform|asciilifeform]: The 24-Hour VWAP for BTC is $ 19584.80 USD
thimbronion: phf: that's a bug.
thimbronion: Each handle should only be listed once
thimbronion: phf if you can figure out how to reliable reproduce I would be much obliged
asciilifeform: thimbronion, phf : i'd expect can reproduce this by reproducing asciilifeform's setup -- connect a newly-baked station to your primary and let it sync
asciilifeform: http://logs.nosuchlabs.com/log/asciilifeform/2022-06-19#1107600 << interestingly, yes, mine eventually synced (or -- at least stopped emitting getdata's -- in fact thought it had 100% synced yest.!) ; no idea presently what precisely was happening there
dulapbot: Logged on 2022-06-19 15:12:00 thimbronion: http://logs.nosuchlabs.com/log/asciilifeform/2022-06-19#1107586 << This is not true according to the experiment I ran this morning. Started up station with empty log table. After receiving one message, it synced fully in about 15 min. I then started pestbot which connected to the station and responded instantly to the first command.
asciilifeform: phf: ftr dulapbot at the time of the lulzy [asciilifeform|asciilifeform|asciilifeform...] was peered only to asciilifeform
asciilifeform: ... evidently bug not only in dedupe, but also where causes hearsays to be relayed >1ce
verisimilitude: I want to pay someone with a cryptocurrency. However, he doesn't accept Bitcoin, but Ethereum. What are your suggestions for a geographical service of which I may make use to send money to an Ethereum wallet?
adlai|text: verisimilitude: search around for "instant exchange", these spring up like weeds. obviously they have counterparty risk, they always work in the way most favorable to their operators, rather than actually using scripts to make the two payments mutually continguent.
adlai|text: the original ones did not require registration of any sort: on first page, HTML form for source and target coins, target address, and amount; click, receive ephemeral sending address for source coin, and amount to pay.
adlai|text has not used any of these recently, although a few years ago they did all seem to begin requiring some amount of additional info, e.g. email address, or worse, an entire account registration process.
adlai|text may have misunderstood what verisimilitude meant by 'geographical'
verisimilitude: I meant like meeting with someone to do this.
adlai|text: aha. localbitcoins.com is/was a centralized site for this kind of matchmaking; and these days, there is a decentralized java hairball whose name I'm inexplicably blanking on.
adlai|text: bitsquare.io
verisimilitude: I'll look into it; I appreciate it, adlai|text.
adlai|text: I think the original idea of BitSquare was to matchmake traders who wanted to trade coin in return for bank transfer of fiat, although it is definitely possible to do one coin for a different one.
adlai|text was disappointed to find it not useful for physically locating traders for a cash payment, a few years ago, although in retrospect this is not too surprising. it is designed with the assumption that the payments in both directions are electronic and reasonably immediate, even if they take some time to confirm.
adlai|text: if able to trade cash... why do you need the java hairball? simply each point pistol at counterparty, smile, and trade; holster upon reaching sufficient confirmations.
adlai|text: if not own pistol, 'not ready for bitcoin' (tm) (/s) (r)