Somewhere along the way, we started treating our coworkers like APIs. This is a problem.
The nohello movement made a reasonable point and then took it too far. Yes, don't send a "hello" and then wait three hours before asking your question. Everyone agrees on that. But the cultural artefact that followed — the Slack status linking to nohello.net, the implicit signal that any greeting is an inefficiency to be eliminated — has made remote work measurably colder.
A "hey!" followed immediately by a question is not the same as a bare "hello" with a cursor blinking expectantly. Both are acceptable. Neither should require a disclaimer.
"The person who sends you a warm greeting before asking their question has not wronged you. They have simply decided that you are a human being."
Three things nohello gets wrong
The only message that's actually bad
Option B is warmer. Some people prefer warmth. That is allowed. The recipient of option B is not being oppressed. They have been wished a good morning and asked a question about infrastructure. They will survive.
Be efficient. Also be a person.
By all means, don't leave people hanging. Include your question. Respect async norms. But saying hello — genuinely, warmly, humanly — is not a bug. It is a small insistence that the person on the other end of the wire is more than a service endpoint.
You can have both. Many people do, every day, without incident.
That's it. That's the whole message. You've just been greeted, and nothing bad happened.