One hell of a weekend we've got going here!
Topic: Wall Observer BTC/USD - Bitcoin price movement tracking & discussion - page 30537. (Read 26710372 times)
January 04, 2014, 05:16:02 PM
January 04, 2014, 05:15:17 PM
January 04, 2014, 05:14:44 PM
This Peter Wynn character just has to suffer some unfortunate mental disorder. He speculates that BitPay added a backdoor for Zynga and that's how money disappeared from his BTC-e account because BitPay also has a backdoor to BTC-e, or something CRAZY. His profile says he's a "crypto prodigy", but people are having to explain password hashing to him. Meanwhile he seems to tweet about once per 15 seconds. Could be a manic episode maybe?
January 04, 2014, 05:13:13 PM
looks like BS:
What is BS,please?ok,I got it BullShit
January 04, 2014, 05:12:54 PM
Looks like he's still insisting something is going on with $80m, seems odd, he seems pretty reputable. More to this than meets the eye I think, maybe his twitter has been hacked :p
https://twitter.com/petertwynn
https://twitter.com/petertwynn
January 04, 2014, 05:10:00 PM
January 04, 2014, 05:08:35 PM
I was just informing that it went from 825 to 810 in a few minutes, so far as i know thats a drop.
you,pietje and Miz4r are talking about a drop, but this is quite a normal swing in BTC-trading January 04, 2014, 05:05:25 PM
January 04, 2014, 05:05:05 PM
https://twitter.com/bitpay
BitPay @bitpay 2m
FAKE Report - BitPay has not been hacked. We reserve all legal rights for those responsibl
BitPay @bitpay 2m
FAKE Report - BitPay has not been hacked. We reserve all legal rights for those responsibl
'We reserver all rights for those responsible' i hope they make an example of these people.
January 04, 2014, 05:04:59 PM
So we saw a $10 drop on Bitstamp because of an unsubstantiated rumour, the FUD worked a little bit better on btc-e but even there not that many people fell for it. If Bitpay really was hacked we would have probably seen a 50% drop in price within a couple hours.
Of course without any good reason. January 04, 2014, 05:01:44 PM
Bitpay just confirmed via twitter, its FUD.
January 04, 2014, 05:01:15 PM
https://twitter.com/bitpay
BitPay @bitpay 2m
FAKE Report - BitPay has not been hacked. We reserve all legal rights for those responsibl
BitPay @bitpay 2m
FAKE Report - BitPay has not been hacked. We reserve all legal rights for those responsibl
January 04, 2014, 04:59:13 PM
So we saw a $10 drop on Bitstamp because of an unsubstantiated rumour, the FUD worked a little bit better on btc-e but even there not that many people fell for it. If Bitpay really was hacked we would have probably seen a 50% drop in price within a couple hours.
January 04, 2014, 04:56:51 PM
Tried even your plugin , seems ok for me.
Certificate Patrol can't tell you if a cert is valid or not, but what it does do is remember which CA signed a certificate and warn you of something changes in a way that looks suspicious.What I meant is that I see the same info as displayed by chrome , not what you have posted in the screen.
January 04, 2014, 04:55:00 PM
the cert is just for *.twimg.com, though.
It seems I'm getting yet another one for that domain: Cybertrust Public SureServer SV CA
The really strange thing is that Chrome sees the expected Verisign certificate, while Firefox is being given one signed by a different CA.It seems I'm getting yet another one for that domain: Cybertrust Public SureServer SV CA
have you tried shift-reload (or clearing browser cache) in both browsers to see if that changes anything?
January 04, 2014, 04:54:22 PM
Tried even your plugin , seems ok for me.
Certificate Patrol can't tell you if a cert is valid or not, but what it does do is remember which CA signed a certificate and warn you of something changes in a way that looks suspicious. January 04, 2014, 04:53:20 PM
the cert is just for *.twimg.com, though.
It seems I'm getting yet another one for that domain: Cybertrust Public SureServer SV CA
The really strange thing is that Chrome sees the expected Verisign certificate, while Firefox is being given one signed by a different CA. It seems I'm getting yet another one for that domain: Cybertrust Public SureServer SV CA
January 04, 2014, 04:52:55 PM
Is this something I don't have a clue what it is? Yup.
Please enlighten a fellow bit coiner who hasn't yet recover from the new year party.
Something interesting is happening.Please enlighten a fellow bit coiner who hasn't yet recover from the new year party.
When I visit Twitter with one web browser, I get an SSL connection with a certificate signed by VeriSign, the same one that I've always seen from Twitter.
However, when I visit Twitter using Firefox, then the connection is inexplicably signed from a new CA. It's almost as if there's something in the middle of the connection trying to do something nefarious.
Check with all my browsers I get the same certificate.
Tried even your plugin , seems ok for me.
Interesting
January 04, 2014, 04:52:25 PM
Mtgox Buy Wall @ $910 is magnificent! I salute you, wall! 
January 04, 2014, 04:51:14 PM
Is this something I don't have a clue what it is? Yup.
Please enlighten a fellow bit coiner who hasn't yet recover from the new year party.
Something interesting is happening.Please enlighten a fellow bit coiner who hasn't yet recover from the new year party.
When I visit Twitter with one web browser, I get an SSL connection with a certificate signed by VeriSign, the same one that I've always seen from Twitter.
However, when I visit Twitter using Firefox, then the connection is inexplicably signed from a new CA. It's almost as if there's something in the middle of the connection trying to do something nefarious.
the cert is just for *.twimg.com, though.
It seems I'm getting yet another one for that domain: Cybertrust Public SureServer SV CA
EDIT: akamai is an organizational unit of twitter now?
These content delivery servers are all over the world. Maybe there's a reason for a large network of those to have certificates from different authorities and your ip range got switched to a different one or something.
Jump to: