HackerReposA FIELD GUIDE TO OPEN SOURCE
ProSponsor the shelf♧ 0
← Back to top all-time
askmike
gekko
JavaScript2013–2018
askmike / gekko · Archived

gekko

A bitcoin trading bot written in node - https://gekko.wizb.it/

3Distinct people
6Mentions
0Explicit recommenders
10.2KGitHub stars
REPOSITORY AT A GLANCE

What to know before exploring

What it is

A bitcoin trading bot written in node - https://gekko.wizb.it/

GitHub

Where it is used

No documented product use has been verified yet.

What people are saying

No recommendation phrase was found in the indexed comments.

No classified warning is attached to this page. Read the discussions before treating silence as approval.

Also in these discussions

No other repository is repeatedly linked in the same discussions.

This week on Hacker News

Nov 7–Nov 14 UTC · Direct repository links and separately labeled related project stories. Indexed through 11/14/2026, 3:56:07 PM UTC.

No direct repository links were found in the indexed HN discussions over the past seven days. Older discussions are available below.

Mentions over time

HN mentions by year6 dated mentions

Observed mentions: 2013-11-13 17:45:27 UTC to 2018-07-24 08:40:21 UTC.

0122013-01-01 00:00:00 UTC to 2014-01-01 00:00:00 UTC (exclusive): 2 mentions; 1 submissions, 1 comments20132014-01-01 00:00:00 UTC to 2015-01-01 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2015-01-01 00:00:00 UTC to 2016-01-01 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments20152016-01-01 00:00:00 UTC to 2017-01-01 00:00:00 UTC (exclusive): 2 mentions; 0 submissions, 2 comments2017-01-01 00:00:00 UTC to 2018-01-01 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2018-01-01 00:00:00 UTC to 2019-01-01 00:00:00 UTC (exclusive): 2 mentions; 0 submissions, 2 comments2018

Counts come from the repository’s dated source evidence. Index cutoff: 2026-11-02 08:16:59 UTC.

View mention counts and date ranges
UTC ranges include their start and exclude their end. Select a period to filter the source evidence.
PeriodStart (UTC)End (exclusive, UTC)MentionsSubmissionsComments
20132013-01-01 00:00:00 UTC2014-01-01 00:00:00 UTC211
20142014-01-01 00:00:00 UTC2015-01-01 00:00:00 UTC000
20152015-01-01 00:00:00 UTC2016-01-01 00:00:00 UTC000
20162016-01-01 00:00:00 UTC2017-01-01 00:00:00 UTC202
20172017-01-01 00:00:00 UTC2018-01-01 00:00:00 UTC000
20182018-01-01 00:00:00 UTC2019-01-01 00:00:00 UTC202

What Hacker News says

6 sources
Woah great feedback. This is very much appreciated! I'm not sure if going specifically into all of your points right here is the best way forward. But suffice to say I am very happen to hear them :) > the abstractions are wrong and most of the code probably relies on some hidden state that's really hard to debug unless you're the code author. This is very much spot on, definitely something I want to work on. ----- The main reason that everything is so spread out (plugins, web API, internal API, etc. etc) is because a ton of people are doing different things with it. 99% of the people only touch the basics, and they don't need to touch any config file, they can go through the UI that handles all of it automatically (Gekko is focused on tech savy but not perse professional programmers). They don't know what (my concept of) a plugin is, and
Read the rest
they don't care about any API (nor any version for that matter). It's about the other 1% who are kind of spread out over: - people who want to hook into certain lifecycles (to push certain data to google spreadsheets[1] for example) - people who only use subparts of the app, for example to have something that can fetch normalized market data from a number of different websites <- this is a big part of the project, but not the sole, hence it should not dictate versioning. - Or people who only want to create their own prediction making logic (with AI or whatever) and use the execution logic of my app. <- in the process of pulling this out as a standalone library. - people building tools on top of the web API that bruteforces a problem space to figure out new solutions[2]. So all the people that care about the versioning (not the 99%) are exactly the hobby DIY hacking people who want to open it up and take it apart. And it feels impossible to steer them into "don't touch this because the interface is not a standardized API". ----- The main thing I am going to do now is rethink the entire config strategy, because it's a huge mess and I think I am the only one who understands it[3]. [1]: https://github.com/RJPGriffin/google-forms-gekko-plugin [2]: https://forum.gekko.wizb.it/thread-56589.html [3]: https://github.com/askmike/gekko/issues/956
In Be Nice and Write Stable Code
I'm maintaining an open source project[0] and I'm struggling with using SemVer because my "app" doesn't have a single API but a few: At it's core it's a node app. Though I also include a small web server that wraps around it (and a UI frontend). 1. It allows people to write scripts (js) that receives inputs and passes on events based on an API (the strategy API)[1]. 2. It has extensive configuration[2] that sometimes changes form (the config API). 3. It talks to a number of external services (crypto exchanges), over a "common" protocol called the "exchange wrapper API"[3] (I am ignoring the version of the exchange API being consumed). 4. The wrapped webserver comes with an API (REST + WS)[4]. 5. The "core app" is a chain of plugins, when they change the required config/events also change (usually breaking changes 1 and 4)[5]. I could take
Read the rest
all of these components apart (microservice way) and version them separately, but I like the monorepo style I use now where pulling one repo means that everything is working together. Also the fact that (in bug reports) people only have to refer to one version (and when on nightly maybe the git commit if I need more details). But versioning is a mess. [0]: https://gekko.wizb.it/ [1]: https://gekko.wizb.it/docs/strategies/creating_a_strategy.ht... [2]: https://github.com/askmike/gekko/blob/develop/sample-config.... [3]: https://gekko.wizb.it/docs/extending/add_an_exchange.html#Ge... [4]: https://gekko.wizb.it/docs/internals/server_api.html#REST-AP... [5]: https://gekko.wizb.it/docs/internals/events.html#List-of-eve... ------- This is not a criticism, I typed this out in the hope that someone can point me in a sane direction (given the discussion on versioning)
In Be Nice and Write Stable Code
Location: Galway, Ireland Remote: YES Willing to relocate: NO Technologies: JavaScript (full stack), NodeJS, HTML5, vue, react, dataviz (d3), bitcoin, cryptocurrencies, (cloud) devops. Résumé/CV: https://mikevanrossum.nl/cv.pdf LinkedIn: https://linkedin.com/in/mikevanrossum Email: yc@mvr.me Open Source: https://github.com/askmike/gekko About me: Having done a bachelor in digital media means I understand a broad aspect of apps and digital services. While I spent most of my time writing backend code, I do have a passion for clean interfaces and data visualisation.
In Ask HN: Who wants to be hired? (December 2016)
Location: Galway, Ireland Remote: YES Willing to relocate: NO Technologies: JavaScript (full stack), NodeJS, HTML5, vue, react, dataviz (d3), bitcoin, cryptocurrencies, (cloud) devops. Résumé/CV: https://mikevanrossum.nl/cv.pdf LinkedIn: https://linkedin.com/in/mikevanrossum Email: yc@mvr.me Open Source: https://github.com/askmike/gekko About me: Having done a bachelor in digital media means I understand a broad aspect of apps and digital services. While I spent most of my time writing backend code, I do have a passion for clean interfaces and data visualisation.
In Ask HN: Who wants to be hired? (November 2016)

MAKE YOURSELF AT HOME

A few shortcuts

/
Search the collection
?
Open this guide
Esc
Close dialogs and navigation

Your saved repositories and interests stay in this browser.