Differences

This shows you the differences between two versions of the page.

--- tools:irc [2025/08/30 14:48] – [IRC in the Cloud] Humphrey Boa-Gart
+++ tools:irc [2025/09/01 08:19] (current) – Humphrey Boa-Gart
@@ Line 1: / Line 1: @@
 ====== Internet Relay Chat (IRC) ======
-[{{ :tools:ss_1756546943.png?300|Use the following Hexchat config to connect to our IRC server. //(Click to enlarge)//}}]
 **Internet Relay Chat** (or **IRC**) is one of the oldest chat platforms. However, it is not a service, nor an application, but a //**communication protocol**//. Using the IRC protocol, anyone can spin up a chat server with any number of individual chat rooms, and any compatible program can connect to any of these servers.
@@ Line 10: / Line 8: @@
 ===== AMI @ IRC =====
-The Anonymous Military Institute's conference hall is located at **#ami** on [[irc://irc.freenode.net/ami|irc.freenode.net]]. If you are using IRC for the first time, it is recommended you use something simple like [[https://irc.com|IRC.com]], or install [[https://hexchat.github.io/|HexChat]]. Refer to the image to the right for configuring Hexchat, then type ''/join #ami'' once you are connected to Freenode.
+The Anonymous Military Institute's conference hall is located at **#ami** on [[irc://irc.hackint.org/ami|irc.hackint.org]]. If you are using IRC for the first time, it is recommended you use the [[https://chat.hackint.org/?join=ami|webchat]], or install [[https://hexchat.github.io/|HexChat]].
 ===== IRC Clients =====
@@ Line 23: / Line 21: @@
 If you're just getting started and are feeling apprehensive about installing software right away, perhaps consider a **browser-based client** to get a feel for the IRC ecosystem first.
-  * [[https://irc.com|IRC.com]] //("official" Freenode webchat, type ''/join #ami'' after connecting)//
+  * [[https://chat.hackint.org/?join=ami]] //(official Hackint IRC webchat service)//
   * [[https://kiwiirc.com/|KiwiIRC]]
   * [[https://www.irccloud.com/|IRCCloud]] //("always-on" paid service)//
@@ Line 73: / Line 71: @@
 Chat rooms on IRC are called **channels**, which are hosted on **servers**. One server will typically have many channels, and not everyone in one channel will be in the other channels on the same server. Before you can join a channel, you have to connect to a server first.
-There are many servers, but for the sake of this tutorial, we will use **Freenode** as an example, since that's where the AMI's channel is hosted. In most clients, you can do this with the ''/server'' command:
+There are many servers, but for the sake of this tutorial, we will use **Hackint** as an example, since that's where the AMI's channel is hosted. In most clients, you can do this with the ''/server'' command:
-  /server irc.freenode.net
+  /server irc.hackint.org
 Once you are connected, you can type ''/join #ami'' to join our channel.
@@ Line 85: / Line 83: @@
 ==== Managing Your "Account" ====
-IRC does not require registration, and allows you to chat under almost any name //(aka 'nick' or 'nickname' in IRC terminology)// as a guest. To change your nick, type ''/nick newnickhere''. There is a limit on how long the nick can be; some networks only allow a maximum of 9 characters, while others let you go up to 18.
+IRC does not require registration, and allows you to chat under almost any name //(aka 'nick' or 'nickname' in IRC terminology)// as a guest. To change your nick, type ''/nick newnickhere''.
-Some servers have nickname registration services, allowing you to keep other people from stealing your nick. On Freenode (and many other servers) this service is called **NickServ**.
+Some servers have nickname registration services, allowing you to keep other people from stealing your nick. On Hackint (and many other servers) this service is called **NickServ**.
 You can get a list of available NickServ options with the ''help'' command:
@@ Line 154: / Line 152: @@
 === IRC over VPN's ===
-Unless you are connecting from a datacenter //(see **"IRC in the Cloud"** below)// you will want to use a [[security:vpn|VPN]]. This is because on IRC //everyone can see your hostname and IP address//. So if you do not want people tracing back to your location, connect to IRC from a VPN, or from a remote server in the cloud.
+Depending on how you are using IRC, you may not always need a [[security:vpn|VPN]]. If you are using TLS to connect to your favorite IRC servers, then your connection is already encrypted. If you are using IRC remotely //(see **"IRC in the Cloud"** below)// via SSH, then know SSH encrypts your connection as well. So rest assured, if you are hanging out with terrorists on EFNet, all anyone can really see is that you are connecting to EFNet - but they cannot see anything else unless this is happening in a public room on EFNet, which they would have to go find in a list of thousands of channels unless they have a way to man-in-the-middle a TLS connection.
+In many cases you will want to use a VPN. This is mainly because on IRC //everyone can see your hostname and IP address//. So if you do not want people tracing back to your location, connect to IRC from a VPN, or from a //via media// remote server in the cloud.
+You will also want a VPN if you are working sensitive [[:op:operations]] on a private IRC server. If you have a remote client in an opsec-conscious environment, you will want a VPN both ways: both between your local machine and your remote client, and between your remote client and the server. Even with encrypted connections using SSH and TLS, the datacenter can still pick up the IP addresses of everything your remote client talks to, and you cannot always trust the datacenter.
 === IRC over TLS/SSL ===
@@ Line 220: / Line 222: @@
 You will then have to wait for your vHost to be approved. Some networks do it automatically after about a few hours, while other nets have it to where it must be manually approved. This command can vary from server to server, and sometimes you will have to contact a server operator directly to make it happen.
-Some networks let you use real domain names as a vhost.... provided you can prove you own it. This is useful if you are connecting from a cloud machine that is providing other services. (See next section)
+Some networks let you use real domain names as a vhost... provided you can prove you own it. This is useful if you are connecting from a cloud machine that is providing other services. (See next section)
 ==== IRC in the Cloud ====
-IRC was developed in a time before the prevalence of mobile phones and wireless internet connections. Because of this, it is a little frustrating to use on unstable connections, as it connects/disconnects repeatedly. Furthermore, when you are disconnected, you completely miss any messages that are being sent in your favorite channels.
+IRC was developed in a time before the prevalence of mobile phones & wireless internet connections. Because of this, it is a little frustrating to use on unstable connections. Furthermore, when you are disconnected and waiting to reconnect, you completely miss any messages that are being sent in your favorite channels.
-To get around this, you will want to set up an IRC client on a remote machine. For under $10/m, you can get [[https://www.vultr.com/?ref=9732785|a VPS with Vultr]], on which you can install a copy of something bare-bones like Debian, and a [[tools:bash|command-line]] IRC client like [[https://weechat.org/|Weechat]] or [[https://irssi.org/|irssi]]. With your IRC client running 24/7 in the cloud, you can use [[tools:ssh|SSH]] to sign in to your VPS, and check IRC at your leisure without missing a single message.
+To get around this, you will want to set up an IRC client on a remote machine. For under $10/m, you can get a [[https://www.vultr.com/?ref=9732786-9J|Debian VPS with Vultr]] //(complete with automated backups)// on which you want to install [[tools:byobu]] or [[tools:tmux]], and a [[tools:bash|terminal-based]] IRC client like [[https://weechat.org/|WeeChat]] or [[https://irssi.org/|irssi]].
-=== Configuring Weechat ===
+By running an IRC client in this type of software stack, it will stay alive 24/7 even if you disconnect or close the window. When combined with a remote machine, you can use [[tools:ssh|SSH]] to check IRC at your leisure without missing a single message. You can even combine it with [[tools:wireguard|WireGuard]] to obfuscate the location of your VPS's datacenter from other IRC users.
+===== Application Specific Instructions =====
+Here are some quick-start guides for several popular IRC clients, if you need help getting started.
+==== Configuring HexChat ====
+To point HexChat to our IRC, configure it as follows. (Click to enlarge)
+<gallery>
+:tools:ss_1756624530.png Server Settings Pt 2 | Add #ami to your autojoin, save and connect
+:tools:ss_1756624511.png Server Settings Pt 1 | Fill out connection info
+:tools:ss_1756624463.png Network List | Create entry for Hackint, favor and edit
+</gallery>
+==== Configuring WeeChat ====
+Eventually you may need more functionality out of your IRC client, and when that time comes you will need a [[tools:bash|terminal]] client. WeeChat is probably the simplest of the terminal clients to configure. It also has a pretty robust out-of-the-box setup without having to track down plugins. For both these reasons, we recommend using WeeChat if you have never used a terminal-based client before.
+You can install WeeChat in Debian with the ''apt'' command, and then the ''weechat'' command to start it:
+  $ sudo apt install weechat
+  $ weechat
+WeeChat requires a little bit of configuration to get going. First off, you will need to tell WeeChat to use Dynamic Rejoining. With this set, WeeChat will remember which channels you were in last, and automatically rejoin them when you connect:
+  /set irc.server_default.autojoin_dynamic on
+Next, you need to connect WeeChat to a server //(again, we will use Hackint as an example)//. To do this, you first need to define some details about the server:
+  /server add hackint irc.hackint.org/6697 -ssl -autoconnect
+Then, use the ''/connect'' command to connect to Hackint:
+  /connect hackint
+Once you are connected, you can type ''/join #ami'' to enter our IRC channel. To test that autoconnect works, type ''/quit'' to exit WeeChat. Then reopen WeeChat. It should dump you right back into #ami on Hackint. There is no real limit to how many servers/channels you can have WeeChat automatically join.
+To keep WeeChat alive on a remote machine, simply run it inside [[tools:byobu]] or [[tools:tmux]] via [[tools:ssh|SSH]]. Then just reattach to your session when you SSH back in.
+==== Configuring irssi ====
+Many power users prefer irssi as a terminal IRC client. Like WeeChat, it can be run locally, and on a remote machine via SSH.
 {{wst>expand}}
 {{tag>Tools Communication}}

User Tools

Site Tools

Differences