Re: Oper Block Issues

[Dingo]

This is in response to a locked post: http://forums.unrealircd.com/viewtopic. ... 410#p35410

Why was it locked? I was never given the chance to even explain what's wrong. I'm also very well grown up and not seeking "IRC God" status. Yes, I am aware such a thing would scare off people. I'm not out to take over channels and so forth, and very well aware of the risks of losing users by doing such. The reason behind having those abilities is to remove unwanted content and abusive users off the network.

I apologise for the repost but I can't think of a reason to lock a post like that. I was asking a valid question as those abilities we working fine. Which even caused it to affect Anope some how. I wasn't even able to interact with the services. I omitted Anope as I was trying to root out my problem to make sure I didn't overlook something.

[katsklaw]

However, the only time I can utilise the said commands I'm having problems with, is when I create a channel. Which seems to defeat the purpose of having an IRC operator.

Every time I try to perform a kick or mode in a channel I keep getting "You're not channel operator."

Here is why it was most likely locked. This statement explains the "IRC God" thing. There are far more cases of users thinking they can do anything once an IRCop and that is simply not true. Your statement is worded verbatum of such a believer.

IRCop status is NOT the same as CHANNEL operator status. IRCops are to maintain their respective server NOT channels. My reply is a direct reaction to your "defeat the purpose of the IRCOp". 100000% false! IRCops are to maintain the server ... period. Their names are a direct and literal label. Channel operators/chanops/chops operate channels. They need at least op status (@). IRCop is IRC Operator, and that access is ONLY to maintain servers. /rehash, /squit, /connect and the like.

Some confusion is generated when you introduce /sa* commands to ignorant operators and it can seem like IRCops are supposed to have unrestricted access to everything. Again 1000000% false. /sa* commands are more like a failsafe to allow opers the ability to take back channels that were taken over when services is absent. Nothing more. Since the advent splitop prevention, /sa* commands aren't really even needed anymore. With Unreal as most other ircds I can think of off the top of my head, IRCops dont even need to be in a channel to affect it. One can get a list of users, even +i users, in the channel and wipe out the touble makers and not even be in the channel .. let alone have ops status.

I suggest you google "ircop myths" and read a few of the files. Many of them pertain to specific nets like DALnet and EFnet, but still have very valueable information.

With that said, I'm locking this thread too. This topic is well covered 43653468754777723455589965 times already, thus not needed yet again. You are more than welcome to PM me and I'll explain further after you have read the documents I've suggested.

PS: Do NOT create another thread on this subject!

PPS: Your inability to interact with services is not directly related to your oper block other than most services require you to be opered as just 1 of several factors required to gain access. Since you admit you have opered, it's no longer relavent.