┬ ┌┬┐ ┬─┐ ┬─┐ ┬─┐ ┌┐┐ ┬─┐
│ │ │─│ │─ │┬┘ │ │─┤
┘─┘ └┴┘ │─┘ ┴─┘ │└┘ ┘ ┘ │
┌─┐ ┬─┐ ┐─┐ ┬─┐
│ │─┤ └─┐ │─┤
└─┘ ┘ │ ──┘ ┘ │
KiwiIRC Webchat | Gamja Webchat | Convos Webchat/Bouncer
Hostnames are cryptographically cloaked so that your IP address information is not visible to others.
It is still visible to server administrators.
To connect configure your IRC client as follows:
If you would like to anonymize the connection against the administrators,
you can access the network via
Webchat via Tor is available through the links on the top - KiwiIRC will offer the best experience.
Guide to setting up i2p here
Use the samle configuration shown above.
Account registration FAQ
1. How do I register my nickname / account?
Use this command, substituting your desired password and e-mail address:
/msg NickServ register mySecretPassword
You can also register on this page here
Once you register your nick it becomes your account name. It is the name with which you are expected to login.
2. How do I authenticate to my nickname?
You should enable SASL in your client. For clients like Hexchat the Username field needs to be populated with the name that you registered.
If your client doesn't support SASL, there are potential workarounds;
you may be able to script your client to authenticate to NickServ
automatically, with `/msg NickServ identify nickname password`.
Ask in #help for support with this.
3. What are the benefits of registering my nickname?
The primary benefit of nickname registration is that the server can act
as an "IRC bouncer" on your behalf. Specifically:
a. No one else will be able to use your nickname
b. If all your clients are configured to use SASL, they can all use the same
nickname (as though they were connected to the same ZNC instance)
c. Optionally, the server can keep you present on the server even if
you have no connected clients. To enable this, use the following command:
`/msg NickServ set always-on true`
d. You will be able to receive history playback (see below).
You can also request a vhost in the channel #help (i.e., a fake hostname that will be displayed
in place of your cloaked IP-based hostname).
4. History Playback.
1 If you set your client to `always-on` (see the previous section for details), you can set a "device ID" for each device you use. Oragono will then remember the last time your device was present on the server, and each time you sign on, it will attempt to replay exactly those messages you missed.
2 You can set the SASL Username as `nick@phone` or `nick@laptop` while connecting. This allows you to fetch history based on your "DeviceID" which is `phone` or `laptop` in these cases.
3 If you only have one device, you can set your client to be always-on and furthermore `/NS SET autoreplay-missed true`. This will replay missed messages, with the caveat that you must be connecting with at most one client at a time.
4 You can autoreplay a fixed number of lines (e.g., 25) each time you join a channel using `/NS SET autoreplay-lines 25`.
5 You can manually request history using `/history #channel 1h` (the parameter is either a message count or a time duration). (Depending on your client, you may need to use `/QUOTE history` instead.)
6 You can also enable history for private messages called `DMs` by passing the following command: `/NS SET dm-history true`.
#### Sessions and Clients
- You can check how many of your sessions are online with `/NS SESSIONS `and the idle times for those.
- You can list your clients in further detail with `/NS CLIENTS list`
- You can use `/NS CLIENTS logout client-id/all` to either logout a single session or all sessions.