Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Pascal66 // rebase target: elliot_waves #14

Merged
merged 298 commits into from
Aug 26, 2016

Conversation

Pascal66
Copy link

No description provided.

antonivs and others added 30 commits June 2, 2016 23:59
Conflicts:
	exchanges.js
	exchanges/bitfinex.js
	package.json
Conflicts:
	exchanges.js
	package.json
Conflicts:
	README.md
	exchanges.js
	package.json
Exclude config.js from git for more security and convenience
Remove Makefile, run tests directly with npm scripts
Fix links to point current (0.2) branch instead of master branch
@kuzetsa
Copy link
Owner

kuzetsa commented Aug 26, 2016

This pull request is huge...

Any chance you'd be up to discussing it?

@kuzetsa kuzetsa changed the base branch from master to Pascal66_elliot_waves August 26, 2016 04:39
@kuzetsa kuzetsa changed the title nikiehihsa by kuzetsa Pascal66 // rebase target: elliot_waves Aug 26, 2016
@kuzetsa
Copy link
Owner

kuzetsa commented Aug 26, 2016

A rebase / proper merge can be done later.

For now, I'm just going to stick it in a new branch.

In the future, please try to do better than:

No description provided.

(next time please explain what you're trying to do or why there are so many commits.

@kuzetsa kuzetsa merged commit 4b24e63 into kuzetsa:Pascal66_elliot_waves Aug 26, 2016
@kuzetsa
Copy link
Owner

kuzetsa commented Aug 26, 2016

I haven't tested this...

It's merged to the newly created branch

UNTESTED / download and use if you want though:

https://github.com/kuzetsa/gekko/releases/tag/Pascal66%402016_Aug_26

@Pascal66 Pascal66 deleted the elliot_waves branch August 26, 2016 11:15
@Pascal66
Copy link
Author

Sorry, i think i've made a mistake. I removed this branch

@kuzetsa
Copy link
Owner

kuzetsa commented Aug 26, 2016

@Pascal66 Either way is fine.

It can be dealt with at a later time if you decide you want to do anything with it.

Not sure if/when I might have a look at the code...

I had a bad experience in 2014 after counterparty risk (an exchange / platform for mining hashrate)

They were using my mining hardware but then one day stopped paying me for leasing out usage of my hardware & electricity. It was very upsetting, and I've barely touched bitcoin since then. (including my work on gekko abruptly ending at around the same time.)

... Unrelatedly -- That particular event was also around the time cex.io stopped selling GHS actually (which was the main thing I was using gekko for managing)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.