107300+ entries in 0.062s
ckang: but
takes much less watts
to start producing
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.
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
a111: Logged on 2018-04-17 20:03 douchebag: Yeah, can you believe last year I had
to
take a QBasic 4.5 class
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: in short, i don't
think esltards even vaguely remember YOU CAN DO
THINGS.
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...."
a111: Logged on 2018-04-17 19:46 douchebag: I
think
that's really awesome way how you do withdrawls
though
lobbesbot: mircea_popescu:
The operation succeeded.
a111: Logged on 2018-04-17 15:01 mircea_popescu: you will roux
the day!
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
ascii_lander ended up N
times with broken copy of gentoo and no way
to determine why other
than exhaustive grunting
ascii_lander: phunphakt : when you give 'exclude' option
to
tar, it excludes RECURSIVELY all files having
that name, regardless of depth.
this cost us 6 or so hrs
today.
trinque: hopefully
that'll be enough fiddling
to let me get back
to migrating
to pizarro, BingoBoingo !
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.
lobbes will gladly
test a phf-made eulora
text 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
☟︎ a111: Logged on 2018-04-17 17:55 mircea_popescu: diana_coman, one consideration was
that if it includes pubkey it will have
to be multipacket and i wanted it
to be singlepacket for some now incomprehensible reason.
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"
☝︎ douchebag: Yeah, can you believe last year I had
to
take a QBasic 4.5 class
☟︎ trinque: after
that somebody bought me a "make your own game!" basic interpreter of some sort
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?
douchebag: Yeah no problem, glad I could bring
that
to your attention
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")
douchebag: I
think
that's really awesome way how you do withdrawls
though
☟︎ 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
douchebag: Hey
trinque I don't mean
to bother you, but with
the various deedbot issues
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
diana_coman: I'll eat
the convo again and
then update
the spec (+link
to log ofc) hopefully
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: i know
this isn't how it works now and hasn't been for a long
time, but i'm ready
to move on!!1
diana_coman: but
to my earlier obs: so you're fine with people creating account with any rsa key (well,
tmsr/eucrypt rsa at least) ?
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: diana_coman, one consideration was
that if it includes pubkey it will have
to be multipacket and i wanted it
to be singlepacket for some now incomprehensible reason.
☟︎ 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: i don't have
this modelled well enough
to say it with certainty ; but it seems
to me 3 is a reasonable choice.
mircea_popescu: diana_coman, kinda 90% of all server code aims
to avoid "accidental client ddos".
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: but if you want less
than 3, it'll keep sending you extras until you give up
trying
to argue with my server.
mircea_popescu: you can send as many as you want,
the server will keep
them for you.
diana_coman: so server sets
threshold at 3; why can't I decide I want
that at 2 and you at 5 and so on
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.
diana_coman: but why does
the server *care*?
to spare
the client
the need
to ask or what?
diana_coman: but if you don't know
that you don't have...
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 .