convos

In addition to the bots others mentioned, there are web front-ends to provide scrollback. Convos [1a], TheLounge [2a], KiwiIRC+KiwiBNC [3] I prefer to instead run irssi+otr in a GNU screen session from a random VM/VPS provider. Most others prefer tmux. I'm just stuck in the past I suppose for using GNU screen. [1a] - https://github.com/convos-chat/convos/ [1b] - https://convos.chat/ [2a] - https://github.com/thelounge [2b] - Demo: https://demo.thelounge.chat/#/connect [3] - https://github.com/kiwiirc/kiwiirc

And UnrealIRCD still rocks. For a quick-and-dirty setup I've deployed ng-ircd but Unreal has always been my go-to for anything serious. If nothing else it can be useful as a backup or internal platform during the rare events that Slack or Discord are having an incident. The common complaint is a lack of channel text scrollback-log but it can be front-ended with TheLounge [1] or Convos [2]. The web front-ends can be scaled up in front of IRCD. I personally prefer to handle that with gnu screen or tmux and WeeChat [3] as that method can scale to tens of thousands of concurrent members on a single node vs. running reddis and some web framework. For identities companies can restrict access using OpenLDAP or AD [4] Non-Free module My favorite aspect of UnrealIRCD is how modular the 4.x+ versions became. One can enable only that which is

For the other layers one can front-end IRC with TheLounge [1][2] or Convos [3][4]. TheLounge only persists history in private mode meaning that users are created in that front-end and chat messages are in Redis. For small networks or groups of friends this is probably fine. Notably missing is voice chat. I use the Mumble client [5] with the Murmur or uMurmur [6] server which is light-weight enough to run on ones home router. I use it on Alpine Linux, works great. It's not a shiny and attention grabbing as Discord but probably fine for everyone else. For people to create their own voice channels would require the full-blown Murmur server. [1] - https://github.com/thelounge [2] - https://thelounge.chat/ [3] - https://github.com/convos-chat/convos/ [4] - https://convos.chat/ [5] - https://www.mumble.info/ [6] - https://github.com/umurm

FWIW TheLounge [1] and Convos [2] can front-end an IRC server giving it much of the look of a modern client and also chat persistence when using TheLounge in private mode. The trade-off in my opinion is scalability. With a bog standard IRCD I can handle tens of thousands of clients per node. Adding web persistent increases memory usage. [1] - https://github.com/thelounge https://thelounge.chat/ [2] - https://github.com/convos-chat/convos/ https://convos.chat/

No need for chat history bots if you front-end your IRCD with a web interface that has chat history, persistence. [1][2] [1] - https://github.com/thelounge/thelounge [2] - https://github.com/convos-chat/convos

FWIW you can make IRC stateless with a web front-end like TheLounge [1] or Convos [2]. Sessions are maintained on the server side in reddis. [1] - https://github.com/thelounge/thelounge [2] - https://github.com/convos-chat/convos

FWIW you can give your IRC users an experience closer to Slack with TheLounge [1] or Convos [2]. [1] - https://github.com/thelounge/thelounge [2] - https://github.com/convos-chat/convos

I would very much like this as well, but "kiosk" mode is currently not planned. Might start consider it again after https://github.com/Nordaaker/convos/issues/414 is closed... Please do open an issue where you describe what you think is required for Convos to work from within your email inbox, or join #convos on freenode and have a chat with us.

Logging in and adding users got a lot easier in version 2.0: https://convos.by/2019/11/24/convos-one-point-two.html The next version of Convos (which will hopefully be released this week) adds support for LDAP, which might also help you manage users. You can have a look at our issue tracker for what is planned for the future versions of Convos: https://github.com/nordaaker/convos/milestones I will soon update the webpage with a longer list of features: https://github.com/Nordaaker/convos/issues/445

There are a few web clients that use redis to allow you to see history. I will be the first to admit, those clients don't scale as well as IRC itself does. [1] [2] And of course, someone would have to manage that infrastructure. It isn't for everyone. Another option would be to rent a really cheap VM and run a tmux or screen session with weechat [3] or epic [4], but command line isn't for everyone either. [1] - https://github.com/thelounge/thelounge [2] - https://github.com/Nordaaker/convos [3] - https://weechat.org/ [4] - http://www.epicsol.org/#getting_epic

You can still put a web client with persistent chat history in front of IRC. TheLounge is one example [1] [2] and Convos is another. [3] [4] [1] - https://thelounge.chat/ [2] - https://github.com/thelounge/thelounge [3] - https://convos.by/ [4] - https://github.com/Nordaaker/convos

There is also Convos [1] a web front end client to IRC that addresses some of your concerns. It uses Redis to maintain state. [1] https://github.com/Nordaaker/convos

Take a peek at convos (web IRC client frontend) https://github.com/Nordaaker/convos for a persistent web client. It uses redis to maintain state.

The reason irccloud is popular is that it is simple to set up and there is a really great mobile client. No one really needs another web based client, even if it is free; there are plenty of alternatives for that such as ircanywhere[1] or Convos[2]. I'm really not sure who this is for. [1] http://ircanywhere.com/ [2] https://github.com/Nordaaker/convos