No matter how much you qualify an answer: “yes, but it’s extremely early in design, we may not be able to find the right manufacturers so it may not happen at all, but the earliest possible date would be late 2022”, there is a segment of people that will have an expectation that you will deliver the product before 2023 and will be upset if you don’t.

Sounds sensible. They're working on it but wouldn't want to have an unexpected obstacle turn into broken promises.

That is right. I’ve answered a few questions in these comments where the answer is basically: It’s technically possible, there is a plausible market need, we think it is worthwhile to do, and we’ve designed for it architecturally, but we can’t commit to a specific date because there are always implementation risks, supplier risks (especially this year), and a large number of programs we have to prioritize between as a small team.

This is the perfect answer. Paste this into every feature request thread.

Haha, yeah, that is exactly the long form of what I expected it meant.

Sounds good. Thanks for the answer.