599700+ entries in 0.308s
mircea_popescu: do you suppose her mother coming
to your room and saying "neither of you is
to leave here until you fuck" help anything ?
mircea_popescu: suppose you're with a girl
that doesn't wanna fuck you.
ben_vulpes: the incentives are aligned! merchant and payment processor must agree
to get anything out.
mircea_popescu: if i knew how
to formalize
this
to be readily understanable for people i'd
trilema it
ben_vulpes: okay, so my derpitude re: m/n aside,
the
thing has a stable solutino.
ben_vulpes: both keys must sign for outputs
to be valid.
mircea_popescu: kinda why i don't
think much of
the entire "multisig" bullcrap.
cazalla: so how long until bitpay pulls
that shit on
the merchant
mircea_popescu: which is how and why
the us political system does not work.
mircea_popescu: you go
to stan : hey listen, he's giving you nothing.
take
this 5 cents sign over
to me.
kakobrekla: there were
to be
two machines connected with serial cable < heh i have such setup with a buffer on
the cable
mircea_popescu: so, me you and stan have
to split a buck. i go : fuck stan, give me 50 cents i'll sign with you.
mircea_popescu: you familiar with
the
three man committee
to split a buck ?
mircea_popescu: otherwise it goes on forever, like
the us puritan
thought pattern.
mircea_popescu: asciilifeform can't blame him. only way out of
that one.
ben_vulpes: funds sent
to M/N address, both merchant and payment solution provider must agree upon processor fee and merchant share
to disburse funds
to each.
mircea_popescu: i'm kinda reminded of
the jews on
toilet joke. "is
this work ?"
decimation: yeah but he also pretty much admits
they are unworkable practically
ben_vulpes: our solution: one of
the few actual uses for M/N signatures.
ben_vulpes: cazalla: i was derping with a colleague about btc payment processing recently.
the
topic: how
to ensure
the payment processor (he who
tells
the
taco-delivery mechanism
to release
tacos) gets paid?
decimation: well, quite simply because
the failure rate would be
too high
mircea_popescu: ben_vulpes cause normally i'm like, oh, logs, fancy
that. but past few days it's been... omfg help me.
mircea_popescu: asciilifeform nah, im sure
that's not
the case, i never cut solid copper anythings.
mircea_popescu: the disadvantage of productivity is
that it's 5am and
the log is closing in on 1k lines. and yest it was nearly 3k. and jesus god it's a lot harder
to go
through when it's not mostly my own lines! i had no idea!
mircea_popescu: back when
there weren't any enemies listening in on our lists
mircea_popescu: <asciilifeform> connected with serial cable <<
this from reading up on old mpex material ?
☟︎☟︎ decimation: perhaps with a protocol validator in
the middle
decimation: asciilifeform: wouldn't it be a good idea for
the privkey need not live in
the same memory space as
the rest of
the code, for instance
mod6 gets ready
to fire up mutt!
mod6: this hasn't been done for some
time, and probably needs
to come back.
mod6: asciilifeform: i like
the idea of a cypherpunk-esq mailing list
to propagate patches from a common release.
ben_vulpes: what is
the bitcoinating?
the part
that attaches
to
the network, downloads and verifies
the blockchain?
ben_vulpes: <asciilifeform> decimation: bitcoind begs
to be split into at least 3 programs << of which only 1 is necessary ! << for
the record, what are
the
three and which
the one?
ben_vulpes: i
think
then
this discussion is settled.
cazalla: maybe
they meant
to raise 50k facebook likes instead
cazalla: mircea_popescu, where
the facebook page and mockups for
that?!?
undata: I yield
the balance of my
time, haha
decimation: folks are welcome
to publish, index as
they see fit
mircea_popescu: decimation yes. but actual gentlemen, rather
than presumed gentlemen.
decimation: asciilifeform: right, I envision it more as
the collected correspondence of gentlemen scholars, rather
than a profitable venture
mircea_popescu: whenever people's conscience is
the only protection,
the
third reich is about
to emerge.
undata: it could be a fancy db implemented atop
the blockchain
undata: doesn't have
to be git
mircea_popescu: and you can't just expect "conscience"
to resist indefinitely.
undata: my main
thrust is
that
the
thing will have
to be structured in some way (a db)
mircea_popescu: which is essential, because our enemies are putting a lot of pressure on
them
to break it
decimation: undata: no one here really minds having a different opinion
than 99.999% of humanity
mircea_popescu: and
this puts huge pressure on
trusted nodes not
to break
the fucking
trust
mircea_popescu: rather
than papering over breakdowns of
trust with "foundations" and "chief scientistdom"
mircea_popescu: undata more properly said : every breakdown of
trust is a fork
undata: that fits
the social happenings well
mircea_popescu: no such
thing as "official" "because we say so". who;'s we.
undata: mircea_popescu: interesting, a fork could emerge due
to a breakdown of
trust
decimation: right, it's in
the 'eye of
the beholder'
mircea_popescu: asciilifeform nah, "official version" is redefined from *
this (static)
to whatever one has most wot
trust
towards.
ben_vulpes: <undata> anyhow, horse is starting
to stink << what is
this a reference
to?
decimation: asciilifeform:
the bigger question is: who is
the 'registrar' of
the 'official version' - or does
that merely exist in
the private collection of each person's note?
undata: anyhow, horse is starting
to stink
undata: asciilifeform: I'm saying it can provide
the input
to your envisioned system