4 ms·
Are you suggesting that a massive company should run their own IRC server, complete with bots that handle OAuth and access control, history saving, document dow
by stnmtn 5y ago
Are you suggesting that a massive company should run their own IRC server, complete with bots that handle OAuth and access control, history saving, document downloading?
- mhitza 5y agoI'm not suggesting anything really. If anything I'd be happier for even more asynchronous collaboration via email, and realtime chat available as an exception. In the thread chain I was just curious why people think IRC could not be a Slack replacement. Related to your question about these integration services. Running an IRC server is definitely not complicated. Bots which implement authentication/authorization already exist (NickServ/ChanServ/X). History saving is also common, and for in-client message history a bouncer is a pretty good tool to have. Document downloading, you have DCC, or yet other bots you can query/download from (pretty common in the mp3 download era). If there was incentive someone could create a bundled package that unifies all these different components + a more modern client interface and people would not have any issue using. It's not in the problem space I'm interested to work on, but functionally even the more restricted existing IRC offering would be something I'd rather use than the gif meme filled, emoji overdosed chats I've had on Slack. On the other hand, I've been an independent contractor for a couple of years now and I had the pleasure of not being part of large team slack channels anymore anyway.