Since day 1 of DigitalIRC we have had a webchat. It was one of the reasons this network was actually started.
\nOur current webchat is TheLounge and has been working quite well for DigitalIRC for several years.\nIt has one major downside for us though. We have to host it on our servers.
\nThat is why with in UnrealIRCd 6.0.5 adding websocket support in 2022, we've been working on adding websockets as an available method to connect to the IRC network.
\nToday we are announcing two websocket based clients which are hosted on DigitalIRC domains but are fully static websites hosted on our CDN edge. KiwiIRC and Gamja
\nKiwiIRC is a returning client, we used an older version of it without websockets before the move to TheLounge, and Gamja is a simple IRC client in the browser which and is the webchat client of choice for one of the largest IRC networks.
\nAs these two new webchats are rolled out we must also announce that Gamja will as of January 2025 become the new default webchat with TheLounge webchat (moving to lounge.webchat.digitalirc.org) eventually being retired by July 2025.
\nIf you use TheLounge webchat embedded into a website, your embedded url options WILL CHANGE.
\nOn the good side you can now host your own webchat and set any custom options you want!
\nFor Gamja please see this page for a list of URL parameters you can set.\nFor KiwiIRC please see this page for a list of URL parameters you can set.
\nSo we've been trialing websockets connecting to IRC for nearly 2 years and we now consider them to be good enough for GA. If you want to connect to the IRC via a websocket a round robin address has been setup.
\nTo connect use wss://irc-websocket.digitalirc.org:8433. Currently there are 3 servers configured to offer websocket connections, and we only offer secure websockets.
I don’t think it needs to be said but security is important to users of the DigitalIRC Network. In line with our continued mission to provide the best experience possible for users of the network we are introducing Security Group as a new extended ban type.
\nSecurity Groups are a new feature of the IRCd we use for the network which allows users to be put into groups based on various categories.
\nThe Groups currently defined are
\n| Group | \nDescription | \n
|---|---|
| known-users | \nIdentified with services and has been connected for a reasonable length of time | \n
| unknown-users | \nUsers who are not connected to webchat, are not identified with services, and are new to the network. | \n
| unidentified | \nUsers who are not identified to services. | \n
| webchat | \nUsers connected via an approved webchat (Our own, kiwiirc, etc) and are not identified with services. | \n
| webchat-identified | \nUsers connected via an approved webchat (Our own, kiwiirc, etc) and are identified with services. | \n
| webchat-reputation | \nUsers connected via an approved webchat (Our own, kiwiirc, etc) and are not identified with services, but have been connected for a while (i.e. not new connections to the network). | \n
| webchat-all | \nAll users connected via an approved webchat. | \n
| unknown-reputation-users | \nUsers who are not connected to webchat and are not identified with services but have been connected for a reasonable length of time. | \n
More info about how reputation works
\nWe also use the Security Groups to reduce flooding by restricting the number of actions a user may take depending on which group they fall into.
\nAs you can see from the table above if you want to ban webchat users you can now easily do it. Just do /mode +b ~G:webchat-all and that’s it, all webchat users will now be banned from the channel.
Users may fall into multiple groups, and you can even add a NOT operator to any ban. For example /mode +b ~G:!webchat-all would match all users that do not fall into the webchat-all group.
As always if you have any feedback for groups you want feel free to ask in #irc-help with your usecase
Webchat, to many it’s the only way they interact with the IRC network and chat with their friends. This is because for most it’s the easiest way for them to access the network, no installs, no configs, it just works.
\nFrom a recent query we got in #help we realised that there was no offical documentation for how to deeplink to a channel with the DigitalIRC Webchat or our backup KiwiIRC Webchat.
\nWhen we talk about deeplinking we are talking about a way to directly link so the webchat will connect to your channel rather than the default, as well as specifying a different nickname. These can also be embedded into a website via an iframe to give a seamless experience to the user.
\nThe DigitalIRC Webchat is our self hosted webchat which is currently based on TheLounge. Previously it’s been based on QwebIRC, and then a self-hosted KiwiIRC instance.
\nTo change the default channel to join on connect all you need to do is add ?join=CHANNEL where CHANNEL is the channel you with to join.
\n\nhttps://webchat.digitalirc.org/?join=test
\n
Please note to not put a # in url as it will cause the webchat to ignore the channel name.
\nIf you want to change the nickname that people join with you can use ?nick=NICKNAME where NICKNAME is the nick to use rather than the default.
\n\nhttps://webchat.digitalirc.org/?nick=JohnSmith
\n
These two options can be combined as well to have a nickname and channel pre-filled when users view the webchat.
\n\n\nhttps://webchat.digitalirc.org/?join=test&nick=JohnSmith
\n
The KiwiIRC is an external IRC Webchat platform we do not run any of the servers it is hosted on, but it does have a webirc password configured to allow it to connect to the DigitalIRC network.
\nTo change the default channel to join on connect all you need to do is add #CHANNEL to the END of the URL, where CHANNEL is the channel you with to join.
\n\nhttps://kiwiirc.com/client?settings=0f3e994c84290c080344dd64496537e7#test
\n
If you want to change the nickname that people join with you can use ?nick=NICKNAME where NICKNAME is the nick to use rather than the default.
\n\nhttps://kiwiirc.com/client?settings=0f3e994c84290c080344dd64496537e7&nick=Cheesus
\n
These two options can be combined as well to have a nickname and channel pre-filled when users view the webchat.
\n\n\n", "date_published": "2020-10-07T00:00:00Z" } , { "id": "https://digitalirc.org/blog/channel-permissions/", "url": "https://digitalirc.org/blog/channel-permissions/", "title": "Channel permissions", "content_html": "https://kiwiirc.com/client?settings=0f3e994c84290c080344dd64496537e7&nick=Cheesus#test
\n
A channel on the network can have six different kinds of users. You might think of them as levels of permission and access.
\nThey are, in increasing amount of capabilities:
\nRegular users and voiced have no power in the channel, though voiced users can talk if the channel has been muted. All levels above voiced have some control over the moderation of the channel.
\nFounders have the highest level of access in the channel; with the ability to change any permissions, channel successor, etc. On DigitalIRC a channel may have up to 5 user accounts with the founder level permission but be warned founders can remove other founders so make sure you trust the people you give it to.\nIf for some reason you need more than 5 users to have founder permission you can assign a groupserv group founder permissions as well.
\nThe table below shows some of the channel permissions available to each level:
\n| Capabilities | \nVOP | \nHOP | \nOP | \nSOP | \nFounder/Owner | \n
|---|---|---|---|---|---|
| Can speak when channel is moderated (+m) | \nYes | \nYes | \nYes | \nYes | \nYes | \n
| Can change channel TOPIC | \n\n | Yes | \nYes | \nYes | \nYes | \n
| Can change Channel Modes | \n\n | Yes | \nYes | \nYes | \nYes | \n
| Can Kick/Ban users with lower status than themselves | \n\n | Yes | \nYes | \nYes | \nYes | \n
| Can Voice/Devoice users (+v) | \n\n | Yes | \nYes | \nYes | \nYes | \n
| Can Half-OP/DeHalf-OP users (+h) | \n\n | \n | Yes | \nYes | \nYes | \n
| Can use Botserv (/bs) commands | \n\n | \n | Yes | \nYes | \nYes | \n
| Can OP/DeOP users (+o) | \n\n | \n | \n | Yes | \nYes | \n
| Can view/add/remove AKICKs | \n\n | \n | \n | Yes | \nYes | \n
| Can SuperOP/DeSuperOP users (+a) | \n\n | \n | \n | \n | Yes | \n
| Can add successor | \n\n | \n | \n | \n | Yes | \n
| Can add other founders | \n\n | \n | \n | \n | Yes | \n
After more than a few people asking we are now adding access to the network via TOR. Currently we will still maintain the ban we have on accessing us on our public interfaces from tor or an open proxy.
\nOur hidden service address is ircnetdbe6ohrrrekzbf33v7crjink7hsafrtzyid6rof4jianus4byd.onion on which we will only listen on with ssl on port 6697. More information about tor can be found on the TOR Project website and we highly recommend the TOR Browser Bundle.
\nUpdate 2018-11-13: Updated hidden service address
\nUpdate 2020-10-01: Tor V3 address
\n", "date_published": "2015-04-08T00:00:00Z" } , { "id": "https://digitalirc.org/blog/extended-bans/", "url": "https://digitalirc.org/blog/extended-bans/", "title": "Extended bans", "content_html": "You can use extended bans to set up an alternative kind of ban that will give you more options, like silencing users.
\nWhen you silence a user, you allow the person to stay in the channel, but block the person’s ability to participate in the discussion or change nicks. It’s an online equivalent of a short timeout, where the person has to sit quietly for several minutes before rejoining discussion.
\nTo silence a user manually, you’d type:
\n/mode #YourChannel +bb ~q:nick!ident@user.host ~n:nick!ident@user.host
That command sets two bans, which is why the host information is listed twice. The first one (~q:nick!ident@user.host) prevents the user from participating in the discussion (unless the user is +v or higher). The ~q stands for quiet. The second one (~n: nick!ident user.host) prevents the user from changing nicks. The ~n stands for nick.
\nIn #YourChannel, bans are normally set by the user’s host, so an example ban would look like this:
\n/mode #YourChannel +bb ~n:*!*@protectedhost-1234578.hsd1.va.comcast.net ~q:*!*@protectedhost-1234578.hsd1.va.comcast.net
That example bans anyone (with any nick or ident) with the hostmask protectedhost-12345678.hsd1.va.comcast.net.
\nIf you silence a user manually, you have to remove the ban manually as well. Since you set the ban with +b, you will remove it by using the same command, but with -b. So to remove the ban, you would type:
\n/mode #YourChannel -bb ~q:nick!ident@user.host ~n:nick!ident@user.host
Everything is the same. You’re just removing the ban. Here’s the way to remove the example ban from above:
\n/mode #YourChannel -bb ~n:*!*@protectedhost-1234578.hsd1.va.comcast.net ~q:*!*@protectedhost-1234578.hsd1.va.comcast.net
There are two other kinds of extended bans:
\nYou are unlikely to need either of these bans, but for the sake of thoroughness here is how they work.
\nTo set an extended channel ban, you’d type:
\n/mode #YourChannel +b ~c:#channel
That ban would prevent anyone in #channel from joining #YourChannel.
\nLet’s pretend there’s a channel called #YourChannelHaters. We might decide that we do not want anyone from #YourChannelHaters to join #YourChannel. We could use this extended ban to prevent them from joining #YourChannel:
\n/mode #YourChannel +b ~c:#YourChannelHaters
You remove this kind of ban by switching to -b, so I could remove the ban on folks from #YourChannelHaters like this:
\n/mode #YourChannel -b ~c:#YourChannelHaters
To set an extended ban based on a user’s real name, you’d type:
\n/mode #YourChannel +b ~r:*real_name*
The * character works as a wildcard, just as it does in other bans. Use the underscore character ( _ ) to represent spaces in the user’s real name. The underscore is also interpreted as an actual underscore character. In other words, the ban above would block someone using either "real name" (with a space) or "real_name" (with an underscore).
\nHere’s an example:
\n/mode #YourChannel +b ~r:*Jane_Doe*
That ban would prevent anyone who was using the real name "Jane Doe" or "Jane_Doe" from joining #YourChannel. Because of the * wildcard, someone with a real name like "Jane Doe rules" or "Jane_Doe_rules" would also be banned.
\nYou remove this kind of ban by switching to -b, so I could remove the ban on "Jane Doe " like this:
\n/mode #YourChannel -b ~r:*Jane_Doe*
We have added a wiki to DigitalIRC, this allows users, channel owners and staff to create pages about channel, services and other interesting titbits of information about DigitalIRC or IRC in general.
\nThe wiki is available at www.digitalirc.org/wiki/
\n", "date_published": "2012-11-09T00:00:00Z" } , { "id": "https://digitalirc.org/blog/how-to-get-a-vhost/", "url": "https://digitalirc.org/blog/how-to-get-a-vhost/", "title": "How to get a vhost", "content_html": "A vhost (a.k.a. vanity host or virtual hosts) is a custom part after the @ in your user mask on IRC. For example:
\n\n\nMrRandom!MrRandom@MrRandom.may.explode.on.impact
\n
My vhost when I use the nickname MrRandom is MrRandom.my.explode.on.impact.
\nWith our recent move to atheme as our services package, all registered accounts have the default vhost assigned to them when they register yournickname.users.digitalirc.org but with atheme’s hostserv (the service we use to manage vhosts) it allows use to now have an offer list, this list contains vhosts which any user can assign to them selves without any operator intervention.
\nThe list of vhosts on the offer list is:
\n\n\n$account.may.explode.on.impact\n$account.users.digitalirc.org\n$account.loves.porn
\n
N.B. Some vhosts are hidden unless you are part of the group it was for. To see the full list do
\n\n\n/hs offerlist
\n
N.B. $account will be replaced by your nickname on IRC, for example MrRandom would become MrRandom.may.explode.on.impact
\nTo get a vhost off the offers list (when identified to services) do:
\n\n\n/msg hostserv take [offer vhost you want]
\n
remember to include the $account part since that is important
\nWhat if I want a custom vhost/a vhost that contains a domain name.
\nFor all domain names that aren’t on the offers list submit a hostserv request which will be reviewed by the Server Operators. The decisions of the operators are final and absolute.
\nAll vhosts applied for are subject to the network rules on profanity and common sense guidelines
\nIf you think your vhost meets these simple requirements simply do:
\n\n\n/msg hostserv request [vhost you want]
\n
If you want a vhost that resolves to an actual domain name, the operator reviewing your request will message you to provide proof that you do own the domain name.
\n", "date_published": "2012-10-28T00:00:00Z" } , { "id": "https://digitalirc.org/blog/why-is-my-bot-banned/", "url": "https://digitalirc.org/blog/why-is-my-bot-banned/", "title": "Why is my bot banned", "content_html": "So your bot can’t connect and it’s saying it has been banned from the network. This has happened because your bot was either:
\nIf your bot didn’t run ident then your entire host has been banned from the network. If you bot did respond to ident then only it was banned so you can still connect to the server just not with the account the bot was on.
\nTo appeal the ban contact an operator in #help or email opers (@) digitalirc (dot) org
\n", "date_published": "2012-09-29T00:00:00Z" } , { "id": "https://digitalirc.org/blog/can-i-link-two-channels/", "url": "https://digitalirc.org/blog/can-i-link-two-channels/", "title": "Can I link two channels?", "content_html": "One question that is routinely asked in #help is how a channel owner can forward users from one channel to another. They usually ask this because they have changed channel names, and there is no other method available to regular users (as opposed to those with access to the IRCd configuration files); however it is also useful if the group that the channel is used by is hosting an event, and to keep the main channel manageable, want to limit it to only X amount of people, and have users that join after that go to an overfill channel.
\nIn any case, linking two channels together is very easy, as it only involves setting two channel modes – the first sets a limit of X people that can be in the channel, and the second sets the channel to send people to after X people have joined the main channel. Also, you are not limited in the number of channels that can be linked together, with the exception that a channel can only forward users to one channel. #Chan1 can forward to #chan2, which can forward to #chan3, etc.
\n\n\nl = Channel may hold at most the specified number of users (This mode is a lowercase L, not a capital i)\nL = Channel link (If +l is full, the next user will auto-join ) [q]
\n
So if I wanted to forward my channel #Inara to #Adria, I would do the following:
\n\n\n/mode #Inara +lL 1 #Adria
\n
If I wanted to always have the channel set like that, so that nobody could change it, I would use chanserv’s mlock option, and do:
\n\n\n/msg chanserv set #Inara mlock +lL 1 #Adria
\n
If you are linking an old channel to a new one (i.e. you’ve moved channels), the number must be 1, and there must be someone in the channel for it to work (note: botserv bots do not count. It can be a bot that you run though). If you have linked a primary channel to an overfill one, the number can be anything equal to or greater than 1.
\nNOTE: Linked channels do not share the same permissions, you will need to add people to the aop/sop/hop/vop lists in each channel.
\nShould you have any questions about linking channels, feel free to leave a comment here, or to join #help and ask in there.
\n", "date_published": "2012-09-09T00:00:00Z" } , { "id": "https://digitalirc.org/blog/what-is-a-vhost/", "url": "https://digitalirc.org/blog/what-is-a-vhost/", "title": "What is a vHost and how to get one", "content_html": "A host is the part that comes after the @ when you join a channel on IRC (For example, [you] (webchat@SilentZombies-2C774A64.your.isp.net) ) has joined #empornium). A vHost (aka virtual host) is a feature on Empornium irc network, that allows you to be identified with a custom host, hiding your real ISP, making some silly joke, or even ban evasion (requesting one for ban evasion will get you banned from the entire network, not just a channel).
\nBy default you host is hidden by a standard vhost which everyone who registers gets (e.g. [you].users.digitalirc.org ), this tutorial is if you want a custom one. For example MrRandom@Ego.sum.penitus.corrupta
\nSo your vhost meets all the rules first you need to be registered with NickServ. Once that is done simply enter:
\n\n\n/hs request your.vhost.here
\n
When it has been approved it will automatically set itself as your host, and each time you subsequently identify each time you connect.
\n", "date_published": "2012-09-02T00:00:00Z" } , { "id": "https://digitalirc.org/blog/using-our-round-robins/", "url": "https://digitalirc.org/blog/using-our-round-robins/", "title": "Are you using our round robins?", "content_html": "As we explain on our Servers page, you often achieve the best connection by connecting to the server geographically closest to you. To do this, you can find the closest server on the map and then connect to servername.digitalirc.org for example, shire.digitalirc.org would be a good choice if you were in Europe.
\nYou can also choose a pool of servers that are near you by using our round robin addresses. The biggest round robin pool is also the most general one (and the one most clients use on their pre-populated server lists): irc.digitalirc.org. That round robin includes all the Digital IRC servers.
\nIf you want to choose a smaller pool, you can use one of these round robins, based on your geographical area:
\nWe also have round robins based on pools of servers with special capabilities. If you need these features, use one of these options:
\nAll Servers support ssl connections on port 6697 and mibbit connections.
\n", "date_published": "2012-09-02T00:00:00Z" } , { "id": "https://digitalirc.org/blog/how-to-group-nicknames/", "url": "https://digitalirc.org/blog/how-to-group-nicknames/", "title": "How to group Nicknames", "content_html": "So you’ve registered your nick, but have more than one computer/device that you join IRC from. You might be wondering “do I need to register a new nick and have people add that nick to access lists as well? Certainly there must be an easier way.”
\nWell luckily for you, there is. You are able to group nicks together so that permissions and other data are shared among accounts. Some of the items that are shared include (but are not limited to): channel ownership, permission levels (owner, halfop, etc.) on channels, group info that was provided when you registered, password, and virtual host. Pretty much anything your single nick has associated with it will be associated with the group of nicks that you have registered.
\nHere’s how to group a nick to one that you already have registered:
\n\n\n/msg nickserv group main_nick password
\n
where main_nick is your primary nick, and password is the password belonging to the primary nick.
\n\n\nExample: I want to group JayneCobb to my primary nick, MalcolmReynolds, and the password for it is S3reni+yV@ll3y (you do use something secure for your passwords, right?). I would type the following as JayneCobb: /msg nickserv group MalcolmReynolds S3reni+yV@ll3y
\n
Look for nickserv to either tell you that you have joined the group of your primay nick or give you an error message, such as “you must wait at least 60 seconds before using the group command again”.
\nAnd just to give you the commands again, they are, in order:
\n\n\n/nick theNewNick\n/msg nickserv group main_nick password
\n
Now what if you want to delink a nick, i.e. remove it from the group, is there some way to do that? Yes there is, you just drop it by switching to the nick, and doing
\n\n\n/msg nickserv drop
\n
Doing that will make nickserv completely drop the nick – it will no longer exist, have any permissions, etc.
\nIs there someway to delink it without dropping, or without it losing the permissions and other information? Not currently, although I suppose it is possible that it could end up in a future version of services, or someone could create a module that could drop a nick and register it using the credentials of the former group and preserving permissions, etc.
\nShould you have any questions about grouping nicks, feel free to leave a comment here, or to join #empornium-help and ask in there.
\nNOTE 1: Before you enter the next command, make sure that you are using the nick you want to add to your\nexisting group. Do NOT be using your main nick. Example: if I wanted to group JayneCobb to my account, I\nwould /nick JayneCobb.\nNOTE 2: If you use a registered nick when the next step if performed, it will first be dropped, then\ngrouped to the main nick. Example: if I try to group JayneCobb (which is registered) to my main nick\nMalcolmReynolds, Services will first drop JayneCobb, then have it join the MalcolmReynolds group. By being\ndropped, any permissions JayneCobb had will be gone.
\n", "date_published": "2012-09-02T00:00:00Z" } , { "id": "https://digitalirc.org/blog/how-to-register-a-nickname/", "url": "https://digitalirc.org/blog/how-to-register-a-nickname/", "title": "How to register a nickname", "content_html": "Registering your nickname on Digital IRC provides a number of benefits. The most notable of these is that registering your nickname prevents other people from using it. Once a user starts using the nickname, they will be asked to ‘identify’ to it with a password. If they fail to do so, their nickname will be changed. This helps to stop people posing as you.
\nOnce you register your nickname, you can be added to the auto voice and op lists in other people’s channels. This enables you to be a permanent staff member in channels. You are also entitled to a vhost once you have been registered.
\nRegistration provides you with many benefits and is completely free.
\nTo register your nickname on Digital IRC, you must first be using it. If you are not currently using it, change to it with the command:
\n\n\n/nick
\n
For example:
\n\n\n/nick CrazyUser
\n
Once you are using the nickname, you may register it in one of two ways. In any client, use the following command:
\n\n\n/ns register
\n
For example:
\n\n\n/ns register supersecretpassword crazyuser@hotmail.com
\n
Following this, you will be not get an e-mail you are done. The e-mail is needed only to recover your password.
\nEach time you connect and start using the registered, you will be told that This nick is owned by someone else. You must ‘identify’ to it using the following command:
\n\n\n/ns identify
\n
For example:
\n\n\n/ns identify supersecretpassword
\n
If you use mIRC, you can load the following script into the Remotes section of your script editor (press alt+R to access this) to identify you automatically. Just replace ‘YOURPASSWORDHERE’ with your actual password:
\non 1:NOTICE:*This nickname is registered and protected*:?: {\n if ($nick == NickServ) {\n ns identify YOURPASSWORDHERE\n }\n}\n\non 1:NOTICE:*This nick is owned by someone else*:?: {\n if ($nick == NickServ) {\n ns identify YOURPASSWORDHERE\n }\n}If you require help, come and see us in [#help on irc.digitalirc.org][1]. Users who have registered with NickServ will automatically get voiced in the channel when they join.
\n[1]: http://www.digitalirc.org/webchat-help/ “IRC Webchat”
\n", "date_published": "2012-06-02T00:00:00Z" } , { "id": "https://digitalirc.org/blog/how-to-add-channel-auto-join/", "url": "https://digitalirc.org/blog/how-to-add-channel-auto-join/", "title": "How to add channels to auto-join", "content_html": "The AJOIN command is a server-side command that keeps track of the channels you join each time you connect to Digital IRC. If you login with your nick and identify with your password, you can join all the same channels automatically. It works no matter what client you use or where you connect from since all the details are kept on the server.
\nNote: that your client may have an option to keep an auto-join locally. Check your documentation for details on using a client-side system if you want to keep your settings on your machine(s). This explanation will focus on the server-side system only.
\nYour nickname has to be registered, and you have to identify before you can use the AJOIN command. Additionally, the channel that you want to join has to be registered. Remember that you can only be in 100 channels, so you can only include 100 channels in your AJOIN list.
\nTo add a channel to the list of those that you join every time you connect to Digital IRC (your AJOIN list), use the following command:
\n\n\n/ns AJOIN ADD #channel
\n
For instance,
\n\n\n/ns AJOIN ADD #topgear
\n
would add the channel #topgear to your AJOIN list.
\nIf the channel you want to add uses a key, you need to include the key when you use the command:
\n\n\n/ns AJOIN ADD #channel key
\n
For instance,
\n\n\n/ns AJOIN ADD #topgear hAmsT3r
\n
would add the channel #topgear with the channel key “hAmsT3r” to your AJOIN list.
\nCan I just add every channel I’m in right now?
\nYes, you can. Join all the channels you want to add, and use the command:
\n\n\n/ns AJOIN ADDALL
\n
The command will also automatically include the keys for any channels to your AJOIN list.
\nTo see a list of all the channels on your AJOIN list, use the command:
\n\n\n/ns AJOIN LIST
\n
Use wild cards with this command to list only the channels on your AJOIN list that match a specific pattern.\nFor instance, the command
\n\n\n/ns AJOIN LIST #top*
\n
would return all the channels on your AJOIN list that begin with “#top” (for instance, #topgear).
\nTo remove a channel from your AJOIN list, use the command
\n\n\n/ns AJOIN DEL #channel
\n
For instance,
\n\n\n/ns AJOIN DEL #topgear
\n
would remove the channel #topgear from your AJOIN list.
\nTo remove all the channels from your AJOIN list, use this command:
\n\n\n/msg NickServ AJOIN CLEAR
\n
The command will delete all the channels from your AJOIN list. When you connect to Digital IRC again, you will not join any channels automatically.
\nIf you are banned from a channel, please be sure to remove it from your AJOIN list, using the AJOIN DEL command above. Keeping a channel you are banned from on your AJOIN list may result in accidentally evading the ban.
\n", "date_published": "2012-06-02T00:00:00Z" } , { "id": "https://digitalirc.org/blog/how-to-make-a-privaterestricted-channel/", "url": "https://digitalirc.org/blog/how-to-make-a-privaterestricted-channel/", "title": "How to make a private/restricted channel", "content_html": "Every channel is able to be private (+p), and/or secret (+s). The two modes are similar, but it is possible for people to find out about a channel that is marked private only (+p). Therefore, if you want a channel nobody will be able to find out about unless they’re told, it is recommended that you mark it as secret and private, +sp. Unless you are in the channel or an IRCop, the server will pretend that the channel doesn’t exist.
\nThere is also channel mode +i, which will let people in only when they have been invited. If the channel is registered with chanserv, those on the access list can /msg chanserv invite #channel, and chanserv (or the botserv bot, if the channel has one) will invite the person into the channel. Standing invites can also be set using channel mode +I, which takes a nick!ident@host mask as a parameter. If the person is not on the access list, and does not have +I set for themselves, they are able to “knock” on the channel by doing /knock #channel optional_message.
\nYou can also set a “key” on the channel using channel mode +k, which takes the key to use as a parameter. If I wanted to set a key on my channel, I would do /mode #serenity +k Kaylee. In order to get in the channel, someone would need to specify the key when they try to join – /join #serenity Kaylee. Alternatively, they can also be invited into the channel and will not need the key.
\nIf the channel is registered, those modes can be mlock’ed, so that they will be reapplied when the channel is recreated (i.e. is empty and someone joins). It is important to note that if the channel is empty, needing a key or an invite is not necessary to join the channel. That is where the next item comes into play.
\nIt is also possible to set a channel to have restricted access. When this option is set, only the people you add to the access list will be able to join. When someone that is not on the list attempts to join, they are kickbanned by chanserv (or the botserv bot, if you have added one) with the reason “You are not permitted to be on this channel”.
\nSince when you set your channel to restricted access you normally don’t want people to know about it, it is recommended to also mlock it +s. To set both the restricted access and mlock, you need to enter the following two commands, replacing #channel with your actual channel:
\n\n\n/msg chanserv set #channel mlock +s\n/msg chanserv set #channel restricted on
\n
Note: If you already have some modes set with mlock, you will need to respecify them when you add +s. So if you have +n (no external messages) set with mlock, you would need to do /msg chanserv set #channel mlock +sptn.
\nShould you have any questions concerning setting your channel to restricted access, feel free to stop in #help and ask.
\n", "date_published": "2012-03-02T00:00:00Z" } ] }