231800+ entries in 0.15s
phf: pitty we didn't have it from
the beginning. all
those beautiful
tumblr pictures lost forever
mircea_popescu: pity we didn't have
the bot archival
thing earlier huh.
phf: it must've been down for a while, because wikipedia uses archive.is
to link
to his homepage
phf: ah, right
that's
the guy
phf: it sort
traced western history from
the perspective of
time measurement. "and
then
they had a city clock
to synchronize everyone"
mircea_popescu reads recipes for coffee liqueur on web. INSTANT COFFEE!
they... USE WATER! holy shit...
phf: i
think it might've been by
the same guy who did "history of
timekeeping" or somesuch
that was briefly
trashed hmm
phf: i feel like
there was a neat article about
the history of seals somewhere inthe logs, but i can't find it
ben_vulpes: rebase/regrind
to move
the patch in
the
tree and seal
to...seal.
ben_vulpes: reseal, what is
this. signed same matter again?
mircea_popescu: ben_vulpes which of
the
trb genesis seals are seal and which reseal ?
ben_vulpes: whence 're',
though.
that other key was 'derpderp ben_vulpes', not 'foundation chair ben_vulpes'
mircea_popescu: reseal =
the act of signing a patch with your own key.
a111: Logged on 2016-12-22 18:49 mircea_popescu: you ~can~ after all rebase a patch ; not just because of
the patch, but also because of
the sig.
mircea_popescu: (which is what all ~ALL~ standardization EVER does - makes it so you're really careful not
to
typo. it can't resolve problems of
the other nature, just
this.)
mod6: sure, but i'll remain unsigned until
testing.
mircea_popescu: but ~making
that list~ is entirely unmachineable ; and me being very careful not
to
typo doesn't help
mircea_popescu: if you have a collection of keys you're - for whatever reason, maybe
they're all me, maybe
they're my harem, maybe
they're all
the people from russia, whatever - interested in, yes you can build
the set of all pathes
they signed.
mod6: So I have made a couple small changes
to my V99995, and have put
together an output
trace of what we were seeing with V99995 and what we now see with
the changes made in a possible V99994 version. Review of
this would be nice
to validate
that
the behavior is correct:
http://www.mod6.net/v-99994-trace.txt mircea_popescu: and
there's no "up
to good" or "no good" directionality of intent involved here. he is up
to nonsense, because meaning and universality are mutually exclusive.
mircea_popescu: yes, once you populate a db with
the keyids of "known mp's subservient keys" you can
mircea_popescu: universality and hardness are orthogonal, how hard a diamond is as a standard of realistic hardness has entirely nothing
to do with how many cunts wear one around
their whatever appendage.
mircea_popescu: anyway. i have a perfectly serviceable way
to harden keys for
the record. it's just not ~standardized~, and it's unclear it should be.
mircea_popescu: nobody forces you
to even consider patches signed by people out of your wot.
mircea_popescu: if patches are signed by dead people only,
they don't belong in presses
phf: asciilifeform:
these are basically
three different solutions
to
the same problem of "how
to allow more
than one kind of vpatch". yours is mechanical, mine is an attempt
to expand
the mythos and mp's is cutting
the gordian knot
☟︎ a111: Logged on 2015-08-28 03:13 asciilifeform:
thing does exactly
three basic kinds of
thing - verifies sigs; determines what subcoagulations of spittle in
the spittoon are in fact in single strands; and permits operator
to select individual strands, and cut'em (by whatever criteria, including signatories or combinations
thereof)
phf: i guess
the multiple keys idea was already introduced in gossipd (in
the original spec i suspect it was a solution
to "no automatic RSA-ing" problem)
mircea_popescu: i'm just saying -
there's nothing lost here. can emulate naked pastebin in v style np.
mircea_popescu: phf yes, in principle. in practice i expect "centralizing" rebasing vpatches
to happen all
the
time
to prune
trees of
their noncontroversial joints.
mircea_popescu: you can literally come up with an idea for a
thing while
travelling ; go
to internet cafe ; spin up gpg
to make you a new key while you bash it down ;
then sign
the patch with
that key which you don't even bother
taking from
there.
phf: mircea_popescu: correction in
this case can come in a form of another vpatch either by original author after
the discussion or by anyone who wants
to make annotations, etc. in which case
the dialog becomes valuable on its own, because it preserves
the differences
that have didactic value
mircea_popescu: can release patch
today under your
text sig ; rebase it later with your main sig.
mircea_popescu: ie, item X enters life signed by "doubful matter key Z" and
then a year later is signed by "ok
this is it key Z" and makes it
to
the stable press
mircea_popescu: you ~can~ after all rebase a patch ; not just because of
the patch, but also because of
the sig.
☟︎ mircea_popescu: phf you don't have
to post a snippet of code as ~vpatch~. can just pastebin it also
a111: Logged on 2016-02-20 22:45 phf: "i, ordained computron mircea lifeform, in
the year of our republic 1932, having devoted
three months
to
the verification of checksums, with my heart pure and my press clean, sit down
to
transcribe vee patch ascii_limits_hack, signed by
the illustrious asciilifeform, mircea_popescu, ben_vulpes and all saints."
phf: but
the reason i made
those statements yesterday is because i
think
that like saying
things in log is an opportunity
to be corrected, so does posting a vpatch, it could be a learning experience. instead
the mindset seems
to be
http://btcbase.org/log/2016-02-20#1411214 ☝︎ mircea_popescu: software design as god intended. FIRST you do by hand ;
THEN you automate
the parts worth automating.
a111: Logged on 2016-01-19 14:46 mircea_popescu: you could
technically run a chan off v.
mircea_popescu: phf ah, yes, but note
that
the item contemplated
there is specifically not discussion ; but its results.
a111: Logged on 2015-09-12 20:28 mircea_popescu: which... you know, i slept on
this, and it occurs
to me
that ACTUAL MATHEMATICS might be
the perfect
thing
to implement over V.
a111: Logged on 2015-08-08 04:11 asciilifeform: mircea_popescu: in somewhat related nyooz, i've been experimenting with what for now i call 'v' - a very dumb 'versioner'
that i've been writing, which eats solely 0) pgp keys 1) patches 2) signatures for same, many-to-many mapping of (2)
to (1)
a111: Logged on 2015-08-05 14:11 mircea_popescu: how would
this b-a versioning system work ?
a111: Logged on 2015-08-05 14:00 mircea_popescu:
there's no reason for
this
to
take a week
to do.
a111: Logged on 2015-08-05 13:38 mircea_popescu: one is USE. specifically - hanbot must be able
to put into work
the
theoretical advances b-a produces. and ima use her as a stand-in for "intelligent and willing
to work, but not able
to grow a beard".
a111: Logged on 2015-08-05 04:42 asciilifeform: also
the continuity of identity. if, for example, my patches at some point go from
tiny
to elephantine, from single-purpose
to 'omnibus', from deadly-simple
to 'wtf is
that' - folks are
to presume
that i have been finally killed and key is in hands of hitler. and should
then rate accordingly.
a111: Logged on 2015-08-05 03:55 mircea_popescu: asciilifeform he still has a point. a) we're careening dangerously
towards -dev levels and b) people can't fucking follow wtf is on
that list.
a111: Logged on 2015-04-03 21:41 asciilifeform:
trinque: when you use a version control apparatus, it is very easy
to produce patches
that cannot be applied using your mind