IB Suggestions & Improvements

[jimrockford]

OK, I have 2 suggestions.

First, IB should put higher priority on making old features, and basic core functions like documentation, and order execution and routing, and quality control, improve and actually work and work reliably and work better. IB should, in order to achieve this, temporarily stop adding new features. Period. IB should refocus on basic quality issues. Bells and whistles are nice, but not at the price of what has been neglected. If a job is worth doing, its worth doing right. I predict this posting will fall on deaf ears, but I say give us more basic quality, and less of the advanced fluff.

Second, we need to start a new thread, which doesn't have the same restrictions which this thread's originator has placed on this thread.

 

[Babak]

jim, regarding your first point: I and others have made the same plea. Hopefully IB will listen.

re your second point: I simply do not want the thread to deteriorate into a bitching session because I don't think anyone will benefit - certainly not us as traders and certainly not IB as they tend to get defensive and not listen when attacked.

So again, I ask that we all please include a positive suggestion on how IB can improve. That will help both IB and traders.

 

[jimrockford]

Babak,

I'm surprised that you actually agree with my first point.

Let me just say that, in my opinion, the concept behind this thread influences IB in exactly the opposite direction than we both want. Yes this thread avoids criticism and confrontation, so IB is more willing to listen, but this only serves to fortify their perception that they are doing the right thing, in sacrificing quality for quantity of features.

I do, however, respect and appreciate your effort at making things better, even if I don't agree with your execution. And maybe this thread does at least help get IB more in the habit of listening to customers.

 

[Babak]

jim, just like other IB users my priority is the stability of the platform over any bells and whistles. Having said that, I must point out that I don't think these two things are necessarily mutually exclusive. Once stability is ensured, I would like to see added functionality (as long as it doesn't mess with stability of course!).

I've had indications from IB that they understand this and are indeed implementing a wholesale overhaul of TWS to make it modular. This would enable you to have a stripped down, lean mean, trading machine. Or to add all the extensions and bells/whistles to your heart's content. In short, it would meet both criteria: stability and customization.

So please keep the suggestions and ideas coming.

 

[giggollo]

I would like to see IB offer an alternative per-ticket commission structure with ECN charges/rebates being pass through to the client...why not!....anyone else would like to see this?

 

[Moreagr]

I would like to see the TIKI symbol added for the DOW PLEASE I am not asking for much now am I??

 

[JackR]

Concur with TIKI. Really not a difficult indicator to construct.

Jack

 

[zf trader]

Has the problem with QM charting been fixed yet? In the past when I opened a QM chart my computer would freeze and I would have to restart it. How about QG-do those charts work.

 

[just21]

Are IB going to change the backfill API so that Neoticker and other programs can use this database? There seems to be a problem that 3rd parties have encountered. Below is an email from tickquest, they seem to have a problem with the backfill.



IB backfill will not be added until after they correctly implement
the necessary changes to their historical data API that
we and other 3rd party suggested.

For daily normal usage, the current form of the IB API does not work.

It is similar to the situation of IQFeed 1 year ago. IQFeed historical
data
request ability is now mature and stable.

Regards,

Support

 

[dcraig]

Quote from just21:

Are IB going to change the backfill API so that Neoticker and other programs can use this database? There seems to be a problem that 3rd parties have encountered. Below is an email from tickquest, they seem to have a problem with the backfill.



IB backfill will not be added until after they correctly implement
the necessary changes to their historical data API that
we and other 3rd party suggested.

For daily normal usage, the current form of the IB API does not work.

It is similar to the situation of IQFeed 1 year ago. IQFeed historical
data
request ability is now mature and stable.

Regards,

Support

I think this is nonsense. While I do not particularly like the TWS historical data API, and it is a bit nasty to code to, it does work reliably and will retrieve up to 6 months of data as IB state in their release notes. If I can manage to code to it, then I'm sure Neoticker can manage it if they put their minds to it.