221000+ entries in 0.145s
mod6: ok. what should
the vtron do with
these extra roots? place
them at
the end of
the flow as leafs?
mircea_popescu: it should respond with "broken
tree, fix seals" error and not press.
mod6: the main reason
that I bring
this up; 'foobar.vpatch' is being dumped out of
the flow and causing problems since i've implemented
the axiom of 'a vpatch can only be in
the flow if all of its antecedents are present.' which causes a problem in
this case as it gets chucked out as an orphan.
mircea_popescu: trb-shiva should be
trb-shiva ; if shiva-genesis also exists nothing is hurt
thereby.
mircea_popescu: asciilifeform an item can exist in
two copies : as its independent
tree AND ALSO as a patch imported in a project.
mod6: both of
these have all inputs as 'false' -- hard for
the code
to
tell which should be witch at face value without something "and it has at least one descendant"
mircea_popescu: but an important point here i must stress is
the COGNITIVE LOAD of a v
tree.
these aren't mechanical "oh, it changed x file so it goes with x". you
think, as
the author, and exactly in
the manner of scoring wot members : what should
this item be anchored on ?
mod6: so say we go with
that...
that 'foobar.vpatch' just inherits an antecedent 'genesis.vpatch'; how does one distinguish between 'foobar.vpatch' as a root and 'genesis.vpatch' as a root without additional criteria?
mircea_popescu: just because it works(tm) ie could be got away with is no good reason
to actually
try.
mircea_popescu: asciilifeform
this is one of
those cases of "sit on side of sanity ask what can get away with".
mircea_popescu: all patches
to
trb
tree must refer
to an antecedent in
the
trb
tree. no exceptions. if "nothing comes
to mind", genesis is a fine default.
mod6: <+mircea_popescu> either it builds in its own independent
tree, or else it declares an antecedent in
the
trb
tree. << so in
the latter part here, should my 'foobar.vpatch'
that just adds one file without any antecedents or descendants actually inherit an antecedent, in
this case 'genesis.vpatch' ? just
trying
to understand ...
mircea_popescu: the criteria for root/leaf are
the same : anything false, root. anything non-false, leaf.
mod6: <+asciilifeform> mod6: wtf means 'root and leaf at
the same
time' << in
the old code, it is a root, because it has no antecedents, and it is a leaf because it also has no descendants.
mod6: ok i guess
that would be bad in
the sense
that "i'm just staring
this project, my genesis should be a root even
though nothing descends it yet..."
mod6: ok, so
that's basically what I was wondering.
to be designated a proper 'root', do we also add
the criteria of "must have an actual proper decendant"
mircea_popescu: either it builds in its own independent
tree, or else it declares an antecedent in
the
trb
tree.
mod6: so in
the case of my previous implementation (V99995),
these island-roots would simply endup at
the end of
the flow, as a leaf. as
they are both a root and a leaf at
the same
time.
mod6: ok, i'd have
to look at shiva genesis again here. but yeah, multiple roots.
mod6: so
this one single vpatch has a 'false' input, and a non-zero sha512 output.
mod6: Say
that we have a flow, like
trb, with all sorts of vpatches
that stem from one single root. where
that root is designated as a 'root' because all of its inputs are 'false'. what should happen with a vpatch
that, for instance, just adds a file
to
the source and has no antecedents, nor decendants.
mod6: So, my V changes
that implement a proper wot-variant V are looking pretty decent. however, I
thought up an edge case
that I'd like
to discuss a bit more -- and I know we've been over
this a bunch, and even recently.
mircea_popescu: yes i'm aware
that forcibly works and
their own heads don't. so ?
mircea_popescu: asciilifeform consider ben_vulpes 's latest article.
the choice is very clearly available ;
the sort of mind who nevertheless opts for idiocy
truly deserves it.
mircea_popescu: not even
that. i don't perceive
they're actually hurting. yes
they're fucking up
the lives of idiots. so ?
mircea_popescu: the ONLY reason
they're still here is
that i've not decided
to end
them.
mircea_popescu: and
this isn't just re derpy "democratic" forum or herpy "free" sexploitatation venue.
this applies
to
the fucking guardian, or
to wikipedia.
mircea_popescu: takes me all of half an hour
to organize a 10% chargeback pile, which is
the immediate end, for isntance.
mircea_popescu: nothing easier
than
to
turn off cc processing for one of
these "website businesses"
mircea_popescu clearly recalls
that when i showed somethingawful.com
the cat
they immediately stfu and ran away.
mircea_popescu: heh.
they should have
thought of
THAT before being annoying.
mircea_popescu: ben_vulpes what's
the "everything should be free"
thing ?
mircea_popescu: broken shit is what you get when you don't let
the "overly agresive Alphas" beat shithead manning into a bloody pulp.
a111: Logged on 2017-01-25 22:32 asciilifeform: broken searches are nearly always a result of some pathetic piece of shit
trying
to 'be clever'.
a111: Logged on 2017-01-25 22:22 ben_vulpes: WHAT i ask you IS
THE POINT of an ultra-heavy IDE
that a) cannot
tell me where
the protocol breakage is during a refactor much less what
to do about it b) has a project search SO MISERABLY BAD
that a man must revert
to grep in order
to find ANYTHING
a111: Logged on 2017-01-25 21:47 phf: so if you have a system
that you implemented fast, but it's slow, but you know how
to now slowly make it fast, you have a strategy. if you're chasing corner cases, running a profiler and get mostly flat distribution, writing in special cases, etc. you don't have one
a111: Logged on 2017-01-25 20:59 asciilifeform: 'Why haven't you embraced Bitcoin
to get away from
the restrictions of
the banks / credit card companies? - We used
to accept bitcoins
through Coinbase.
They dropped us a year ago because we are a kinky site. No joke.'
a111: Logged on 2017-01-25 20:55 asciilifeform: wtf is
the point of making umpteenth centralized arsebook.
a111: Logged on 2017-01-25 20:54 asciilifeform: 'Yes, it was mainly for FetLife's and my protection, and we had
to act swiftly. One could easily argue
that we didn't move swift enough and
that I shouldn't even make
this post because something in it might incriminate FetLife or me.' << lel
ben_vulpes: also phf may i please have
the log backups?
ben_vulpes: asciilifeform: posix regexes work, i'll see what
the performance implications are of using
those instead.
ben_vulpes: postgres full
text search; "some pathetic piece of shit
trying
to be clever"
ben_vulpes: WHAT i ask you IS
THE POINT of an ultra-heavy IDE
that a) cannot
tell me where
the protocol breakage is during a refactor much less what
to do about it b) has a project search SO MISERABLY BAD
that a man must revert
to grep in order
to find ANYTHING
☟︎ ben_vulpes: in which it is shown
that xcode's "find occurences of string in project" ACTUALLY FUCKING DOES NOT
a111: Logged on 2017-01-25 21:44 phf:
http://btcbase.org/log/2017-01-24#1606341 << optimization strategy is when you have a slow algorithm somewhere in your architecture (you put it
there because it was a reasonable
tradeoff at
the point), but you can replace it with a faster algorithm without leaving
too much damage on
the architecture (alf calls it "scaring")
phf: so if you have a system
that you implemented fast, but it's slow, but you know how
to now slowly make it fast, you have a strategy. if you're chasing corner cases, running a profiler and get mostly flat distribution, writing in special cases, etc. you don't have one
☟︎ ben_vulpes: ugh mircea_popescu how do i find
the qualia
thread in your blog
phf:
http://btcbase.org/log/2017-01-24#1606341 << optimization strategy is when you have a slow algorithm somewhere in your architecture (you put it
there because it was a reasonable
tradeoff at
the point), but you can replace it with a faster algorithm without leaving
too much damage on
the architecture (alf calls it "scaring")
☝︎☟︎ ben_vulpes: YOUR PERVERSE
THOUGHTS MARK YOU FOR
THE GULAG