Aurora IRC Client User Guide

Version 0.8.4

Aurora IRC Client is a Linux-native IRC client designed around a familiar HexChat/XChat-style workflow while maintaining its own identity, interface, and development direction.

Official project home: https://greyline86.com/irc-client/

Maintainer: Brandin Hess, AL1AR

Email support: packages@greyline86.com

Live IRC support: irc.greyline86.com, channel #aurora

Aurora is maintained as a one-person project. Live support is available when possible, but replies may not be immediate.

1. What's New in v0.8.4

Added local font-family selection for the main chat/input area.
Added separate local font-family selection for the channel/server tree.
Added separate local font-family selection for the user list.
Font lists are populated from fonts available through Qt on the user's computer.
Strengthened font-size application across chat views, input controls, the channel tree, user list, and status labels.
Added safe fallback behaviour when a saved font is unavailable on another Linux installation.
Removed stylesheet font declarations that could override user preferences on some distributions.
Retained per-buffer input history and keyboard chat navigation.

2. Coming from HexChat or XChat?

Aurora uses many concepts familiar to experienced IRC users:

A server and channel tree on the left.
A central conversation buffer.
A channel topic bar.
A user list on the right.
Standard slash commands.
Per-buffer input history.
Keyboard-driven navigation.
Persistent logs and scrollback.
Separate server, channel, and private-message views.

Aurora is not intended to be a direct clone. It provides a familiar Linux-first workflow while continuing to develop independently.

3. Installation

Debian package

Download the .deb package and install it from a terminal:

cd ~/Downloads
sudo apt install ./aurora-irc_0.8.4-1_all.deb

Close Aurora before replacing an installed version.

Source tarball

cd ~/Downloads
tar -xzf aurora-irc-0.8.4.tar.xz
cd aurora-irc-client-v0.8.4
python3 main.py

PySide6

Aurora requires Python 3 and PySide6. On distributions that provide PySide6 packages, use the distribution package manager. On older Ubuntu or Linux Mint releases where PySide6 is unavailable from APT:

python3 -m pip install --user PySide6

Configuration and data locations

User configuration:

~/.config/aurora-irc-client/

Logs:

~/.local/share/aurora-irc-client/logs/

Downloaded updates:

~/Downloads/

4. First Launch

On first launch, Aurora opens its setup workflow.

Create a network profile with:

A descriptive network name.
Server hostname.
Port.
TLS/SSL setting.
Nickname.
Username or ident.
Real name.
Auto-join channels.
Optional connect commands.
Optional certificate exceptions.

Use a TLS-enabled port whenever the network supports it.

5. Network Profiles

Open the Network List to create, edit, delete, connect to, or reconnect saved networks.

A profile can store:

Server address and port.
TLS preferences.
Nickname, username, and real name.
Auto-connect behaviour.
Auto-join channel list.
Commands to run after registration.
Operator-related preferences where configured.

Quick Connect creates a temporary server entry without requiring a permanent saved profile.

Ctrl+T opens the server-tab workflow, including access to saved networks, Network List management, and Quick Connect.

6. Connecting to IRC Networks

Aurora sends standard registration information and performs basic IRCv3 capability negotiation.

Current compatibility features include:

CAP LS 302
Conservative multi-prefix capability requests
CAP ACK, CAP NAK, and CAP END handling
Automatic PING/PONG
Per-network latency measurement
Nickname collision handling
TLS connections
Configurable connect commands

Some networks enforce their own account, SASL, proxy, DNSBL, cloak, or client-policy rules. A rejection is not always an Aurora error; read the server's disconnect text carefully.

7. Main Window

Server and channel tree

The left side contains connected servers, channels, service conversations, and private-message views.

Aurora uses distinct activity colours:

Normal message activity.
Mentions or highlights.
Membership activity such as JOIN, PART, QUIT, KICK, and nickname changes.

This separation prevents routine membership traffic from looking like an important conversation.

Chat buffer

The centre displays server output, channel conversation, private messages, notices, actions, and status lines.

Your own nickname appears in green. Other users' nicknames appear in blue. Loaded scrollback uses the same colour rules as live messages.

Topic bar

Channel views display the current topic above the chat buffer. Topic editing depends on your privileges and the network's rules.

User list

The right side displays channel members and privilege dots.

Owner/founder
Admin
Operator
Half-operator
Voice
Regular user

The summary line shows total users and channel operators.

When your local away state is active, your nickname text is dimmed while its privilege dot remains unchanged.

Status area

The bottom area contains your nickname, input box, connection state, and active network lag.

Each server tracks its own latency. Background-network lag updates do not overwrite the active network's displayed value.

8. Server, Channel, and Private-Message Views

Server view

Displays registration replies, MOTD, server notices, connection messages, WHOIS results, and administrative status.

Channel view

Displays channel conversation, topic, user list, membership activity, and local message history.

Private-message view

Displays direct conversation with another user.

Input history is stored independently for each view. Text entered in one channel does not appear when browsing history in another channel.

9. Keyboard Shortcuts

Shortcut	Action
`Ctrl+T`	Open a new server-tab/network selection workflow
`Ctrl+W`	Close the active view where supported
`Up Arrow`	Recall the previous entry typed in the current buffer
`Down Arrow`	Move forward through the current buffer's input history
`Tab`	Complete a nickname
`Shift+Tab`	Cycle nickname completion backward where available
`Page Up`	Scroll the active chat buffer upward
`Page Down`	Scroll the active chat buffer downward
`Ctrl+Home`	Jump to the oldest line in the active buffer
`Ctrl+End`	Jump to the newest line in the active buffer
`Enter`	Send the current input

Input-history draft preservation

When you have unfinished text in the input box and press Up Arrow, Aurora stores that draft before showing older entries. Press Down Arrow until you reach the newest position to restore the unfinished text.

Aurora keeps up to approximately 100 entries per server, channel, or private-message buffer during the current application session.

10. Chat Features

Timestamps

Timestamps can be shown or hidden. Changing timestamp visibility re-renders existing visible scrollback.

Persistent scrollback

Aurora loads recent logged conversation into views. Previously logged messages retain their original timestamps and correct nickname colours.

Mentions and attention

Messages mentioning your nickname can trigger highlight colouring and desktop/window attention.

Membership events

JOIN, PART, QUIT, KICK, and nickname changes are displayed in affected channels when enabled.

11. Command Reference

`/join`

Join a channel.

/join #channel

`/part`

Leave the current or specified channel.

/part
/part #channel
/part #channel reason

`/msg`

Send a private message.

/msg nickname message

`/me`

Send an IRC action to the active channel.

/me waves

`/nick`

Change your nickname.

/nick NewNickname

`/whois`

Request information about a user.

/whois nickname

WHOIS output may include username, hostname, real name, server, channels, idle time, account, operator status, TLS status, and away text. Available fields depend on the network.

`/away`

Set your away status.

/away
/away Out for lunch

Without text, Aurora uses a generic away message.

`/back`

Clear your away status.

/back

`/invite`

Invite a user to a channel.

/invite nickname
/invite nickname #channel

When no channel is supplied, Aurora uses the active channel. Aurora waits for server numeric 341 before reporting success. Networks that reject INVITE may return numeric 421 or another error.

`/list`

Open or request the channel list.

/list
/list search-text

`/motd`

Display or request the selected server's Message of the Day.

/motd

`/ping`

Send a manual latency test.

/ping

`/raw`

Send a raw IRC protocol line. Use this only when you understand the command.

/raw COMMAND parameters

`/quit` or `/disconnect`

Disconnect from the current network.

/quit
/disconnect

`/reconnect`

Reconnect the current network.

/reconnect

Aurora may also include network- or services-specific helper commands depending on the build and profile.

12. CTCP Support

Aurora responds to:

VERSION
PING
TIME
CLIENTINFO
ACTION

The VERSION reply identifies Aurora IRC Client and provides the official project page:

https://greyline86.com/irc-client/

13. Checking for Updates

Open:

Help → Check for Updates

Aurora checks:

https://repo.greyline86.com/

When an update is available, Aurora offers to open the official Greyline86 releases area.

Aurora deliberately does not install updates automatically because installation requires administrator privileges and differs across Linux distributions and desktop environments.

For a Debian package:

cd ~/Downloads
sudo apt install ./aurora_irc_client_VERSION_all.deb

14. Preferences

Available preferences may include:

Timestamps.
Logging.
Scrollback limits.
JOIN/PART display.
Server PING visibility.
Theme and interface behaviour.
Notification behaviour.
Reconnection-related settings.

Changes affecting message rendering may cause existing views to re-render.

15. Logs

Aurora stores logs beneath:

~/.local/share/aurora-irc-client/logs/

Each network receives its own directory. Channel, server, and private-message logs are separated.

Diagnostic logs may also record selected inbound and outbound protocol events to assist with troubleshooting.

The downloadable package does not contain private network profiles, passwords, connect commands, or your personal logs.

16. Troubleshooting

The Debian package will not install

Use a terminal instead of the graphical software installer:

cd ~/Downloads
sudo apt install ./aurora_irc_client_VERSION_all.deb

Then repair incomplete dependencies if necessary:

sudo apt --fix-broken install

PySide6 is missing

Try your distribution's PySide6 packages first. On older Linux Mint or Ubuntu systems:

python3 -m pip install --user PySide6

Aurora cannot connect

Check:

Server hostname.
Port.
TLS setting.
Local firewall.
DNS resolution.
Network bans or DNSBL restrictions.
Server password or account requirements.
Server disconnect message.

A network disconnects Aurora immediately

The network may require account registration, SASL, a specific TLS policy, a valid ident, a non-blocked address, or other network-specific rules. Aurora supports basic IRCv3 CAP negotiation and CTCP identification, but not every optional network extension.

Nickname already in use

Aurora automatically tries a modified nickname. You can also use:

/nick AnotherNick

Icons are missing

Reinstall the Debian package and refresh the icon cache:

sudo gtk-update-icon-cache -f /usr/share/icons/hicolor

Log out and back in if the desktop still shows a cached icon.

Update checking fails

Confirm that this page opens in a web browser:

https://greyline86.com/irc-client/

Also check system time, TLS certificates, DNS, firewall, and Internet connectivity.

Old messages show incorrect colours

Aurora v0.5.12 and later pass the active network nickname directly to the scrollback renderer. Upgrade to the latest release and reconnect.

17. Frequently Asked Questions

Is Aurora a HexChat clone?

No. Aurora uses a familiar workflow inspired by established IRC clients but is developed independently.

Does Aurora support multiple networks?

Yes. Each network maintains separate connection state, latency, server output, channels, private messages, and input history.

Is input history shared between channels?

No. Beginning with v0.7.0, input history is per buffer.

Does Aurora automatically install updates?

No. It downloads updates and gives manual installation instructions.

Does Aurora store passwords in the release package?

No. User-specific profiles and credentials remain in the user's local configuration directory.

Why can one network behave differently from another?

IRC networks use different daemon software, services packages, capabilities, policies, and security controls.

Where can I report a problem?

Use the support details below and include:

Aurora version.
Linux distribution and version.
Installation method.
IRC network.
Exact server error.
Steps to reproduce the issue.

18. Getting Support

Project home

https://greyline86.com/irc-client/

Email

packages@greyline86.com

IRC

Server: irc.greyline86.com

Channel: #aurora

Please allow time for a response. Aurora IRC Client is maintained as a one-person operation.

19. About Aurora

Aurora IRC Client is developed and maintained by:

Brandin Hess, AL1AR

Aurora is a Linux-native IRC client focused on a familiar workflow, clear multi-network state, useful keyboard operation, dependable logging, and practical compatibility with IRC networks.

Aurora IRC Client User Guide