If he loses because of an 8 sec lag he should start looking for another tradeplan.
Remarkable, 8 trades buying the high and selling the low, were the high and the low were separated exactly by 8 seconds each time?
Sporadic Connectivity @ eSignal
- Thread starter JayF_eSignal
- Start date
If he loses because of an 8 sec lag he should start looking for another tradeplan.
Remarkable, 8 trades buying the high and selling the low, were the high and the low were separated exactly by 8 seconds each time?
You're right, trader28, you must know everything. I suppose there is no possible situation where this could occur. I trade off of charts, jagoff, so when i think i'm buying a confirmed breakout, the stock has actually failed to break out, i'm buying on the way down and then get stopped on my pre-determined stop. At first I thought it was just volatility and had already lost on 5 trades before anyone realized there was latency. So GFY. The last 3 trades I'll pin on myself. Does that make you feel better?
My methodology, spike, involves using precise entry points to limit my risk. My entries are price sensitive, not time. 8 seconds lag has less to do with it than displaying wrong prices. Wrong prices mean improper entry which means getting stopped out quicker which means losing trades. Comprende?
I pay over $200/month for this crap ass service, there is absolutely no reason that I should have to pay to adjust the way I do things because they can't get their act together over at esignal. I want to do battle with the marketplace, not someone who's supposed to be providing me a service.
And before I can get another wise-ass response, yes, I will be looking at alternate quote servers.
I pay over $200/month for this crap ass service, there is absolutely no reason that I should have to pay to adjust the way I do things because they can't get their act together over at esignal. I want to do battle with the marketplace, not someone who's supposed to be providing me a service.
And before I can get another wise-ass response, yes, I will be looking at alternate quote servers.
This is what YOU said:Bought highs and sold lows.
So due to the 8 sec difference all the highs became the lows and all the lows became the highs. That's what you say.
You didn't get 2 wise-ass responses, but 2 embarrassing responses for you.
No matter what you say trading is YOUR responsibility, you KNOW downtime is part and parcel of the game, if it affects your bottom line that much then it is YOUR responsibility to have a redundancy feed in place, you can piss and moan until the cows come home but this is business, YOUR business.... now fecking run it like one!!!!
A workman does blame his tools when they're broken. A carpenter can't hammer in a nail properly if his hammer is broken. It in no way affects his skill as a carpenter to have a broken hammer. It affects his ability to get his job done. If the carpenter continues to have problems with the same hammer, he might warn his fellow carpenters not to buy that hammer.
I know that ultimately I am responsible for my losses. And yes I should have backup systems and backups to backups in place. However, like I said these losses occurred BEFORE anyone knew there were latency issues. Down time is one thing, wrong time is an entirely other situation. If I system goes down and I don't have backup, I don't trade. Sure I miss opportunities, but I don't lose money. If a provider is providing bogus info, then it becomes detrimental.
Again spike, it all has to do with entry points. I didn't buy the "absolute high" and then sell the "absolute low" within 8 seconds. Thats not whats happening. The problem occurs when ur stop is set against a price that is higher than what u actually purchased at. For example: If i am buying a stock at the figure and than setting a .25 stop, my stop is at .75. If i actually bought the stock at .80, then my stop is at .55. If i think i'm buying the stock at the figure, but actually get filled at .90 and my stop is at .75 its only .15 away, which happens to be too tight for the range of that particualr issue. Boom. Stopped out, loss of .15. And so on and so on.
Now quit being esignal sanctimonious syncophants and just admit that it sucks.
I know that ultimately I am responsible for my losses. And yes I should have backup systems and backups to backups in place. However, like I said these losses occurred BEFORE anyone knew there were latency issues. Down time is one thing, wrong time is an entirely other situation. If I system goes down and I don't have backup, I don't trade. Sure I miss opportunities, but I don't lose money. If a provider is providing bogus info, then it becomes detrimental.
Again spike, it all has to do with entry points. I didn't buy the "absolute high" and then sell the "absolute low" within 8 seconds. Thats not whats happening. The problem occurs when ur stop is set against a price that is higher than what u actually purchased at. For example: If i am buying a stock at the figure and than setting a .25 stop, my stop is at .75. If i actually bought the stock at .80, then my stop is at .55. If i think i'm buying the stock at the figure, but actually get filled at .90 and my stop is at .75 its only .15 away, which happens to be too tight for the range of that particualr issue. Boom. Stopped out, loss of .15. And so on and so on.
Now quit being esignal sanctimonious syncophants and just admit that it sucks.