Look! Even that sentence was longer than a tweet! I don't know how people do it.
(That's exactly 140 characters for you :) )
— Blaise Pascal (sometimes wrongly attributed to Mark Twain)
To me, this is exactly the kind of nuance that is lost by training yourself to limit ideas to 140 characters.
And for the record: I don't train myself to limit my thoughts, I train myself to use a form for expressing them appropriate to the medium I'm doing it in. Expressing something shorter and in steps is not inferior to long-winded explanations. If you must blame something for a fine nuance I failed to grasp, blame the fact that English is not my first language. I doubt I would have caught it in Dutch either, but at least that could be a valid reason.
e.g. blunt, rough.
Unfortunately for you, both connotation and denotation were working against you.
Particularly in technical writing, you've got to get your words nailed down correctly. This is why there are things like the RFC defining what 'shall', 'should', and 'may' mean (intended for other RFCs, but it's also used elsewhere)[1], or the development of Simplified Technical English[2]. The latter was developed in aerospace engineering, where minor misunderstandings can literally cost lives.
Subtle differences between words are important, and they allow us to communicate more complex ideas. Twitter may have it's place, but any conversation involving nuance really isn't suited for it. A high-quality conversation includes caveats and careful framing, which can't really be fit into 140 characters. At least, in my opinion.
[1]https://www.ietf.org/rfc/rfc2119.txt [2]http://en.wikipedia.org/wiki/Simplified_Technical_English
In any case, using some form of video calling is too intrusive. I can type this reply, do something else for 10 minutes, then check back. But then I was always one for text mediums rather than video or audio calls :)