Here there is a Google Chrome installer for the 13 version. (Windows Version)
http://www.oldapps.com/google_chrome.php?old_chrome=6373
I download and install it (on Win7) and work great for the clark's tool.
REMEMBER: Is a good idea if you already have chrome installed, first uninstall, afterwards clean de registry (I use CClaner basicly) and when you sure google chrome is really uninstalled then install the 13 version.
Grettings
Topic: Real Time Charting, Order Book, and Time & Sales - page 30. (Read 85544 times)
Enabled for Opera, we're back mortimer!
Sweet...
Sweet...
Just installed Opera, it says it does not support websockets.
You may have to enable support in opera:config.
Just installed Opera, it says it does not support websockets.
Chrome still not working.
Safari 5.1 not holding up either.
Safari 5.1 not holding up either.
Safari 5.1 (7534.50) works for me. Have you tried Opera? (It's actually the second most popular browser in my logs).
And please be sure to complain to MagicalTux for breaking a service that you need to use.
Chrome still not working.
Safari 5.1 not holding up either.
Safari 5.1 not holding up either.
I pushed an update to the platform that should eliminate the order book reversal bug. I'm viewing a working platform in Opera 11.10 and Safari 5.1. Edit: It also works in Opera 11.51.
Opera manages to connect to the secure WebSocket, while Safari has a little trouble and goes with the non-secure one.
Opera manages to connect to the secure WebSocket, while Safari has a little trouble and goes with the non-secure one.
To Bad, This WAS a great product...............
:<
:<
Ouch!
It still works fine in Safari 5.1 and Opera 11.10 for me. This is a lesson to all you developers out there: you MUST be in control of your own data stream! The success of my product is completely at the mercy of MtGox and its API.
Clark, can you add support for tradehill or other exchanges? I don't know if they offer websockets but even a self updating order book (by polling the json api every minute or something) would be quite useful.
That's looking like a better and better idea all the time. I should provide a polling fall back for MtGox as well as add support for the other exchanges.
Clark, can you add support for tradehill or other exchanges? I don't know if they offer websockets but even a self updating order book (by polling the json api every minute or something) would be quite useful.
The socket still shuts down using Chrome.........(and every other browser)
Only thing that works is thru the iPhone..............
To Bad, This WAS a great product...............
:<
Only thing that works is thru the iPhone..............
To Bad, This WAS a great product...............
:<
Well, I've launched the updated code. I now attempt to connect to the secure WebSocket first before trying the unsecured one. Also, you shouldn't see the prices flipping around on the Bid side anymore.
As far as compatibility goes, I'm not sure if there will be any progress for Chrome 14 until MtGox updates its server protocol.
Safari 5.1 and late-model Opera work just fine for me. Firefox 6.0.2 says it's connected, but it doesn't receive anything. Chrome 14 seems to do the same thing.
The error console says
As far as compatibility goes, I'm not sure if there will be any progress for Chrome 14 until MtGox updates its server protocol.
Safari 5.1 and late-model Opera work just fine for me. Firefox 6.0.2 says it's connected, but it doesn't receive anything. Chrome 14 seems to do the same thing.
The error console says
Code:
One or more reserved bits are on: reserved1 = 0, reserved2 = 1, reserved3 = 0
Just wanted to say thank you for the provided free services. So donation is on it's way...
Well thank you very much!
I've been working on compatibility for the latest browsers and fixing the price grouping bug. Stay tuned for the updated code sometime soon.
Yeay, compatibility for the recent Firefox version would be hailed like the Lord. It's the "Lord's update", right?
Just wanted to say thank you for the provided free services. So donation is on it's way...
Well thank you very much!
I've been working on compatibility for the latest browsers and fixing the price grouping bug. Stay tuned for the updated code sometime soon.
Just wanted to say thank you for the provided free services. So donation is on it's way...
Hello,
looks very nice!
Is it possible to export the Time & Sales as CSV (txt) file?
looks very nice!
Is it possible to export the Time & Sales as CSV (txt) file?
You're going to want to check this out for that functionality: http://bitcoincharts.com/about/markets-api/
Hello,
looks very nice!
Is it possible to export the Time & Sales as CSV (txt) file?
looks very nice!
Is it possible to export the Time & Sales as CSV (txt) file?
Has the order book been changed to show the highest bids at the bottom of the page and the lowest asks at the top of the page?
or is this an issue with safari?
or is this an issue with safari?
Yeah, this is an issue with Firefox & Safari. I'll need to clean this up very soon!
Has the order book been changed to show the highest bids at the bottom of the page and the lowest asks at the top of the page?
or is this an issue with safari?
or is this an issue with safari?
The connection issue is detailed a little bit here on the Chromium Bugs Google discussion:
http://groups.google.com/a/chromium.org/group/chromium-bugs/browse_thread/thread/aea7ab1fd995e78b/a8133bbe76e4067e?lnk=raot
Thanks for whoever posted it there. Apparently the MtGox frame format is old, but the handshake is new.
This link has also been posted in the websockets thread here: https://bitcointalksearch.org/topic/m.535523
http://groups.google.com/a/chromium.org/group/chromium-bugs/browse_thread/thread/aea7ab1fd995e78b/a8133bbe76e4067e?lnk=raot
Thanks for whoever posted it there. Apparently the MtGox frame format is old, but the handshake is new.
This link has also been posted in the websockets thread here: https://bitcointalksearch.org/topic/m.535523
I'm wondering how you decide when a direction turn is taken. Do you take a fixed length interval and use a weighted average and compare it to the previous low/high?
The direction is simply all the trades that go one way. I store the last traded price and the current direction. If the next trade is higher or the same price than that last traded price (and the direction is up), we add the volume of the trade to the current direction. If some trade comes along that is lower than the last trade, then our direction has changed to down.
I record the price at the direction change to compute the trend size, and I reset a volume counter as well, so we can see the amount traded in that direction. This really helps in exposing the true size of large orders as they sweep the book of many small orders.
If the time & sales are showing lots of green trades, and then a single red one, we've changed direction. It's as simple as that.
Jump to: