[{"_1":2,"_163":-5,"_164":-5},"loaderData",{"_3":4,"_18":19,"_25":26,"_142":143},"root",{"_5":-5,"_6":-7,"_7":8,"_9":-7,"_10":11,"_12":-7,"_13":14,"_15":16,"_17":11},"currentUser","primaryEmail","siteVerification","6LeIxAcTAAAAAJcZVRqyHh71UMIEGNQ_MXjiZKhI","toast","enableDev",false,"incidentStatus","theme","system","contrast","normal","dockerRebrandTour","routes/_layout",{"_20":-5,"_21":22,"_23":11,"_24":22},"username","isAskGordonEnabled",true,"showMinimalLanding","showHoneypotTrap","routes/_layout.r.$namespace.$reponame",{"_27":28,"_29":-5,"_30":11,"_31":11,"_32":33,"_34":35,"_36":-5,"_37":11,"_38":39,"_89":-5,"_90":91,"_130":-5,"_131":11,"_132":22,"_133":11,"_134":11,"_135":-5,"_136":11,"_137":-5,"_138":139,"_140":92,"_141":-7},"canonicalUrl","https://hub.docker.com/r/dreamcat4/irc/tags","mcpServer","canSeeDockerfile","canSeeAutobuilds","namespace","dreamcat4","reponame","irc","cloudBuildSource","isAutobuildsAvailable","repo",{"_40":41,"_42":43,"_45":46,"_47":48,"_49":11,"_50":51,"_52":53,"_54":55,"_57":35,"_32":33,"_58":59,"_60":44,"_61":62,"_63":64,"_65":66,"_67":-5,"_68":69,"_70":71,"_72":11,"_73":33,"_74":75,"_80":22,"_81":82,"_86":33,"_87":88},"categories",[],"content_types",[44],"image","date_registered","2016-04-11T10:43:41.501602Z","description","A collection of pre-configured irc programs and services. Designed to make IRC easy.","is_private","last_updated","2020-11-01T12:03:50.773894Z","last_modified","2024-10-16T13:48:34.145251Z","media_types",[56],"application/vnd.docker.container.image.v1+json","name","pull_count",2693,"repository_type","star_count",4,"status",1,"status_description","active","source","collaborator_count",0,"full_description","*This page is best viewed on --->* ***[Github](https://github.com/dreamcat4/docker-images/tree/master/irc).***\n\n*Back to this page on --->* ***[DockerHub](https://hub.docker.com/r/dreamcat4/irc/).***\n\n* This Docker image is based on ubuntu 16.04 base image (xenial xerus).\n* **1.4 GB Image size[***](https://github.com/dreamcat4/docker-images/tree/master/irc#pros-and-cons-of-this-docker-image).**\n\n# irc\n\nA collection of pre-configured irc programs and services. Designed to make IRC easy. Everything to come up on container start, all working together.\n\n**Includes [irssi over ssh](http://i.imgur.com/Fk94eHf.png) and [glowing-bear web interface](http://i.imgur.com/bAAPFkS.png), as pictured below.**\n\n...but also: ***SO MUCH MORE!***\n\n![irssi client theme customizations](http://i.imgur.com/Fk94eHf.png \"irssi client theme customizations\")\n\n![glowing-bear web interface](http://i.imgur.com/bAAPFkS.png \"glowing-bear web interface\")\n\n## Contents\n\n\n\n \n\n- [What's included?](#whats-included)\n - [Pros and Cons of this Docker image](#pros-and-cons-of-this-docker-image)\n - [Connection diagram](#connection-diagram)\n - [Service ports](#service-ports)\n- [Quickstart](#quickstart)\n - [Configure ZNC](#configure-znc)\n - [Configure irc clients](#configure-irc-clients)\n - [irssi](#irssi)\n - [limnoria (aka supybot)](#limnoria-aka-supybot)\n - [weechat](#weechat)\n - [Configure local irc server - peer passwords](#configure-local-irc-server---peer-passwords)\n - [Connecting](#connecting)\n - [Over ssh](#over-ssh)\n - [From a web browser](#from-a-web-browser)\n- [IRC Servers](#irc-servers)\n - [Public IRC networks](#public-irc-networks)\n - [Private / localhost services](#private--localhost-services)\n- [Editing configuration files](#editing-configuration-files)\n- [Configuration](#configuration)\n - [ssh](#ssh)\n - [znc](#znc)\n - [weechat](#weechat-1)\n - [irssi](#irssi-1)\n - [Notifications to your i-Devices, android, Desktop, etc.](#notifications-to-your-i-devices-android-desktop-etc)\n - [IRC Data](#irc-data)\n - [Logs](#logs)\n - [URLs](#urls)\n - [Bitlbee](#bitlbee)\n - [tmux](#tmux)\n - [Limnoria (aka supybot)](#limnoria-aka-supybot)\n - [ngircd](#ngircd)\n - [atheme irc services](#atheme-irc-services)\n - [Bitlbee chat protocols](#bitlbee-chat-protocols)\n - [LibPurple](#libpurple)\n - [WhatsApp](#whatsapp)\n - [Skype](#skype)\n - [SIPE](#sipe)\n - [Facebook](#facebook)\n - [Steam Chat](#steam-chat)\n - [Telegram](#telegram)\n - [Torchat](#torchat)\n - [Other chat protocols](#other-chat-protocols)\n- [Searching irc logs](#searching-irc-logs)\n- [Connecting to the irssi session](#connecting-to-the-irssi-session)\n- [Disconnecting from an irssi session](#disconnecting-from-an-irssi-session)\n- [Per-user setup](#per-user-setup)\n - [ZNC user configuration](#znc-user-configuration)\n - [Setting up nickserv on znc](#setting-up-nickserv-on-znc)\n - [Per-network Authentication methods](#per-network-authentication-methods)\n - [&bitlbee](#&bitlbee)\n - [dalnet](#dalnet)\n - [efnet](#efnet)\n - [freenode](#freenode)\n - [gnome](#gnome)\n - [ircnet](#ircnet)\n - [mozilla](#mozilla)\n - [oftc](#oftc)\n - [quakenet](#quakenet)\n - [undernet](#undernet)\n- [Irssi Scripts](#irssi-scripts)\n - [Tweaked scripts](#tweaked-scripts)\n - [Not met script dependancies](#not-met-script-dependancies)\n- [File permissions](#file-permissions)\n- [Docker Compose](#docker-compose)\n- [Web-browser alternative](#web-browser-alternative)\n\n\n\n## What's included?\n\n* IRC clients\n * [irssi](https://irssi.org/)\n * [weechat](https://weechat.org/about/screenshots/), for the [glowing-bear](https://www.glowing-bear.org/) web interface\n * [tmux](https://en.wikipedia.org/wiki/Tmux) and [sshd](http://www.openssh.com/) for terminal services\n\n* IRC services\n * [ZNC bouncer](http://wiki.znc.in/Webadmin)\n * [Bitlbee](https://wiki.bitlbee.org/) (for IM accounts)\n * [ngircd](https://github.com/ngircd/ngircd) - your own local / private IRC server\n * [atheme irc services](https://atheme.github.io/atheme.net/atheme.html) - for nickserv, sasl etc\n * [Limnoria IRC bot](http://doc.supybot.aperio.fr/en/latest/use/index.html) (aka supybot)\n\n### Pros and Cons of this Docker image\n\n**Pros:**\n\n* All of the *best*, most *useful*, and most *practical* IRC services\n* Services come preconfigured to work together with each other out-of-the box, often communicating over localhost 127.0.0.1\n* Each service runs under its own unpriviledged unix account\n* Well organised `/config` folder, with user pre-seeding\n * the is easiest way to manage your irc settings files\n * can diff, merge, version control, and overlay your per-user IRC settings ontop of the pre-configured defaults\n* Bitlbee comes 'fully' loaded with support for all of the major chat protocols - no hassles, just go!\n* Not resource hungry, can easily run on local modest hardware, or limited remote VPS plan. With ease.\n\n**Cons:**\n\n* Very large image size ~1.4gb, most of which is the bitlbee (IM chat) and limnoria (irc bot) dependancies\n* It is less secure than having many isolated individual images\n* May include some service you didn't want\n\n***However:***\n\nThis image's Dockerfile has been properly organised into isolated sections for each services. And each service is kept in individual separate folders. Therefore this image should be very easily broken down. Want to split it up / remove some un-needed services? Should be a sinch.\n\n***Top tip:***\n\nBitlbee and limnoria were by far the biggest culprits to image bloat here. The large image size is mostly due to their dependancies. Before adding them the image was 'only a mere ~700mb'. By adding them it fully doubled the image size from previous all estimates. That smarted much. But ah well! What can you do eh? Be left without access to all the most popular IM chat servers in the entire world? Live life without your very own personal IRC bot? Noooooo! :)))\n\nI shall leave it for some other guys to come and break up the party. This one shall remain a masterpiece complete. The complete collection. The full enchilada. So be it. 1.4 GB urrrghhh then. At least everything runs super-fast, and not slow or cacky in any way.\n\n### Connection diagram\n\nGeneral diagram how these programs are connected up:\n\n```sh\n\natheme <--- ngircd <-\\ /- limnoria IRC bot (supybot)\nPublic IRC Servers <--- ZNC <--- irssi <--- TMUX Session <--- SSH <--- Client computer\n Bitlbee <-/ \\- weechat -/\n \\- weechat relay <--- glowing bear <--- web browser\n```\n\nAnd thanks to TMUX, simultaneous ssh logins are supported. So you can have the same irssi or weechat text-based session open on multiple machines no problem. And multiple glowing-bear instances of the web interface too.\n\n### Service ports\n\nThis container runs multiple services on it, and as several different user accounts. They are as follows:\n\n```sh\nINTERFACE, TCP_PORT, (PROTOCOL), UNIX_USER, SERVICE, COMMENT\n\n0.0.0.0 (all interfaces), 22, (SSH term), irssi, irssi client in a tmux session, always running\n\n0.0.0.0 (all interfaces), 6697, (SSL HTTPS), znc, znc web interface, for configuring the znc service\n\n0.0.0.0 (all interfaces), 6697, (SSL IRC), znc, znc irc server, for other irc clients / mobile apps etc. can be disabled in znc.conf file, then restart container / znc server\n\n0.0.0.0 (all interfaces), 9001, (SSL weechat relay), weechat, weechat relay port, for glowing-bear web-based IRC interface\n\nlocalhost, 9997 (SSL IRC), znc, znc irc server, only visible inside container, for client: conatiner's local instance of irssi program\n\nlocalhost, 6111, (http IRC), bitlbee, bitlbee irc server, only visible inside container, for client: local ZNC server\n\nlocalhost, 6667, (http IRC), ngircd, ngircd irc server, only visible inside container, for client: local ZNC server\n```\n\nThe user is intended to access the IRC service primarily as the user `irssi`, on ssh port 22. Via public-private SSH key authentication (no ssh password). The container's irssi program itself is always kept running under a perpetual tmux session named `tmux`. Which supports simultaneous logins from multiple computers.\n\n## Quickstart\n\nFor the most part, you just need to set new username & password(s) for your own personal irc accounts. However these same logins are referenced across multiple programs / multiple configuration files.\n\n* After this section is completed, all of your znc bouncer account logins should be updated.\n\n* Some irc networks also require you to identify yourself, or register your nickname with their services. That has not been covered in this quickstart section. As that depends which specific irc servers you actually wish to connect to. There is a seperate section for all the nickserv stuff / per-network registration instructions.\n\n### Configure ZNC\n\n* Create a new container of `dreamcat4/irc` image, with bind:mounted volumes for the `/config` and `/irc` folders\n* Start the container\n\n* Point your web browser to `https://CONTAINER_IP:6697`\n * Log into znc web interface with initial username: `znc` and password: `znc`\n\n* Click 'Manage Users'\n * Click 'Clone' button for `znc` user\n * To give your own real nickname, and choose a new password\n * Click 'Clone and Return' button\n\n* After saving new user, click 'Edit' again, and In the 'Flags' section, select 'admin' checkbox to make yourself the admin user\n* Logout as user `znc`\n* Log back in as your own nickname, with your new password\n\n* Click 'Manage Users' again\n * Delete the initial `znc` user account\n\n * Click 'Clone' button for `supybot` machine account\n * Again to give your bot its own nickname, and choose a unique password for it\n * Delete the previous `supybot` machine account\n\n* You should be left with 2 znc user accounts. 1 admin status account of `YOUR_IRC_NICKNAME`. Plus 1 machine account of `YOUR_IRC_BOT_NICKNAME`.\n\n* Stop the container\n* Navigate to the bind:mounted volume `/config`\n\nNow for some reason (or perhaps a bug in znc), as a side-effect of our user clone operation znc has inserted many redundant duplicate config lines in each network's config block. Which are now incorrectly referring to the previous nicknames we dont wish for: `znc_user`and `supybot`. Therefore, we must now also replace all cruft instances of the `znc_user` and `supybot` strings in the znc config text file, located at:\n\n```sh\n/config/znc/configs/znc.conf\n```\n\nJust search / replace all occurences of the string with your own personal irc nickname. Or else just delete them. As they are all extraneous config lines being repeated, they are not actually needed.\n\n### Configure irc clients\n\nWe now need to replace the znc username:password login credentials, with your new user accounts. The next files to modify are:\n\n```sh\n/config/irssi/config\n/config/limnoria/supybot.conf\n/config/limnoria/conf/users.conf\n/config/weechat/irc.conf\n/config/weechat/relay.conf\n```\n\n#### irssi\n\n**`/config/irssi/config:`**\n\n* For the znc server logins, those instructions are included inside the config file itself.\n\n* You should also change the following irssi's settings to your real IRC nickname / account name:\n\n```perl\nsettings = {\n core = {\n real_name = \"znc user\";\n user_name = \"znc_user\";\n nick = \"znc_user\";\n```\n\nBTW, the following setting:\n\n```perl\nipw_password = \"irssi\";\n```\n\nIs the login access password for 'glowing-bear over irssi'. That would require extra runtime files which is not included in the container. We decided to leave it out because it is simpler to use glowing-bear with weechat instead.\n\n#### limnoria (aka supybot)\n\n**`/config/limnoria/supybot.conf:`**\n\nFind these bot settings, and change them to your bot's new znc name / znc password:\n\n```yaml\nsupybot.nick: supybot\nsupybot.ident: supybot\nsupybot.user: znc_users familiar\n```\n\nAnd for each network login setting, just as we show in the irssi config file, change them to:\n\n```yaml\nsupybot.networks.NETWORK.password: ZNC_BOT_USERNAME/NETWORK:ZNC_BOT_PASSWORD\n```\n\nThe lines to find are:\n\n```yaml\nsupybot.networks.barton.password: supybot/barton:supybot\nsupybot.networks.bitlbee.password: supybot/bitlbee:supybot\nsupybot.networks.dalnet.password: supybot/dalnet:supybot\nand so on...\n```\n\nThere are about 12 networks to update.\n\n**`/config/limnoria/conf/users.conf:`**\n\nReplace the bot owner `znc_user` --> `YOUR_IRC_NICKNAME`.\n\nThe default initial 'owner password' is also stored here. However in a hashed form. Owner password is used to identify yourself as to the bot as its admin, and take ownership of it. The default owner password is `supybot`. But its encrypted so we cant change it right now. Once logged in over IRC, you first authenticate yourself with that initial owner password `supybot`. Then change it with `/query supybot user set password supybot YOUR_NEW_BOT_OWNER_PASSWORD`.\n\n#### weechat\n\n**`/config/weechat/irc.conf:`**\n\nIn this file, you must now update the following options, with the credendials of your new znc user account:\n\n```perl\nnicks = \"znc_user,znc_user_\"\npassword = \"znc\"\n```\n\nthen also for each configured znc network:\n\n```perl\nbarton.username = \"znc/barton\"\nbitlbee.username = \"znc/bitlbee\"\ndalnet.username = \"znc/dalnet\"\nand so on...\n```\n\nThere are about 12 networks to update.\n\n**`/config/weechat/relay.conf:`**\n\nThis is for your glowing-bear web access / login password. Change the line:\n\n```perl\npassword = \"weechat\"\n```\n\n### Configure local irc server - peer passwords\n\nWe can change the peer connection password, to help secure our own local irc server and its seperated atheme services daemon.\n\n**`/config/atheme/atheme.conf:`**\n\nFind the lines:\n\n```sh\n send_password = \"atheme\";\n receive_password = \"ngircd\";\n```\n\n**`/config/ngircd/ngircd.conf:`**\n\nFind the lines:\n\n```sh\n MyPassword = atheme\n PeerPassword = ngircd\n```\n\nAnd change the 2 passwords to something un-guessable. Make sure that the `send_password` still matches the `MyPassword` in the other file. And that the `receive_password` = `PeerPassword` in counterpart file.\n\n* That is the quickstart configuration finished!\n\nIt is now recommended to copy only these few modified config files, into the overlay folder named `config.custom/` in the docker build context. Which can be checked out from github repo. Then if you ever re-build this docker image yourself, it will automatically include all your unique login / accounts info (as the pre-seeded default /config).\n\n### Connecting\n\n#### Over ssh\n\nFor ssh, you can find new ssh private access keys. They are auto-generated on first boot, into the following locations:\n\n```sh\n/config/irssi/.ssh/id_rsa\n/config/weechat/.ssh/id_rsa\n```\n\nGrab the 2 unique `id_rsa` private key files. One is for irssi, and the other one is for weechat. Rename them to something obvious. For example `irssi_rsa` and `weechat_rsa`. Then copy them to your client computers from where you want to login. Then you can ssh something like this:\n\n```sh\nssh -i irssi_rsa irssi@CONTAINER_IP\nssh -i weechat_rsa weechat@CONTAINER_IP\n```\n\nOr even better, create ssh aliases, to just `ssh irssi` and `ssh weechat`.\n\n```sh\n.ssh/config:\n\nHost irssi\n Hostname YOUR_CONTAINER_IP\n User irssi\n PubKeyAuthentication yes\n IdentityFile ~/.ssh/irssi_rsa\n\nHost weechat\n Hostname YOUR_CONTAINER_IP\n User weechat\n PubKeyAuthentication yes\n IdentityFile ~/.ssh/weechat_rsa\n```\n\n#### From a web browser\n\nFor glowing-bear web access, over HTTPS SSL/TLS:\n\nNavigate in your web browser to the [glowing bear website](https://www.glowing-bear.org). You should be able to log in with `CONTAINER_IP` and TCP port `9001`. And the weechat relay password you have put into `/config/weechat/relay.conf`. Make sure you have selected the SSL/TLS secure connection option. Since it is not configured for regular (unsecured) http.\n\n\n## IRC Servers\n\nIRC Networks and channels pre-configured. However they are not all switched on by default. You will need to go into your znc web settings to enable / disable each networks you want to znc to connect to.\n\n#### Public IRC networks\n\n * barton\n * `#ngircd`\n * public help / support channel\n\n * dalnet\n\n * efnet\n\n * freenode\n * `#atheme`\n * public help / support channel\n * `#irssi`\n * public help / support channel\n * `#limnoria`\n * public help / support channel\n * `#weechat`\n * public help / support channel\n * `#znc`\n * public help / support channel\n\n * gnome\n\n * ircnet\n\n * mozilla\n\n * oftc\n * `#bitlbee`\n * public help / support channel\n\n * quakenet\n\n * undernet\n\n\n#### Private / localhost services\n\n * \"ngircd\"\n * `#local` sandbox channel (for limnoria / \"supybot\")\n\n * bitlbee\n * `&bitlbee` - connect using IM chat protocols\n\n\n## Editing configuration files\n\nThe text editor `nano` is included for simple editing of configuration files. e.g. `nano /config/irssi/config`. Be careful to do that under the right unix user instead of `root`.\n\nFor example:\n\n```sh\nsudo su -l znc [return]\nnano /config/znc/configs/znc.conf [return]\n\n# or\nsudo su -l irssi [return]\nnano /config/irssi/config [return]\n```\n\n## Configuration\n\nPre-seeded Configuration Folder:\n\nAll configuration files are held in the working folder `/config`. There are different versions of the config folder. See [`config.default/README.md`](config.default/README.md) and [`config.custom/README.md`](config.custom/README.md) for more information about those.\n\n### ssh\n\nFor ssh terminal access you can put your existing ssh public key (e.g. `id_rsa.pub`) into `/config/irssi/.ssh/known_hosts` file. Else a new keypair will be automatically generated per container on first run. And the resultant `id_rsa` private key file can be copied from `/config/irssi/.ssh/id_rsa` of your new running container's mounted `/config` volume.\n\n### znc\n\nPrimarily you will want to change the znc admin username and password to something else more secure. And to be your own IRC nickname.\n\nThe znc server will be configurable from any standard web browser, available on SSL protocol `https://$your_container_ip:6697`. The default username and password for znc admin user is `znc:znc`. It is recommended to then goto manage users --> Duplicate the default `znc` user with your own IRC nick name.\n\nThe `znc.conf` text file can also be edited directly. It is stored in the usual loacation at `/config/znc/configs/znc.conf`\n\n### weechat\n\nYour irc login settings are held in the file `/config/weechat/irc.conf`. The password for glowing-bear web interface is held in `/config/weechat/relay.conf`.\n\n### irssi\n\nAssuming that you have changed the znc username and password, then you must also change those `/server` lines in the irssi config file. To use your new znc nick name and password. This file is located at `/config/irssi/config`.\n\n### Notifications to your i-Devices, android, Desktop, etc.\n\nThe recommended notification system to use is znc's [`*push`] module](https://github.com/jreese/znc-push). Which you will need to configure for your target device. Unfortunately ATTO znc push only [supports 1 service at a time](https://github.com/jreese/znc-push/issues/162).\n\nHowever both irssi and weechat are also kept running all of the time. So in addition to znv `*push`, you can also install any extra notifications addons / scripts for those programs as you wish. \n\n### IRC Data\n\nGenerated data gets written to thedocker volume `/irc`.\n\nNote: An additional docker image, `dreamcat4/nginx` or `dreamcat4/samba` is also useful. To more easily access the contents of this `/irc` data folder on your LAN.\n\n### Logs\n\nBy default all IRC channel logs are kept by ZNC and written to the `/irc/znc/logs` folder.\n\n### URLs\n\nThe irssi `urlplot` script is pre-configured to write all posted urls to `/irc/irssi/urlplot` folder. In both HTML and CSV format. The generated HTML file can bookmarked in your local web browser for easy access.\n\nThere are also URL plugins for znc and weechat, however their generated 'text only' output is not as good as html files created by `urlplot`.\n\n### Bitlbee\n\nTends to be configured interactively by commands to the `&bitlbee` control channel, all done while running irssi client. Or by hand-editing the config file at `/config/bitlbee/bitlbee.conf`.\n\n### tmux\n\nThe config file is located at `/config/irssi/.tmux.conf` (for irssi), and `/config/weechat/.tmux.conf` (for weechat).\n\nThis default tmux config does not really need any specific per user configuration. Unless you want to customize the behaviour of tmux more to your liking. For example to hide the `tmux ...` line at the top of the screen, or change the key-bindings etc.\n\n### Limnoria (aka supybot)\n\nNOTE: YOU SHOULD CHANGE YOUR BOT'S NICK FROM `supybot` ---> `YOUR BOT`\n\n* The config file is located at `/config/limnoria/supybot.conf`\n* The default owner nickname of this bot is `znc_user`\n* The default owner password for this bot is `supybot`\n* Connects to the znc user named `supybot` with znc password `supybot` <-- CHANGE THIS IN YOUR ZNC CONFIG TOO\n* This bot is pre-configured to only connect join the channel `#local` on your own private `ngircd` IRC server\n* Public IRC networks are also pre-configured in `supybot.conf`. They are just all disabled by default except for ngircd\n\nHow to identify yourself to the bot as it's owner:\n\n```\n@list --unloaded\n#. supybot# znc_user: Error: You don't have the owner capability. If you think that you should have this capability, be sure that you are identified before trying again. The 'whoami' command can tell you if you're identified.\n\n@whoami\n#. supybot# znc_user: I don't recognize you. You can message me either of these two commands: \"user identify \" to log in or \"user register \" to register.\n\n/query supybot user identify znc_user supybot\n-supybot(~supybot@localhost)- The operation succeeded.\n```\n\nYou will need to change the owner in `supybot.conf` to your real nick, if you didnt already do so in the quickstart instructions. This involves stopping the container, and changing the owner name setting in the file `/config/limnoria/conf/users.conf`. Then restart the container.\n\nNow we can login again, and change the owner password to something more secure than `supybot` before taking it online to public irc servers:\n\n```\n/query supybot user identify YOUR_IRC_NICKNAME supybot\n-supybot(~supybot@localhost)- The operation succeeded.\n\n/query supybot user set password supybot YOUR_NEW_BOT_OWNER_PASSWORD\n-supybot(~supybot@localhost)- The operation succeeded.\n```\n\n**EXTRA NOTE:**\n\nGoing online to public servers with an IRC bot can be considered bad behaviour. Or suspicious due to botnets etc. So using a bot in the wrong way(s) can very quickly get you banned. Either from a specific channel, or IRC network, or even multiple IRC networks! Due to shared global blacklisting mechanisms. So be sure to check any relevant bot policies for those specific network(s) and channel(s) before taking your supybot online to any specific networks or channels. Check with a actual human being, and be asking for clarification / permission to do so where applicable.\n\n### ngircd\n\nProvides the `#local` channel. Which is where znc and the supybot are pre-configured to automatically join to. This is your playground to configure / use the bot before taking it online elsewhere.\n\n* The config file is located at `/config/ngircd/ngircd.conf`\n* This irc server is pre-configured to listen only on the localhost `127.0.0.1` network interface.\n* Includes pairing passwords for the localhost `atheme` services daemon.\n\n**NOTE:**\n\nThis IRC server is minimally configured. But should be safe to use for private localhost use only. To be taking this ngircd instnace public (exposing ports to outside). Then at very least you should change the atheme pairing passwords. In both ngircd config file and atheme's config file.\n\nHowever its not recommended to use this single fat image for any public of semi-public hosting. As other IRC programs are running in the same image. For better hardening, use seperate sigle-service docker images, each linked together. For example 1 container for ngircd, 1 container for atheme services.\n\n### atheme irc services\n\n* The config file is located at `/config/atheme/atheme.conf`\n* These servcies are only minimally configured (enough to work with the ngircd instance)\n* The actual services offered (nickserv, chanserv, sasl, etc) are all left at defaults\n* The pairing passwords (for connection to this IRC services daemon) are also configured in `ngircd.conf`\n\n### Bitlbee chat protocols\n\nComes installed with all the necessary 3rd party plugins for all the most popular non-core protocols including WhatsApp, Steam Chat, Telegram, Facebook, Skype (via 'SkypeWeb') and so on.\n\nSo for any of the below links, you do not need to install a","has_starred","hub_user","immutable_tags_settings",{"_76":11,"_77":78},"enabled","rules",[79],".*","is_automated","permissions",{"_83":22,"_84":11,"_85":11},"read","write","admin","user","storage_size",155631658775,"orgData","recentTags",[92],{"_93":44,"_94":95,"_96":97,"_98":99,"_100":101,"_50":119,"_120":95,"_121":33,"_122":56,"_57":123,"_124":125,"_126":110,"_127":119,"_128":66,"_129":22},"content_type","creator",190978,"full_size",738068851,"id",2607367,"images",[102],{"_103":104,"_105":106,"_107":108,"_109":110,"_111":112,"_113":114,"_115":108,"_116":-5,"_117":97,"_63":66,"_118":-5},"architecture","amd64","digest","sha256:f2011246dcfcd5a2921d9cbc80c0b64669946a5ef89a9a66810742b8d67ed94d","features","","last_pulled","2026-11-02T03:42:10.703218386Z","last_pushed","2020-11-01T12:03:51Z","os","linux","os_features","os_version","size","variant","2020-11-01T12:03:50.258444Z","last_updater","last_updater_username","media_type","latest","repository",629448,"tag_last_pulled","tag_last_pushed","tag_status","v2","sbxKitMetadata","isPotentialSpam","isHubSbxKitsEnabled","showSbxRunInCloud","showSbxLogoOverride","sbxTrademarkText","displaySecurityMetadata","tagAttestations","tagsHaveAttestations",[],"selectedTag","attestationsUrl","routes/_layout.r.$namespace.$reponame.tags",{"_38":144,"_151":152,"_138":161,"_162":11},{"_40":145,"_42":146,"_45":46,"_47":48,"_49":11,"_50":51,"_52":53,"_54":147,"_57":35,"_32":33,"_58":59,"_60":44,"_61":62,"_63":64,"_65":66,"_67":-5,"_68":69,"_70":71,"_72":11,"_73":33,"_74":148,"_80":22,"_81":150,"_86":33,"_87":88},[],[44],[56],{"_76":11,"_77":149},[79],{"_83":22,"_84":11,"_85":11},"tags",{"_153":64,"_154":-5,"_155":-5,"_156":157},"count","next","previous","results",[158],{"_93":44,"_94":95,"_96":97,"_98":99,"_100":159,"_50":119,"_120":95,"_121":33,"_122":56,"_57":123,"_124":125,"_126":110,"_127":119,"_128":66,"_129":22},[160],{"_103":104,"_105":106,"_107":108,"_109":110,"_111":112,"_113":114,"_115":108,"_116":-5,"_117":97,"_63":66,"_118":-5},[],"canDeleteTags","actionData","errors"]

dreamcat4/irc

Tags for dreamcat4/irc