Originally Posted by
Zorak
I don't think anyone's advocating that.
False. You can also post announcements with screenshots or sample videos and let people decide if they want the new feature or not.
If TPTB are worried a feature will not get enough uptake unless it is forced on people (opt-out instead of opt-in), that may suggest the feature is not compelling enough to cause users to want it.
If TPTB are worried about having engineers waste time on a feature that is not compelling enough to cause users to want it, they could do some UX research, use the results of user surveys, address bugs and user stories that people have raised in the tech support forum, ...
Not saying IB has to, or even
should do any of this -- after all if I don't like it I'm entitled to a full refund of my $0

-- so long as it's acknowledged that they
could.
Thank you for your thoughts.
In this case -- I am not arguing all recent cases -- the only thing people were "opted into" was a feature we did not even plan on including, so we were unable to set it to "opt in." It is now set to opt in. Simple oversight.