929800+ entries in 0.638s
bgupta: KRS-1: it was below $.10 not
that long ago..
jurov: it is possible ltc will get more attractive since btc starts
to be unusable for micropayments. or maybe not.
KRS1337: hmmm maybe i can buy a
ton right now
jurov: i'm not going
to predict anything. just don't panic and wait it out
bgupta: it's pulled back quite a bit as people who bought ltc at very low prices are
taking profits
jurov: that's bs, it went up before
that announcement
bgupta: KRS1337: Dude ltc hit an all
time high on btc-e based on rumos
that mtgox is gonna start allowing ltc
trading
there..
jurov: KRS1337: just inform yourself at recent mtgox happenings.
they are just seriously inept.
bgupta: am
trading AM but not
trading on MPOE yet.
KRS1337: so i can probably
transfer
them
to another exchange? I see people on btc-e losing
their asses
jurov: and if you absolutely must
trade btcusd, bitfloor seems
to be rising.
KRS1337: jurov: idk..i see ltc
tanking
then i hear get away from gox..idk what
to do
jurov: bgupta,
trade mpex stocks instead :D
bgupta: jurov, where else can I
trade btc with liqudity
bgupta: ltc had rally on mtgox rumor/pseudo-news.. (that mtgox was gonna
trade ltc)
jurov: imho coinlab hit some major snags with
these alphas, hence no update
KRS1337: great friday morning i woke up
to
KRS1337: will I lose my btc investment
too soon? wtf is going on
KRS1337: so
the ltcs at BTC-e are worthless, but
tthe ltc's at another exchange arent?
bgupta: so jurov you aren't gonna wait
to see if mtgox wil follow
through?
jurov: so more ppl did
the same, i guess
bgupta: KRS1337: What is your question? IE: WHo are you
talking
to?
gribble: MtGox lag is 0.270389 seconds. During
this
time, light
travels 0.000541856528574 AU. You could have sent a bitcoin
to
the other side of
the Earth, along
the surface (0.0001339 AU).
gribble: There are currently 31105962 bitcoins demanded at or over 0.0 USD, worth 10993520.0394 USD in
total. | Data vintage: 40.9189 seconds
gribble: BTCUSD
ticker | Best bid: 137.50339, Best ask: 137.99979, Bid-ask spread: 0.49640, Last
trade: 137.99979, 24 hour volume: 67917.79154725, 24 hour low: 128.00100, 24 hour high: 142.12000, 24 hour vwap: 134.97076
bgupta: So are
the bot algos relatively public?
Trying
to understand why some spreads are so wide and others aren't? Or are
the less
tight spreads situations were
there is a human counterparties on
the book?
mircea_popescu: well,
the
thing is, i'm really uninterested in oppinions. i am stating facts.
bgupta: You guys don't even directly compete, so
that makes comparison even harder. Anyway
this is
turning into a bit of a rathole.. IE: we are probably not going
to change each others opinions.
mircea_popescu: the criteria is having customers serviced within
the day
bgupta: there are many other ways
to measure..
those were just
two examples.
bgupta: well it depends on what your criteria of comparison is… If a pretty site is
the criteria,
they win.. if never having been hacked is
the criteria you win. It's not balck or white.
mircea_popescu: obviously he doesn't have a prayer in hell
to compete seeing how he handles < 1k and i do over 1k. of course my service would be better.
mircea_popescu: wehn he comes back wityh "no we're better" he's getting
the bitchslap.
mircea_popescu: when i say you suck and mpex owns you, he says "this is
true"
bgupta: (I was
third level support, and it generally
took a long
time
to get
to my desk, and if it did it wasn't
trivial
to solve.
bgupta: (Saying
this because I have worked in customer service orgs in
the past.
bgupta: If it fits in script
they can reply within 20 mins, if not it needs
to be escalated
bgupta: I
think
that
they are at a scale
that
they are using "helpdesk staff"
that are largely following scripts.
mircea_popescu: then again i guess
that's asking a little much,
they probably don't have
the
technical ability
to do anything other
than read
tickets from
their host.
mircea_popescu: it says specifically what i wish from a service
that aspires
to be halpful.
bgupta: let's see if
they will.. what do you want
to know?
bgupta: I'm reading it as we
take care of simple issues in 20 minutes… complex issues or outage related issues exluded.
mircea_popescu: and
they are still being useless. not saying anything concrete about
the ddos
bgupta: well,
their PR matched my read on
the situation, as a number of btc sites where were being hammered at
that
time.
mircea_popescu: it also means
that
the ONLY cases where a
ticker
takes over 20 minutes is when either a.
there's no info or b.
there's an outage and
the
ticket relates
to
the outage.
bgupta: I don't read "when issues are not simple user-specific issues (or linked
to an outage)" as "when issues are not simple user-specific issues
that are linked
to an outage"
mircea_popescu: that people in general read crap like
their recent release and
think something was said is a property of large crowds of people.
bgupta: well. I'd be curious
to know what
they mean by "simple user-specific issues" IE: Does
that preclude "complicated user-specific issues"?
mircea_popescu: it also means
that
the ONLY cases where a
ticker
takes over 20 minutes is when either a.
there's no info or b.
there's an outage and
the
ticket relates
to
the outage.
mircea_popescu: This means
that ALL
tickets
that are properly spelled out and affect a single user are handledwithin 20 mintes.
mircea_popescu: what he said was : "Most open
tickets have a resolution within 20 minutes. Remaining cases are when
there is not enough information, or when issues are not simple user-specific issues (or linked
to an outage)."
bgupta: they didn't say everything..
they said most.. my
take is if
they handle more
than 50% in 20 minutes…
that means
that statement is correct..
the rest could
take weeks/months.
mircea_popescu: which makes him a liar (again, for
that matter, no big deal, it's banal by now)
mircea_popescu: except
the forum is replete with cases
they do no such
thing.
mircea_popescu: we are discussing
that mpex handles everything within
the same day, and
to counter
this
tux claiomed
they do it in 20 minutes.
bgupta: which isn't really something
to brag about
mircea_popescu: or for
that piece where some new guy was complaining about mtgox
telling him
that his funds are locked and "they'll get in
touch with
the developers"
to fix it.
mircea_popescu: look for
that classic piece on
the part of inaba where he's been dicked around for months over 20k
mircea_popescu: but if you're curious, do a search for mtgox, see what
turns up.
bgupta: For some reason I
thought
that it was you… since you are always linking
to posts by said avatar.
mircea_popescu: i'm not saying
this
to exclude you, just saying,
this is all very banal crap
bgupta: Your evidence
that
they lied is a post from you claiming
that
they lied.. oh, mpoe-pr isn't you?
bgupta: "I won't bother
to compile
the endless list of proof
to show you just lied" Why not?
mircea_popescu: when mtgox hinted
to a dddos
there's nothing but pr fluff.
mircea_popescu: bgupta
they were not
transparent about either.
they are not
transparent now either. i have no idea what you are
talking about.
mircea_popescu: they are of
the persuasion
that pr is bullshit & lieing as much as possibkle.
bgupta: and what
they were doing
to mitigate
the issue
bgupta: They were very
transparent about
their screwups leading
to
the
theft of a large amount of btc.
mircea_popescu: for
the other, whats some random site
trying
to leech hits by republishing random content
to dow ith anything ?
bgupta: You are basically saying
they are now lying
to
the world.
bgupta: historically mtgox has been pretty
transparant about owning up
to
their problems
gribble: BTCUSD
ticker | Best bid: 136.00001, Best ask: 136.60000, Bid-ask spread: 0.59999, Last
trade: 136.60000, 24 hour volume: 67059.71450567, 24 hour low: 128.00100, 24 hour high: 142.12000, 24 hour vwap: 134.51139
mircea_popescu: Apr 05 06:06:48 <ThickAsThieves> mp, did you do a hacker bat signal
to ddos mtgox on
the rally
to 147?
bgupta: and
that mtgox crashed under
the load of people selling?