From c53097000bbfd7fad7f2f369cf3293309045e68a Mon Sep 17 00:00:00 2001 From: Shivaram Lingamneni Date: Sun, 13 Jun 2021 15:57:26 -0400 Subject: [PATCH] fix remaining references to Freenode in documentation --- README.md | 2 +- docs/MANUAL.md | 4 ++-- docs/USERGUIDE.md | 2 +- 3 files changed, 4 insertions(+), 4 deletions(-) diff --git a/README.md b/README.md index 91124090..eb9e714d 100644 --- a/README.md +++ b/README.md @@ -104,7 +104,7 @@ With this, you receive a blob of text which you can plug into your configuration ### Nickname and channel registration -Ergo relies heavily on user accounts to enable its distinctive features (such as allowing multiple clients per nickname). As a user, you can register your current nickname as an account using `/msg NickServ register `. Once you have done so, you should [enable SASL in your clients](https://freenode.net/kb/answer/sasl), ensuring that you will be automatically logged into your account on each connection. This will prevent [problems claiming your registered nickname](https://github.com/ergochat/ergo/blob/master/docs/MANUAL.md#nick-equals-account). +Ergo relies heavily on user accounts to enable its distinctive features (such as allowing multiple clients per nickname). As a user, you can register your current nickname as an account using `/msg NickServ register `. Once you have done so, you should [enable SASL in your clients](https://libera.chat/guides/sasl), ensuring that you will be automatically logged into your account on each connection. This will prevent [problems claiming your registered nickname](https://github.com/ergochat/ergo/blob/master/docs/MANUAL.md#nick-equals-account). Once you have registered your nickname, you can use it to register channels: diff --git a/docs/MANUAL.md b/docs/MANUAL.md index 4d7c29ba..d0828df3 100644 --- a/docs/MANUAL.md +++ b/docs/MANUAL.md @@ -257,7 +257,7 @@ If you want to use a TLS client certificate instead of a password to authenticat /NS REGISTER * -Once you've registered, you'll need to set up SASL to login. One of the more complete SASL instruction pages is Freenode's page [here](https://freenode.net/kb/answer/sasl). Open up that page, find your IRC client and then setup SASL with your chosen username and password! +Once you've registered, you'll need to set up SASL to login. One of the more complete SASL instruction pages is libera.chat's page [here](https://libera.chat/guides/sasl). Open up that page, find your IRC client and then setup SASL with your chosen username and password! If your client doesn't support SASL, you can typically use the "server password" (`PASS`) field in your client to log into your account automatically when connecting. Set the server password to `accountname:accountpassword`, where `accountname` is your account name and `accountpassword` is your account password. @@ -273,7 +273,7 @@ In this mode (the default), registering an account gives you privileges over the 1. You must use your nickname, i.e., if you are logged into your account, then the server will require you to use your account name as your nickname 1. If you unregister your account, your nickname will be permanently unreclaimable (thus preventing people from impersonating you) -In this mode, it is very important that end users authenticate to their accounts as part of the initial IRC handshake (traditionally referred to as "connection registration"); otherwise they will not be able to use their registered nicknames. The preferred mechanism for this is [SASL](https://freenode.net/kb/answer/sasl), which is supported by most modern clients. As a fallback, this can also be done via the `PASS` (server password) command; set the "server password" field of the client to `AzureDiamond:hunter2`, where `AzureDiamond` is the account name and `hunter2` is the account password. +In this mode, it is very important that end users authenticate to their accounts as part of the initial IRC handshake (traditionally referred to as "connection registration"); otherwise they will not be able to use their registered nicknames. The preferred mechanism for this is [SASL](https://libera.chat/guides/sasl), which is supported by most modern clients. As a fallback, this can also be done via the `PASS` (server password) command; set the "server password" field of the client to `AzureDiamond:hunter2`, where `AzureDiamond` is the account name and `hunter2` is the account password. As an end user, if you want to change your nickname, you can register a new account and transfer any channel ownerships to it using `/msg ChanServ transfer`. diff --git a/docs/USERGUIDE.md b/docs/USERGUIDE.md index e09f901a..75a03ddf 100644 --- a/docs/USERGUIDE.md +++ b/docs/USERGUIDE.md @@ -72,7 +72,7 @@ Although (as in other IRC systems) basic chat functionality is available without This registers your current nickname as your account name, with the password `mySecretPassword` (replace this with your own secret password!) -Once you have registered your account, you must configure SASL in your client, so that you will be logged in automatically on each connection. [Freenode's SASL guide](https://freenode.net/kb/answer/sasl) covers most popular clients. +Once you have registered your account, you must configure SASL in your client, so that you will be logged in automatically on each connection. [libera.chat's SASL guide](https://libera.chat/guides/sasl) covers most popular clients. If your client doesn't support SASL, you can typically use the "server password" (`PASS`) field in your client to log into your account automatically when connecting. Set the server password to `accountname:accountpassword`, where `accountname` is your account name and `accountpassword` is your account password.