2015-09-19 16:56:56 +02:00
|
|
|
---
|
|
|
|
layout: post
|
|
|
|
comments: true
|
|
|
|
title: "Quickstart with Atheme IRC Services (& forks) for end users"
|
|
|
|
category: [english]
|
|
|
|
tags: [english, irc, atheme]
|
2024-06-03 08:48:19 +02:00
|
|
|
sitemap: true
|
|
|
|
robots: noai
|
2017-07-18 21:31:45 +02:00
|
|
|
redirect_from:
|
2015-10-24 09:29:39 +02:00
|
|
|
- /nickserv.html
|
|
|
|
- /chanserv.html
|
|
|
|
- /groupserv.html
|
|
|
|
- /atheme.html
|
2018-11-25 23:51:24 +01:00
|
|
|
- /english/2015/09/19/atheme-quickstart.html
|
2015-09-19 16:56:56 +02:00
|
|
|
---
|
|
|
|
|
2024-06-19 07:19:44 +02:00
|
|
|
Atheme IRC Services is the most used IRC service package. However many people
|
|
|
|
have difficulties with registering a channel and then managing it, which I
|
|
|
|
attempt to help with here. I start by explaining NickServ registration (and as a
|
|
|
|
bonus HostServ) and then move to channel management and you just cannot talk
|
|
|
|
about that without mentioning GroupServ too...
|
2015-09-19 16:56:56 +02:00
|
|
|
|
|
|
|
## NickServ
|
|
|
|
|
2024-06-19 07:19:44 +02:00
|
|
|
You won't be able to do anything unless you register your nick. This is as easy
|
|
|
|
as `/msg nickserv register PASSWORD someone@example.net`.
|
2015-09-19 16:56:56 +02:00
|
|
|
|
2024-06-19 07:19:44 +02:00
|
|
|
Depending on Atheme configuration on the IRC network you are using, you must
|
|
|
|
verify your email by checking it and copy-pasting the command which starts with
|
|
|
|
`/msg NickServ verify register` to NickServ.
|
2015-09-19 16:56:56 +02:00
|
|
|
|
2024-06-19 07:19:44 +02:00
|
|
|
In case you wish to have multiple nicks in the same account, that is also easy,
|
|
|
|
just `/nick AltNick` and `/msg nickserv group`. You can see nicks you have by
|
|
|
|
using `/msg nickserv info yournick` (other people (except IRC operators) cannot
|
|
|
|
see that part).
|
2015-09-19 16:56:56 +02:00
|
|
|
|
|
|
|
Now you should be successfully identified and should configure automatic
|
2024-06-19 07:19:44 +02:00
|
|
|
identification, I cannot help with it so much, but I can point you to beginning:
|
2015-09-19 16:56:56 +02:00
|
|
|
|
2023-02-22 19:28:38 +01:00
|
|
|
- [liberachat's SASL instructions](https://libera.chat/guides/sasl)
|
|
|
|
- [My instructions for SASL with WeeChat]({% post_url blog/2015-03-26-weechat-sasl-simply %})
|
|
|
|
- [Searx YOURCLIENTHERE SASL](https://search.disroot.org/?q=YOURCLIENTHERE+SASL)
|
2024-06-19 07:19:44 +02:00
|
|
|
- IRCCloud: edit network and go to advanced settings and you will see box for
|
|
|
|
NickServ password.
|
|
|
|
- KiwiIRC: Check "I have a password" and type your passsword there. Ensure that
|
|
|
|
you specified a nick that is grouped to your account.
|
2023-02-22 19:28:38 +01:00
|
|
|
- Matrix: in the admin room (direct chat with the appservice-irc), say
|
2024-06-19 07:19:44 +02:00
|
|
|
`!storepass password` to have the password send with PASS on connect. In case
|
|
|
|
of liberachat use `!storepass nick:password` and/or see more information at
|
|
|
|
[matrix-appservice-irc wiki].
|
2023-02-22 19:28:38 +01:00
|
|
|
- [IRC networks with Matrix bridge]
|
|
|
|
- [Matrix bridge end-user FAQ register/identify section]
|
2017-07-18 21:31:45 +02:00
|
|
|
|
2024-06-19 07:19:44 +02:00
|
|
|
[matrix-appservice-irc wiki]:
|
|
|
|
https://github.com/matrix-org/matrix-appservice-irc/wiki/
|
|
|
|
[irc networks with matrix bridge]:
|
|
|
|
https://github.com/matrix-org/matrix-appservice-irc/wiki/Bridged-IRC-networks
|
|
|
|
[matrix bridge end-user faq register/identify section]:
|
|
|
|
https://github.com/matrix-org/matrix-appservice-irc/wiki/End-user-FAQ#how-do-i-registeridentify-to-nickserv
|
2015-09-19 16:56:56 +02:00
|
|
|
|
|
|
|
## HostServ
|
|
|
|
|
2024-06-19 07:19:44 +02:00
|
|
|
In case the network you are on has HostServ, you can get vhosts with it. Vhosts
|
|
|
|
appear in place of your real host/cloaked host, but
|
2015-09-19 16:56:56 +02:00
|
|
|
[won't hide your IP](https://gist.github.com/maxteufel/1e2cf7ada079c271bd3c).
|
|
|
|
|
|
|
|
There are two ways to get a vhost, take one that is offered to everyone or
|
|
|
|
request something.
|
|
|
|
|
2024-06-19 07:19:44 +02:00
|
|
|
- Check `/msg hostserv offerlist` and if you see something you like, you can
|
|
|
|
enable it with e.g. `/msg hostserv take $user.irc.example.net` and running
|
|
|
|
`/msg hostserv on`.
|
|
|
|
- Use `/msg nickserv request blah` and when you receive message telling you that
|
|
|
|
your requested vhost has been approved use `/msg hostserv on`.
|
2015-09-19 16:56:56 +02:00
|
|
|
|
|
|
|
## ChanServ
|
|
|
|
|
2024-06-19 07:19:44 +02:00
|
|
|
And finally to the topic which seems to be the most difficult, channel (access)
|
|
|
|
management.
|
2015-09-19 16:56:56 +02:00
|
|
|
|
2024-06-19 07:19:44 +02:00
|
|
|
First register the channel with `/msg ChanServ register #channel` while you are
|
|
|
|
opped. Now you are free to setup the channel as you wish.
|
2015-09-19 16:56:56 +02:00
|
|
|
|
|
|
|
I use the following templates, so I can e.g.
|
2015-09-19 17:05:19 +02:00
|
|
|
`/msg chanserv flags #channel someone op` instead of
|
|
|
|
`/msg chanserv flags #channel someone +vVhHoOirtAe`. You can also use the
|
|
|
|
network defaults that you can see with `/msg chanserv template`.
|
2015-09-19 16:56:56 +02:00
|
|
|
|
2023-02-22 19:28:38 +01:00
|
|
|
_This is a bash scripts which is ran like `./cstemplate #channel` and
|
2024-06-19 07:19:44 +02:00
|
|
|
copy-pasted to ChanServ. It basically allows ops to do everything they could do
|
|
|
|
anyway by being opped using services and "trusted users" have became regulars on
|
|
|
|
channels I am on. If a flag doesn't exist on the network you are on, Atheme will
|
|
|
|
just silently ignore it._
|
2015-09-19 16:56:56 +02:00
|
|
|
|
2024-06-19 07:19:44 +02:00
|
|
|
**You should see my cstemplate script here, but the embedding isn't working, to
|
|
|
|
see it
|
|
|
|
[please click here to go to the GitHub instance of it](https://github.com/Mikaela/gist/blob/master/irc/atheme/cstemplate).**
|
2015-09-19 16:56:56 +02:00
|
|
|
|
2024-06-19 07:19:44 +02:00
|
|
|
Another example using my templates would be
|
|
|
|
`/msg ChanServ flags #channel !channel-ops op` which would give op permissions
|
|
|
|
above to users in the !channel-ops group.
|
2015-09-19 16:56:56 +02:00
|
|
|
|
|
|
|
## GroupServ
|
|
|
|
|
2024-06-19 07:19:44 +02:00
|
|
|
I mentioned groups a little earlier and now I am returning to them. They are a
|
|
|
|
way to manage flags of group of users very easily by having all users in the
|
|
|
|
group and just setting flags to the group instead of invidual users.
|
2015-09-19 16:56:56 +02:00
|
|
|
|
2024-06-19 07:19:44 +02:00
|
|
|
_GroupServ is undervalued service and it might not be surprising if it's missing
|
|
|
|
from your network :(_
|
2015-09-19 16:56:56 +02:00
|
|
|
|
2024-06-19 07:19:44 +02:00
|
|
|
Start by creating your group `/msg groupserv register !blah` (you might want to
|
|
|
|
register a more descriptive name).
|
2015-09-19 16:56:56 +02:00
|
|
|
|
2024-06-19 07:19:44 +02:00
|
|
|
Next, as in this example this group is going to be op #somewhere we close the
|
|
|
|
group: `/msg groupserv set !group open off`.
|
2015-09-19 16:56:56 +02:00
|
|
|
|
2024-06-19 07:19:44 +02:00
|
|
|
Now there are only two tasks left, making the group op and adding ops there:
|
2015-09-19 16:56:56 +02:00
|
|
|
|
2023-02-22 19:28:38 +01:00
|
|
|
- `/msg chanserv flags #channel !blah op`
|
2024-06-19 07:19:44 +02:00
|
|
|
- where `op` can still be replaced with `aop` if you are following Atheme
|
|
|
|
defaults or some other template you created or your own set of flags.
|
2023-02-22 19:28:38 +01:00
|
|
|
- `/msg groupserv flags !blah user +c`
|
2024-06-19 07:19:44 +02:00
|
|
|
- Repeat as many times as you have ops, to remove ops you simply remove their
|
|
|
|
`-c` flag or all flags (`-*`). You will also want to read
|
2023-02-22 19:28:38 +01:00
|
|
|
`/msg groupserv help flags` as there is more than I said here.
|
2015-09-19 16:56:56 +02:00
|
|
|
|
|
|
|
## Futher reading
|
|
|
|
|
2024-06-19 07:19:44 +02:00
|
|
|
- [Always add opers to access list (this is the $oper in
|
|
|
|
my
|
|
|
|
templates)]({% post_url blog/2015-01-10-channels-hostmask-groups-a-basic-howto %})
|
2023-02-22 19:28:38 +01:00
|
|
|
- oops, did I just repeat previous post
|
|
|
|
- [Keep the ops opped]({% post_url blog/2015-04-01-keep-the-ops-opped %})
|
2024-06-19 07:19:44 +02:00
|
|
|
- especially read this if you are at liberachat or wondering why you don't get
|
|
|
|
automatically opped after registering the channel and cycling while being
|
|
|
|
identified!
|
2023-02-22 19:28:38 +01:00
|
|
|
- `/msg NickServ help`
|
|
|
|
- `/msg NickServ help set`
|
|
|
|
- especially worth taking a look at: `emailmemos` & `enforce`
|
|
|
|
- `/msg ChanServ help`
|
|
|
|
- `/msg ChanServ help set`
|
2024-06-19 07:19:44 +02:00
|
|
|
- especially worth taking a look at: `guard`, `keeptopic`, `verbose`
|
2023-02-22 19:28:38 +01:00
|
|
|
- `/msg ChanServ help flags`
|
|
|
|
- what flags are available, what they do and managing them.
|
|
|
|
- `/msg ChanServ help template`
|
|
|
|
- official documentation for using templates.
|
|
|
|
- `/msg GroupServ help`
|
|
|
|
- `/msg GroupServ help flags`
|
|
|
|
- `/msg GroupServ help set`
|