211300+ entries in 0.998s
trinque: how do
they expect me
to watch gender studies courses on how
to properly sit on my hands?
mircea_popescu: "breaking news : so very importuned were
the damsels by
that fabled rod,
they made an appointment
to be visited again next week."
mircea_popescu has participated in
this sort of "home invasion" where one girl got fucked,
the other one "are you going
to fuck me
too ?" "maybe
tomorrow". on
the morrow, dilligent, awaiting her
turn...
mircea_popescu: dude fucks some kids, usg files suit on
the expectation
that kidfucker is going
to be so fucking impressed with
them caring he'll sign anything
they want. when
this expectation fails
to materialize, usg asks judge
to roll back
time, "really for keepsies never happensies", judge agrees, on
the rationale
that maybe we fuck him later. dude... sticks around.
mircea_popescu: which nevertheless he will do, as per alf's "there's no shortage of usg cowsies who WISH
to be such."
mircea_popescu: that dude has
to be
the king of imbeciles
to STAY IN
THE US
Framedragger: (not implying
that
there's much worth for any noob
to start running a
tor node *now*.)
Framedragger: sure. well,
tor had been rather useful
to me before, i
took from it more
than it's
taken from me, so at least
there's
that. :)
Framedragger: (small virtual machine so wouldn't be
too useful for
traffic analysis, not much
traffic)
Framedragger: reminds me, i
think i'm still running one
tor exit lol. mebbe
time
to redirect resources
trinque: but yes,
they don't want
to "disclose" because of
the shriveled cock
trinque: asciilifeform: grunts
that did
this probably don't get
the good
toys
ben_vulpes: also something something maersk and ibm cockchain
tekmologies
ben_vulpes: in more lcs gold:
http://archive.is/XcC3N << not only are
the damned
things made of paper and disintegrate as soon as you drop
them in
the water, but
the amount of money
that
the usg.navy has burnt on
them is actually so embarrassing as
to be worth a classification fight
trinque: aside
the fact
that
tor doesn't work
trinque: we would - I'm sure - be shocked
to find
that
the
top secret exploit is
the damned rebranded firefox
mircea_popescu: fig 7 directly what you'd expect based on
the competent discussion of "What is a
timer"
mircea_popescu: the guys did actually splendid work, read
the paper, worth it.
☟︎ mircea_popescu: one increment per 4.7 cycles.
they really massaged
the shit out of it
mircea_popescu: trinque
the students are retarded
to
the point of abrutissement.
trinque: not unlike what's on
the wot browser
trinque: asciilifeform: lots of paring down of output, svg nodes shall be clickable links, only showing
to depth 3 on any given page
trinque: I've been slogging
through
the
thing reading
the paths for acquiring and validating blocks, and my god, must have map.
a111: Logged on 2015-07-04 03:18 asciilifeform: so far i'm utterly failing
to even get 'codeviz'
to build.
trinque: the
teachers or students? or can
they be discerned?
mircea_popescu: and in other news,
they were going
to open
the school year
today, so
they went on strike instead. soberania! haymasfuturo!
Framedragger: i wonder how well a
typical hashtable with 2**64 elements work in practice,
tho. where would store its elements?
mircea_popescu: look-up
table has its niche. it isn;t
the universal solution of all computing.
mircea_popescu: 64 SEEKS.
thousands of asm lines. all i do is a mult. one.
Framedragger: well, at least your user input is segregated into
two 'containers': 1. GET requests for static files; and 2. user comments - processed by some specific script, separate from
the rest. but yeah,
this isn't exactly amazing innovation, i agree.
trinque: maybe narrower, sure, but don't
treat it like it's safe
trinque: so my
http requests don't run
through it; something does
trinque: if your user input is run
through your scripting language, how exactly have you changed
things in regards
to attack surface?
trinque: Framedragger:
though actually I don't buy it
Framedragger: trinque: point
taken. :) (i'll only repeat one
thing here: in a 'proper static site' setup, one is *not* exposing vulns of a scripting language
to
the web. only
those of
the webserver.)
trinque: PHP was just
the most popular of
them
trinque: Framedragger: oh also,
take a look at
the history of exploits against python sometime.
trinque: if you're sitting
there saying "huh, now my writes
take a year because I have
to update sidebar comments on every page I ever wrote"
Framedragger: (just for posterity, other metrics say
that consumer ssds seek average may be ~3ms.)
☟︎ trinque: if
the
thing benefits from caching, cache
trinque: as always with
tools,
there is not a one-size-fits-all rule
to be dumbly applied
Framedragger: btw, if you store 2**64 nodes in a (balanced) binary
tree, wouldn't
the "number of seeks" be ~64? i suppose
that doesn't look
too pretty, but considering
that an ssd's seek
time is ~0.1ms... not
that
these numbers are rigorous or anything.
mircea_popescu: neways ; i shall be back
to
town. anyone wanting
to argue
the above -- in a few hours.
mircea_popescu: (and no, any other storage scheme is cheating -- you're
trying
to use my f(x) = 2x without admitting it.)
Framedragger: right, basically i'm putting a lot of
trust into fs, fundamentally. hence disagreement - fair enough. (to summarise.)
mircea_popescu: Framedragger imagine you have a 64 bit maxint stored as binary
tree (provedly - fastest) and now you seek... how many nodes ?
Framedragger: well, you'd like
that "compute faster" line
to be
true, but it ain't.
mircea_popescu: and
this fundamental problem holds. flat is not necessarily faster.
Framedragger: ...that's why it's great
to host
this on a disk with great random access
times.
mircea_popescu: and i'll compute 2 * maxint/2 faster
than you'll seek maxint/2
mircea_popescu: fx = 2x can be flattened into (1, 2), (2, 4), (3, 6) etc.
this clearly flattens it in space, but just as clearly fucks up
the
time. now you have
to seek.
Framedragger: first off,
the former has a less clear attack surface, may depend on script in question, etc. second off, may scale not as well (no
this is not
the same as kiddie complaining
that an rdbms is "not web scale").
mircea_popescu: over space, yes. over
time - not necessarily.
that is
the rub here.
Framedragger: no need
to compress, what i meant by compression is
that an index is sorta-doing
that. storing flat files on fs is basically 'flattening'
the process over space and
time.
mircea_popescu: what is
the cogent difference between
these symbols, "script-specific php processes" and "a standardised additional unit of its resources" ?
Framedragger: that being said, my point would work better if
trilema had been having performance issues... which it ain't.
Framedragger: well,
the compression-decompression process is so
to speak serialised / offloaded
to an fs. not a bad
thing!
mircea_popescu: some kind of index. otherwise you end up repeating shit
to high heavens for no reason, and your computer looks more like an abacus.
mircea_popescu: in your flat scheme,
the words "Trilema - a blog by mircea_popescu " would appear... 72k
times!
Framedragger: i can't see how i can be convinced
that launching script-specific php processes is ~same as a webserver allocating a standardised additional unit of its resources (memory /
thread etc.)
mircea_popescu: well everything can end up
the same
to
the man determined it be so.