Surely you can see the issue with having some features just not work for some people? Reactions is the most obvious one. They aren't just for fun - people use them for polls for example.
[username] reacted to message [username]: [message]
> Surely you can see the issue with having some features just not work for some people?
No, I honestly don't. If I'm using IRC, even after slack warns me about missing and unsupported features. That's likely what I want! What if I don't want to see reactions when I'm trying get work done, but I am willing to be interrupted to answer questions, etc? Also, that example is easy to solve for IRC (see above)
People using it for polls is nice, and I think reactions are a useful feature. But there's no reason you can't make a "best effort" to support something people want to use. If I need to react, I'll grab my phone, (or open a browser). Meanwhile I can have access to the information that's *actually* important... text messages.
> [username] reacted to message [username]: [message]
Apple does this for iMessage and as far as I can tell (I don't live in the US) it's widely hated and believed to be deliberately annoying to Android users.
Do you really want 20 or those notifications for popular messages? Are you going to count them up for polls?
> Surely you can see the issue with having some features just not work for some people?
No, I honestly don't. If I'm using IRC, even after slack warns me about missing and unsupported features. That's likely what I want! What if I don't want to see reactions when I'm trying get work done, but I am willing to be interrupted to answer questions, etc? Also, that example is easy to solve for IRC (see above)
People using it for polls is nice, and I think reactions are a useful feature. But there's no reason you can't make a "best effort" to support something people want to use. If I need to react, I'll grab my phone, (or open a browser). Meanwhile I can have access to the information that's *actually* important... text messages.