87400+ entries in 0.079s
phf: asciilifeform: well,
that would be one of
the reasons why "hasher gotta be hardwired". vtools give you hard guarantees about
the format of
the patch,
the state of
the press,
that can actually be manipulated outside of unix soup
mircea_popescu: or if we actually
took ourselves seriously enough
to get rid of
the dumb shit.
phf: i've been using vpatch/vdiff without full blown v, because i can order
the patches by hand (and
there's now an explicit ordering provided by manifest), and vpatch verifies
the hashes for me. it would be handy if i could also press existing sha patches with `vpatch -a sha` or whatever
☟︎ BingoBoingo: <mircea_popescu> and what's
the point of not shooting said maid needn't be answered because maid-council established "you couldn't do
that", and what maid council establishes fucking goes, or what. << Plan seems
to be fuck off and leave confused maid and maid council behind
phf: now
the reason i kept
the branches separate is because i was expecting a rapid switch
to keccak as soon as one's available, so
the need
to deal with sha patches would've been rare.
that's not
the case, and i want
to have similar functionality available for both sha and keccak until
there's no more active sha patches in
the wild.
mircea_popescu: and what's
the point of not shooting said maid needn't be answered because maid-council established "you couldn't do
that", and what maid council establishes fucking goes, or what.
BingoBoingo: The latest news out of Venezuela is
that
the Maid won't reliably show up
to work because Maduro is handing out free food, and what's
the point of working when
there's food handouts
mircea_popescu: i didn't realise
there's disadvantages
to a gnat system
esthlos: I'm going
to
think of how
to proceed and blog
the reasoning
esthlos: very interesting,
thanks diana_coman and mircea_popescu
mircea_popescu: "should #1477 [bit of privkey] be
true or false ?" === "do i x or y in situation z"
mircea_popescu: it's
the direct equivalent of a key, actually. if you regard a rsa key as "a succession of 2048 binary questions"
to which one gives exactly correct answers ;
then ~choices you make~ are ultimately
the basis of identity.
mircea_popescu: the above especially. whole
thing works just like eulora price formation, gotta have some sort of reasoning
to back you up.
diana_coman: esthlos, measure 10
times, cut once and esp... know why you chose whatever you chose
esthlos: gah. hope I don't suck,
then
mircea_popescu: i ain't gonna make
them for you, even if you
turn out
to suck at it.
mircea_popescu: esthlos welcome
to
the mechanisms of lordship. it's your project, it's your job
to make
this sort of decisions. "should
this be rewritten in lisp, imported in ada, be
turned into a point of grafting on eucrypt
tree ?"
☟︎ diana_coman: it can't hurt
to have a lisp implementation of keccak
too imo
esthlos: but if it's desired for entire
thing
to be lisp,
then yeah
diana_coman: esthlos,
the fix is literally one line +
test of
the issue
diana_coman: alternatively you can press
to ch9 and
then add
the fix on
top I guess
diana_coman: esthlos, you can compile it standalone but indeed because of
the bitrate fix you'll need
to patch all
the way
to
that at least so getting everything in
mircea_popescu: esthlos of course, if your whole
thing is lisp,
the utility of ada keccak may be limited ?
esthlos: if standalone is difficult due
to eucrypt_keccak_bitrate_fix,
then I'll plan
to copy code
mircea_popescu: this has nothing
to do with
the particularls, not you, nor
the project etc ; it's just how it goes, either way 1 or way 2.
mircea_popescu: or else you copy over
the code you want
to use into your own
tree.
mircea_popescu: i'm not suggesting either ; i'm just saying
that you have
two ways you could proceed. either identify among
the code you wish
to reuse a
tree
to nestle among, and
then your vtron would be an eucrypt downstream item, or a phf vtron item or whatever you pick ;
esthlos: right. but are you suggesting
to pull in all of eucrypt, including mpi, etc.?
mircea_popescu: esthlos if you patch ~off~ of eucrypt your whole
thing becomes a patchset.
esthlos: trying
to figure out what patch I can base
the press from
to get keccak. seems like its eucrypt_keccak_birate_fix, but
that pulls in
the other components according
to
the graph
mircea_popescu: "da fuck ? you
told me warm ?!" "yes well...
that was
then. what, you
think medical science made no progress in
the interval ?"
mircea_popescu: months pass,
the
two meet socially. "how goes ?" "i got divorced" "how come ?" "wife -- annoying" "but
there's medical cures for
that!" "oh, i
tried warm compresses
till i was black and blue from it" "no, not warm. cold."
mircea_popescu: guy goes
to doctor, "doc, my wife is annoying". so doctor recommends warm compresses,
to be placed on
the annoying parts.
mircea_popescu: hey, gotta account for
technological progress since 2014.
mircea_popescu: esthlos
there's an eucrypt keccak you can either import (by patching off eucrypt) or copy over (as a different patch).
esthlos: so
two
things I see are: 1. what
to do for hasher? somehow integrate phf's item into my vtron? 2. what do
to for diff/patch? lisp McIlroy?
mircea_popescu: now, shelling out
to diff / patch is one
thing (though somewhat iffy for reasons discussed in a long
thread, which phf mostly fixed). but shelling out
to hasher is no longer possible because keccak implementation isn't shell.
a111: Logged on 2018-07-07 11:40 spyked: btw
trinque, I'm getting back
to
trilemabot-works next week, so I can do
the regrind after
trilemabot part ii if
that's
too deep in your queue.
mircea_popescu: trinque
the idea is
to get a definitive item, does everything.
mircea_popescu: esthlos genesis ~never needs redoing. it's a purely administrative decision,
to regrind, dun sweat it.
esthlos: additionally, before I make another mistake, does
this warrant redoing
the genesis (because original item is broken?), or a new patch?
trinque: is
the
task for esthlos here
to produce a patch util
that cares about hashes, or
to build all patching functionality into
the vtron ?
mircea_popescu: gotta check
that
the
trusted (as established by sigs)
transformation is applied on a) what it expects
to be applied and b)
the provided
transformation ~actually matches~
the described
transformation
that was
trusted.
esthlos: asciilifeform:
this is 100%
true. I need some adult supervision. kinda why I'm here
mircea_popescu: and b) you're applying "fuck you()" on
the expectation it hashes as "pupcakes and soda cop"
mircea_popescu: esthlos exactly. for all you know a) you're applying patches on
the wrong fileset, resulting in a broken / uncompilable pile
a111: Logged on 2016-09-08 15:31 mircea_popescu: ie, young brazillian chick WILL have
to have her cooking checked for shit, because apparently wash hands is not universally comprehended in brazil.
esthlos: ah wait, so sig is "I place my
trust in
this
transformation", but I didn't check initial conditions, did I?
mircea_popescu: and change how you
think.
the whole point of even having any of
this is
to have all of it.
esthlos: ok, I'll get on fixing
that. sorry for
trouble
mircea_popescu: and
then
the hashes aren't checked against
the file updated prior
to updating and
the result after updating it ?
mircea_popescu: why
the fuck would you
trust some random number from a file.
esthlos: they are already lying in
the vpatch file
though. what am I missing?
esthlos: mircea_popescu: it matches hashes
to build
the dependency graph
esthlos: well
there is vtools for vdiff, right?
a111: Logged on 2018-07-06 23:13
trinque: shells out
to patch, perhaps
the intent
there was
to end up with an external patch util
that understands vpatch hashes. esthlos, maybe shed light?
mircea_popescu: in otherr lulz, chick
tastes my steak, "Hey,
this isn't steak
tartare ;
this is steak a la mode"
mircea_popescu transparently has about as much respect for
the intellectual productions of north america as for
the intellectual productions of
the gabon republic.
mircea_popescu: asciilifeform anyway, what i'm waiting for is you discovering
there's ~1% NEW keys in
that 4.6mn pile. after which we can simply declare github ie "technology" production in
the empire dead and move on.
mircea_popescu: right. might as well use realistic
terminology rather
than
their in-universe nonsensical wank.