There has been a horrendous change to Bitsgap affecting all traders. I want this escalated NOW to senior management and I want Bitsgap changed back so that if I have multiple web browser tabs open to Bitsgap, I can have each tab open to different crypto coins so that I can easily scan the market conditions for cryptos.
For example, I open a Chrome browser tab on Bitsgap with BTC. Then I want to look at ETH so I open a second browser tab on Chrome. But when I look at both Chrome tabs, they have both changed to ETH.
Then when I try to open a third tab on Bitsgap with TURBO, then all the tabs suddently change to TURBO and there is no more ETH or BTC displayed. Bitsgap forces all web browser tabs open to Bitsgap onto the same crypto coin! This is insane.
This is on the Bots pages.
I have never seen Bitsgap do this before in years of using Bitsgap. I was advised by Customer Support chat that this was due to a product change, but there was NO notice and I used Bitsgap yesterday, just about 7 hours ago. The bottom line is that if this change is not corrected so that we can use multiple tabs on Bitsgap to see different cryupto coins, this makes Bitsgap USELESS for trading.
This change to Bitsgap only displaying one crypto coin on multiple browser tabs is costing me hundreds of dollars for today, and potentially thousands of dollars a week.
I trade on the 1 minute time frame, so I need to be able to easiily scan multiple cryptos to check on prices. I need to keep BTC and multiple other cryptos on my web browsers, particularly since BTC affects the entire crypto market.
It is too time consuming to have to constantly change 1 web browser to BTC and then to alt coins and back again, over and over again. It’s critical that I be able to see changes to market conditions quickly.
Please change back the Bots pages so that each web browser on Bitsgap can display a different crypto coin. If this change is not reverted, I will definitely have to find another bot trading service other than Bitsgap, and I’ll be telling as many people as possible to avoid Bitsgap.