317400+ entries in 0.201s
mircea_popescu: ~only way
to make a shorter
text reliably is
to rely on specified notation known in advance.
assbot: Logged on 22-11-2015 06:30:10; mircea_popescu: abstraction is loss. you
throw out all sorts of stuff and hope&pray
that it wasn't actually needed.
mircea_popescu: ben_vulpes happens
to me all
the
time!
then alf runs off and invents it and i'm like fuuuu wasn't
this on
trilema!
☟︎ ben_vulpes: i have been failing
to shit words on
the
topic out because i
think of familiarity with it. it all seems so obvious!
ben_vulpes: another good
topic is "specificity of diddling".
mircea_popescu: but
the complexity of
this notion is rapidly expanding.
mircea_popescu: davout you pm deedbot with a list of strings which it retains for
the day, prints a cloud somewhere, one can click items in cloud
to get list of days so
tagged
mircea_popescu: the sad fact of
the matter is
that summarization squarely relies on ignorance.
there's no obvious way around
that rock.
davout: mircea_popescu: maybe use log.b-a.com for
that purpose? how would pm
tagging work?
ben_vulpes: 'twas not actually
that hard, but it did
take knowing
the variety speak
thoroughly.
ben_vulpes: i recently
took a 45 minute sojourn into
the history of "protocol vs. promise"
mircea_popescu: or is it
the sort of midway solution
that's
the average of man and woman and horse and chimney ?
mircea_popescu: would actually
the idea of pm
tagging for each DAY solve anything / be worth anything ?
davout: anyway, my point is
that if nobody remembers,
that nobody bothered
to blog it,
the fact
that completeness is a problem might indicate a violation of fits-in-head
davout: ok, i meant
that
this issue came up when you were
talking about "what should go into a
tmsr fork"
that danielpbarron ended up summarizing on his blog?
davout: re
the mp describes a HF
that danielpbarron ended up blawging about?
mircea_popescu: if someone, as oft is
the case for say mod6, is
trying
to make
the whole pile of what was said abvout X,
they encounter a very present difficulty.
☟︎ davout: if nobody remembers how
to find a particular
thread, maybe
that
thread isn't really worth remembering after all
trinque: hm. it does invite
that abominable hashtag social media
tic.
mircea_popescu: i suppose
this could be mediated by doing
the
tagging over pm
mircea_popescu: so, IF we start
tagging
things in chan,
this is indistinguishable from good old spam. (textual content of no
textual intent).
mircea_popescu: mrottenkolber don't kid yourself,
they're living in a dictator sheep.
mircea_popescu: but my main concern with
that scheme, upon meditation, is
that... ok, brace yourselves :
mircea_popescu: turns out, re prev
tagging discussion,
that ... we're already doing a rudimentary, grassroots sort of
that.
phf: we're an anarcho-syndicalist commune. we
take it in
turns
to act as a sort of executive officer for
the week.
mrottenkolber: I am indeed using ssl
to connect
to freenode,
this assbot
thing might actually work. :D
mrottenkolber: I
totally get why bitcoin development motivates v, obviously
there is motivation for adversaries here.
mircea_popescu: well if you're curious, free money is
the basis for
the existence of
the republic which is
the reason stuff like v ended up existing. but i suppose from outside
this string of actual events may as well be coincidental.
mrottenkolber: mircea_popescu: No, sorry, still mumbling aout
the why I am in b-a
mircea_popescu: mrottenkolber nothing i said was related
to bitcoin, was it ?
mrottenkolber: I have absolutely no interest in bitcoin
to be honest, don't see
the point.
mircea_popescu: asciilifeform something
tells me commenter has never seen hyenas. wtf, some of
the most social animals, in its good days washington dc polite society more or less approximates pack of hyenas.
mircea_popescu: mrottenkolber> Naive question: what would be
the implications of using sha1 instead of sha512 in vdiff? << roughly speaking you'd be going back in
time, we're by and large in
the process of moving
to sha-3
mrottenkolber: I read about v and liked
the hack, ran into
the expired signature and well...
mircea_popescu: will be signign
the davout application later
today myself.
mrottenkolber: But e.g. in my head, if you spend 70k
to compute a sha1 collision, it won't look like C code probably ;-)
mrottenkolber: I am only mentioning
the sha1 option because I don't understand crypto well enough
to be able
to rationalize
the effort of producing a file, with
the same sha1sum, with an exploit while
the patch still applies.
phf: mrottenkolber: a better place
to wire v would be mercurial's mq facility. mercurial has a way of managing plaintext patchsets,
to do
things like patch refresh, i.e update
the contents of patch from
the current
tree state, mercurial managed patch press, i.e. instead of doing "manual" v press hg will keep
track of state for you, etc.
this will not be a way
to share patches, as much as a way
to facilitate vpatch authoring.
assbot: Searching pgp.mit.edu for key with fingerprint: 76EB8DE4EA28A5C4746C71AA7C7F34CDCF4CDA75.
This may
take a few moments.
mrottenkolber: will probably not be chatting
that much, but I am very keen of actually starting
to build some wotness. My gpg is useless right now its so bare.
phf: asciilifeform: well, you can verify data without verifying git. i've done it, and
the
thing definitely produces a semblance of "blockchain", i.e. later commits hashes previous commits' hashes, so you can if you ignore
the sha1 issue,
take a git branch and confirm its uniqueness from
the final hash
mrottenkolber: phf:
That's why I
thought about adding signatures of “git vdiff”
to commit messages and an alias/command
to verify a branch.
phf: mrottenkolber: if
that's your only goal, you don't need v for
that. git already does it for you by having a linearly hashed commit chain. right now you have a reasonable way of verifying
the git chain from
the
top hash, but you can't make any crypto claims about it, since
the hashes are sha1
mrottenkolber: My point is
the
toposort isn't really part of
the problem v solves.
The function is
to cryptographically verfiy a sequence of patches (based on a wot), who cares where
that sequence comes from, as long as each patch (commit) has a signature.
mrottenkolber: Naive question: what would be
the implications of using sha1 instead of sha512 in vdiff? (thinking about porting V
to git hooks/aliases)
nubbins`: mrottenkolber did you
try manually verifying
the sig?
mrottenkolber: asciilifeform: So I dowloaded v99.tar.gz because I
thought it was a cool hack, and expected
the following
to work: (inside
the v99 directory): ./v.py -v --wot wot --seals sigs patches f
nubbins`: asciilifeform did you receive yr
textiles yet?
☟︎ phf: that's a bit
too many dirty words for my
taste, but i'll give it a
try
phf: that looks neat, but is
there a compiler
that adds retro compatibility?
trinque: my approach
tends
to be
to set different flexbox rules depending on viewport size
trinque: phf: ever use flexbox? something resembling a layout system ended up in
the standard itself
phf: ben_vulpes: do you know any css libraries
that will give me bootstrap style layout
techniques, without rest of bootstrap (columns, show/hide conditional based on medium)