924000+ entries in 0.66s
MJR_: i just
think
that
the silicon valley mindset of "let
them explore and figure it out" is not a great strategy for most scenarios
guruvan: I've done a buncha dotcom stuff and we always
talked about
that
MJR_: BUT,
there are some
times when you need
to do
that
MJR_: i personally, and
this is just my opinion, hate
the
term "burn rate"
jcpham: making a secure site isn't
that hard
MJR_: he actually introduced me
to a nice lawyer
dub: MJR_:
table/card games, painting little plastic soldiers
guruvan: what's
the CTOs name MJR_?
MJR_: what's
tux's background?
guruvan: he seemed
to
think I'd be more interested in
the site's security, rather
than
the principal's backgrounds
guruvan: I'm curious about his &
the cto's backgrounds
jcpham: i wonder if we can get
these guys
to do shoeonhead.jpg
MJR_: we had lunch a few
times
MJR_: but i haven't watched him at all
times
jcpham: gonna have
to follow him for sure
jcpham: mircea_popescu's
twitter is off
the charts lulzbot
guruvan: their site was broke when I went
there at first...tweeted about
that, and he responded
to
the
tweet & sent mail
guruvan: he said he's on
the forums & recognized my name - but I didn't recognize his
jcpham: if you
think
things are wild now...just wait
guruvan: coinsetter = leveraged
trading of some sort
jcpham: it's
th new bitcoinica pigeons
pigeons: oh well if
the ceo says he's legit, its gotta be
true
guruvan: I've had a chat with him in email - everyone sez
that
jcpham: he says
they are legit
guruvan: I am so glad I closed out my positions
there last week
bVector: everyone has
their price right? ;)
bVector: mircea_popescu: you're closer
than I am, how much would it
take
to get you
to kick icbit admin in
the nuts?
ThickAsThieves: i have real
trouble understanding why a receipt cant be
the last
thing
that happens in
the chain
mircea_popescu: i get
that it's way lower
than mtgox ever manages, but still. ridoinculous.
mircea_popescu: for one
thing
the 100msecond lag is getting on my motherfucking nerves.
guruvan: seems everyone's
trade engines were hosed yesterday..I know I should audit my
trades
jurov: not going into
that discussion now... see ya later
guruvan: ++
ThickAsThieves ;) not pliable....but consistent.
ThickAsThieves: i just mean
that we make plenty of reasonable requests and suggestions
that end up being painted as absurd of
they conflict with mp's original decision
jurov: it will help me not
to have a mess in books eventually
jurov: checked
their history
jurov: anyway, will do
thorough check later. but it would help me if anyone who did anything in coinbr during
that
time
ThickAsThieves: now i have
to go back and audit all my fucking excercises
Bugpowder: After
the
trade rollback, a NEW order appeared with a #
that was higher
than an order I placed AFTER my fill at 122
jurov: hmm, coinbr did complain about more inconsistencies
than necessary, but looked quite benign
Bugpowder: I didn't notice
this order number discrepancy before
jurov: so
these
trades got rofled back?
jurov: yes. but am
tired and
the scrollback looks hairy
ThickAsThieves: i did
try
to buy puts at
the same
time as Bug, but I was
too late
jurov: ThickAsThieves, so you were affected
too?
Bugpowder: You see, following my 122 order, I placed
this order, which did not get filled
ThickAsThieves: mp, do you have a log of when
the bot vwap lowered from 227.18 yesterday?
mircea_popescu: the reason it lasted
too long is
that
the server itself was being isolated from syncing
through being ddosed
to as much as it could
take
mircea_popescu: the problem is
the webserver he was directed
to for
the stat was inconsistent weith
the
trade engine master
mircea_popescu: receipt just says "we received your order".
this isn't really
the problem.
mircea_popescu: 's no way
to know what happened
to
the guy's
trade when you issue
the receipt.
jborkl_: mp, sorry
to do
this again, deposit
mircea_popescu: it is possible (if unlikely)
these days for
that state
to be messy
Doffx: I find it somewhat ironic
that
they store
their bitcoin backups at banks
ThickAsThieves: wouldnt matter of being
the same second causes glitches
Scrat: master/slave can still be done with single
threaded setup
Bugpowder: It's a shame
that
the bot does not have a
timestamped receipt
to compare against mine.
Scrat: pgp: a
true multimaster system requires
two phased commits
pgp: can't run an exchange
that way - you can't have single points of failure...
mircea_popescu: material errors happen. my job of course is
to keep it
to a minimum.
mircea_popescu: sometimes
the police batters down your door and you were
the wrong guy.
pgp: unless, of course, you prefer a single
threaded, single server solution for your exchange...
ThickAsThieves: but surely your system is gated
to only give receipts as proof of confirmed purchase, no?
pgp: we deal with occasional race condition-type issues from
time
to
time - happens
mircea_popescu: Apr 11 12:27:16 <mircea_popescu> this promises
to be a bumpy weekend.
mircea_popescu: Apr 11 12:27:12 <mircea_popescu> okay, everyone get your
trades
through if you were contemplating anything
mircea_popescu: it hasn't been happening since
the january upgrade at all, but
then again
ThickAsThieves: easy answer is mp shut off bot manually
to protect puts
MJR_: always showing up late
to
the party
pgp: guys - equity, option and futures exchanges bust
trades for all sorts of reasons everyday all day long...
Bugpowder: Was
the bot going offline a response
to
the purchase coming across
the
ticker here? Or was it just a coincidence?
ThickAsThieves: i still dont see how
that matters if you got a receipt
Bugpowder: Whether
that happened before or after
the actual bot cancellation, I have no way of knowing