> Keeping in mind that generally technical people will join this server and may have a vested interest in the move from IRC? I'm not sure what the implication

> Keeping in mind that generally technical people will join this server and may have a vested interest in the move from IRC? I'm not sure what the implication is here. > The issue around IRC is not a problem that can't be solved and really has been solved with the Web UI clients, for an every day user, to clients that make it simple otherwise. The issues surrounding IRC are partly because of inconsistent client implementation of features, but I think an even bigger problem is the inconsistent feature set of servers, which end-users have no control over. Sometimes it's because the server simply hasn't implemented a particular feature, other times it's because there is no feature - and if you're lucky, you'll even be told condescendingly that you don't actually need that feature in the first place. And of course, there's also the stuff that is implemented, but only accessible through bot interfaces that are incompatible between servers. Or the problems that are technically possible but require using a bouncer, and even still, that has inconvenient warts like having to grep through logs to search for stuff that isn't in your backlog, and the seemingly impossible-to-solve issue of persisting private messages across reconnects in a way that's useful in all situations. In any case, Mozilla has mentioned their intent to make their Matrix server accessible from an IRC bridge in the future, so it really does seem like the best of both worlds - giving Matrix uses the advantages of the platform like editing chats and easy offline channel history, while allowing IRC users to continue using their comfy client. Personally, for me, it's the other way around - Matrix has almost completely supplanted the use of my self-hosted IRC bouncer, and I'm looking forward to the day when I can shut it off for good.