Every other time when you don't need to know that, you can still not get all the problems of the empty "hello" message.
I almost always have time to fight fires — unless busy with a larger conflagration. I may or may not have the time to debate the finer points of table naming conventions however.
Without context I might say yes and then have to take it back once I discover the topic.
Hello without a context is ignored.
Hello with a context empowers me to make a decision about how my day will go.
A "hello" means it is "IM urgent" so it can wait for the moment I am OK to exchange.
Like I said, this is also cultural - some cultures allow people to interrupt others, some not.
That is why hello is annoying. People are capable to talk immediately, but take forever to finish writing.
Re: your messages in this thread
Dear BrandoElFollito:
You're rebuilding TCP over UDP. Chat apps are connectionless (or RESTful, if you will). What makes them productive, especially in the workplace, is the fact that they can work without all the handshaking that accompanies more structured communication like in-person, spoken human conversations.
Nothing is stopping you from adding back all your binds, listens, SYNs, and ACKs to a protocol that doesn't need them. But it's a conversational code smell if you do.
Sincerely yours,
sowbug
Sending Hello this way seems like calling somebody and if they answer it's ok to interrupt.
Being responsive doesn't mean you're idle.
If this is to say something minor I will block that person, or never pick up their call again.