4 ms·
Yeah, this is why I still prefer IRC over Slack and most other team chat systems. I hear a lot of people suggest them because of missing messages with IRC, but
by jsight 10y ago
Yeah, this is why I still prefer IRC over Slack and most other team chat systems. I hear a lot of people suggest them because of missing messages with IRC, but I actually think the missing messages is a feature. A ping on IRC to someone that isn't there is a bit like walking by someone's office and noticing that they aren't there.
I don't want my phone to notify me immediately every time a team chat message goes through. Direct hangouts messages have a higher "weight" and are useful sometimes, too, though.
Basically, this is just a cultural problem that needs to be worked out. Sort of like the (usually) understood idea that you shouldn't disturb a person wearing headphones and working.
- Can_Not 10y ago> a bit like walking by someone's office and noticing that they aren't there. No, it's absolutely not like that. The use case for "not dropping messages" is that you send a message and know they received it. You don't have to remember it manually, you don't have to introduce another chat system just to asynchronously remember to resend messages later. The other guy can respond at their convenience. Dropping messages would make the application a critical failure for any serious business uses. There are lots of features to mute notifications per room or for time durations.
- jsight 10y agoYes, it is absolutely like that. My "presence" is when I am in the room (not marked away or afk or anything like that). My non-presence is when I walk away (or leave the "office" for the day). Having multiple chat systems is ok, if they actually serve multiple purposes.