Registered: Sep 2011
01-02-12 03:33 PM
First of all - QT *might* continue working with TDA just fine in years to come. They pulled it from the listing of "supported third party" applications on their website, but that doesn't neccessarily means, that QT won't work with their datafeeds, authentication servers just fine for a long time. It's just that it's been said by some (on this forum) that *official* support ends, as far as I know.
I'm not aware of any other method of aiding the case, than just simply calling TDA as often as possible (let's make an effort! let them know we take this seriously), writing support tickets, requesting TDA to keep allowing QT connections to their servers, datafeeds and trading, and to have this continued in future. They will/might persuade to use their "better, faster, with more features" platform (such as Thinkorswim) instead. However, if someone prefers "outdated" QT as their platform of choice, they should accept that, and be thankful we keep using their business. After all, in trading, nobody should tell you what tools you should use, it SHOULD be your choice.
QT integration with TDA service was the only reason I chose TDA in the first place, and if QT stops working with their feeds/trading, I might go find some other provider that does.
They make money on our trading after all, and should listen to the customer's requests. If they hesitate, TDA has to be aware that they might loose the customer because of simple thing like that.
Also, it'd be great if someone with enough knowledge on the subject (Jerry Medved?) would help the community by posting information on how to update QT modules to keep up with any protocol changes for TDA and other providers.