> I am sure you can appreciate we are not able to
> comment on any speculative information regarding
> future changes.
Actually, Ross, I can't. Not at all.
When I did technical enablement for products in the Lotus division of IBM several years ago, we went out of our way to keep our business partners informed of the status of their requests, upcoming release vehicles, and the chances of the different requests making it into different releases. This is because they were trying to build a business based on our middleware. We couldn't always do what they wanted when they wanted, but if we gave them the information to plan, they could still plan their business, and adjust their schedules and expectations accordingly.
So I'm utterly mystified at the repeated stonewalling here with comments like the above. I'd love to talk with however set that policy and hear from them how they expect it to encourage engagement in their platform, or what horrible risk they are avoiding by keeping the adopters of their platform in the dark.
At this time all Echo interactions must be initialized by the user speaking to the device.
I am sure you can appreciate we are not able to comment on any speculative information regarding future changes.