Search content
Sort by
Showing 20 of 40 results by maverick1337
Re: WARNING: Do not upgrade Google Authenticator (iPhone), you will loose keys!
Oops, just did...
I hate the red "1" sign on the top right, so I always upgrade everything as soon as it's available.
Just successfully recovered the old version in iTunes. Here is how I did it:
First of first, go to iTunes ASAP, locate your most updated iPhone backup and make a copy before you try any recover trick.
1. delete the new version of authenticator on your iPhone
2. disable auto sync in iTunes
3. Connect your iPhone via USB
4. Click your iPhone, then go to "application" tab
5. On the left side, scroll down, you gonna see the old version of authenticator, install it.
So close...
I hate the red "1" sign on the top right, so I always upgrade everything as soon as it's available.
Just successfully recovered the old version in iTunes. Here is how I did it:
First of first, go to iTunes ASAP, locate your most updated iPhone backup and make a copy before you try any recover trick.
1. delete the new version of authenticator on your iPhone
2. disable auto sync in iTunes
3. Connect your iPhone via USB
4. Click your iPhone, then go to "application" tab
5. On the left side, scroll down, you gonna see the old version of authenticator, install it.
So close...
Did that and still didn't work. When I deleted the new GA app (or when you delete any app) it asks if you want to delete all the data that comes with it. In order to delete any app you have to say yes, is that why it probably didn't work? I know I've backed up my iPhone within the last few months so it doesn't make sense to me why it's not there.
That's because on the chart to the left you're looking at the 15-min interval (upper left corner) and on the bot it's on the 1-hr interval (at the top). I could be wrong though.
TobbeLino, I know this is not part of Goomboo's system but there are two requests I have. Although dangerous" a lot of ppl would like to see a hold on sells until the buy they paid is reached with the Fee. There are times when I have done an extensive advance advance study and might be say 85% sure that a price of so and so will be reached. Then then a hiccup and I get sold short only to see I was right a few days later. The 2ed is a tailing stop. Say 5% with avg, ... or something like that. Both should not be default but a little box you can tick in.
If I get the time I'll try to implement some experimental functions that takes the price you paid into account, e.g. "don't sell with loss". And maybe some kind of stop loss (need to figure out how it's supposed to work together with the other bot-strategy though, as the stop loss logic and the bot-strategy will sometimes conflict)
But right now I'm working on a different feature in the bot...
This has nothing to do with your bot but I was trying to download your new version, 0.2.2.3, and it kept returning a 502: failure. Any other way to download your bot without having to click "zip"?
Would adding a setting in for the fee help at all? Such that it will only sell if it covers the fee? That way it wouldn't sell at a loss. Of course this only works if the price is rising. This might mess with the EMA portion of the bot, but I'm not completely sure if this would help at all. But I am loving the bot! Great work on it and thanks!
This has been proposed by many. But it's a risky strategy imo (based on the highly emotional assumption that the price WILL go up, and every down-trend is just very temporary). It may put you in a very bad position, and all it really does it that it "hides" your loss and make it worse. It will also cripple the EMA-strategy (the strategy is symmetric and should not prefer "buying" over "selling").
But maybe something will show up in the "experimental section" in the future
The bot can fetch the fee from the user info from MtGox, and the latest trades could also be fetched, so it's possible to use the last paid price in the strategy. But be warned: Your last paid price really has nothing to to with where the price will go from here!
Just a quick note on your bot, not sure if this is intentional or not, but whether you check or uncheck "disabled on start," when you close out of the browser and boot it up the bot is always disabled. Basically it's always disabled on start whether you check or uncheck that box.
What happened was the lines were already crossed to buy. When you started the ability to trade the buy threshold was passed and it bought. Well it went down and it passed your sell threshold then sold. Basically, you need to "turn on" your bot when your settings will not automatically make a trade.
I think that is a great idea. But I'm worried about the amount of samples taking too long. Usually when there is a trend it spikes very quickly and can gain a couple dollars within the hour or two you waited for the samples. The same could be for selling. You see the lines go down and you figure you want to sell as quickly as possible but now you want to wait another hour or 2 to see if it's really going down. More often than not it declines very rapidly and spikes up a little and then back down. I try to buy in when there is a clear trend and get out as soon as it looks bad. I guess this is a way to play it safe for the long term but I was wondering what your thoughts are.
I think you misunderstand a bit how a bot works. A bot will never "buy at the bottom and sell at the top". It will always wait and see if the trends seems solid. That's just how it's supposed to work, and that's why it is often (but not always) more successful than myself trading manually
If you try to buy at the very bottom of a swing, and sell at the very top, you will have to take way to high risks all the time, and you will very often find yourself out of synch with the trends (because you bought or sold to early, thinking you where at the bottom/top), and you start losing...Well what happened was I had it set to 30 min. intervals and by the time it passed my thresholds it bought but it was at the very top. I went to bed and it happened to just tank after it bought, then it passed my sell threshold and sold at a loss and I lost $40. I'm trying to figure out how to avoid this happening in the future, any thoughts?
.
Does the succession have to be past your threshold? Say your threshold is 0.2 and the last three samples are 0.15 0.19 and 0.23. Does it buy based off the current trend even before the pass in threshold or do all samples have to be past the threshold (ie 0.21 0.24 0.26 --> BUY!)?Updated version of bot posted on https://bitcointalk.org/index.php?topic=67591.msg2122016#msg2122016
Download: https://mega.co.nz/#!1lUVAC4J!P6KIlB7NRSCTMk66Y1v9xndDZFNTadSI5qfnMVc5NAE
Added volatility to the graph
Made the sound only play when a real transaction goes through because in simulation mode it plays too often.
Added an additional check that the final sample of the EMA is actually trending, so if you have say 2 or 3 EMA samples and the latest sample is actually against the EMA trend it will spot the slight change in direction and wait for the next sample to buy (if it is again back on the trend). This makes the bot slightly smarter and really is a necessity in case the EMA is still above your threshold but volatility is suddenly high because of a sudden change in direction (I will add option to turn that on/off in options later but I believe it should be a default setting to on).
So for example you have EMA set to 3 samples and the EMA comes out in order 0.15% 0.24% 0.21%: this will not buy as the 0.21% suggests trend is not continuous, the previous versions would have still bought in here!.
If it comes out 0.15% 0.24% 0.26%: then this is a continuous trend and should buy.
If it comes out 0.15% 0.24% 0.21% 0.25%: then it skips the 0.21% and because the next one is 0.25% and again higher suggesting trend is staying and should therefore buy.
I think this is smarter, thoughts?
I think that is a great idea. But I'm worried about the amount of samples taking too long. Usually when there is a trend it spikes very quickly and can gain a couple dollars within the hour or two you waited for the samples. The same could be for selling. You see the lines go down and you figure you want to sell as quickly as possible but now you want to wait another hour or 2 to see if it's really going down. More often than not it declines very rapidly and spikes up a little and then back down. I try to buy in when there is a clear trend and get out as soon as it looks bad. I guess this is a way to play it safe for the long term but I was wondering what your thoughts are.Download: https://mega.co.nz/#!1lUVAC4J!P6KIlB7NRSCTMk66Y1v9xndDZFNTadSI5qfnMVc5NAE
Added volatility to the graph
Made the sound only play when a real transaction goes through because in simulation mode it plays too often.
Added an additional check that the final sample of the EMA is actually trending, so if you have say 2 or 3 EMA samples and the latest sample is actually against the EMA trend it will spot the slight change in direction and wait for the next sample to buy (if it is again back on the trend). This makes the bot slightly smarter and really is a necessity in case the EMA is still above your threshold but volatility is suddenly high because of a sudden change in direction (I will add option to turn that on/off in options later but I believe it should be a default setting to on).
So for example you have EMA set to 3 samples and the EMA comes out in order 0.15% 0.24% 0.21%: this will not buy as the 0.21% suggests trend is not continuous, the previous versions would have still bought in here!.
If it comes out 0.15% 0.24% 0.26%: then this is a continuous trend and should buy.
If it comes out 0.15% 0.24% 0.21% 0.25%: then it skips the 0.21% and because the next one is 0.25% and again higher suggesting trend is staying and should therefore buy.
I think this is smarter, thoughts?
eduk, I've noticed you happen to know how far fible1's paid version has developed. As per 2 days ago, Tobbelino's one was much better (not to mention, free). This volatility check addition is a must-have, and I saw it was implemented in fible1's version, too. Any clue on how it performed? Is tobli's version always the best one?
Here is the volatility one I made yesterday https://bitcointalk.org/index.php?topic=67591.msg2122016#msg2122016 which is free because most of it is other peoples work as it is TobbeLino's version with a volatility check, I'm still testing though, I literally finished coding the modification last night and have only run it for about 10 hours today. But it is avoiding sells and buys.
I'm also figuring out other ways to make it smarter, as during stable periods like we've seen these last few days it an be too agressive.
Here's a (very brutal, indeed) fix for everyone having issues with v0 gox apis: v1 work very well indeed!
You need to change the following lines in background.js:
Line 128:
Line 271:
Line 283:
Line 304:
The bot is behaving MUCH better now thanks to the new apis
EDIT: probably the big issue was Chrome using the cached content, which stopped the bot any time it went through an empty page. With the line 128 workaround (above), v0 apis should work well, too!
I can attest that these changes do make the bot work better. Before, when I clicked on "chart" it wouldn't show anything, just a blank screen. Now it actually works and things seem to be running more smoothly. Thanks for delving into this matter.You need to change the following lines in background.js:
Line 128:
Code:
req.open("GET", url);
becomes (preventing chrome to use cached pages)Code:
req.open("GET", url+"?sid=" + Math.random());
Line 271:
Code:
var url = "https://data.mtgox.com/api/0/data/getTrades.php?Currency="+currency+"&since="+since;
becomesCode:
var url = "https://data.mtgox.com/api/1/BTC"+currency+"/trades?since="+since;
Line 283:
Code:
var trs = JSON.parse(req.responseText);
becomes (quite raw, but it works!)Code:
var trs = JSON.parse(req.responseText.replace("{\"result\":\"success\",\"return\":","").replace("]}","]"));
Line 304:
Code:
url = "https://data.mtgox.com/api/0/data/getTrades.php?Currency="+currency+"&since="+since;
becomesCode:
url = "https://data.mtgox.com/api/1/BTC"+currency+"/trades?since="+since;
The bot is behaving MUCH better now thanks to the new apis
EDIT: probably the big issue was Chrome using the cached content, which stopped the bot any time it went through an empty page. With the line 128 workaround (above), v0 apis should work well, too!
EDIT - One thing I noticed in the console, almost every line says "TypeError". What does this mean? The bot works fine but in the console I just see this a lot.
I want to first thank you for your hard work on your free bot. I am a little confused how it trades. According to your description, it buys and sells based on the "absolute difference between EMA %" and that statement worries me. I thought you would initiate a buy when it's positive difference and a sell when the difference is negative. How does it determine when to buy and sell based off absolute values?
I'm very interested in your bot but I have 3 questions. What if I want to sell/buy on my own, does that mess up the bot? Also, can I have it buy off a certain trade frequency, say H1, but have it sell off a different frequency like M15? One last thing, this is a chrome extension right, so can I use it on my Mac and/or PC? What if I log-in to another computer and have it sync over my extensions, does that mess up the bot?
Thanks in advance.
Thanks in advance.
Looks like a good update.
Which update are you talking about?
Can you make the chart widget show the price in the title? Similar to what bitcoinity does with its title.
Give ya some coinage if you do it
Give ya some coinage if you do it
Why not just use http://bitcoin.clarkmoody.com/
They put the price in the title.
This may sound weird but is it possible to have a bot notify you (via email/text/etc) when the EMA lines cross, and that only? I don't want it to automatically trade but to just send me a notification of when they cross so I can initiate the trades myself. You wouldn't have to include any trading data or anything. I know people spend a lot o time and effort on their codes and was wondering if this was possible.
Thank you in advance for any help.
Thank you in advance for any help.