like every technical and public facility, a system needs administrators / watchdogs / contact persons. In an IRC chat, this contact person represents the so-called IRC-OP.
IRCOP = Internet relay chat operator
IRCOP has nothing to do with a COP.
He has a specific task depending on his status.
Because not every IRCOP has the same powers / rights.
We assume a network with services.
|Services admin / rootNet adminServer administratorTechAdminCo administrator- —GlobalIRCOPLocal– -HelpOp -HelpOp|
First and foremost is the ServicesRoot The ServiceRoot is, so to speak, the master of the services (OperServ, nickserv, USW)
As long as they are online, it is the most powerful Admin / IRCOP of the network, so to speak.
All admins, server administrators, network administrators, technical administrators and the administrator stand under him.
If there were no services there, it would be classified as ServerAdmin.
Whereby according to the status he would still be ServicesAdmin, just without services (lobby).
Since admins can sometimes set all the flags themselves, they have the same status in terms of rank. The different nicknames should just reflect the position of the operating room. So who is responsible for what.
In the middle we see the normal IRCOP, no after flags its powers can change again.
The global IRCOP can, for example, kick / kill / clinch any USER in a network. A local IRCOP, however, only if the user is on the same server (local server).
A HElp – Op, if it has + h as the only flag, is the lowest IRCOP at all. He has no great rights in itself. He may only get a message from certain admins if someone needs help somewhere.
In addition, the normal user should be shown that this user is offering his help.
Usually this status is always linked to another status.
So every admin / IRCOP can use this status.
Again to the tasks of the individual IRCOPs 🙂
|Tasks of the IRCOPs|
|IRCOPs / admins should defend the trouble-free chat process.|
that is, if some servers have split, they bring them back to the network. If a user or a user group is noticed unpleasantly, the respective admin has to exclude the user or the user group from chat.
If a user has forgotten the password for his nickname (if NickServ is available)
then the ServicesAdmin is responsible, for example, that the respective password is sent to the respective e-mail.
If a USER notices heavy crimes (child pornography, etc.), he / she has the DUTY to report this. Ideally an IRCOP so that it can first determine the IP of the respective USER.
However, this process is not a special administrative task, but every CITIZEN has the duty to report such acts.
These are the duties of every citizen of the FRG. And morally, everyone’s duties!
Since this can only be punished on the basis of the IP, an admin may have to be notified
How do I become an IRCOP?
- sigh *
If you really want to become IRCOP, you should build your own network. You can find out how to do this under “ How can I set up my own IRC-Net? „
However, most of them expect the respective admin to simply enter them.
- sigh *
If you think you have earned IRCOP / admin rights in another network, then the first thing you should do is rate yourself well.
No admin of a large network will give you IRCOP status just for fun.
Here I have summarized some questions that I personally rate as important.
An IRCOP should primarily complement the team.
You don’t need power addicts who want to show their friends what they have already achieved 😉
Have you ever dealt with programming an IRCD or the services? `If
Which projects can you show?
Which IRCD did you deal with?
Are you able to create your own modules for IRCServices?
If so, please pick up a test assignment.
If not, then you should have other benefits;)
Which IRCD and which services would you prefer?
Why this one?
What speaks against Unreal
What speaks for Unreal?
What is wrong with Bahamut?
What are the advantages of Bahamut?
If you could become an IRCOP in our network, what would you change first?
In terms of structure?
Which new service modules would you recommend?