bitlbee VS ngircd

ah didn't realize it had gone away. its successor appears to be [0]

now I'm reliving the chaos of the late-00s/early-10s instant messaging apocalypse when AOL sunsetted AIM. Clients like Trillian were absolutely necessary before AIM shut down. Everybuddy was a good linux-friendly client. When I still spent time on IRC, I really really liked Bitlbee [1] with ERC [2].

(I'm not saying that there's a connection there, but rather that all the chat protocols started getting used less around the same time for the same reason, which was smartphones becoming commonplace in late-00s.)

[0] https://en.wikipedia.org/wiki/Ayttm

[1] https://www.bitlbee.org/

[2] https://www.gnu.org/software/emacs/erc.html

I use purple-discord (libpurple/Pidgin plugin) + BItlBee (IRC chat gateway, libpurple variant) + Quassel (distribued IRC client, like a bouncer) on a home server, and use Quasseldroid to connect on mobile. I would eventually like to simplify this setup.

I used to have a similar setup to use IRC for everything using https://www.bitlbee.org. Fun times!

Another approach to this is to use bitlbee's twitter support and your favorite Emacs IRC client to access that. This is especially nice if you are using bitlbee anyway.

This won't likely help after the fact but I would suggest separating Artwork discussion into their own Discord server and then move all business partners and certainly financial information discussion with employees into private self-hosted servers so that one has control over the server, chat filters, IP/domain blocks and even approved/denied web links. It's not perfect and some may not be happy about having to register on a second site friction and all but it sounds like in this case it would have helped. Leave cloaking disabled on the business server so you can see where people are connecting from ahead of time and password protect sensitive channels.

Additionally IRC server filters can be updated daily with the most prevalent scam domains using the same sources as uBlock and a few other git mirrors on github. One could even block all text that appears to be any kind of URL and instead require them to get on voice chat to verify themselves. uMurmur is a tiny daemon that is very easy and quick to set up and one can also password protect channels on uMurmur. There is an android client for uMurmur called Mumla.

Take a look at Ngircd [1] and TheLounge as a quick way to set up a private secure chat server in less than 20 minutes. uMurmur [3] takes even less time to set up. All three daemons are available in sever Linux distribution repositories and have example configurations.

[1] - https://ngircd.barton.de/

[2] - https://thelounge.chat/

[3] - https://github.com/umurmur/umurmur/wiki/Configuration

I am pretty sure nobody except nerds knows what IRC is right now. It's long since been supplanted by user-friendlier group chat services.

I agree with this. Like I mentioned this is slowly changing with web front-ends to IRC like TheLounge. NGIRCD [1] + TheLounge [2] take all of about 10 minutes to set up and then maybe another 10 minutes to tie that into and configure IRC services such as Anope. I would not be surprised if this has already been automated with Docker or Ansible. Discord and Slack will probably be popular until they reach critical mass and feel confident enough to start doing hostile things to their user base or until someone with a large ego purchases them.

[1] - https://ngircd.barton.de/

[2] - https://thelounge.chat/

Got bored and wanted to muck about with one of my favourite IRC bots (without peeing off my usual haunt' opers). So I compiled ngIRCd and had a bash at running RBot