One instance of this I've struggled with (mainly b/c online comms is hard) is when people publicly post that they're annoyed about a confusing thing. "OMG why does it take 10 clicks to do X". This often prompts solutions ("If you turn on Y, then it will only take 2 clicks"), but can sometimes then be followed by irritated rebuttals ("Yes yes I know it's configurable but the point is...").
On the one hand I get the desire to just vent. But if you're going to post certain types of problems (esp technical) very publicly, IMO the expectation should be for unsolicited feedback, especially since others might benefit. Nonetheless, I still usually err on the side of not replying.
I can see myself being one of these irritated people. More than once, I've posted (maybe not even on Twitter; maybe on a support channel of some sort) something like "why did it take me 30 minutes to figure out how to do X?" And people, particularly the developers or people in the community, will reply with "just do Y and Z and you can do X". This irritates me because I didn't say "I can't do X!", I said "it took me 30 minutes to figure out how to do X". I.e, a usability problem, not a functionality problem. And the fact that it doesn't register to them that this is what I'm complaining about is all the more irritating ("yes I know, but the point is..." from your example), because it feeds into my bias that they have a blind spot about their own UI.
As to whether I'm just venting, I suppose I imagine that on Twitter the developers might hear my complaints. (And yes, as such I should always remind myself to keep my complaint relatively respectful for this reason).
On the one hand I get the desire to just vent. But if you're going to post certain types of problems (esp technical) very publicly, IMO the expectation should be for unsolicited feedback, especially since others might benefit. Nonetheless, I still usually err on the side of not replying.