341400+ entries in 0.219s
ben_vulpes: phf:
the chains must kiss somewhere in order for
the ordering
to make sense
phf: in fact kahn iterates over a set of nodes, so
there's no explicit order guarantee
felipelalli: trinque, no I was
talking about deedbot-.
The bot didn't accept my renewed key.
felipelalli: mircea_popescu, I know
that you
think expire a key is a bad idea. I saw you saying
that in MPEx FAQ. But why? Could you elaborate more about
that? Isn't
that useful in case someone dies or lost
the control over
the key?
assbot: Founder of Liberty Reserve Pleads Guilty
to Laundering More
Than $250 Million
through His Digital Currency Business | OPA | Department of Justice ... (
http://bit.ly/1WVGFwa )
phf: doing by
the book kahn
topo sort on my graph results in
topo a b c d e so pressing
to c drops
the whole d e subgraph
phf: so if i have a->b->c d->e and i'm pressing
to b, i need
to make sure
that
topo sort is d e a b c, so
that
the press includes d and e
assbot: BtcAlpha.com F.MPIF
Tracker estimated NAV per share: 0.00021486 B (Total: 426.88 B). Delta: -1.51 B. Last
trade for F.MPIF on MPEX was at 0.000209 BTC [-]
ben_vulpes: ;;later
tell asciilifeform ^^ plz
to opine
ben_vulpes: so
that operators can press, migrate dir, and press more.
ben_vulpes: eg
that `v press shiva stans_sweet_patch.vpatch && v press shiva stans_sweet_patch.vpatch' must result in
the same
tree as running
the command once.
ben_vulpes: this means
that v-pressings have
to be idempotent.
ben_vulpes: a
thing
to do might be
to leave
the genesis press as-is, move
the resulting
tinyscheme dir into
the correct shiva location and
then press
the rest of
the patches reground
to reference
the shivadir
punkman: it'd work better for viewing, because I've seen broken selections a lot
too
mircea_popescu: the dom is a wholly client side
thing, server just spits out a string as far as it's concerned
phf: ben_vulpes: so shiva 2 of 2 links
to rest of
tree, shiva 1 of 1 is a genesis with no descendants, and
that whole
tinyscheme_genesis_fixed
tree presses into
tinyscheme/ root
that's not even inside bitcoin. i'm not sure what ascii is up
to
ben_vulpes: but it's so close! with only an unknowable amount of further hacking it could
totally work!
mircea_popescu: phf
the
truth is
that it'd be great if
there was a way for reader
to select what
text he's referencing. but if it can't be made
to work
then we can't really use it.
ben_vulpes: asciilifeform: has blessed us with a new root node with which
to fuzz all v implementations
mircea_popescu: i guess i fucked it up when putting it on
trilema ? asciilifeform ^ mind saying what
the above link does ?
☟︎ phf: yeah,
that's what i'm debugging right now
mircea_popescu: "riously, so
the girl won't fuck because she figures you don't value her if she" << on my system
punkman: there's a part about a dir rename in
that mail
phf: so i dropped patches from "[BTC-dev]
Tinyscheme Genesis, Cleanup, and Fixes, CORRECTED; -and- Shiva Pedigree Bridge." but i'm still missing something so
they are just hanging
there separately,
http://104.131.72.249/patches/ ☟︎ ben_vulpes: phf: also, if you'd care
to share your llvm/clang compilator i'd love
to
take a look
mircea_popescu: ben_vulpes does
the selection work on
trilema for you ?
phf: ben_vulpes: yeah, i fixed more
things since i last chimed in, but now end range is not being covered on safari
jurov pats mod6 on
the shoulder... no problem, i had
to redo monthly
treasury report once or
twice,
too
mod6: i just
tried
to avoid extra clutter in
there.
mod6: where
that part is above
the section for [V]
mod6: makefiles, as
they were submitted
to
the Mailing List [R.06]
mod6: NOTE: With
the publication of
the latest version of V [v99996] [R.05]
these
mod6: oh, it does, sometimes if it's been referenced before in
the document, i don't re-reference it.
mircea_popescu: so
then "the email
to
the mailing list" symbol shouldn't have a reference ?
mod6: mircea_popescu:
that part is just in reference
to V's release in R.05, not
the high/low S patch which is R.09
ben_vulpes: asciilifeform: would you confirm
that
tinyscheme_genesis_fixed.vpatch does *not* depend on shiva parts one and
two?
☟︎ mircea_popescu: change requests.
The intimate details of
the changes are outlined in
the
mircea_popescu: mod6 released V [v99996] [R.05]
that resolved a defect and implemented
two
ben_vulpes: i even pointed
that one out
to you, but we're mad busy
mod6: ok yeah,
there is a ref in
there. ^
mircea_popescu: the first is a mere spelling error.
the second, shoul;dn't
there be a [R]eference
to
the email ?
mod6: oh hey, did i screw
that up?
BingoBoingo: brb after dinner and 12&12 study
to issue qntra statement
mircea_popescu: actually from what i hear,
that's
the voice of privilege.
ben_vulpes: don't even add up
to a whole computer over
the year.
ben_vulpes: how do you
think i'd rather spend my dollars, on 'macbook pros' or bitcoins and linux workstations?
ben_vulpes: mircea_popescu: you
think i don't know
this?
BingoBoingo: <mircea_popescu> BingoBoingo is actually right,
there's some history of derpage in all
this. << username high-s malleator used on social media was 'amaclin'
mircea_popescu: ben_vulpes serenissima would rather buy coke whores from drexl
than west coast web coders.
ben_vulpes: la serenissima might be able
to rent my oar pullers if it could convert my deficit spending
to
turkey-buying dollars
BingoBoingo: <mircea_popescu> since
they agreed
to only include low-s for whatever random reason / concern
trolling / misinformed desire
to be nice and good,
they're stuck now. << It's power derps malleating
tx on
the way
to miners, including on
that realy network.
phf: he can get me a pm at $150/hr and
two junior devs $50/hr each in no
time. selection will work by next iteration, but will depend on jquery and react
☟︎ mircea_popescu: BingoBoingo is actually right,
there's some history of derpage in all
this.
phf: gotta outsource it
to ben_vulpes
phf: i got
tricked into hacking web
mod6: sometimes when i'm quoteing someone, as opposed
to a
thing, i'll use `` '' instead.
BingoBoingo: <ben_vulpes> in
that it's possible
to malleate in either direction. ease i suppose doesn't figure into
the question. << Someone malleating
to high-s is why power derps started malleating
to low-s
ben_vulpes: that's how mod6 has always quoted
things...
mircea_popescu: ``heathen command'' << am i
the only one seeing a weird set of unmatching quotes here ?
ben_vulpes: but
there's no actual reason why
they couldn't mine high-s
transactions, adherence
to party line aside.
mircea_popescu: statutory solutions
to bad design, a "western world" specialty.
mircea_popescu: note
the very usg-tard approach
to
things : it IS
true
that ambiguous signatures are bad ; it is DEEPLY UNTRUE
that we can counter
this by AGREEING among ourselves "not
to do it".
mircea_popescu: since
they agreed
to only include low-s for whatever random reason / concern
trolling / misinformed desire
to be nice and good,
they're stuck now.
mircea_popescu: if you include
the
tx, you get
the fee. if you don't include it, for any reason, you don't get
the fee.
ben_vulpes: it is greater on malleated
transactions?! but but
ben_vulpes: how did you come
to
the conclusion
that it was miners doing
the malleation, and not nobodies malleating and rebroadcasting?
ben_vulpes: but digging as far down into
the roots of my conclusions as makes sense
to dispel ambiguity
mircea_popescu: feel free
to read it yourself, pointer
to code was in log
mircea_popescu: i originally
thought so but research in here shows
that no, it's never checked.
☟︎ ben_vulpes: now were b,tmsr~
to run its own pool mining only high-s
transactions, would clients in
the wild reject
those blocks?
mircea_popescu: the benefit of all
this pile of legwork is deeply unclear,
mircea_popescu: the miners are mining low-s as is and malleating all high-s and mining
them as low-s
ben_vulpes: now, are miners not mining
transactions signed low?
mircea_popescu: mostly because
the conversion consists of substracting from a constant