trinque: meanwhile Poka_ says to himself "b-but I had theorems to share!"
mircea_popescu: yeah, i noticed this, given present supply of pot the herbivores really need encouragement.
mircea_popescu: i suspect that's the driver, people couldn't get enough of bad talk radio and commutes.
mircea_popescu: trinque, discord being an audio channel, it dun encourage much more conversation than its forerunner, the car radio.
trinque: these creatures must be monosyllabic on "discord"
mircea_popescu: phf, not really drunk as such. it's either the plum thing, or else the sour cherry thing, basically. not really herbing.
phf: mircea_popescu: that's the romanian word for nastoyka? i know polaks calls it nalewka
douchebag: me neither
phf: a friend solved the problem of sourcing proper alcohol for nastoyka here by working at NIH.
mircea_popescu: ckang, ppl do actually, many older folk own a quarter acre of plumtrees or so, make their own 45-52% "tuica".
phf: everyone has their own special "nastoyka"
mircea_popescu: i suppose you could get a custom made resistor + multi-spot thermometers and push a point.
mircea_popescu: copper stills are great for taking mash (0.x - 7% or so alcohol) to spirit (30-40% or so). they're terrible for trying the 30-50% to 95% part.
mircea_popescu: ckang, yes, but that's too calorically bulky to work for the proposed use here.
ckang: these are a pretty good value overall
phf: it's a question of perception though, i'm commenting on the mechanics of learned helplessness
mircea_popescu: also it's not properly production, merely fractional distillation of last pass. you're just taking the BBAV/BAC/whatever shitstilleries out of your cup.
mircea_popescu: it won't make commercial amounts, but even the smallest still can outpour your gullet.
ckang: in general they wont really mess with you unless you are selling and being 'loud'
phf: i think alcohol production is forbidden in u.s. by a divine inca decree, so there's only two ways of doing it, in a redneck bathtub, while being redneck, or using hadron collider, like a civilized store alcohol supplier.
a111: Logged on 2018-04-18 00:59 phf: lobbes: same for me, i don't have the right machine to eulora. i tried rebuilding my mac homebrew version recently and it's all kinds of broken since the update a year or so ago
a111: Logged on 2018-04-17 20:39 diana_coman: and at any rate, we end up with a "hello" packet that is the first one, containing version of comms protocol and client id string and all that jazz but *at most* some bits of the key only, followed by... more packets with the remaining, chopped-up public rsa key
mircea_popescu: http://btcbase.org/log/2018-04-17#1801151 << myeah. there's no way out of it, helo packet will have to be multi-packet. sad but true.
mircea_popescu: http://btcbase.org/log/2018-04-17#1801146 << the reason teachers keep pushing wirth's abomination upon students is that they're trying to teach them ada but don't know the word for it.
a111: Logged on 2018-04-17 19:55 trinque: clicked in my head that "oh, *this* is what the computer is for. change the text, and it does something different."
mircea_popescu: http://btcbase.org/log/2018-04-17#1801142 << pretty great story. not to mention the obvious moral : "are you ruining your child's chances to a future by failing to provide a safe learning environment for him through your limp wristed inability to create a clear and present threat to violent bodily harm ?"
mircea_popescu: put it in oj or w/e. but this apparently was divine intervention, half hour's labour worth of parts and half hour's worth of work assembling them together.
mircea_popescu: what fucking divine intervention, a still is $15 in household equipment, get one of those rice cookers or w/e pot warmers, wirth digital temperature adjustment. set it for 79C, stick an erlenmeyer glass in there with a cork and a bent tube coming out, put an ice pack over the tube and voila! whatever southern confort goes in, 195 or so proof alcohol comes out.
mircea_popescu: no further than earlier over coffee, girl proposed that during her stay in $us.shithole she "tried getting into beer" because well... gotta have an activity and there was no good alcohool available, except for this beer that didn't utterly suck. so i said, "why not make a still", and she said "baring divine intervention...."
mircea_popescu: http://btcbase.org/log/2018-04-17#1801135 >> maybe actually putting a blogpost up with a detailed and illustrated description of the process might be a good idea, both for deedbot and for tmsr in general. i don't think many people even realise security is a thing.
lobbesbot: mircea_popescu: The operation succeeded.
a111: Logged on 2018-04-17 15:01 mircea_popescu: you will roux the day!
lobbes: listen, I'm gonna have to put you under a roast for punishing the logs with these puny puns >> http://btcbase.org/log/2018-04-17#1800942
phf: lobbes: same for me, i don't have the right machine to eulora. i tried rebuilding my mac homebrew version recently and it's all kinds of broken since the update a year or so ago
ascii_lander bbl, had vehehehery long day down here in the bunker
BingoBoingo: The grunting was loud
ascii_lander ended up N times with broken copy of gentoo and no way to determine why other than exhaustive grunting
trinque: ok, thing's back up and I'm getting quite a bit more speed from the pipe.
lobbes: main thing putting me off from playing more frequently has been the graphics requirement.
phf: http://btcbase.org/log/2018-04-17#1800966 << i'll start reading the spec, i was already planning on writing my own version of client
diana_coman: alternatively the hello message stays single-packet and uses a keccak hash of the public key (n,e,comment) as "account ID" so 3.1.5; then key is sent via Data packages and basically I need to define another type for RSA public key; server can ask/expect the RSA key *every time* to preserve same answer behaviour or otherwise only if it doesn't know the key
diana_coman: and at any rate, we end up with a "hello" packet that is the first one, containing version of comms protocol and client id string and all that jazz but *at most* some bits of the key only, followed by... more packets with the remaining, chopped-up public rsa key
diana_coman: http://btcbase.org/log/2018-04-17#1801097 <- mircea_popescu looking at it again from all sides I think the consideration is not necessarily misplaced in itself i.e. multi-packet there does make a mess out of the neat "these are the only *packets* you may ever send"; this being said though, I don't quite see the solution that would *also* preserve the desired "whatever it is, server responds the same: with a set of X keys"
trinque: that's about it, really. pretty african origin story compared to the 80s kids
trinque: clicked in my head that "oh, *this* is what the computer is for. change the text, and it does something different."
trinque: mmm, got my dad's computer stuck in DOS back in the win95 days playing a game. I was about 7-8? he was away on a trip, so I had 2 days to "fix the computer" or certain asswhippin. found the thing in win.ini or w/e it was, changed it, avoided wrath.
douchebag: So trinque, what is it exactly that got you interested in programming/networking/sysadmin stuff? What sort of things interested you the most and motivated you to keep learning?
trinque: well and I have to admit that leaning on it exposed that the !!register service was weak (albeit weak meaning "couldn't survive 10kbps wire with packet loss")
trinque: the !!pay wasn't broken, just !!balance and !!withdraw
trinque: I have 7 in the hopper for this evening.
douchebag: I was just making sure withdrawls for those girls yesterday went through properly - no rush getting them processed
trinque: deedbot will be offline briefly as the DC fixes its networking situation
mircea_popescu: yes. but hey, this is precisely why god gave us blogs in the first place.
diana_coman: certainly; and it goes for the data types too; fwiw I wasn't keen on putting this up precisely because it's a bit in the air as it stands and I expect other issues to emerge at implementation time
mircea_popescu: aite. i really think we have to have someone working at this wall from the other end, hence the original http://btcbase.org/log/2018-04-17#1800966 comment.
diana_coman: otherwise there isn't any hello as such, just send directly whatever it wants/needs, encrypted with one of the X keys and that's that
diana_coman: well yes, it is only one, the "hello-new-account" although whether it's "old" or "new"...same difference
mircea_popescu: re "registered with deedbot" part : i expect in-game trade should be the driver of both rating and registration.
mircea_popescu: im thinking it's actually best to have a single helo, with r-pubkey. if it is known to the server then it sends X keys ; if it is not known then... it sends X keys.
diana_coman: ok, so then there is hello-new-account with the R public key; there are otherwise *only* X messages? and if no X key then ...account lost or can it re-send "new account" and basically retrieve the old one?
mircea_popescu: yeah. it's the only sane identifier to be had.
mircea_popescu: but no, seems the correct approach is to replace 3.1.5 with "rsa pubkey". and ACTUALLY use that as the account id.
mircea_popescu: (it does away with the "is user logged in". you can pm everyone all the time, they're always logged in anyway).
diana_coman: so it's not enough that client plonks a key in there
diana_coman: re creating account: it obviously needs the client's public rsa and atm that one is nowhere in there, yes; I thought you didn't want them in there because it's not just about "a rsa key" but rather one registered with deedbot sort of thing
mircea_popescu: (for the oursiders : it is the agreement in minigame boardroom that rsa helo packets from existing clients will be lowest priority, after 1. serpent packets and 2. rsa helo packets from unknown clients. the idea is you keep your serpent keys, and continue your "session" whenever, it's kind of a stateless session)\
diana_coman: uhm, dunno about that certainty there; maybe client doesn't want to keep serpent keys between sessions for all I know
mircea_popescu: yes, but here's the principle : if server knows something will be needed as a certainty, server should act rather than wait to be called to act. which is why it's a server rather than a client.
diana_coman: I'm still not convinced it has to be; if it gets lower than 1 and client hasn't asked, I'd just disconnect them and they can get back with a hello that is low priority and they..w.ait
diana_coman: well, it's certainly not the number I have a problem with anyway
mircea_popescu: seems to me the threshold will practically be set at 1 as a matter of absolute necessity. once that is the case, setting it at 3 is in no substantial way different : just as many keys will be used as before, but the setting at 3 forces key creation at a time prior to when keys are needed, which seems to help with resource load spread.
diana_coman: server wants to look after clients so they don't end up without keys; it can, sure; all I'm saying is that I don't quite see the reason for this; perhaps other than "clients are idiots, let's at least avoid the case where they end up going hello hello all the time"
mircea_popescu: because it's stuck keeping a list of keys anyway. so it knows how many they are anyway. so might as well send when needed rather than wait to be asked.
mircea_popescu: how could the server not know ?
mircea_popescu: but basically the idea for X keys is to work like that, if you don't have any server makes, if you make them then server uses .
diana_coman: I don't quite follow why is server concerned with client's stock of X keys? client can request new keys, burn them, do whatever it wants as it decides how often it wants new keys
diana_coman: ugh, meant X there
mircea_popescu: X keys only ; R key is one. and server is concerned because if it has no client X keys, it can't send, and if the client has no server X keys, the server can't receive.
diana_coman: I don't quite follow why is server concerned with client's stock of R keys? client can request new keys, burn them, do whatever it wants as it decides how often it wants new keys
mircea_popescu: diana_coman, in any case strictly speaking, the helo as we spec it does not include R pubkey ; whereas in practice it actually must. but read the whole blob, this is better compiled htan parsed.
diana_coman: ah, you mean the same but just id vs no id?
diana_coman: the idea was that if client loses all his X keys, he can send a hello message again
a111: Logged on 2018-04-17 16:50 mircea_popescu: at this juncture, server knows "someone" claiming to be A initiated a connection. it should therefore send X(answer) back, where X uses a key that S knows A should have, on the basis of previous comms.
diana_coman: http://btcbase.org/log/2018-04-17#1801027 --> uhm, for starters this is not correct; initial hello is meant for....initial, no "previous comms" wtf; server needs to reply not with X(answer) but with R(answer) and yes, it needs to know the public rsa key of the account; the creation of accts is still a bit in the air as server needs to get somehow the public key
mircea_popescu: now obviously, this approach wouldn't be nearly as useful for dynamically linked clients ; but i deem the fact that it puts the security incentive on dumping dynamic linking a very good thing.
mircea_popescu: (one could object, "it's pointless to attempt this, hacked client can just replace magic string", which is true, but nevertheless client can still binary audit his item and see / login with a special, known-good string-test-only client and see what he should be. ie, client can bootstrap himself out of the fakebox produced by a hacked binary.
mircea_popescu: the reason for this is that games are eminently a domain where people share binaries, a matter of fact established both from general and minigame's own experience. obviously in the sane world of source sharing, v is the correct solution. but if people are going to share binaries, this seems like the only available approach.
mircea_popescu: now here's a question on which i'd very much like to hear a lordship oppinion. so, the model currently contemplated for eulora includes a bit whereby the server has to be told by the client a magic string, and will report this back to the client on demand, "here's what you told me you are". the idea is that the client can then sha his binary, and see if the strings match.
ascii_lander reporting live from... inside the cage. fixed the raid oops on smg box; nao partitioning it & copying dulap's gentoo
mircea_popescu: also important, third question : should the client be permitted to generate X keys for the server ?
mircea_popescu: now subsidiary for all this : server should generate a batch of X keys and send them to the client every time its store of either S or C X keys drops under a certain value. it's therefore the client responsibility to make sure there's enough keys in store if it doesn't want to pay for key generation. now, what should this threshold be ? 3 ?
mircea_popescu: like this, server must not lose its R privkey and clients must not lose their R privkey , but pubkeys of all these can be safely lost, and X keys don't matter at all. seems altogether safer and less friable.
mircea_popescu: if instead we made it rely on R, there'd be great benefits. consider this alternate model : C : R(hi, this is C.R.key) S : R(here's some X keys for me and for you) C:(actually i'd rather you use these X keys for me).
mircea_popescu: which then runs into the obvious problem that i had been chasing all this time : client's R key has to come earlier in the flux. how about the rule that all hello items sent to the server are either a) encrypted to a pre-existing X key or else b) contain a R key ? ie, our helo is not correct as specced.
mircea_popescu: this is then the eulora future login handshake : C : hello ; S : new account, here are your keys ; C : here's some keys of mine. they can now continue indefinitely, just as long as nobody loses all the keys.
mircea_popescu: so implementations MUST keep at least a local and a server X key at all times ; doing otherwise is === deleting the account.
mircea_popescu: now, if B wants to update his X.keys with the server, he sends them X'd with one of the existing S keys. meaning, again, that if B manages to lose all S's X keys, it lost the account.
mircea_popescu: if A fails to respond, S will close the connection, practically meaning that A can't claim to be A unless he keeps some X keys about. which is something A-implementers must be aware of.
mircea_popescu: at this juncture, server knows "someone" claiming to be A initiated a connection. it should therefore send X(answer) back, where X uses a key that S knows A should have, on the basis of previous comms.
mircea_popescu: diana_coman, this is too fluid to fix in a comment, and i'd rather have it here than in #eulora. so : let's call eucrypt.serpent X and eucrypt.RSA-OAEP R. now, 1. client wants to log in, R(hello) -> S[erver].
spyked: aha, found nothing on hardware and software specs. mircea_popescu, if it's any similar to the calculators I had as a kid, it might not even have any software (all calculator logic implemented using gates)
mircea_popescu: the confounding factor here is pantsuitist outlook, whereby some retard (the user) regards self as meausre of all things and imagines all vectors start from him, and therefore in his boneheaded approach to the world, "general purpose os" means something about him. it fucking doesn't, a general purpose os isn't one joe schcmucktoe can put on a stick and carry around and "it'll work on all computers he encounters".
mircea_popescu: because in the former case, the VARIOUS gposen would still be in fact different from each other.
mircea_popescu: it all comes down to WHAT is the special purpose. mind that the direction the bitcoin node os is taking is towards ~special purpose hardware~. this is very fucking different, whether you have special purpose hardware run by general purpose osen, or whether you have ibm at clone consumershit emulated into republican sanity by usg's flaour of special purpose os.
spyked: mircea_popescu, I don't see a fundamental problem with special-purpose os (which is why I mentioned "bitcoin node os" as one, though it *could* in principle be implemented as a particular instance of a general-purpose os). embedded hardware (e.g. requiring timing constriants) is full of them.
mircea_popescu: whereas the one user one box tmsr approach sticks with the general purpose os philosophy, and expects spurious color-of-bits considerations to be implemented in the realm in which they belong -- if you want to own the bits own the box, there shall be no legislating here.
mircea_popescu: and perhaps worthy of noting here, that the "trend" "emerging" from usg's own "computer security" roadside act cum flea circus, is towards special-purpose os. because that's what they mean by "security".
mircea_popescu: spyked, perhaps another useful heuristic is the authority problem. if the specification of a user program CAN include a MUST statement, quo warranto ? if "the os", then it is not general purpose.
mircea_popescu: spyked, cleanly ie, simplest bijective. 1. all items in A are represented in B ; 2. all items in B have an underlying in A ; 3. there is no simpler relation in any case.
a111: Logged on 2018-04-17 15:05 mircea_popescu: if however that os runs on a no-op single instruction cpu, then it is absolutely general purpose.
spyked: http://btcbase.org/log/2018-04-17#1800949 <-- could also be a turing-capable cpu that exposes the instructions natively after the program is loaded. the important part was re what the os itself exposes (or not, in this case) and how this relates to "makes no assumptions about P"
spyked: anyway, this thread put together should make for a decent follow-up piece, i'ma get to it tomorrow.
spyked: so, taking anotehr shot at this definition: a general-purpose os is an os that cleanly exposes hardware to user programs, without making assumptions about the latter. it's still not immediately clear to me what "cleanly" means, but this'll have to do.
spyked: http://btcbase.org/log/2018-04-17#1800947 <-- I deliberately left the "underneath the OS" bit out because it was not explicitly mentioned in the definition. but yes, in my question I was looking for "specificity", same that's mentioned in http://thetarpit.org/posts/y04/06d-what-is-an-os.html#selection-179.0-179.238
trinque: the singapore one of course, not pizarro.
trinque: aaaand 10-12% packet loss inside the dc
mircea_popescu: in other news, we're up to 55 titbitpairs
mircea_popescu: you don't understand the game of world politics and international intrigue of the web! you're supposed to not tell things! THERES TERRORISTS OUT THERE.
trinque: ckang: no, I'll have the deedbot keys pulled down in an hour; they'll then be able to withdraw, whoever can't
ascii_lander: but this is at the cost of 'hey i'ma eat a video card'
BingoBoingo: I just kinda forgot petrocheese was a thing with the real stuff here
BingoBoingo: Until alf arrived I had been taking the cheese versus petrocheese gulf for granted
mircea_popescu: alf the beedog happines = long walks + icecream stops.
ascii_lander: will reconnect from inside the cage.
ascii_lander: (coffee, then to dc)
ascii_lander: mircea_popescu: i'ma actually headed to the smg box shortly
mircea_popescu: ben_vulpes, sooo, did you send login details to douchebag ? what do these cost in the end ?
mircea_popescu: http://qntra.net/2018/04/21-coearn-com-saga-ends-with-coinbase-acquisition/ << aka 'usg.coinbase is the usg-designated bagholder in the space, it'll "buy" all the failed attempts of all usg agencies so the empire of idiots can "save face".'
ascii_lander: trinque: out of curiosity -- this is in a heathen dc ? usa ?
trinque: kind of a wonder it's working at all under these conditions
mircea_popescu: ped a "userland package" at all points in its existence, there's no substantial difference between "the office suite" and "windows + the office suite".
mircea_popescu: the jury is still out, as far as i'm concerned, on whether the os that loses control of a machine is still an os, meaning it's not altogether clear to me the basic-whatever combo they had at the time actually constitutes an os. but the problem FUCKING ISNT the naive perception at the time, "oh, it didn't hjave icons to click like windows 3.1". windows 3.1 was not an os ; nor was any other windows product an os. microsoft ship
mircea_popescu: (fun facts for the recently born : 1. most old zx-80 clone programs were games, whether you count by titles, or by total cpu time, or any other way ; 2. they did not return (mostly because to make a good one you had to fuck the kernel space, that zx80 shit was tight), you pressed the reset button to load the next item on the tape.
mircea_popescu: exactly how medicine does not consider whether you were fashionably dressed at the moment of symptoms, to establish whether your sartorial ineptitude maybe upset Sartrus, the god of suits.
a111: Logged on 2018-04-17 09:05 spyked: call, "exit(code)", which allows P to return control to NOP-OS, so that the user can load another program P'. same question here.
mircea_popescu: http://btcbase.org/log/2018-04-17#1800914 <<< how it manages user interfacing is not even a consideration here. whether it returns control via pushing that specific-sounding button on the back left like the old tim-s ; or whether it has a software call implemented is irrelevant. not from a gui/ux perspoective, of course, but this is the fucking point of systems design as a discipline : that it does NOT consider other discipl
mircea_popescu: but instead, it would be a particular-purpose os, "for those cases when the user wants the machine to not be 3 degrees from freezing".
mircea_popescu: if you modified it so it checked whether the machine temperature is within three degrees of freezing and did not expose the no-op in THAT case, then thereby it would be a general purpose os no longer
mircea_popescu: if however that os runs on a no-op single instruction cpu, then it is absolutely general purpose.
a111: Logged on 2018-04-17 09:05 spyked: http://btcbase.org/log/2018-04-16#1799861 <-- I dun fully grasp this, so bear with me for a moment. suppose the following (imho no-nonsense) thought experiment: say we have an os, NOP-OS, that works as follows: after initialization, the os loads a (user-provided) program P; the NOP-OS interface exposes to P exactly one system call, "no-op", which does nothing and returns. is then NOP-OS a general-purpose OS? say we add another system
mircea_popescu: so what's that mean, that they were both riding dinosaurs into combat, big deal.
ascii_lander: eachother
mircea_popescu: from you you mean ? or from each other ?
ascii_lander: these 'earlies' are ~1000yr apart eh
mircea_popescu: you will roux the day!
mircea_popescu: http://btcbase.org/log/2018-04-17#1800909 << wasn't, no. and yes, the ti-89, sure. or my ancient citizen solar powered item which i haven't seen for 15 years at the least but which was revolutionary for its time and literally worked by degrees -- if you obstructed two of its cell it could still slightly power the screen so it did.
shinohai: BingoBoingo: overvalues firm / overvalues the firm ?
BingoBoingo: asciilifeform's sense of wonder here has been good for the moral. Been learning quite a bit here.
spyked: call, "exit(code)", which allows P to return control to NOP-OS, so that the user can load another program P'. same question here.
a111: Logged on 2018-04-16 15:22 mircea_popescu: whereas the proper definition of "general purpose" is the one mentioned, "which makes no assumptions about the userland".
spyked: http://btcbase.org/log/2018-04-16#1799861 <-- I dun fully grasp this, so bear with me for a moment. suppose the following (imho no-nonsense) thought experiment: say we have an os, NOP-OS, that works as follows: after initialization, the os loads a (user-provided) program P; the NOP-OS interface exposes to P exactly one system call, "no-op", which does nothing and returns. is then NOP-OS a general-purpose OS? say we add another system
mimisbrunnr: Logged on 2018-04-16 15:12 mircea_popescu: i suppose at work might be a confusion between what-some-idiots-might-be-thinking-retroconstructed-on-the-flimsy-basis-of-how-they-behave, where "general purpose os" means "the sprinkle of magic turning the computer from a computer to anything i want it to be, which is to say a tool that magicvally works for any purpose i might come up with, especially the nonsensical and self-contradic
a111: Logged on 2018-04-16 15:20 mircea_popescu: the best example i can think of is the code on the old handheld calculators. THAT is a general purpose os : it makes no assumption about the downstream, merely fully, cleanly and directly exposes the hardware.
ckang: trinque: do they need to register ?
trinque shipped a patch that'll retry fetching the key
trinque: that'd explain some of the incomplete registrations (got nick:fp pair, did not get key into wallet's keychain)
trinque: looks like there's packet loss between the wallet and deedbot, with the fault on the deedbot end.
ckang: im not a huge fan of tats, they look bad with time
ben_vulpes: ckang: mirroring tattoos on self turns the narcicissm to eleven
a111: Logged on 2018-04-16 20:03 mircea_popescu: you know, "show me the light, by all means, but later"
ckang: why would you want to read a tattoo every time you get out of the shower backwards
ckang: you do, in the mirror
trinque: kendraB: so when you were getting this tattoo, how it looked in a mirror took precedence over how it... looked as you stand there?
ckang: another for you mircea_popescu
ascii_lander: mircea_popescu: aha, then would
mircea_popescu: admitting ad absurdum that there's a large number of nodes only knowing this set of peers.
mircea_popescu: the only guarantee is you won't have outside node talking to 2 locals.
ascii_lander: which is overwhelimingly heathen
ascii_lander: if a node it tried to connect to, failed to answer, iirc it skips to a random node from the cache
mircea_popescu: so adding more nodes in bbistan helps, somewhat. it doesn't help the pipe, but it spreads the load among boxes.
mircea_popescu: resulting in this situation where if a large k nodes wnat to talk to the n group, each node in the n group will see k/n inbound connections on average.
mircea_popescu: so they just pick one local node.
mircea_popescu: trinque, im not even sure it's so bad. spreads the load.
trinque will have a synced node in there before long
ascii_lander: mircea_popescu: yea verily, this is possibly the 1 commonplace thing where they definitely won't shine
lobbes: well, she'd have had to write either the string or have had the tattoo mirrored when creating
ascii_lander: 217G total mass of the dir.
ascii_lander: as for only the bloxx -- mine weigh 150+G
mircea_popescu: lobbes, ascii_lander the blockchain isn't even 50gb yet. so it'll work for years.
kendraB: I wrote around the tattoo
ascii_lander: but 1) rockchip will prolly never be an idea trb box 2) wakeup folx installing 77th trb in the rack ! trb dun do much good with N nodez hanging off 1 fiber.
ascii_lander: http://btcbase.org/log/2018-04-17#1800708 << the stock disk is 128GB, lobbes , toosmall for trb
a111: Logged on 2018-04-16 20:24 danielpbarron: right now i'm trying to figure out why the pretty urls thing broke my edit-post thing to where the handy "insert link/blockquote" buttons disappeared
esthlos: hanbot et al: my mp-wp seems borked: when trying to make a new post, the "tab" to switch to raw HTML is greyed out and does nothing, and HTML tags are ignored. Also, the visual editing features aren't showing at all. Any ideas?
deedbot: mod6 unrated thestringpuller.
deedbot: mod6 updated rating of mike_c from 3 to 1 << Met IRL. Former Lord, off doing other things.
deedbot: mod6 updated rating of danielpbarron from 2 to 3 << The learned Trishop
deedbot: mod6 updated rating of trinque from 3 to 4 << Master of the Rolls, deedbot
deedbot: mod6 updated rating of jurov from 4 to 4 << Three years of service as The Bitcoin Foundation Treasurer
deedbot: mod6 updated rating of hanbot from 4 to 4 << Met IRL. The Lady Falconeer, Tester of all things TMSR~
deedbot: mod6 updated rating of ben_vulpes from 5 to 5 << Met IRL. The Lord of the Well, Bitcoin Foundation Co-Chair, Pizarro Manager
deedbot: mod6 updated rating of mircea_popescu from 6 to 6 << Met IRL. MPEx, Trilema, S.NSA, S.MG: Father of The Most Serene Republic.
mod6: Here comes the flood.
trinque would stare at the thing the whole time, eventually lost interest. "that ain't coming off or getting covered"
trinque: when american goes bad it goes allthewaybad
mircea_popescu: trinque, theoretically women are more clustered towards the mediocre. in practice however...
lobbes: my current trb box I'm planning to run at home is a mystery box someone gave me; troubleshooting all the hardware issues I keep uncovering are delaying things. Would be nice to have two eventually anyhow
mimisbrunnr: Logged on 2018-04-08 04:28 PeterL: Oh, I see the question got asked but I don't see an answer in the logs? http://logs.bvulpes.com/pizarro?d=2018-4-8#327411
ascii_lander: once i can get hold of a bootable-sumthing that knows about the raid.
ascii_lander: we now adjourn for the evening, rack-wise, gotta eat, sleep
ascii_lander: we will at some point post photos of, e.g., rooftop at night where we drmengele'd the mains distributor panel bought from orcshop
ascii_lander: let's move the proceeding to #p
trinque: then not routing from outside world?
ascii_lander: aaaaaaand the rockchippen are live
ascii_lander: aaaaaaand reporting live from inside the fuckin' rack!!
lobbes esp. loved the parallel running convos of mp/wiresharkguy with mp/atruechurchguy
douchebag: don't mean to bother you, just reminding
ben_vulpes: probably same programs that harp on quantum decryption and steadfastly ignore their own failures to produce constanttime encryptulators.
ben_vulpes: https://gizmodo.com/meet-the-woman-who-leads-nightwatch-google-s-internal-1825227132 << haw haw, google 'cmu alum' attempts to get homomorphic encryption into production, discovers upon review by people who actually write instead of wank^H^Hx theoretic that it'd take more horsepower than google has worldwide
mircea_popescu: nah, don't pester the guy.
mircea_popescu: seemed to me the interplay was actually productive.
mircea_popescu: danielpbarron, so is it your inference the wireguard fellow got bothered by the wrongness of it all / jealous / whatever ?
mircea_popescu: is it thatbitchlola or different girl altogether ?
mircea_popescu: aite, we'll see what trinque says about this when he has a moment. in the meanwhile Melissalmao Brittt dun fret, your cents are safe.
mircea_popescu: douchebag, somewhat suspicious, as it told me "<deedbot> mircea_popescu paid Melissalmao 0.02". is their key no good or something ?
douchebag: mircea_popescu: I think it's worth mentioning that both Melissalmao and Brittt are recieving the same issue with deedbot as earlier
mircea_popescu: so basically it's like an arthouse/halfwayhouse w/e, there's a bunch of you girls living together and trying to make ends meet ?
Melissalmao: well no amount in particular we pay for eachothers shit though
mircea_popescu was always impressed by how similar really devout religious people, doing the whole purity thing, and really dedicated whores, doing the whole thing, drugs etc actually are.
Melissalmao: it goes on until the phone stops ringing its a hell of a lifestyle
mircea_popescu: but besides that ? or is it one of those things, like being religious, takes up the whole day.
mircea_popescu: a blurry gaze for the books, huh.
mircea_popescu: let's try and get the first one right shall we!
ascii_lander discovered that some things take a while in orcistan: hour march to get to cable shop, plodding behind flocks of zombies, then hr back..