Show Idle (>14 d.) Chans

← 2022-12-11 | 2022-12-13 →
asciilifeform: $ticker btc usd
asciilifeform: hmm bot awol?
billymg[asciilifeform]: DOJ wants to charge the exchange that *didn't* recently crash and take customer funds with it
billymg[asciilifeform] is not saying binance should be trusted or anything, just how absurd it is that the DOJ cares more about them than the one that already blew up
asciilifeform: billymg: goxes are built, under sufferance of the reich, to fatten up an' get popped when reich decides is time.
asciilifeform: goxes are to the btc exch rate as ballast is to balloon.
awt[asciilifeform]: Lol who popped ftx tho? Not usg.
billymg[asciilifeform]: asciilifeform: binance under a different reich's jurisdiction, which is why i think they don't like it
asciilifeform: billymg: there's only 1 reich
asciilifeform: awt: popped via 'bank run' neh
billymg[asciilifeform]: asciilifeform: i count three (US, russia, china)
asciilifeform: ru & cn not claim global jurisdiction, unlike nato reich
asciilifeform not aware of any cases where someone was extradited from reich to ru or cn, or where a ru or cn biz found itself unable to operate at home on acct of 'violate us payment laws' etc
asciilifeform: is what distinguishes a generic shithole from a reich, in asciilifeform's pov
billymg[asciilifeform]: asciilifeform: ok, then in that sense i agree. but i believe binance doesn't care about what US imagines its jurisdiction to be, because it's backed by the chicoms, so going to war with binance == going to war with Xi
asciilifeform: xi vassal or not, if binance condemned by nato reich, prolly will go similarly to huawei -- nomoar reichbux wires to/from, executives dumb enuff to fly into / through reich ports kidnapped, etc
billymg[asciilifeform]: sorta like russia and its partners don't care in the slightest about whatever "price cap" usg sets on russian oil
asciilifeform: rather, but with the diff that errybody eats petro, but otoh shitcoin-pumpers are to be found mostly in reich afaik
asciilifeform not has 'dog in the race', is of the 'good gox is a dead gox' school of thought fwiw
billymg[asciilifeform]: asciilifeform: likewise, only pointing out how obvious it is what the doj actually cares about: steal money from plebs (FTX) -- "a ok, great work"; let some plebs trade shitcoins without first providing blood sample and retinal scan (binance) -- "money laundering!"
asciilifeform: likely binance was in front of queue to chopping block for some time nao -- possib. it didn't have a conveyor of 'donation' dough to dnc
awt[asciilifeform]: I suspect Bankman will also be prosecuted.
asciilifeform: awt: possibly, but karpeles-style 'catch&release'
awt[asciilifeform]: I don't know if ftx even qualifies as a gox. Doesn't fit into the waterfal model. They don't have any btc to crash the market with.
awt[asciilifeform]: Unrelatedly I gotta say ChatGPT is proving to be an interesting competitor to google in terms of figuring out how to get lang A to do XYZ.
dulapbot: (asciilifeform) 2022-12-12 mats: dunno why binance keeps getting referred to as being inside chinese jurisdiction
asciilifeform: << near as can tell, all that's req'd to crash market is a reveal of 'we have n < m btc' where m is claimed qty. and n can be 0
bitbot[asciilifeform]: Logged on 2022-12-12 15:15:48 awt: I don't know if ftx even qualifies as a gox. Doesn't fit into the waterfal model. They don't have any btc to crash the market with.
billymg[asciilifeform]: << it's more like, who's the actual sovereign that an individual/company/country resolves to. if he's under canada then that resolves to usg
dulapbot: (asciilifeform) 2022-12-12 mats: i guess it works if you assume all people with chinamen names are chinese vassals
billymg[asciilifeform]: from my perspective can only resolve to one of three (usg, russia, china)
billymg[asciilifeform]: awt: seems like a handy stack overflow replacement
asciilifeform: if mats correct -- neither the co nor its fuhrer in cn
asciilifeform: billymg: the text dun appear to be cribbed verbatim from overflow
billymg[asciilifeform]: canada is not a sovereign, cz is not a sovereign (no army)
asciilifeform: (possibly -- paraphrased)
asciilifeform tried the linked chatbot, but went away empty-handed, 'we're at capacity, come back laters'
billymg[asciilifeform]: asciilifeform: meant it could be used as an SO replacement as in, ask it question instead of SO
asciilifeform: possibly
asciilifeform: billymg: there are gnarly edge cases (e.g. possibly turkey)
asciilifeform: for that matter, venezuela with its micro-army which nonetheless made short work of 'democracy-spreaders' coupla yrs ago
asciilifeform: ( or -- iran, similarly )
billymg[asciilifeform]: perhaps cz has his own way of not getting "stopped at airport" but i always assumed it was because someone up the chain (xi? biden?) could pick up the phone on his behalf
billymg[asciilifeform]: perhaps he has his own personal network of spies and hitmen, a la mp, and is 'tru sovereign'
phf[asciilifeform]: ah hmm, bitdash is not actually up to date with #a
phf[asciilifeform]: ftr, link replacement was added to btcbase on account of kako #b-a shenanigans, at some point clean cut made sense, consider that btcbase was superior in many ways to old #b-a
phf[asciilifeform]: but link replacement when you have multiple parallel logs running is kind of iffy
phf[asciilifeform]: which also reminds me, since this was never brought up, but is ownder my mp, and is going to expire on 2025-04
phf[asciilifeform]: so will have to send it off at sea in less than two years
phf[asciilifeform]: maybe hannah has access to that account, but i'm not sure if i should bother her with such a trifle
phf[asciilifeform]: and in something complete different, is there enough theoretical machinery in the protocol at this moment for there to be a self heal, when peers switch ips or otherwise go down
dulapbot: (asciilifeform) 2022-12-07 unpx: I closed pest. I do not have time to look after it every time a peer link breaks.
phf[asciilifeform]: i just don't quite remember. i feel like there's some kind of mechanism to ensure that AT gets updated, when peer reconnects and announces itself
signpost[asciilifeform]: and ftr I still have an active peering with unpx so I don't know why he's being bitchy
signpost[asciilifeform]: this isn't comcast technical support.
billymg[asciilifeform]: phf, yeah, it was working at one point when dulapbot and bitbot were perfectly in sync with #a. never quite worked with #pest but haven't yet implemented the exception. at this point should probably disable for #a logs as well, since i've been less diligent about restarting my logger over there
signpost[asciilifeform]: iirc the last person with whom I added a peering had my updated IP from addrcast faster than he put in the AT command
signpost[asciilifeform]: not saying there isn't some bug, but theoretically the more peerings someone has the more likely they are to be resilient, I'd think.
signpost[asciilifeform]: re: hannah doesn't hurt to ask, but at some point we just start farting out "DNS" messages via our pest stations. dunno there's any reason to keep a domain aside nostalgia
phf[asciilifeform]: ostensibly problem only arrises when "my pest station went down, i haven't check on it for a few days, meanwhile signpost switched his ip deliberately. there's no way for the two of us to find each other without and addrcast"
signpost[asciilifeform]: yeah and we have no mutual friends situation
asciilifeform: phf: addrcast & prod, but atm not fully worx ( partly b/c not erryone on latest ver. of blatta (nfi whether all worx in smalpest) ) partly on acct of symmetric NATs and 'hammer' not yet exists in blatta
asciilifeform: phf: theoretically in a pestron 100% to new spec, won't need to manually massage AT after init. peering, oughta self-heal
asciilifeform: (but -- remains to be seen how well 'hammer' worx in practice)
bitbot[asciilifeform]: Logged on 2022-12-12 16:17:12 phf[awt]: so will have to send it off at sea in less than two years
bitbot[asciilifeform]: Logged on 2022-11-29 10:05:40 asciilifeform[jonsykkel|deedbot|awt]: in other oddities: namecheap 'oopsed' '' dns : jurov had transferred it to asciilifeform's acct in '21 ( along with '', which still worx ) but recently 'untransfered' (??!) and nao again seems to point to jurov's long
asciilifeform: ideally at some pt we'll have this and can 'send off at sea' most of the dns crud.
dulapbot: (asciilifeform) 2022-04-01 asciilifeform: what's needed is http over pest, where can fetch e.g. http://localhost:1337/asciilifeform/ and it'll work for so long as asciilifeform is in yer l_n (for some n)
asciilifeform for 1 is pretty tired of paying the dns racketeers.
phf[asciilifeform]: signpost, ambassadorial reasons :D
phf[asciilifeform]: oughtta "lock"
asciilifeform: << the wwwtronic logs, asciilifeform expects, will go away once a standard pestron knows how to serve up its log on 8080 or watnot; and knows how to 'reply to msg' using netchain
bitbot[asciilifeform]: Logged on 2022-12-12 16:12:02 phf[awt]: but link replacement when you have multiple parallel logs running is kind of iffy
asciilifeform: the irc emulation thing was a 'training wheels' thing, imho, ought not to stay around
phf[asciilifeform]: hmm, i need to add multipeering. i've been losing packets from time to time, and then i get stuck in buffer.
phf[asciilifeform]: i suspect logs will stay around. stations go down, bugs surface, vex and mats reading www only, etc.
asciilifeform: they can read a pestron-generated log neh
asciilifeform will stand one up in place of dulapbot station once such thing avail.
asciilifeform: and iirc phf had sumthing in the way of a prototype www gate
asciilifeform: pestron-powered log will properly refill self if goes up/down etc
asciilifeform: (unlike the current legacy abominations)
phf[asciilifeform]: << that's presently unspecced, right? also how does it distinguish between "parent" and "reply"?
asciilifeform: atm not distinguishes.
phf[asciilifeform]: hmm, packet loss again..
bitbot[asciilifeform]: Logged on 2022-12-12 16:40:18 asciilifeform[5]: << the wwwtronic logs, asciilifeform expects, will go away once a standard pestron knows how to serve up its log on 8080 or watnot; and knows how to 'reply to msg' using netchain
asciilifeform: ( how to distinguish -- and whether -- is currently open q )
asciilifeform must bbl
phf[asciilifeform]: i was thinking of standing up a111 just so that i can do something like ``13CCB22822884 << hello, world`` and a111 quoting whatever's in 13cc..
phf[asciilifeform]: right now all these inline log…/pest/date#<random number> are basically information loss. once corresponding loggers go down no easy way to recover that info
phf[asciilifeform]: actually i'm wrong. can probably do fuzzy match against the *bot responses
bitbot[asciilifeform]: Logged on 2022-12-12 16:38:16 asciilifeform[4]: for 1 is pretty tired of paying the dns racketeers.
bitbot[asciilifeform]: Logged on 2022-11-15 11:58:41 bitbot: (asciilifeform) 2022-11-15 lobbes: Along the lines of letting my tools rust, I let expire and some chinese squatter has gobbled it up. My blog still lives, however, at my old domain name (this one I renewed until 2027):
← 2022-12-11 | 2022-12-13 →