Rodel, I'm on a phone. I couldn't know if this was a thread or not. I got a message, and i replied. It went from there

Just as a note about human interaction, this response dodged any responsibility. I can understand if it's more difficult to know if you're in a thread or not on a different device, but it would still likely have been better to start your response with a simple "Sorry!". Then if you felt the need to go into the details of why it was difficult for you to know if it was a thread or not you could. Related, I know on the iPhone app at the top of the screen it will show if you're in a channel or thread. Channels will have the '#adobe' with '917 members' under it, where as the thread has 'Message' with '#adobe' under it. I know that isn't particularly intuitive, so I definitely can understand the confusion and not knowing where you were talking. (and I don't know if you're using the iPhone app or not, and I haven't used any other mobile interfaces, so I'm not certain if they behave the same) Thank you for moving the conversation into a thread though! It helps keep the main chat more digestible for those that only check in once or twice a day. (they can choose to look at a full conversation if they main message interests them, otherwise they can easily scan past it to other threads) Hope all is well.

Dude, I'm driving. How about a little grace? Have I demonstrated previously this poor comm skill you refer to? If so, I AM sorry and would want to be corrected.

Sorry Charlie, I don't see anything graceless re @rodel30 trying to help you. It doesn't even sound patronising or passive-aggressive or anything. It reads as him... just... trying to help, and offering good advice. However your own two replies (in this thread) are a bit... abrupt... perhaps. Anyway, good call @rodel30 for suggesting threads. Saved me from doing it 😉

text based conversations are not the best medium for trying to correct others in my experience, particuarly with people you don't know very well. It lacks the emotions/body language/tone of voice that can give you cues to the persons intent. I personally also felt that rodels suggestion that charlie was dodging personal responsibility was unnecessary/presumptuous/rude when I read it.

Thanks, Scott. And Adam, my replies were abrupt because as I said I was driving! FFS, if I elaborate I'm chided for waffling. Now I'm brief and I'm chided for being abrupt. :-) Consider me new to slack. I certainly use it infrequently. Again, I was driving, someone tagged me for help, I replied. The conversation ensued. And then Rodel suggested use a thread, so I did. Then he offered all that about human interaction, in a very long thread I couldn't read while driving. I'd said earlier in the tread I was driving. Maybe he didn't read that, I can't know. I just thought it overkill to reply as he did. The first suggestion was enough, and I complied. Like Scott, I saw those first few sentences of his long initial reply here and replied briefly to that, again as I was driving. (I'd pulled over when having all the back and forth with Luis, to focus on his problem and the solution he sought.) Anyway, anyone who cares to learn from this thread should have what they need. I have, and I will try to be more careful when replying to see if it's a thread. I can see now that the Android app DOES indicate that. Only with experience would one notice the difference when it is and is not. Now I know. Can we leave it at that?

Don't drive and text 🙂

And thank you @carehart for helping get this figured out. You are definitely appreciated.

@seancorfield I realize you were perhaps just making a quip, but you might have missed the part where I said I'd pulled over for the more extended part of the original support conversation. 🙂 Since the "slings and arrows" part was blowing up once I was back on the road, I'll admit I was glancing at those when I had spare moments at stop lights, etc, as I needed to get back for a client support call. (I realize in some states/countries even that is verboten, but not where I live.) And Dan (@garciadev), thanks much for the kind regards. I did really want to help you guys...and to get to the better solution of the Adobe hotfix that fixes the problem rather than leaving it at downgrading the mysql driver. Hope that may work out.

@carehart I made the comment because you used the fact that you were on the phone "while driving" as an excuse for not following the community protocol here of using threads for conversations -- and instead of apologizing for that social gaffe, you doubled down and got snippy with people who very reasonably asked you to follow the community protocol.

I reasonably complied the first time I was asked. Stop it

No, you didn't apologize and you got snippy with people. That's not acceptable behavior here Charlie. Please at least APOLOGIZE and stop doubling down.

Yes, exactly. And I have learned now to be more careful

The context for your one "sorry" was "Dude, I'm driving. How about a little grace? Have I demonstrated previously this poor comm skill you refer to?"

Yes

Nice one, Charlie.

I think an important takeaway that could help avoid miscommunications in the future should be for everyone to Assume Positive Intent. I personally think that everyone on this slack is primarily trying to help/be helped/collaborate with the CF community in a positive way. https://collaborativeway.com/general/a-ceos-advice-assume-positive-intent/