I'll go first. I can understand both sides of this argument. The thread generated thoughtful conversation and valuable feedback for us to consider. However, when the original poster had to step in around post #153 to redirect the discussion back to the original topic, it became clear that the conversation had drifted significantly. At that point, closing the thread was a reasonable step to preserve its original intent.
As you said, we’re not children here—everyone is generally trying to be helpful and contribute constructively. When a thread is closed, it’s rarely about controlling the narrative or shutting down feedback. More often, it’s simply about keeping discussions focused, productive, and respectful of the original purpose so the feedback can actually be acted upon.
Here is a summary of the key takeaways from the 161-post thread that I’ve already shared with our team:
- Dashboard usability and flexibility need improvement.
- There are notable gaps in support for European users.
- Some important Matter capabilities are missing, including broader driver support.
- The absence of an integrated Thread radio is a recurring concern.
@pascal.nohl and others, if I missed something, please feel free to add to the discussion here or start a new thread.
