Quote from TapeFighter:
But using third party software on something which points to a brokerage account...eehheee.. he. :eek:
Quote from OldTrader:
Evidently you see some type of problem? You'll need to be somewhat explicit. By the way, I've used both with zero problems. So I'll look forward to your answer.
OldTrader
, but of course they can not legally use it in the comfort and privacy of their home because it is patent violation? Please reply with references - I am not going to risk my ass for free.Using a 3rd party API software such as the one's in the market is completely safe. API software has no access to your password. I know this for a fact. Unless they install a key logger, which I doubt. Then you need to worry about a lot more than your IB password. Start worrying about all bank, credit card password, etc. etc. - you get my drift. And with a securID token that IB supplies, you are protected even from a stolen password.Quote from TapeFighter:
The problem I see is that should you use third party software as a frontend for your brokerage account, you must be completely sure that such third party is reliable. You don't want other people to have a chance to get access to your account number/password because if they do you're toast.

I don't see how it could fail.Quote from DarthSidious:
@TapeFighter, even if what you are suggesting can be done (which I doubt), you still can't use it in US.
The internet does make territorial rights a bit messy, but I think the problem would be that TT's lawyers would simply argue that IB, if supplying their US clients with the software, would effectively be importing the software into the US - which would be an infringement. It would be difficult for IB to claim that they don't know where the software is being dowloaded to or where the client is located, because they do.Quote from TapeFighter:
Hey, wait a moment. TT's patents are U.S. patents right? If so, couldn't IB register its TWS software in name of one of their European branches?