4 ms·

Just a couple of comments on some of your use cases. * I don't use Bitbucket specifically, but what's difficult about mirroring code between two different git

Just a couple of comments on some of your use cases. * I don't use Bitbucket specifically, but what's difficult about mirroring code between two different git instances? I do it between GitHub and GitLab.[0] Local git config just needs to be configured to push to both destinations. Or perhaps I haven't understood the specific "code backup" use case? * The Wimbledon match results vs betting odds could be interesting, but I would think the betting odds should very quickly reflect the match results. At least this would be my experience on Betfair. What's the opportunity here? Is it arbitrage between bookmakers? [0] https://github.com/phillc73/backblazer https://github.com/phillc73/backblazer and https://gitlab.com/phillc73/backblazer https://gitlab.com/phillc73/backblazer

m-i-l 11y ago
I would think the betting odds should very quickly reflect the match results. In actual fact, the betting odds are sometimes updated before the broadcast results, thanks to bookmakers employing courtsiders[0] to transmit scores direct. [0] https://en.wikipedia.org/wiki/Courtsiding https://en.wikipedia.org/wiki/Courtsiding
- mindset 11y ago
  Yes, much like the stock market responds to news, mostly faster than msnbc can discuss these. The issue this app solves is the ephemeral nature of the betting data. A simple scheduling feature allowed me to have historical data easily. Otherwise, go deal with a server, scheduled jobs, etc. Not impossible, just discouraging for many people that can develop, but don't want to deal with the overhead for every little application.
mindset 11y ago
From my attempts, it's not trivial with bitbucket. Beyond that, the functionality for this app also includes slack notification on new releases,and a nice templated email notification on what's changed. That was the request from the guys wanting this app.The point is that an app can do a anything a user wants, tailored to that user. The betting odds app was my own pet app, mostly for testing purposes. I listed it to demonstrate something like this can be done. Otherwise, a server, database and code all have to be setup, tested, and monitored. The idea here is to let developers focus on the code only, and easily publish apps for anyone to use.

m-i-l 11y ago

I would think the betting odds should very quickly reflect the match results. In actual fact, the betting odds are sometimes updated before the broadcast results, thanks to bookmakers employing courtsiders[0] to transmit scores direct. [0] https://en.wikipedia.org/wiki/Courtsiding https://en.wikipedia.org/wiki/Courtsiding

mindset 11y ago
Yes, much like the stock market responds to news, mostly faster than msnbc can discuss these. The issue this app solves is the ephemeral nature of the betting data. A simple scheduling feature allowed me to have historical data easily. Otherwise, go deal with a server, scheduled jobs, etc. Not impossible, just discouraging for many people that can develop, but don't want to deal with the overhead for every little application.

mindset 11y ago

From my attempts, it's not trivial with bitbucket. Beyond that, the functionality for this app also includes slack notification on new releases,and a nice templated email notification on what's changed. That was the request from the guys wanting this app.The point is that an app can do a anything a user wants, tailored to that user. The betting odds app was my own pet app, mostly for testing purposes. I listed it to demonstrate something like this can be done. Otherwise, a server, database and code all have to be setup, tested, and monitored. The idea here is to let developers focus on the code only, and easily publish apps for anyone to use.