Quote from: Xenius on April 24, 2013, 06:06:04 PM

Quote from: deepceleron on April 24, 2013, 10:31:44 AM

sierrachartfeed.exe

Great. That way i'll learn python pretty soon..

Are you going to up it into the github repo?

I think I've got everything done worth doing, and it shouldn't break or have any more buffer overflow vulnerabilities than it did before. If bitcoincharts is down or 500, it errors out. If the data API changes to something else or is blank, just the current ticker works. If there are periods of data without trades in history (like from ddos) the logic doesn't care.

I'll just refactor to minimize diff lines before I put a pull request in (and create an account, install git, etc). Someone else could check it in; slush could look if I broke his functions, etc; it's public domain.

Quote from: Xenius on April 24, 2013, 06:06:04 PM

Quote from: lucif on April 23, 2013, 04:48:09 PM

I changed mtgox feed to native SC data source: https://www.sierrachart.com/SupportBoard.php?ThreadID=527

Why there's a difference in feeds? Different apis? Websockets vs socketio?

SierraChart recently added their own mtgox data feed (and a $10/month bitcoin-only subscription).
Before that, and again now, the trial/free version of SierraChart can use data downloaded from bitcoincharts/mtgox when processed by the feed/bridge.