3 ms·
For something like IRC? Yes. The service is dead simple and one server can handle thousands of users with modest hardware and without breaking a sweat. A comple
by Karunamon 7y ago
For something like IRC? Yes. The service is dead simple and one server can handle thousands of users with modest hardware and without breaking a sweat. A completely unfamiliar sysadmin could set it up in an hour or less. Since it's probably internal, there's little need for public services (nick/channel registration, etc).
- untog 7y agoSo what about the mobile device issue? Corporate logins? If you want to match what Slack offers you aren't just running an IRC server, you're going to have a small fleet of dependent services that, added up, just about match what Slack does. Is it really that surprising that people just opt to pay for someone to deal with all of this for them?
- Karunamon 7y agoAt which point you're not looking at IRC as a service anymore. There are different niches served - but the question was about the reasonableness of setting up IRC alone, which is still dead easy.
- LinuxBender 7y agoPut TheLounge [1] in front of it for people that want a web interface. Perhaps use ldap for corp users. [2] [1] - https://thelounge.chat/ https://thelounge.chat/ [2] - https://thelounge.chat/docs/configuration#ldap-support https://thelounge.chat/docs/configuration#ldap-support
- derefr 7y agoMost of how I use Slack, and how everyone I know uses Slack, involves 1. sending messages to people who are “away” to get their attention/loop them into a conversation; and 2. people reading back up in history for context when they come online. Now, modern IRCds might have features I’ve never experienced on raw IRC... but if they don’t, I don’t suppose you’re suggesting that this server also run thousands of bouncer bots in order to provide this contextual history feature? (Also, whence push notifications?)