> [server-side history] That's a feature, not a bug. Whatever your personal feelings on message history are, people and businesses need functionality like usab

> [server-side history] That's a feature, not a bug. Whatever your personal feelings on message history are, people and businesses need functionality like usable mobile clients they can receive messages in without keeping the client open continuously, or the ability for administrators to delete messages which have been sent by other users. IRC doesn't, and cannot, provide those features. > [no attachments] Good, no silly gifs cluttering up the chat. Also means it's difficult to discuss inherently audiovisual content like graphical designs, or to transfer files -- all things that come up in business contexts. > [permissions] How fine grained do you need it to be? It's not that the permissions aren't fine-grained so much as that the entire system is crudely designed. Users' permissions in a channel are mostly tied to their presence in the channel; if you leave and rejoin (or disconnect and reconnect to IRC), any permissions are lost and have to be regranted by another user in the channel. Bans are tied to nicknames (which are volatile) or connection hostnames (which are differently volatile). Invite-only channels use passwords. And so on. It's a mess. Yes, you can add bots to handle some of that for you -- but having to rely on bolt-on components for basic functionality is a sign of a badly designed service.