How To Register Public Channel In Freenode
This page has been set up to answer common questions. Information technology'due south non intended to provide a tutorial nigh IRC in general, merely to address the peculiarities of freenode. If yous can't find the reply to your question hither, feel free to inquire united states in #freenode, where staff are voiced, or drop us a line to support at freenode dot net! Thank you.
People on freenode connect from fourth dimension zones all around the globe. To skip discussions of morning versus afternoon in any given time zone, freenode adopted the convention that when a user first joins or becomes active, it's considered morning, and when the user leaves or goes abroad, information technology is evening. This is likewise known as Universal Greeting Time (UGT).
Information technology's still necessary to coordinate on timestamps or specific coming together times, and in this context, fST is a jovial reference to UTC.
Your nick is how people on freenode know y'all. If you register it, y'all'll be able to utilise the same nick over and over. If you don't annals, someone else may finish up registering the nick you want. If y'all register and use the same nick, people will begin to know you by reputation. If they're running IRC software which supports the CAP identify-msg, they'll be able to tell when someone is spoofing your identity.
If a aqueduct is set to mode +r, y'all won't be able to join information technology unless you are registered and identified to NickServ. If you try to bring together, you might exist forwarded to a different channel. If a aqueduct is set to mode +q $~a, you lot won't be able to speak while on that channel unless y'all are registered and identified. Both of these modes are used to reduce channel harassment and abuse.
For more information on how to prepare upwards a registered nick, take a look hither.
Please follow these steps to fix your nick and configure your client. Bank check off each step to make sure information technology'due south been washed:
-
Select a permanent, primary nickname. If the nickname you lot want is registered only has expired, just enquire a staffer and in well-nigh cases, we will be happy to drop it for y'all.
Please avert using the name of a customs project or trademarked entity, to avert conflicts. Write down your countersign and be sure to keep the sail of paper in a safe identify.
-
Register your IRC nick:
/msg NickServ Annals password [email protected]Replace password with a secure, unguessable password that you lot keep secret.
-
The e-mail address that you lot select will not be given out by staff, and is mainly used to allow us to help you recover the account in the event that you lot forget your password. For this reason, you are required to use a real, non-disposable, electronic mail accost. Upon registering, you will receive an electronic mail with a verification command that yous will demand to run to complete the registration procedure. Failure to verify the account will cause it to be automatically dropped subsequently about 24 hours.
-
To continue your email accost private, rather than displaying it publicly, mark it every bit subconscious (which is washed by default for new accounts):
/msg NickServ SET HIDEMAIL ON -
It's useful, simply not required, to have an alternating nick grouped to your account. For example, if your main nick is foo:
/nick foo_and then identify to your primary account:
/msg NickServ IDENTIFY foo passwordand finally, group the new nick to your account
/msg NickServ Group -
We prefer y'all to employ just i account, and group nicks to it as described to a higher place, rather than registering for multiple accounts. Grouping nicks in this way gives you the benefit of having all your nicks covered by the aforementioned cloak, should you choose to wear a cloak.
The exception to this is where yous might want to run a bot. You should register a divide account for your bot.
-
Configure your client to identify itself to NickServ automatically whenever information technology connects to freenode so that information technology'due south less likely you'll connect to the network without being identified to NickServ. The easiest arroyo is to specify your NickServ password every bit a server password.
If your client supports server password, please ready this up as accountname:password . Make sure to include the colon. This volition allow yous to identify to your services account on connect, regardless of the nickname you are using when y'all connect. For example:
/connect chat.freenode.cyberspace 6667 mquin:uwhY8wgzWw22-zXs.M39p
If your client supports SASL, that is best. Otherwise, just plug your NickServ password into your client equally a server password. To make this piece of work when connecting from a different nick than the i yous've got registered, use nick:password . You lot'll be identified to NickServ automatically when you connect.
In some cases, information technology's more user-friendly to configure your client to ship this command to reach the same consequence:
/msg NickServ IDENTIFY account countersignWe recommend you read and follow the steps of the canonical nickname setup to brand sure your customer identifies reliably to NickServ.
If your client supports CAP identify-msg, yous tin configure it to let you know when someone speaking on channel or via /msg is not identified to services. A script to take reward of CAP identify-msg is currently bachelor for irssi. It was originally written for the CAPAB command in dancer (hyperion), merely has been modified to support the more than versatile CAP control in charybdis (ircd-seven). If you want other people using this feature to know that you're you, have your client place to NickServ when y'all connect to the network. You lot should besides follow the canonical setup steps for your IRC nickname.
Now, newer capabilities exist to enable clients and scripts to manage identity tracking: account notify, extended-join, and format parameters to WHO. If yous are willing to share a script that demonstrates these features for a pop customer (or clients), let u.s. know.
At staffer discretion, we consider IRC nicks expired after they have not been used for ten weeks plus one boosted week per total yr of registration, normally up to a maximum of five boosted weeks. Nicks which are at least two weeks old and which were last used less than 2 hours after their cosmos are also considered to be expired. These time limits do not use to held nicks, which are allocated and dropped as needed. If the nick you want is someone'southward NickServ business relationship name, information technology is considered expired simply when the business relationship itself is expired.
Nicknames that are not confirmed past a valid e-mail address volition exist automatically dropped after 24 hours.
We occasionally prune the Services databases, removing nicknames and channels that have not been in apply for some time. Delight ensure yous Place to avoid thwarting as identifying is the only way we accept of telling if your nickname is even so in use.
Nosotros know this only as a outcome of your identifying to NickServ when you connect to the network. If you lot don't identify, we'll have no way to know that your nick is in apply, and it will eventually be dropped. You lot should also follow the canonical setup steps for your IRC nickname. You lot tin run into the last time someone identified to NickServ for a nick with:
/msg NickServ INFO nickThe Final seen: field tells you the last time someone used the nick while identified.
To go on your registered nick, you must go on to use it. If yous do non identify to your nick, it may eventually get expired. In one case it becomes expired, someone tin can ask to accept information technology dropped. When a nick has been dropped and picked up past another user, we are not able to take information technology back from them. That would be unfair to the user who picked it up. In other cases, someone could simply exist using the nick while unidentified. Y'all can force them to change their nick with:
/msg NickServ RELEASE yournick yourpasswordYous may need to run the in a higher place command a second time if yous get a message saying the nick is temporarily unavailable. You lot can besides set up enforce on your nick to accept NickServ forcefulness users to place to the business relationship within 30 seconds in lodge to continue to use it:
/msg NickServ SET ENFORCE ONAt that place is an official freenode webchat running at webchat.freenode.cyberspace, you are welcome to employ this. We run Qwebirc, an open source web IRC customer originally designed by and for the QuakeNet IRC network.
In that location are many other such facilities available. Simply consult Yahoo or Google for a list and endeavor one of the pages on the list. Obviously freenode can not recommend a particular webchat facility bar our own, and we might have to limit access if they're driveling, but we're happy to have y'all connect in this way.
The '~', or lack thereof, is in fact in the username field. Usernames will typically display a tilde ('~') at the beginning of the username if it is provided past the IRC client, instead of the identd or authd service. Usually ident or auth daemons are run past beat services, gateways, or other situations where multiple users may share the aforementioned host.
Try to avoid unnecessarily-broad bans. As the catalysts page implies, we don't support unnecessary employ of bans. When banning, target the ban as narrowly every bit possible. With the tilde structure, banning someone with the user proper name "foo" without regard to whether they friction match ident is frequently done in this way:
/mode #aqueduct +b nickmask!*foo@hostmaskwhich bans both foo and ~foo. Unfortunately, it also bans usernames such equally:
foofoo moofoo goofoo anythingfooInstead, ban just 'foo' past using the following:
/mode #channel +b nickmask!~foo@hostmaskIf identd or authd is in use, use:
/mode #channel +b nickmask!foo@hostmaskCheck the Gelhausen site for a current list. To find channels about a specific topic you lot can also utilize our "alis" service:
/msg Alis Help ListingNosotros consider non-principal IRC channels (those which start with "##") to be expired after they have not been used for 60 days. Staff volition determine this by verifying that the founder has not been present in the channel for that duration of fourth dimension. We might also idle in the channel to confirm that information technology really is non beingness used.
For agile channels where the founder might take simply disappeared, staff may make up one's mind to accept the regular users of the aqueduct vote who the new channel founder should be.
Chief channels, namely those which start with a single "#", can but exist dropped if a valid Grouping Registration is completed. Main channels are not dropped due to founder nick drops or after a long period of time without use.
We put information on the network in a diversity of places. Your all-time ongoing source is this website; information technology provides reference information on the network, its philosophy, the software it uses, etc. In addition, staff send WALLOPS messages with fourth dimension-sensitive status information (besides every bit a variety of general comments and announcements). To receive these letters, on most clients, you can use:
/umode +westor
/mode yournick +wFor best results, place the command in your client's startup script.
In addition to WALLOPS we make announcements via our blog, and twitter. You tin can also connect with us on Google+ .
Finally, we send information we judge to take global significance to our users via global notices. You don't generally accept to exercise anything to run into these, though they may appear on a different window of your client (along with the WALLOPS messages).
Nearly of those letters are sent via WALLOPS, an IRC facility for displaying letters from server operators. On freenode, WALLOPS letters may contain non-critical comments and announcements from staff, as well every bit detailed server assistants information. If you lot don't similar the number of letters or the letters seem too lilliputian or detailed, you can plow them off by turning off user mode "w". On most clients this can be achieved via:
/umode -wor
/fashion yournick -westFor best results, identify the command in your customer's startup script.
We also transport data with global significance to our users via global notices. These notices are a bit more than difficult to plow off; you can ordinarily tell your customer to ignore notices from specific staff members, notices from all staffers or all notices. Information technology'south non recommended. But on about clients, it works something similar this:
/ignore *!*@freenode/staff/* DiscoverCTCP VERSION is a public IRC customer interface which you tin turn on or off or fifty-fifty spoof. We've started to request version data using that interface when users connect to freenode, so that we can help users with customer-related issues, rail down calumniating bots and deny network access from quondam, insecure releases of client software, as well equally analyze client-use statistics to help us meliorate back up our users' needs. Information technology helps us as administrators for yous to leave CTCP VERSION available and un-spoofed, but yous should upgrade your client oftentimes to reduce your exposure to attacks.
For privacy purposes, staff may publish that version information in statistical grade, aggregated with that of other users. Nosotros'll be conscientious to avoid using it in ways which unnecessarily disrupt your use of the network.
Sometimes freenode has to bargain with infestations of spam bots. These bots oft join big channels to become lists of people to spam via private bulletin. We're working on long-term solutions to the problem. In the concurrently, your best bet is to register your IRC nickname and exercise the standard setup, and so set up your user style to +R to filter out any private letters sent to yous by unregistered users. Depending on which client you're running, one of these commands will prepare that user mode:
/umode +R /way yournick +R /quote MODE yournick +R /raw MODE yournick +RIf you run a support channel, please consider using something similar:
/mode #channel +rf #channel-unregisteredThis volition forward unregistered users to a split up channel on join. You can let those users know nigh registration options, but try to provide them support on the 'unregistered' channel, as well — information technology'due south a style to help keep spammers from taking away support options from our unregistered users! Annotation that you will accept to be +o in #channel-unregistered, or that channel must be +F to set the forward.
Your business relationship name and password must exist sent to NickServ and verified, and then NickServ must tell the servers about your cloak. This process may take a lilliputian time, depending on how heavily services is loaded and the corporeality of lag betwixt your server and services.
Some clients ship your identification to NickServ and, without waiting, outset to bring together channels. This may lead to showing your uncloaked host when you join the aqueduct, followed shortly by a quit and re-join as your cloak is applied.
To preclude this, you lot may need to do one of the following (roughly in order of preference):
- Authenticate using SASL.
SASL is a method of identifying during your connectedness, before anything else happens. This is the best fashion to ensure you lot are cloaked immediately. A collection of scripts for mutual clients and instructions for setting upward SASL tin be found here. - Look to join channels until after the server notifies y'all that it has set your hidden host. This notification is done with a 396 numeric that looks like this: 396 YourNick unaffiliated/youraccount :is at present your subconscious host (gear up by services.) Scripts to exercise this for X-Chat and mirc were kindly contributed by our users. You lot won't receive this numeric if your business relationship or connection (for gateways) is not cloaked.
- Add a fixed corporeality of wait time before joining channels.
This can be washed on Ten-Chat with set irc_join_delay, or on irssi by adding wait time to the autosendcmd for the network. - Don't auto-join channels; do information technology manually.
freenode supports SSL, for client and server connections. Users connecting via SSL will get user style +Z to denote this. More information about connecting via SSL is on the IRC servers page.
Client SSL certificates are also supported, and may exist used for services identification. More data near CertFP is on the CertFP folio.
There are a few things that might be preventing you from joining a channel. The outset thing you should bank check is whether you are identified to NickServ. You can identify to NickServ with:
/msg NickServ IDENTIFY YourNick YourPasswordCertain channels have channel mode +r set, which prevents unidentified users from joining. You can check what aqueduct modes are enabled on a channel with:
/manner #channelThe next thing you should check is whether or not you lot are banned from the channel. You tin view the ban list with:
/mode #channel +bRecollect, you lot may exist unintentionally affected by a large ban that was fix, so pay particular attending to bans that include wildcards (* and ?). Also, proceed in mind that if you are cloaked, a ban prepare against your IP address will even so prevent you from joining. Finally, do not forget nigh extbans. A ban confronting $~a will work just like channel mode +r, and might not exist initially obvious. An explanation virtually bans (including extbans) is available hither. If you lot practice find a ban prepare against you and you feel it is a fault, you should contact the channel operators to discuss having it removed.
If neither of these methods piece of work, you will desire to check what other channel modes are enabled for the channel. modes such as +i, +k, and several others might be preventing y'all from joining.
If you are still unable to figure out why you lot tin can't bring together a certain channel, experience gratuitous to ask in #freenode.
freenode tries to allow channels to run and manage themselves. As a result, channel operators are generally free to ban/quiet users for any reason they come across fit. If yous wish to discuss your ban/quiet, you volition need to contact the channel operators. A list of operators can be plant with
/msg ChanServ ACCESS #channel LISTOperators volition have the +o flag. One of these operators will have to unban/unquiet you, freenode staff will not intervene in most cases.
There are two common reasons for being unable to talk in a aqueduct. The first is that yous might exist quieted. You tin view the quiet listing for a channel with
/mode #aqueduct +qIf you detect a quiet set against you lot and you feel it is a mistake, you should contact the aqueduct operators to discuss having it removed.
The 2d common reason for being unable to talk in a aqueduct is that it has aqueduct mode +m enabled. This mode prevents anyone who is not voiced from talking (if channel mode +z is likewise enabled, you will be able to talk, but only operators will meet your messages).
If you lot are identified to your account, you tin can alter your countersign yourself. To change the countersign, enter the following command:
/msg NickServ SET Password mynewpasswordMake certain that you are using SET Password instead of SETPASS. If y'all accept forgotten your erstwhile password and are unable to identify, encounter below for data on how to send a password reset electronic mail.
If you forget your password, only still have access to the email account that is associated with your nick, you tin can have a password reset email sent. Showtime, please await at
/msg NickServ INFO nicknameto verify that you have the correct account. If the registration fourth dimension, last address, and other information looks correct, then use
/msg NickServ SENDPASS nicknameAn email with a single-use reset token volition exist sent. Depending on mail server configurations, it may make it immediately, or only afterward some filibuster. If you lot don't encounter information technology, remember to check your junk/spam folders.
If you practice not call back what nick you lot registered, just ask a staff member or in #freenode for assist. Staffers can send a password reset based on your e-mail address (without knowing the nick), or help you find what nick you lot registered.
freenode runs several services, one of which is MemoServ. Y'all tin send a message to a user via MemoServ with:
/msg MemoServ Ship nhandler I read the FAQ and learned about MemoServ. Thank you!In this example, nhandler will be notified when he comes online nigh the message. If he has notifications enabled, he will as well be notified via email. You can enable email notifications with:
/msg NickServ SET EMAILMEMOS ONY'all can prevent yourself from receiving letters via MemoServ with:
/msg NickServ Set NOMEMO ONBeginning, bank check if you lot have enabled Guard by looking at the flags line in
/msg ChanServ INFO #channelIf you see GUARD listed as a flag, you can crusade ChanServ to part by turning off Guard:
/msg ChanServ Ready #channel Guard offIf ChanServ nevertheless won't leave, and y'all are the only other person in the aqueduct, you are seeing ChanServ'south "inhabit" beliefs. Some clients role and rejoin a aqueduct when they are its only occupant, attempting to gain ops. This doesn't work on a network that has services, similar freenode, and causes the customer to rapidly bring together and part the aqueduct.
To preclude this behavior, ChanServ remains in the channel until another person joins. This behavior cannot be disabled. If it is bothersome, you can momentarily join the aqueduct on a 2nd connexion. This volition crusade ChanServ to part. If the aqueduct empties and is recreated, the inhabit behavior will be triggered again.
Google App Engine, Opera Turbo, and like services are basically open proxies; they allow anyone to connect from any of a big number of IP addresses. Open up proxies are blocked considering they are often used equally gateways to the network for disruptive beliefs that is hard to stop. There is nothing to uniquely identify a proxied user. For VPNs and similar anonymizing services we can (and do) mitigate this past requiring SASL. This allows a user to voluntarily provide a unique identifier that can be used to mitigate abuse if necessary. Webchat does not support SASL, so we have to block services like App Engine and Turbo.
All staff currently connected to the network will be voiced in #freenode. Go along in listen that all network staff are volunteers and yous may sometimes have to wait for a staffer to go active. Yous can also outcome the command
/stats pfrom within your IRC customer. Certain clients, such have BitchX, have bugs which make information technology harder to use the control; in those cases you may have to type something like /quote STATS p. You'll be provided a current list of on-call freenode staffers. Feel costless to message one or more staffers as necessary until you lot find someone who can help you. Not all freenode staffers are listed; please use this listing as your indication of current availability.
You can enquire for an unaffiliated cloak in #freenode. This is our standard cloak and normally shows unaffiliated/youraccountname . You lot will need a registered nickserv account. Remember to verify your email address. Some of our registered groups offer their own cloaks for their projects. To obtain one of these, yous need to find the group contact for the group you lot are interested in, and ask them to arrange the cloak for you lot.
We generally offer only one cloak per person, and a cloak is practical to a nickserv business relationship. If you want a cloak for your bot, please create a separate business relationship for it before request. Unaffiliated bot cloaks look similar unaffiliated/youraccountname/bot/botname .
Every bit always, please find skilful behaviour and adhere to network policies whilst wearing cloaks. Nosotros reserve the right to reject to cloak accounts, and to remove cloaks from accounts if necessary.
Lastly, note that a cloak does not guarantee that your IP accost remains hidden. If this is very important to you, we'd suggest that you wait at the Tor hidden service.
Groups with an approved group registration on file can request cloaks for their participants. During the grouping registration process, we'll piece of work out an appropriate cloaking prefix to place your group. Your group contact will be responsible for contacting us, every bit needed, to designate the IRC nicknames of participants who are eligible to accept your project cloaks, every bit well equally the specifics of the cloaks.
Until GMS complements services, this process will remain a more often than not-manual one, so please don't hesitate to ping a staffer if you don't receive a response within a couple of weeks or and then.
Grouping contacts represent your group to freenode staff. Group contacts can request cloaks for grouping members or project participants. They can request changes in the channel founder or access list for any channel reserved to your group.
Grouping contacts are also invited to sit down on the Group Advisory Lath, or GAB as we refer to it, which has been introduced to permit the projects who use our services to have a voice in shaping the hereafter of freenode and which direction nosotros take in future and how we can all-time help create environments that promote cross projection collaboration, sharing of resources and bringing people together, on and offline.
Our group registration folio provides basic reference information for the registration process. Group registration indicates official participation by your group or organisation in freenode, so discuss it with your board or leadership and have them make an official decision before proceeding.
Then, have a lath representative, a managing director or a fellow member of your core group, as appropriate, make full out a group contact grade, selecting "I am: a primary contact person" and providing his or her own contact information. More than 1 chief contact form can be submitted, every bit appropriate. You tin can also accept one or more than agile group contacts fill out the grouping contact course, selecting "I am: a contact person being alternating."
A main contact has the authority to represent your group, project or organisation and to verify that your group has approved its registration with freenode. For a legal entity, a principal contact can be an upper-level managing director or a member of your board. For an informal group, a primary contact should be your project lead or a member of the cadre commission that makes decisions for your group.
An alternate contact, where specified, is an individual who does not accept articulate authority to stand for your group and must be alternate by at to the lowest degree one chief contact.
Grouping cloak components appear in left-major order and are separated past slashes ('/'). They are:
-
Group or project name: Nosotros'll provide you with a group proper name and with optional project names. For each cloak you request, y'all should select a name from the set we've reserved for y'all.
-
Cloak hierarchy: You can select "inside" tokens to indicate the user's function in your project or group. These might include words like developer, staffer, support, member or fifty-fifty donor. You can create a hierarchy of roles if you wish. "Inside" tokens and any cloak hierarchy are entirely your choice, and some projects omit them.
Please utilize the token "bot" to indicate automated utility clients.
-
Unique identifier:The last token of a grouping cloak is a unique identifier for the user to whom the cloak belongs. Examples: the user's name, their forum proper noun, their committer id or account id on your server, or their main IRC nick. Whatever you choose must be unique within the context of your projection or grouping.
Dual cloaks, where a menstruum-separated label to the token bearing the name of some other project is inserted into the cloak, are strongly discouraged and are merely applied, as for all cloaks, at staff discretion and with the consent of grouping contacts involved and the user.
To request a cloak, just provide us with your user's main IRC nickname and the proposed cloak. You can request a listing of cloaks or cloaking changes at one time. If information technology's a short list, cheque with commencement level support and we'll be happy to assistance. If it's a longer list, delight electronic mail it to support at freenode dot net and mark your email as containing cloak updates for your projection. You can still check with beginning-level support to speed things along.
Nosotros'll process your cloak updates as soon every bit we can. Global changes, such equally those involved in a group name change, will probably take longer.
Copyright © 2002 – 2016 by freenode
Comments to e-mail address: back up at freenode dot net
How To Register Public Channel In Freenode,
Source: http://bit.ly/24VcOcj
Posted by: gonzalezwerharters.blogspot.com
0 Response to "How To Register Public Channel In Freenode"
Post a Comment