tools:irc
Differences
This shows you the differences between two versions of the page.
Both sides previous revisionPrevious revisionNext revision | Previous revision | ||
tools:irc [2025/08/30 11:29] – [Connecting to Chat Rooms] Humphrey Boa-Gart | tools:irc [2025/09/01 08:19] (current) – Humphrey Boa-Gart | ||
---|---|---|---|
Line 1: | Line 1: | ||
====== Internet Relay Chat (IRC) ====== | ====== Internet Relay Chat (IRC) ====== | ||
- | |||
- | [{{ : | ||
**Internet Relay Chat** (or **IRC**) is one of the oldest chat platforms. However, it is not a service, nor an application, | **Internet Relay Chat** (or **IRC**) is one of the oldest chat platforms. However, it is not a service, nor an application, | ||
Line 10: | Line 8: | ||
===== AMI @ IRC ===== | ===== AMI @ IRC ===== | ||
- | The Anonymous Military Institute' | + | The Anonymous Military Institute' |
===== IRC Clients ===== | ===== 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. | 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:// | ||
* [[https:// | * [[https:// | ||
* [[https:// | * [[https:// | ||
Line 72: | Line 71: | ||
Chat rooms on IRC are called **channels**, | Chat rooms on IRC are called **channels**, | ||
- | 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 ''/ | + | 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 irc.freenode.net | + | /server irc.hackint.org |
| | ||
Once you are connected, you can type ''/ | Once you are connected, you can type ''/ | ||
Line 84: | Line 83: | ||
==== Managing Your " | ==== Managing Your " | ||
- | IRC does not require registration, | + | IRC does not require registration, |
- | Some servers have nickname registration services, allowing you to keep other people from stealing your nick. On Freenode | + | Some servers have nickname registration services, allowing you to keep other people from stealing your nick. On Hackint |
You can get a list of available NickServ options with the '' | You can get a list of available NickServ options with the '' | ||
Line 145: | Line 144: | ||
IRC's simple text-based interface hides a lot of functionality. Some things which you may find useful: | IRC's simple text-based interface hides a lot of functionality. Some things which you may find useful: | ||
+ | |||
+ | |||
+ | ==== Secure IRC ==== | ||
+ | |||
+ | IRC is not the most secure platform in the world, but a few simple tricks can dramatically increase your privacy: | ||
+ | |||
+ | === IRC over VPN's === | ||
+ | |||
+ | Depending on how you are using IRC, you may not always need a [[security: | ||
+ | |||
+ | 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 [[: | ||
+ | |||
+ | === IRC over TLS/SSL === | ||
+ | |||
+ | Most modern IRC clients support encrypted connections between client-server with TLS //(the modern successor to SSL)//. You should enable this, as it will keep people on your local network from being able to read your communications, | ||
+ | |||
+ | TLS/SSL connections are made over different ports than non-encrypted connections. For IRC, this is usually be on **Port 6697**, but it can vary from server to server. | ||
==== Channel Management ==== | ==== Channel Management ==== | ||
Line 174: | Line 192: | ||
You can also change '' | You can also change '' | ||
- | === Access Level System === | ||
- | /msg ChanServ access # | + | === Kicking People Out === |
- | Adds a user to the access list with that level. If a user is already on the list, their level will simply be changed to the specified level. | + | Too much of a pussy to kick or ban someone yourself? ChanServ can do it for you! |
- | /msg ChanServ access | + | /msg chanserv (kick|ban) |
- | Deletes a user from the access list. | + | **Note:** If the channel has signkick enabled (default), your nick will be displayed in the kick message. |
- | By default, the following access levels are defined: | + | ==== Secure Noticing ==== |
- | * Founder - Gives +qo upon entering, allows full access to ChanServ commands. Only one user may have this status. | + | To send a message to everyone on a channel with a certain level or higher, type this: |
- | * 10 - Gives +ao upon entering, allows access to akick. | + | |
- | * 5 - Gives +o upon entering. | + | |
- | * 3 - Gives +v upon entering. | + | |
- | * 0 - Nothing. | + | |
- | * <0 - User cannot be opped. | + | |
- | === ChanServ kick === | + | /notice (~|& |
- | Too much of a pussy to kick/ban someone yourself? ChanServ can do it for you! | + | where the symbol represents the minimum level to send the message to (see " |
- | /msg ChanServ (kick|ban) # | + | Use this to share sensitive information without spais finding out. |
- | Note that if the channel has signkick enabled (default), your nick will be displayed in the kick message. | ||
+ | ==== Custom Hostnames ==== | ||
- | ==== Secure Noticing ==== | + | Normally when you join a channel, people see a long ugly hostname - a sort of long-form address that corresponds to your IP address. However, with a registered nick, you can replace your plain old hostname with a vHost, which is basically just a fake hostname that looks a lot prettier. |
- | To send a message | + | To request |
- | /notice (~|&|@|%|+)# | + | /msg hostserv request vhost@goes.here |
- | where the symbol represents the minimum level to send the message | + | 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 |
- | Use this to share sensitive information without spais finding out. | + | 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) |
- | ==== HostServ | + | ==== IRC in the Cloud ==== |
+ | |||
+ | 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, | ||
+ | |||
+ | 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:// | ||
+ | |||
+ | 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: | ||
+ | |||
+ | |||
+ | ===== 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) | ||
+ | |||
+ | < | ||
+ | : | ||
+ | : | ||
+ | : | ||
+ | </ | ||
+ | |||
+ | |||
+ | |||
+ | ==== Configuring WeeChat ==== | ||
+ | |||
+ | Eventually you may need more functionality out of your IRC client, and when that time comes you will need a [[tools: | ||
+ | |||
+ | You can install WeeChat in Debian with the '' | ||
+ | |||
+ | $ 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/ | ||
+ | |||
+ | Then, use the ''/ | ||
+ | |||
+ | /connect hackint | ||
+ | |||
+ | Once you are connected, you can type ''/ | ||
+ | |||
+ | To keep WeeChat alive on a remote machine, simply run it inside [[tools: | ||
- | With a registered nick, you can replace your plain old hostname with a vHost, which is basically just a fake hostname. | + | ==== Configuring irssi ==== |
- | To request | + | Many power users prefer irssi as a terminal IRC client. Like WeeChat, it can be run locally, and on a remote machine via SSH. |
- | /msg HostServ request vhost@goes.here | + | {{wst> |
- | 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. | ||
{{tag> | {{tag> |
tools/irc.1756553351.txt.gz · Last modified: by Humphrey Boa-Gart
Find this page online at: https://bestpoint.institute/tools/irc
Find this page online at: https://bestpoint.institute/tools/irc