Many people seem to be concerned about IB's ease of implementation. I agree with this concern. TalkBoard should not ask for the Moon on the basis that maybe it will work and maybe it won't. Otherwise we lose our influence for crucial upgrades.
Accordingly, I need to find out exactly what IB can do with their existing software and what would need new coding. I pledge to do that and incorporate my findings and TalkBoard member preferences before any call for a vote.
I wanted to start with a sky is the limit discussion so as not to bias our thinking toward what IB already has. I think that has been accomplished. At this point I think it's OK to peek at what vBulletin can do for us and let that inform our preferences.
As to pushing a proposal, I have stated my objective: to find the best consensus proposal. If the best does not turn out to have 6 supporters, so be it. I have made no effort to count votes for drafts because I know I haven't yet addressed all concerns. I'm not even sure all the concerns have been mentioned yet. This process seems slow because it is slow. I want to measure many times before cutting.
Bolding mine: Will you be sharing this publicly or keeping it as "inside information"
as you noted in your post here?
Originally Posted by
CMK10
Straw man argument. If IB says "we can either get you a Like Button OR a better mobile app" your argument would be compelling, but without actual proof that working on this (especially as nsx is hinting it wouldn't be difficult[/B]) is going to burden IB and take away from more active complaints, I don't think your argument holds water.
Bolding mine: "Hinting"
due to inside information which should be shared publicly!